[SPARK-10542] [PYSPARK] fix serialize namedtuple

Merged build triggered.

Merged build started.

Test build #42289 has started for   PR 8707 at commit d7ef6ce.

Test build #42289 has finished for   PR 8707 at commit d7ef6ce.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42289/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #42293 has started for   PR 8707 at commit 6b9095b.

Merged build triggered.

Merged build started.

Test build #42295 has started for   PR 8707 at commit 1d766aa.

Test build #42293 has finished for   PR 8707 at commit 6b9095b.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42293/
Test FAILed.

Test build #42295 has finished for   PR 8707 at commit 1d766aa.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42295/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #42298 has started for   PR 8707 at commit a2f9f36.

Test build #42298 has finished for   PR 8707 at commit a2f9f36.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42298/
Test FAILed.

Test build #1739 has started for   PR 8707 at commit a2f9f36.

Test build #1739 has finished for   PR 8707 at commit a2f9f36.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopWriter(jobConf: JobConf)
class BlockRDD[T: ClassTag](sc: SparkContext, @transient val blockIds: Array[BlockId])
class ZippedWithIndexRDD[T: ClassTag](prev: RDD[T]) extends RDD[(T, Long)](prev)
 case class Instance(w: Double, a: Vector, b: Double)
class DefaultSource extends RelationProvider with DataSourceRegister
class WeibullGenerator(
class IndexToString(JavaTransformer, HasInputCol, HasOutputCol):
class Checkpoint(ssc: StreamingContext, val checkpointTime: Time)
abstract class InputDStream[T: ClassTag] (ssc_ : StreamingContext)
abstract class ReceiverInputDStream[T: ClassTag](ssc_ : StreamingContext)

Merged build triggered.

Merged build started.

Test build #42304 has started for   PR 8707 at commit 9326697.

Test build #42304 has finished for   PR 8707 at commit 9326697.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42304/
Test PASSed.

Over at https://issues.apache.org/jira/browse/SPARK-10544, someone commented to mention that other types of built-in types do not seem to be pickleable in 1.5.  For instance, here's the example that they gave:
sc.parallelize(["the red", "Fox Runs", "FAST"]).map(str.lower).count()

However, this specific example also seems to fail in 1.3.1, so I don't think that this is a regression. Just wanted to mention this discussion here to make sure you were aware of it.

Do you have any intuition for why this worked prior to 1.5 without the changes implemented here?

Actually, one point of confusion: it looks like python/pyspark/serializers.py had some methods for serializing namedtuple classes with its _restore and _hack_namedtuple(cls) methods, but this patch also adds logic to cloudpickle.py to handle pickling of these instances. Do we need both of these methods? Are some only needed by certain versions of Python? It would be good to add some comments to explain some of this stuff, since it's not obvious from reading the code.

The HACK in serializers.py is used for cPickler, not cloudpickle.

Before 1.5, the old way work in CPython, but not PyPy (we don't have a unit test for it).

@JoshRosen BTW, this patch introduce a special case for namedtuple, it should be safe to merge into branch-1.5.

Empirically, this seems to work, so unless you think that we should investigate the root cause any further I'm fine with giving this an LGTM and merging to 1.5. Feel free to merge yourself, or I can do it.

I tried to find the root cause, but it seems hard to work in all Python versions (you can see them in the older commit), finally switch to current approach. merging this into master and 1.5 branch, thanks!

FYI, this works for us @ NinthDecimal. Thanks for the fix, it was a stumper!
Python 2.7.5
Spark-1.5 Branch @ 4c4a9ba28d9052fad45caca9a1eba9ef9db309d5

Hi! I am not sure if this is related but is I look for this issue everything points me here basically. I'm getting
    f(self, obj) # Call unbound method with explicit self
  File "/usr/lib/python2.7/pickle.py", line 649, in save_dict
    self._batch_setitems(obj.iteritems())
  File "/usr/lib/python2.7/pickle.py", line 681, in _batch_setitems
    save(v)
  File "/usr/lib/python2.7/pickle.py", line 286, in save
    f(self, obj) # Call unbound method with explicit self
  File "/opt/spark/python/lib/pyspark.zip/pyspark/cloudpickle.py", line 315, in save_builtin_function
    return self.save_function(obj)
  File "/opt/spark/python/lib/pyspark.zip/pyspark/cloudpickle.py", line 191, in save_function
    if islambda(obj) or obj.__code__.co_filename == '<stdin>' or themodule is None:
AttributeError: 'builtin_function_or_method' object has no attribute '__code__'

When trying to create a data frame from an RDD:
        rdd = self.sc.textFile(self.input_file_path).map(lambda line: self.process_line(line))

        schema = StructType([StructField(u'Variable', StringType(), nullable=False),
                             StructField(u'Time', TimestampType(), nullable=False),
                             StructField(u'Value', FloatType(), nullable=False)])

        return sql_context.createDataFrame(rdd, schema)

I am on PySpark 1.6.0 - any ideas what I'm doing wrong here?

I also get this error when using namedtuples
n = namedtuple('test', ['a', 'b'])
cloudpickle.dumps(n(1,2))


Uninitialized local variable leads to no SPIDEV init

https://github.com/EmbeddedRPC/erpc/blob/e8e2e633f23948291b2191a93a13927cd160843d/erpc_c/transports/erpc_spidev_master_transport.cpp#L111
In my oppinion there is a bug in mentioned line above.
Should be:
erpc_status_t status = kErpcStatus_Success;

@bastivi Hi and thank you very much for pointing us to this error.


Targets' add_target(s) methods do not correctly check passed paths

Description of issue or feature request:
Judging from the docstrings and comments, add_target and add_targets are expected to update a Targets object with passed target paths, if they are relative to a targets directory base path (i.e. self._targets_directory).
However, they don't seem to take into account that Python's os.path.join ignores all path component arguments prior to a component that looks like an absolute path.
Current behavior:

Works as expected (?) if passed target path is relative to a targets directory base path or absolute but falls into the targets directory:

# repo._targets_directory == "/path/to/repo/targets"
repo.targets.add_target("foo.txt")
repo.targets.add_target("/path/to/repo/targets/bar.txt)
# Successfully adds "foo.txt" and "bar.txt"

Fails if the passed target path is not absolute and does not exist relative to  targets directory base path "/path/to/repo/targets".

# repo._targets_directory == "/path/to/repo/targets"
repo.targets.add_target("repo/targets/foo.txt")
# Fails with "'/path/to/repo/targets/repo/targets/foo.txt' is not a valid file in the repository's targets directory"

Fails if the passed target path is absolute and does not exist

#repo._targets_directory == "/path/to/repo/targets"
repo.targets.add_target("/path/does/not/exist/foo.txt")
# Fails with "'/path/does/not/exist/foo.txt' is not a valid file in the repository's targets directory"

Has unexpected behavior if the passed path is absolute and exists!

Expected behavior:
Revise intended behavior, update implementation accordingly.

IIUC target files don't get hashed right away, i.e. on add_target(). This happens when generating and writing targets metadata to disk, e.g. via writeall(). So why not completely ignore the notion of files on disk until then?
add_target could just add any paths passed to the internal representation of targets metadata, checking that they are relative (and maybe don't contain ".."?).  And only later, when the corresponding files are actually needed, i.e. to generate hashes, should it fail gracefully if any of the paths can't be resolved into a file relative to the targets directory base path.

A possible disadvantage of this proposal may be that it's harder to debug if the errors come at a seemingly unrelated call site. Path related failures when you add those paths in add_target() feels a lot more intuitive than path related failures at a later time.
Is it safe to infer from the issue report that all four of the current behaviour examples should succeed? I'd be happy to have a go at implementing a fix for this.
Aside: I've worked on projects in the past where we had to implement an alternative path joining function, due to the / related behaviour of os.path.join(). That might be a way to go here, perhaps a helper in SSL? I'll need to look at the current code some before committing to that, though.

I agree with your debugging concern, @joshuagl. I am concerned with least surprise. :)
To me, and this should answer your other question, none of above cases seems fully surprise-free. Here are some concerns:

Why can I pass an absolute path, if the spec says that targetpaths should be relative?
Why should I pass an absolute path, if it must be relative to an "unknown"  base path (i.e. self._targets_directory), which gets discarded anyway?
Why must a relative path be relative to an "unknown" base path, and not relative to my cwd?

add_target could just add any paths passed to the internal representation of targets metadata, checking that they are relative (and maybe don't contain ".."?). And only later, when the corresponding files are actually needed, i.e. to generate hashes, should it fail gracefully if any of the paths can't be resolved into a file relative to the targets directory base path.

This feels like a sensible approach, that handles @lukpueh's least-surprise concerns above and we can address my debugability concern with appropriate logging.

For consistency we should adopt whatever behavior we want for add_target and add_targets to other methods of repository_tool.Targets, that allow adding target files, i.e.:

delegate
delegate_hashed_bin (coordinate with #995)
add_target_to_bin and (oddly) remove_target_from_bin (coordinate with #994).

Fixed in #1008


Investigate why Volt's SLI (work book) stopped working

Current Behavior
Somewhere between 30-60 days ago Volt's SLI stopped working.
Confirmed on both U-001 and T-001.
See dump from U-001 here and note the flatlining:

Acceptance criteria:

[ ] A conclusion has been made to why the SLI stopped working. Note: A solution will be done in a separate story.

Expected behavior

How to reproduce
Log on to Azure -> Find the Charges Resource group -> Open the Volt SLI -> Open work book
Logs

Environment
U-001, T-001, most likely also in B-002.
Possible Solution
Workbook
Names of endpoints have been changed, so this needs to change, but the big problem is that it groups logs by operation_Id. The problem is that requests that are saved in the outbox database have a operation_Id and when the outbox processor endpoint runs it creates a new operation_Id.
Therefor no results found when trying to for example group by ChargeIngestion a ChargeInformationRejectionDataAvailableNotifierEndpoint
A possible solution might be to log correlation id in OutboxEndpoint and try to make a join on operation_Id = correlationid inside log analytics
Dashboard
Was broken on the 9. september which indicates its broken when we changed servicebus namespace. I tried to fix it here https://github.com/Energinet-DataHub/geh-charges/pull/1746 by using service bus namespace name instead of id which changed in the PR on the 9. but when trying to deploy it manually it didnt seem to fix it, so there might be another or more issues.
Additional context/screenshots

Read through Mads' investigation results, and added relevant acceptance criteria to story #1770. Closed.


Update mockito-scala to 1.16.12

Updates org.mockito:mockito-scala from 1.16.0 to 1.16.12.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.16.0).
You might want to review and update them manually.
project/Dependencies.scala

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito", artifactId = "mockito-scala" } ]

labels: test-library-update, semver-patch, old-version-remains

Superseded by #757.

Superseded by #757.


Created footer-white-14

Issue- #507
Please review this.

For the mobile version it breaks. @kunal00000


Extend helper feature tests.

Lately I was struggling with stubbing current user in helper tests, with some tries I found this behaviours:

Methods from helper are defined in ExampleGroup as well
Methods defined within ExampleGroup are then also visible within those methods

Stubbing current user for helper ended up with error
allow(helper).to receive(:current_user).and_return(User.new)
# => #<#<Class:0x00000004585be8>:0x00000004509f20 .................... > does not implement: current_user

And of course it's because it's defined in controllers. So the question is how else can we stub helper methods from controllers in helpers?

Thank you for taking the time to put this together :blue_heart: :blue_heart:
Unfortunately, this PR as an addition to the public relish docs isn't something as it that I think we'll be able to accept. The behaviors documented here are not the intended behavior of helper specs :cold_sweat:
I really appreciate your effort and work on this :smile_cat:.  The working examples have clearly pointed out some major flaws in the helper spec implementations. They also are a great start as future implementation checks that should be added / moved into the regular spec suite.
To answer your initial question, my current suggestion for controller based helpers are to make them into a module which your application would include. However, to server as documentation if that's not an option, I would consider starting with one of the following approaches:
require 'rails_helper'

module UserHelper
  def email
    current_user.email
  end
end

RSpec.describe UserHelper, :type => :helper do

  specify "uses the controller helper's current user" do
    controller_helper = Module.new do
      def current_user
        User.new(email: "any email")
      end
    end
    helper.extend controller_helper

    expect(helper.email).to eq "any email"
  end

  another_controller_helper = Module.new do
    def current_user; end
  end

  specify "stubbing the helper under test feels awkward" do
    helper.extend another_controller_helper
    allow(helper).to receive(:current_user).and_return(
      instance_double(User, email: :any_email)
    )

    expect(helper.email).to eq :any_email
  end
end

Given the slightly awkward nature of that and accessing let and other helpers in the module can be a little odd I would be open to considering a new DSL method. Perhaps something like:
RSpec.describe UserHelper, :type => :helper do

  let(:an_email) { :let_memo }

  controller_helper(:current_user) do
    instance_double(User, email: an_email)
  end

  specify "the anonymous module is setup and extended for you" do
    expect(helper.email).to eq an_email
  end

end

Thoughts?

I'd just like to :+1: @cupakromer's comments, I'm very surprised you can access the methods directly in the test, that seems insane.

Thanks @cupakromer and yes those examples were mainly to show off the weird behaviour.
controller_helper method would be great! Although we can probably use this anonymous module in mean time.

@driv3r do you have the time to finish this pull request off? We'd love to see it merged.

@samphippen this PR is unrelated to the changes we'd actually like to see, as @cupakromer mentioned this behaviour is currently a bug not a feature, I'm going to close this because any changes arising from this discussion would be suitably different to the original content.


Consider supporting x-ms-client-name on schemas

It's something we do a lot in storage:
https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/storage/Azure.Storage.Blobs/swagger#restypeservicecompproperties

and make sure it works with XML by adding name to XML extensions when it's there.


GetMassListFromScanNum equivalent in Python / dotNET

Hello,
Not really an issue,
but wondering the equivalent call from older C++ interface XRawfile::IXRawfile2Ptr GetMassListFromScanNum() in the new dotNet / Python world?
thx e.-

Hi @keesh0,
Since I am not familiar with the C++ library you are describing and am not affiliated with Thermo Fisher in any way, I can only
provide you some hints.

Have a look at the examples and, maybe you'll find something useful.
The RawFileAccess class should provide you all the scan events in your file:

scan_event = raw_file_access.scan_events.get_event(my_scan_num)
masses = scan_event.get_mass_range(idx)

The following appeared to work for me:
raw_file.get_centroid_stream() and
raw_file.get_segmented_scan_from_scan_number().

I am glad to hear that you found something that suits your needs. If you open the RawFile code you see that it is pretty much just a wrapper for the RawFileAccess class. This might help you if there are requirements which are not covered by RawFile. Closing the issue for now.

I think part of the confusion is due to unclear terminology. In my domain, which is mostly small molecule inorganic chemistry, centroid-style mass spectra are not really used anymore and we almost exclusively work with "profile spectra".
However, something I was not aware of until now is that at least ThermoFisher *.raw files do not store the full scan range as intensity vs. m/z, as it is done in NMR, IR, and UV/Vis spectroscopy, where you really have x/y pairs of data over the full range, but only "peak regions" with a little bit of zeros to the left and right.
When you think about it, it actually makes a lot of sense not to store tons of close to zero values, as scan range in mass spectrometry is much wider than in the other methods and at the same time with high-resolution mass analyzers also records much more data points per unit of x-axis.
So I think the key for me was to realize that the "segmented scan" is actually the "profile scan" that I need.
It's really just that it did not show up under the name I expected.


How to vertically center slider controls?

Given the following:
<FluentStack VerticalAlignment="VerticalAlignment.Center" Style="background-color: cornflowerblue;">
    <FluentBadge Appearance="Appearance.Accent">
        100 words
        <FluentIcon Value="@(new Icons.Filled.Size12.ArrowBidirectionalUpDown().WithColor(Color.Lightweight))" />
    </FluentBadge>
    <FluentSlider Style="background-color: red;" Min="0" Max="100" Step="10" Value="0" />
</FluentStack>

The slider doesn't render vertically centered:

I've tried all sorts of combinations of CSS alignment attributes but I can't figure out how to tell the slider to align its parts vertically centered (via style or otherwise). Any tips?
The goal is to have the slider be vertically centered (both thumb and track) with regards to other elements in the same "row" (flex-wise)
WORKAROUND
Set the slider height, such as: Style="calc((var(--design-unit) + var(--stroke-width)) * 1px)"

I've come this far:

By using this CSS:
::deep fluent-slider::part(positioning-region) {
    align-items: center;
    border: 1px solid red;;
}

::deep fluent-slider.horizontal::part(track-container) {
        align-self: auto;
    }

::deep fluent-slider.horizontal::part(thumb-container) {
    transform: translateX(calc(var(--thumb-size) * 0.5px)) translateY(0);
}

You should be able to get that adapted to your use case.

wow, I wish there was more docs on the ::part and what parts each control has for advanced styling like this. Totally awesome CSS-fu, sir!

I wonder if a vertically centered display couldn't be just a built-in property (like VerticalAlignment) that automatically causes those styles to apply 🤔

I tend to agree. But that would need to be implemented at the web component level then...


Add kubernetes labels

This adds support for adding kubernetes labels to pods.  Either via the kubernetes decorator with labels={"label": "value", "label2": "value2"}, with an env var METAFLOW_KUBERNETES_LABELS="label=value,label2=value2", or add to the with command python hello_world.py run --with kubernetes:labels="cli_label=cli_value".  I also created an issue for this:
Netflix/metaflow#1235

Hey @dhpollack, thanks for looking into this. Metaflow also has the concept of tags (https://docs.metaflow.org/scaling/tagging).
Is there any overlap between tags and labels? And could there be some option to simply use one to avoid confusion? WDYT?

We use kubernetes labels everywhere in our organization for cost tracking and tagging. Some of these labels are not very useful as metaflow tags.

Hey @dhpollack, thanks for looking into this. Metaflow also has the concept of tags (https://docs.metaflow.org/scaling/tagging).
Is there any overlap between tags and labels? And could there be some option to simply use one to avoid confusion? WDYT?

But specifically about overlap... There is a little but they are not the same nor do I think one should try to use them in the same.
For one, your tags are strings, while the kubernetes labels are key-valur pairs. But even from a user perspective, metaflow tags seem designed for data scientists to track experiments in metaflow. While kubernetes labels are what a lot of the kubernetes universe uses for filtering and organizing things that happen on kubernetes...
If you changed metaflow tags to mirror kubernetes labels (key-valur, restrictions on length and valid characters, etc etc) then i think you could simply use one of them. But that's a lot more work for you and I think people that want to add kubernetes labels to their pods generally know what kubernetes labels are and wouldn't be too bothered by the additional complexity.

@shrinandj can you re-run the failed CI test?  It looks like it failed but shouldn't have.  Probably just a hiccup on the machine.

Generally looks good. Thanks for doing this @dhpollack! Can you add some details of the tests that were run for testing this PR? Especially, did you create argo workflows with this code and ensure that the pods created by Argo have the correct labels?

So to test this I used something like the following flow:
from metaflow import FlowSpec, step, kubernetes

class TestFlow(FlowSpec):
    @step
    def start(self):
        self.my_var = "hello world"
        self.next(self.a)

    @kubernetes(labels={"my_label": "my_value", "label2": None, "label3": "val"})
    @step
    def a(self):
        print("the data artifact is: %s" % self.my_var)
        self.next(self.b)

    @kubernetes(
        labels={
            "my_label": "superlonglabelthatshouldgethashedbytheautomatedhashingfunctionorsomethinglikethat",  # noqa: E501
            "my_label2": "ein bißchen falsch",
        }
    )
    @step
    def b(self):
        pass
        self.next(self.end)

    @step
    def end(self):
        print("the data artifact is still: %s" % self.my_var)

if __name__ == "__main__":
    TestFlow()

Then I ran the following (note image each space is a new terminal):
export METAFLOW_KUBERNETES_LABELS='env_label=env_var`
python test_workflow.py run  --with kubernetes

python test_workflow.py run

python test_workflow.py run --with kubernetes:labels="label1=val1,label2=val2,label3,label4=val4"

# remove kubernetes decorators from the flow (this is actually how we generally would use this)
export METAFLOW_KUBERNETES_LABELS='env_label=env_var`
python test_workflow.py run --with kubernetes

export METAFLOW_KUBERNETES_LABELS='env_label=env_var`
python test_workflow.py argo-workflows create && python test_workflows argo-workflows trigger

There are a few quirks.

If you set an env var and use --with kubernetes the steps decorated with the kubernetes labels overwrite the env var labels completely.
The argo labels seem to work, but it feels a bit like magic because metaflow automatically imports the kubernetes decorator and that adds the labels.  If you look at the argo template that gets generated, the labels are not in the argo metadata.  But I feel like that was ok, because if you wanted to set those then perhaps you'd have a separate parameter for the argo decorator that is a flow decorator rather than a step decorator.

Thanks for the details about testing. It definitely increases the reviewers confidence in the commits.
Just a couple of other tests:

Can you test with K8s labels AND nodeSelectors since this code touches that functionality as well.
Can you test original @kubernetes and --with kubernetes functionality without labels. Basically, to ensure that nothing has regressed because of this change.

Thanks for the details about testing. It definitely increases the reviewers confidence in the commits.
Just a couple of other tests:
* Can you test with K8s labels AND nodeSelectors since this code touches that functionality as well.

* Can you test original `@kubernetes` and `--with kubernetes` functionality without labels. Basically, to ensure that nothing has regressed because of this change.

I forgot to mention that in my comment about the tests.  I also tested without labels and with node selectors in different combinations as well (alone, via the decorator, env vars, and using --with kubernetes:....  The main change was the change in the runtime_step_cli.  Previously, if you had more than one node selector, then it would create a tuple with a single item like ('label1=val1,label2=val2',) and now it will do ('label1=val1', 'label2=val2') which I think was just a bug in the previous code.

@savingoyal Anything you would like done here?

I download the source code locally and tried to test this change.

Ran a flow with Kubernetes and a single label. This worked just fine.

$ python3 /tmp/a.py run --with kubernetes:labels="abc=pqr"
...

Ran a flow with Kubernetes decorator and added a label there. This worked just fine.

    @kubernetes(labels={"abc":"pqr"})

Ran a flow with Kubernetes decorator and add two labels. This worked just fine too.

    @kubernetes(labels={"abc":"pqr", "lmn":"xyz"})

Ran a flow with Kubernetes on cli with two labels. THIS FAILED with the following error

$ python3 a.py run --with kubernetes:labels="abc=pqr,lmn=xyz"
Metaflow 2.7.19 executing StarterFlow for user:shri
    Unknown decorator attribute:
    Decorator 'kubernetes' does not support the attribute 'lmn'. These attributes are supported: cpu, memory, disk, image, service_account, secrets, node_selector, labels, namespace, gpu, gpu_vendor, tolerations.

exported the env variable METAFLOW_KUBERNETES_LABELS with one label and ran a flow. This worked just fine.

exported the env variable METAFLOW_KUBERNETES_LABELS with two labels and ran a flow. This worked just fine too.

Ran a few other flows with Kubernetes specifying cpu, memory, etc. on the cli. They worked just fine.

@shrinandj looking at how metaflow creates the --with kubernetes string for argo.  It actually does something like --with kubernetes:labels='{"abc":"pqr", "lmn":"xyz"}'.  I am not sure if this is undesired behavior or bad documentation.  The way that I had it before was based on the node selector, but that also did not work correctly when having multiple node selectors.
https://github.com/Netflix/metaflow/pull/1236#discussion_r1071193731
It's related to this issue which I brought up earlier.

The following code will split "labels=l1=v1,l2=v2" as [("labels", "l1=v1"), ("l2", "v2")].  It looks like the only way to have multiple objects in this format is to use a json object.  The other way would be to write a much more complicated regex that searches for valid keys and then rewrites that string as a json.
https://github.com/Netflix/metaflow/blob/master/metaflow/decorators.py#L132
    @classmethod
    def _parse_decorator_spec(cls, deco_spec):
        if len(deco_spec) == 0:
            return cls()

        attrs = {}
        # TODO: Do we really want to allow spaces in the names of attributes?!?
        for a in re.split(""",(?=[\s\w]+=)""", deco_spec):
            name, val = a.split("=", 1)
            ...

There's some quirkiness involved related to the shell and the OS involved when there are multiple labels to be specified on the CLI. Using the json style input works just fine in that case.
Verified this with:
python a.py run --with kubernetes:labels='{"l1":"v1","l2":"v2"}'

This change should be good to go!

@dhpollack looks like this PR is backward incompatible -

I have created #1359 which reverts this PR so that releases are unblocked. Can you please address this issue and resubmit the PR?

@dhpollack looks like this PR is backward incompatible -

I have created #1359 which reverts this PR so that releases are unblocked. Can you please address this issue and resubmit the PR?

Yea, looks like it should be a quick fix.  I'll work on it tomorrow.


error 443

hi , i tried to host it online on ubantu 18.04 with my hosting domain.but issue is when i send url to another perosn even another tab its shows Not Found The requested URL was not found on this server.  Apache/2.4.29 (Ubuntu) Server at  Port 443

Sorry from this information, we don't see any issue and can not help. Please provide a very detailed problem description, that you experience connected to our developments.

Sorry from this information, we don't see any issue and can not help. Please provide a very detailed problem description, that you experience connected to our developments.

thanks for reply, I have application live where multiparty meeting is running .....i moved build folder to /var/www/html  it works fine but i am not able to create room ...when i move all files from build to main directory which /var/www/html ..i can make room but when i send link to join it shows Not Found The requested URL was not found on this server. Apache/2.4.29 (Ubuntu) Server at Port 443

You don't have to run an Apache or any external web server, you should run the server part of our service.
Even more I propose to just use the ansible playbook and the docker image.
See this screencast.

Please open a new issue if we can help you further.. Thanks!


Frontend - Provide Current User for Post detail

Closed by https://github.com/jobsgowhere/jobsgowhere/pull/140


master-Live

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/develop-your-app/InvestigateMemoryLeaks.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/Loopback.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.


pgsql sanitation

Fixes #168
Confirmed working for me with a fresh Postgres database and fresh Lychee install
Thanks to @jprokop1 on #168

Thanks, i was too tired to finish this


Image pull always gives error via Portainer, works via commandline

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
I have a container that has the image ghcr.io/fastenhealth/fasten-onprem:main. There’s a new build every day, so the image update notification is always (x). I want to fetch the new image, as the current image is detected as out of date.
Repro:

Click on the “Images” tab on the left
In the top “Pull image” section, click “🌐 Advanced Mode”
In the “Image” textbox, put in ghcr.io/fastenhealth/fasten-onprem:main
Click “Pull the image”

Expected Behavior
I expect the image to successfully pull.
Actual Behavior
I get an error:
Head "https://ghcr.io/v2/fastenhealth/fasten-onprem/manifests/main": denied: denied

Steps to Reproduce
As above.

Portainer logs or screenshots
No response
Portainer version
2.19.1
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
Docker version 20.10.23, build 876964a
OS and Architecture
Synology DSM 7.2-64570 Update 3
Browser
Google Chrome Dev 120.0.6062.2
What command did you use to deploy Portainer?
No response
Additional Information
No response

Does access to that image registry require authentication?
I note you're using a Synology NAS here - we're aware that Synology roll their own custom version of Docker on their DSM devices which have some unique behaviors, and this might be one of those.

I’m unaware of any registration required by that registry. Doing it from the commandline works, and I don’t have any registration set up there.

I've just tried this with Portainer CE 2.19.1 on a Synology DS220+ (DSM 7.2-64570 Update 1) and was able to pull the image you specified through Portainer without any issue. BE shouldn't be any different, but I'll give that a go shortly to confirm.
Is there anything in your network that might affect outgoing calls to ghcr.io?

To get your setup close to mine, set up a container with it, and then, when it’s marked as out of date, try going into Images and try to re-pull with Advanced mode.
A sample Compose setup:
version: '3.3'
services:
    fastenhealth:
        image: ghcr.io/fastenhealth/fasten-onprem:main
        volumes:
            - /volume1/docker/fastenhealth/db:/opt/fasten/db:rw
        restart: unless-stopped

I've now updated the Synology to DSM 7.2-64570 Update 3 (same as yours) and installed BE 2.19.1. I've deployed the stack as you described above and it launched successfully, so I'll check in on it tomorrow to see if an updated image is available and try and re-pull then. I made sure that I removed the local cached image before deploying, to make sure it was indeed still pulling.

Sorry for the delay - when I checked the following day there was no new image available. I've just looked now and there was a new version available, so I followed your steps:

Click on the “Images” tab on the left
In the top “Pull image” section, click “🌐 Advanced Mode”
In the “Image” textbox, put in ghcr.io/fastenhealth/fasten-onprem:main
Click “Pull the image”

This succeeded without any errors - the image pulled successfully.

:/
Are there logs or anything else I can share that will help diagnose the issue? I’m still seeing it.

Do you have any sort of outgoing proxy that might be interfering with the call? Do you have ghcr.io configured as a registry in Portainer (or in Synology's Container Manager)?
I'm not sure what could be causing this otherwise...

Come to speak of it, yes, I do have ghcr.io set up as a registry.

Would you perhaps be able to temporarily remove the registry configuration for ghcr.io and see if the problem still persists?

I removed the registry, but the issue remains.

Boo, I thought we might be on to something there.
I'm not sure where to go next on this unfortunately - as I can't reproduce the issue here it's hard for us to dig any further.

I’d be happy to provide logs or anything you want to help diagnose.

I’m seeing a similar issue with “Update Portainer”. There’s “New version available 2.19.4” in the lower left.  If I click “Start update” I get an error bubble in the upper right “image portainer/portainer-ee:latest not found on registry”.

I’m seeing a similar issue with “Update Portainer”. There’s “New version available 2.19.4” in the lower left.  If I click “Start update” I get an error bubble in the upper right “image portainer/portainer-ee:latest not found on registry”.

This is a separate and known issue with Synology's implementation of Docker. We don't have a fix for this yet but you can try manually pulling the portainer/portainer-ee:latest image first then trying the in-app upgrade again.


Remove _detach method

If there is no valid case why an element should not have a parentNode, _detach could be easily replaced with just element.parentNode.removeChild(element) to remove abstraction.
Current implementation of _detach:
/**
 * Detach element from DOM
 * @param {Element} element
 */
var _detach = function (element) {
  if (element.parentNode) {
    element.parentNode.removeChild(element)
  }
}

Was replaced by native .remove()


[AndroidTV] periodic microfreezes of frames on video_player, as well as on other players (for example, media_kit)

Steps to reproduce

Create an empty flutter project
Copy the code to the main.dart file
Add dependency "video_player: ^2.8.2" to pubspec.yml
Run the code on an Android TV device (I used HD Xiaomi Mi TV P1 32 (L32M6-6ARG), Android 9 (API 28), on an MSD6683 chip, Mali-470 video processor), but the problem is also visible on Android TV set-top boxes

Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:video_player/video_player.dart';

void main() {
  WidgetsFlutterBinding.ensureInitialized();
  runApp(
    const MaterialApp(
      // showPerformanceOverlay: true, // disabling performanceOverlay does not change the behavior of the player, the problem remains.
      home: MyScreen(),
    ),
  );
}

class MyScreen extends StatefulWidget {
  const MyScreen({Key? key}) : super(key: key);
  @override
  State<MyScreen> createState() => MyScreenState();
}

class MyScreenState extends State<MyScreen> {
  late VideoPlayerController _controller;

  @override
  void initState() {
    super.initState();
    _controller = VideoPlayerController.networkUrl(
      Uri.parse(
        'https://test-streams.mux.dev/x36xhzz/x36xhzz.m3u8',
      ),
    )..play();

    _controller.addListener(() {
      setState(() {});
    });
    _controller.initialize();
  }

  @override
  void dispose() {
    _controller.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return SingleChildScrollView(
      child: Column(
        children: <Widget>[
          Container(
            padding: const EdgeInsets.all(20),
            child: AspectRatio(
              aspectRatio: _controller.value.aspectRatio,
              child: Stack(
                alignment: Alignment.bottomCenter,
                children: <Widget>[VideoPlayer(_controller)],
              ),
            ),
          ),
        ],
      ),
    );
  }
}

Performance profiling on master channel

[X] The issue still persists on the master channel

Timeline Traces
Timeline Traces JSON
dart_devtools_2024-01-31_11_43_23.191.json.zip

Video demonstration

Video demonstration
(https://github.com/flutter/flutter/assets/62155164/1ccde618-6cf3-46e5-831c-3cc12ab1c367)

What target platforms are you seeing this bug on?
Android
OS/Browser name and version | Device information
HD Xiaomi Mi TV P1 32 (L32M6-6ARG), Android 9 (API 28), on an MSD6683 chip, Mali-470 video processor)
Does the problem occur on emulator/simulator as well as on physical devices?
Unknown
Is the problem only reproducible with Impeller?
N/A
Logs
Logs
flutter.profile.trace.skia.log.zip

Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.16.9, on Microsoft Windows [Version 10.0.17763.5329], locale ru-RU)
    • Flutter version 3.16.9 on channel stable at C:\Users\Alex\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 41456452f2 (5 days ago), 2024-01-25 10:06:23 -0800
    • Engine revision f40e976bed
    • Dart version 3.2.6
    • DevTools version 2.28.5

[√] Windows Version (Installed version of Windows is version 10 or higher)

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\Alex\AppData\Local\Android\sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[√] Android Studio (version 2023.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)

[√] VS Code (version 1.85.2)
    • VS Code at C:\Users\Alex\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.80.0

[√] Connected device (3 available)
    • MiTV MSSP2 (mobile) • <IP_ADDRESS>:5555 • android-arm    • Android 9 (API 28)
    • Windows (desktop)   • windows             • windows-x64    • Microsoft Windows [Version 10.0.17763.5329]
    • Chrome (web)        • chrome              • web-javascript • Google Chrome 120.0.6099.225

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Thanks for the report.
Although I don't have physical android tv device to verify the reported behavior on, but I tried on Android tv emulator and observed below:
https://github.com/flutter/flutter/assets/67046386/1e4e883a-5ac3-41ce-ac55-2d6f3b957ba9
It does show performance spikes as in the video above, but I ran it in debug mode and emulator doesn't properly simulate the performance.
Based on the timeline traces provided, I'll keep the issue open and label for team's input / attention. However, this doesn't seem to be specific to video_player plugin only as specified by OP. Other video players may show same behavior, but labeling as applicable.

Any ideas why this happens? at least in which direction to dig


Import docs from external repo

This is part of https://github.com/rancher-sandbox/cOS-toolkit/issues/1286. I'd like to first merge it in and see the preview on github and then update links to point to new URLs.
There are just few minor adaptations (e.g. now packages docs are generated from the tree, no checkout needed)
Signed-off-by: Ettore Di Giacinto<EMAIL_ADDRESS>

Not waiting for CI as it is unrelated. Will clean up makefiles in follow-ups, as I have already to update all links once its published


The property outside not propagated correctly on skeleton elements

Motivation and context
The issue reported by customer
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

Bug Fixes

Resolved an issue where the "outside" property was not being propagated correctly on skeleton elements.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.66%. Comparing base (6d49b89) to head (65880c4).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #8105      +/-   ##
===========================================
+ Coverage    83.63%   83.66%   +0.02%
===========================================
  Files          383      383
  Lines        40503    40502       -1
  Branches      3831     3830       -1
===========================================
+ Hits         33876    33887      +11
+ Misses        6627     6615      -12

Components
Coverage Δ

cvat-ui
79.73% <ø> (+0.05%)
:arrow_up:

cvat-server
87.26% <ø> (+<0.01%)
:arrow_up:


ZKP2P for Starknet

Preface
Exploration Hypothesis

Blockchain suffers from a problem: the lack of data portability. Currently, the most popular solution is the use of Oracles, an expensive solution that's impossible to scale, particularly for personally identifiable information (PII).
Aware of this situation, many projects have explored alternative approaches, and with the advent of zk-Proofs, one stands out for its potential: leveraging TLSNotary.
The idea is simple in theory: use TLSNotary to generate a zk-SNARK attesting to the veracity of information sent securely via TLS (TLS being the S in HTTPS).
For example, asking a notary to generate a zk-SNARK attesting that https://instagram.com sent me a web page containing my username in the header. Thus, I can prove to the blockchain that I indeed own this Instagram account. And thanks to the privacy offered by zk-SNARKs, the rest of the web page doesn't need to be revealed.
This technology opens the door to a sea of new possibilities, and the one we're going to explore with this project concerns onramp/offramp, as ZKP2P did on Base, by proving the existence of electronic receipts on-chain.
Scope

Building the smart contract responsible for managing the funds and verifying the proofs.
Design and develop a web client with a meticulously crafted UX.
Exploring avenues for improving the protocol by breaking down offramp requests into multiple smaller onramps, and by incorporating reserves in order to improve UX (as always).
Exploring ways to decentralise the notary entity.

Hypothesis Testing

The project should be evaluated with potential users to compare the new onramp/offramp process against the existing ones, assessing whether they offer an improved experience.
Architecture

Project Continuation

Giving the project to the zkp2p team
Building a startup from it. A straightforward business model would be to take fees. But in order to have a decentralised set or notaries, the project could also legitimately launch its own token.

Benchmarks

Gas fees during onramp/offramp

Name proposition: PicSouk (it involves money => picsou and it's decentralised => souk)


Go modules dependency fetching doesn't work

1:
>> go version
go version go1.14.1 linux/amd64

2:
>> git clone https://github.com/lalamove/konfig && cd konfig

3:
>> go mod download
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>invalid pseudo-version: version before v0.1.0 would have negative patch number

Hello, this is now fixed in #63


python311Packages.pytest-mock: 3.11.1 -> 3.12.0

Description of changes
Changelog: https://github.com/pytest-dev/pytest-mock/blob/v3.12.0/CHANGELOG.rst

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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.

Priorities
Add a :+1: reaction to pull requests you find important.

Superseded in #270457.


Windows Defender issue with .exe distribution

Windows threats neva.exe like a malware.
Solution - use https://github.com/mtrojnar/osslsigncode to sign binaries before publishing them.
See https://www.reddit.com/r/golang/comments/s1bh01/goexecutables_and_windows_defender/ for more info
Source: https://discord.com/channels/1094102475927203921/1094102475927203924/1215367559403282452

Microsoft Security Intelligence response is that:

submitted files do not meet our criteria for malware

Not sure if this will actually fix the problem tho. Maybe they only removed exactly that distribution and next versions will have problem again. Testing needed.


TST: add image baselines for PR 5036

In support to https://github.com/yt-project/yt/pull/5036

@chrishavlin or @matthewturk for review ?


QKC/OP Devs Meeting #15 Agenda

Meeting Info

Aug 24, 2024, 10:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress

Write a tweet about inbox contract https://x.com/qc_qizhou/status/1826315531714265377
Read the updates of OP including granite upgrade and interop
Review Po's code
Discussed with Alan about dynamic and static l1 attribute

Discussed with Qi and Mark about dynamic and static l1 attribute, seems there're some flaws with this design

Review Po's code https://github.com/ethstorage/optimism/pull/51
Study Dispute Game V2

Refactoring and Rewriting blockstm, split large structures, rearrange code structure and optimizations.
Research on Luban preconf design and rbuilder implementation.

Summary OP Stack Interoperability resources

Study how to implement multi-sec op-challenger
Review https://github.com/ethstorage/optimism/pull/51
Study Optimism audit report and our inbox contract


Add ids to question and use to select in relationships

What is the context of this PR?
Add an ID to questions and fieldsets and use the IDs to select question in relationships. This is to fix an issue in runner with we have when selecting this with a class as after the legend as a title changes the correct class is no longer being set at the relationship level.
How to review
Relationships still work as expected

 Change how question is selected in relationships

Wouldn't it be better to make these params with a default?

Yeah that would be a good idea normally, but in this case if those ids are set to something else when using relationships it would break the js


Plugin does not load correctly (at least in Godot4.3 betas)

Subj.
It seems they have made some changes / improvements in 4.3. Now I can observe the following scenario:

logger.gd is about to be added as autoload Log
however, while being parsed, it references Log which is not yet there
parsing fails
autoload is displayed as if it is there, but all other scripts using Log are now broken (they don't display in Inspector), because they reference logger.gd / Log which are not valid

This is not an issue if I replace Log in logger.gd with a reference to a static field, e.g.:
# Copyright (c) 2024 The gdlogging Contributors
# Inspired by https://github.com/KOBUGE-Games/godot-logger/blob/master/logger.gd
@tool
class_name CLog # <--- added class_name to reference static field
extends Node

# ...

static var _log_instance: CLog # <-- static field as an alterntative to referencing Log autoload

#...

	func write_bulks(p_log_records: Array[Dictionary], p_formatted_messages: PackedStringArray) -> void:
                # all Log.* references changed to CLog._log_instance
		CLog._log_instance._logger_direct_console.warning("LogSink: write_bulks() not implemented.")
#...

func _init() -> void:
	_global_broadcast_sink = BroadcastPipe.new()
	var log_formatter := LogRecordFormatter.new()
	_global_logger = Logger.new("Global", LogLevel.TRACE, log_formatter, _global_broadcast_sink)
	_logger_direct_console = Logger.new("gdlogging", LogLevel.TRACE, log_formatter, ConsoleSink.new())
	if Engine.is_editor_hint():
		add_sink(ConsoleSink.new())
	_log_instance = self # <----------------- added this line

I can not reproduce this issue with Godot Engine v4.3.beta2.mono.official.b75f0485b.

Hmmm, I also cannot reproduce it in clean project with v4.3.beta2.official [b75f0485b]. Maybe this is related to editor cache or something as on my main project this was blocking me (same Godot version).
Closing the issue for now, thank you for quick response


Investigate and replace GoogleVR code

The GoogleVR package included in Scripts/ThirdParty/GoogleVR  (GitHub, GoogleVR, Unity packages) is deprecated.

It is used for audio (see AudioManager) on all builds.
Supports some Google devices.

Since the package is deprecated we should look at replacing it. The new XR management plugin tries to delete it. See class XRLegacyUninstaller.
private static List<string> k_PackagesToBeRemoved = new List<string>(){
            "com.unity.xr.googlevr.android",
            "com.unity.xr.googlevr.ios",
            "com.unity.xr.oculus.android",
            "com.unity.xr.oculus.standalone",
            "com.unity.xr.openvr.standalone",
            "com.unity.xr.windowsmr.metro",
        };

What features are required to be replaced?
What is a good replacement?
How/when will replacement be done?

This is gone in XR v2 branch.


feat: select version parameter

This is a re-implement of #25.
Thank you to the original author. We wanted to refactor the orb and quickly release a major change with some upgrades without needing to ask contributors to make changes.
This PR adds a parameter to set the version of the serverless framework CLI to be installed. A new unit test was added to verify the install version.

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:ca182e676e7901b4234d19fa171d97a7fba4e47b

In testing, attempting to download version 2.72.3, the binary appeared to be downloaded but --version showed 2.72.2. Testing again with version3.15.0

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:026d3eba87b0ab624fc20610d49873f6bb8cf55b

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/serverless-framework?version=dev:266132eb8e02586e583671e188c0c4d0423e3c2c


Crash on Replace -c

Steps to reproduce:

Launch micro
Run replace with the -c flag.
Replace several instances in quick succession.

Micro crashes with the following error:
micro menu.go micro/cmd/micro/*
Micro encountered an error: runtime error: slice bounds out of range
runtime.errorString runtime error: slice bounds out of range
/home/zbyedidia/go/src/runtime/panic.go:489 (0x42a63f)
/home/zbyedidia/go/src/runtime/panic.go:35 (0x42932e)
/home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/search.go:103 (0x85c4a7)
/home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/command.go:511 (0x824cc0)
/home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/command.go:672 (0x825d1b)
/home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/actions.go:1375 (0x814b68)
/home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/view.go:475 (0x86abe4)
/home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/micro.go:479 (0x836b97)
/home/zbyedidia/go/src/runtime/proc.go:185 (0x42c42a)
/home/zbyedidia/go/src/runtime/asm_amd64.s:2197 (0x457411)

Commit hash: 53a19af
OS: Ubuntu 16.04
Terminal:  GNOME Terminal 3.18.3

I'm having trouble reproducing this. Could you provide an example file where you are experiencing this bug?

@zyedidia Hmm. I can't seem to be able to reproduce the crash either now that I try. At least I got the stack trace so you know approximately where there's some code that caused at least one crash.

Closing issue on account of being unable to reproduce error.


fix typos

fixed little typo in the delete account and sensor modals.

:tada: This PR is included in version 1.1.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


TRC Opens in Preview but fails in Tool

Description
Using the 4.0 GUI, I preview the experimental markers (static_post1.trc)— this opens in the GUI without an issue. Then, I open the included model and scale— using the included scale setup file. An error occurs and the message indicates the number of columns expected vs the number given is incorrect.
Expected result
I would expect that a file that I can preview in the GUI to be usable by the Tool. I use the Preview to test if files are 'readable' which seems to be a bad assumption now since the GUI and Tool use different parsers to read the file. Either the Previewer should throw the same exception as the tool, or the tool should use the same mechanism as the GUI.
Actual result
The Scaletool will send an exception saying the number of expected columns does not equal the number of given columns
Environment and GUI version
Error both on Windows and Mac. GUI.
marker_test.zip

Issue moved to opensim-org/opensim-core #2148 via ZenHub


Auto-loading new tweets in stream is not working

One of the highlights in the README is "Auto-loads new tweets in the stream if you're scrolled to the top. No more clicking "See 3 new Tweets"!", but it doesn't seem like that feature actually works. I'm currently in that state and could provide a screenshot - but don't think that'd be very helpful. Please let me know what additional info you need to debug further.

Are you scrolled all the way to the top?

Yes.

Windows
Chrome
Window is as wide as the feed and snapped

I've pushed out a new release which should be out within an hour that should fix the problem.

Awesome. What version should I look out for?

<IP_ADDRESS>0 (Versions are date-based)

Where can I find the version number of what I have installed? Chrome is showing me a semver version.

Mine pulled it in and fixed it. Its on the chrome://extensions/ page

you might have to check developer mode

Awesome. Yep, I was waiting on Chrome to update it. Didn't think to force the update. Have the correct version now - just waiting for a new tweet to roll in so I confirm the scenario. Thanks, @scttcper!

Confirmed. Thanks, @sindresorhus!


xtensa: log: add missing strdup

Fix missing log_strdup call
Signed-off-by: Sylvio Alves<EMAIL_ADDRESS>

Hm... these are fatal error log which means the logging subsystem is already in immediate mode (AFAIK). IIRC, there is no need to do strdup() when in immediate mode. Did logging complain about missing strdup()?

Hm... these are fatal error log which means the logging subsystem is already in immediate mode (AFAIK). IIRC, there is no need to do strdup() when in immediate mode. Did logging complain about missing strdup()?

Yes. Right after app crashes, it floods the terminal with lots of missing strdup(). This PR fixes that. However, I couldn't figure out whether it is ESP32 issue or general.

(Mine is a soft -1, btw.  No complaints about merging per se, I just don't think this is a root cause and want someone to figure out whether it is or not.  Feel free to override.)

@andyross, I guess it might related to ESP32 environment then. Let me re-check the linker script on logging stuff.
[00:00:00.617,000] <err> os:  ** FATAL EXCEPTION
[00:00:00.617,000] <err> os:  ** CPU 0 EXCCAUSE 28 (load prohibited)
[00:00:00.617,000] <err> os:  **  PC 0x400d153d VADDR 0xf0004
[00:00:00.617,000] <err> os:  **  PS 0x60f20
[00:00:00.617,000] <err> os:  **    (INTLEVEL:0 EXCM: 0 UM:1 RING:0 WOE:1 OWB:15 CALLINC:2)
[00:00:00.617,000] <err> os:  **  A0 0x8008af06  SP 0x3ffe7210  A2 0xf0004  A3 0x3ffc0ce0
[00:00:00.617,000] <err> os:  **  A4 0x60f23  A5 0x3ffc0bc8  A6 (nil)  A7 (nil)
[00:00:00.617,000] <err> os:  **  A8 (nil)  A9 0x3ffe71e0 A10 0x2c A11 0x120c
[00:00:00.617,000] <err> os:  ** A12 0x241 A13 0x7fff A14 (nil) A15 (nil)
[00:00:00.617,000] <err> os:  ** LBEG 0x400d1b80 LEND 0x400d1b8a LCOUNT (nil)
[00:00:00.617,000] <err> os:  ** SAR 0x19
[00:00:00.630,000] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:00.630,000] <err> os: Current thread: 0x3ffc08d0 (unknown)
[00:00:00.733,000] <err> log: argument 2 in source os log message " ** CPU %d EXCCAUSE %d (%s)" missinglog_strdup().
[00:00:00.805,000] <err> log: argument 1 in source os log message ">>> ZEPHYR FATAL ERROR %d: %s on CPU %d" missinglog_strdup().
[00:00:00.820,000] <err> log: argument 2 in source log log message "argument %d in source %s log message "%s" missinglog_strdup()." missinglog_strdup().
[00:00:00.820,000] <err> log: argument 1 in source log log message "argument %d in source %s log message "%s" missinglog_strdup()." missinglog_strdup().
[00:00:00.831,000] <err> log: argument 2 in source log log message "argument %d in source %s log message "%s" missinglog_strdup()." missinglog_strdup().

Yeah, the smoking gun is that the log subsystem is warning about its own log messages needing a strdup. :)
I don't know exactly how this is supposed to work, but I suspect it relies on string literals living in a specific address range that the linker tells Zephyr about.  My guess this is missing on esp32.

Hi, thanks for those inputs. In fact it is related to linker/rom area on ESP32.
I'll open a new PR once I get it fixed.


Investigate adding toByteBuffer() to Bytes

Something I though of while looking at #369.  Bytes could have a toByteBuffer() method that returns a read only ByteBuffer and does not copy the data.

This was done


Ladder: Character jerkily teleports towards  the center of the ladder in Dev branch

I think there is no need to teleport the player to the center.
We could instead allow the player to be in climb state as long as one is colliding.
Daisy Dangerous allows the player to climb the ladder as long as one is colliding withe the ladder and the game doesn't need the player centered in the ladder.
Or if you do want to be at the center you could slowly move the player in that direction.

Ok, so for this one I think that a simple "snap" bool on the ladder will do the trick.
if snap is turned on, the character snaps to the ladder's center, otherwise it just starts climbing wherever it grabbed on the ladder, wachu think @Logmytech ?

In case you do snap wouldn't it be cool to move very fastly to the center.
That would remove the jerky teleport.

I think this is fixed on https://github.com/pigdevstudio/platform_template/commit/910b0e7e0fe818062f4b41c41bac8700498df87c I won't add a smoothing when the snap config is turned on...snapping teleports to the snapping point, so not smoothing when snap is on. :laughing:


Converted film duration doesn't show on Tenet film page

I'm assuming this is to do with the Letterboxd easter egg that inverts the page once you scroll down to the bottom

Yup, the easter egg was messing with it (and it broke all of the custom tooltips)
Fixed with v3.11.0 released today for Chrome and Firefox


reproducible panic "dispatch dropped without returning error"

This panic affects 0.14 and master.
Minimal reproduction on master:
#[tokio::main]
async fn main() {
    let (mut request_sender, mut connection) =
        hyper::client::conn::http1::handshake(Io).await.unwrap();
    let request = hyper::Request::builder().body("".to_string()).unwrap();
    let response = request_sender.send_request(request);
    futures_util::pin_mut!(response);

    let _ = futures_util::poll!(&mut connection);
    std::mem::drop(connection);
    // this line panics
    let _ = futures_util::poll!(&mut response);
}

My fork has a runnable example at https://github.com/e00E/hyper/blob/panic-example/examples/panic.rs using an always pending IO implementation. Note that this branch also changes Cargo.toml. The panic can also be observed with real IO like tokio::TcpStream. I observed this panic in real code using reqwest and researched this issue afterwards.
On master the panic message is

thread 'main' panicked at 'dispatch dropped without returning error', /home/e/temp/hyper/src/client/conn/http1.rs:200:39

On 0.14. the panic message is

thread 'main' panicked at 'dispatch dropped without returning error', src/client/conn.rs:1023:39

The panicking code assumes that a channel is never dropped before a value is sent. However if proto::h1::dispatch::Client is dropped at the right moment this condition is violated. The problem is in src/proto/h1/dispatch.rs around line 580 (master and 0.14.x) this.callback = Some(cb);. The Callback is removed from the Envelope and stored in Client. If Client is then dropped the Callback and the contained Sender are dropped without sending a value.
I made a PR to master with a fix. https://github.com/hyperium/hyper/pull/3031 . The same fix also works on 0.14.x . We can discuss the master PR first and when it is good I can backport the change.
I am not very familiar with the hyper internals so there might be a better solution. I wasn't sure if the PRs should contain a test case and where it should reside, and whether the commit messages should include a full description of the issue.
I am unsure if http2 is affected. On master I see that we spawn a task on the executor that calls the callback. This seems problematic too because when the executor shuts down it will drop the task.

Fixed on 0.14.x by https://github.com/hyperium/hyper/pull/2790 .


Release 0.2.0-rc.1

What type of PR is this?

subproject management

What this PR does / why we need it:
This is "Release PR" for ICM Release 0.2.0-rc.1
Which issue(s) this PR fixes:
Related to #146
Special notes for reviewers:

The team agreed to proceed with a release candidate directly, bypassing the alpha release, given the stability and closed scope of the current state. See https://wiki.camaraproject.org/x/JYDcAQ for further details.
README.md - with the existing format in ICM there is no need to change anything.
CAMARA-AuthN-AuthZ-Concept.md is DEPRECATED and needs to be removed, but we should do it for the public release I think, not now for this release candidate "pre-release" (to avoid "breaking" the main branch now).
References in the released documents should always be links to a released version, not to the main branch. If the documents are released together, the links need to be updated at least within the release PR. But, same as previous point, we should do it for the public release, I think, and not now for this release candidate "pre-release" (to avoid "breaking" the main branch now).
CHANGELOG.md - Only the CHANGELOG file needs to be updated in the pre-release for now. Added all changes from the previous public release v0.1.0.

NEXT STEPS (edited by @hdamker):

Merge this PR when ready.
Merge #173 as agreed in the June 19 WG meeting call. → UPDATE (21/06): DONE
- Create release v0.2.0 branch: release-0.2.0-rc
Create a release v0.2.0-rc.1 tag for the latest commit.
Create pre-release v0.2.0-rc.1 in the github project (copy the section from CHANGELOG.md into the description)

NOTE: I will be on vacation for the next two weeks, I will need @AxelNennker, @sebdewet or other volunteers to continue this work for me. My goal is to merge this PR before I leave :) (fingercross)
Changelog input
ICM Release 0.2.0-rc.1

Additional documentation
https://wiki.camaraproject.org/display/CAM/Meta-release+Process#MetareleaseProcess-Milestoneactivities
https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24

@AxelNennker
a) there are three "hidden" suggestions in my review to be committed to update the remaining links
b) I've updated the description of the PR slightly to align it with the versioning and release process guidelines

For the release process, please add @camaraproject/TSC_participants to the reviewers of this PR.

@AxelNennker @jpengar Can one of you please merge this PR and create the pre-release in GitHub before today's AHC on 16:00? If you can't for some reason I offer to take it.

@jpengar Thanks! Looks good to me. I would just recommend to update the README.md and mention there the release candidate explicitly, maybe even replacing the link to "latest public release" v0.1.0, as now the v0.2.0-rc.1 is more important.

@jpengar Thanks! Looks good to me. I would just recommend to update the README.md and mention there the release candidate explicitly, maybe even replacing the link to "latest public release" v0.1.0, as now the v0.2.0-rc.1 is more important.

@hdamker @AxelNennker @sebdewet https://github.com/camaraproject/IdentityAndConsentManagement/pull/179 please review.


Actually use nextContext

This must be a bug, right? The intent is to pass the next context values, I assume.

woops hehe


Android Issue : sprite pink

I tried for many hours to find a solution but i'm out of ideas !
I'm working on Unity 2018, SpriteGlow 1.6 (and it's the same with 1.7).
I have the processing stack enabled on my project, and a sprite with a glow effect.
It's ok in my editor and in play mode and it's ok when I build for Windows, I can see the glow effect.
But when I build for Android and try the .apk on Android Studio, the sprite with the SpriteGlowEffect script is pink.
I manually added the shader Sprite/Outline in Graphics settings but no effect.
Do you have an idea ? Tthanks !

There could be shader errors or the shader itself is missing. Try reading the device logs to find out more.


Is there FormBuilderDropdown lazy loading items?

Hi,
I need that function which allow me to get the FormBuilderDropdown items when I tap/push on down-arrow in the side.
When it's dropping-down/opening, this should be call an HTTP request for the real/big FormBuilderDropdown-items.
BUT before it this need to show the initialValue!
Because of this error message I got all the time:
"There should be exactly one item with [DropdownButton]'s value: OPERATINGCURRENTACCOUNT. \nEither zero or 2 or more [DropdownMenuItem]s were detected with the same value"

Maybe you are receiving two instances of something that has the same value. i.e: ['Some Value', 'Some Value']


Update README.md

Updates the configuration section describing the environment variables and their default values.
Drive-by:

Fixes the Markdown lint violations and formats using prettier.

What this PR does / why we need it
Description
Which issue(s) this PR fixes (optional)
(optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged)*
Fixes #
Acceptance Criteria Met

[X] Docs changes if needed
[ ] Testing changes if needed
[ ] All workflow checks passing (automatically enforced)
[ ] All review conversations resolved (automatically enforced)
[ ] DCO Sign-off

Special notes for your reviewer:

I am not sure what I can do about the db-migrations test failing.

I am not sure what I can do about the db-migrations test failing.

I'm investigating it.

Thank you, @rgreinho, for the PR improving our doc. 🎉
Merging it. 🚀


Add try-catch around bonfire upgrade button presses

I ran into a condition in the fast-paragon experiments where all of the conditions in KS to push the aqueduct-to-hydroplant button were met, but the mustExist(getBuildButton(aqueduct)) failed. I think there is another condition before the game makes the upgrade button available. It might be having at least one miner, but I'm not exactly sure. For safety I added try/catch blocks around all of the bonfire upgrade operations. The catch just prints a console warning if the upgrade fails and KS should try it again in a future tick.

I'm sorry, but this issue will require a proper fix.

Here is a screenshot showing the debugger hitting the catch on the missing aqueduct build button. The game has not rendered the aqueduct button yet.

I'm guessing the missing condition is aqueductMeta.unlocked==true.


cventry subitem possible?

I would like to have a subitem under each item, so that I can elaborate a little more on each point (the system is huge and I have to break it down). Would that be possible in the current version?

#219

Thanks @xoac, seems to be answered effectively there; closing.


KAFKA-14208: Should not wake-up with non-blocking coordinator discovery

Today we may try to discover coordinator in both blocking (e.g. in poll) and non-blocking (e.g. in commitAsync) way. For the latter we would poll the underlying network client with timeout 0, and in this case we should not trigger wakeup since these are non-blocking calls and hence should not throw wake-ups.
In this PR I'm trying to fix it in a least intrusive way (a more general fix should be, potentially, to have two versions of ensureCoordinatorReady), since in our threading refactoring, the ensureCoordinatorReady function would not be called by the calling thread any more and only triggered by the background thread, and hence we would have a much simpler manner to ensure that non-blocking functions never throw wake-ups.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Call @philipnee @showuon for reviews.

@showuon Since Guozhang is out sick, I raised https://github.com/apache/kafka/pull/12626 which addresses your (and my) comments. Please take a look. I'll leave this open for now.

I'll go ahead and close this since we're going to merge https://github.com/apache/kafka/pull/12626.


Regarding the issue of camposes.

Why is there no roll input? If doing camera pose estimation, is it necessary to rotate the input image to make the roll zero?

I wasn't very clear about the campose code for these requirements before, thank you for letting me know


Performing JSInterop call during pre-rendering results in a null ref

@inject IJSRuntime JS
@code {
protected async Task OnInitializedAsync()
{
    await JS.InvokeVoidAsync("toString");
}

Expect: Pretty printed exception message that says you can't do this when the app is pre-rendering
Actual:
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime.BeginInvokeJS(Int64 asyncHandle, String identifier, String argsJson)
   at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](String identifier, CancellationToken cancellationToken, Object[] args)
   at Microsoft.JSInterop.JSRuntime.InvokeWithDefaultCancellation[T](String identifier, Object[] args)
   at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args)
   at BlazorApp2.Pages.Index.OnInitializedAsync() in C:\Users\prkrishn\source\repos\BlazorApp2\BlazorApp2\Pages\Index.razor:line 12

I don't know if there is another issue for this but I get the same exception even when I invoke js from OnAfterRenderAsync but only in a server-side project.
That doesn't seem right.. Shouldn't the pre-rendering already be done there?
I have a reusable component in a razor library:
@using Microsoft.JSInterop
@inject IJSRuntime jsRuntime

This is a js-interop test component.

@code{
    protected override async Task OnAfterRenderAsync()
    {
        string input = await jsRuntime.InvokeAsync<string>(
                "exampleJsFunctions.showPrompt",
                "Type something");

        Console.WriteLine(input);
    }
}

The js-code is just this:
window.exampleJsFunctions = {
  showPrompt: function (message) {
    return prompt(message, 'Type anything here');
  }
};

Consumed by a client side blazor application (without backend), everything works as expected.
However, when used in a server side blazor application, it results in the following exception.
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime.BeginInvokeJS(Int64 asyncHandle, String identifier, String argsJson)
   at Microsoft.JSInterop.JSRuntimeBase.InvokeAsync[T](String identifier, IEnumerable`1 args, CancellationToken cancellationToken)
   at Microsoft.JSInterop.JSRuntimeBase.InvokeWithDefaultCancellation[T](String identifier, IEnumerable`1 args)
   at SampleLibrary.Component1.OnAfterRenderAsync() in C:\StaticAssetsTest\SampleLibrary\Component1.razor:line 9
   at Microsoft.AspNetCore.Components.Rendering.HtmlRenderer.HandleException(Exception exception)
   at Microsoft.AspNetCore.Components.Rendering.Renderer.AddToPendingTasks(Task task)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.SetDirectParameters(ParameterView parameters)
   at Microsoft.AspNetCore.Components.Rendering.Renderer.RenderRootComponentAsync(Int32 componentId, ParameterView initialParameters)
   at Microsoft.AspNetCore.Components.Rendering.HtmlRenderer.CreateInitialRenderAsync(Type componentType, ParameterView initialParameters)
   at Microsoft.AspNetCore.Components.Rendering.HtmlRenderer.RenderComponentAsync(Type componentType, ParameterView initialParameters)
   at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<>c__11`1.<<InvokeAsync>b__11_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.ViewFeatures.RazorComponents.StaticComponentRenderer.PrerenderComponentAsync(ParameterView parameters, HttpContext httpContext, Type componentType)
   at Microsoft.AspNetCore.Mvc.Rendering.HtmlHelperRazorComponentExtensions.RenderStaticComponentAsync[TComponent](IHtmlHelper htmlHelper, Object parameters)
   at WebCore_SS.Pages.Pages__Host.<ExecuteAsync>b__10_1() in C:\StaticAssetsTest\WebCore_SS\Pages\_Host.cshtml:line 18
   at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperExecutionContext.SetOutputContentAsync()
   at WebCore_SS.Pages.Pages__Host.ExecuteAsync()
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync(IRazorPage page, ViewContext context)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync(IRazorPage page, ViewContext context, Boolean invokeViewStarts)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|29_0[TFilter,TFilterAsync](ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.SetRoutingAndContinue(HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

This always occures when directly going to the page this component is on. If you navigate there later using a NavLink it won't occur.
FYI I have also noticed the exact same behaviour when using OnInitializedAsync, CS works and SS doesn't.
So there are two issues:

Same as the orignal issue here, it doesn't show a user-friendly exception.
It happens even when using AfterRender which I would assume is executed after any (pre-)rendering is done.

Another option is to check if the client connection is already established, like below shows:
@page "/"
@using Microsoft.JSInterop
@inject IComponentContext ComponentContext
@inject IJSRuntime jsRuntime

This is a js-interop test component.

@code{

    protected override async Task OnAfterRenderAsync()
    {
        if (!ComponentContext.IsConnected) return;

        string input = await jsRuntime.InvokeAsync<string>(
                "exampleJsFunctions.showPrompt",
                "Type something");

        Console.WriteLine(input);
    }
}

You can refer to https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-3.0#server-side for the detail.


[WIP] [ITensorGPU] [ENHANCEMENT] Fix circuit AD on GPU

Description
This PR is meant to fix doing automatic differentiation of a circuit simulation with MPS/MPO on GPU, including PastaQ's runcircuit.
There were a few MPS/MPO functions that weren't differentiable, including ones for transferring MPS/MPO back and forth between CPU/GPU.
In the process, I also simplified some of the GPU code, for example I rewrote the MPS/MPO constructors to just call the CPU versions and then transfer the results to GPU. I think the tradeoff of any performance issues with that (if there are any) are outweighed by the code simplification.
Minimal demonstration
[YOUR MINIMAL DEMONSTRATION OF PREVIOUS BEHAVIOR]

How Has This Been Tested?
Need to add tests, possibly including doing AD of PastaQ.runcircuit on GPU.
Checklist:

[x] My code follows the style guidelines of this project. Please run using JuliaFormatter; format(".") in the base directory of the repository (~/.julia/dev/ITensors) to format your code according to our style guidelines.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have added tests that verify the behavior of the changes I made.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] Any dependent changes have been merged and published in downstream modules.

Codecov Report

Merging #956 (1ebd381) into main (22f6950) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

:exclamation: Current head 1ebd381 differs from pull request most recent head f9ea5e6. Consider uploading reports for the commit f9ea5e6 to get more accurate results

@@            Coverage Diff             @@
##             main     #956      +/-   ##
==========================================
- Coverage   67.14%   67.07%   -0.07%
==========================================
  Files          88       88
  Lines        9395     9403       +8
==========================================
- Hits         6308     6307       -1
- Misses       3087     3096       +9

Impacted Files
Coverage Δ

src/ITensorChainRules/mps/abstractmps.jl
88.37% <0.00%> (-10.33%)
:arrow_down:

src/mps/abstractmps.jl
85.13% <0.00%> (ø)

src/ITensorChainRules/ITensorChainRules.jl
84.61% <0.00%> (-7.70%)
:arrow_down:

src/Deprecated/autompo/opsum.jl
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

@kshyatt the main changes here to ITensorGPU are:

A more generic cu function built on top of Adapt.adapt and Functors.fmap (and more generally, making ITensor objects compatible with Adapt.jl). This also includes some better functionality for adapting the element type and storage/data types in general.
Simplify the ITensorGPU MPS/MPO constructors by just calling the CPU versions and then moving the result to GPU. That seemed to basically be what the previous versions were doing anyway.
Use the new adapt functionality to make expect and correlation_matrix work on GPUs. The basic issue with the previous version was that op creates ITensors on CPU by default, so then when you try to contract them with the MPS tensors which are on GPU it throws an error since we don't support contract CPU and GPU ITensors (I've also improved the error message when trying to contract CPU and GPU tensors together). The fix here is to use adapt to adapt the data type of the ITensor built with op to the data type of the tensors of the input MPS. We could consider adding support to op where you can input a custom data type (so op(Vector, "Sz", s, 1) if you want it on CPU and op(CuVector, "Sz", s, 1) if you want it on GPU but I'll leave that for a future PR).
Better handling of EmptyStorage with CuVector data types.

There is a lingering question I have with the cu function that the CUDA.cu function moves the data to GPU and also converts to single precision, whereas the design in ITensorGPU is that for ITensor objects it preserves the precision of the input. Maybe we can consider using the behavior of CUDA.cu in the future to make things consistent (I'm imagining a case where we have some code that mixes ITensor objects with Julia Arrays or Flux objects and it may confusing if they have different behavior).
Anyway, I'll merge this when tests pass since I want to work on some things that make use of this PR, most of this is behind the scenes and can be changed in the future if needed.


Spells / Items

Just a note to be careful that you are not including non SRD spells / items as it is a no no. :)

I have confirmed with both Nath and Atropos on this and am under strict instructions :)


windows: pipx installed meltano can not find meltano dependency example gunicorn

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3483
Originally created by @BuzzCutNorman on 2022-05-12 17:30:19

What is the current bug behavior?
pipx installed meltano is not able to find dependent packages like gunicorn.
What is the expected correct behavior?
I am expecting pipx meltano to be able to find dependent packages like an it does in a manually created python enviroment with pip installed meltano.
Steps to reproduce
pipx meltano FileNotFound steps
pipx install meltano
meltano init meltano-demo
cd meltano-demo
meltano ui

python venv pip meltano file found ran and crashes on ModuleNotFoundError
python -m venv .\.venv\meltano
.\.venv\meltano\Scripts\Activate.ps1
pip install meltano
cd meltano-demo
meltano ui

Relevant logs and/or screenshots

Possible fixes
The fix is that in the meltano_invoker it searches for exact file name in the active python environment but in windows these files have a .exe at the end so the file search fails.  The command is run hoping it is in the path but the only path pipx give it to the users .local\bin that does not contain all the dependent packages so the application doesn't run.
Further regression test
Ensure we automatically catch similar issues in the future

[ ] Write additional adequate test cases and submit test results
[ ] Test results should be reviewed by a person from the team

View 2 previous comments from the original issue on GitLab


[Blog] - Python Automation API

Proposed changes
Python Automation API blog post
Related issues (optional)
Resolves: https://github.com/pulumi/pulumi/issues/6126

I would rather this be a discrete article instead of redirecting readers to another article to see updated examples. Happy to do the work to coalesce the python examples into this post.

I removed updated this so it's just an update of the original blog post.


Exclude owned types

You should change line 15 in ModelBuilderExtensions.cs to the following:
var entityTypes = modelBuilder.Model.GetEntityTypes().Where(e => !e.IsOwned()).ToList();
Otherwise, using owned types and UseTemporalTables() gives you the following exception:
System.Data.SqlClient.SqlException: 'Cannot find the object "dbo.EntityType._OwnedType" because it does not exist or you do not have permissions.'

Point taken, thanks for the suggestion!


Bug to generate the URL to visualize the diff between versions in changelog

The script to update the file CHANGES.md is buggy. For example, when using it for creating 4.1.0, it yielded the following line:
## 4.1.0 (2019-10-28)
[View detailed changelog](https://github.com/neuropoly/spinalcordtoolbox/compare/v4.0.0-beta.3...4.1.0)

whereas the changelog should point to the following diff: 4.0.1...4.1.0
To reproduce:
$SCT_DIR/python/bin/python $SCT_DIR/install/sct_changelog.py

Fixed by removing all tags starting with "v" in the main repository.

tags were restored (because they were associated with specific release). So the issue remains.


Bad result

excuse me, I get this error when I try demo.py, how can i solve the problem? thanks
tensor(5.7164e+05): wipe alive receiver doing wipe alive payer wipe [ pontoon ]
tensor(2.9898e+05): wipe [ jetliner ] skating corsage wipe thermos doing wipe [ macbook ]
.....
tensor(3.6977e+05): wipe straining rubs crotch doing wipe [ ski ] rubs crotch payer wipe [ ski ] rubs standing
saving...
Traceback (most recent call last):
  File "demo.py", line 255, in <module>
    if opt.att_model == 'topdown':
  File "/opt/conda/lib/python3.6/json/__init__.py", line 179, in dump
    for chunk in iterable:
  File "/opt/conda/lib/python3.6/json/encoder.py", line 428, in _iterencode
    yield from _iterencode_list(o, _current_indent_level)
  File "/opt/conda/lib/python3.6/json/encoder.py", line 325, in _iterencode_list
    yield from chunks
  File "/opt/conda/lib/python3.6/json/encoder.py", line 404, in _iterencode_dict
    yield from chunks
  File "/opt/conda/lib/python3.6/json/encoder.py", line 437, in _iterencode
    o = _default(o)
  File "/opt/conda/lib/python3.6/json/encoder.py", line 180, in default
    o.__class__.__name__)
TypeError: Object of type 'Tensor' is not JSON serializable

I have solved it.
add .item() function to the code:
entry = {'image_id': img_id[0].item(), 'caption': sents[0]}

The results are very bad.
Why the demo.py generates captions like this?

I also have very similar result,  the result is very bad.
what does wipe mean here? it seems there are so many wipe appearing

I think the pre-trained weight is not right. When I use the pre-trained model for evaluation, the BLEU4 and Cider is so bad. But After training my model without pre-trained weights which they provided, the result is good.


NEW: add "opera" and "edge" support for shared browser

Resolves gh-421

Codecov Report

Merging #422 (5db3575) into master (6c1bb5f) will decrease coverage by 0.17%.
The diff coverage is 73.33%.

@@            Coverage Diff             @@
##           master     #422      +/-   ##
==========================================
- Coverage   62.67%   62.50%   -0.18%
==========================================
  Files          35       35
  Lines        2015     2024       +9
  Branches      153      153
==========================================
+ Hits         1263     1265       +2
- Misses        721      726       +5
- Partials       31       33       +2

Impacted Files
Coverage Δ

selene/support/shared/config.py
85.71% <73.33%> (-1.49%)
:arrow_down:

selene/core/condition.py
81.92% <0.00%> (-2.41%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Generic MJPEG Camera does not close connections

Home Assistant release (hass --version):
0.51.2
Python release (python3 --version):
Python 3.4.2
Component/platform:
Generic MJPEG Camera
Description of problem:
When a user opens camera stream in UI HASS opens a connection to the camera. But these connection is not closed once preview is closed in UI. In fact, it is never closed.
If a user closes and opens camera stream from time to time, the number of opened connections grows until camera connections limit is reached.
Expected:
HASS should close a connection once the stream view is closed in UI.
Problem-relevant configuration.yaml entries and steps to reproduce:
camera:
  - platform: mjpeg
    mjpeg_url: !secret camera0_url
    name: camera0

The camera is a USB camera served with motion daemon
netstat output:
tcp        7      0 <IP_ADDRESS>:8081            <IP_ADDRESS>:*               LISTEN
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:34206     ESTABLISHED
tcp      167      0 <IP_ADDRESS>:8081       <IP_ADDRESS>:49902     CLOSE_WAIT
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:34484     ESTABLISHED
tcp      148      0 <IP_ADDRESS>:8081       <IP_ADDRESS>:49948     ESTABLISHED
tcp      148      0 <IP_ADDRESS>:8081       <IP_ADDRESS>:49864     ESTABLISHED
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:36064     ESTABLISHED
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:35248     ESTABLISHED
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:56614     ESTABLISHED
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:35580     ESTABLISHED
tcp      148      0 <IP_ADDRESS>:8081       <IP_ADDRESS>:49860     ESTABLISHED
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:35414     ESTABLISHED
tcp      148      0 <IP_ADDRESS>:8081       <IP_ADDRESS>:49870     ESTABLISHED
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:35772     ESTABLISHED
tcp      166 130320 <IP_ADDRESS>:8081       <IP_ADDRESS>:34442     ESTABLISHED

UI screenshot (once limit is reached)
https://www.dropbox.com/s/4lh6wrxjoe9cx0k/Screenshot from 2017-08-24 09-26-38.png?dl=0

Well that certainly explains why my mjpeg camera stops serving quite regularly. Going to subscribe to this issue to see its outcome.


Consider renaming actions-performed-by-role

Lovely work and very clean and understandable code.
May I suggest renaming actions-performed-by-role. I immediately assumed that it would return the actions actually performed by a certain role, as opposed to the actions allowed by a specific role. This especially because of actions-performed which returns all performed actions.

Thanks!
I totally agree. How about 'actions-allowed-by-role'?

That's spot on I think.
On Mon, Jun 17, 2019 at 10:22 PM Morgan Bentell<EMAIL_ADDRESS>wrote:

Thanks!
I totally agree. How about 'actions-allowed-by-role'?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/agentbellnorm/dativity/issues/1?email_source=notifications&email_token=AAAPUXA3EEC3XUL7FLRSHZLP27W6ZA5CNFSM4HWWH45KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX4KYYI#issuecomment-502836321,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPUXBCKPWCATRTFO7DM5TP27W6ZANCNFSM4HWWH45A
.

Implemented in 2.0.0
Closing the issue.


Use TypeScript for the Quickstart page

Hi,
since AtScript is TypeScript now, I think we should use TypeScript in the example on https://angular.io/docs/js/latest/quickstart.html so we don't need an explanation of AtScript and es6-shim.

:+1:

Hell all,
Right now we're waiting on TypeScript 1.5 which will have the features needed to fully drop AtScript in Angular 2.
The example in the quickstart will be valid TypeScript once 1.5 releases. The only change that will be needed is dropping the traceur/es6-shim setup in favor of the TypeScript compiler. The code should stay the same.
Once TypeScript 1.5 releases we'll update the quickstart. Until then it's not completely truthful to use TypeScript in the code samples.

This sounds very reasonable :-) looking forward to TS 1.5 then. Thank you very much.


Unable to get the Guild members

func messageCreate(s *discordgo.Session, m *discordgo.MessageCreate) {
	g, err := s.State.Guild(m.guildID)
	if err != nil {
		fmt.Println(err.Error())

	}
	fmt.Println(g.Members)
}

Not at all getting guildmembers as when I am trying to get guild member count  then it shows 0 as output , May I know how do I use guildMembers
Thank you

As @Nv7-GitHub stated above, List Guild Members is a privileged intent. See my other answer here for more info


Cannot switch to old mode now.

I am trying to upload file using piping from request stream to ftp put socket stream.
In resume  I got
Error: Cannot switch to old mode now.
    at emitDataEvents (_stream_readable.js:748:11)
    at IncomingMessage.Readable.resume (_stream_readable.js:733:3)

ftp.getPutSocket(remotePath, function (err, writableSocket) {
   writableSocket.on('close', function (err) {
         if (err) return callback(err)

         pool.release(ftp)
         return cb()
   })

   req.pipe(writableSocket) // Transfer from request to the remote file
   req.resume(writableSocket) // ERROR Cannot switch to old mode now.
})

I am not sure how can I use it right way.
Node v0.10.30

Hi! Thanks for this report, as it lead to fixing a potential bug in jsftp. As for your code, req.pipe should already resume the stream, so there is no need to use the req.resume(...). A semi-explanation of what's happening is here: https://nodejs.org/api/all.html#all_class_stream_readable and here: http://stackoverflow.com/questions/18306954/cannot-switch-to-old-mode-now-node-js-apn-module-error-in-tls-connect-functi
Of course, switch to Node.js 0.12 or 4.x if you can. Apparently they handle this situation more gracefully.
Let me know if that helps, and if it doesn't please reopen the issue!