cellTemplate is not working

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

I'm doing everything in this plunkr but to no avail: https://embed.plnkr.co/FxZo4SxKLbCPxmNTveXr/
Expected behavior

The cellTemplate column option would actually allow me to author my own template and use it.
Reproduction of the problem

What is the motivation / use case for changing the behavior?

I need to dynamically create hyperlinks in my table
Please tell us about your environment:

Table version: 10.3.0

Angular version: 4.2.0

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

I am using chrome

Language: [all | TypeScript X.X | ES6/7 | ES5]

Typescript / Html

(SystemJS) Error: XHR error loading https://unpkg.com/rxjs/operators/refCount.js at ZoneDelegate.prototype.invokeTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:423:13) at Zone.prototype.runTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:192:21) at ZoneTask.invokeTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:499:17) at invokeTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:1540:9) at globalZoneAwareCallback (https://unpkg.com/zone.js@0.8.18/dist/zone.js:1566:17) Error loading https://unpkg.com/rxjs/operators/refCount.js as "./refCount" from https://unpkg.com/rxjs/operators/share.js", message: "(SystemJS) Error: XHR error loading https://unpkg.com/rxjs/operators/refCount.js at ZoneDelegate.prototype.invokeTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:423:13) at Zone.prototype.runTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:192:21) at ZoneTask.invokeTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:499:17) at invokeTask (https://unpkg.com/zone.js@0.8.18/dist/zone.js:1540:9) at globalZoneAwareCallback (https://unpkg.com/zone.js@0.8.18/dist/zone.js:1566:17) Error loading https://unpkg.com/rxjs/operators/refCount.js as "./refCount" from https://unpkg.com/rxjs/operators/share.js

@bberkobien check the dev tools console log for errors. It looks like you are having an issue with rxjs loading from unpkg.com and has nothing to do with this project. Try reproducing your problem using a proper plunker setup such as the one that comes with the issue tracker template http://plnkr.co/edit/vtAo2zzWFn8kFOGRH88r

Here is a link to the plunkr that I have made: https://plnkr.co/edit/ijDOrfN61SOvzBLLnUfc?p=preview .
If I remove [count]="page.totalElements" [externalPaging]="true" from the ngx-datatable that the values will show for the template. I'm not sure why this is true.

@bberkobien sorry, my mistake, my uBlock origin plugin was blocking your plunker example for some reason. I can take a look at it now.

You're fine, I'm just confused as to why this isn't working. I'm leaning toward something to do with the paging. I'm not sure. Thanks for the help.

@bberkobien still a good idea to take a look at your dev tool console log. I'm getting this error now:

Cannot read property 'totalElements' of undefined
at Object.eval [as updateDirectives] (App.ngfactory.js:64)
at Object.debugUpdateDirectives [as updateDirectives] (core.umd.js:13099)
at checkAndUpdateView (core.umd.js:12283)
at callViewAction (core.umd.js:12631)
at execComponentViewsAction (core.umd.js:12563)
at checkAndUpdateView (core.umd.js:12289)
at callWithDebugContext (core.umd.js:13499)
at Object.debugCheckAndUpdateView [as checkAndUpdateView] (core.umd.js:13039)
at ViewRef_.detectChanges (core.umd.js:10206)
at eval (core.umd.js:4844)

Try defining page along with it's totalElements property first.

[count]="page.totalElements"

I meant to remove that before you saw it. Try it now (or just remove that
[count]="page.totalElements")
On Fri, Oct 20, 2017 at 2:04 PM, Thomas J. Crowe<EMAIL_ADDRESS>wrote:

@bberkobien https://github.com/bberkobien still a good idea to take a
look at your dev tool console log. I'm getting this error now:
Cannot read property 'totalElements' of undefined
at Object.eval [as updateDirectives] (App.ngfactory.js:64)
at Object.debugUpdateDirectives [as updateDirectives] (core.umd.js:13099)
at checkAndUpdateView (core.umd.js:12283)
at callViewAction (core.umd.js:12631)
at execComponentViewsAction (core.umd.js:12563)
at checkAndUpdateView (core.umd.js:12289)
at callWithDebugContext (core.umd.js:13499)
at Object.debugCheckAndUpdateView [as checkAndUpdateView]
(core.umd.js:13039)
at ViewRef_.detectChanges (core.umd.js:10206)
at eval (core.umd.js:4844)
Try defining page along with it's totalElements property first.
[count]="page.totalElements"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/swimlane/ngx-datatable/issues/1066#issuecomment-338280965,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV_hpRJ9M9pvZs1oS9n8PQqs_nkAXok7ks5suOCsgaJpZM4QAoY_
.

--
Bradley Berkobien
Web Application Developer

The only thing different is the fact that in the plunkr I defined the rows explcitly, whereas in my application i do a call to the backend for paging and it returns the result of 100 rows and sets that equal to rows.

@bberkobien You can't remove count as it's required for externalPaging. It's an all or nothing type deal.

Okay fair enough. I made another plunkr to help you better understand my issue. The template does not work here. http://plnkr.co/edit/ISu5bSHMMP0Igp9bqZfL?p=info

@bberkobien when you use @ViewChild, make sure you initialize anything that depends on it on or after the ngOnInit lifecycle callback. In your case, initialize columns in the ngOnInit lifecycle.
columns = [];

ngOnInit() {
  columns = [
    {name:"Name", cellTemplate: this.template},
    {name:"Gender"},
    {name:"Company"}
  ];
}

I have updated the plunkr and you are correct, however this still doesn't work on my personal application. Trying to figure out what I'm missing here.....

It has nothing to do with paging or setting the rows. Might be the version # of one of my packages?

@bberkobien without seeing your source code, I don't really have any idea. I haven't seen anything related to this on my end.

Thanks for your help. I will update this if/when I find a solution.

So what seems to be the issue is that the data-table and template cannot be placed within an *ngIf tag. Here is a plunkr to demonstrate the bug. https://plnkr.co/edit/UpI3v68k6zF0m3TFtCjT?p=preview . Remove the *ngIf and it will work fine.

The solution to this is removing the template itself from the *ngIf.

@bberkobien you can fix that by changing the lifecycle of the initialization from ngOnInit to ngAfterViewInit. I think it has something to do with when the @ViewChild is populated, which should always be after the view is initialized. I guess it's probably a bug that you can even access it on the ngOnInit lifecycle.

@bberkobien I filed a bug report with the angular team. IMO I think ngOnInit should never provide results for any @View... or @Content... query selector in any circumstance as it leads to inconsistent behavior.

Thank you for following up and filing that report. I do agree with your last statement and will be interested in seeing what the Angular team replies with. Thanks for your help as this problem had me confused for a couple of days.

@bberkobien I did get some feedback about some more advanced angular feature that I wasn't aware of. @ViewChild can either be a static or dynamic query. A static query is never updated and is initialized upon creation, thus causing the usability issue. So technically the behavior is correct and by design but I wouldn't say straightforward. The fact that the template reference is inside an *ngIf template makes it a dynamic query thus changing when the initialization occurs.
You can follow the reference here and add any comments.


backlog retention policy doesn't work without subscriptions

Describe the bug
When persistent topic never had subscriptions the published messages will deleted after few minutes with no reason
To Reproduce
Steps to reproduce the behavior:

publish to a new topic "persistent://public/default/my-topic" the message "test"
create reader from "persistent://public/default/my-topic"
get the message "test"
wait about 1 min
create reader from "persistent://public/default/my-topic"
topic is empty

Expected behavior
persistent topic should store messages in backlog by backlog retention policy
In my case is
bin/pulsar-admin namespaces get-backlog-quotas public/default

{
  "destination_storage" : {
    "limit" :<PHONE_NUMBER>0,
    "policy" : "producer_request_hold"
  }
}

Desktop (please complete the following information):

OS: Official docker from apachepulsar/pulsar:2.4.0

Backlog retention policy can affect the subscriber's backlog data retention. If you want to save data  whether or not you have a subscription, you can use:
bin/pulsar-admin namespace set-retention

Hope can help you.

@codelipenghui  Yes, I did. It doesn't work.
bin/pulsar-admin namespaces get-retention public/default

{
  "retentionTimeInMinutes" : 0,
  "retentionSizeInMB" : 0
}

@codelipenghui thanks!


[test] Need performance test

@abdelaziz-mahdy Ran a comprehensive benchmark of the framework not to long ago available in the discussions here: https://github.com/serverpod/serverpod/discussions/1791


Run arethetypeswrong from in-memory tarball data

This should be a performance win, but is also preparation for fixing https://github.com/DefinitelyTyped/DefinitelyTyped/issues/67361 and bringing dts-critic suggestions back.

Needs a changeset, but, after that I'm excited for in-memory. Would love to eliminate all of our other calls out to npm for info too.


JobLog ID CTGGT0012/13/56/55 not saved in influx

Copied from internal git.
Currently it is not possible to parse filepaths within joblogs.
Due the escaping any  \ within the message breaks the current parse-regex.
Those ID's are currently not parsed, though those errors should be resolved to avoid a high error-count & allow a parsing on later stages.

Applied within Merge Request #70 - reducing the ammount of failing lines by a lot.
This changes the issue from having a bad escaping to an unknown issue:
The escaping is fine, the queries may be send like this via CLI, but the real issue is that the InsertQuery following the ID 0055 is directly appended to the previous query.
This double-query causes the statement to fail.
Adding spaces before/after did not work. The influx-client-package simply adds a \n between each query - I do not see why it is failing.
Since we are deciding whether we want to reduce the amount of logs saved, this issue could be ignored.

This is most probably an Issue of the InfluxDB-Client: https://github.com/influxdata/influxdb-python
This repository did not recive an update in a long time, nor any support on the open issues.
I'm closing this issue since will most likley not affect any messageID's of interest and will be solved once we filter only by message ID's.
The only way it could affect important ID's is by ruining the message right after it (missing \n), but that is quite unlikley.
This might be solved by Influx2.0. Before that, however, we have to address several other issues


Unexpected keyword argument with python property

Describe the bug

When use @property and pass value in __init__, mypy show error: Unexpedted keyword argument "<property>" for "<entity>"
To Reproduce
from hashlib import md5

import sqlalchemy as sa
from sqlalchemy import orm

Base = orm.declarative_base()

class User(Base):
    __tablename__ = 'user'

    id = sa.Column(sa.Integer, primary_key=True)
    nickname = sa.Column(sa.Unicode(20), nullable=False)
    pwd_hash = sa.Column(sa.Unicode(200))

    @property
    def password(self):
        raise AttributeError('Cannot read password.')

    @password.setter
    def password(self, value: str):
        self.pwd_hash = md5(value.encode('utf-8')).hexdigest()

if __name__ == '__main__':
    user = User(nickname='kenny', password='Aa1234')  # <-- mypy: Unexpected keyword argument "password" for "User"

Error
app\__init__.py:25: error: Unexpected keyword argument "password" for "User"

Versions.

OS: Windows 10 / Debian 10
Python: 3.9.1
SQLAlchemy: 1.4.15
mypy: 0.812
SQLAlchemy2-stubs: 0.0.2a1

Have a nice day!

Yes, my **kw was regarding the inferred constructor generated by the sqlalchemy mypy plugin.
You can workaround for now by defining a constructor, maybe this will work just for type checking?
class User(Base):
    if TYPE_CHECKING:
        def __init__(self, id: Optiona[int]=None, nickname: Optional[str]=None,
                           pwd_hash: Optional[str]= None, password:Optional[str]=None): ...
    # same as is now


3.1 Custom validators

All default data types should be supported. Default data types are:

strings
numbers
dates

Will use the same API as the "Ability to make some fields mandatory" to flag invalid cells.
Demo example should be provided

Moved to milestone 5 to allow some improvements


Default structs to define

In addition to the interface, this package should probably contain basic implementations for the most common types of graphs.
Here's a possible list:

Name
Vertices
Metadata

(Simple)(Di)Graph
1:n
none

(Simple)Weighted(Di)Graph
1:n
edge weights

(Simple)Meta(Di)Graph
1:n
vertex and edge

(Simple)VertexSafe(Di)Graph
non-contiguous integers
none

For each one, we will provide both the simple version (no multi-edges, possible self-loops) and the generic version.

I would really suggest to try our best to make MetaGraphs.jl obselete. So this would mean that the implementation of a MetaGraph should be type-stable for performance but also fallback to a generic struct using Any types for flexibility.

I'm not sure yet how it will look like, but I don't think a fallback is a great idea. I think if users want metadata of type Any, they have to say it explicitly. Strictly typed metadata is also a safeguard against bad code


Complete testing

verify complete testing of the code

Almost completely tested:

pfaffian.jl
cholesky.jl
exp.jl
jmatrix.jl
hessenberg.jl
skewhermitian.jl
eigen.jl and tridiag. jl: need to test the specialized versions of eigvals


adding new pass metadata for generating design metadata

NOTE: This has been moved to #3158 due to branch rename
As part of some work on SBY this pass is to extract design metadata for ingestion into other tools.
It is not a full netlist output, and as we did not want to consume the final design netlist JSON this pass was added.
NOTE: This pass is still a big WIP
The rough outline of the JSON object the pass will generate is as follows:
{
  "version": "0.0.0",

  // e.g. if “formal” is here, then the dump contains assertions, assumptions, etc
  "features": ["formal", "connections"],   // optional if complete dump

  "modules": [
    {
      "name": <module_name>,
      "cell_sorts": [
        [
          {
            "type": <cell_type_or_module_name>,
            "ports": [
              {
                "name": <port_name>,
                "direction": <port_direction>,
                "range": [<msb>, <lsb>]  // (optional, default is [0,0])
              },
            ],
            "cells": [
              {
                "name": <cell_name>, // (optional)
                "attributes": {
                  <attr_name>: <val>,
                },
                "parameters": { // (optional, must not overwrite entries from sort parameters)
                  <param_name>: <val>,
                },
              },
              // cell indices that are out of bounds refer to cells without name or attributes
            ],
            "parameters": { // (optional)
            	<param_name>: <val>,
            },
          },
        ],
      ],
      "connections": [
        {
          "ports": [
            {
              "cell": [<cell_sort_idx>, <cell_idx>],
              "port": <port_idx>,
              "range": [<msb>, <lsb>]   // (optional)
            },
          ],
          "labels": [
            {
              "name": <netname>,
              "range": [<msb>, <lsb>]   // (optional)
            },
          ],
        },
      ],
    },
  ],
}

It is not a full netlist output, and as we did not want to consume the final design netlist JSON this pass was added.

I think this does give you enough information to reconstruct a netlist in its complete form, though, unless I'm missing something (and the 'cell sort' approach may well end up more compact than the existing JSON output for many post-synthesis designs)

It is not a full netlist output, and as we did not want to consume the final design netlist JSON this pass was added.

I think this does give you enough information to reconstruct a netlist in its complete form, though, unless I'm missing something (and the 'cell sort' approach may well end up more compact than the existing JSON output for many post-synthesis designs)

I'm not sure there will be enough information in the end to reconstruct the whole netlist for every design with this output or not to be honest, but seeing as it's still very much in flux that could change, seeing as currently only the information needed for the upcoming sby changes are being exported.
Im not super clear if this would end up replacing the current JSON output or not either, as having two JSON netlist export passes seems silly, but seeing as this is still a WIP draft that can be worked out in due time i think.

What specific issues with write_json does this actually solve?

NOTE: This has been moved to #3158 due to branch rename


[Bug]: Error creating and inserting to collections using Persistent Client

What happened?
The code below works perfectly when I use the non persistent client.
positive = ["yes", "sure", "ok", "okay", "yeah", "yup", "yep", "yea", "yah", "yas", "ya", "yap"]
negative = ["no", "nope", "nah", "nay", "nope", "nah", "nay"]

positiveStr = " ".join(positive)
negativeStr = " ".join(negative)
#client = Client()
client = PersistentClient()

booleanCollection =client.get_or_create_collection(name="booleanDiscriminationMemory",
                                                 embedding_function=NexusEmbeddingFunction(),
                                                 metadata={"hnsw:space": "l2"})
booleanCollection.add(documents=[negativeStr, positiveStr], ids=["0", "1"])

print(booleanCollection.count())
query = booleanCollection.query(query_texts=["Excellent, continue!"], n_results=1, where=[], include=[])
id = query["ids"][0][0]
print(query)

When I use the persistent client it gives the following error upon adding the reccords:
Exception occurred invoking consumer for subscription 7c0db0e298924b649c9f33477d48b7ddto topic persistent://default/default/f18fdbe1-e802-4b03-96f3-abb7a8d78b97 init_index(): incompatible function arguments. The following argument types are supported:
    1. (self: hnswlib.Index, max_elements: int, M: int = 16, ef_construction: int = 200, random_seed: int = 100, allow_replace_deleted: bool = False) -> None

Invoked with: <hnswlib.Index(space='l2', dim=768)>; kwargs: max_elements=1000, ef_construction=100, M=16, is_persistent_index=True, persistence_location='./chroma\\79f314c4-a58c-4fec-b0b5-9159b4e3e1c5'

and when I query the collection it gives this message:
Number of requested results 1 is greater than number of elements in index 0, updating n_results = 0
I'm using chroma 4.22 and python 3.9
Underlining the fact that the same code executes as expected when using Client() instead of PersistentClient()
Versions
I'm using chroma 4.22 and python 3.9.6 on windows 10
Relevant log output
No response

It looks like the index fails at creation because a bad argument is passed to index creation - I was not able to reproduce
locally, but this is very strange. Do you happen to have HNSW installed separately?
@tazarov could you see if you can repro this?

hnswlib version 0.8.0. Tried to update to see if the error went away. It did not. Gonna switch back to the original version now

Chroma uses our own fork of HNSW under the hood: https://github.com/chroma-core/hnswlib


Add National Ilan University

Add National Ilan University
website: https://niu-en.niu.edu.tw/

@kflejohn I am sorry, the domain ems.niu.edu.tw is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Templating temperature

I am not very familiar with the codes, but I would like to display the optimal room temperature based on a temperature sensor, I used this formula, it works with all operands +, *, / but if I use the - what I need does not work , can someone help me?
      [[[         return 'Optimal Room Temperature: ' + states["sensor.temperature"].state - 5;       ]]]

If I understand correctly, than this works:
[[[ return 'Optimal Room Temperature: ' + states["sensor.temperature"].state + 5; ]]]

But this does not?
[[[ return 'Optimal Room Temperature: ' + states["sensor.temperature"].state - 5; ]]]

That's weird. Can you make sure that "state" contains a number and not a string type?

yes correct, the state is a temperature sensor so the result is for expample "28.1"
i try again and only work / or *


Add touch sensor code blocks to NUgus.proto

https://github.blog/2018-01-29-commit-together-with-co-authors/ make sure @NDxiura is given github credit for this as well when this is merged, since making a new branch will probably not show that he did this

https://github.blog/2018-01-29-commit-together-with-co-authors/ make sure @NDxiura is given github credit for this as well when this is merged, since making a new branch will probably not show that he did this

Okay, will do. Thanks!

Tested it and it works well.

Has @NDxiura been credited?


Add unit tests for DefaultTemplateEngineFactoryService

We need to add some unit tests for this class. Might be worth waiting until the design is finalized for #1183.

4fe07f2298f0fe3233a18dc0f23522133c02d101


Clean installs from repo lead to deprecation warnings in Mongoose

Server is hitting a problem with launching database.
Error log reads:

I think I have fixed this with the latest commit. Just doing a fresh install to test.

The real issue was a clash on the ports, but it didn't hurt to fix the deprecation issue either.

I still get the following warning:
DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html

Adding:
mongoose.Promise = global.Promise;

should fix it.
Also not sure why you would write the result of mongoose.connect to a variable?
I think this code should work fine (adding only two lines of code to the initial server.js):
mongoose.Promise = global.Promise;   // <- added

mongoose.connect( url, {
  useMongoClient: true,              // <- added
} );

var db = mongoose.connection;
db.on( 'error', console.error.bind( console, 'connection error:' ) );
if ( !process.env.NODE_ENV === 'test' ) {
  db.once( 'open', function () {
    console.log( 'DB Connected' );
  } );
}

Or did I just not correctly update after your commit?

I was going to open that as a separate issue later. It's only a warning, but better to update it properly.
My initial problem was actually nothing to do with the deprecation problem - it was just a port clash on windows :)
If you want to make a separate issue and fix it with a PR, go ahead :)
Does this mean you're back on board, @BenGitter?

Just to clarify - I fixed the useMongoClient requirement, but that led to the mpromise deprecation warning.
I half suspect when we fix the mpromise one, another one will rear its head :)

I will create an issue for it.

Does this mean you're back on board, @BenGitter?

I believe I have not even added one commit so far... But I certainly want to start now 👍

IIRC you wrote some of the early tests when it was living in the other two repos :)


PyCicle - first attempt at a build toold for checking PR's

Simple python tool that polls github for PRs and triggers
builds over SSH using slurm (or directly if desired) to
run tests of the PR merged to master.

Pycicle moved to it's own repo. No need for this any more.

Here is the repository: https://github.com/biddisco/pycicle.


Add hideAneLibSymbols property

Add hideAneLibSymbols property missing but necessary when multiple ANEs are present in the project

Looks good! Thanks for the PR!
This is now available on our snapshot repository (https://oss.sonatype.org/content/repositories/snapshots) as version 1.5.0-SNAPSHOT


Adding a Size breaks the drop down?

I added a "size" to the configuration and it seems to break the dropdown. I see a drop down but it's only about 5 pixels tall with no data inside. Any idea what I'm doing wrong?
$("#add-collection select").selectOrDie({
    cycle: true,
    size: 3
});

Sorry. I don't have a fix for this, but looks like some kind of CSS conflict with a modal window I'm using the select or die drop down inside. So I'm going to work on fixing that; it's not a problem with select or die at all.  Thanks.


Build failure with recent new phoenix app

There are two problems when deploying an app generated with a recent Phoenix version (1.7.7):

The buildpack assumes there is a assets/package.json and fails when installing deps from it. The most recent phoenix 1.7 doesn't place this file there. This is the log tail (deployment to Dokku).

-----> Installing binaries
       /cache/node-v18.18.0-linux-x64.tar.gz: OK
       Using cached node 18.18.0...
       Installing Node 18.18.0...
       Downloading and installing npm 10.2.0 (replacing version 9.8.1)...

-----> Building dependencies
       Installing node modules

       up to date in 517ms
       npm ERR! code ENOENT
       npm ERR! syscall open
       npm ERR! path /tmp/build/assets/package.json
       npm ERR! errno -2
       npm ERR! enoent ENOENT: no such file or directory, open '/tmp/build/assets/package.json'
       npm ERR! enoent This is related to npm not being able to find a file.
       npm ERR! enoent

       npm ERR!      Failure during app build
remote:  !     Retagging old image 2e974a41ab58 as dokku/testapp-ex:latest
remote:  !     App build failed

The build command is now mix assets.deploy instead of the previous mix $phoenix.digest. This is an alias from mix.exs, which still runs phx.digest, but after tailwind and esbuild.

PR by @iloveitaly addresses the part with mix assets.deploy too, among other things. - https://github.com/gigalixir/gigalixir-buildpack-phoenix-static/pull/3/files#diff-eba8dcd606bd0014b899e3624e527598796eee3446de65af0fb4274ff8a4792fR14

Workaround/Solution
Place an empty package.json into assets/ and override the compile command.
The package.json can look like this:
{
  "name": "myapp",
  "version": "0.0.1",
  "description": "placeholder package.json to pacify static buildpack",
  "main": "js/app.js"
}

The compile can be overridden by placing a file compile in the project root directory with this content:
cd $phoenix_dir
mix assets.deploy


Support metadata with message pacts

This plugin currently supports grpc request/response metadata when doing grpc services.
It would be great if it also supported metadata with the proto messages too.
Our particular use-cases is around kafka messages, where apart from the message body we can also have message key, headers, and topic data (name, replication factor).
Each of these is encoded in bytes: https://github.com/confluentinc/confluent-kafka-go/blob/master/kafka/message.go#L72
We often encode body as a proto as well.
So for cases when body is a proto, I was thinking of using this plugin and use the proto message to pass the body and metadata to pass the rest of the fields (key, headers).
However I don't think metadata is supported when passing proto messages (last parameter is None):
https://github.com/pactflow/pact-protobuf-plugin/blob/main/src/protobuf.rs#L301

I'm willing to help, but don't know rust. Will learn it eventually, but will likely take some time since I'm working on other projects too rn :)


MPU Fault on some platforms after THREAD_MONITOR "fix"

after commit 718597fe32cdef56e179f9b60b412c708043902f, we are seeing faults on at least 2 platforms: sam e70 and nrf52840_pca10056:
testcase: tests/kernel/threads/thread_apis
***** delaying boot 1000ms (per build configuration) *****
***** Booting Zephyr OS 1.12.0-rc2 (delayed boot 1000ms) *****
Running test suite threads_lifecycle
===================================================================
starting test - test_threads_spawn_params
PASS - test_threads_spawn_params
===================================================================
starting test - test_threads_spawn_priority
PASS - test_threads_spawn_priority
===================================================================
starting test - test_threads_spawn_delay
PASS - test_threads_spawn_delay
===================================================================
starting test - test_threads_spawn_forever
PASS - test_threads_spawn_forever
===================================================================
starting test - test_thread_start
PASS - test_thread_start
===================================================================
starting test - test_threads_suspend_resume_cooperative
PASS - test_threads_suspend_resume_cooperative
===================================================================
starting test - test_threads_suspend_resume_preemptible
PASS - test_threads_suspend_resume_preemptible
===================================================================
starting test - test_threads_priority_set
PASS - test_threads_priority_set
===================================================================
starting test - test_threads_abort_self
PASS - test_threads_abort_self
===================================================================
starting test - test_threads_abort_others
PASS - test_threads_abort_others
===================================================================
starting test - test_threads_abort_repeat
PASS - test_threads_abort_repeat
===================================================================
starting test - test_abort_handler
***** MPU FAULT *****
Executing thread ID (thread): 0x20005164
Faulting instruction address: 0x5bf60ffc
Stacking error
Data Access Violation
Address: 0x20001d18
Fatal fault in thread 0x20005164! Aborting.
Child thread's abort handler called
Calling abort of child from parent
Child thread's abort handler called
PASS - test_abort_handler
===================================================================
starting test - test_delayed_thread_abort
PASS - test_delayed_thread_abort
===================================================================
starting test - test_essential_thread_operation
PASS - test_essential_thread_operation
===================================================================
starting test - test_systhreads_main
PASS - test_systhreads_main
===================================================================
starting test - test_systhreads_idle
PASS - test_systhreads_idle
===================================================================
starting test - test_customdata_get_set_coop

@agross-linaro fyi

Seems not unlikely to just be a stack overflow, given that the only real operation of that patch was to allocate a 16 byte struct at the base of the stack.  Will check in morning.

Consider #8220 , which just moves all this stuff to common code.

Not a stack overflow, what happened is that the MPU stack guard feature requires the stack top to be 32-byte aligned, and I was pushing the new (16 byte) struct onto the stack after that alignment was done instead of before.
Doesn't matter thought because @andrewboie's fix is like 1000% cleaner

I like #8220


Can't tirgger radio onChange event in Filed Component

My Filed Component is:
<Field
    name="rechargeType"
    component="input"
    type="radio"
    value={item.text}
   onChange={::this.handleChange}
/>

and the handleChange Fun is:
    handleChange(e){
        debugger
        console.log(e.target)
    }

the handleChange has no work,and I try to set the Field Component into:
<input
    name="rechargeType"
    type="radio"
    value={item.text}
   onChange={::this.handleChange}
/>

and the fun of handleChange can work, but I must use <Filed ... /> to connect redux and via change the value of radio to change other thing, how can I do?

I had similar problems about the onChange event. Dont know if it is intended or not.
You can manually override the Field components onChange, like this #2406 - I am new to this lib though, so dont know if this is the proper way to do it.
I also found this #2434 today so seems other people having problems with this too.
Perhaps there should be some documentation/examples about how to deal with custom onChange events? Afterall its quite common to do more stuff than just set the value for an onChange.

Fixed by #2385. Let's wait for a new release.


Support for InfluxDB

Objective
Application should support influxdb as datastore as it does now with prometheus
Outcome

[x] Configuration file should have a parameter to support influxdb_url
[x] Application should be worked as normally how it works with prometheus
[x] Documentation should be updated

merged changes with #16


RangeError in structure highlighting

RangeError: Invalid position 978 in document of length 977
  at lineAt(../node_modules/@codemirror/state/dist/index.js:14:19)
  at lineAt(../node_modules/@codemirror/view/dist/index.js:4327:44)
  at lineAt(../node_modules/@codemirror/view/dist/index.js:4422:26)
  at lineAt(../node_modules/@codemirror/view/dist/index.js:4422:26)
  at lineAt(../node_modules/@codemirror/view/dist/index.js:4422:26)
  at lineAt(../node_modules/@codemirror/view/dist/index.js:4422:26)
  at lineAt(../node_modules/@codemirror/view/dist/index.js:4422:26)
  at lineAt(../node_modules/@codemirror/view/dist/index.js:4422:26)
  at lineBlockAt(../node_modules/@codemirror/view/dist/index.js:5086:39)
  at lineBlockAt(../node_modules/@codemirror/view/dist/index.js:6580:31)
  at positionsForNode(editor/codemirror/structure-highlighting/view.ts:102:28)
  at leave(editor/codemirror/structure-highlighting/view.ts:184:43)
  at iterate(../node_modules/@lezer/common/dist/index.js:355:21)
  at read(editor/codemirror/structure-highlighting/view.ts:155:16)
  at ? (../node_modules/@codemirror/view/dist/index.js:6380:34)
  at Array.map(<anonymous>)
  at measure(../node_modules/@codemirror/view/dist/index.js:6378:42)
  at onScrollChanged(../node_modules/@codemirror/view/dist/index.js:6152:22)
  at wrappedArguments(../node_modules/@codemirror/view/dist/index.js:5548:14)
  at HTMLDivElement.i(../../../../browser/src/helpers.ts:73:23)

Now clearer in logging since #1054. This one is unrelated.

The code is adding 1 to a position so it seems likely that some straightforward defensiveness would fix. Would be nice to have a repro though.

So we're finding the lineBlock for the start of the body. I think that starts with the colon.
But visually we want to highlight the next line, so we're moving to the next line via the +1.
But that position might not exist.
So far as I can tell it routinely does not exist in scenarios like
if True: pass

...but lineBlockAt doesn't fail in in these obvious reproductions.

I'm going to extend the minimal fix above to also address this related inconsistency:

Left is my updated fix, right is current behaviour.


Check for != Healthy instead of = [ multiple error codes ]

Hi,
during configuration only existing health states are shown, not all that exist. So it's easier to use != healthy instead of covering all existing failure types (and maybe excluding future failture codes that do not yet exist).
Greetings
Klaas

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

ID: f92acc95-43dd-7756-e20e-fe63c7ed0898
Version Independent ID: 0bf8fc0c-262a-f664-de76-c4146729be8b
Content: Monitor the health of your backups using Azure Backup Metrics (preview) - Azure Backup
Content Source: articles/backup/metrics-overview.md
Service: backup
GitHub Login: @v-amallick
Microsoft Alias: v-amallick

@Klaas- Thanks for the feedback. We will review this request with the content owner and update as appropriate.

Hi @Klaas-
We have updated the Sample alert scenarios section. The changes will be live today.
As the document updates are done, we are now closing this issue. Please reopen this issue if you have any queries around it.
Thanks!
#please-close

Commit https://github.com/MicrosoftDocs/azure-docs/commit/2a1172d64567b1439ab3b0787bdbd5321c583487


Bug: Dashboard Error with Nuxt-svgo module and vite-svg-loader

Hey @murisceman,
I found a new bug regarding svg integration.
When using either https://nuxt.com/modules/nuxt-svgo or the package vite-svg-loader (which the nuxt module is based upon), the pruvious dashboard throws an error.

I know that there's the PruviousIcon and how to integrate that, but sometimes it makes sense to hardcode some SVGs and therefor I thought I should bring it up. Hopefully there's an easy fix.
I used pruvious and vite-svg-loader together in a differen project. Here are the versions.
    "pruvious": "^3.11.7",
    "vite-svg-loader": "^5.1.0"

Nuxt svgo: https://nuxt.com/modules/nuxt-svgo
Vite-SVG-loader: https://github.com/jpkleemans/vite-svg-loader
Thank you in advance!

Hey @SuddenDev!
I just tried the nuxt-svgo module, and it only works if I set the defaultImport to something like 'component'. I'm not sure what causes the error, but I will investigate it when I have time.

I am also getting an error, i only have this two modules in Nuxt 3 modules: ['pruvious', 'nuxt-svgo'],

Is there any quick solution for now?

Hey @Jchegenye!
Depending on how many svgs you have, I just created vue components manually out of those. Otherwise I was also unable to find a workaround.

Hey, @Jchegenye! It's great that you've found a fix for using nuxt-svgo. You can replace Head.vue more elegantly by specifying a path to a custom Head component in your nuxt.config.ts file. The relevant option is pruvious.dashboard.baseComponents.head:
https://github.com/pruvious/pruvious/blob/88271c02e78ce8cece9201bf1e8dfc7cf1fc0ab0/src/runtime/module-types.ts#L249-L254

@murisceman thanks for clarifying, it worked. 👍


Source files not affected by all module resolution options

Stops taking dependency on all module resolution options when sharing sourceFiles and instead moves resolvedModules and resolvedTypeReferenceDirectiveNames from sourceFile to Program so it is safe by program to copy the resolutions across.
This came up as part of testing with #54785 where axion and some more (which i dont recollect) didnt pass incremental resolution check. This is shown in ddaf1c7 specifically (https://github.com/microsoft/TypeScript/commit/ddaf1c77fc29e91cc8a8a5c45dc1cb002d0ee061#diff-215d7c39ab1082f80d4c3a4f1c8bd9dd1c9ccb1c6450192bbaf409b8e5376579R140) where the resolved module on sourceFile changes and results in issues program referencing other resolution.
The issue here lies in fact that "as type" resolution takes into account typeRoots and if config had it its good and used as a key for affecting resolution but if user didnt specify it depends on "config file location" if present otherwise "currentDirectory" . This is issue because you could include either by types or default types (matching in both projects) a type thats in parent directories node_modules/@types but then that type could include types directive of say node which in both projects will be resolved say from config location which is different and if those directories have their own node_modules/@types/node then the location which is picked will depend on which project is picked first
Investigated few options for this

adding default type roots as key but that mean resolutions cannot be shared between two projects with config file in different directories which is very common.
On top of above option adding only present node_modules/@types  in the key but that means on each npm install we would need to update module resolutions from scratch as its change in "key" and parse "sourceFiles" so that doesnt seem practical
The current change where decoupling sourceFiles and module resolution storage, This doesnt fix module resolution cache sharing across projects (which is only in tsbuild for now which doesnt share the caches between watch events and in future we will share in tsserver but that one will watch failed lookup locations so we could somehow use that so probably can be handled in some way without having to invalidate everything)

@typescript-bot test this
@typescript-bot test top100
@typescript-bot test tsserver top100
@typescript-bot user test this
@typescript-bot user test tsserver
@typescript-bot perf test this

@typescript-bot test this
@typescript-bot test top100
@typescript-bot test tsserver top100
@typescript-bot user test this
@typescript-bot user test tsserver
@typescript-bot perf test this

Can you give some more details on what this change is regarding? I can see baselines changing, but I'm not entirely sure what was wrong before.

@DanielRosenwasser Was just in process of writing

Just to confirm my understanding, this moves properties off of SourceFile onto Program, such that the SourceFile can be shared more and has fewer props, and the diff is just all of the old places now calling the Program to get the same info, without any other behavior changes?

It seems like this could actually inflate memory usage (you can see a couple modest increases in some of the perf tests) when there are many programs with identical moduleResolution-related settings and some common dependencies. If the resolution-affecting options are the same between programs, those cases already had optimal SourceFile reuse but will now duplicate the resolutions (or at least maps of pointers to them) across each Program. Would it be valuable to move the resolutions not just to Program but to a shared, properly-keyed data structure similar to DocumentRegistry?

I was thinking as a next step we could try and use module resolution cache to get the result instead of storing it in the program but that needs some thinking( since in most cases resolution already exists in the cache)
storing on document registry would need so comparisons and invalidation logic that would lead to similar issue as I am trying to fix here (resolving type reference of auto type from different locations when two projects don’t specify type roots )


[Analyzer] Nullsafety on final after if, gives an error

Small issue with the analyser regarding to nullsafety
I'm using version Dart SDK version: 2.14.2 (stable) (Wed Sep 15 12:32:06 2021 +0200) on "macos_x64"
We have the following flutter code. _controller is a nullable InAppWebViewController?. To not have to include a ! when we use it, we add a final final controller = _controller and do a check await controller?.canGoBack() == true. In this case, controller is never null, since controller?.anything will return null and null != true 😁.  Therefore await controller.goBack(); should be fine, but it throws an error.
The method 'goBack' can't be unconditionally invoked because the receiver can be 'null'. Try making the call conditional (using '?.') or adding a null check to the target ('!').dart(unchecked_use_of_nullable_value)
  Widget build(BuildContext context) {
    final controller = _controller;
      return WillPopScope(
        onWillPop: () async {
          if (await controller?.canGoBack() == true) {
            await controller.goBack();
            return false;
          }
          return true;
        },

if we instead do
if (controller != null && await controller.canGoBack() == true) {
  await controller.goBack();
...

no errors are thrown. And everything compiles.
If I simplify the code further, this becomes more apparent:
onBackClicked: () async {
  final controller = _controller;
  if (controller?.canGoBack == true) {
    controller.goBack(); <-- The method 'goBack' can't be unconditionally invoked because the receiver can be 'null'.
    return;
  }

Is there any way that controller can be null?
Otherwise, I would suggest to check if the analyser can detect this and allow us to not have to check for null again.

Dart promotes the types of variables when you do certain checks on the variable itself.
Here the controller != null check will promote the controller variable to a non-null type along the true branch.
The check controller?.canGoBack == true does not check the variable controller directly, so there is no promotion.
It's logically correct that if controller?.canGoBack is the non-null value true, then controller cannot be null, but that's more logical inference steps than the compiler will do for you.
We are aware of this short-coming (see https://github.com/dart-lang/language/issues/1224). We haven't decided whether to increase the complexity of the non-null inference to support this case yet.


[BEAM-3566] Replace apply_* hooks in DirectRunner with PTransformOverrides

In the Python DirectRunner, we currently use apply_* overrides to override the operation of the default .expand() operation for certain transforms.  For example, GroupByKey has a special implementation in the DirectRunner, so we use an apply_* override hook to replace the implementation of GroupByKey.expand().
However, this strategy has drawbacks.  Because this override operation happens eagerly during graph construction, the pipeline graph is specialized and modified before a specific runner is bound to the pipeline's execution.  This makes the pipeline graph non-portable and blocks full migration to using the Runner API pipeline representation in the DirectRunner.
By contrast, the SDK's PTransformOverride mechanism allows the expression of matchers that operate on the unspecialized graph, replacing PTransforms as necessary to produce a DirectRunner-specialized pipeline graph for execution.
We therefore want to replace these eager apply_* overrides with PTransformOverrides that operate on the completely constructed graph.
https://issues.apache.org/jira/browse/BEAM-3566

R: @robertwb
This is ready for review.


Add color on ansible logs

Which issue(s) this PR fixes

Fixes None
Additional comments

Add ANSIBLE_FORCE_COLOR environment variable to the ansible subprocess to enable color on logs.
Agreements

[X] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
[X] I hereby agree to grant TOSIT a copyright license to use my contributions.

Why forcing Ansible color ? If a user wants color, it can be activate by adding ANSIBLE_FORCE_COLOR inside .env no ?

I'd like to find a way to both:

be able to remove the colors from the output (as it is currently by default)
but still being able to enable them later when browsing the logs

If we omit them by default, we would never be able to retrieve them later.

We should use the ansible.cfg config, no need to force it.


Force quit with the ability to revert changes silently

With Vim keybinding extensions, there is a command :q! that is a force quit.
When you execute this command it quits, without prompting, and without storing any changes. This is what differentiates it from hotexit, all changes should be reverted.
All prompts should be suppressed and the editor should be closed right away.
Currently there is nothing in the API to allow us to do this
:q! to quit without saving (short for :quit!)
Over at VSCodeVim this is one of our highest rated issues:
https://github.com/VSCodeVim/Vim/issues/979

@bpasero thanks for the comments on the other ticket!

This sounds like a good issue to work on via PR 👍

It was a trap!

If no one is on this yet, I'll try to look into this issue

I have roughly implemented force quit and added an API linked to it. Since i'm not really sure if this is the right way to do it, it would be nice to get some comments about the PR

After implementing, I realized it might be better to add the revert() function into
interface IEditorInput
and directly call the revert function from newly implemented ForceCloseEditorAction
Any thoughts?

@misoguy I think you can do everything with the current API without introducing a lot more. You can use the IEditorGroupService from your action to access the model (IEditorStacksModel) which holds any editor that is open. You can iterate over the groups and editors and call revert() on the ones which are dirty. After that is done you can close the editors.
Btw is it really that q! should close all editors? Maybe this should keep the editors open but just revert all?

@bpasero It seems like the revert() function is only implemented in the abstract class EditorInput and not declared in interface IEditorInput. That is why i asked if declaring the revert() function into the interface was a good idea so that it could be invoked in my action as you proposed.
As for the q! command, it is to my understanding that it should only close the activeEditor, therefore there is no need to iterate over all editors that are open. Did i understand it right? @xconverge

@misoguy yeah the interface doesn't mean a lot, so try to add it there but watch for compile errors.

@bpasero I tried to use the IEditorGroupService in my action as you said, and spent more time looking deeply into the code base. After understanding more of the code, it feels like the code change in my current PR #21548 is more suitable to implement the q! command.
It would be nice if you could briefly review my codes and comment on the changed lines if you still think IEditorGroupService is a better way. Thanks in advance! :)

@misoguy I would first collect the actual requirements of what q! should do before going on. Does it close all files or the active file? Does it only revert? Does it quit?

q! only reverts and quits the active editor

@xconverge what does "active editor" mean when you have multiple editors open. Does it literally reverts and close the currently active tab in the tab UI or revert all tabs and close the window?

Yes the tab, if a user does "qa!" Then we will use this command and iterate over the tabs from our side

@xconverge thanks, looks like we need 2 new commands then.
@misoguy I still think using the editor group API to get the current active editor or all editors and then calling revert is a better approach. The API is all there so we should not arbitrarily introduce new API.

Why do you need 2 new commands? We will use the "force close tab" command and then loop over all tabs and execute the same command
2 commands would be fine though, just no guarantees we would use the "close all tabs of editor" command

After carefully reading the comments, I have newly implemented the command "workbench.action.forceCloseActiveEditor".
As for "force closing all tabs", I wasn't sure if it should be implemented or not.

There is now a workbench.action.revertAndCloseActiveEditor that keybinding can be associated with.


Health check is failing

When fully synced, avalanche will report being unhealthy. This is because the service expects the block count to increase within a certain time period, but the block production rate means this fails.
We should improve the health check so it doesn't report false positives

https://github.com/subquery/subql-avalanche/pull/43
https://github.com/subquery/subql/pull/1501


Bugfix in the matching routine

Our colleague Sofia Johannesson found a bug in the matching routine when using a lattice with RF cavities.
I traced the bug to this change in TEAPOT_MATRIX_Lattice:
https://github.com/PyORBIT-Collaboration/py-orbit/commit/20eb9af471ec3f67a3d53f004db178f071634a46
Since the method to calculate Twiss parameters in TEAPOT_MATRIX_Lattice is also used in the orbit correction and the bumps routines, I assume they are also affected by the bug.
This PR reverts the change that caused the bug.

I think this was introduced by Sabrina Appel @sappel
Let's see if she wants to review it.

I will try to review tomorrow.


governance: Ignore test for changes in monorepo

Problem
According to https://github.com/solana-labs/solana/pull/34407, a governance test currently fails because of how solana-program-test manages forks.
Solution
To unblock that PR, ignore the test for now. Once solana-program-test does things correctly, we can re-enable it.

Merging early to unblock


[Docs] I’m truly sorry if this is not protocol, I have out moronized myself and can’t figure out even to get this working in my spaces

Summary
I’m pretty dumb when it comes to coding I’m a little decent at understanding and structured if anybody has it in her heart to feeling of sorrow for me to try to help me get this going I’d appreciate it
OS / Environment
Apple iPad
Additional Information
It would be cool to have some thing for morons like myself that is more "one button " play
Code of Conduct

[X] I agree to follow the PSF Code of Conduct

No complete description of the problem. Assuming it is a spam.

No complete description of the problem. Assuming it is a spam.

I have no clue how to get the program that is my problem, not spam

Hi @ryanoZphoto I am afraid we need more information than that to understand what is happening.
The way this issue is currently written we cannot simply guess what the problem is about.
Please also note that this issue tracker is exclusive to the setuptools project, if you have problems with other pieces of software, this is not the best place to bring it up.
If you haven't yet read through the Quickstart guide, I recommend to do so.
In the very first paragraphs there is a description of how to install/use setuptools.
If you are not familiar with pip (mentioned in the Quickstart guide), I also recommend having a look on https://pip.pypa.io/en/stable/ and https://packaging.python.org/en/latest/overview/.
After that, if you still have a problem please open a new issue in https://github.com/pypa/setuptools/issues/new/choose and add a more specific description of what you are trying to achieve. If possible add a minimal reproducible example of the steps that you are currently using and why the steps you are using don't work for achieving your goals.


[WIP] Action chain validation improvements

This pull request includes some action chain validation improvements.

Perform on-success and on-failure task name validation during run time. Previously validation happened during run time which means develop-feedback loop was very slow if user was testing workflow with long running tasks and there was, for en example, typo in the take name referenced in on-success / on-failure. This should speed up the whole develop - test loop since this issues are now detected during "pre_run" phase.

I've added some more fixes / improvements.
Now we return a more friendly error if a action parameter or publish parameter resolving fails. Previously only the actual Jinja exception was bubbled up which was not really friendly and made debugging harder.
Now the error message includes task where the exception happened, parameter name and the actual template string.
Before:
ParameterRenderingFailedException: UndefinedError: 'foo_bar' is undefined

After:
ParameterRenderingFailedException: Failed rendering value for parameter "p1" in task "c2" (template string={{ foo_bar }}): 'foo_bar' is undefined


Modify visualizer

This PR introduce some modifications in the following scripts:

iDynTreIrrlichtVisualizer.m;
Utils.m.
in order to let the Visualizer display a plane (flat or inclined).

Closes https://github.com/ami-iit/matlab-whole-body-simulator/issues/77.

After some checks on the code because of errors appearing during the compilation phase, it is now possible to review the Pull Request.

Hi @fabiodinatale,
I added some commits to the PR. Basically, my commits include:

Adding the urdf of the plane to the repo
Simplify the plane urdf to only one plane
remove the duplication of the function "compute rotation matrix of the contact surface"
make the visualizer compatible with its previous version, so if someone is using the visualizer, his/her code works fine also after merging this PR.
Edit the function "compute rotation matrix of the contact surface" to include also the "if condition".

About the function "compute rotation matrix of the contact surface", it seems that the error that we saw was actually because of the length of the function, so if we reduce the comment part in the function, the error is solved.
With the new commits, you should be able to run a simulation in a horizontal/inclined surface. Please check if you could use it in your local project.

Hi @VenusPasandi, thanks for your review and the modifications you made to the code.
In order to check that everything works also on another machine, the latest version of this branch was downloaded and installed. Everything went fine, but when running the simulation, the plane is not displayed in the Visualizer, as the urdf file is not present in the folder robotology-superbuild/build/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf/Plane/FlatPlane, even if the same file is available in the corresponding source directory.
The file was manually copied and it is possible to confirm that with your modifications the plane is displayed with the proper inclination.

About the problem explained above, we tried to reduce the length of the path, but this solution did not solve the problem.
Could the format of the file be the cause of this problem? @traversaro

How did you installed the new branch? If you switched to the new branch and run make install without first re-running CMake it is possible that CMake is not aware that a new file is there. If you run cmake the problem should be fixed.

About the problem explained above, we tried to reduce the length of the path, but this solution did not solve the problem.
Could the format of the file be the cause of this problem? @traversaro

How did you installed the new branch? If you switched to the new branch and run make install without first re-running CMake it is possible that CMake is not aware that a new file is there. If you run cmake the problem should be fixed.

Yes, I first run cmake and then make install, it creates the new folders but it does not create the new file. @traversaro please note that we located the urdf file in +mwbs/+Visualizer/+robotVisualizer/Urdf/Plane/FlatPlane where we have all the matlab files. I think when we install the repo, it creates all the matlab files in mex folder, and the urdf file is not a matlab file, so it does not locate it in mex folder. It is just my feeling, I don't know if it is correct.

Ok, let me check.

Yes, I first run cmake and then make install, it creates the new folders but it does not create the new file.

Just to confirm that I followed the same procedure and had the same results.

Indeed, I just tried and the files installed are:
traversaro@IITICUBLAP257:~/robotology-superbuild/buildapt/src/matlab-whole-body-simulator$ make install
Install the project...
-- Install configuration: "Release"
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_robotSensors_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/slblocks.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_visualizers_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@Utils
-- Up-to-date<EMAIL_ADDRESS>-- Installing<EMAIL_ADDRESS>-- Installing<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer
-- Installing: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf
-- Installing: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf/Plane
-- Installing: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf/Plane/FlatPlane
-- Installing: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/iDynTreeIrrlichtVisualizer.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/RobotVisualizer.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/initRobotVisualizer.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+robotDynWC
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+robotDynWC/step_block.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+robotDynWC/step_block_with_closed_chain.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/loadRobotDynamicsWithContactsCB.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/initRobotDynamicsWithContactsCB.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/initRobotDynamicsWithContactsCB_closedChains.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+iDynTree2WBTmappers
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+iDynTree2WBTmappers/loadReducedModel.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+iDynTree2WBTmappers/KinDynComputations.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/init_mask_RobotDynWithContactsClosedChainCB.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@Contacts
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Installing<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@State
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@Robot
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/getModelPathFromFileNameAndYarpFinder.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotSensors
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotSensors/+IMUsensor
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotSensors/+IMUsensor/IMUsensorProc.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_robotDynamicsWithContacts_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/meshes
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/meshes/hokuyo.dae
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/meshes/hokuyo.stl
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/robots
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/robots/RRbot1
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/robots/RRbot1/model.urdf

so +robotVisualizer/Urdf/Plane/FlatPlane/Plane.urdf is not installed. So, I checked why these files should be installed in the first place, and this is in the CMakeLists.txt:
# Copy the classes and Simulink slx library files
install(
  DIRECTORY ${M_FILES_DIR}
  DESTINATION ${MATLAB_WHOLE_BODY_SIMULATOR_INSTALL_MATLAB_FILESDIR}
  USE_SOURCE_PERMISSIONS
  FILES_MATCHING
  PATTERN "*.m"
  PATTERN "*.slx")

from https://github.com/ami-iit/matlab-whole-body-simulator/blob/c760c0d80337d0128704b4124607f8739a9e3000/CMakeLists.txt#L25 . Probably the problem is that there the parameters:
  FILES_MATCHING
  PATTERN "*.m"
  PATTERN "*.slx"

only install .m and .slx files. Removing those parameters, I obtain:
traversaro@IITICUBLAP257:~/robotology-superbuild/buildapt/src/matlab-whole-body-simulator$ make install
Install the project...
-- Install configuration: "Release"
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_robotSensors_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/slblocks.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_visualizers_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@Utils
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf/Plane
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf/Plane/FlatPlane
-- Installing: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf/Plane/FlatPlane/Plane.urdf
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/iDynTreeIrrlichtVisualizer.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/RobotVisualizer.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/initRobotVisualizer.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+robotDynWC
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+robotDynWC/step_block.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+robotDynWC/step_block_with_closed_chain.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/loadRobotDynamicsWithContactsCB.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/initRobotDynamicsWithContactsCB.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/initRobotDynamicsWithContactsCB_closedChains.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+iDynTree2WBTmappers
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+iDynTree2WBTmappers/loadReducedModel.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/+iDynTree2WBTmappers/KinDynComputations.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotDynamicsWithContacts/init_mask_RobotDynWithContactsClosedChainCB.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@Contacts
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@State
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/@Robot
-- Up-to-date<EMAIL_ADDRESS>-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/getModelPathFromFileNameAndYarpFinder.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotSensors
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotSensors/+IMUsensor
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+RobotSensors/+IMUsensor/IMUsensorProc.m
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/mex/mwbs_robotDynamicsWithContacts_lib.slx
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/meshes
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/meshes/hokuyo.dae
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/meshes/hokuyo.stl
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/robots
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/robots/RRbot1
-- Up-to-date: /home/traversaro/robotology-superbuild/buildapt/install/share/RRbot/robots/RRbot1/model.urdf

So you can see that -- Installing: /home/traversaro/robotology-superbuild/buildapt/install/mex/+mwbs/+Visualizers/+robotVisualizer/Urdf/Plane/FlatPlane/Plane.urdf is correctly installed.
As I do not see any advantage in having those parameters (just more problems like this the next time somebody wants to add a file with a different extension), I just dropped them in the next commit.

Problem with the installation fixed in https://github.com/ami-iit/matlab-whole-body-simulator/pull/79/commits/61f8d797a1fc2601f57b7ffe37d3659a01b9a956 .

Confirm that the modification done by @traversaro solved the problem:

Thanks!

Thanks @traversaro for the detailed explanation about the problem.


Not able to package(secor-0.24) : mvn clean -Pkafka-0.10-dev package failed

[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ secor --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 86 source files to /Users/jeetu/Repositories/secor-0.24/target/classes [WARNING] /Users/jeetu/Repositories/secor-0.24/src/main/java/com/pinterest/secor/tools/TestLogMessageProducer.java: Some input files use or override a deprecated API. [WARNING] /Users/jeetu/Repositories/secor-0.24/src/main/java/com/pinterest/secor/tools/TestLogMessageProducer.java: Recompile with -Xlint:deprecation for details. [WARNING] /Users/jeetu/Repositories/secor-0.24/src/main/java/com/pinterest/secor/tools/ProgressMonitor.java: Some input files use unchecked or unsafe operations. [WARNING] /Users/jeetu/Repositories/secor-0.24/src/main/java/com/pinterest/secor/tools/ProgressMonitor.java: Recompile with -Xlint:unchecked for details. [INFO]  [INFO] --- exec-maven-plugin:1.1:exec (default) @ secor --- [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.863 s [INFO] Finished at: 2017-09-01T14:23:43+05:30 [INFO] Final Memory: 43M/335M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1:exec (default) on project secor: Result of /bin/sh -c cd /Users/jeetu/Repositories/secor-0.24 && git log --pretty=format:build_revision=%H -n1 execution is: '128'. -> [Help 1] [ERROR]  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR]  [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

It doesn't seem I can reproduce this problem, 'mvn clean -Pkafka-0.10-dev
package' works fine for me.  And current version is already '0.25-SNAPSHOT'
On Fri, Sep 1, 2017 at 1:57 AM, jitendrasinghsankhwar <
<EMAIL_ADDRESS>wrote:

[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ secor
--- [INFO] Changes detected - recompiling the module! [INFO] Compiling 86
source files to /Users/jeetu/Repositories/secor-0.24/target/classes
[WARNING] /Users/jeetu/Repositories/secor-0.24/src/main/java/com/
pinterest/secor/tools/TestLogMessageProducer.java: Some input files use
or override a deprecated API. [WARNING] /Users/jeetu/Repositories/
secor-0.24/src/main/java/com/pinterest/secor/tools/TestLogMessageProducer.java:
Recompile with -Xlint:deprecation for details. [WARNING]
/Users/jeetu/Repositories/secor-0.24/src/main/java/com/
pinterest/secor/tools/ProgressMonitor.java: Some input files use
unchecked or unsafe operations. [WARNING] /Users/jeetu/Repositories/
secor-0.24/src/main/java/com/pinterest/secor/tools/ProgressMonitor.java:
Recompile with -Xlint:unchecked for details. [INFO] [INFO] ---
exec-maven-plugin:1.1:exec (default) @ secor --- [INFO]
[INFO] BUILD FAILURE [INFO] ------------------------------
------------------------------------------ [INFO] Total time: 5.863 s
[INFO] Finished at: 2017-09-01T14:23:43+05:30 [INFO] Final Memory: 43M/335M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1:exec
(default) on project secor: Result of /bin/sh -c cd
/Users/jeetu/Repositories/secor-0.24 && git log --pretty=format:build_revision=%H
-n1 execution is: '128'. -> [Help 1] [ERROR] [ERROR] To see the full stack
trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven
using the -X switch to enable full debug logging. [ERROR] [ERROR] For more
information about the errors and possible solutions, please read the
following articles: [ERROR] [Help 1] http://cwiki.apache.org/
confluence/display/MAVEN/MojoExecutionException
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/360, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHCX_-eYKGX4s6mRHDXtma8gWSeVHMrJks5sd8b-gaJpZM4PJ4fz
.

Hi @HenryCaiHaiying,
I'm seeing a similar issue. In fact I am unable to build the release 0.24. However I am able to build a release for the current master branch.
I think that it is related to [this].(https://github.com/pinterest/secor/commit/77200c8ca3eb9e4ff6ad6fe4925b74615d7e0fbf#diff-600376dffeb79835ede4a0b285078036)
Would it be possible to push a release for 0.25?

is 0.24 packaging the wrong pom.xml?
I can try to push out the 0.25 with the current master branch.
On Tue, Sep 19, 2017 at 6:20 PM, Jesse<EMAIL_ADDRESS>wrote:

Hi @HenryCaiHaiying https://github.com/henrycaihaiying,
I'm seeing a similar issue. In fact I am unable to build the release 0.24.
However I am able to build a release for the current master branch.
I think that it is related to [this].(77200c8#diff-
600376dffeb79835ede4a0b285078036
https://github.com/pinterest/secor/commit/77200c8ca3eb9e4ff6ad6fe4925b74615d7e0fbf#diff-600376dffeb79835ede4a0b285078036
)
Would it be possible to push a release for 0.25?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/360#issuecomment-330717690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHCX_xrQwsBBClKECWd6xyQzTKdp_SUfks5skGhIgaJpZM4PJ4fz
.

Hi @HenryCaiHaiying,
I am actually struggling to reliably reproduce the issue I mentioned above.
it may just be easier to push out the 0.25 release.
Thanks,
jesse

Just cut the version 0.25, please have a try to see if that fixed your
problem.
On Wed, Sep 20, 2017 at 9:31 PM, Jesse<EMAIL_ADDRESS>wrote:

Hi @HenryCaiHaiying https://github.com/henrycaihaiying,
I am actually struggling to reliably reproduce the issue I mentioned above.
it may just be easier to push out the 0.25 release.
Thanks,
jesse
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/360#issuecomment-331048248,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHCX_x-3CnSWlWuj3INSRQTVrTp_nXg8ks5skeargaJpZM4PJ4fz
.


I just lost all my environment variable overrides

Description
I was adding in 2 new environment variables for a react app in the Manage environment variables section. I also added some overrides and i subsequently lost all other branch variable overrides. I don't even know how it happened maybe the ui didn't load fully and i was too quick to save the form with the new env vars I added? Using Brave [Version 1.67.119 Chromium: 126.0.6478.114 (Official Build) (arm64)]
We've managed to add them back in, maybe it's a numbers issue? So far we have 29 variables with 39 various overrides

Hi @michaeltrestianu23 , thanks for reaching out. Can you confirm if the below steps are accurate to reproduce the issue?

Start with an existing app that has a few environment variables and overrides
Add a couple of new environment variables with overrides
Save the changes
Observe that the branch-level overrides for the existing environment variables were unexpectedly deleted

Also, can you share your Amplify app id?

Hi @Jay2113 thanks for getting back to me,
Our app id is d2125if9n5v7i0
I can confirm that this is defiantly a loading issue. This morning I saw that I was logged out and so I logged back in only to see that the overrides didn't load again, even after multiple page refreshes. I subsequently went to the app overview page to get you the app id and went back and they all displayed/loaded. Yesterday i didn't notice so when i added new overrides along with new variables it must've removed the ones that didn't load.
Thanks

Hi @Jay2113 I work on the same project as Michael and the issue seems to be that it doesn't always open the override variables in the UI when you click the "Manage Variables" button. I can see the variables being returned in the network tab, but they just aren't making their way to the UI. This means if you go to add a new variable and click save it completely removes the old override variables. I suspect it may be some kind of state issue in the UI. Perhaps it would be good to have a JSON tab where you can edit override variables there instead? Many Thanks!

@mattrout92 @michaeltrestianu23  thanks for sharing the additional details. If you are still able to reproduce this behavior, can you capture a HAR file and share it with us? This will be helpful for us to investigate the network requests and responses.
Steps to capture the HAR file are outlined here: https://repost.aws/knowledge-center/support-case-browser-har-file.

@Jay2113 i'm not comfortable sharing that as it'll contain sensitive info. Here are the steps to re-produce

Login
Ensure there are 29 environment variables set up for a project
Add overrides (we have 9 for branch w, 9 for branch x, 12 for branch y, 12 for branch z)
If you navigate directly to the url variables/edit the overrides don't loaded properly

When you manually use the internal links in the Hosting side menu and click environment variables and then select the manage variables button then they load properly.
The issue seems to be something around server side requests.
Thanks

@michaeltrestianu23 I was able to reproduce the issue when directly navigating to the variables/edit deep link URL. Marking this as a bug and in the interim we highly recommend you to use the console workflow for managing the environment variables and overrides i.e. Hosting -> Environment variables -> Manage variables -> Save.
We are working on prioritizing a fix for this issue.

Hi @Jay2113
The Console workflow has the same problem; we've lost all our environment variables.
Hosting -> Environment variables -> Manage variables -> Save

Hi @rammanokar-plateron, can you please provide the following:

The Amplify app id
A HAR file capturing the network requests and responses. Steps to capture the HAR file
Detailed steps to reproduce the issue, as we are unable to replicate it.

Hi @michaeltrestianu23 @mattrout92 @rammanokar-plateron 👋 , thanks for your continued patience. We have deployed a fix for this issue. I will go ahead and close this thread but please feel free to reopen it or create a new thread if you are still experiencing this issue.


List transaction outputs

I think this is ready to go. I did a few things:

Bitcoin datadir needed Bitcoin added to it on Linux
The map vs string issue was because getrawtransactions returns hex when verbose is false
Update to redb 0.5.0, which automatically aborts transactions on drop, so we won't get that leaked write transaction warning (see https://github.com/cberner/redb/issues/320)

I added and then removed a wrapper, AbortOnDrop, but post 0.5.0 we don't need it so I removed it.


Routeupdate

New branches should be from develop branch, not master. Closing this one for now. Please submit new one that is from develop according to git-workflow document with the same code changes


Downloadable files

I need help on this.
I need to implement downloadable files for

[ ] Press Files
[ ] Possible downloadable Assets in Articles

Dear Issei, how can I help you on this?

Dear Nicholas,
as you might remember, we ran into a snag when we tried to make assets downloadable in the PressFiles page.
We left it on the side as we kept our attention on more pressing matters. But now it is necessary for me to visit this problem again, since downloadable assets are also needed for the articles in the Blog.
I have found little help on the interweb to take care of this matter myself. I'm afraid that my global comprehensions of servers and nodejs is seriously lacking. It seemed to me that these were needed to better understand the subject.
Hence, my plea for help.
I await thy reply gratefully


Stage Editor, 6K+ support, and winning icons.

close the other issue

just get good at coding lol

give me a pre builded psych engine

whats a beathit editor?

whats a beathit editor?

well. a editor for the beathit.hx file. you can edit the values

whats a beathit editor?

well. a editor for the beathit.hx file. you can edit the values

What is it even supposed to do

What is it even supposed to do

this. a editor for the beathit.hx file to edit the beathit on a song without using the fuckin sourcecode

There's no beathit.hx file, and that still doesn't explain what the point of this is

where is the "Beathit.hx" file located

the source folder. heres the code
package;
import Conductor.BPMChangeEvent;
import flixel.FlxG;
import flixel.addons.ui.FlxUIState;
import flixel.math.FlxRect;
import flixel.util.FlxTimer;
import flixel.addons.transition.FlxTransitionableState;
import flixel.tweens.FlxEase;
import flixel.tweens.FlxTween;
import flixel.FlxSprite;
import flixel.util.FlxColor;
import flixel.util.FlxGradient;
import flixel.FlxState;
import flixel.FlxBasic;
class MusicBeatState extends FlxUIState
{
private var lastBeat:Float = 0;
private var lastStep:Float = 0;
private var curStep:Int = 0;
private var curBeat:Int = 0;

private var controls(get, never):Controls;

inline function get_controls():Controls
	return PlayerSettings.player1.controls;

override function create() {
	var skip:Bool = FlxTransitionableState.skipNextTransOut;
	super.create();

	if(!skip) {
		openSubState(new CustomFadeTransition(0.7, true));
	}
	FlxTransitionableState.skipNextTransOut = false;
}

#if (VIDEOS_ALLOWED && windows)
override public function onFocus():Void
{
	FlxVideo.onFocus();
	super.onFocus();
}

override public function onFocusLost():Void
{
	FlxVideo.onFocusLost();
	super.onFocusLost();
}
#end

override function update(elapsed:Float)
{
	//everyStep();
	var oldStep:Int = curStep;

	updateCurStep();
	updateBeat();

	if (oldStep != curStep && curStep > 0)
		stepHit();

	if(FlxG.save.data != null) FlxG.save.data.fullscreen = FlxG.fullscreen;

	super.update(elapsed);
}

private function updateBeat():Void
{
	curBeat = Math.floor(curStep / 4);
}

private function updateCurStep():Void
{
	var lastChange:BPMChangeEvent = {
		stepTime: 0,
		songTime: 0,
		bpm: 0
	}
	for (i in 0...Conductor.bpmChangeMap.length)
	{
		if (Conductor.songPosition >= Conductor.bpmChangeMap[i].songTime)
			lastChange = Conductor.bpmChangeMap[i];
	}

	curStep = lastChange.stepTime + Math.floor(((Conductor.songPosition - ClientPrefs.noteOffset) - lastChange.songTime) / Conductor.stepCrochet);
}

public static function switchState(nextState:FlxState) {
	// Custom made Trans in
	var curState:Dynamic = FlxG.state;
	var leState:MusicBeatState = curState;
	if(!FlxTransitionableState.skipNextTransIn) {
		leState.openSubState(new CustomFadeTransition(0.6, false));
		if(nextState == FlxG.state) {
			CustomFadeTransition.finishCallback = function() {
				FlxG.resetState();
			};
			//trace('resetted');
		} else {
			CustomFadeTransition.finishCallback = function() {
				FlxG.switchState(nextState);
			};
			//trace('changed state');
		}
		return;
	}
	FlxTransitionableState.skipNextTransIn = false;
	FlxG.switchState(nextState);
}

public static function resetState() {
	MusicBeatState.switchState(FlxG.state);
}

public static function getState():MusicBeatState {
	var curState:Dynamic = FlxG.state;
	var leState:MusicBeatState = curState;
	return leState;
}

public function stepHit():Void
{
	if (curStep % 4 == 0)
		beatHit();
}

public function beatHit():Void
{
	//do literally nothing dumbass
}

}

that file is not called beathit, and you still haven't explained what the point of this is


RoboVM won't include gdx into classpath when using libGDX compiled from source

Issue details
When libGDX is compiled from source using mvn install (https://libgdx.com/dev/from-source/) everything works fine except the robovm-backend. When trying to use the manually compiled robovm-backend it won't work. The gdx module won't get included in the classpath (can be seen in the building log). Therefor the app isn't running because the gdx core is missing.
Reproduction steps/code
I've forked a simple libGDX App.

clone this repository: https://github.com/Berstanio/chigginblazzder
run the ios module with the IntelliJ mobivm plugin (newest official version)
The App will run normally. (This means the configuration of the game is correct)
clone libGDX and run mvn install
checkout the "error" branch
clear all caches and do a gradle sync (It was important for reproducing when I tested it)
run the ios module with the IntelliJ mobivm plugin (newest official version)
It will produce a NoClassDefFound error when running but the reason is that the gdx module won't get included into the classpath (can be seen in the logs)

I hope it can be reproduced!
Version of libGDX and/or relevant dependencies
Build from source.
Stacktrace
Not relevant. But if the build logs are needed I can provide them.
Please select the affected platforms

[ ] Android
[x] iOS
[ ] HTML/GWT
[ ] Windows
[ ] Linux
[ ] MacOS

I've just tested building a libGDX version from Master and your demo project works ok with it.
I'd suggest you test with a named version (such as 1.10.1.TEST), SNAPSHOT are not always updated and becaue of the Maven cache policies them are not ideal for this kind of testing. You can just find/replace in files from IDEA on all pom.xml files and if you need to test again use TEST2, etc...
Also, when building libGDX do a mvn clean install (be aware of the CLEAN).
I've tested with MobiVM 2.3.12 plugin, don't think it's related but just as disclosure.

Today I tried it again (without rebuild of libGDX) and it worked. The only thing I changed was setting the "MAVEN_REPOSITORY" environment variable because Android Studio said it wasn't set. But other dependencies that were in the local maven repository were picked up correctly. So could this missing variable still lead to the issue?


Remove Stetho/Flipper linkage from Release build

Stetho/Flipper are great tools for looking inside your Android/iOS app. But they are not tools we should leave in the app when we build a Release. Show through additional modules how to remove Stetho/Flipper on Release builds.
I am happy to raise a PR for this

Both removed


Set an  and

What ist the common way to set a line breake
 and a
.
I tried

**What's new?** /
---

* The release notes now use HTML to look friendlier
* A lot of small improvements on Courier2

/There should be no visible changes for Courier 1 users.

in this code.
package main

import (
	"fmt"
	"io/ioutil"

	"github.com/a8m/mark"
)

func main() {
	markdown_text, err := ioutil.ReadFile("testdata/test3.md")
	html := mark.Render(string(markdown_text))
	fmt.Print(html, err)
}

But it dont set an
 after two spaces or an
 for ---.
I got this

strong>Test This

 ---

Bla 1

Bla 2

Did it work?

<nil>

Headline
---

---

hello
world

Note that there are two spaces after the word hello.

Closing this issue, feel free to open if you have more comments.


Preliminary work for adding SDFG elements graphically

Contains search UI improvements and preliminary work for adding SDFG elements graphically

I'm closing this PR because just like with the webclient, I have moved all commits to a new branch so we can continue working on this and eventually merge your changes in - see PR #29. Very nice work, thank you for the awesome contribution!


Incorrect audio bitrate value on itag lookup table of file 'itags.py'

While trying to get information about a progressive 720p stream(itag 22), the library gave me a value of '192kbps' as the audio bitrate for said stream.
However, as I downloaded the stream and inspected it with ffprobe, it then said that the audio bitrate was 128kbps instead of the 192kbps stated by pytubefix.
So, I decided to investigate further and found out that the culprit of this issue is in pytubefix/itags.py (line 10), and in the lookup table the audio bitrate is set to 192kbps instead of the correct 128kbps value.
I also tried this with 10 random videos and the issue persists.

This is the script to download and get information about the aforementioned stream:
from pytubefix import YouTube

suspect = YouTube(
	'https://www.youtube.com/watch?v=E8gmARGvPlI', # Wham! - Last Christmas
	use_oauth=True,
	allow_oauth_cache=True
).streams.get_by_itag(22)

print('Audio Bitrate:', suspect.abr)

suspect.download()

This is the output of the script:
Audio Bitrate: 192kbps

This is the ffprobe script I used to get information about the video:
ffprobe -hide_banner <filename>.mp4

And this is the output of ffprobe:
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\Wham! - Last Christmas (Official Video).mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2023-12-21T14:58:19.000000Z
  Duration: 00:04:38.36, start: 0.000000, bitrate: 968 kb/s
  Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], 837 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
    Metadata:
      creation_time   : 2023-12-21T14:58:19.000000Z
      handler_name    : ISO Media file produced by Google Inc. Created on: 12/21/2023.
      vendor_id       : [0][0][0][0]
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 127 kb/s (default) # THIS LINE
    Metadata:
      creation_time   : 2023-12-21T14:58:19.000000Z
      handler_name    : ISO Media file produced by Google Inc. Created on: 12/21/2023.
      vendor_id       : [0][0][0][0]

After searching a bit on the internet I found out itag 22 is meant to be 192kbps, but for some reason it rarely is.
I don't know what the reason might be, but it seems like I've made a mistake.
Sorry if I caused any problems.


Yellow and orange need some work.

The theme is still in its early days, and now that it's mostly styled, I have to be honest that the orange and yellow variants are not as pleasant to look at as the peach. Yellow, especially. Readability is great and all, but there's probably more research to be done on the intersection between readability and reduced eyestrain.

Original yellow and orange themes removed in upcoming branch.


unable to aggregate multiple .json/.html into single report(how to do that)

Hi,
I currently, I have the following set up in my pom.
However, upon running them using mvn clean compile test - the tests run e2e and also it generates multiple .json/.html file in the above folder. But I need one single report with all the test runs. Can you explain on how I can achieve this?

I have the same questions.

Hi there! You can aggregate all these results by maven-cucumber-reporting plugin
            <plugin>                 <groupId>net.masterthought</groupId>                 <artifactId>maven-cucumber-reporting</artifactId>                 <version>${maven-cucumber-reporting.version}</version>                 <executions>                     <execution>                         <id>execution</id>                         <phase>verify</phase>                         <goals>                             <goal>generate</goal>                         </goals>                         <configuration>                             <projectName>vdr-tests</projectName>                             <outputDirectory>${project.build.directory}/cucumber-parallel/cucumber-html-reports</outputDirectory>                             <cucumberOutput>${project.build.directory}/cucumber-parallel/</cucumberOutput>                             <parallelTesting>true</parallelTesting>                         </configuration>                     </execution>                 </executions>             </plugin>

Hi @natkrish ! You can aggregate all these results by maven-cucumber-reporting plugin
            <plugin>
                <groupId>net.masterthought</groupId>
                <artifactId>maven-cucumber-reporting</artifactId>
                <version>${maven-cucumber-reporting.version}</version>
                <executions>
                    <execution>
                        <id>execution</id>
                        <phase>verify</phase>
                        <goals>
                            <goal>generate</goal>
                        </goals>
                        <configuration>
                            <projectName>vdr-tests</projectName>
                            <outputDirectory>${project.build.directory}/cucumber-parallel/cucumber-html-reports</outputDirectory>
                            <cucumberOutput>${project.build.directory}/cucumber-parallel/</cucumberOutput>
                            <parallelTesting>true</parallelTesting>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

It will be looks like

Hi @natkrish ,
You can check out below plugin as well.
https://github.com/trivago/cluecumber-report-plugin


Update Cirq decomposition to use RZ, RX, CNOT only

These gates are preferred for efficiency in our system.
I looked at updating the tests, but they appear to be agnostic to how we decompose and just check correctness, which is great!
Hopefully coverage agrees, will add cases for uncovered lines.

Please forgive any glaring errors, I am only a software middleman for the quantum goodness :) Specifically I don't know enough about gate naming convention to be sure my docs/comments are correct.

sorry for the slow turnaround :) here you are

If you point me in the direction of an example migration to transformer, I can start that PR :)

Automerge cancelled: A required status check is not present.
Missing statuses: ['Pytest Ubuntu (3.7)', 'Pytest Ubuntu (3.8)', 'Pytest Ubuntu (3.9)', 'Pytest Windows (3.7)', 'Pytest Windows (3.8)', 'Pytest Windows (3.9)', 'Typescript lint check', 'Typescript tests', 'Typescript tests coverage']

cut https://github.com/quantumlib/Cirq/issues/4901
Thanks for the review! :)


fix issue about user list function  && delete record operation function - [closed]

In GitLab by @sokril on Jul 9, 2018, 06:05
Merges weidev -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:14
The test coverage for backend is 23.6%  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:14
The test coverage for backend is 23.6%  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:14
The test coverage for backend is 23.6%  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:14
The test coverage for backend is 23.6%  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:14
closed