Start Using SAP HANA 2.0, express edition (Virtual Machine Method)

The part "(Optionl) Install SAP Enterprise Architecture Designer ..." seems not to be correctly documented for HANA Express 2 because:

the file XSACHANAEAD00_0.ZIP is not conteined in the mentioned directroy but in the subdirectory "XSA_CONTENT_10"
command to install is "xs install XSACHANAEAD00_0.ZIP ..." (ZIP must be in capital letters)
the installation failed during deployment with this feedback in the command line:

Unexpected error: Error detecting MTA major schema version_ Error while parsing YAML string:
_schema-version "2.0.0"
ID: com.sap.hana.eadesigner.ext
extends: com.sap.hana.eadesigner
modules:

name: eadesigner-backend
properties:
ADMIN_PASSWORD:

while parsing a block collection
in 'string', line 6, column 3:
- name: eadesigner-backend
^
expected , but found Key
in 'string', line 7, column 3:
properties:
^

I have the same issue. Tried so many variations (also opened) another thread for the same issue without looking into this.  Same error stuck w/o any resolutions

Can you attach your mtaext file?
The indentation (number of spaces) is very important in that file.

As xiaoyun59 mentions, spacing problems in mtaext will cause the issue you reported.
Here's the spacing recommendation information from the tutorial Installing SAP HANA 2.0, express edition (Virtual Machine Method)

Log in as hxeadm.

Create a text file, copy the following content to it, replacing the variable  with your choice of a temporary administrator password for the first login, and save it as firstTime.mtaext:
_schema-version: "2.0.0"
ID: com.sap.hana.eadesigner.ext
extends: com.sap.hana.eadesigner

modules:
  - name: eadesigner-backend
  properties:
     ADMIN_PASSWORD: <tempPwd>

Note: Make sure that properties and ADMIN_PASSWORD are indented with spaces (not tab). There are two spaces in front of properties.

Note: If you do not specify this temporary password file in your installation command, the installation will proceed normally, but you will not be able to log into SAP EA Designer. We recommend that your temporary password should contain 8 or more characters including a mix of numbers and uppercase and lowercase letters. Once installation is complete, you should delete this file.

Hope this helps,
John C.

EA Designer installer pathnames and filenames have been updated in Start Using SAP HANA 2.0, express edition (Virtual Machine Method).
-John C.

I did attach the file. did u see and get it?
Thanks
On Thu, Jan 12, 2017 at 2:17 AM, xiaoyun59<EMAIL_ADDRESS>wrote:

Can you attach your mtaext file?
The indentation (number of spaces) is very important in that file.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SAPDocuments/Tutorials/issues/1224#issuecomment-272093822,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXtqeRXAhTrMwjiuhUWTl08a4sDxAHG6ks5rRdOngaJpZM4LS0OG
.


Modify -p autogen-subclasses to print all descendants of specified superclasses

NB this diff is currently stacked on https://github.com/sorbet/sorbet/pull/916. I'll rebase this PR on that one again after I implement the requested changes from code review.

Moves configuration for filepath ignoring (i.e., ignore constants in test/, etc.) and which parent classes we want to generate SUBCLASSES for (i.e., InheritedClassesStep::CLASSES) to command-args (--autogen-subclasses-ignore and --autogen-subclasses-parent, respectively).

I made a new ignore flag instead of using --ignore b/c this ends up saving an extra call to Sorbet in SorbetAutogen (b/c we don't want to ignore stuff with -p msgpack).

Modifies -p autogen-subclasses (should prob rename to -p autogen-descendants) to print all descendants of the classes listed.

This should provide some speedup but it's mostly to clean up the interface b/w Sorbet and Ruby (by passing config to Sorbet via CLI flags instead of e.g., adding more data to Sorbet's output and filtering in Ruby).
Haven't yet looked at writing the .rb/.yaml (i.e., porting AbstractConstantSteps behavior) from Sorbet but I can in a follow-on. That may involve updating DependencyDB from Sorbet.
Motivation

InheritedClasssesStep (and DescendantsMap) in Sorbet
Test plan

See included automated tests.

Some minor stuff, but the direction looks right to me.


Fix in windows

This plugin can not work in my windows system, l create this fix.
l do not test in other system, l guess it will not break in other system

Sorry for the late response, somehow I didn't see this pull request. Thank you for it, but for now I will not merge it, since I currently don't have a Windows machine to test it. And second since this is the part of the addon I'm scared of touching again without being tested completely.
So I'll wait for more issue reports for now.

I can confirm it works. Renmu123's fix solved the problem for me (Windows 11).


result for MVTec

Well job! I notice that you use the class 'leather' in MVTec dataset to show the segmentation performance. So, I wonder whether you do a complete experiment on MVTec and report the image/pixel AUROC?

Hi,
We just performed preliminary experiments and showed some example samples.
Thanks,
Julian

From: DidiD1 @.>
Sent: 04 December 2023 02:47
To: Julian-Wyatt/AnoDDPM @.>
Cc: Subscribed @.***>
Subject: [Julian-Wyatt/AnoDDPM] result for MVTec (Issue #30)
Well job! I notice that you use the class 'leather' in MVTec dataset to show the segmentation performance. So, I wonder whether you do a complete experiment on MVTec and report the image/pixel AUROC?
—
Reply to this email directly, view it on GitHubhttps://github.com/Julian-Wyatt/AnoDDPM/issues/30, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKRBCM3BQXBQ2K5L5Z6ZRW3YHU2U5AVCNFSM6AAAAABAFIYOM2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZDEOJQHEZTMOI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Add Registry to AbstractJobStore so that uncleaned job stores can be listed

Currently the AWS and Azure job stores maintain a registry to prevent eventual consistency issues. Beyond this concern it is a common problem where users forget to clean a job store and then run into issues later such as running out of buckets, or even incurring extra charges from a storage service.
If each job store maintains a registry we can easily implement a command line function that lists all uncleaned job stores as well as other relevant information (e.g. when the job store was created, when it was last used, etc... ).

Toil needs a strongly consistent answer to the question whether a job store exists or not. The purpose of the registry domain in the AWS job store is to work around  eventual consistency of SDB domain creation.
There are simpler ways of listing existing job stores by looking for buckets, domains etc that match a certain naming pattern. No need for a registry.
I vote for closing this as won't fix.


Fixes failing app component e2e test

Good morning,
the assert 'should have a title' in app.component.e2e.ts currently fails on the latest master.
Reason: The assert expects the title to be 'Angular 2 Seed', but is actually 'Put name of your app here' (which was introduced by the commit 598efd5f669def1a9f573007a958912117275d9d)
Possible solutions:
A)

Fix the assert in app.component.e2e.ts to expect 'My Angular 2 App'
Comment out the this.APP_TITLE in project.config.ts

Pro:

Set expectations in the e2e test to the baseline configuration of the seed
Commenting out the override in project.config.ts to still have the example of how to change the tile, yet not alter the baseline seed configuration

Con:

The override of the project specific app title would be reverted

B)

Fix the assert in app.component.e2e.ts to expect 'Put name of your app here'

Pro:

Assert would be fixed to expected the overriden app title

Con:

Expectation would deviate from baseline seed configuration

Proposed soultion:
The attached commit is target at solution A).
Greetings
Christian

Yess, thanks for the catch!


rebar3 templates not found when compiled with R15B-03

I have a system with R15B-03, when I get the nightly I can run
% rebar3 new release myrelease

with no issues, however, when I following the instructions for installing from source
% git clone https://github.com/rebar/rebar3.git
% cd rebar3
% ./bootstrap
% DEBUG=1 ./rebar3 new release myrelease
===> Expanded command sequence to be run: [{default,new}]
===> Available templates: []

===> Available templates: []

template not found.

uh, interesting. Will have to check, but if a newer version works but not an older one, this would mean the compilation process for the escriptize task is failing or behaving differently on R15B03, but not the access to the packaged template files in the final escript.

Found the cause in the changelogs of R16B: http://www.erlang.org/download/otp_src_R16B.readme
  OTP-10812  == stdlib ==

	      filelib:wildcard("some/relative/path/*.beam", Path) would
	      fail to match any file. That is, filelib:wildcard/2 would not
	      work if the first component of the pattern did not contain
	      any wildcard characters. (A previous attempt to fix the
	      problem in R15B02 seems to have made matters worse.)

	      (Thanks to Samuel Rivas and Tuncer Ayaz.)

	      There is also an incompatible change to the Path argument. It
	      is no longer allowed to be a binary.

The bug can only be fixed by copy/pasting the wildcard info for this. This function is used in 23 different places within Rebar3. I'm not sure whether we should mark it wontfix and that's the end of it. @djnym is this fairly critical for you?

No, not really, I was just testing, I most likely will just stay with rebar 2 for now.  Our build systems still use R15B03, and you appeared to support that based on travis, but if you plan to drop R15 support I'd understand.

I'll be closing this. With OTP 19 on the way, I don't think we'll realistically take the time to fix it. Sorry for the inconvenience.


Angular Route/URL error after refresh

Can you help how to overcome virtual route for angular compatible with eel after refresh, hosting i use .htaccess but in this i have no clue to proceed

i found solution, use this reference, but python eel can't invoke function from js eel, from my understanding, python init -> my directory and start without detecting eel.expose in every component in angular, except eel.expose in index.html

Update for Angular, python eel can invoke simple function put on index.html
step 1.  app.component.ts,
window["dummy"] = new Subject() //<=== Subject come from rxjs
window["dummy"].subscribe((res) => {
//do anything you want from data subscribe
console.log(res);
// {"msg":"something from python"}
})
step 2. index.html
eel.expose(sendData);
function sendData(data){
if(data){
window["dummy"].next(data); //<== window["dummy"] created as Subject Instance from rxjs
}
}
!!! make sure key "dummy" created on window object as Subject Instance...
then on python, just call function declare on index.html....
eel.sendData({"msg":"something from python"})
try to make angular service listen to window["dummy"] based on your system requirement.... or make it dynamic...


Add PushDownAggregate optimization

Which issue does this PR close?

Closes #4772
Rationale for this change

See the issue.
What changes are included in this PR?

Added a new optimization PushDownAggregate
Added it to the default list in optimizer.rs.
Are these changes tested?

Unit tests inside  push_down_aggregate.rs.
Added tests to pg_compat_union.slt to ensure, that computation results are still correct.
Are there any user-facing changes?
No.

No, I'm afraid this optimization is useless. Could you please check the physical plan ?
I think in the physical plan phase, there was already the partial agg and final agg and actually the partial agg is already pushed down.

@mingmwang Thank you for your observation. Let's make an experiment...
Experiment
Copied arrow-datafusion/datafusion/core/tests/data/aggregate_simple.csv to aggregate_simple.csv.
Script:
use datafusion::prelude::*;

#[tokio::main]
async fn main() -> datafusion::error::Result<()> {
    let ctx = SessionContext::new();

    ctx.register_csv(
        "my_table",
        "datafusion/core/tests/data/aggregate_simple.csv",
        CsvReadOptions::default(),
    ).await?;
    ctx.register_csv(
        "my_table2",
        "datafusion/core/tests/data/aggregate_simple2.csv",
        CsvReadOptions::default(),
    ).await?;

    let sql = "SELECT COUNT(*) FROM (SELECT * from my_table UNION ALL SELECT * from my_table2)";
    let df = ctx.sql(sql).await?;
    df.clone().explain(true, false)?.show().await?;
    df.show().await?;

    Ok(())
}

Optimized logical and physical plans are below.
Without push_down_aggregate
Explain after optimizations
...
| logical_plan                                               | Aggregate: groupBy=[[]], aggr=[[COUNT(UInt8(1))]]                                                                                |
|                                                            |   Union                                                                                |
|                                                            |     TableScan: my_table projection=[c1]                                                                                |
|                                                            |     Projection: my_table2.c1 AS my_table.c1                                                                                |
|                                                            |       TableScan: my_table2 projection=[c1]
...
| physical_plan                                              | AggregateExec: mode=Final, gby=[], aggr=[COUNT(UInt8(1))]                                                                                |
|                                                            |   CoalescePartitionsExec                                                                                |
|                                                            |     AggregateExec: mode=Partial, gby=[], aggr=[COUNT(UInt8(1))]                                                                                |
|                                                            |       RepartitionExec: partitioning=RoundRobinBatch(10), input_partitions=2                                                                                |
|                                                            |         UnionExec                                                                                |
|                                                            |           CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple.csv]]}, has_header=true, limit=None, projection=[c1]    |
|                                                            |           ProjectionExec: expr=[c1@0 as my_table.c1]                                                                                |
|                                                            |             CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple2.csv]]}, has_header=true, limit=None, projection=[c1] |
|                                                            |                                                                                |
+------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

These CSV files will be naively mixed together with RoundRobinBatch - only to count the rows at the end! 😧

actually the partial agg is already pushed down.

❗ No, it isn't...
With push_down_aggregate
Explain after optimizations
...
| logical_plan                                               | Projection: SUM(COUNT(aggr_1)) AS COUNT(UInt8(1))                                                                                |
|                                                            |   Aggregate: groupBy=[[]], aggr=[[SUM(COUNT(aggr_1))]]                                                                                |
|                                                            |     Union                                                                                |
|                                                            |       Aggregate: groupBy=[[]], aggr=[[COUNT(aggr_1)]]                                                                                |
|                                                            |         Projection: UInt8(1) AS aggr_1                                                                                |
|                                                            |           TableScan: my_table projection=[c1]                                                                                |
|                                                            |       Aggregate: groupBy=[[]], aggr=[[COUNT(aggr_1)]]                                                                                |
|                                                            |         Projection: UInt8(1) AS aggr_1                                                                                |
|                                                            |           TableScan: my_table2 projection=[c1]
...
| physical_plan                                              | ProjectionExec: expr=[SUM(COUNT(aggr_1))@0 as COUNT(UInt8(1))]                                                                                |
|                                                            |   AggregateExec: mode=Final, gby=[], aggr=[SUM(COUNT(aggr_1))]                                                                                |
|                                                            |     CoalescePartitionsExec                                                                                |
|                                                            |       AggregateExec: mode=Partial, gby=[], aggr=[SUM(COUNT(aggr_1))]                                                                                |
|                                                            |         UnionExec                                                                                |
|                                                            |           AggregateExec: mode=Final, gby=[], aggr=[COUNT(aggr_1)]                                                                                |
|                                                            |             CoalescePartitionsExec                                                                                |
|                                                            |               AggregateExec: mode=Partial, gby=[], aggr=[COUNT(aggr_1)]                                                                                |
|                                                            |                 ProjectionExec: expr=[1 as aggr_1]                                                                                |
|                                                            |                   RepartitionExec: partitioning=RoundRobinBatch(10), input_partitions=1                                                                                |
|                                                            |                     CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple.csv]]}, has_header=true, limit=None, projection=[c1]  |
|                                                            |           AggregateExec: mode=Final, gby=[], aggr=[COUNT(aggr_1)]                                                                                |
|                                                            |             CoalescePartitionsExec                                                                                |
|                                                            |               AggregateExec: mode=Partial, gby=[], aggr=[COUNT(aggr_1)]                                                                                |
|                                                            |                 ProjectionExec: expr=[1 as aggr_1]                                                                                |
|                                                            |                   RepartitionExec: partitioning=RoundRobinBatch(10), input_partitions=1                                                                                |
|                                                            |                     CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple2.csv]]}, has_header=true, limit=None, projection=[c1] |
|

There is no mixing of the file contents.
To AggregateExec: mode=Partial, gby=[], aggr=[SUM(COUNT(aggr_1))] are going only two rows.

@mingmwang You gave a great idea - it should be a physical plan optimization! 💡
The optimization should push down partial aggregate though union:
...
| logical_plan                                               | Aggregate: groupBy=[[]], aggr=[[COUNT(UInt8(1))]]                                                                                |
|                                                            |   Union                                                                                |
|                                                            |     TableScan: my_table projection=[c1]                                                                                |
|                                                            |     Projection: my_table2.c1 AS my_table.c1                                                                                |
|                                                            |       TableScan: my_table2 projection=[c1]
...
| physical_plan                                              | AggregateExec: mode=Final, gby=[], aggr=[COUNT(UInt8(1))]                                                                                |
|                                                            |   CoalescePartitionsExec                                                                                |                                                                                |
|                                                            |       RepartitionExec: partitioning=RoundRobinBatch(10), input_partitions=2                                                                                |
|                                                            |         UnionExec
|                                                            |           AggregateExec: mode=Partial, gby=[], aggr=[COUNT(UInt8(1))]                                                                                |
|                                                            |             CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple.csv]]}, has_header=true, limit=None, projection=[c1]    |
|                                                            |           AggregateExec: mode=Partial, gby=[], aggr=[COUNT(UInt8(1))]
|                                                            |             ProjectionExec: expr=[c1@0 as my_table.c1]                                                                                |
|                                                            |               CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple2.csv]]}, has_header=true, limit=None, projection=[c1] |
|                                                            |                                                                                |
+------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Optimization in the logical plan gave unnecessary doubled final-partial aggregate pair.
@mingmwang What do you think?

@mingmwang You gave a great idea - it should be a physical plan optimization! 💡
The optimization should push down partial aggregate though union:
...
| logical_plan                                               | Aggregate: groupBy=[[]], aggr=[[COUNT(UInt8(1))]]                                                                                |
|                                                            |   Union                                                                                |
|                                                            |     TableScan: my_table projection=[c1]                                                                                |
|                                                            |     Projection: my_table2.c1 AS my_table.c1                                                                                |
|                                                            |       TableScan: my_table2 projection=[c1]
...
| physical_plan                                              | AggregateExec: mode=Final, gby=[], aggr=[COUNT(UInt8(1))]                                                                                |
|                                                            |   CoalescePartitionsExec                                                                                |                                                                                |
|                                                            |       RepartitionExec: partitioning=RoundRobinBatch(10), input_partitions=2                                                                                |
|                                                            |         UnionExec
|                                                            |           AggregateExec: mode=Partial, gby=[], aggr=[COUNT(UInt8(1))]                                                                                |
|                                                            |             CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple.csv]]}, has_header=true, limit=None, projection=[c1]    |
|                                                            |           AggregateExec: mode=Partial, gby=[], aggr=[COUNT(UInt8(1))]
|                                                            |             ProjectionExec: expr=[c1@0 as my_table.c1]                                                                                |
|                                                            |               CsvExec: files={1 group: [[/home/hello/repo/arrow-datafusion/datafusion/core/tests/data/aggregate_simple2.csv]]}, has_header=true, limit=None, projection=[c1] |
|                                                            |                                                                                |
+------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Optimization in the logical plan gave unnecessary doubled final-partial aggregate pair.
@mingmwang What do you think?

I think even during the physical planning phase, push down the partial aggregate though repartition + union might not give performance benefit, because it might reduce the parallism of the partial aggregate.

My intuitions says, that 2 partial aggregates in PARALLEL branches would be more susceptible to parallelization - than one big partial aggregate. 🧐
Could you clarify, why that's not the case?

My intuitions says, that 2 partial aggregates in PARALLEL branches would be more susceptible to parallelization - than one big partial aggregate. 🧐
Could you clarify, why that's not the case?

This is related to how UnionExec is actually executed:
For example, if we have a plan fragment like below, if each CsvExec's parallelization is 1, then the AggregateExec's parallelization is 2
AggregateExec(2)
    UnionExec(2)
       CsvExec(1)
       CsvExec(1)

If we push down the  AggregateExec through UnionExec like below,  the total parallelization of AggregateExec is still 2.
This is what I mean the pushdown is useless.
 UnionExec(2)
    AggregateExec(1)
       CsvExec(1)
   AggregateExec(1)
       CsvExec(1)

Now we take the RepartitionExec into consideration, if the RepartitionExec change the parallelization to 4, the parallelization of AggregateExec is 4
AggregateExec(4)
   RepartitionExec(4)
       UnionExec(2)
         CsvExec(1)
         CsvExec(1)

If we push down the AggregateExec  through RepartitionExec + UnionExec ,  it will reduce the parallelization of AggregateExec to 2 and will not get performance benefits
 RepartitionExec(4)
     UnionExec(2)
        AggregateExec(1)
           CsvExec(1)
        AggregateExec(1)
           CsvExec(1)

Hope this explains.

@mingmwang Thank you for a thorough explanation! 🙂 It makes a perfect sense.
Yeah. Union is only a concatenated list of partitions... itself it does no performance impact - that's what I've forgotten! 😬
So the only performance issue is: when RepartitionExec(4) can be avoided? When we have in all branches equally-sized partitions, and their amount allows for a sensible parallelization - then the reshuffle could be avoided.
But:

it is not related in a specific way to the union, it's a general issue
it would require data from some Metastore

To sum up, it looks like this PR should be closed without merge. 😭

I think you can close this PR.
But you can file another ticket to track the RepartitionExec enhancement.
It is better if you can give some real SQL examples with the physical plan fragments generated by the DataFusion optimizer which can prove the RepartitionExec is unnecessary.

Closing per comments above


empack_config file filter does not seem to be working

Description
The file filter specified in XeusAddon.empack_config is not used.
https://github.com/jupyterlite/xeus/blob/main/jupyterlite_xeus/add_on.py#L263-L287
Reproduce
jupyter lite build --XeusAddon.empack_config=empack_config.yml

Context
It might be better handled as follows
https://github.com/jupyterlite/xeus-python-kernel/blob/main/jupyterlite_xeus_python/build.py#L321
pack_env(
      env_prefix=self.prefix,
      relocate_prefix="/",
      outdir=out_path,
      use_cache=True,
      **pack_kwargs,
)

Thank you for opening an issue. I blame myself for not testing the feature properly.
Would you like to open a PR to get credits for your fix?

I would like to!
I have created a PR here.
https://github.com/jupyterlite/xeus/pull/53


Write proposal for sender-side routing

User Story
As a sender I want to be able to dictate where a message gets routed, so that the delivery of my message isn't dependent on receiver settings.
Description/Use Case
This may be useful for ETOR (TI) and for ELIMS work.
In ELIMS, an ELIMS sender may want to send a message to a given state and want to do that regardless of that state receiver's given filters. In the ELIMS case, this would be one sender sending messages to potentially many different receivers.
For ETOR (TI), a sender may know exactly what receiver (like Trusted Intermediary) should receive a message, and may only ever send to that receiver. Having the sender indicate that receiver may be simpler than relying on existing filtering to enforce that 1:1 connection of sender to receiver.
Another use case: Presently, the CDC has routing software similar to AIMS that is "route not read." More information can be found here: https://www.cdc.gov/phin/tools/phinms/index.html.  There are some states that still insist on using PHINMS, and some CDC programs that still use it for delivery. This software is purportedly very old and flakey (it uses ebXML), and there could be major value added to the CDC if RS was able to replace PHINMS' "route not read." and onboard their current senders and receivers.
These are slightly different use cases, but the proposal resulting from this story should address all.
Risks/Impacts/Considerations
The implications on the receiver side should be considered when writing and reviewing the proposal. A receiver should have some say in who gets to send to them, and filters probably should not be bypassed altogether. Maybe a receiver can specify a list of trusted senders? Maybe sender-side routing replaces a jurisdictional filter check, but all other receiver filters are still applied? Whatever the solution, it should not introduce the possibility of receivers receiving undesired data without having the ability to prevent it.
We also need to consider the possibility of skipping the UP steps all-together. It may be necessary for RS, in some use cases, to NOT convert messages received to an internal FHIR format and instead just deliver the original message received...
Dev Notes
It may be useful to reference the routeTo URL parameter from the legacy pipeline. This is a version of "sender-side routing", even if it might be preferable to have something controlled at the settings level.
It may be useful to reference #8497 for some considerations and ideas on this topic.
Acceptance Criteria

[ ] A proposal has been written, reviewed, and checked into the repo. This proposal should include a plan for sender-side routing for both ELIMS and ETOR applications (in other words, for 1-to-1 sender-to-receiver relationships, and for 1-to-many sender-to-receiver relationships) without being specific to those particular applications (in other words, the design can be extended to future use cases).
[ ] Follow up tickets have been written and assigned to the appropriate epic(s)

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @JessicaWNava @jimmyfagan @luis-pabon-tf @mkalish @thetaurean

@jimmyfagan @arnejduranovic Do we still need this ticket given that we are not doing sender side routing anymore?

@bishoyayoub yes but let's move it to icebox because we may need something like this in the future, and unassign any epics


tracker & controller need information from each other to calculate most recent pose.

Currently the device managers call .update() and that's it. However, to calculate pose, the tracker(s) needs to know the controller colours from the controllers, and the controllers need to know the latest position from the tracker(s). So we need to replace the device manager .update() with 3 steps, and change the order around a little.
void DeviceManager::update()
{
    m_controller_manager.update();
    m_tracker_manager.update();
    m_hmd_manager.update();
}

becomes
void DeviceManager::update()
{
    m_tracker_manager.poll(); // Update tracker count and poll video frames
    m_controller_manager.poll(); // Update controller counts and poll button/IMU state
    m_hmd_manager.poll(); // Update tracker count

    m_tracker_manager.updateStateAndPredict(); // Get controller colors and update tracking blob positions/predictions
    m_controller_manager.updateStateAndPredict(); // Compute pose/prediction of tracking blob+IMU state
    m_hmd_manager.updateStateAndPredict(); // Get the pose + prediction for HMD

    m_tracker_manager.publish(); // publish tracker state to any listening clients (probably only used by ConfigTool)
    m_controller_manager.publish(); // publish controller state to any listening clients  (common case)
    m_hmd_manager.publish(); // publish hmd state to any listening clients (probably only used by ConfigTool)
}

The device managers still need information from each other. Maybe they can do this via the DeviceManager singleton (i.e., DeviceManager::getInstance()->getControllers) or we can pass in context arguments to the updateStateAndPredict functions.

The framework for this is now in place and running. You can see the position data being feed through here in the tracker calibration tool: https://www.youtube.com/watch?v=FFJqLH_dkRw
I'm going to create separate tasks/bugs for the DS4 tracking and the ellipse fitting issue


Debug build fails for an undeclared identifier

tensorflow/core/BUILD:2014:1: C++ compilation of rule '//tensorflow/core:core_cpu_base' failed (Exit 1): compute failed: error executing command
  (cd /home/user/.cache/bazel/_bazel_user/a13281f85a8fbd2310ce125e40037b63/execroot/org_tensorflow && \
  exec env - \
    COMPUTECPP_TOOLKIT_PATH=/opt/ComputeCpp-CE-0.9.0-Ubuntu-16.04-x86_64 \
    PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl \
    PWD=/proc/self/cwd \
    PYTHON_BIN_PATH=/usr/bin/python3.6dm \
    PYTHON_LIB_PATH=/usr/lib/python3.6/site-packages \
    TF_NEED_COMPUTECPP=1 \
    TF_NEED_CUDA=0 \
    TF_NEED_OPENCL_SYCL=1 \
    TF_SYCL_BITCODE_TARGET=spir64 \
  /opt/ComputeCpp-CE-0.9.0-Ubuntu-16.04-x86_64/bin/compute -ffunction-sections -fdata-sections -fPIE -fno-omit-frame-pointer -Wall -g '-std=c++11' -fsycl-ih-last -sycl-driver -Xclang -cl-denorms-are-zero -Xclang -cl-fp32-correctly-rounded-divide-sqrt -Xclang -cl-mad-enable -sycl-target spir64 '-DTENSORFLOW_USE_SYCL=1' '-DEIGEN_USE_SYCL=1' '-DEIGEN_HAS_C99_MATH=1' '-DEIGEN_HAS_CXX11_MATH=1' -Wno-unused-variable -Wno-unused-const-variable -MD -MF bazel-out/k8-py3-dbg/bin/tensorflow/core/_objs/core_cpu_base/tensorflow/core/common_runtime/shape_refiner.pic.d '-frandom-seed=bazel-out/k8-py3-dbg/bin/tensorflow/core/_objs/core_cpu_base/tensorflow/core/common_runtime/shape_refiner.pic.o' -fPIC -DEIGEN_MPL2_ONLY -D__CLANG_SUPPORT_DYN_ANNOTATION__ -DTENSORFLOW_USE_ABSL -DTF_USE_SNAPPY -iquote . -iquote bazel-out/k8-py3-dbg/genfiles -iquote external/bazel_tools -iquote bazel-out/k8-py3-dbg/genfiles/external/bazel_tools -iquote external/eigen_archive -iquote bazel-out/k8-py3-dbg/genfiles/external/eigen_archive -iquote external/local_config_sycl -iquote bazel-out/k8-py3-dbg/genfiles/external/local_config_sycl -iquote external/opencl_headers -iquote bazel-out/k8-py3-dbg/genfiles/external/opencl_headers -iquote external/com_google_absl -iquote bazel-out/k8-py3-dbg/genfiles/external/com_google_absl -iquote external/nsync -iquote bazel-out/k8-py3-dbg/genfiles/external/nsync -iquote external/gif_archive -iquote bazel-out/k8-py3-dbg/genfiles/external/gif_archive -iquote external/jpeg -iquote bazel-out/k8-py3-dbg/genfiles/external/jpeg -iquote external/protobuf_archive -iquote bazel-out/k8-py3-dbg/genfiles/external/protobuf_archive -iquote external/com_googlesource_code_re2 -iquote bazel-out/k8-py3-dbg/genfiles/external/com_googlesource_code_re2 -iquote external/farmhash_archive -iquote bazel-out/k8-py3-dbg/genfiles/external/farmhash_archive -iquote external/fft2d -iquote bazel-out/k8-py3-dbg/genfiles/external/fft2d -iquote external/highwayhash -iquote bazel-out/k8-py3-dbg/genfiles/external/highwayhash -iquote external/png_archive -iquote bazel-out/k8-py3-dbg/genfiles/external/png_archive -iquote external/zlib_archive -iquote bazel-out/k8-py3-dbg/genfiles/external/zlib_archive -Ibazel-out/k8-py3-dbg/bin/external/opencl_headers/_virtual_includes/OpenCL-Headers -isystem external/eigen_archive -isystem bazel-out/k8-py3-dbg/genfiles/external/eigen_archive -isystem bazel-out/k8-py3-dbg/bin/external/eigen_archive -isystem external/local_config_sycl/sycl -isystem bazel-out/k8-py3-dbg/genfiles/external/local_config_sycl/sycl -isystem bazel-out/k8-py3-dbg/bin/external/local_config_sycl/sycl -isystem external/local_config_sycl/sycl/include -isystem bazel-out/k8-py3-dbg/genfiles/external/local_config_sycl/sycl/include -isystem bazel-out/k8-py3-dbg/bin/external/local_config_sycl/sycl/include -isystem external/nsync/public -isystem bazel-out/k8-py3-dbg/genfiles/external/nsync/public -isystem bazel-out/k8-py3-dbg/bin/external/nsync/public -isystem external/gif_archive/lib -isystem bazel-out/k8-py3-dbg/genfiles/external/gif_archive/lib -isystem bazel-out/k8-py3-dbg/bin/external/gif_archive/lib -isystem external/protobuf_archive/src -isystem bazel-out/k8-py3-dbg/genfiles/external/protobuf_archive/src -isystem bazel-out/k8-py3-dbg/bin/external/protobuf_archive/src -isystem external/farmhash_archive/src -isystem bazel-out/k8-py3-dbg/genfiles/external/farmhash_archive/src -isystem bazel-out/k8-py3-dbg/bin/external/farmhash_archive/src -isystem external/png_archive -isystem bazel-out/k8-py3-dbg/genfiles/external/png_archive -isystem bazel-out/k8-py3-dbg/bin/external/png_archive -isystem external/zlib_archive -isystem bazel-out/k8-py3-dbg/genfiles/external/zlib_archive -isystem bazel-out/k8-py3-dbg/bin/external/zlib_archive -DGEMMLOWP_ALLOW_SLOW_SCALAR_FALLBACK '-DDISABLE_SKINNY=1' '-DTENSORFLOW_SYCL_NO_HALF=1' '-DTENSORFLOW_SYCL_NO_DOUBLE=1' -sycl-compress-name -DEIGEN_AVOID_STL_ARRAY -Iexternal/gemmlowp -Wno-sign-compare '-ftemplate-depth=900' -msse3 -pthread -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -no-canonical-prefixes -c tensorflow/core/common_runtime/shape_refiner.cc -o bazel-out/k8-py3-dbg/bin/tensorflow/core/_objs/core_cpu_base/tensorflow/core/common_runtime/shape_refiner.pic.o)
In file included from <built-in>:1:
In file included from ./tensorflow/core/common_runtime/shape_refiner.cc:15:
In file included from ./tensorflow/core/common_runtime/shape_refiner.h:20:
In file included from ./tensorflow/core/common_runtime/graph_runner.h:23:
In file included from ./tensorflow/core/common_runtime/device.h:35:
In file included from ./tensorflow/core/framework/allocator.h:23:
In file included from ./tensorflow/core/framework/numeric_types.h:20:
In file included from ./third_party/eigen3/unsupported/Eigen/CXX11/Tensor:1:
In file included from external/eigen_archive/unsupported/Eigen/CXX11/Tensor:15:
In file included from external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/Core:103:
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/util/Macros.h:1051:3: error: use of undeclared identifier 'assert'
  eigen_assert(first && message);
  ^
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/util/Macros.h:615:25: note: expanded from macro 'eigen_assert'
#define eigen_assert(x) eigen_plain_assert(x)
                        ^
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/util/Macros.h:585:35: note: expanded from macro 'eigen_plain_assert'
    #define eigen_plain_assert(x) assert(x)
                                  ^

Since quite a lot of months, if you remember

Yes this is a known issue in our version of Eigen. It will be fixed once we merge with upstream.
In the mean time the fix is to manually include  either in Eigen/src/Core/util/Macros.h or in TF before including Eigen.

feels like spending the day bisecting to 2bfcec29d449f7a0b2322d2b9ddda8c114a28f43 was useless

Haha sorry and thanks for trying to find more information. Closing now.


Add IPv6 to GeoIP2 Enterprise test data

Closing this and creating a new one.

Created https://github.com/maxmind/MaxMind-DB/pull/104


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67116

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/85112


Fix duplicated help tag suda

This PR fixes the following error.
E154: Duplicate tag "suda"

📝 reproduce script
helptags /path/to/suda.vim

Fix: https://github.com/lambdalisue/suda.vim/issues/72

Summary by CodeRabbit

Documentation

Updated the documentation to enhance clarity around the usage of suda in sudo authentication contexts, including a formatting change for better consistency.

Thanks a lot


Update WDLs to adhere with  implicit coercions requirement

This PR updates WDLs to adhere to the requirements of concatenating optional and required variables. For instance,

Instead of:
String? firstname
String name = firstname + " lastname"

Use:
String? firstname
String name = select_first([firstname]) + " lastname"

This assertion was enforced in the recent miniwdl release. This PR updates the WDLs to adhere to the implicit coercion requirement. Specifically resolving miniwdl validation errors such as the following.
# from WDL, where `disk_gb` is optional:
disks: "local-disk " + runtime_attr.disk_gb + " HDD"

# error:
Validation Error: 'Cannot add/concatenate String and Int?'

Thanks, @mwalker174!


Come up with new titles and descriptions for all items

Items now are grouped into "families" by the same effect they provide to the carrier. The idea is to remake titles and descriptions for items which now have inconsistent icon. Icons were AI-generated so 90% of them don't much the description. Families of items should have somehow related icons and titles. You can find families and items properties here: https://github.com/Praytic/youtd2/tree/main/Data. To get item icons please ask @Praytic to get access to the source file.

Started working on this in this google sheet:
https://docs.google.com/spreadsheets/d/1GzsSddZCpvstKTwQKm7hLkG3Sp_-FaKfIeu030uXVos/edit?usp=sharing


[API] Configure role claim

Hi,
While implementing I noticed that TokenValidationClaimRole is only available in the Admin-UI Project.
The API authorization looks like this where JwtClaimTypes.Role defaults to "role". In many cases, however, the actual role claim may be different..? (at least in my case..)
Would be great if it was possible to also have something like TokenValidationClaimRole together with the already existing AdministrationRole in the API's appsettings.json to be able to configure admin-rights even better.. :)

Hey, do you mean this one? -
https://github.com/skoruba/IdentityServer4.Admin/blob/master/src/Skoruba.IdentityServer4.Admin.Api/appsettings.json#L16

Exactly, but that only let’s you define the role-value.. the name (or key) of the role claim is JwtClaimTypes.Role which is the constant string "role".
Then again if #478 is the current idea, you would probably just have one setting file where you can specify both the role-claim and the actual role-value.. just as in the Admin project. ^^


AttributeError at /invoice/ - 'NoneType' object has no attribute 'encode'

Hi,
I am trying to render the example template (invoice page) and receive the following error:
http://dpaste.com/1782321/
My template:
base.html - http://dpaste.com/1782328/
invoice.html - http://dpaste.com/1782324/
views.py - http://dpaste.com/1782332/
urls.py - http://dpaste.com/1782334/

Hello, I am having an issue with getting images on the pdf. When I put an image tag with src pointing to my image, I am getting the same error.
settings.py:
STATIC_URL = '/static/'
STATIC_ROOT = os.path.join(BASE_DIR,'..', 'static')
STATICFILES_DIRS = (
    os.path.join(BASE_DIR, 'assets'), # We do this so that django's collectstatic copies or our bundles to the STATIC_ROOT or syncs them to whatever storage we use.
)

My settings.py is here:
RootFolder/app/mainapp/settings.py
And my image file is here:
RootFolder/mainapp/assets/images/img1.png
In my html template I have put the img tag like this:

I have also tried using {% load staticfiles %} and changed the img tag as
. But it doesn't work either.
When I check the sources tab, localhost doesn't show a static folder either. This is happening only in this page. Other than this page, I get the static folder in all the other pages.
@nigma Can you please look into it and help me

Okay, I found a fix but its not what I desire.
I had to make a static folder in the RootFolder and pu the image inside that folder. But it would be really convenient if this problem could be solved. Is there a way to avoid what I have done?


1.3.0 release is breaking js_image_layer

https://github.com/bazel-contrib/rules_oci/pull/313 removes support for .tar.gz file extensions, but rules_js produces them
https://github.com/aspect-build/rules_js/blob/main/js/private/js_image_layer.bzl#L230
#313 says

Non-tar files never actually worked here

But this test has been passing https://github.com/aspect-build/rules_js/blob/main/e2e/js_image_oci/src/test.yaml#L6 so I think that may be incorrect, and we should just revert #313.
FYI @mattyclarkson as this originated from #302

My issue was with .tar.xz, so it's likely it recognises .tar.gz as that's what it compresses the layers to anyway.


Fixing various compilation warnings

Updates rapidjson and doctest, so far.
Should hopefully fix many of the warnings as errors with newer compilers.

Note that I'll be pushing ahead with the next release even though not all of the tests are passing - these will be addressed as soon as possible.


ENH: Move towards sqlalchemy ORM

Adds SQLAlchemy as an ORM layer on top of asyncpg, which is still used as the driver behind the queries.
Adds new environmental variable MIGAS_DEBUG which, when enabled, displays SQL queries to the console.
Adds support for unique usage querying. When rewriting/porting queries it was trivial so included it in with the new changes.

This PR also includes some breaking changes:

Removes MIGAS_DATABASE_URI environment variable in favor of DATABASE_URL. This is simpler and more commonly used anyways.
geolocs table - removes location column in favor of latitude and longitude columns.
Renames a few functions on the database module.

TODO

[x] add alembic to simplify migrations

This PR has gotten fairly big and hard to review - I'm going to merge this so it gets pushed into the staging server for further testing


Automatic Iteration of Paged Search Results

Hey Jim,
I'd like to propose building in some facilities for automatic iteration of paged results in order to operate on a complete set of results when the responses are paged. The impetus for this is once again the search endpoint. I'd love to be able to get all of the results for a given database and for many databases which have thousands of datasets the limitation of 100 results at a time results in tons of paging needing to be done.
I'd love to build in functionality to handle this transparently and automatically page through results in serial or parallel. I imagine this as an AutoPagingSearchResult class which is returned by an "autoPagingSearch" method on QuandlSession. It would take in an AutoPagingSearchRequest which is similar to SearchRequest but leaves out the page number field and instead has the user specify serial/parallel and, if necessary, number of threads for the parallel requests.
What do you think of this proposal?
Best,
Hamel

Hmmmm, I realize for my specific needs, the datasets_list endpoint which returns a zip of a csv is probably a better fit https://www.quandl.com/docs/api#dataset-list (shame on me for not digging into the docs more), still, this might be cool to add.

I've noticed odd behaviour when your have a large number of pages.  I used to use the empty query with a random page offset to pick test data for the unit tests, but that stopped working a few months back.  That's probably partly that querying a page in a result set tends to make the database need to realise all the rows before that page.  Agree it could be a nice thing to add - perhaps as an iterator?


Create SportsMentor.md

📝 Description
Access a vast array of sports training drills, exercises  designed to elevate your skills and enhance performance in sport asked by user.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
lol

Dear user,
Thanks for your contribution. Please add the URL of the AI Agent you created in your PR so that we can find it easily. You can  find the link on illa.ai. 2⃣ on the image will displayed after login and we will copy the url when click it.


Interchain KV Queries should be imported to https://github.com/cosmos/ibc-apps/blob/main/modules/

[ ] put the softwhere where it oughtta be
[ ] update the List of Apps / Ecosystem Apps tables in the README.

completed


Support start/end dates without times

It would be convenient if I could optionally provide dates without times for --start-date and --end-date. If no time is provided, T00:00:00Z/T23:59:59Z would be automatically added to the provided start and end dates. EDSC does this as well as the C2C CLI tooling. The C2C CLI code can probably be reused here

+1 from

Just to be clear:
start dates with no time will use start time at T00:00:00Z
end dates with no time will use end of day time T23:59:59Z


Maven publish webdav

Fixes #14750
This change uses the maven wagon webdav provider to do the work. There are many different ways that this could have been implemented, I went with extending the resources-http module. I'm happy to receive any feedback on the approach, taking into account the overall design direction (which I know little about).
I haven't included any unit tests, as most functionality is offloaded to the wagon provider. I have added an integration test, which sets up a WebDAV server and publishes to it. This seemed more appropriate than stubbing responses from a mocked-up server.
I added a paragraph in the documentation describing the change, There didn't seem to be anything relevant to add to the DSL Reference or Javadoc.
Context

It's been reported by others as far back as 2013. Currently we're using the legacy maven plugin publishing support to accomplish this, but we're getting deprecation warnings that this will be removed in Gradle 7.0

https://github.com/gradle/gradle/issues/14750
https://issues.gradle.org/browse/GRADLE-2919
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

It's been reported by others as far back as 2013. Currently we're using the legacy maven plugin publishing support to accomplish this, but we're getting deprecation warnings that this will be removed in Gradle 7.0

@gradle/core
If we're removing support for the old publishing mechanism, this does look like it's legitimately a gap we need to fill.

We really appreciate the amount of time and effort that's gone into this contribution. However, we're concerned that this change introduces an inordinate number of external dependencies instead of reducing them, especially maven jars.
Most of the new mechanism (if not all?) is already our own implementation IIRC. If we're going to re-introduce this feature, we'd probably want to do it ourselves without dragging these external components along.

Most of the new mechanism (if not all?) is already our own implementation IIRC. If we're going to re-introduce this feature, we'd probably want to do it ourselves without dragging these external components along.

@JLLeitschuh Thanks for your feedback. I don't disagree that it would be better implemented directly in Gradle instead of offloading to a 3rd party jar, however that was a daunting task for me. I understand your concern about the new dependencies. I meant to do an audit of which transitive dependencies I could exclude, but that slipped my mind at the end. I don't know how many of the maven dependencies I could exclude anyway...
Can you give me some advice on how to proceed with this? I can take another look from scratch, with a view to doing more of the implementation in Gradle itself, but this will take me some time, and it's unlikely I'll get anything useful done for a while (definitely not before next year with the other demands on my time right now). For now, we are getting by with the legacy maven plugin, but it's not nice, and I'd rather not be blocked from upgrading Gradle when support for that plugin is removed.

@bschelberg Thank you again for tackling this topic in this PR. And apologies for not getting back earlier again.
Unfortunately, this clashed with some other changes lined up for Gradle 7.0. In Gradle 7, all dependencies to Maven Wagons will be removed from the distribution. So this solution would add back even more dependencies to the distribution.
On the long run, it would be best if Gradle provided an API to add solutions like this via a plugin. While this is not planned right now, it might be something we do in the future.
I described it in more detail here: https://github.com/gradle/gradle/issues/14750#issuecomment-784358228
And I also describe how you can solve your use case with Gradle 7 through an additional task. I was only able to create this example by using what you did in this PR. So this was very helpful even if we have to reject the PR itself.
I hope you can use the proposed solution in your build. If not, please give further feedback on #14750.

Excellent, thanks. This is usable, and I can use the maven-publish plugin now.


feat: Centralize leaked ENI cleanup

Issue #, if available:
N/A
Description of changes:
Merge feature branch eni-cleanup into master for release.
Centralize leaked ENI cleanup in the controller to delete leaked ENIs provisioned by the controller and VPC-CNI:

Added finalizer in CNINode: when kubernetes deletes an object that has finalizers specified for it, the Kubernetes API marks the object for deletion by populating .metadata.deletionTimestamp, and returns a 202 status code (HTTP "Accepted"). The target object remains in a terminating state while the control plane, or other components, take the actions defined by the finalizers. After these actions are complete, the controller removes the relevant finalizers from the target object. When the metadata.finalizers field is empty, Kubernetes considers the deletion complete and deletes the object.
Add a new field in Spec to add Tag: This is currently used to specify tags that need to added to network interfaces provisioned by the controller and VPC-CNI. VPC-CNI will read the CNINode to get the tags.

The CNINode reconciler will add the finalizer and tag if missing on existing CNINode objects and handles the finalizer routine to clean up leaked resources.

Re-create CNINode if deleted by user: The controller will re-create CNINode if deleted by user when node object is still present.
Added metrics to count number of available ENIs found and number of leaked ENIs that failed to be deleted

Tests:
Webhook
Ran 11 of 11 Specs in 107.573 seconds
SUCCESS! -- 11 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 1m49.904100803s
Test Suite Passed

SGP
Ran 18 of 22 Specs in 1183.287 seconds
SUCCESS! -- 18 Passed | 0 Failed | 0 Pending | 4 Skipped
PASS

Ginkgo ran 1 suite in 19m46.06109991s
Test Suite Passed

CNINode
Ran 6 of 6 Specs in 491.560 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 8m14.030002297s
Test Suite Passed

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Merged #374 from dev branch.


Direct conversion between tendermint::Time and protobuf TimeStamp

This PR enables direct conversion between tendermint::Time and the protobuf TimeStamp type without having to go through std::time::SystemTime. This is needed so that we can remove the dependency to std for informalsystems/ibc-rs#1158.
I also make public the underlying chrono::DateTime field, as there is no reason to encapsulate tendermint::Time being a newtype wrapper to chrono::DateTime.

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Added entry in .changelog/

There seem to be a bunch of test failures here at the moment that seem directly related to the new time code.
There are also now errors in the light client integration test.


How to run the scripts in background without having to keep terminal open

I tried:
python /home/openhabian/zzzzz/fetcher.py &
But it didn't work. Even
python /home/openhabian/zzzzz/fetcher.py
says
SECRETS.txt: no such file or directory
I have to manually navigate to zzzzz folder using cd command and then run
python fetcher.py
in order to make it run
Same goes for other scripts. How to run them in background?

Because fetcher.py tries to open a file that should exist in the same directory where you are running the script.  Running python /home/openhabian/zzzzz/fetcher.py will open try to open /SECRETS.txt

There is no need to run with sudo. If you close the terminal, the script stops


Unceasing Flame - Plan and implement

-Place here implementation list-

Ok, beyond the basic:

Check of different cards for each pair each turn;
Reducing the cost of an attack by one for one turn;
Protection against infinite looping in case of a only Power left draw pile;
Linking the relic when it spawns;
Slow and fast play for deck drawing;


It is not possible to set a procedurally created mesh on a collision component

If you create a model procedurally and set it on a model component for rendering, it is not currently possible to also set it on a collision component to make the mesh into a static body. Not using the API anyway. A workaround is to call:
        context.systems.collision.addComponent(this.entity, {
            type: 'mesh'
        });
        this.entity.collision.model = model;
        context.systems.collision.implementations.mesh.doRecreatePhysicalShape(this.entity.collision);

Fixed in https://github.com/playcanvas/engine/commit/7121f902e44fcca4f05db5682e3a3284cb6da483


Readme build instructions use the incorrect directory

Describe the bug
The readme file's build instructions say
(Recommended) Remove the existing {{ cookiecutter.book_name }}/_build/ directory
Run jupyter-book build {{ cookiecutter.book_name }}/

however the directory is actually named {{cookiecutter.book_slug}}.
To Reproduce
Steps to reproduce the behavior:
Create a book where the book name and slug are different and follow the build instructions in the generated readme
Expected behavior
A clear and concise description of what you expected to happen.
Readme should read
(Recommended) Remove the existing {{ cookiecutter.book_slug }}/_build/ directory
Run jupyter-book build {{ cookiecutter.book_slug }}/

Environment

Python Version [e.g. 3.7.1]: 3.8.6
Package versions or output of jupyter-book --version:

Jupyter Book: 0.10.1
MyST-NB: 0.12.0
Sphinx Book Theme: 0.0.41
MyST-Parser: 0.13.5
Jupyter-Cache: 0.4.2
NbClient: 0.5.2

Operating System: WSL

Additional context
Add any other context about the problem here.

Thanks for this @ScottWales - I'll make a PR later tonight to fix this one up. Appreciate it!


Add section on linters & auto-formatters.

Draft text for introducing students to linters & auto-formatters.
Fixes #18.

👍 Thanks for taking a look, I've removed the section on autoformatters.

These changes look good to me.

Quick question: is there a reason to prefer one of these linters over the others or to use more than one?  We currently use pylint in 141.

They do check different things & give somewhat different results, I've seen a handful of projects that make use of both.
I think the quick version is that pylint is a bit more comprehensive out of the gate but flake8 seems more configurable & also has a lot of popular plugins that can extend its linting capabilities to cover other patterns people want to check for (https://github.com/DmytroLitvinov/awesome-flake8-extensions) such as leaving debugging statements in code or validating docstrings.


Unable to run on digitalocean function

Hi @H4ad ,
I was trying https://github.com/H4ad/serverless-adapter-examples/tree/master/examples/trpc-digital-ocean to deploy to digital ocean functions I added npm package instead of file link in package.json "@h4ad/node-modules-packer": "^1.1.0",
I was able to deploy correctly but when I click run on DO functions I am getting error
2022-09-11T13:27:48.168357007Z stdout: Error: Cannot find module '@h4ad/serverless-adapter'
2022-09-11T13:27:48.168412462Z stdout: Require stack:
2022-09-11T13:27:48.168415989Z stdout: - /tmp/ZWzb5Bqh/dist/index.js
2022-09-11T13:27:48.168418343Z stdout:     at Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
2022-09-11T13:27:48.168422641Z stdout:     at Module._load (node:internal/modules/cjs/loader:804:27)
2022-09-11T13:27:48.168425056Z stdout:     at Module.require (node:internal/modules/cjs/loader:1022:19)
2022-09-11T13:27:48.16842743Z  stdout:     at require (node:internal/modules/cjs/helpers:102:18)
2022-09-11T13:27:48.168429805Z stdout:     at Object.<anonymous> (/tmp/ZWzb5Bqh/dist/index.js:4:30)
2022-09-11T13:27:48.168433032Z stdout:     at Module._compile (node:internal/modules/cjs/loader:1120:14)
2022-09-11T13:27:48.168435366Z stdout:     at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
2022-09-11T13:27:48.16843776Z  stdout:     at Module.load (node:internal/modules/cjs/loader:998:32)
2022-09-11T13:27:48.168440095Z stdout:     at Module._load (node:internal/modules/cjs/loader:839:12)
2022-09-11T13:27:48.168442389Z stdout:     at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:170:29) {
2022-09-11T13:27:48.168444864Z stdout:   code: 'MODULE_NOT_FOUND',
2022-09-11T13:27:48.168447138Z stdout:   requireStack: [ '/tmp/ZWzb5Bqh/dist/index.js' ]
2022-09-11T13:27:48.168449402Z stdout: }
2022-09-11T13:27:48.171598Z    stderr: The action did not initialize or run as expecte

Hey @jmd9019, thanks for using serverless-adapter.
Some questions:

Did you use NPM?
Are you deploying inside Windows or Linux?

Yes I am using NPM and i am using VS Code as IDE and my PC is windows. Also I am trying to deploy on DO functions

And to be clear, as of now I am just deploying to DO's function and try to send get GET request to URL provided by DO's function

Maybe the problem is with Windows, @h4ad/node-modules-packer may not be able to bundle the @h4ad/serverless-adapter library.
To test, zip the dist folder and the node_modules folder into a file called deploy.zip, then move this zip folder to packages/api/prod and replace the zip that was there.
Then run npm run update-function to update your code inside the DO.

Also, inside package.json, did you change the @h4ad/serverless-adapter for @h4ad/node-modules-packer or is just a typo issue in your description here "I added npm package instead of file link in package.json "@h4ad/node-modules-packer": "^1.1.0",".
If you changed, this could be the issue too, inside package.json, in production dependencies, you must have @h4ad/serverless-adapter version 2.10.0 at least.

I think its correctly creating deploy.zip I looked into zip file It had 2 file node_modules and dist which has the code

Here's the dependencies inside package.json
  "dependencies": {
    "@h4ad/node-modules-packer": "^1.1.0",
    "@h4ad/serverless-adapter": "^2.10.0",
    "@trpc/server": "9.27.0",
    "zod": "^3.18.0"
  },

I think its correctly creating deploy.zip I looked into zip file It had 2 file node_modules and dist which has the code

Look inside node_modules, there is a @h4ad folder and inside it is serverless-adapter.

Ok inside deploy.zip in node_modules there is no folder @h4ad but in my PC's node_modules there is @h4ad folder

I will try this https://github.com/H4ad/serverless-adapter-examples/issues/2#issuecomment-1242976900 and see if I can make some progress

Hi @H4ad ,
I did it manually now creating deploy.zip and used npm run update-function. Still there is error
I am sending GET request to '/getUser'
export const appRouter = trpc
  .router<TrpcContext>()
  .transformer(new BufferToJSObjectTransformer())
  .query('getUser', {
    async resolve() {
      return { name: 'Bilbo' };
    },
  })

Getting error as
"2022-09-11T15:16:26.332147Z    stderr: The action did not initialize or run as expected. Log data might be missing."

When you call the API inside DO, you should add the prefix of your folders inside package, so instead /getUser, you call /api/prod/getUser.

This the url : https://faas-blr1-8177d592.doserverless.co/api/v1/web/fn-c2f6a867-3589-4d9d-be04-a587c0224939/api/prod/getUser

Let's just summarize:

You created a deploy.zip with the dist and node_modules folders.
Replaced deploy.zip inside packages/api/prod with the zip file you created.
So you ran npm run update-function.

About the code, did you change anything? Because these errors sound like something related to the tRPC code.
What about project.yml, did you change anything in the example?
Are you receiving any logs inside DO?

Yes did follow all 3 points
About code nothing is changed also nothing is changed on project.yml
packages:
  - name: api
    functions:
      - name: 'prod'
        main: 'dist/index.main'
        runtime: 'nodejs:18'
        web: 'raw'

Strange, very strange, everything seems fine.
Try using this zip folder to deploy, I created it using linux and running @h4ad/node-modules-packer:
deploy.zip
If it works, try to see if there are any differences between the files inside dist or see if any dependencies are missing inside node_modules.

Yes, your deploy.zip is working but I don't see any packages missing in my
deploy (2).zip
But has some extra packages

Try removing typescript, esbuild-windows-64 and yarn from your node_modules inside your deploy.zip and then deploy again.
Also, do you have WSL? If so, try deploying inside WSL, I think it's a bug in node-modules-packer on Windows and some issue with the size of the zip.

Try removing typescript, esbuild-windows-64 and yarn from your node_modules inside your deploy.zip and then deploy again.
I removed these files and redeployed now its working

I don't have WSL as my PC SSD is running out of space

I will try to fix the issue of packing inside Windows in node-modules-packer, but until then, you will need to pack your files manually and remove typescript and esbuild-windows-64.
The issue with the size is probably issue on DO but this thing we can't control.

Sure, I will remove it manually as of now, also can this be also fixed https://github.com/H4ad/serverless-adapter-examples/issues/2#issuecomment-1242977984
node-modules-packer was missing out modules which had folder names starting with @ on my PC

Hey @jmd9019, I release a new version of @h4ad/node-modules-packer, try running again with it to see if now works.

Hi @H4ad,
I tried "@h4ad/node-modules-packer": "^1.2.1" on windows now it's deploying correctly.
Thanks for the help.

Nice man, thanks for using it and reporting this bug.


Changed test set-up to test anti-case of if statement for removeAutho…

…rizedAddress.

Pull Request Test Coverage Report for Build 223

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 92.523%

Totals

Change from base Build 220:
0.9%

Covered Lines:
65

Relevant Lines:
71

💛  - Coveralls


Add decorators to test task?

I have installed and made it work the babel-plugin-transform-decorators-legacy.
To do so, I added:
  babelQuery: {
    plugins: [
      'transform-decorators-legacy',
    ],
  },

to my webpack.base.babel.js file.
I've also added the same plugin in the babel.env.production.plugins section of package.json.
Also, I have added the plugin in the webpack.test.babel.js
They work fine in dev and production builds, but seems to not get loaded when i run npm run test.
Should I include the plugin somewhere else?
More generically, may you provide an example to make it clear how to add an additional babel plugin to the tests configuration?

I think I'm near the solution... https://github.com/deepsweet/isparta-loader/issues/18
any help is welcome

I ended up using https://github.com/jas-chen/karma-sourcemap-writer to generate coverage reports with istanbul.
It seems to work better and doesn't give me all these problems.
Maybe you could consider using it instead of the current (not supported) isparta

Yeah that looks solid! See #274, would definitely appreciate a PR!
I'll close this since it seems resolved :grin:

@FezVrasta I cannot make it work in dev or in production even with you instructions...
I'm still having a Unexpected character '@' . Any other clues ?


Feature/185

PR for Content Fragment Renderer and Variation Component

@davidjgonzalez - This PR is for https://github.com/Adobe-Marketing-Cloud/asset-share-commons/issues/185. Kindly review.


Prisma-like JSON Query Constructor

Any plans to make a Prisma-like JSON query constructor? The idea is to make conditional queries easier, for example:
import { NextApiRequest, NextApiResponse } from "next";
import { pscale } from @planetscale/database

export default async function handler(
  req: NextApiRequest,
  res: NextApiResponse
) {
    const { param1, param2, param3 } = req.query as {
      param1?: string;
      param2?: string;
      param3?: string;
    };
    const response = await pscale.table.findMany({
        where: {
            ...(param1 && {
                  attr1: param1
             }),
            ...(param2 && {
                  attr2: param2
             }),
            ...(param3 && {
                  attr3: param3
             }),
        }
    })
    res.status(200).json(response);
}

@theobr might be doing this already with https://github.com/TheoBr/pscalebench/blob/main/src/pages/index.astro 👀

Ideally this would become a connector for Prisma


Support Co-Authored-By

Github introduced a convention where the commit message contains a list of co-authors, for use when pairing.
Example:
commit 032db38255275dd7372f575e3d06947c878ef4c6
Author: Tommy Brunn<EMAIL_ADDRESS>Date:   Thu May 17 10:21:16 2018 +0200

    Encode int64

    Co-Authored-By: Tulio Ornelas<EMAIL_ADDRESS>
Both Github and Atom then displays both authors whenever they are showing author information. See http://blog.atom.io/2018/04/18/atom-1-26.html#github-package-improvements-1 for an example of what it looks like in Atom.

While I could provide a command or menu that (in theory) could add the co-author into the Source Control input, I couldn't make it nice and integrated like Atom. For that to happy vscode would need to add this feature into the Git extension itself. I will think about it some more, but I would recommend you request this feature on the vscode repo as well.

Ah, thanks. I wasn't sure if this was provided by vscode's Git extension or you. I'll open an issue there instead.

Opened Microsoft/vscode/issues/50090


As a developer, I need to fix problems in the display of Creators in the DANS Oral history collection

Where: Search tool
How to reproduce:

Open the Search tool
Select the DANS OH collection
Search for "amersfoort"
Observe the Creators facet:

The problem:
-Some creators start with a comma and a parenthesis
Acceptance criteria:
@jwassenaarbg Could you please take a look and define what has to be done? Thanks

Issue moved to beeldengeluid/labs-importer #16 via ZenHub


[chefdk] Bump chefspec version to 4.3.0.

This release contains sethvargo/chefspec#607 which makes the coverage
report on Windows workstations delightful and viable.

:+1:


Replace generate.ps1 with pointer to fixed swagger files

autorest fixed a bug that required Search to have a generate.ps1 script to merge swaggers. We no longer need the script.
At the same time, once guidance is given we should point to a specific commit to download swagger files.

I can take this one. We have a few changes coming up next week that shouldn't change the public API, and I don't think we even need generate.ps1 anymore anyway. Key Vault recently was able to reference multiple swaggers within a single autorest.md file.


Change reporter to not wipe out the existing body content

Hi.
I've just started using this after reading about Jest. It works really well and I do like the diffs it produces.
I just find it annoying that it replaces the whole body tag with it's report, as it removes the content from the htmlReporter. I've hacked it around for the moment to prepend the content to the top for now.
In jasmineDone I replaced
document.body.innerHTML = html_summary;
with
document.body.innerHTML = html_summary + document.body.innerHTML;
That's a nice quick workaround, but I was wondering if it's possible to add the diff and new snapshot to the result object instead? This would mean that the results are usable in any reporter.
Thanks

Seems worth doing.
I'm super busy with 2 full-time jobs right now, but I'll see if I can get to it.


FIX: Wrong node address is loaded from Bond tab

Wrong node address is loaded from the bond screen.
if you have more than one node in the BOND tab, if you select any node and attempt to send a management tx (bond, unbond, etc.) AsgardEx loads the address for the first node in the list and not the one you select.

closing issue


[elixir-omg] Add Sentry support for omg_api

As title

Tested locally that the childchain starts up without the Sentry DSN ENV populated. Good to merge.


Prototype frame combiner using ffmpeg

requires ffmpeg
added some sample pngs for testing

I am with Luis on the run command thing. We could use some library to interact with ffmpeg instead. This seems to be the most maintained I could find with a quick search (I think, Java libs can simply be included in Kotlin, right?).

We could also look into this lib as it is also available for android