multiple compilers

This is my model:
mid = (td.Map(td.Tensor((24,10)) >>
                td.ScopedLayer(convLayer) >>
                td.Function(lambda x: tf.reshape(x,[-1,64*(10-2)]))) >>
         td.Fold(td.Concat() >>
                 td.Function(td.FC(128)), td.FromTensor(tf.zeros(128))))
model = ( mid  >>  td.Function(td.FC(1)))

(The ScopedLayer(convLayer) part is related to solved issue #14 )
I trained it using model: compiler = td.Compiler.create((model, td.Scalar())), and it works. However, now I want the result of mid for a set of values. I can do encod.eval(X[i]) for every piece of data, but that is painfully slow. However, if I try to create a new compiler:
newComp=td.Compiler.create((mid,))
Y=sess.run(mid,newComp.build_feed_dict(X))

I get: TypeError: block <td.Pipe> is already a child of <td.Pipe>
How can I solve this? eval on each entry will take a bit over 4 hours ...

Hi Fábio,
The eval function is intended for interactively testing your compiler
object.  It pays a lot of setup costs every time as a result.
Have a look at "Batching Inputs
https://github.com/tensorflow/fold/blob/master/tensorflow_fold/g3doc/running.md#batching-inputs"
to see how to run using the compiler.build_feed_dict mechanism, which
should be much faster.
Best wishes,
-Marcello
On Thu, Feb 23, 2017 at 10:45 PM, Fábio Dias<EMAIL_ADDRESS>wrote:

This is my model:
mid = (td.Map(td.Tensor((24,10)) >>
td.ScopedLayer(convLayer) >>
td.Function(lambda x: tf.reshape(x,[-1,64*(10-2)]))) >>
td.Fold(td.Concat() >>
td.Function(td.FC(128)), td.FromTensor(tf.zeros(128))))
model = ( mid  >>  td.Function(td.FC(1)))
(The ScopedLayer(convLayer) part is related to solved issue #14
https://github.com/tensorflow/fold/issues/14 )
I trained it using model: compiler = td.Compiler.create((model,
td.Scalar())), and it works. However, now I want the result of mid for a
set of values. I can do encod.eval(X[i]) for every piece of data, but that
is painfully slow. However, if I try to create a new compiler:
newComp=td.Compiler.create((mid,))
Y=sess.run(mid,newComp.build_feed_dict(X))
I get: TypeError: block <td.Pipe> is already a child of <td.Pipe>
How can I solve this? eval on each entry will take a bit over 4 hours ...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/fold/issues/16, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABepNCPtZfud7Tcae4vaSsf_QRESrdcks5rfnyKgaJpZM4MK4Yb
.

Marcello, I'm aware, however, as I said, when I construct a new compiler it doesn't work, with the error:
TypeError: block <td.Pipe> is already a child of <td.Pipe>

Ah.  I misread this the first time.
We didn't anticipate this use-case, so blocks are mutable objects that have
state and belong to at most one compiler.  If this is sufficiently
counterintuitive we'll consider fixing it.
For now, you can create a copy of the blocks (though you'll also have to
explicitly set a scope in the scoped layers so they'll use the same
variables.)
You should be able to get away with something like this:
convScopedLayer = td.ScopedLayer(convLayer)
def make_mid():
return (td.Map(td.Tensor((24,10)) >>
convScopedLayer >>
td.Function(lambda x: tf.reshape(x,[-1,64*(10-2)]))) >>
td.Fold(td.Concat() >>
td.Function(td.FC(128)), td.FromTensor(tf.zeros(128))))
model = ( make_mid  >>  td.Function(td.FC(1)))
compiler1 = td.Compiler(model)
compiler2 = td.Compiler(make_mid())
On Fri, Feb 24, 2017 at 9:17 AM, Fábio Dias<EMAIL_ADDRESS>wrote:

Marcello, I'm aware, however, as I said, when I construct a new compiler
it doesn't work, with the error:
TypeError: block <td.Pipe> is already a child of <td.Pipe>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/fold/issues/16#issuecomment-282348581, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABepPej3sUoroQEIbWR1yZjHSzqh7Unks5rfxCNgaJpZM4MK4Yb
.

Lost some parentheses, that line should be "model = ( make_mid() >>
td.Function(td.FC(1)))"
On Fri, Feb 24, 2017 at 9:31 AM, Marcello Herreshoff <
<EMAIL_ADDRESS>wrote:

Ah.  I misread this the first time.
We didn't anticipate this use-case, so blocks are mutable objects that
have state and belong to at most one compiler.  If this is sufficiently
counterintuitive we'll consider fixing it.
For now, you can create a copy of the blocks (though you'll also have to
explicitly set a scope in the scoped layers so they'll use the same
variables.)
You should be able to get away with something like this:
convScopedLayer = td.ScopedLayer(convLayer)
def make_mid():
return (td.Map(td.Tensor((24,10)) >>
convScopedLayer >>
td.Function(lambda x: tf.reshape(x,[-1,64*(10-2)]))) >>
td.Fold(td.Concat() >>
td.Function(td.FC(128)), td.FromTensor(tf.zeros(128))))
model = ( make_mid  >>  td.Function(td.FC(1)))
compiler1 = td.Compiler(model)
compiler2 = td.Compiler(make_mid())
On Fri, Feb 24, 2017 at 9:17 AM, Fábio Dias<EMAIL_ADDRESS>wrote:

Marcello, I'm aware, however, as I said, when I construct a new compiler
it doesn't work, with the error:
TypeError: block <td.Pipe> is already a child of <td.Pipe>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/fold/issues/16#issuecomment-282348581,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABepPej3sUoroQEIbWR1yZjHSzqh7Unks5rfxCNgaJpZM4MK4Yb
.

So, I tried that approach. Here's the relevant (full) code:

CL=td.ScopedLayer(convLayer)

def mk_encod():
    return(td.Map(td.Tensor((24,10)) >>  CL >>
                  td.Function(lambda x: tf.reshape(x,[-1,64*(10-2)]))) >>
           td.Fold(td.Concat() >>
                   td.Function(td.FC(256)), td.FromTensor(tf.zeros(256))))

model = ( mk_encod()  >>  td.Function(td.FC(1)))

compiler = td.Compiler.create((model, td.Scalar()))
y, y_ = compiler.output_tensors
loss = tf.nn.l2_loss(y - y_)
train = tf.train.AdamOptimizer().minimize(loss)
sess.run(tf.global_variables_initializer())
for i in range(1000):
    sess.run(train, compiler.build_feed_dict([get_example() for _ in range(batch_size)]))

encod=mk_encod()
newComp=td.Compiler.create((encod,td.Scalar())) #copied the structure of the prev. compiler
fvBlock,_=newComp.output_tensors
FV=sess.run(fvBlock,newComp.build_feed_dict([get_real(i) for i in range(N)]))

However, that gets me:
FailedPreconditionError (see above for traceback): Attempting to use uninitialized value FC_256_2/weights
	 [[Node: FC_256_2/weights/read = Identity[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](FC_256_2/weights)]]

So I guess I'm messing up with the scopes, I think...
Isn't this approach (train a whole net, use the results of a middle layer) somewhat common on NLP ?(isn't word2vec like this?). What would be the canonical way for that?

Expose the output of the middle layer as an output of the model.  td.AllOf
is good for that.
On Fri, Feb 24, 2017 at 10:13 PM, Fábio Dias<EMAIL_ADDRESS>wrote:

So, I tried that approach. Here's the relevant (full) code:
CL=td.ScopedLayer(convLayer)
def mk_encod():
return(td.Map(td.Tensor((24,10)) >>  CL >>
td.Function(lambda x: tf.reshape(x,[-1,64*(10-2)]))) >>
td.Fold(td.Concat() >>
td.Function(td.FC(256)), td.FromTensor(tf.zeros(256))))
model = ( mk_encod()  >>  td.Function(td.FC(1)))
compiler = td.Compiler.create((model, td.Scalar()))
y, y_ = compiler.output_tensors
loss = tf.nn.l2_loss(y - y_)
train = tf.train.AdamOptimizer().minimize(loss)
sess.run(tf.global_variables_initializer())for i in range(1000):
sess.run(train, compiler.build_feed_dict([get_example() for _ in range(batch_size)]))
encod=mk_encod()
newComp=td.Compiler.create((encod,td.Scalar())) #copied the structure of the prev. compiler
fvBlock,_=newComp.output_tensorsFV=sess.run(fvBlock,newComp.build_feed_dict([get_real(i) for i in range(N)]))
However, that gets me:
FailedPreconditionError (see above for traceback): Attempting to use uninitialized value FC_256_2/weights
[[Node: FC_256_2/weights/read = IdentityT=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"]]
So I guess I'm messing up with the scopes, I think...
Isn't this approach (train a whole net, use the results of a middle layer)
somewhat common on NLP ?(isn't word2vec like this?). What would be the
canonical way for that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/fold/issues/16#issuecomment-282463707, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGGbTXsnl7Y_vsNx5WyBnPaZxqw6-3N1ks5rf8Z2gaJpZM4MK4Yb
.

--
DeLesley Hutchins | Software Engineer |<EMAIL_ADDRESS>|<PHONE_NUMBER>

Is my understanding correct that there is (currently) no way to obtain/inspect the output_tensors of a non-root block without compiling a separate instance of the tf graph (for each such block), and then doing separate corresponding executions of sess.run(...), etc.? Since sess.run([tensor1, tensor2,...]) already allows arbitrary/non-root tensors in the tf graph to be specified, it seems like this may be an issue with the td compiler only being able to expose the root-level tensors in the resulting graph. Anyway, having a simple way to inspect non-root tensors would be very helpful for debugging purposes. Thanks for the great resource!

If you drop down to the loom layer, you can expose any part of the
computation as an output.  Within the blocks library, we provide the notion
of "metrics".  A metric is a computation (usually loss, perplexity or some
other measure) that can be attached to the output of any block.  Each
metric has a name that you can use to retrieve it later.  Keep in mind that
non-root blocks may be evaluated multiple times (e.g. the child block of
td.Sequence) or not at all (Optional/OneOf) so when you retrieve a metric
by name, you get a concatenation of all metrics with that name.
On Wed, Mar 1, 2017 at 8:10 PM, Rachel Rudinger<EMAIL_ADDRESS>wrote:

Is my understanding correct that there is (currently) no way to
obtain/inspect the output_tensors of a non-root block without compiling a
separate instance of the tf graph (for each such block), and then doing
separate corresponding executions of sess.run(...), etc.? Since
sess.run([tensor1, tensor2,...]) already allows arbitrary/non-root tensors
in the tf graph to be specified, it seems like this may be an issue with
the td compiler only being able to expose the root-level tensors in the
resulting graph. Anyway, having a simple way to inspect non-root tensors
would be very helpful for debugging purposes. Thanks for the great resource!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/fold/issues/16#issuecomment-283550983, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGGbTRzObJ6zQu8vvivHh4Vbx3a3oMD7ks5rhkEmgaJpZM4MK4Yb
.

--
DeLesley Hutchins | Software Engineer |<EMAIL_ADDRESS>|<PHONE_NUMBER>

Ok, I think I see how one could post-hoc stitch a Metric into the pipeline to inspect values in a non-root block. A simple example of a graph that sums two numbers and doubles them, where we want to inspect the values at the intermediate summing stage:
import tensorflow as tf
sess = tf.InteractiveSession()
import tensorflow_fold as td

inputs = td.Record((td.Scalar(), td.Scalar()))
sum_block = inputs >> td.Function(tf.add)
m = td.Composition()
with m.scope():
    td.Metric('sum').reads(m.input)
    m.output.reads(m.input)
double_block = sum_block >> m >> td.Function(lambda x: 2.0*x)

compiler = td.Compiler.create(double_block)
fd = compiler.build_feed_dict([(1,2),(3,4),(5,6)])
outputs, metrics = sess.run([compiler.output_tensors, compiler.metric_tensors], feed_dict=fd)

I imagine there's a cleaner way to write this, but this at least accomplishes what I want (avoiding multiple compilers). Thanks for the tip!

@rudinger Thanks for the stitch! Do you know if the retrieved outputs can be used for further ops in the tensorflow graph? Will the gradients flow back correctly if this is done?

@satwikkottur Sorry I don't have an answer, I've moved to a different project. Good luck!

The original purpose of metrics was to attach losses to predictions that
are buried deep within non-root blocks, so yes, the gradients will flow
back correctly.
-DeLesley
On Tue, Oct 17, 2017 at 7:06 AM, Satwik Kottur<EMAIL_ADDRESS>wrote:

@rudinger https://github.com/rudinger Thanks for the stitch! Do you
know if the retrieved outputs can be used for further ops in the tensorflow
graph? Will the gradients flow back correctly if this is done?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/fold/issues/16#issuecomment-337242733, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGGbTYF3_ONPf8oGPeiXkEYYmJLGlJq-ks5stLRUgaJpZM4MK4Yb
.

--
DeLesley Hutchins | Software Engineer |<EMAIL_ADDRESS>|<PHONE_NUMBER>

I tried this by dropping down to loom layer. But looks like I can specific the outputs (which are Loom id ints), and they stack up as output. Is there any other way I can get more structured outputs from loom, rather than rearranging them post loom?
For eg., I want [1, 2, 5] outputs together and [3, 4, 6] together. (note that integers here are loom ids)

If you drop down to the loom layer, you can expose any part of the
computation as an output.


[Galley] Fix race in strategy shutdown.

The Close() logic was holding onto the state lock, which can race with worker thread. Specifically, the worker thread could be in a call to onTimer awaiting the lock, which would never be acquired since the Close() method is stuck waiting for the stopped channel to close.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: nmittler
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cbf90827d84a69bd58240564ee17cd379be10cb9
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler, ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS [ozevren]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
024b9015074b9bf75ef0dc6447897b32d723ac6b
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add Zapier

Dear Airflow Maintainers,
The standard submission form seems irrelevant as this is just an incremental update of the list of companies using Airflow.  I've added [Zapier][https://www.zapier.com].  If you are no longer accepting updates to this list I can create an issue and update the Readme to eliminate the call to action.
Best,
Russell

@drknexus We are actively accepting updates to the list of companies. However, I do ask that you follow the contributor guidelines described here.
Though it might seem heavy handed for such a trivial commit, consider it an introduction to contributing. Essentially, please create a JIRA and prefix your commit message (and this PR title) with [AIRFLOW-XXX] and place a link to the JIRA in this PR. Once done, we will happily merge.

Will do. I'll close for now so I can get it all squared away.


F821 triggers when referencing a deleted (in an if) variable in an else/elif

Example reproduction code:
def func(seq, arg):
    if seq:
        del arg
    elif arg:  # false-positive F821
        print(arg)  # false-positive F821
    else:
        print(arg)  # false-positive F821

    print(arg)  # correctly reported F821

Story time
While running into this false-positive, I actually found a different issue so it's net-positive :)
def func(seq, show_this_once):
    if seq:
        for elem in seq:
            print(elem, show_this_once)
            del show_this_once
    elif show_this_once:
        print(show_this_once)

The del in the for loop here was problematic because on second iteration the variable no loner exists. Somehow we never tested it with a sequence longer than one so this went undetected. Note that ruff didn't report this directly, I just found it because of the elif branch I had :) I suppose there could be a rule for reporting this kind of possibly unbound variable issue but it would probably be prone to false positives so I'm not really feature requesting that :smile:

Would be great if early returns were supported as well:
def func(remove, arg1, arg2, arg3):
    if remove & 1:
        del arg1
        return

    print(arg1)

    if remove & 2:
        del arg2
        raise RuntimeError("!!!")

    print(arg2)

    for _ in range(2):
        if remove & 4:
            del arg3
            continue
        print(arg3)

as in, all prints should be considered valid.


address look up pages

@Ella-Welsby I noticed you'd pasted in the "Find your address" content into the "Who can we contact..." by accident so I fixed that and just removed a bit of whitespace around the HTML. Hopefully that weird start page issue is fixed now too,


TFLITE version used by larod 2.2

Issue description
We're developing an application with a custom model  and when the app runs, it gives an error:
Unable to run inference on model /usr/local/packages/XXXXXXXX/model/XXXXXXXXX.tflite: Asynchronous connection has been closed (-6)
We suspect that this error is because of an unsupported layer in TF Lite. Can you please, inform us which version of  TF Lite, larod is using ?
System setup

AXIS product/device : Q1798-LE
Device firmware version : 10.6
SDK version :  ACAP SDK 3.4

Logs
Unable to run inference on model /usr/local/packages/XXXXXXXX/model/XXXXXXXXX.tflite: Asynchronous connection has been closed (-6)

Larod in firmware 10.6 is using TF lite version 2.3.1
Please find more information on how to use larod here.


Figure out how to run vulkan on various virtualbox and VNC setups; also see about wasm 2D bitmap-only strategy.

It would be useful to be able to run in virtual machines and remote desktops.
Vulkan in software may be getting better in various forms (mesa, some other thing that android or ios uses in its simulator).
Alternatively, the 2D framework is now working well using non-vulkan impl of drawer interface -- could reasonably support 2D only using a much simpler API that only uses this bitmap-based interface, running on some kind of really basic glfw window interface (not even opengl).  That would be worth it for allowing majority of apps to run in VMs etc.
See #483 for example where it doesn't work.

It has worked fine on VNC in my experience.

Also, it would be nice if I could support termux, I used termux for a long time before buying a tablet, it was as smooth as Windows xp, using the xfce interface

At some point, we will implement WebGPU support (#507), which may remove the need for adding a backup 2D vulkan-free driver. Even if we do still need to implement a separate compatibility driver, doing so will not be especially quick, and we have limited time before our initial release. Therefore, we will work on resolving this later, as everything works properly on the vast majority of devices already.


tasks.schema.json - Is it complete?

Looking at the VSTS Tasks repository I can see that task.json file for many tasks contains something like
{
    "visibility": [
		"Build",
		"Release"
	],
}

This property is not listed in the tasks.schema.json is this correct?
I have also encountered an additional version property isTest, I think it was in the VSTS REST API documentation that I first encountered came across the property.
{
    "version":  {
                    "Major":  0,
                    "Minor":  1,
                    "Patch":  0,
                    "isTest":  true
                },
}

Setting isTest to true appears to:

Show the version number in VSTS as something like  0.*-test
Allow a release definition to automatically pick the newest version of the task when a new release is created.  I believe that when isTest is not specified then the exact major, minor, patch of the task will be used that was selected when the task was added in to the release definition.  (I assume a similar thing happens with build definitions).  Or perhaps it has something to do with forcing the VSTS Agent to downloading new versions of cached tasks??

Some clarification would be helpful.

They were intentionally left out because they are not supported / honored completely.  There's a task to go remove it from our tasks.  Sorry for the confusion.

Looks like the isTest property was removed. Visibility is still around, but since its being tracked I'm going to close here. Feel free to reopen as appropriate.


Policy Maker issue 1

Not having the right data to answer the desired questions.

Information found and housed on JobHopper Miro board.


Added NLP examples to flask app.

FileNotFoundError when click 'Capture Mosul' and 'New_NLP_sample' for 'NLP'
error: FileNotFoundError: [Errno 2] No such file or directory: 'out/nlp/tmp6atcwdv7.png'


Integrating Base/Module Classes with Codebase

This pull request aims to merge the various classes, as well as the state machine code to master.
Currently to-do with this iteration of the code:
-Supply actual parameter values to StateMachine. If there is a need for functions to model bamocar input, please supply them.
-Perform Unit testing of FlexCAN message FIFO setup to ensure that:
a) The code stops reading messages when there are no messages left to be read (motor_controller/main.cpp)
b) The FIFO buffer has been set up correctly, such that it can store messages until they can be read
-Perform Unit testing of BamocarInterface to ensure that unit conversions have been correctly supplied
-Unit Test StateMachine position tracking. StateMachine should stop the run after 100m. This relies on a successful nav module.
-Move the MessageMaster and prebuilt classes/headers to a better location
-Change the name of motor_controller to something better (state_machine?)
-Take a look at the test projects under 'Testing'. These were used for testing whether sensors/CANbus nodes had been successfully set up.

Do you guys mind taking a look at the motor_controller folder?
@OkTerrific you might want to look at the MessageMaster class


Fix style/naming issues

There are several style/naming issues in the v0.1 release that I would like to fix.  It necessitates breaking some backwards compatibility, e.g. changing write_rds() to writeRDS(), etc.
@darthhater, @bhamail - let me know if this would be a pain, I could do a deprecation period if necessary.

I uploaded a 0.2-SNAPSHOT with (some of?) these changes.

None of this is deal breakers for us (we've yet to use it). Suggestion would be to create new method signatures with your preferred name, and just call the old ones, and mark those as @Deprecated


Newly created files are not committed

Description
Newly generated files are not committed because the command git diff --shortstat CHANGELOG.md | wc -l does not count untracked files.
Current behavior
Newly created files are not committed.
Expected behavior
Even newly created files are committed.

Would it be possible to use git status -u?

The git status -u command doesn't work properly. It seems like git ls-files CHANGELOG.md --exclude-standard --others is the way to go.


docs: Add a short explanation of conventional commits in the contributing.md file

Description
Add a short explanation of conventional commits in the contributing.md file
Fixes #85
Type of change
Please delete options that are not relevant.

[X] Docs

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] My changes generate no new warnings
[X] Existing unit test passes locally with my changes

Thanks for your contribution @choubari


Add sponsor to readme

Pull Request Test Coverage Report for Build 272

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.004%

Totals

Change from base Build 270:
0.0%

Covered Lines:
2210

Relevant Lines:
2255

💛  - Coveralls


Allow silencing of threads

Threads (& forum posts) can now be locked without the need to close them. This behaviour is exactly what we want for silencing a thread, and mods can still type in the threads without causing them to be unlocked.
We should update the Silence cog to allow for threads to be both silenced and unsilenced.

This look like a good issue to tackle, can i work on it ?

Sure, I've assigned you!

@MedAliMarz Hi, did you make any progress on this?

Hi, i woud like to work on this


Launching the app from icon when no window is open

Check for existing issues

[X] Completed

Is your feature request related to a problem?
No.
Describe the solution you'd like
On Mac, when no window of an application is open, the app can still run on background. For a better user experience, clicking the app icon should open a new window if no other window is open. Currently, nothing happens when you click the icon.
If applicable, add mockups / screenshots to help present your vision of the feature
No response

This is a cool suggestion, thanks @kilicbaran

I find myself clicking the icon expecting the same!

This is now implemented.


bug: Resolve "Windows Firewall has blocked cortex.cpp"

When we run Cortex for the first time, i.e. cortex run ..., a firewall warning "Windows firewall has blocked cortex.cpp" comes up. Anyway around this?
Related issue #627

Hi @0xSage, may I know which cortex version are you running?

it was the version as of July 26th

Thanks for your information. I will try to reproduce and fix the issue soon.

@0xSage did you got this warning after running the setup.exe file on windows? https://github.com/janhq/cortex/issues/799

@hiento09 Let's create a new issue for installers. I think the mentioned issue is with the npm installation

@0xSage are you running tensorrt-llm model? there is a known issue related to MPI server


python311Packages.fastembed: unstable-2023-09-07 -> 0.1.1

Diff: https://github.com/qdrant/fastembed/compare/9c5d32f271dfe9ae4730694727ff5df480983942...0.1.1
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 261576 run on x86_64-linux 1

4 packages built:

python310Packages.fastembed
python310Packages.fastembed.dist
python311Packages.fastembed
python311Packages.fastembed.dist


Update launcher plugin with recent changes to proto files

Overview
Update after #1190

See: https://jira.bf.local/browse/ECR-XYZ
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 86.064% when pulling 47da542b42655c143e8ef10a735b6e38244c44c4 on vitvakatu:update-launcher-plugin into 9d95923f5f841bf0d62da3d69b8d48337d34558d on exonum:dynamic-services.


Hosting

Hi I'm learning to make a project like this but having a hard time at running it what's the best way to host a website as iv tried like netifly but it won't get the likes of the login system I have I'm assuming netifly won't use all directorys of the repo

Hello!
Musicale is actually a static website, which means the server only needs to serve the content, without any computation.
That said, before hosting you should build the project using Node.js running all these steps (excluding running "DEV mode" and preview).
After this, you will find the production-ready build inside dist/public, which you can host anywhere.
Anyway, as you talked about Netlify, you can use Netlify Drop and upload the folder there. It will handle for you all the steps to serve you the app.

Thanks mate I'm testing out on maybe helping u a little I'm new and learning the ropes haha have you got a discord sever as it says the sever link has expired 😁

Thanks for letting me know, I just updated the Discord link!

No worries can I have permissions to sort the discord sever out a little please dude


Adding example TypeSpec definition for CLU

@heaths

Could you make the PR title something descriptive, like "Adding example TypeSpec definition for CLU" or something like that? It helps to track down changes later.

While you're at it, could you also add me to the root CODEOWNERS file? Something like:
/specification/cognitiveservices/Language.Conversations/ @kristapratico @heaths

While you're at it, could you also add me to the root CODEOWNERS file? Something like:
/specification/cognitiveservices/Language.Conversations/ @kristapratico @heaths

I just added this line.


Support AVC depacketizer breaks pion/webrtc

related to PR:
https://github.com/pion/rtp/pull/110
@debiandebiandebian There is an issue with this PR will break pion/webrtc h264writer_test.go
The reason is because the writer uses:
	data, err := (&codecs.H264Packet{}).Unmarshal(packet.Payload)

Basically, it creates a H264Packet object on the fly to unmarshal to... but the unit test first writes the h264 FUA START, then an H264 FU END packet, but the first packet unmarshal returns data array with 0 content, the second only returns the END data but not the contents in fuaBuffer because it's been discarded between the previous write.
I'm uncertain the expected fix. I think the H264 packet object be reused in the webrtc h264 writer until the close is called to ensure any buffering in the fuaBuffer is preserved, but I worry about the side effects.
cc: @Sean-Der

@debiandebiandebian if you can confirm that webrtc writer needs to be fixed as described above then I'll submit a patch to webrtc with that fix.

I think the fix is this:
https://github.com/pion/webrtc/pull/1801/files
Only changes in this file are related to this issue:
pkg/media/h264writer/h264writer.go

@robin-raymond You're right. My PR would break this case. Re-using a H264Packet is necessary.

Thank you! I'll leave this issue open until the pion/webrtc fix is merged. Then I will close this issue.

This is an off-topic, but can you educate me where h264writer is actually used? I can't find any in pion/webrtc.

I'm uncertain. I just wanted the unit tests to pass to fix other webrtc issues. I am guessing it's in pion/ion-avp or pion/ion-sfu?

Thanks for your time. I should have checked other dependencies before merging this PR. =/


[Camel 3.19.0] Kubernetes: tests + native has to be disabled until Quarkus 2.14

See more details in https://github.com/apache/camel-quarkus/issues/4083
The problem is caused by the fact that camel 3.19 upgraded kubernetes-client to 6.x and Quarkus 2.13 uses kubernetes-client 5.x
Clients 5.x and 6.x are not compatible. Quarkus 2.13 will stay on 5.x until Quarkus 2.14.
Once problem is gone, enable native build and enable the tests in the kubernetes tests extension.

The same problem is with master-opensshift/.../MasterOpenShiftTest#testFailover

Closing as it's out of date now.


Resource Buildings / Management

Description

Team 5 have decided to team up with #10 in Sprint one, working on Buildings but more specifically, Resource related buildings to be implemented in our Atlantis Sinks game. To begin with, we will probably only implement one form of resource (i.e. stone) within Sprint 1 and implement more later on.

This will entail us designing a ‘mine’ or alternatively if we don’t want to take up space, ‘tools’ that the playable character can use. Regarding programming, we will be implementing various classes to function these mines / tools and a value store as to how much they’ve collected and potentially in the future work with #4 on costing of items from the shop.

Alternately, because this isn’t a time-based game, we can't have mines that work on real time but instead might have to function like the banana farms in Bloons TD where they pay off after each round. More of an investment for the late game player.

Another idea, could be the player chooses to mine a specific square of their grid and that square becomes unusable until the next round etc.

Similarly, to buildings, at the beginning the player will be given the option to place ‘mines’ down in the squares at the beginning of the round before the attack begins.

(Need to discuss with the studio about gameplay and how they want this to work)
SubFeature/component
Resource Management

Currency system: allow player to buy, sell and trade buildings/tools/equipment
Health system: allow player to view the health status
Ammunition system: allow player to manage weapons/tools/equipment

Resource Buildings
Examples

Resource collecting buildings (e.g. gold mines)
Roads of all shapes. The roads are filled with soil of various colours and textures that players can pick up at will.
Stone. Building materials for the player
Wood. Player need find them to create the buildings

Dependencies

Base code for buildings can be built upon for the resource buildings (i.e. resource buildings are a subclass of building #10)
The player will need a UI that displays the resources they have available
The currency/resources will be used with the shop to purchase items
The playable character (main character #xx) will be required to use the tool system

Milestones
List of sub-features you intend to have done and in Master by the end of the sprint.

[ ] Goal 1 (Aug. 20)
Planning

Coordinate base building code with Team 7 (buildings)
Coordinate currency implementation with Team 6 (shop)
Find out what the main character can do with Team 2 (main character)

Design

Begin design of resource(s)
Outlines and designs confirmed
Make wireframes / prototypes

Programming

Base currency classes implemented
Resource building base class (inherits base building class #10)

[ ] Goal 2 (Aug. 23)
Planning

Discuss with Team 7 _____
Meet with other teams

Design

Prototypes for [everything] finalised
Functionality of the currency system
What the resources buildings can do decided

Programming

Begin implementing resource building functionality
Test that base classes work

[ ] Goal 3 (Aug. 26)
Design

Wiki documentation

Programming

All functionality completed for currency system and resource buildings

[ ] Goal 4 (Aug. 28)

Sprint Achievement Form completed

Final testing of all code

Completion Deadline: Aug. 30
Extras

[ ] Expand single currency to multiple different currencies
[ ] Building upgrades (ammunition, mining rates etc.)
[ ] Game points system

Documentation

Main description of feature
User documentation
...

Members

Luke Graham (@luke4641942) (Luke Graham)
Cliff Worsfold (@JumpOffACliffy) (Cliff Worsfold)
Suki Zhang (@sukizzz) (Suki Zhang)
Xi Wang (@XiWangBeryl) (Xi Wang)
Naman Argwal (@Naman-Agarwal1608) (Naman Argwal)

Hey Team 5, just clarifying a few things from our studio this morning to ensure that we are all on the same page throughout sprint 1. For this sprint, we will create a shop interface that uses a currency system to purchase items within the shop interface, the items being artefacts, weapons etc. which will be purchased with 'gold'. As we spoke about this morning, you guys will create buildings that 'produce' resources (ie. gold mine, stone mine etc.) which the player can purchase from the shops and use these resources (stone, wood etc.) to purchase buildlings. In this sprint, we will be implementing a shop that deals only in gold with only 1 item available to purchase so that we can ensure the basic functionality is correct before integrating with other teams - let me know if you have any questions or if any of the above isn't correct!

Hi, there team 5, just leaving a comment on behalf of the UI team to confirm that a currency count and stone count will be added to the UI. After the week 4 studio, teams 5 and 6 agreed to implement 2 types of currency in the game. Thus, count tracking of the available resources will be implemented next to or integrated with the illustrations of stones and coins respectively (TBC).

hey team 5! just dropped a comment on here to confirm that we have used your resource building images to inspire the icons we have designed for them for the shop feature as below. Any questions let me know!


CMS6: Default to utf8mb4

Description
A while back, we put some effort in making easy to set up up your database to store Emojis and fanciful characters in your DB fields. However, we didn't want to force people to upgrade their project to the 4-bit UTF8 charset ... because breaking change.
We did add a better config in recipe-cms so people creating brand new projects would get the 4-bit charset.
However, we forgot to update the default charset and collation in CMS 5 ... so people still have to keep that snippet in their YML config if they want to use 4-bit UTF8 char.
We should update CMS 6 to use 4-bit UTF8 char out of the box.
Additional context or points of discussion
This bit should be removed in CMS 6: https://github.com/silverstripe/recipe-core/blob/5/app/_config/mysite.yml#L7-L16
Instead the matching config values should be set directly in MySQLDatabase:
https://github.com/silverstripe/silverstripe-framework/blob/5/src/ORM/Connect/MySQLDatabase.php#L28-L76
Validations

[X] You intend to implement the feature yourself
[X] You have read the contributing guide
[X] You strongly believe this feature should be in core, rather than being its own community module
[X] You have checked for existing issues or pull requests related to this feature (and didn't find any)

Makes sense to me

@maxime-rainville Are you still interested in doing this?

Sorry ... got busy with life, StripeCon presentation and screaming at AWS over the last two months. Just got a bunch of PR for this one.

PRs merged. Thanks for taking care of that


reliability: Determine and document SLOs for the agent

cc @metalmatze

In my mind, the most important thing is that Parca Agent can unwind stacks successfully and attempts to send profiling data (note that I intentionally don't say that it succeeds because that is outside of its responsibility).
Being able to measure this is most important, setting goals is good, but understanding it is most important I think and we can then use the current state to set goals to improve.


[CI] add license checker

Description
add license checker
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)

Changes

[x] add license checker to CI

Job PR-804/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-804/1/index.html

Job PR-804/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-804/2/index.html

Job PR-804/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-804/3/index.html

Job PR-804/4 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-804/4/index.html

Job PR-804/5 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-804/5/index.html

Job PR-804/6 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-804/6/index.html


Bug: when navigating up to the previous folder, the page will flash at the top position and then jump to the previous position

Description
when navigating up to the previous folder, the page will flash at the top position and then jump to the previous position
Steps To Reproduce

open [scroll to previous folder when navigating up] in settings.
open a folder which has a lot of folders.
Open any folder other than the first one.
navigating up to the previous level folder.

Requirements
when navigating up, the page should be straightly at the previous position.
Files Version
<IP_ADDRESS>
Windows Version
Windows11 22631.3155
Log File
debug.log

Thank you for your feedback, this is more of a performance issue as we can only scroll to the correct position after the items are loaded. Our goal is to get to a point where it's barely noticeable but in the meantime, you can track our progress in #4180.


[UI Design] Creation of virtual Roles (aka "Packs")

Task
[UI Design] Creation of virtual Roles

Task Title
[UI Design] Creation of virtual Roles

User Story
link associated User Story for this task

Epic
#529

T-shirt size default is S(mall)
S

Story Points - Fibonacci (1,2,3,5)
3

Description
Define workflow & mock-ups for Creation of virtual Roles use cases

Business Need (the why):

Applications or Systems impacted

Dependencies

Assumptions
if any

the UI design of packs seems to be done.


custom channel connector docs improvements

Proposed changes:

Restructure the custom connector docs page to clarify how it should be implemented and referred to
closes https://github.com/RasaHQ/rasa/issues/6626

Status (please check what you already did):

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

@erohmensing The description of calling on_new_message is still very confusing (to me). Where is on_new_message handled? I can't find it defined anywhere in the codebase, it seems to just get called by all the blueprint methods.

@erohmensing have you had a chance to look at this yet?

@erohmensing have you had a chance to look at this yet?

I'm pretty sure this is where it is sent: https://github.com/RasaHQ/rasa/blob/main/rasa/core/agent.py#L511
When we define the blueprint, we give it a handler, which is a callable method that can handle the incoming requests (so in this case on_new_message is the handler).
Then when we register the channels when loading up the server, we tell it that the handler method is going to refer specifically to rasa.core.agent.handle_message here: https://github.com/RasaHQ/rasa/blob/main/rasa/core/channels/channel.py#L85
At least that's how i understand it. I think it'll be clearer in the docs if we just explain that calling on_new_message will send that to handle_message

I'm pretty sure this is where it is sent: https://github.com/RasaHQ/rasa/blob/main/rasa/core/agent.py#L511
When we define the blueprint, we give it a handler, which is a callable method that can handle the incoming requests (so in this case on_new_message is the handler).
Then when we register the channels when loading up the server, we tell it that the handler method is going to refer specifically to rasa.core.agent.handle_message here: https://github.com/RasaHQ/rasa/blob/main/rasa/core/channels/channel.py#L85
At least that's how i understand it. I think it'll be clearer in the docs if we just explain that calling on_new_message will send that to handle_message

@melindaloubser1 Please merge to main or 2.3.x instead of 2.2.x. I'll release 2.3.0 today.

Ah shoot forgot this was still open


NTR: Casparian strip organization

Please provide as much information as you can:

Suggested term label:

Casparian strip organization

Definition (free text)

A process that results in the assembly, arrangement of constituent parts, or disassembly of the Casparian strip, the region of plant cell wall specialised to act as a seal to prevent back leakage of secreted material (analogous to tight junction between epithelial cells). Found particularly where root parenchymal cells secrete solutes into xylem vessels.

Reference, in format PMID:#######
PMID:28104889

Gene product name and ID to be annotated to this term
Q84MD2
O65684

Parent term(s)
GO:0009664 plant-type cell wall organization

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

@Antonialock
Why not 'Casparian strip assembly'? (I imagine the assembly and disassembly pathways to be very different, not sure if the latter exists).
In this case parents would be

is_a GO:0022607 cellular component assembly
part_of GO:0071668 plant-type cell wall assembly

Thanks, Pascale

I meant to say that I had never heard of these structures until yesterday (so yes, feel free to make suggestions!)
The referenced paper suggested that there can be some development to casparian strips later in the plant's life if adverse soil conditions require it (contrary to old thinking that the strip forms and that's it) which made me think "rearrangement of parts" - but perhaps it is more like "reinforcement" which isn't really a dynamic restructuring.
Assembly is probably fine?

Let's ask @tberardini to comment

Could we use 'Casparian strip formation' as that is the string that is more commonly used (vs. Casparian strip assembly). If it's cleaner to use assembly as the primary term name, that should be ok, if you can add formation as a synonym.

+[Term]
+id: GO:0160073
+name: Casparian strip assembly
+namespace: biological_process
+def: "The aggregation, arrangement and bonding together of a set of components to form a Casparian strip, a region of plant cell wall specialised to act as a seal to prevent back leakage of secreted material." [PMID:28104889]
+synonym: "Casparian strip formation" EXACT []
+intersection_of: GO:0022607 ! cellular component assembly
+intersection_of: results_in_assembly_of GO:0048226 ! Casparian strip
+relationship: part_of GO:0071668 ! plant-type cell wall assembly
+created_by: rynl
+creation_date: 2023-01-10T00:56:06Z


no sensor created - sensor.telenet_telemeter_internet - Error doing job: Task exception was never retrieved

Good afternoon
I just added the integration via HACS.
Both internet and mobile are checked in the configuration. The connection was successful. However, no sensor is created "sensor.telenet_telemeter_internet_".
I get the following information in the log files:
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
   File "/config/custom_components/telenet_telemeter/sensor.py", line 118, in async_setup_entry
     await dry_setup(hass, config, async_add_devices)
   File "/config/custom_components/telenet_telemeter/sensor.py", line 51, in dry_setup
     await data_internet._forced_update()
   File "/config/custom_components/telenet_telemeter/sensor.py", line 153, in _forced_update
     await self._hass.async_add_executor_job(lambda: self._session.login(self._username, self._password))
   File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
     result = self.fn(*self.args, **self.kwargs)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/config/custom_components/telenet_telemeter/sensor.py", line 153, in <lambda>
     await self._hass.async_add_executor_job(lambda: self._session.login(self._username, self._password))
                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^
   File "/config/custom_components/telenet_telemeter/utils.py", line 97, in login
     self.callTelenet("https://api.prd.telenet.be/ocapi/oauth/userdetails","login")
   File "/config/custom_components/telenet_telemeter/utils.py", line 80, in callTelenet
     assert response.status_code == expectedStatusCode
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError

Thanks in advance!

Hi, this seems to be caused by a wrong username and/or password set in the Telenet Telemeter addon. Or maybe some very special characters are used in the password which are might not be well supported. could you try to remove the device and add again and if still issues set a new password via the Telenet website. Please also make sure to upgrade to the latest version of this integration (1.5.4) and reboot HA before adding the device.

Thank you! After changing the password, I got everything as expected.
Remarkable: I had to change the password via 'forgotten password'. Changing after logging in to my telenet was not possible. Unprecedented error.
Problem solved now. Thank you!


Vulnerabilities found after using npx create-react-app

npm audit report
browserslist  4.0.0 - 4.16.4
Severity: moderate
Regular Expression Denial of Service - https://npmjs.com/advisories/1747
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/react-dev-utils/node_modules/browserslist
react-dev-utils  >=6.0.0-next.03604a46
Depends on vulnerable versions of browserslist
node_modules/react-dev-utils
react-scripts  >=0.10.0-alpha.328cb32e
Depends on vulnerable versions of @pmmmwh/react-refresh-webpack-plugin
Depends on vulnerable versions of @svgr/webpack
Depends on vulnerable versions of mini-css-extract-plugin
Depends on vulnerable versions of react-dev-utils
Depends on vulnerable versions of webpack-dev-server
node_modules/react-scripts
css-what  <5.0.1
Severity: high
Denial of Service - https://npmjs.com/advisories/1754
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/svgo/node_modules/css-what
css-select  <=3.1.2
Depends on vulnerable versions of css-what
node_modules/svgo/node_modules/css-select
svgo  >=1.0.0
Depends on vulnerable versions of css-select
node_modules/svgo
@svgr/plugin-svgo  *
Depends on vulnerable versions of svgo
node_modules/@svgr/plugin-svgo
@svgr/webpack  >=4.0.0
Depends on vulnerable versions of @svgr/plugin-svgo
node_modules/@svgr/webpack
react-scripts  >=0.10.0-alpha.328cb32e
Depends on vulnerable versions of @pmmmwh/react-refresh-webpack-plugin
Depends on vulnerable versions of @svgr/webpack
Depends on vulnerable versions of mini-css-extract-plugin
Depends on vulnerable versions of react-dev-utils
Depends on vulnerable versions of webpack-dev-server
node_modules/react-scripts
postcss-svgo  >=4.0.0-nightly.2020.1.9
Depends on vulnerable versions of svgo
node_modules/postcss-svgo
cssnano-preset-default  *
Depends on vulnerable versions of postcss-normalize-url
Depends on vulnerable versions of postcss-svgo
node_modules/cssnano-preset-default
cssnano  4.0.0-nightly.2020.1.9 - 4.1.11
Depends on vulnerable versions of cssnano-preset-default
node_modules/cssnano
optimize-css-assets-webpack-plugin  3.2.1 || 5.0.0 - 5.0.6
Depends on vulnerable versions of cssnano
node_modules/optimize-css-assets-webpack-plugin
glob-parent  <5.1.2
Severity: moderate
Regular expression denial of service - https://npmjs.com/advisories/1751
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/watchpack-chokidar2/node_modules/glob-parent
node_modules/webpack-dev-server/node_modules/glob-parent
chokidar  1.0.0-rc1 - 2.1.8
Depends on vulnerable versions of glob-parent
node_modules/watchpack-chokidar2/node_modules/chokidar
node_modules/webpack-dev-server/node_modules/chokidar
watchpack-chokidar2  *
Depends on vulnerable versions of chokidar
node_modules/watchpack-chokidar2
watchpack  1.7.2 - 1.7.5
Depends on vulnerable versions of watchpack-chokidar2
node_modules/watchpack
webpack  4.44.0 - 4.46.0
Depends on vulnerable versions of watchpack
node_modules/webpack
webpack-dev-server  2.0.0-beta - 3.11.2
Depends on vulnerable versions of chokidar
node_modules/webpack-dev-server
@pmmmwh/react-refresh-webpack-plugin  0.3.1 - 0.5.0-beta.4
Depends on vulnerable versions of webpack-dev-server
node_modules/@pmmmwh/react-refresh-webpack-plugin
react-scripts  >=0.10.0-alpha.328cb32e
Depends on vulnerable versions of @pmmmwh/react-refresh-webpack-plugin
Depends on vulnerable versions of @svgr/webpack
Depends on vulnerable versions of mini-css-extract-plugin
Depends on vulnerable versions of react-dev-utils
Depends on vulnerable versions of webpack-dev-server
node_modules/react-scripts
normalize-url  <=4.5.0 || 5.0.0 - 5.3.0 || 6.0.0
Severity: high
Regular Expression Denial of Service - https://npmjs.com/advisories/1755
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/normalize-url
node_modules/postcss-normalize-url/node_modules/normalize-url
mini-css-extract-plugin  0.6.0 - 1.0.0
Depends on vulnerable versions of normalize-url
node_modules/mini-css-extract-plugin
react-scripts  >=0.10.0-alpha.328cb32e
Depends on vulnerable versions of @pmmmwh/react-refresh-webpack-plugin
Depends on vulnerable versions of @svgr/webpack
Depends on vulnerable versions of mini-css-extract-plugin
Depends on vulnerable versions of react-dev-utils
Depends on vulnerable versions of webpack-dev-server
node_modules/react-scripts
postcss-normalize-url  <=4.0.1
Depends on vulnerable versions of normalize-url
node_modules/postcss-normalize-url
cssnano-preset-default  *
Depends on vulnerable versions of postcss-normalize-url
Depends on vulnerable versions of postcss-svgo
node_modules/cssnano-preset-default
cssnano  4.0.0-nightly.2020.1.9 - 4.1.11
Depends on vulnerable versions of cssnano-preset-default
node_modules/cssnano
optimize-css-assets-webpack-plugin  3.2.1 || 5.0.0 - 5.0.6
Depends on vulnerable versions of cssnano
node_modules/optimize-css-assets-webpack-plugin
22 vulnerabilities (9 moderate, 13 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force

Same issue here.
22 vulnerabilities (9 moderate, 13 high)

Here another with the same issue 🙋♂
Using Node 16 with npm 7

Exactly the same

Same issue

Also same issue. Using latest LTS Node

Same issue here

Same here

Same issue here too

same

Same issue here. There are only 87 of vulnerabilities reported :D

7 vulnerabilities, of which 4 high: 2 each in script packages css-what and normalize-url
node 14.13.0
npm 6.14.8

Same issue here too

Same here...

same here

These vulnerabilities have been around for a long time. Is there any plan to fix them??

I manually upgraded all the dependencies in the package.json to latest, and it's still reporting 22 vulnerabilities (9 moderate, 13 high). I suspect the react-scripts package is at fault, depending on several outdated packages - are there any plans to upgrade them upstream to more modern versions? Not even npm audit fix --force is working on my side.

Same here, originally had 19 vulnerabilities (9 moderate, 10 high). Then used npm audit fix --force, and received 44 vulnerabilities (25 low, 8 moderate, 11 high).

Same here, initially had 19 vulnerabilities (9 moderate, 10 high). Then used npm audit fix --force, and got 44 vulnerabilities (25 low, 8 moderate, 11 high).

I don't think that npm audit fix --force is the right way to solve it. Since there is no newer version of react-scripts yet, the --force flag will downgrade your react-scripts package version to 1.x.x instead of 4.x.x which is a bad breaking change

Same here, 19 vulnerabilities (9 moderate, 10 high).

These warnings are false positives. There are no actual vulnerabilities affecting your app here. To remove npm audit warnings, move react-scripts from dependencies to devDependencies in your package.json.
I agree with the point in https://github.com/facebook/create-react-app/issues/11102 and will make this change so that new projects don't keep having these false positive warnings.

Please see https://github.com/facebook/create-react-app/issues/11174.


Write a GO program to calculate compound interest

Description
Write a GO program to calculate compound interest
Compound interest = principal amount * (1 + rate of interest) ^ time
Principal : 1000
Rate      : 10
Time      : 5

Compound interest : 1610.51

How to contribute

Save the solution in calculate_compound_interest.go file
Add calculate_compound_interest.go file in calculate-compound-interest folder

!assign

Hey @Chirag8023,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)


We should put a bit of order in the development process

@fadils @Meisolsson @hzsweers @mustafa01ali
Hi guys, I've been on vacations for a few weeks now, so I haven't been able to contribute (I'll get back to it soon), but I've been following the development process and running the latest master on my phone, and I haven't updated the ForkHub app because I've found too many bugs and inconsistencies.
I know the development is going really fast and it's impossible to add no bugs, but we could minimize them. So please test harder the PRs before merging, I'll help with this as soon as I can.
I've also noticed that the git history is quite messy and it's hard for me to revise the commits. Please try to rebase your branches before merging.
We'll have a really awesome app in next to no time, thank you all for your contributions.

Ah, this is a very good point.
We need to decide about this. Whether we want to merge fast, and fix later when there is a problem. Or we want to make sure first (put a thorough check on the PR, create a unit test where applicable, etc) before merging it to the master.
Several things to put in mind though. First, none of us is maintaining this repo full-time. Second, the urgency to progress this project is pretty dire. And how to keep contributors contributing.

A good thing would be to add a checklist for PR's. So we who are new to the whole Git thing do it right from the start

Separate question, but could you guys give us a little big of background on what the situation is with you guys, GitHub, and ForkHub? It seems strange to me that a collaborator for this repo is still maintaining a separate fork, and I can't actually tell if anyone here works for GitHub.

@fadils the development is moving really fast, and I'm very happy to see the app active again, I want to keep it that way. But, as long as the feedback is quick, I don't think discussing and testing the PRs harder will push back contributions, and I'll be back soon to help in this.
Everyone wants their patches to be great, lets help them do it by pointing out the possible improvements.
@hzsweers we don't work for GitHub, I have a full-time job at another company and just contribute on my spare time, just like everyone else.
I created ForkHub because the official app was unmaintained and had several bugs that made it unusable and I like GitHub to much for not being able to use it on my phone :laughing:
We don't have access to GitHub's Play Store account, so I'll keep updating ForkHub at least until a new version of the official app is uploaded. I think that having an app in the Play Store (even if it's not the official one) will also attract contributors, but I wont upload version that aren't stable enough for daily use.
So, lets make an awesome app :+1:

Does @fadils work for GitHub?
On Thu, Jan 15, 2015 at 4:30 PM Jon Ander Peñalba<EMAIL_ADDRESS>wrote:

@fadils https://github.com/fadils the development is moving really
fast, and I'm very happy to see the app active again, I want to keep it
that way. But, as long as the feedback is quick, I don't think discussing
and testing the PRs harder will push back contributions, and I'll be back
soon to help in this.
Everyone wants their patches to be great, lets help them do it by pointing
out the possible improvements.
@hzsweers https://github.com/hzsweers we don't work for GitHub, I have
a full-time job at another company and just contribute on my spare time,
just like everyone else.
I created ForkHub because the official app was unmaintained and had
several bugs that made it unusable and I like GitHub to much for not being
able to use it on my phone [image: :laughing:]
We don't have access to GitHub's Play Store account, so I'll keep updating
ForkHub at least until a new version of the official app is uploaded. I
think that having an app in the Play Store (even if it's not the official
one) will also attract contributors, but I wont upload version that aren't
stable enough for daily use.
So, lets make an awesome app [image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/github/android/issues/682#issuecomment-70189350.

@hzsweers I wish I worked at GitHub. =)
I think we can tell @kevinsawicki to update the app on the Play Store.
I mean, it's quite a progress compared to Play Store's version.

It feels kind of weird that GitHub isn't actually leading the effort to improve their app. I'm all for open source work and contributions, but they should be the ones organizing this. Have you guys been in touch at least regarding the work over the past few weeks?

I'm in touch with Kevin. Will update you once I receive his response.

Any response?

I'm in touch with Kevin. Will update you once I receive his response.

I'll respond directly here instead.
After thinking about this for the last couple days, I think it makes sense to move this repository from the GitHub org to somewhere else and remove the original app from the Play store.
No one at GitHub is currently working on this app or planning to work on it in the future. People are instead working on mobile web views for the site.
If people want, I would be happy to transfer the repository to a new organization so all the issues are preserved.
I'm sorry I haven't properly maintained this app but it has been great seeing renewed interest in it. I just don't think it makes sense to keep it under the GitHub organization if we aren't prepared to maintain it properly and publish it regularly.

If this detaches as an official GitHub app, we forfeit being able to use any logos or even the word "GitHub" in the name due to the Play Store's strict policies.
IMO it would be best to keep this as an official project if at all possible. Is there any way we could have someone liaison with you about development and let you know when we should update the store build?

The man @kevinsawicki has spoken.
First, there is nothing to feel sorry about. You started everything from scratch and it's full of awesomeness.
But sometimes, somethings are getting more interesting and people just choose to go with it.
In all honesty, we all thank you for this repo.
Continuing, we need to look this issue two ways.

The importance of the word "GitHub" goes with this repo. I can always fork this repo, add whatever I want, and upload it in the playstore. But people will still search and use the official app.
Heck, even when we're looking at some issues reported, it still references to the official app although @jonanp has in several places mentioned about ForkHub, which is less bugs, and more-improved cloned version.

We also need to respect @kevinsawicki responsibilities and personal interest.

All we need is a little persuasion. Is there anything we can do to minimize the interruption to your work @kevinsawicki ? I mean perhaps a simple once-a-month update?
This is an awesome app. Lots of good codes in it. Many people are being helped by it.
And I'm just afraid that once it loses its GitHub association, then everything will stall.

As an outsider to this situation, I feel my perspective might need to be shared.
I, and no doubt the vast majority of users with the app named "GitHub" installed on their phones, thought this was an official project. It makes sense, after all, for GitHub to make it as easy as possible for us users to use their service from our mobile devices. But the app published in the Play Store is essentially unusable. It hasn't been updated in 11 months. GitHub looks bad for that.
From where I sit, it would be a poor choice to remove the official app from the store or from the GitHub org. Might come across as GitHub the company saying, more or less, "we don't care about Android, you guys should just use a browser".
If the original maintainer isn't willing to upload an updated build every few weeks, then the app listed on Google Play should be transferred to someone willing to maintain it. Not abandoned—revived. Lead by example and show us that community development can support an official offering.

@dgw I'm not sure which side you're a proponent of. On one hand you seem to suggest that it should remain an official GitHub client, but then you also suggest that it should be turned over to someone else/another group. Could you clarify?

@hzsweers The main goal is to get the official app updated. In order to use GitHub logos and names, the app has to be official, doesn't it? Ideally the other person who'd be taking over maintenance of the Google Play listing would be affiliated with GitHub so it could remain official. I'm probably not being as clear as I could be (it's late night here and I'm about to go to sleep) but I advocate for NOT removing the app from Google Play, and for keeping it in the GitHub org.

Ok thanks for clarifying. I agree with you

Is there anything we can do to minimize the interruption to your work @kevinsawicki ? I mean perhaps a simple once-a-month update?

I think something like this could work, just doing regular, consistent, once a month updates. And maybe starting a CHANGELOG to document the changes over the past month.

That would be a great solution.
It would need some work (like having an always-ready-for-release branch), that's kind of the original objective of this issue, so it's fine with me.

Yes, exactly. What my tired mind could not articulate last night was the need to maintain a stable branch always, and merge in changes only after testing. That way whenever @kevinsawicki has time he can just push a build with whatever the current stable revision is.

Just an FYI to @kevinsawicki, I haven't been focused on Hubroid for a long time now since I thought this official app would have taken off. I'd be sad to see it go (even if I don't currently have any mobile client installed on my devices). Don't create more work for me. ;)

@kevinsawicki that sounds great. A changelog would be easy to maintain as well, and we could easily set up way to programmatically update the play store builds and changelog (we do something similar for internal builds here at Flipboard).
@jonanp @dgw Git-flow seems like a good approach, where master is always "ship-able", and branches/pull requests are reviewed heavily.

+1 with @hzsweers although either way is doable.
Special thanks for @kevinsawicki.

I've been thinking a lot about all this the last couple of days and I think the best solution is to start a new stable branch from the last release. I'll explain.
I think we all agree that we need a new release ASAP, we have three very important bugs that should be fixed in the Play Store: #609, #513 and #582. Current master has a lot of important changes not well tested that will take quite some time to get to a releasable state.
I suggest a stable branch that cherry-picks the bug fixes from master (#609 and #513 are already fixed) so @kevinsawicki can prepare a release soon enough, maybe not even fixing #582 just yet (which needs a significant change).
Most of the work is in fact mostly done, I'd do a 1.9.1 release with exactly what ForkHub has know in the Play Store, that is, just bugfixes for: #495, #554, #513, #609, #561, #591 (and all the duplicates of those bugs), and later a 1.9.2 release for #582.
Once we have this ready we can concentrate on 2.0.0 with all the new Material Design stuff.
What do you think?

I'd rather we just make master stable, and release later down the line.
I think we shouldn't make separate release branches, as that just makes
things confusing (merge to master? Merge to "Release"? When does release
get updated? What is master for anyway?)
I'm a little disheartened by the lack of interest from Github in
maintaining an app they developed, and am worried about that if this goes
forward as a community project. There needs to be some sort of formal
leadership, and communication with Github must be a two way street with
good faith that both sides will respond in a timely manner. There's more to
this than just updating the app as well. Crash reporting, user feedback,
new feature planning, who settles/moderates issue/PR discussions, should
there be project style guidelines, how much can we really test as a small
group, and more.
Basically, there needs to be a well organized group behind this, but I'm
pretty sure all of us have other full time responsibilities. Right now it
feels like we have a lot of people that want to help, but this thread
doesn't seem to be going anywhere fast.
On Wed, Jan 28, 2015, 3:53 AM Jon Ander Peñalba<EMAIL_ADDRESS>wrote:

I've been thinking a lot about all this the last couple of days and I
think the best solution is to start a new stable branch from the last
release. I'll explain.
I think we all agree that we need a new release ASAP, we have three very
important bugs that should be fixed in the Play Store: #609
https://github.com/github/android/issues/609, #513
https://github.com/github/android/issues/513 and #582
https://github.com/github/android/issues/582. Current master has a lot
of important changes not well tested that will take quite some time to get
to a releasable state.
I suggest a stable branch that cherry-picks the bug fixes from master (
#609 https://github.com/github/android/issues/609 and #513
https://github.com/github/android/issues/513 are already fixed) so
@kevinsawicki https://github.com/kevinsawicki can prepare a release
soon enough, maybe not even fixing #582
https://github.com/github/android/issues/582 just yet (which needs a
significant change).
Most of the work is in fact mostly done, I'd do a 1.9.1 release with
exactly what ForkHub has know in the Play Store, that is, just bugfixes
for: #495 https://github.com/github/android/issues/495, #554
https://github.com/github/android/issues/554, #513
https://github.com/github/android/issues/513, #609
https://github.com/github/android/issues/609, #561
https://github.com/github/android/issues/561, #591
https://github.com/github/android/issues/591 (and all the duplicates of
those bugs), and later a 1.9.2 release for #582
https://github.com/github/android/issues/582.
Once we have this ready we can concentrate on 2.0.0 with all the new
Material Design stuff.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/github/android/issues/682#issuecomment-71822829.

Technically, master should always be stable. We should be branching out for fixes and development.

I am disappointed with the lack of interest from Github as well. If the folks there are not interested in maintaining this app or actively participating if it becomes a community project, it doesn't make sense to keep working on it.

I don't want to enter the debate of what GitHub should or shouldn't do, they are free to do what they want and the solution @kevinsawicki proposed is good enough for me. I'll start working on a stable branch we can release every month.

I'm closing this. First and foremost is to prevent the negativity vibe that this thread may cause. This project is basically stalled ever since. Other issues such as master, stable, whatever, please create in another issue. Finally, whoever wants to contribute then you're very welcome. And who doesn't feel to contribute then you're very welcome too. Thanks so much for the input and important points stated in this thread. But it's time to move on.

I think this project is a bust. It's been nearly 2 weeks since we last heard from GitHub, how is this going to get off the ground if we can't get a solid dialogue going? I personally would be (and am) hesitant to contribute any further for worry that nothing here will actually see the light of day.
I get that everyone here wants to help and likes the idea of being in charge of the Github app development, but there needs to be some level of official oversight.


Re-ID, Ingest to Napa DB, and Verify Napa compliance for "Luqillo" study nmdc:sty-11-076c9980

Note: Scope of this work is the Napa Database Instance. The same steps will need to be repeated in a prod-ready environment
For the "Luqillo" Study -
id: nmdc:sty-11-076c9980
legacy id: gold:Gs0128850

[x] Extract records
[x] Process records: generate re-ID'ed records and changesheet for OmicsProcessing records
[x] Ingest records
[x] Delete old and failed records
[x] Apply OmicsProcessing changesheet
[x] Extract study to YAML
[x] Validate vs schema via linkml-validate
[x] Convert to RDF datastore
[x] SPARQL query for referential integrity checks

linkml-validate vs. 8.0.0 schema:  No issues found
Imported to GraphDB
PREFIX nmdc: <https://w3id.org/nmdc/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
select * where {
	?s nmdc:has_output ?o .
    minus {?o rdf:type ?oo}
} limit 100

No objects that are not Typed Subjects

Validation vs. the 10.1.0 schema has 2 errors:
(nmdc-schema-py3.9) (base) MBThornton@MBThornton-M92 nmdc-schema % linkml-validate -s ./local/nmdc-schema-v10.1.0.yaml ./local/nmdc:sty-11-076c9980.yaml

INFO:root:Using SchemaView with im=None
[ERROR] [./local/nmdc:sty-11-076c9980.yaml/0] Additional properties are not allowed ('award_dois' was unexpected) in /study_set/0
[ERROR] [./local/nmdc:sty-11-076c9980.yaml/0] 'study_category' is a required property in /study_set/0
(nmdc-schema-py3.9) (base) MBThornton@MBThornton-M92 nmdc-schema %


Specify image ID needed in section 1.6.2

In section 1.6.2 of Module 1, it is asked to enter an image ID, but none is specified. It should be mentioned which image to use, like "ubuntu_1204_server_cloudimg_amd64".

fixed with commit bc868a4


Fix wrong await code.

This await code is wrong... fixed it in this pr.

Hey @rogeralsing , I will merge this since it's a small fix. = )


[8.2.x] ISPN-4390 Realigned with ConcurrentHashMap from the JSR-166 repository

https://issues.jboss.org/browse/ISPN-4390

LGTM

Will need to fix this.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 6ebbaba:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-04-28-08-41-33 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-04-28-08-41-33

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Introduce ForceFormatting

I'm hoping I didn't step on any work you had in progress, but wanted to take a stab at #7 and put in the groundwork for #8 .

@itzg I actually started work on #7 and #8 yesterday =) I'll take a look at your approach, however I can't guarantee that this PR could be merged, I also did some refactoring of the original code.

...yes, I see you're definitely in-progress https://github.com/x-cray/logrus-prefixed-formatter/tree/develop, so feel free to close this PR.

@x-cray I was just wondering if you've made any progress?

@itzg Sorry for not picking up this for so long, busy work schedule. Yes, I have some uncommitted intermediate changes which I want to finalise. Hope to commit today.

@x-cray a gentle ping, but also wondering if you'd like me to point a PR at the develop branch to blend with your ongoing changes?

I've implemented those changes in #13. Closing this PR.

Awesome, thanks

Again, sorry for waiting


[Watt-time] Error when cloud/region value is not provided

Run the following manifest, which doesn't contain cloud/region value.
Actual result: Error  fetching data from Wattime Api.
Expected result: Should fetch the region from Wattime APi, which corresponds to the provided geolocation.
name: cloud-instance-metadata
description: example impl invoking Cloud Instance Metadata plugin
tags:
initialize:
  # outputs: ["yaml", "csv"]
  plugins:
    watttime:
      path: "@grnsft/if-unofficial-plugins"
      method: WattTimeGridEmissions
    cloud-instance-metadata:
      method: CloudMetadata
      path: "@grnsft/if-plugins"
tree:
  children:
    child:
      pipeline:
        # - cloud-instance-metadata
        - watttime
      config:
        cloud-instance-metadata:
          fields:
             - cloud/region-wt-id
            # - cloud/region-geolocation
      inputs:
        - timestamp: "2024-03-05T00:03:00.000Z" # [KEYWORD] [NO-SUBFIELDS] time when measurement occurred
          duration: 100
          cloud/vendor: azure
          # cloud/region: westeurope
          cloud/instance-type: Standard_E64_v3
          cpu/utilization: 10
          geolocation: 37.7749,-122.4194
          # geolocation: 52.0055,37.9587
          # cloud/region-wt-id: FR
          signal-type: co2_moer

not reproduceable


Can you provide code demo for each function?

My request is as title.

Hi, you can find some examples here: https://www.pywhy.org/dowhy/v0.11.1/example_notebooks/nb_index.html

Thank you, that's really great:)


KeypointRCNN Loss Index Error

🐛 Describe the bug
I am running into an IndexError when the keypoint_loss is being calculated:
        keypoint_loss = F.cross_entropy(keypoint_logits[valid], keypoint_targets[valid])

The issue is the valid indexes extend beyond the size of the keypoint_logits variable.
After a lot of debugging and investigating, the only pattern I notice is that the shape of the keypoint_logits is substantially larger when this error occurs (see below where keypoint_logits.shape is outputted):
N: 5, K: 4, H: 56, W: 56
N: 6, K: 4, H: 56, W: 56
N: 8, K: 4, H: 56, W: 56
N: 10, K: 4, H: 56, W: 56
N: 20, K: 4, H: 56, W: 56 <--- where the problem occurs

This does not happen on every image, and I have not been able to see a pattern on the input images and targets side that might suggest it is an error with the input data (but I know this could very well be where the issue is).
This is a custom dataset with only a single bounding box per image, 4 keypoints per bounding box, and a single label per bounding box.
Here is an example of a target dictionary
{'boxes': tensor([[ 50.4433,  53.8947, 461.5564, 459.5478]]),
 'labels': tensor([3]),
 'keypoints': tensor([[ 50.4433, 170.1647,   1.0000],
         [442.2101,  53.8947,   1.0000],
         [461.5564, 343.2779,   1.0000],
         [ 69.7896, 459.5478,   1.0000]])}

The images are resized to (512,512) in the dataset.getitem() and I have ensured all target keypoints and bounding boxes fall within the image.
The shape of keypoint_logits is  [20,  4, 56, 56] when it is passed to the function, and torch.Size([80, 3136]) after the line
    keypoint_logits = keypoint_logits.view(N * K, H * W)

The code to reproduce this would be too much to add everything, I think it would be easier if I could get some guidance on things to look for/extra info to provide here that would help.
Versions
Collecting environment information...
PyTorch version: 1.12.1
Is debug build: False
CUDA used to build PyTorch: 11.3
ROCM used to build PyTorch: N/A
OS: Microsoft Windows 10 Enterprise
GCC version: Could not collect
Clang version: Could not collect
CMake version: version 3.24.1
Libc version: N/A
Python version: 3.8.13 | packaged by conda-forge | (default, Mar 25 2022, 05:59:45) [MSC v.1929 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.19045-SP0
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to:
GPU models and configuration: GPU 0: GeForce GTX 1650
Nvidia driver version: 462.30
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Revision=
Versions of relevant libraries:
[pip3] numpy==1.23.3
[pip3] torch==1.12.1
[pip3] torchaudio==0.12.1
[pip3] torchmetrics==1.0.0
[pip3] torchvision==0.13.1
[conda] blas                      2.116                       mkl    conda-forge
[conda] blas-devel                3.9.0              16_win64_mkl    conda-forge
[conda] cudatoolkit               11.3.1               h59b6b97_2
[conda] libblas                   3.9.0              16_win64_mkl    conda-forge
[conda] libcblas                  3.9.0              16_win64_mkl    conda-forge
[conda] liblapack                 3.9.0              16_win64_mkl    conda-forge
[conda] liblapacke                3.9.0              16_win64_mkl    conda-forge
[conda] mkl                       2022.1.0           h6a75c08_874    conda-forge
[conda] mkl-devel                 2022.1.0           h57928b3_875    conda-forge
[conda] mkl-include               2022.1.0           h6a75c08_874    conda-forge
[conda] numpy                     1.23.3           py38h8503d5b_0    conda-forge
[conda] pytorch                   1.12.1          py3.8_cuda11.3_cudnn8_0    pytorch
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchaudio                0.12.1               py38_cu113    pytorch
[conda] torchmetrics              1.0.0                    pypi_0    pypi
[conda] torchvision               0.13.1               py38_cu113    pytorch

The code to reproduce this would be too much to add everything, I think it would be easier if I could get some guidance on things to look for/extra info to provide here that would help.

Hmmmm I'd suggest looking into (almost) all the files in https://github.com/pytorch/vision/tree/main/references/detection and in particular what happens when keypoints are used / transformed there.

@NicolasHug  The keypoints targets that are passed don't appear to be an issue. I have gone through the reference implementation and I believe there is no issue directly with the targets or the images passed during training.
After playing with the anchor generator parameters (scale and aspect ratios), it seems like modifying the scale has some impact on the section where I am getting an error, in fact, I get the exact same error at the first pass when I make the anchor generator scales large.
It seems that keypoints_to_heatmap outputs a square of shape N x N, but keypoint_tensors doesn't always have the first dimension of at least N. I'm not sure why this happens or what would be affecting the generation of the keypoint_tensors. Any suggestions here would be appreciated

After further investigation, it seems to have been an error on our end with the keypoints shape [4,3] instead of [1,4,3].
Could perhaps be useful to check that the first dimension of the keypoints matches the first dimension of boxes and raise an error indicating mismatch to the user?


Fixes Windows CI: prepend '/c/Program Files/Git/bin'

Bash@3 started failing after a recent change related to WSL
https://github.com/actions/virtual-environments/pull/1081
https://github.com/actions/virtual-environments/pull/1276
This PR ensure bash.exe is picked from Git Bash

Thanks @-phated for the idea

🙌

Thank you @phated and @prometheansacrifice. I incorporated the fixes into this PR:
https://github.com/facebook/reason/pull/2605
I'll merge the other one if it's ready within the day, else merge this one.


Fix/plangeneration

Changes the url of the opentosca runtime within winery to enable plan generation again

[x] Ensure that you followed http://eclipse.github.io/winery/dev/ToolChain#github---prepare-pull-request. Especially, we require a single commit
[x] Ensure that the commit message is a good commit message
[x] Ensure to use auto format in all files
[x] Ensure that you appear in NOTICE at Copyright Holders
[ ] Tests created for changes
[x] Documentation updated (if needed)
[x] Screenshots added (for UI changes)

Can one of the admins verify this patch?

Can one of the admins verify this patch?


How to install Sharp on angular 2 ?

When i run the server appear this error:
`
WARNING in ./~/sharp/lib/icc/sRGB.icc
Module parse failed: C:\Users\Work\Desktop\AngularNodeTest\new\DoodlyAccounts\node_modules\sharp\lib\icc\sRGB.icc Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type.
(Source code omitted for this binary file)
 @ ./~/sharp/lib ^\.\/.*$
 @ ./~/sharp/lib/index.js
 @ ./src/app/app.component.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://accounts.doodly.com:81 ./src/main.ts

WARNING in ./~/sharp/lib/icc/cmyk.icm
Module parse failed: C:\Users\Work\Desktop\AngularNodeTest\new\DoodlyAccounts\node_modules\sharp\lib\icc\cmyk.icm Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type.
(Source code omitted for this binary file)
 @ ./~/sharp/lib ^\.\/.*$
 @ ./~/sharp/lib/index.js
 @ ./src/app/app.component.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://accounts.doodly.com:81 ./src/main.ts

WARNING in ./~/sharp/lib/constructor.js
Module not found: Error: Can't resolve '../vendor/lib/versions.json' in 'C:\Users\Work\Desktop\AngularNodeTest\new\DoodlyAccounts\node_modules\sharp\lib'
 @ ./~/sharp/lib/constructor.js 24:15-53
 @ ./~/sharp/lib/index.js
 @ ./src/app/app.component.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://accounts.doodly.com:81 ./src/main.ts

ERROR in C:/Users/Work/Desktop/AngularNodeTest/new/DoodlyAccounts/src/app/app.component.ts (28,1): Cannot find name 'readableStream'.

ERROR in C:/Users/Work/Desktop/AngularNodeTest/new/DoodlyAccounts/src/app/app.component.ts (30,9): Cannot find name 'writableStream'.

ERROR in C:/Users/Work/Desktop/AngularNodeTest/new/DoodlyAccounts/src/app/app.component.ts (28,1): Cannot find name 'readableStream'.

ERROR in C:/Users/Work/Desktop/AngularNodeTest/new/DoodlyAccounts/src/app/app.component.ts (30,9): Cannot find name 'writableStream'.

ERROR in ./~/sharp/build/Release/sharp.node
Module parse failed: C:\Users\Work\Desktop\AngularNodeTest\new\DoodlyAccounts\node_modules\sharp\build\Release\sharp.node Unexpected character '�' (1:2)
You may need an appropriate loader to handle this file type.
(Source code omitted for this binary file)
 @ ./~/sharp/lib/constructor.js 9:14-52
 @ ./~/sharp/lib/index.js
 @ ./src/app/app.component.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://accounts.doodly.com:81 ./src/main.ts
webpack: Failed to compile.

`
how can I solve this problem ?

sharp is a server side node module. You're trying to load it using a webpack loader?
Afaik it's not possible because sharp requires many native modules to work.


pull request for e2e test at 11/12/2016 19:26:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Encapsulate workflow basic dependencies into a workflow-core package

This PR adds a new sub-project in sbt called workflow-core, under micro-services.
It contains a duplicated codebase of workflow core dependencies, including:

Tuple, Attribute, Schema;
OperatorExecutor;
PhysicalOp, PhysicalPlan;
Identities;
and other utility functions.

Migration plan:
After exporting workflow-core as a local dependency, we can build workflow-compiling-service and workflow-execution-service based on it.

Can other micro services like workflow-compiling-service import workflow-core as dependencies after this PR?

Can other micro services like workflow-compiling-service import workflow-core as dependencies after this PR?

That is the idea. I sent you a POC branch as an example for using workflow-core as dependency.


Dropdowns inside child component get reinitialized to null.

I upgraded to carbon framework v4 and I implemented reactive forms, since then I been having issues with 3 dropdowns that are located inside a child component, I have an *ngIf condition in my parent component to display only when there is a property value, I was using ngModel before implementing reactive forms, my parent component is responsible for initializing and patching the form with the database values, the initialization is done inside the constructor in my parent component and I pass the form via input to my child component, the child component does not do anything in the constructor I only have an ngOnInit but do not do anything with the form.
The issue is that the dropdowns shows as if they were null, even when I patch them before, during the patch I set the value to some text inputs as well, this text inputs are also inside the child component and they do not loose the value patched once the view is fully loaded, I debugged the value of the form controls for the dropdowns and they have values all the way but when the child component and parent component fully display the dropdowns are back to null.
I try patching the values inside the child component inside "ngAfterViewChecked" and "ngAfterViewInit" but still does not works, so some how the dropdowns are loosing the value and set back to null, again it only happens with the dropdowns.
I was told to use "itemValueKey" or to assign the "select" property of the list to "true" but nothing is working. I think there might be a bug that is reseting my dropdowns to null when the parent and child component fully display.
Note: I have a button inside the child component that the user uses to upload changes in the form and when they use this the dropdowns work fine they do not loose the value, but in this cases the view was completely loaded. I can not just let the form visible all the time because I do not have values all the times so it does not look good and it sends errors of undefined for the same reason.

Is this a feature request (new component, new icon), a bug, or a general issue?

Yes this issue is specific to the dropdown component.

I expect that after the parent and child component my form does not looses the value previously patched. Instead the value of the dropdowns are being set to null and the form shows invalid and the users needs to select values again to turn it to valid.

My browser is Chrome.

The version of Carbon Design System is v4.

*This is the parent component already loaded but with ngIf hiding the parent and child input components.

Here I select a file that I already have most of the required values except the last dropdown to the right. I patch the form controls with the values after loading the file. For example here the "requested payment terms" is part of the child component and is also required so this one does not have any issues. The dropdowns should not be invalid because they have a value patched, but the controls looses the value and are set to null, you can see a value selected because I'm using the placeholder property.

In this case I need to select the values from the dropdown again now that the view is fully loaded so that my form state turns back to valid.

This is the code from the parent component:

This is the code from my child component:

Hi Team I found the issue, I have added a function that executed on the selected event of the dropdown that patched the value of the form control and by some reason I guess this was being executed when the component loaded for the first time and I think this was setting the value to null, when I removed this patch command it worked fine. We can close this issue. Thanks for your time.


literal storage: 4x performance improvement using a hashmap

This PR is used to improve the literal storage performance:
Currently, literals are stored using a linked list: The drawback of the linked list is that when the number of literal entries increases, the time it takes to add a new entry increases proportionally to the number of entries: The reason is that before adding new entries, the storage engine first needs to iterate over all existing entries to find out if the "new" entry is a duplicate of an existing one or a new entity.
When running on a 200 Mhz CPU with a heap stored in PSRAM, if 1000 entries are already in the literal storage linked list, then it takes almost 1 millisecond to add a new entry (eg 1 millisecond to iterate over all existing 1000 entries). This makes loading snapshots very slow, especially when many background modules have already been loaded (where each background module adds its literals). Empirically, we measured that it takes 200 milliseconds for jerry_exec_snapshot to load and execute a snapshot containing about 200 literals when 1000 literals are already in the list before loading (measured on 200Mhz CPU with heap in PSRAM).
The change introduces an additional hashmap to speed up the look-up of existing literals: This way, it is not necessary to iterate through the entire literal linked list (in O(n)) - and instead, an O(1) lookup operation can be used. Empirically, we have noticed that the application that took 200 milliseconds to load now takes 50 ms (measured from jerry_exec_snapshot), bringing a 4 times performance improvement.
This feature can be enabled using the flag JERRY_LIT_HASHMAP. The test configuration has been updated to include this feature flag. Unit and functional tests have successfully passed. Test has also been done on the Open Harmony Jerry script version.
JerryScript-DCO-1.0-Signed-off-by: Ronan Jezequel<EMAIL_ADDRESS>

ok, let me rewrite the hashmap library, and at the same time use the standard comment syntax from jerryscript.

New commit added, with hashmap completely written from scratch - and also with better performance.

Looks like a nice patch! We check it further soon

It looks like tests/jerry/arithmetics.js fails. Do you know why?

@ronanj I apologize for the delay, the CI issues for OSX have been resolved, please squash your changes, and add DCO to the commit message.

Close and reopen to re-trigger the CI

@ronanj could you please rebase the PR? It will make the CI green (probably).

I have some idea about this, currently, the ecma_string_t is super complicated and have many issue about that, I'd like to take the idea Atom from quickjs to implement string and string in jerryscript, and Atom is Hash-Table based, so the performance issue addressed by this MR will also be resolved.