Add CLIENT_PUBLIC_PATH env var

I'm running this in docker. On my host, I connect to the container using a hostname like myproject.docker. Inside the container, the app has to listen on <IP_ADDRESS>.
Currently, if I set the HOST env var, it tries to listen on a non-existent host:
Error: Could not find an open port at myproject.docker.
Network error message: getaddrinfo ENOTFOUND myproject.docker

    at detect.then.err (/var/www/html/razzle/packages/razzle/node_modules/react-dev-utils/WebpackDevServerUtils.js:420:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:118:7)

By adding this CLIENT_PUBLIC_PATH env var, I can leave HOST at the default, and use the new env var to tell the client where to connect.

@jaredpalmer could you reopen this? I'm hoping to get it merged in, and would be happy to make any changes necessary.


Create a label-blocker plugin to prevent the manual addition of certain key labels

Feature Request

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

Which project: TKV

Describe the feature you'd like:
Create a label-blocker plugin to prevent the manual addition of certain key labels.
For example:
We do not want collaborators to manually add status/can-merge label.
Do you have any ideas on how to implement it?(Optional)

cc: https://github.com/ti-community-infra/configs/discussions/101#discussioncomment-275981

cc: https://github.com/ti-community-infra/configs/discussions/101#discussioncomment-275981

/cc @Mini256
What do you think?

/cc @Mini256
What do you think?

I think it's necessary, but we have to find a way to achieve it.

I think it's necessary, but we have to find a way to achieve it.

/close by https://github.com/ti-community-infra/tichi/issues/258

/close by https://github.com/ti-community-infra/tichi/issues/258

/close
by #258

/close
by #258


Replace Bitcoin Connect with custom invoice payment component

Bitcoin Connect does not properly fit this usecase. We can just show a QR and copy button (similar to the onchain deposit component we have) . Also, we should clearly add a link to a guide if a user does not know how to pay the invoice.
In the guide we can include different ways to topup (e.g. pay with lightning from an exchange)

@jpl-btc can you help us prepare a guide for this?

@jpl-btc created a guide: https://guides.getalby.com/user-guide/alby-account-and-browser-extension/alby-hub/wallet/open-your-first-channel

idea: same style as the onchain QR on the deposit page, but directly below the QR add a clear "Learn about ways to pay" link which goes to the above guide.

The guide, while published, is still in draft form and has room for improvement.
I'd like to propose two ideas:

Add a "Help" button on both pages of the flow to assist users if they encounter issues. This button would redirect users to the "Open Your First Channel" guide. Each button will have context-specific copy that suits the user’s current environment, even though both link to the same guide: "What is this page, Learn more!" | "Unsure of this QR code? Find out!" -> the buttons should be visible for them to "work" and be clicked, perhaps a little bit of gray on the backround of the text, inside the button. something aligned with the current theme of course.

Move all bottom buttons closer to the channel creation steps. On the first page, these buttons should be nearer to the "Next" button (they’re barely visible now). On the second page, they should be closer to the QR code... especially the new button "Unsure of this QR code? Find out!" that links to the Open your first channel guide.

Here is a screenshot with the idea;

@jpl-btc looks good (I think the "Unsure about this QR code" should look more like a clickable link ).You said you'd try work on this, right? it would be good to look at the onchain deposit page to get an idea of how the onchain QR code is implemented (since that is without bitcoin connect)


ContextualLexer/UnexpectedInput puppet

This is the start of a solution for the bug report that came up in the gitter.im chat. Note that this does really solve it! It is still impossible (I think) to actually skip over UnexpecedCharacters (or the Tokens the ContextualLexer creates from them).
Also, the tests fail with a for me not understandable error message.

Regarding the design, what if we define a "Resumeable" interface that both the lexer and parser adhere to?
Something like
class Resumable:
    def get_resumable_capsule(self):
        "Returns a capsule of data for resuming self"
        pass

    @classmethod
    def resume(cls, capsule):
        "Resume execution from given point"

...

class ContextualLexer(Resumable):
    ...

class LalrParser(Resumable):
    ...

Something like that. What do you think?

But the intersting aspect would be how to modify this resumable State. For the parser, we can just use the Puppet with a few modifications (maybe scrolling back might be interesting? For discarding open brackets or something).
The Lexer State should also be relativly simple to create an interface for.
But yes, the seems like a great idea.

Perhaps a similar LexerPuppet with methods like "feed_text", "move_cursor", etc.

Context:
MegaIng @MegaIng Aug 14 13:18
from lark import Lark

grammar = """
start: A+
A: "a"
"""

def handle_undefined(e):
    return True

parser = Lark(grammar, parser='lalr')

tree = parser.parse("aabab", on_error = handle_undefined)
print(tree)

Will simple stop parsing without any kind of error message
(and only return the tree till the first b)
(assuming you are using my PR)
Erez Shinan @erezsh Aug 14 13:37
Right, because the UnexpectedCharacters exception interrupts the lexer loop, the stream to the parser ends. There is no mechanism to tell the lexer to continue lexing from where it stopped
So it seems that we have to either add a "resume" mechanism to the lexer, or transmit the error to the parser without raising (by yielding the exception?)
Resuming shouldn't be too hard, I think. You just have to save the LineCounter and pass it back to the lexer when it resumes. (Unless I'm forgetting something)
But both (resuming vs. yielding error) seems like reasonable and actionable solutions to me
MegaIng @MegaIng Aug 14 14:06
The problem with yielding is that I am not sure how to best pass information about skipped characters. As example, we want to skip the rest of the line, how do we pass that information to the lexer?
This should be simple for the developer to modify, depending on all available information (state, value_stack, accepted, ...)
(And I am still thinking about revamping a bit of the lexer infrastructure to allow custom contextual lexer. This could also be used to allow lexer that return an object, and not a function generator, allowing for inspection/overriding of the lexer state)

Better progress in #700.


Implement custom blocks for end users

For certain use cases it'd be great to provide a way for users to mix in a handful of their own components to the Blocks editor. We want something that essentially "Just Works" for most components, and complex needs for users can be addressed using a custom plugin.
To start I think we should only focus on block-level custom components to keep things as simple as possible for this MVP.
The API should be simple and declarative. Perhaps something like?:
<Editor theme={theme} components={components} />

In order to work with Slate we need to handle a handful of things that are required to integrate into our implementation of the editor.
Component controls
We can leverage something like propTypes or propertyControls which determine the props that can be changed and what their dials/knobs might look like.
Depending on the amount of controls and properties allowed, we can open up the inline editor like links/images.

If there are many properties that are editable we can expose a sidebar like the theme editor.
If a component accepts children it can then be edited within as though it's the editor itself.

The output MDX will look something like:
# Hello, *world*!

<TomatoBox>

## Here's some editing

Inside our custom `TomatoBox` block!

<YouTube videoId="4fHw4GeW3EU" />

</TomatoBox>

And more stuff!

In addition to editing the components, the toolbar will need to know what components have been passed and expose them in the toolbar (perhaps in a custom component dropdown or expandable sidebar).
Commands
We'll need to be able to expose Slate commands so we can insert/toggle components that are in context for when they're clicked. Toggle will be for elements that accept children. Insert for void elements.
Rendering
In node rendering we will have to check the block type against available components and render them when relevant. If nothing exists, we return next() since there might be a plugin that handles the rendering of that node.
Serialization
This is probably the trickiest piece, but one I think that we have almost there. We have to be able to read in custom components as JSX nodes in the MDX and map them to blocks. This means that the serializer will have to know. Here's a test showing part of that functionality.
If it's not a component that it knows about, it sets it as a jsx block (for the live editor).
In addition to handling MDX => Slate schema, we need to go the other direction. This part could be a bit tricky since the serializer needs to know, ahead of time, the component block type. One potential way to do that is to add some type of private prop __BLOCKS_COMPONENT_NODE__: true with a catch all matcher at the end of the serializer.
If we end up there and the props exist we know to write out as JSX.
Schema definition
If a component is a void component we will need to specify that in Slate. Currently the schema looks like:
import { Block } from 'slate'

export default {
  document: {
    last: { type: 'paragraph' },
    normalize: (change, { code, node }) => {
      switch (code) {
        case 'last_child_type_invalid': {
          const paragraph = Block.create('paragraph')
          return change.insertNodeByKey(node.key, node.nodes.size, paragraph)
        }
        default: {
        }
      }
    }
  },

  blocks: {
    image: {
      isVoid: true
    },
    hr: {
      isVoid: true
    },
    YouTube: {
      isVoid: true
    },
    Gist: {
      isVoid: true
    }
  }
}

We will likely need to have some sort of static property in user components that we can use to extend the config. We could also potentially check in propTypes to see if children is accepted as a prop.

I think these are all the pieces we need. Am I missing anything @jxnblk?

This sounds like it covers most of the bases. Here's a few thoughts:
// I don't think there's much value in using context here
<Blocks.Provider theme={theme} blockComponents={components}>
  <Blocks.Editor />
</Blocks.Provider>

// E.g. using props seems more standard/straight-forward
<Editor theme={theme} components={components} />

As for the schema and serialization, I think it could make sense to treat all blocks as the jsx type in the Slate schema, and use an addition data.type property or similar to add the root component name, which can be checked against the components provided to the Editor. If we're talking about using static properties to define the shape of the editing forms anyway, we'll need to check that in the runtime. We probably will still need someway to know whether a JSX block accepts children or not though... I think I have enough to put together a proof of concept of this if this doesn't make sense

Updated the proposed API to <Editor theme={theme} components={components} /> 👍

In order to make things simpler we're now opting (as of #17) to only use two custom block types: jsx and jsx-void which a block extends. The metadata needed for rendering and exposing the form can be added to the node's data field.
{
  type: 'jsx-void',
  data: {
    type: 'YouTube',
    props: {}
  }
}

Addressed by #17 and #19


Adding Gherkin-like feature set, see #50

WIP at the moment - relates to #50

Coverage decreased (-3.5%) to 96.538% when pulling 40e398993a92c9a5217d510a394f7fbaea192f4f on ashleyfrieze:af-bdd-1 into 782fd7a7251feb34010fbf5f972d34b66c14c29f on greghaskins:master.

Odd build problem:
"test -z \"$(git status --porcelain)\""

is failing, but the code MUST all be checked in, or how would it have gotten there! Unless there's something funny in your gradle that's rewriting files.

Instead of failing on style rules, I try to have the build fix things itself where possible (indentation, etc). This error means you have not checked in the "final" version of those files (unstaged local changes). ./gradlew clean build is the source of truth; you'll be good on CI if you commit after that runs green.

As I feared, running gradle under Windows has caused the files to have their CRLFs mangled. Yuck.
Any idea how to tell gradle not to be so annoying? Or do I have to do my final commits on a Linux command line...?

Ahaha! I added a .gitattributes file to control EOL - this means that dumb collaborators like me have less chance of breaking the merges when Spotless rewrites the files.

Coverage decreased (-0.4%) to 99.623% when pulling 900e7b9ac124360f0efc87f403fc6f2a92ee3882 on ashleyfrieze:af-bdd-1 into 782fd7a7251feb34010fbf5f972d34b66c14c29f on greghaskins:master.

Getting that build to pass was extremely time consuming... We're there now! Yay. Coverage is basically 100%.
Not ready for check-in yet. Any feedback gratefully received. Going to look at more stuff relating to ignoring and tagging, since my aim for this is to be able to substitute this for Cucumber in terms of BDD expressiveness and usage in a complex test suite.

BTW style rules that fail builds because of full stops in JavaDoc... :(

Coverage decreased (-0.7%) to 99.281% when pulling 73184fb24195c99479e0202f79cf8d456f57f108 on ashleyfrieze:af-bdd-1 into 782fd7a7251feb34010fbf5f972d34b66c14c29f on greghaskins:master.

I think there's a risk of dissonance between my just-submitted ignore mechanism vs the xit/xdescribe technique already present. Given the requirement for both backwards compatibility and similarity to other frameworks, I think the x/f class of functions should be a thing in their own right. The more JUnit-like ignore function is itself a warm-up for the tagging capability I'm about to add.

Coverage decreased (-0.4%) to 99.635% when pulling c80bfc15103b5b624ebef1c29fbdf589bd209815 on ashleyfrieze:af-bdd-1 into 782fd7a7251feb34010fbf5f972d34b66c14c29f on greghaskins:master.

Coverage decreased (-0.4%) to 99.636% when pulling 09910dbd63b602c0967525d0e9c782ef42209a80 on ashleyfrieze:af-bdd-1 into 782fd7a7251feb34010fbf5f972d34b66c14c29f on greghaskins:master.

Coverage decreased (-0.3%) to 99.698% when pulling f5d2af8d1ac4d1f4239b9dc131939cde9e8d6999 on ashleyfrieze:af-bdd-1 into 782fd7a7251feb34010fbf5f972d34b66c14c29f on greghaskins:master.

Tagging functionality now provided. This adds onto the general purpose ignore feature. It allows suites and specs to be given a series of tags and for them to be selected for running based on those tags. Example usage would be to mark a specific suite as WIP and add something to the system properties to either not run it or ONLY run it. This is a bit like the focus feature or the temp ignore feature. It's stronger because it might allow you to configure CI never to run WIP tests, or configure separate categories of tests to run in different builds.

Coverage decreased (-0.3%) to 99.708% when pulling ecff7d28fdb60b27c6c77bf3a230e4ba89b81c9e on ashleyfrieze:af-bdd-1 into 782fd7a7251feb34010fbf5f972d34b66c14c29f on greghaskins:master.

@greghaskins I'm basically done with the Gherkin/Cucumber type features. I have already prototyped getting JUnit rules into the code, so would like to have a crack at doing that properly. It makes sense for me to branch off from this code to do it, but that's going to be self-defeating if, in code review, you come up with some major changes.
Do you think you'll be able to give this PR a quick review so I can see whether I should delay the next step?

Sure. I'll check it out this evening.
I haven't seen everything yet, but it does sound like this is quite a lot of functionality for one PR. Tagging & alternate ignore syntax sound like separate features, for example.
PRs also accepted on the build script and CONTRIBUTING.md instructions. I use the included config files with my IDE, and run gradle on the command-line often in my TDD cycle. But I'm just one dev, so there are probably things that work better across people and platforms.

@ashleyfrieze Really nice work. This is looking like a super easy-to-use way to declare Gherkin-style tests. In my experience, Cucumber-JVM has been a pain because of all the step definitions required behind the scenes. This makes tests readable for non-programmers, but simple to implement/edit/refactor for developers. Win!
Some quick points/questions:

The “BDD” term is ambiguous, since for example both RSpec and Cucumber both claim to be “BDD” tools. I think the “Gherkin” term is pretty well-aligned with the given-when-then style, so we should consider using GherkinSyntax instead of BddSyntax, unless you have an even better name. In my own usage, I tend to call the describe/it style test runners as “spec-style” runners. Perhaps what will evolve later on is a separate SpecSyntax to compliment GherkinSyntax.
Spectrum is ready to start having some better package organization. Maybe the Gherkin-specific syntax features could be moved to a sub-package like com.greghaskins.spectrum.gherkin or even com.greghaskins.spectrum.syntax.gherkin (perhaps looking forward to com.greghaskins.spectrum.syntax.spec for the describe/it API down the line).
This is some major waffling on my part: we call the wrapper class Value in there now (as before), and you originally suggested Box. I’m wondering if a better term is something like Variable because that’s really what’s going on: declaring a mutable variable whose value can be retrieved and changed. Not sure if any of them will make sense to newcomers right away. Opinions?
 Otherwise we’ll have to keep looking at coverage decreases case-by-case. (That said, I’d like to get rid of the annoying coveralls bot, I think there are better alternatives.) In the real world, this will really only be a pain for utility classes like BddSyntax where we don’t call the constructor, and those are rare. I can live with one ugly test case in exchange for being able to show off the “100% coverage” badge. If you like, you can chalk this one up to me just being too dogmatic about TDD.

Now, a few bigger points.
For starters, let’s focus this PR down on just the Gherkin-style test declarations, so we can get it merged quickly and move on to additional features. Specifically, we should break out separate PRs for:

Tagging. This is bigger than just a Gherkin thing, and warrants a separate discussion. We should consider existing designs from RSpec (https://www.relishapp.com/rspec/rspec-core/v/3-5/docs/command-line/tag-option) and Mocha (https://github.com/mochajs/mocha/wiki/Tagging). I also see tagging as a more generic version of the existing focus/ignore functionality (only run a subset of the specs)—it would be nice if those implementations could align somehow.
Spectrum configuration. @SpectrumOptions is one idea, but again this warrants a larger conversation and consideration of prior art. I know we already touched on this over in #47.
Parameterized scenarios. I really like parameterized tests, but it feels like a separate feature that would be generally useful even for non-Gherkin tests. It also doesn’t quite work (at least in Eclipse) since it marks tests as started and never marks them as finished. In the mean time without scenario outlines, we can accomplish the same effect with a simple forEach loop that has spec-style or Gherkin-style blocks inside it.

I think the commits you made are pretty atomic, so we should be able to port these features over to separate PRs fairly easily (I can help too). I don’t want the back-and-forth around these related but separate ideas to stand in the way of getting a slick new Gherkin syntax in place.
For the Gherkin implementation itself, we’ve introduced some fairly tight coupling between Suite “children” to achieve the given/when/then workflow (which is required, you can't run then if the given fails). This adds a lot of complexity to the Suite class to track which children are related, etc. I think a cleaner approach would create the appropriate extension points or abstractions so that multiple declaration styles can work independently without stepping on each others’ toes. You’re partly there with the ChildRunner concept, which is essentially the Strategy design pattern. I wonder if we could split out those different run strategies to handle two unique styles and even simplify the core Suite class in the process.
Come to think of it, what about going one step further? Gherkin-style tests really operate in a different way and with different rules than spec-style tests. It might be cleaner if there was a proper object model for Feature, Scenario and so on, rather than trying to shoehorn those concepts into Suite and Spec. I’m not sure, but it could be simpler to create a some new Child implementations that are an alternative to Suite/Spec. That might make it easier to extend and maintain the Gherkin syntax down the road, like validating that all the correct pieces are in place (no missing thens) or adding real semantic meaning to given/when/then beyond just reporting them as separate steps.
I'm interested to hear your take on that.

Wow, lots of words! Overall, this work represents a really solid upgrade for Spectrum. Please let me know how I can help further, including collaborating on the code itself. I also set up a chat room over at https://gitter.im/greghaskins/spectrum if you want an easier way to communicate directly.

Coverage decreased (-0.4%) to 99.623% when pulling a58cb16321f8248137bda61716102f35da464b48 on ashleyfrieze:af-bdd-1 into bd63595caa1fafc1dbbc93467ba51951f7d8d95c on greghaskins:master.

Coverage decreased (-0.4%) to 99.623% when pulling a58cb16321f8248137bda61716102f35da464b48 on ashleyfrieze:af-bdd-1 into bd63595caa1fafc1dbbc93467ba51951f7d8d95c on greghaskins:master.

Coverage remained the same at 100.0% when pulling bed4efa84bd56c4e6aec7a41b192d1573a2f82fa on ashleyfrieze:af-bdd-1 into bd63595caa1fafc1dbbc93467ba51951f7d8d95c on greghaskins:master.

@greghaskins - wise feedback. A lot of it. I have responded with a push.

BDD now replaced with Gherkin - I was describing it that way in my attempt at changing the Readme
Syntax package created
Wrapper now called Variable
Coverage = 100%
Tagging/ignoring stored for a future PR - we can discuss the options there
Paramaterized scenarios dropped for now

I would like to leave the ChildRunner and describeChain features alone for now. I had considered subclassing Suite and realised it did everything for step relationship except for its child running strategy. That's why I just turned that into a lambda. It also follows that someone using it could reasonably wish any failure in a describe stopped the suite. So they can do that with describeChain.
I'm really aiming to get to JUnit rules, and we're getting caught up at the starting blocks. I'd like to use Spectrum with this feature set in the very near future.
Let's focus just on this PR - what else should change to get this syntax in and merged? Then we can re-open the subject of ignoring/tagging. Then we can do rules.

Coverage remained the same at 100.0% when pulling 8647e11455c0dfb10bdd316afdab7bfcb906a29e on ashleyfrieze:af-bdd-1 into bd63595caa1fafc1dbbc93467ba51951f7d8d95c on greghaskins:master.

Coverage remained the same at 100.0% when pulling 629c7fb2c256b22f3f5e90c7d2095c9ba4247718 on ashleyfrieze:af-bdd-1 into bd63595caa1fafc1dbbc93467ba51951f7d8d95c on greghaskins:master.

Nice work; merging now. I have a couple minor fixups, mostly for consistency in the JavaDocs and README which I'll submit as a follow-up PR.
I realized with our latest change, the public API for the Gherkin syntax will be under the root package, in com.greghaskins.spectrum.GherkinSyntax. If we move it later, that will be a semver-major change. I'm okay with that, but wanted to raise the point.


Question / Request: Number of downloads/installs

Hi.
Is it possible to get the number of times an app was downloaded / installed?
I'm only concered about getting this for my app, but I need an API for that, not viewing in the app portal.

This is not something that Apple exposes anywhere, sorry. The best you can get as an estimation is the number of reviews.


I couldn't localize the AM and PM to some other UTF-8 language. Any help?

I tried to localize AM and PM labels and got áˆ›á‰³ thing.


[Bug] [Minor] Extraneous error in frontend

@weienlee could you please remove the extraneous error being logged here?

@weienlee ping

fixed in this commit


Moving api (1) resource to v1beta1 version

Moving 1 resource in the api group:

[ ] azurerm_api_connection

Resource require Data Source: azurerm_managed_api which is not created in azure. I also tried to use azurerm_api_management_api instead
apiVersion: apimanagement.azure.upbound.io/v1beta1
kind: Management
metadata:
  annotations:
    meta.upbound.io/example-id: apimanagement/v1beta1/api
  labels:
    testing.upbound.io/example-name: example
  name: api-example
spec:
  forProvider:
    location: West Europe
    publisherEmail<EMAIL_ADDRESS>    publisherName: My Company
    resourceGroupNameSelector:
      matchLabels:
        testing.upbound.io/example-name: example
    skuName: Developer_1

but it fails with
message: 'observe failed: cannot run refresh: refresh failed: parsing "notif-example":
expected 8 segments within the Resource ID but got 1 for "notif-example": '
reason: ReconcileError
status: "False
Also I was not able to test it manually via azure UI, as there is no way to create Connection manually in https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fconnections

Hello, team.
Does it possible to create Api Connection somehow with Crossplane?


Fatal error  SQLSTATE[HY000] [2002] Connection timed out

Fatal error
SQLSTATE[HY000] [2002] Connection timed out
on http://socl.bz
What's going on?

Your database server address is wrong, or the server is down or silently dropping connections from your YOURLS server.


renderer: disable heat haze stage at load time

Disable heat haze stage at load time, instead of iterating it and skipping it at render time.

I added an extra commit to do b = condition instead of if (!condition) b = false when disabling stages.

It's just extending a PR already merged:

https://github.com/DaemonEngine/Daemon/pull/1075/files#diff-17e274af0ffef15a9550978320ee0f4ad5a61dfa7f3af3b350b456f8083e64faL2631-L2637
https://github.com/DaemonEngine/Daemon/pull/1075/files#diff-9bbcfb69e22103b6c19b7c09f034a0c69882809de7e9a48de71b499c01a63b59R5182-R5188

Instead of testing if the feature is disabled at render time while iterating active stages, just test if the feature is disabled at shader parsing time and remove it from the list that will be processed at render time:

https://github.com/DaemonEngine/Daemon/pull/1074


Allow clearing the custom draw for TreeItem

Due to the way the check on set_custom_draw works there's no way to clear this by calling set_custom_draw(0, null, &"") or similar, decided to not go the route of allowing it to be null and clear the values in that case

Could also add get_custom_draw_object and get_custom_draw_callback to fetch the callback from the method, but starting out like this

tbh custom draw should be a Callable, but it's too late to change it now I guess.

Agreed, we can add a new method for it and deprecate this one, it would still work fine with the new feature as it can still use the old method, but I think adding this won't hurt and does allow for easier clearing up

Gonna look at reworking this for a callable as well as allowing clearing

Thanks!


MNT: Re-rendered with conda-build 3.20.3, conda-smithy 3.8.0, and con…

…da-forge-pinning 2<IP_ADDRESS>.03.27

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@jwillemsen thanks for all your work here and also on conda-smithy and the rest of the ecosystem! Do you have other recipes that you would like to have on conda-forge? I am happy to help out!

Not at this moment, depends on the needs of our users like @traversaro

I personally only needed ace as it is a dependency of YARP, that we extensively use on the iCub robot. At the moment I am still trying in my free time to get our software to compile with conda-forge dependencies (see https://github.com/robotology/robotology-superbuild/issues/477) and after that I have some ideas on how to even have conda binaries for those, but let's do one thing at the time. The extremely nice thing that I noticed is that we have a lot of commonalities with the work that you (@wolfv and @Tobias-Fischer) are doing in https://github.com/RoboStack, so I should drop a line in RoboStack's Gitter one of these days.

Yes that is very true. I think it would be great to have a robotology-superbuild like thing on conda. From my memory it shouldn't be too bad to build yarp and icub-main now that ACE is built. Drop by on gitter and maybe send me a private message there, too - it would be great to get your opinion on something.


mobile profile page add information on which company I am

think to other things to add.

No relevant anymore due to bastiUI design


feat(metaconfig): for new config sources, add groupable options and refactor mutual exclusion

meta config options allow an entire configuration to be
specified by a single source. the only existing native
capability was the use of ini files, but there was no
way to specify which ini file, much less specify it the
same way any other Option could be specified (cli, env, keyring).
this connects a metaconfig instance that can be used to provision
an entire (or part of) a Config. the first meta option to be
implemented was --ini since Config natively supports parsing ini
files.
See the MetaConfig docstring for more details.
todo

[ ] tests

The @argument at the end I think supported supplying an ini file per the docs. Was that not sufficient?

I really like the change to the mutual exclusion to allow groups to exist separately.  Cleaning of the CLI help to be more user friendly is big win.


Bulk Operations

This task is in block status because I couldn't find an affordable CPE with BulkData support.

Testing Bulk data with other methods rather than "usp notify".

HTTP is working, get choose what to do new


autoHeight Don't work on iOS

please post your code & screen capture

For me, it isn't working on iOS, but Android is OK.
I used the code provided in the demo.

@greatbsky please let me know if I can help on fixing this.

@tioback sorry for waiting, I have tell someone to fix this....

@tioback thanks for your report, Auto height should be supported on ios from version 1.0.3, if you still have problem , tell me please ~~

sorry, still not work, I will modify the day after tomorraw

@greatbsky - it worked for me in RN 0.34.0 and react-native-webview2 1.0.3 🤔

@tioback is it on ios?

Yeah, iOS sometimes works, sometimes doesn't.
Android was working, but now stopped. I must have done something that messed it up.

@tioback hi, react-native-webview2 of version 1.0.4 have supported autoheight on ios.
so I close this issue.


helm 3.0.0-beta4: ca-file does not work for helm repo add/update

We are using an internal helm repository with a certificate signed by our internal company CA.
When using this repository in helm 3.0.0-beta4 I get this x509 error:
$ helm repo add name https://repourl --ca-file /path/to/ca.pem
Error: looks like "https://repourl" is not a valid chart repository or cannot be reached: Get https://repourl/index.yaml: x509: certificate signed by unknown authority

The same happens when I migrate my existing helm v2 repository config and call helm repo update.
Executing the exact same commands in helm v2.14.3 with the same repository configuration and same ca.pem file is working fine.
Output of helm version:
version.BuildInfo{Version:"v3.0.0-beta.4", GitCommit:"7ffc879f137bd3a69eea53349b01f05e3d1d2385", GitTreeState:"dirty", GoVersion:"go1.13.1"}

+1 on this. Exact same sequence works in helm2 but not helm3-beta4. --ca-file appears to not be passed.

Is this addressed in beta 5?

Feel free to check, but not that I'm aware, no. Feel like taking a crack at fixing it?

I'm taking a look at this. Starting with reproducing the issue. Will post updates 😄

I'm able to reproduce the issue using mkcert and a local chart repository hosted with serve. Digging into it now

Okay, I found the issue. Yes, CA file input is not being used. Reason -
When we create http client using this
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/httpgetter.go#L77
we don't give it options. The flow is,
there's ca file value here -
https://github.com/helm/helm/blob/4d6a2461f394f171d871e4680b4dfd439c97961e/cmd/helm/repo_add.go#L122
then we create a chart repo struct
https://github.com/helm/helm/blob/4d6a2461f394f171d871e4680b4dfd439c97961e/cmd/helm/repo_add.go#L125
in which we create a simple http client
https://github.com/helm/helm/blob/704133ddd540eb9c3a49f973d4c00fc12910eb34/pkg/repo/chartrepo.go#L66
while creating http client, we don't pass any options
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/getter.go#L114
the constructor is here
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/getter.go#L122
the constructor does have code to support cert file and related things when given options
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/httpgetter.go#L83
but there's still a bug in the if condition as it checks only for cert (public key) and key (private key) file, it should check for ca file too
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/httpgetter.go#L83
in helm 2 it's there
https://github.com/helm/helm/blob/6b5ab08a61d73980ca6f84ccdb3f6b996d950cae/pkg/getter/httpgetter.go#L88
back to helm3,
we do pass tls config actually, over here while downloading
https://github.com/helm/helm/blob/704133ddd540eb9c3a49f973d4c00fc12910eb34/pkg/repo/chartrepo.go#L124
but the problem is, while downloading, the get method uses the options for username and stuff over here
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/httpgetter.go#L58
but there's no code to use the options like ca file, which will be basically the duplicate of whatever code is here
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/httpgetter.go#L84
I was first wondering what can be done, as I can see multiple ways to fix this. In helm2, we actually create the http client with all the configs
https://github.com/helm/helm/blob/519ccac2949695ad54a8f8b159b353b998462e03/pkg/repo/chartrepo.go#L66
this way, we don't have to pass it every time we do a Get. Also, I felt get should still work as it's ca file etc options are set similar to username, password (basic auth) options, but we would be changing the http client's transport field during the Get. Actually, if I think about it now, if we change the transport field during Get, it's a mutation that will affect anyone else using the client later.
Now what do we do? Should we create http client with tls config already? or just change in Get based on options
In any case, I think ByScheme should support taking options
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/getter.go#L111
as Constructor does take options
https://github.com/helm/helm/blob/9bc7934f350233fa72a11d2d29065aa78ab62792/pkg/getter/getter.go#L84
so it can be just passed through
@bacongobbler what do you think is a good approach?

FYI I have a PR ready for this issue. I'm just unable to submit a PR at this time due to spurious HTTP 500 internal errors from GitHub when opening a PR against helm/helm.
In the meantime, here's the development branch if anyone wants to take a look and give it a spin: https://github.com/bacongobbler/helm/tree/fix-6635

Oh. Cool. I was planning to work on it 🙈 Anyways, I'll take a look at the code 👍

Thanks for taking a look at this and sorry for just reviewing it now (I'm not a go dev and have no go env set up...).
Unfortunately, it looks like my use case is still not working in the newest release, containing your PR.
The behaviour is exactly the same as in my first post.
Output of helm version
version.BuildInfo{Version:"v3.0.0-rc.3", GitCommit:"2ed206799b451830c68bff30af2a52879b8b937a", GitTreeState:"clean", GoVersion:"go1.13.4"}

You need to provide both a CA file as well as the key file for the TLS certs to be passed along:
https://github.com/helm/helm/blob/43acbfe86d2228134a5f3478e97cae433ca33fb2/pkg/getter/httpgetter.go#L92
So, at a minimum, you need to pass along --cert-file and --key-file for the TLS options to be propagated. Perhaps there's a use case here we can improve upon.
Demoting from a bug to a question/support as the original issue has been fixed. This now looks to be a usability question.

I'm actually not sure about what the --cert-file and --key-file is for. I mean, I'm assuming key means private key, and cert means public key. And I'm assuming these are related to the repo endpoint. Public key of the endpoint can be obtained by hitting the https endpoint. We usually cannot obtain the private key, and usually need not obtain as a client.
I think here, the user is trying to pass --ca-file, the Certificate Authority's (CA) public key, to verify if the public key (ssl cert) of the repo endpoint is valid, as it's possible that the ssl certificate was signed by a CA who's not trusted by the system. For example, an internal CA.
In helm 2, the code is like this :
https://github.com/helm/helm/blob/6b5ab08a61d73980ca6f84ccdb3f6b996d950cae/pkg/getter/httpgetter.go#L88
It looks for (cert and key file) or CA file. May be we need to do the same here? @bacongobbler

Yes.

I think here, the user is trying to pass --ca-file, the Certificate Authority's (CA) public key, to verify if the public key (ssl cert) of the repo endpoint is valid, as it's possible that the ssl certificate was signed by a CA who's not trusted by the system. For example, an internal CA.

This is exactly what I am trying to do. I don't have access to the private key for that cert.
So I would really appreciate the suggested change for that condition.

Yes, without this working flag, a custom chart repo cannot be added. The private key is not needed.

see #6913.

works as expected in rc4, thanks.

$ helm repo add name https://repourl --ca-file /path/to/ca.pem
Error: looks like "https://repourl" is not a valid chart repository or cannot be reached: Get https://repourl/index.yaml: x509: certificate signed by unknown authority


RFC: Suspense in React 18

In this RFC, we describe a few changes to Suspense that we intend to ship in React 18.
View the formatted RFC.

One issue that I saw with Next.js is that some folks are already using Suspense on the client, and such APIs might not work well with server rendering without additional changes.
Would it make sense to officially recommend something like having existing client-only suspense APIs start throwing an error when rendered on the server so that they fallback to client-rendering, until the API can be updated to properly support server-side Suspense?

Re: https://github.com/reactjs/rfcs/pull/213#issuecomment-1076763161

One issue that I saw with Next.js is that some folks are already using Suspense on the client, and such APIs might not work well with server rendering without additional changes.

Is it the case where people do conditional rendering like {typeof window !== 'undefined' && <Suspense>...</Suspense>}, or is this some other case? Currently, it throws on the server if rendered unconditionally. Rendering different content on the client and server based on a condition was never officially supported, so I'm not sure which scenario this refers to.
If it's the scenario I'm thinking of, the fix is usually to do rendering in two passes:
const [mounted, setMounted] = useState(false);
useEffect(() => {
  setMounted(true);
}, []);

<div>
  {mounted && <Suspense>...</Suspense>}
</div>

It's not great but would have the same behavior.

Would it make sense to officially recommend something like having existing client-only suspense APIs start throwing an error when rendered on the server so that they fallback to client-rendering, until the API can be updated to properly support server-side Suspense?

I'm not sure I understand what you're proposing. Is it to make renderToString throw on Suspense nodes? Or something else? Thanks!

@gaearon The case is not something that happens by just upgrading to newer React. It's when you first upgrade to newer React and then later start using existing Suspense-y APIs on the server and <Suspense> "just works". Except it doesn't just work because the result isn't serialized in the stream so it might change and cause hydration errors.
So there's no conditional Suspense.

existing Suspense-y APIs on the server

Do you mean third-party libs that throw Promises today?

OK yeah got it. I thought this was about using <Suspense> for code splitting, but I see now the question was about using libraries that try to use Suspense for data fetching (which is not fully supported yet), and the fact that these libraries used to throw on the server, but now they may just subtly be broken. I agree it makes sense for them to throw explicitly until there is a way to transfer the data to the client.

Are the layout effects to re-run when content reappears effectively only those defined using useLayoutEffect? Although not recommended due to visual inconsistency, DOM mutations and reading using useEffect also happen (folks sometimes move to useLayoutEffect only after noticing blinks, layout shift, etc.) Are those effects also re-running?

Re: https://github.com/reactjs/rfcs/pull/213#issuecomment-1077053718

Are the layout effects to re-run when content reappears effectively only those defined using useLayoutEffect?

Yes, as well as ref callbacks.

DOM mutations and reading using useEffect also happen (folks sometimes move to useLayoutEffect only after noticing blinks, layout shift, etc.) Are those effects also re-running?

No, useEffect does not re-run. If it's visually important then useLayoutEffect is the right tool to use, so this builds on the existing distinction (like you said, otherwise you might have shifts anyway). Not re-running useEffect is important because it leaves you a workaround for things that should not reset. It also avoids performance issues with running too much setup/cleanup code when hiding/showing stuff.

This sounds trivial, but: What are the current scenarios that allow a component to suspend in general?
The whole RFC gives explanations for what happens when a component suspends, but how do I, as a developer, enable a component to suspend? With that I mean throwing a promise, startTransition, and so on.
Or, in other words: What are the "tools" we can use in our code so <Suspense> (and its fallback) is actually used?
I saw "The exact protocol a component should use to tell React that it's suspended." at the "Unresolved questions" - maybe I'm lost in translation, but I read this as "How a component lets React know while it is suspending" (=> "loading state"). Sorry for asking if it was not meant like this.

Re: https://github.com/reactjs/rfcs/pull/213#issuecomment-1077953067

The whole RFC gives explanations for what happens when a component suspends, but how do I, as a developer, enable a component to suspend?

Indeed, that's the "unresolved question" you're mentioning. The pragmatic answer is that today it works by throwing a Promise. However that's not an "official" or "final" API, and it's also not a complete description of the contract. You can't just throw arbitrary promises and expect it to work. Rather, it has to be backed by some cache outside of your components (rather than create during rendering), you need to throw the same Promise while it's pending (rather than creating a new one every time), you have to store its result outside of your components, you can't mutate the received data, and so on. These requirements are somewhat difficult to satisfy on your own, which is why we don't consider Suspense for data fetching officially supported yet. https://github.com/reactwg/react-18/discussions/25 is part of the work to make this simpler.

I have a question, with this new behavior, if Panel is a big component that takes time to render it's better to put it outside the fallback like this:
<Panel>
  <Suspense fallback={<Spinner />}>
    <Comments />
  </Suspense>
</Panel>

Because with the previous behavior Panel is already mounted, thus we don't have to wait for it to mount again once the Comments times out?
However, I am more in favor of the new approach because, in addition to its simplicity and all the reasons you have mentioned, I think it also simplifies react-devtools code by removing many of the Suspense edge cases, thanks to the fact that Suspense now behaves the same as regular fibers from the devtools perspective, right?

Re: https://github.com/reactjs/rfcs/pull/213#issuecomment-1078166879

Because with the previous behavior Panel is already mounted, thus we don't have to wait for it to mount again once the Comments times out?

Re-rendering always starts from the Suspense node, so even in the old behavior, Panel would get re-rendered when Comments completes.

I recently had proplems with Suspense during hydration. I had a text mismatch warning and then that immediatelly failed the Suspense root and switched to client side rendering. If it's "just" a warning, I wouldn't expect the whole thing to break. If it's an error, why is it only a warning? :) I tested with suppressHydrationWarning just out of curiousity, and my app didn't switch to client render anymore. Is this really the expected behavior?

Re: https://github.com/reactjs/rfcs/pull/213#issuecomment-1078667103
Yes, we’re treating hydration mismatches as errors now. They cause a fully client render at the granularity of the closest Suspense boundary above the mismatch. I will post more details about this later today. The correct fix is usually to fix the mismatch but you’re right that for things like timestamps, the “suppress warning” prop now actually has production behavior too. This is unfortunate and we might rename it in a future release.

We've effectively introduced a new form of Error that's kind of between a Warning and an Error... "Recoverable Error". It just means it can recover by client rendering so the user won't see it but it's an error so worth fixing.

More on that: https://github.com/reactjs/rfcs/pull/215


Support C++

ClangSharp
Using libclang to Parse C++ (aka libclang 101)
public void Parse()
{
    var index = clang.createIndex(0, 0);
    var unit = clang.parseTranslationUnit(index,"path",null, 0, out var unsavedFiles, 0, 0);
    clang.disposeTranslationUnit(unit);
    clang.disposeIndex(index);
}

Any news on the C++ support? Your extension would greatly enhance my C++ coding experience.

Unfortunately no news on C++ support. I'm not a C++ developer so it will be difficult for me to correctly write the parsing logic. So I am afraid I do not have the time available right now to dive into this :(

For what I know - C++ (and probably C too) is unparsable. I mean - to get the full picture of the code you probably need to complete what pre-processor does and then do entire lexing and mabe even part of compiling. The problem is probably with macros. They can contain code similar to basic C, but AFAIK the syntax is different. BUT - VS probably does that for us. It holds it somewhere and it's probable available via it's API. So - I'd say impossible with parsing, but probably doable using VS API.


Trying the first example to see how it works, received this error

Steps to reproduce
Oh no! Something went wrong: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'd:'
Expected behavior
Create a readme.md file
Actual behavior
Trying the main example, have received this on windows: Oh no! Something went wrong: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'd:'
System configuration
Tell us about the applicable parts of your setup.
NodeJS version:
v21.6.1
Operating System:
Windows 11
Module Loader:
ESM

Thank you for reporting! Can you see if you have version 0.5.1 (or later) installed? I believe this should be fixed via https://github.com/featherscloud/pinion/pull/59.

Looking at it again, that change didn't actually apply everywhere it needed to but it should work in v0.5.2 via #61 now.


encoding: missing support for toml

(Go) Tools like InfluxDB, GitLab CI (Runner), Traefik use TOML as their configuration language. Atm. CUE has no encoding support for TOML configuration files to be imported or exported. Since Go doesn't have native support for TOML, a third-party implementation needs to be imported as it's the case for YAML. Another thing to be aware of is that the native support for Date-Time, Date, Time values in TOML. Maybe this could be something CUE might want to support in the future as well. Also a mapping of array of tables to a appropriate CUE representation might be needed.

I'm fine with TOML, being as common as it is, to be one of the few more configuration formats that's natively supported. At the moment, YAML, JSON, Go, Proto, and OpenAPI are higher on the list to complete support for, though.
Note that generating TOML output should already not be too hard using the text/template builtin package.
CUE has some limited support for time and date parsing through the time builtin package. It is high on the list to complete this support as part of the OpenAPI support effort. With this, a time field is indicated as:
import "time"

meetingTime: time.Time

where meetingTime is a string with the respective time format.
I don't understand why arrays of tables are not just lists of values. It seems to be a special TOML notation that needs no special treatment in CUE. I do plan to add support for associative lists at some point, which would allow one to define different items of a list at different locations, though, sticking to CUE's associativity and commutativity properties, without any guarantee of order other than adhering to some topological sort.

This issue has been migrated to https://github.com/cue-lang/cue/issues/68.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


container runtime blob manager

Add blobManager to ContainerRuntime (and remove the one on Container)
Blob handles returned by BlobManager.createBlob() send a BlobAttach op when attached
add blob test

Closed because of repo going public, new PR at #3573


[Question] Custom polyfill

How am I able to specify some custom polyfill script without ejecting?
More specifically, I want to polyfill toJSON in Error:
if (!('toJSON' in Error.prototype)) {
  Object.defineProperty(Error.prototype, 'toJSON', {
    value: function () {
        const alt = {};
        Object.getOwnPropertyNames(this).forEach(function (key) {
            alt[key] = this[key];
        }, this);
        return alt;
    },
    configurable: true,
    writable: true
  });
}

Thanks!

Create src/polyfills.js and import it in src/index.js.

You can place this code anywhere, but I'd suggest in a dedicated file as suggested by @miraage.
Make sure it's the first thing you import in src/index.js!


dep: bump scalapb related stuff

This is an attempt to try to better align the protoc related tooling
since we've bumped the version of protobuf in the main build, but also
have older transitive stuff that is being brought in by these. Probably
best to bump them as well.
Sort of an attempt to see what might be going on with
https://github.com/sourcegraph/scip-java/issues/486.
Test plan
Tests should just remain 🟢

First-time contributors need a maintainer to approve running workflows

Any idea why it still thinks I'm a first-time contributor?

I also opened #488, which should probably fix the underlying issue, but it's good to perform this upgrade nevertheless.

Any idea why it still thinks I'm a first-time contributor?

I have no idea why I need to repeatedly press this button 🤷


fix: remove reference to make generate in release

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5158

Relevant Lines:
7093

💛  - Coveralls


Run the app locally without having to install pnpm on the host machine

CONTRIBUTING.md  shows how to run the app locally using Docker. However, it requires installing pnpm AND the project dependencies (with pnpm install) in the host machine. I don't want to do either: I use Docker, because I don't want to install anything locally, but only inside a Docker image. Could you provide a Dockerfile to build a Docker image, which I could spin with docker compose? Thanks

Of course, this compose example demonstrates exactly what you are asking for: https://github.com/AmruthPillai/Reactive-Resume/blob/main/tools/compose/simple.yml

Thanks, @AmruthPillai, this works really well.


feature: optimize undo module duplicate log output during two-stage retry

Why you need it?
Is your feature request related to a problem? Please describe in details

Output the Exception stack
Reduce the duplicate output, can consider that each GlobalTransaction is only output once

How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
Other related information
Add any other context or screenshots about the feature request here.

https://github.com/seata/seata/pull/1775


Replace deno cache with deno install [WIP]

Closes https://github.com/denoland/docs/issues/863
I need a bit of guidance here, I want to completely remove the runtime/reference/cli/cache.md page and instead redirect to runtime/reference/cli/script_installer.md preferably to a concrete anchor. Is that possible?
CC @marvinhagemeister @thisisjofrank

Yeah, replacing the file is possible. Use the 'oldUrl' setting in the top of the new markdown.
The _data file with the sidebar links will need to be updated and we can do a find replace for any links to the old file to the new file.


Grabbed Passwords

When do the grab password it works but no file

they have no saved passwords on CHROME

anyway to get a script that can do it?

idk find one


Configuration with Unix sockets not working

Afaik I'm up-to-date and configured correctly. I suspect that asgi_redis hasn't been updated with recent Redis changes. I'll let the logs speak for themselves.
Versions:
asgi-redis==1.2.1
asgiref==1.1.1
channels==1.1.2
daphne==1.2.0
Django==1.11
redis==2.10.5
redis-structures==0.1.6

Python 3.4

Configuration:
CHANNEL_LAYERS = {
    "default": {
        "BACKEND": "asgi_redis.RedisChannelLayer",
        "CONFIG": {
            "hosts": ["unix:///var/run/redis/redis.sock"],
        },
        "ROUTING": "community.routing.channel_routing",
    },
}

Daphne log:
2017-04-07 02:49:30,515 INFO     Starting server at unix:/var/www/next/community/daphne.sock, channel layer community.asgi:channel_layer.
2017-04-07 02:49:30,516 INFO     HTTP/2 support not enabled (install the http2 and tls Twisted extras)
2017-04-07 02:49:30,516 INFO     Using busy-loop synchronous mode on channel layer
2017-04-07 02:49:30,516 INFO     Listening on endpoint unix:/var/www/next/community/daphne.sock
2017-04-07 02:49:30,533 ERROR    Error trying to receive messages: __init__() got an unexpected keyword argument 'socket_connect_timeout'
2017-04-07 02:49:35,534 ERROR    Error trying to receive messages: __init__() got an unexpected keyword argument 'socket_connect_timeout'
2017-04-07 02:49:40,535 ERROR    Error trying to receive messages: __init__() got an unexpected keyword argument 'socket_connect_timeout'
2017-04-07 02:49:45,536 ERROR    Error trying to receive messages: __init__() got an unexpected keyword argument 'socket_connect_timeout'
2017-04-07 02:49:50,537 ERROR    Error trying to receive messages: __init__() got an unexpected keyword argument 'socket_connect_timeout'
2017-04-07 02:49:55,538 ERROR    Error trying to receive messages: __init__() got an unexpected keyword argument 'socket_connect_timeout'

Daphne Worker log:
2017-04-07 02:50:23,334 - INFO - runworker - Using single-threaded worker.
2017-04-07 02:50:23,334 - INFO - runworker - Running worker against channel layer default (asgi_redis.core.RedisChannelLayer)
2017-04-07 02:50:23,335 - INFO - worker - Listening on channels websocket.connect, websocket.disconnect, websocket.receive
Traceback (most recent call last):
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 895, in get_connection
    connection = self._available_connections.pop()
IndexError: pop from empty list

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/www/next/community/manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line
    utility.execute()
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/__init__.py", line 355, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/var/www/next/venv/lib/python3.4/site-packages/channels/management/commands/runworker.py", line 83, in handle
    worker.run()
  File "/var/www/next/venv/lib/python3.4/site-packages/channels/worker.py", line 87, in run
    channel, content = self.channel_layer.receive_many(channels, block=True)
  File "/var/www/next/venv/lib/python3.4/site-packages/asgiref/base_layer.py", line 43, in receive_many
    return self.receive(channels, block)
  File "/var/www/next/venv/lib/python3.4/site-packages/asgi_redis/core.py", line 211, in receive
    result = connection.blpop(list_names, timeout=self.blpop_timeout)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/client.py", line 1163, in blpop
    return self.execute_command('BLPOP', *keys)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/client.py", line 570, in execute_command
    connection = pool.get_connection(command_name, **options)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 897, in get_connection
    connection = self.make_connection()
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 906, in make_connection
    return self.connection_class(**self.connection_kwargs)
TypeError: __init__() got an unexpected keyword argument 'socket_connect_timeout'
2017-04-07 02:50:28,350 - INFO - runworker - Using single-threaded worker.
2017-04-07 02:50:28,350 - INFO - runworker - Running worker against channel layer default (asgi_redis.core.RedisChannelLayer)
2017-04-07 02:50:28,351 - INFO - worker - Listening on channels websocket.connect, websocket.disconnect, websocket.receive
Traceback (most recent call last):
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 895, in get_connection
    connection = self._available_connections.pop()
IndexError: pop from empty list

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/www/next/community/manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line
    utility.execute()
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/__init__.py", line 355, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/var/www/next/venv/lib/python3.4/site-packages/channels/management/commands/runworker.py", line 83, in handle
    worker.run()
  File "/var/www/next/venv/lib/python3.4/site-packages/channels/worker.py", line 87, in run
    channel, content = self.channel_layer.receive_many(channels, block=True)
  File "/var/www/next/venv/lib/python3.4/site-packages/asgiref/base_layer.py", line 43, in receive_many
    return self.receive(channels, block)
  File "/var/www/next/venv/lib/python3.4/site-packages/asgi_redis/core.py", line 211, in receive
    result = connection.blpop(list_names, timeout=self.blpop_timeout)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/client.py", line 1163, in blpop
    return self.execute_command('BLPOP', *keys)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/client.py", line 570, in execute_command
    connection = pool.get_connection(command_name, **options)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 897, in get_connection
    connection = self.make_connection()
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 906, in make_connection
    return self.connection_class(**self.connection_kwargs)
TypeError: __init__() got an unexpected keyword argument 'socket_keepalive_options'
2017-04-07 02:50:33,408 - INFO - runworker - Using single-threaded worker.
2017-04-07 02:50:33,408 - INFO - runworker - Running worker against channel layer default (asgi_redis.core.RedisChannelLayer)
2017-04-07 02:50:33,409 - INFO - worker - Listening on channels websocket.connect, websocket.disconnect, websocket.receive
Traceback (most recent call last):
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 895, in get_connection
    connection = self._available_connections.pop()
IndexError: pop from empty list

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/www/next/community/manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line
    utility.execute()
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/__init__.py", line 355, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/var/www/next/venv/lib/python3.4/site-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/var/www/next/venv/lib/python3.4/site-packages/channels/management/commands/runworker.py", line 83, in handle
    worker.run()
  File "/var/www/next/venv/lib/python3.4/site-packages/channels/worker.py", line 87, in run
    channel, content = self.channel_layer.receive_many(channels, block=True)
  File "/var/www/next/venv/lib/python3.4/site-packages/asgiref/base_layer.py", line 43, in receive_many
    return self.receive(channels, block)
  File "/var/www/next/venv/lib/python3.4/site-packages/asgi_redis/core.py", line 211, in receive
    result = connection.blpop(list_names, timeout=self.blpop_timeout)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/client.py", line 1163, in blpop
    return self.execute_command('BLPOP', *keys)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/client.py", line 570, in execute_command
    connection = pool.get_connection(command_name, **options)
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 897, in get_connection
    connection = self.make_connection()
  File "/var/www/next/venv/lib/python3.4/site-packages/redis/connection.py", line 906, in make_connection
    return self.connection_class(**self.connection_kwargs)
TypeError: __init__() got an unexpected keyword argument 'socket_keepalive'

Duplicate of https://github.com/django/asgi_redis/issues/36 - this is already fixed in master. I'll issue a release now.


Fixed nan loss by filtering out-of-frame gt_bboxes in coco.py

There may exist out-of-frame annotations in custom datasets. These abnormal annotations will cause nan loss. For example, such cases exist in the object365 datasets, and I found both Libra RCNN and Cascade RCNN diverged due to nan loss. After filtering these abnormal cases, these detectors converged. Even though this should be avoided by dataset annotators, it can be more robust of mmdetection to filter out-of-frame annotations.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @Jokoe66 ！First of all, we want to express our gratitude for your significant PR in the mmdetection project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/raweFPmdzG
If you are Chinese or have WeChat，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


Fix wb mode with zstd compression

Motivation
Fixes #814
I'm not sure this is the best fix, but it seems to work
Checklist
Before you create the PR, please make sure you have:

[x] Picked a concise, informative and complete title
[x] Clearly explained the motivation behind the PR
[x] Linked to any existing issues that your PR will be solving
[x] Included tests for any new functionality
[x] Checked that all unit tests pass

Thank you!


Script snippets mentioned on this page are not included.

The script snippets mentioned in the blog post did not come through with the migration.

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

ID: adaf3b73-2793-a059-96ac-7f18e17c39d4
Version Independent ID: f421e1bc-9521-f5eb-696a-634bf0f81529
Content: Allowing an additional host to run a VM with virtual TPM
Content Source: virtualization/community/team-blog/2016/20161025-allowing-an-additional-host-to-run-a-vm-with-virtual-tpm.md
GitHub Login: @scooley

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Consuming Messages from a topic

I'm copy and pasting the sample from the readme to dequeue  messages from our kafka and i get this error message
panic: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)
I have other projects in Scala, and they connect fine so I know for sure the cluster is reachable.
Any idea what i might be missing here ?

I was use to using brokers as "brokera,brokerb,brokerc", i just needed to put them in go slice format...


S3 Protection

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature
Guard Duty has a feature to read S3 logs and look for findings there. This module should have a toggle to enable such a feature
Expected Behavior
A parameter is available that can enable or disable GuardDuty's S3 protection feature
Use Case
To enable S3 protection
Describe Ideal Solution
A parameter exists to toggle this feature
Alternatives Considered
Manual configuration in the console
Additional Context
PR incoming

I believe this already exists https://registry.terraform.io/modules/cloudposse/guardduty/aws/latest#input_s3_protection_enabled


Add your profile to the Github Profile READMEs !

If this is your first pull request, please read this article: How To Create a Pull Request on GitHub
Read more about GitHub Profile README: GitHub Official Profile README Docs
Step 1
Fork the repo by pressing the "Fork" button on the top right side of the
repository and clone your forked repository.
Step 2
In your forked repository, edit users.js (src/dataSet/users.js) and add your name and github userName to the bottom of the file using this format:
  {
    name : "Full Name",
    github : "github userName"
  }

Step 3
In your forked repository, go to githubCards folder (src/dataSet/githubCards) and add you Github Profile README template keeping the name of the file as your github userName with extension as .md.
Example :
if GitHub userName is srinibasbiswal, then the fileName will be :

srinibasbiswal.md

Step 4
Commit your changes and submit a pull request! After your pull request gets accepted, you will be able to see your very own GitHub README card on the Github Profile READMEs!

Add my profile, thank's!

Created PR for my profile! Thanks

Created PR for my profile. Please merge

Done @Abhijith126 . Thanks for contributing.

Created PR for my profile. Learnt to Add new badge, stats in markdown files. It's a great experience. Thanks @srinibasbiswal. Plz merge #49

thank you for contributing @immayurpanchal


In ProbAttention, why should we initial context tensor?

Thanks for sharing this amazing work!!
In class ProbAttention (file models/attn.py), line 90-92
https://github.com/zhouhaoyi/Informer2020/blob/90e080593e9c345f5f9676359bb3d1618e9aa735/models/attn.py#L90-L92
I'm confused why should we initial context, instead of directly using attn * v as context, maybe like:
context_in = torch.matmul(attn, V)

Same as pseudo-code (line 8), why cannot just set S = {S1}

Please let me know, if I missed some details which was mentioned paper 🤣

In ProbAttention, we initialize the context_in in function _get_initial_context() and the shape of context_in is [L, L]. And we use Q_K_sample to calculate attn, so the shape of attn is [L, log(L)]. So we assign the index of context_in usign attn * V.

In ProbAttention, we initialize the context_in in function _get_initial_context() and the shape of context_in is [L, L]. And we use Q_K_sample to calculate attn, so the shape of attn is [L, log(L)]. So we assign the index of context_in using attn * V.

Appreciate for your reply.
I‘m confused why connot directly use attn * V as context_in (with shape [batch_size, top_n, ...]),  instead of just assigning the index of context_in (with shape [batch_size, sequence_length, ...])
(Maybe we need to keep same sequence length, in order to pass it to the next layer?)

In ProbAttention, we initialize the context_in in function _get_initial_context() and the shape of context_in is [L, L]. And we use Q_K_sample to calculate attn, so the shape of attn is [L, log(L)]. So we assign the index of context_in using attn * V.

Appreciate for your reply.
I‘m confused why connot directly use attn * V as context_in (with shape [batch_size, top_n, ...]), instead of just assigning the index of context_in (with shape [batch_size, sequence_length, ...])
(Maybe we need to keep same sequence length, in order to pass it to the next layer?)

Yes, we need to keep the context_in as shape [B, L, ...].

In ProbAttention, we initialize the context_in in function _get_initial_context() and the shape of context_in is [L, L]. And we use Q_K_sample to calculate attn, so the shape of attn is [L, log(L)]. So we assign the index of context_in using attn * V.

Appreciate for your reply.
I‘m confused why connot directly use attn * V as context_in (with shape [batch_size, top_n, ...]), instead of just assigning the index of context_in (with shape [batch_size, sequence_length, ...])
(Maybe we need to keep output of AttentionLayer has same shape with sequence length, in order that pass it to the next layer?)

Yes, we need to keep the context_in as shape [B, L, ...].

After attention layer, we use Conv1d as next layer, and do 1D convolution (kernel width=3) on time dimension, it will finally reduce time dimension. So...why should we keep context_in as shape [B, L, ...], instead of reducing time dimension in this step?
Maybe keep original shape (use more sequence information?) can improve accuracy? (Sorry if I bothered you...

Actually, the Conv1d will turn down the information faucet from the self-attention block. We believe it is affordable in performing long-term forecasting. But it may help in the short-term cases if we keep the original shape.


CAUSE 9002: file is not a database: ,

Google Pixel 2 XL, Android 11. Had been running for ~10 days (since release), but stopped running today.

The app now always crashes on startup.

Problem seems to be known in the original German app as well: https://github.com/corona-warn-app/cwa-app-android/issues/642

I have the exact same  issue that I wanted to report.
This on a Huawei P8 Lite (first generation), Android 6.0.
Installed the App about 6 days ago (official website I think), use bluetooth intermittently (only when going out so contact tracing is enabled).
The only thing I can think of is I did an automatic weekly "Clean" of the phone, maybe it threw away the local sqllite database file?

I looked up the German reports and  indeed seems to be prevalent on "lower-end" phones like Huawei P8 lite and others.
App is using an encryption library/service on the phone which apparently can't handle too much concurrency so gives back a "busy" signal which in turn is interpreted as an event where keys need to be re-generated which overwrites the old keys so database can't be accessed anymore because wrong keys.

Thanks for reporting this issue. Indeed this is something that's already happening in the original, German, codebase.
They seem to have found a workaround (I say "seem" because since it's impossible to reproduce we can't be 100% sure) and we are looking into incorporating their fix in our codebase.
What they implemented has not been released to the public yet so it remains to be seen if that actually resolves the issue for all affected users (it's scheduled in 1.4.0, but their latest version is 1.3.1).


the generic term "Authorization Token" to describe an access_token is really confusing!

https://github.com/IHE/ITI.IUA/blob/master/IHE_ITI_Suppl_IUA.md#34111-authorization-client
The use of the term "Authorization Token" to refer to the OAuth2 access_token is super confusing to readers familiar with the HL7 SMART spec and should be changed.

Low: Typo or other minor classification that an editor can manage. Requires no group discussion.

seems reasonable to change to Access Token when in narrative.

Will make the change Friday morning after morning changes.


[webapi] Add reference file for css color tests

Impacted tests(approved):new 0,update 4,delete 0
Unit test platform:[android]
Unit test result summary:pass 1,fail 3,block 0

@chenxix I would expect the commit message says something like "Sync reference files for CSS Color tests to latest W3C", or "Integrate reference files for CSS Color tests to latest W3C"; so that people knows you have done in upstream.

Better with the upstream PR link(s) in the commit message.


Add 'Typelevel Scala' dialects

The dialects are equal to their corresponding mainstream Scala version
with the literal types syntax enabled.

Maybe we need to create a ParadiseTypelevelScala211 and ParadiseTypelevelScala212, so literal types syntax is enabled there...

TLS can have other dialect differences from its corresponding LBS. For example TLS 2.12.1 added kind polymorphism and trailing commas.

FWIW, I opened https://github.com/scalameta/scalameta/issues/661 to start a discussion on reorganizing dialects to more easily accommodate new dialects.

I close the PR or a wait till #662 is merged, then I accommodate this PR to that one?

Sounds good @xavier-fernandez


Is there any way to load code from a url or a local path on disk?

I'm embedding the editor in a MacOS native app. Everything is working well except when trying to set text that has "\n" characters. I'm a little lost as to how to go about this since I only see one way to set text using setValue()
https://cl.ly/0H0J280G2y2B
const _code = `
//  cues.js

var cues = function() {

    const _cues = [
        "CUE \n ONE",
        "CUE \n TWO",
        "CUE \n THREE"
    ];

    return _cues;
}`;

window.editor.setValue (_code);

In this specific example, \n will be interpreted by the JavaScript runtime as a line break. So to get literally the characters \ and n in the editor you need to escape them. e.g.:
const _code = `
//  cues.js

var cues = function() {

    const _cues = [
        "CUE \\n ONE",
        "CUE \\n TWO",
        "CUE \\n THREE"
    ];

    return _cues;
}`;

window.editor.setValue (_code);

I don't think this is a monaco editor issue, the same happens if console.log(_code) is used.

right. thanks @alexandrudima , got it all sorted now.


Expose a method to check if the job has been already scheduled

Problem
It is impossible to check if the job has already been scheduled preventing from double scheduling.
Current state
If the job with the same name is scheduled multiple times consequent job scheduling attempts fail with an unhanded exception. To avoid exceptions client has to maintain state about scheduled job which is not a great developer experience.
Solution
There are multiple ways to approach job scheduling:

Expose a method that allows the client to check if given job is already scheduled, e.g.:  isScheduled(jobName).
Pros: no state tracking on the client, allows to query job manager if specific job exists and execute custom logic based on that
Cons: expands job-managers API with one more method which will need maintenance
Catch the exception internally in scheduleJob method and return empty result null
Pros: keeps the API surface small
Cons: there might be use-cases where the client doesn't necessarily wants to schedule a job but only needs to check if one is already there (for example if some other job needs to be registered under this specific condition)

Leaning towards 1st option as it's the least confusing behavior and having one more method in the small API won't be too much of a burden.

There's also a 3rd option, which is the method used by the Stripe API:

The method to schedule a job should be idempotent given a unique/idempotency ID

If it’s called again with the same ID (which may or may not be the job name?) then it should throw an idempotency error saying specifically that the job has already been scheduled. If the job reference/ID is different to the idempotency key then the error should return the previously scheduled job ID as a reference.
The client should/could also be able to choose to schedule a job without an idempotency ID in order to always have the job be scheduled again, if that behaviour is needed. An idempotency ID can be an existing key like the job name, or a separate concept.
The methods behaviour is then transparent to the client and the client can handle the idempotency error smoothly for it's own use case, normally the same as a success.
IMO this idempotency pattern will be needed in lots of our libraries/public and private APIs, so we should get familiar with it.


Species.tau file has NAs

After a amalgkit run with 3 samples excluded, the .tau output file gives a "highest" and "order", but the numerical tau value is NA.
Example below.

<title></title>
<meta name="generator" content="LibreOffice <IP_ADDRESS> (Windows)"/>
<style type="text/css">
	body,div,table,thead,tbody,tfoot,tr,th,td,p { font-family:"Liberation Sans"; font-size:x-small }
	a.comment-indicator:hover + comment { background:#ffd; position:absolute; display:block; border:1px solid black; padding:0.5em;  }
	a.comment-indicator { background:red; display:inline-block; border:1px solid black; width:0.5em; height:0.5em;  }
	comment { display:none;  }
</style>

tau | highest | order |
-- | -- | -- | --
lcl|NC_037638.1_cds_XP_623975.1_1 | NA | embryo_W | embryo_W|ovary_W|midgut_W|embryo_M|hypopharyngeal_glands_W|larval_gut_W|mandibular_gland_W|nasonov_gland_W|skeletal_muscle_W|malpighian_tubule_W|adipose_Q|head_and_thorax_Q|adipose_W|sting_gland_W|antennae_W|second_thoracic_ganglia_W|brain_Q|mushroom_bodies_M|brain_W|mandibular_gland_Q|mushroom_bodies_W
lcl|NC_037638.1_cds_XP_623952.2_2 | NA | embryo_M | embryo_M|ovary_W|nasonov_gland_W|malpighian_tubule_W|midgut_W|adipose_Q|mandibular_gland_W|hypopharyngeal_glands_W|antennae_W|sting_gland_W|brain_Q|second_thoracic_ganglia_W|larval_gut_W|skeletal_muscle_W|mushroom_bodies_M|brain_W|mushroom_bodies_W|embryo_W|adipose_W|mandibular_gland_Q|head_and_thorax_Q
lcl|NC_037638.1_cds_XP_006557469.1_3 | NA | embryo_M | embryo_M|embryo_W|antennae_W|midgut_W|second_thoracic_ganglia_W|nasonov_gland_W|hypopharyngeal_glands_W|skeletal_muscle_W|mandibular_gland_W|malpighian_tubule_W|adipose_Q|sting_gland_W|larval_gut_W|mushroom_bodies_M|ovary_W|brain_Q|brain_W|mandibular_gland_Q|head_and_thorax_Q|adipose_W|mushroom_bodies_W
lcl|NC_037638.1_cds_XP_006557467.1_4 | NA | embryo_M | embryo_M|embryo_W|midgut_W|hypopharyngeal_glands_W|mandibular_gland_Q|larval_gut_W|brain_W|mushroom_bodies_W|adipose_W|sting_gland_W|head_and_thorax_Q|ovary_W|second_thoracic_ganglia_W|mushroom_bodies_M|malpighian_tubule_W|nasonov_gland_W|adipose_Q|mandibular_gland_W|skeletal_muscle_W|antennae_W|brain_Q

Did amalgkit finish without errors?
Do other amalgkit outputs of this run OK, or do they have problems as well?

Amalgkit finished with no errors.
Yes I have done other runs where the .tau calculations were numerical and complete.

How about the species.curate_group.mean.tsv ? Do they look "normal" (like, all tissues there, values reasonable, etc.)?

@C20H25N30 I think I found the cause of this, but I'm still investigating where and why it happens. This is specific to your dataset, so let's continue this discussion via mail.

This issue was caused by all samples of a certain curate_group (i.e. tissue) being marked for exclusion, which caused problems with the tau calculation further down the line.
I have added a failsave that works like this:

print warning message that all samples of a tissue have been marked for exclusion
continue the algorithm without this tissue

updated in amalgkit ver. 0.5.1:
https://github.com/kfuku52/amalgkit/commit/0bf4fc3083336883b3aab8aed87b1f1f0e9dba99


Update my collection

Hi. So my collection was already in the registry but I'm not sure whether it was pulled from Ordswap automatically or whether the Ordswap team added it for me. Either way, it was incomplete on Ordswap so this pull request includes the complete collection. Thanks :)

Shortened collection name


Change ports where scheduler and manager are listening

inspection-report-20200113_203422.tar.gz
Is there any way to change port where scheduler and controller-manager components are listening?
I mean, currently thuey are listening to 10252 and 10251.
Is there any way to change that?

You should be able to adjust the parameters in
/var/snap/microk8s/current/args/kube-scheduler
According to the docs here: https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/


publish package (v17.x)

Please publish the new version to the npm registry to support angular 17

My team is look forward for this update

@RobbieTheWagner may you publish the package, when you have some minutes to spare?

@RobbieTheWagner could you please look into this.

My team are also in desperate need for this

17.0.0 published, sorry for the delay!


Add Snake Game With Obstacles

Community Contribution
Link to live project, video, or image:
https://sanjana-mukherjee.github.io/Snake-Game/

Sharing

[x] I would be happy to have my project shared on The Coding Train's social media!

Awesome 🐍🕹


'Open Mailbox' is not working behind proxy

I am not able to connect to mailbox from behind the proxy server, is there any keyword or workaround for the same ?

May I know are you able to use Open Mailbox keyword?
I write below code it does not work
Open Mailbox   host=outlook.office365.com<EMAIL_ADDRESS>password=*******  port=993
I got an error, "ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it". Any idea how to fix it?

Hi!
When using the method "Open Mailbox" with correct access data we get the error message:
gaierror: [Errno 11003] getaddrinfo failed
It would be great if you could help us solve the issue and/or if you add a detailed error message to help us solve the problems ourselves.
Thanks a lot in advance!

Hi Rick,
robotframework-imaplibrary2 0.3.2  is broken. I try to use new version it
is not working on python 3.7.4.
Error : after installation and using pycharm this library always highlight
on red line. In addition pressing control + B does not open keyword
details,  Moreover try to use "Open mailbox" Keyword does not work.
Any suggestions? How this library will work?
Please send me email for more details.
Thanks
Harry
On Fri, Aug 16, 2019 at 3:07 AM TestMed<EMAIL_ADDRESS>wrote:

Hi!
When using the method "Open Mailbox" with correct access data we get the
error message:
gaierror: [Errno 11003] getaddrinfo failed
It would be great if you could help us solve the issue and/or if you add a
detailed error message to help us solve the problems ourselves.
Thanks a lot in advance!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rickypc/robotframework-imaplibrary/issues/18?email_source=notifications&email_token=AHUY5FF63IMN2DZAUOWRDH3QEZG23A5CNFSM4FQBBTIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4N3NIQ#issuecomment-521909922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHUY5FBPFTQONYJKA7IYEELQEZG23ANCNFSM4FQBBTIA
.


Add BlueZ in CHIP

-- Add BlueZ in Third-party for CHIP Linux device layer BLE manager integration
fixes #741

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please add initial GN support as well.

Please add initial GN support as well, or at least let's discuss the plan for it with @mspang.

Can you provide some context on why bluez needs to be managed? Is it possible to have two copies of bluez running at the same time on the developer's system?

Please add initial GN support as well, or at least let's discuss the plan for it with @mspang.

Can you provide some context on why bluez needs to be managed? Is it possible to have two copies of bluez running at the same time on the developer's system?

In the past several year, since bluez5.44, the bluez BLE dbus APIs starts to become ready for public experimental use, and experience continuous changes on API behavior and parameters, bugs are introduced in recent years. When engineers, including me, add fix in bluez upstream, there is only sanity and manual test to verify if this fix work, and then those fix easily break other features in lack of comprehensive unit and integration test. Different ubuntu, debian, embedded linux, chrome os I have worked before are using different version of BlueZ, for example, chrome os is still using bluez5.44, debian(tesing/experimental) are using 5.50, other different ubuntu OS are using various bluez version. Currently our qa teams proves 5.47 and 5.48 are pretty stable on BLE APIs, for example, 5.45,5.46 have several ble stability bugs we found. Therefore we lock down the commit in 5.48 in Weave. We would also plan BlueZ 5.50 or latest after enough tests have been done.
BlueZ is using bluetoothd daemon, currently in this pr, it is compiling in linux device layer, but not running. When testing it, developers usually kill the system's bluetoothd process, and run the compiled bluetoothd during testing. In weave, we have automated this test procedure for weave ble integration test via virtual btvirt, the bluez bt emulator generated from BlueZ, note os system itself is not including this btvirt tool, and these weave over BlueZ tests are running during presubmit and postsubmit CI. Usually in weave, at default, these ble tests are at default disabled. developer locally don't need run these weave over BlueZ test, when developer touched these codes, they need to run the automate test.
That's why we need to compile blueZ. It is not possible to have two BlueZ bluetoothd running at the same time in same host now.
Btw, in project cirque, we also are exploring how to bring up multiple bluetoothd across multiple docker in same host for BlueZ BLE virtualization in docker, which would need some additional changes in blueZ upstream.

Seems ok, however needs a build fix.

Hi, Andrei
Yes, I am fixing them!
Best wishes
Yunhan

Please add initial GN support as well, or at least let's discuss the plan for it with @mspang.

Can you provide some context on why bluez needs to be managed? Is it possible to have two copies of bluez running at the same time on the developer's system?

In the past several year, since bluez5.44, the bluez BLE dbus APIs starts to become ready for public experimental use, and experience continuous changes on API behavior and parameters, bugs are introduced in recent years. When engineers, including me, add fix in bluez upstream, there is only sanity and manual test to verify if this fix work, and then those fix easily break other features in lack of comprehensive unit and integration test. Different ubuntu, debian, embedded linux, chrome os I have worked before are using different version of BlueZ, for example, chrome os is still using bluez5.44, debian(tesing/experimental) are using 5.50, other different ubuntu OS are using various bluez version. Currently our qa teams proves 5.47 and 5.48 are pretty stable on BLE APIs, for example, 5.45,5.46 have several ble stability bugs we found. Therefore we lock down the commit in 5.48 in Weave. We would also plan BlueZ 5.50 or latest after enough tests have been done.
BlueZ is using bluetoothd daemon, currently in this pr, it is compiling in linux device layer, but not running. When testing it, developers usually kill the system's bluetoothd process, and run the compiled bluetoothd during testing.

Ok, that's what I feared, you can't really solve this problem by simply building a new bluez inside CHIP; running it interferes with the system install.
We might consider just providing instructions on installing a backport and just asserting that the version is OK. It sounds like Debian testing/gLinux are new enough, and CrOS we can fix ourselves..

In weave, we have automated this test procedure for weave ble integration test via virtual btvirt, the bluez bt emulator generated from BlueZ, note os system itself is not including this btvirt tool, and these weave over BlueZ tests are running during presubmit and postsubmit CI. Usually in weave, at default, these ble tests are at default disabled. developer locally don't need run these weave over BlueZ test, when developer touched these codes, they need to run the automate test.
That's why we need to compile blueZ. It is not possible to have two BlueZ bluetoothd running at the same time in same host now.
Btw, in project cirque, we also are exploring how to bring up multiple bluetoothd across multiple docker in same host for BlueZ BLE virtualization in docker, which would need some additional changes in blueZ upstream.

"Ok, that's what I feared, you can't really solve this problem by simply building a new bluez inside CHIP; running it interferes with the system install.

We might consider just providing instructions on installing a backport and just asserting that the version is OK. It sounds like Debian testing/gLinux are new enough, and CrOS we can fix ourselves..

It will not interfere with the system install, it just compiled it inside CHIP device layer automatically, and not install in system path. As I mentioned, if you don't run ble related test, you don't need touch it, which would not impact you. If you run it, Chip BlueZ support would automatically help you. Besides, if you compile chip in docker, and run bluetoothd in docker, it would not impact/interfere your system blueZ. The docker installation/validation/test would be recommended way in presubmit and local validation to provide the unified/controllable CHIP environment for developer/tester for the IOT world.
In github docker, there is no bluez inside, there is no interference at all from that point.
Debian testing/glinux's 5.50 is not working as we expect, we need to lock down specific commit. CROS has stopped bluez support, and reject all upgrade or fix from bluez 5.44.
We also added bluez in weave, from internal or external partners, we don't hear the related complains on the bluetoothd interference issue. From the experience, developer/tester bring up woble test, and run it smoothly.

"Ok, that's what I feared, you can't really solve this problem by simply building a new bluez inside CHIP; running it interferes with the system install.

We might consider just providing instructions on installing a backport and just asserting that the version is OK. It sounds like Debian testing/gLinux are new enough, and CrOS we can fix ourselves..

It will not interfere with the system install, it just compiled it inside CHIP device layer automatically, and not install in system path. As I mentioned, if you don't run ble related test, you don't need touch it, which would not impact you. If you run it, Chip BlueZ support would automatically help you. Besides, if you compile chip in docker, and run bluetoothd in docker, it would not impact/interfere your system blueZ. The docker installation/validation/test would be recommended way in presubmit and local validation to provide the unified/controllable CHIP environment for developer/tester for the IOT world.
In github CHIP docker, there is no bluez inside, there is no interference at all from that point currently.
Debian testing/glinux's 5.50 is not working as we expect, we need to lock down specific commit. CROS has stopped bluez support, and reject all upgrade or fix from bluez 5.44.

Does it work with bluez's HEAD? If not, we have a future problem in addition to the problems you've listed already.

We also added bluez in weave, from internal or external partners, we don't hear the related complains on the bluetoothd interference issue. From the experience, developer/tester bring up woble test, and run it smoothly.

I thought you said you had to stop the OS daemon to run the local one? That's the interference I was referring to.

Per offline chat with @mspang, we agree to build bluez in chip, I would try to work with @mspang for gn integration, i will open another ticket there.

@jelderton @saurabhst @BroderickCarlin ?

@saurabhst @jelderton ?


ROX-23847: Attempt at reducing lock contention in network entities datastore

Description
When a cluster is deleted, it calls DeleteExternalNetworkEntitiesForCluster in networkEntity's in a go routine. When multiple clusters are deleted, there are multiple routines calling DeleteExternalNetworkEntitiesForCluster. This function acquires lock on netEntityLock and walks through all the network entities. This can be slow and cause other routines to timeout waiting on netEntityLock . This is probably causing "TestClusterDeletion" failures in CI because that test creates 58083 network entities. This is an attempt at a quick fix to filter out some of the entities before walking through them to reduce contention. A more complete solution would be to make clusterID searchable in NetworkEntity proto but that would require migration and thus more time to fix.
Checklist

[ ] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
Passing CI is enough
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

I think this makes sense to try, but like you said the real fix is to make the cluster_id searchable. We should document that as a ticket and put it on the backlog if we aren't going to do that now.

Created ROX-24317