Questions on Shared Faces and Face Neighbors

I have a few questions about the concepts of shared faces and face neighbors as they appear in the mfem::ParMesh class:

What exactly is a face neighbor (referred to by mfem::ParMesh::GetNFaceNeighbors(), mfem::ParMesh::GetFaceNbrGroup, etc.)? Is this just a term for a parallel group that spans one or more faces?
What exactly is a shared face (referred to by mfem::ParMesh::GetNSharedFaces() and mfem::ParMesh::GetSharedFace(int))? Does this term refer to faces that lie on abutment surfaces between domains?
Does each shared face correspond to a local face on a particular local domain? If not, what are some cases where a domain knows about a shared face with no local corresponding local face?

To make these questions a bit more concrete, consider the following 4-domain problem:
Y

^ (0, 2)        vvsf23
|   +-----------++-----------+
|   |    face20>||<face30    |
|   |           ||           |
|   |  domain2  ||  domain3  |
|   |           ||           |
|   |vface21    ||    face31v|
| s>+-----------++-----------+<s
| f>+-----------++-----------+<f
| 0 |^face01    ||    face11^| 1
| 2 |           ||           | 3
|   |  domain0  ||  domain1  |
|   |           ||           |
|   |    face00>||<face10    |
|   +-----------++-----------+
|           sf01^^         (2, 0)
+----------------------------->  X

For domain0, are the face neighbors domain1 and domain2?
For domain0, are the shared faces sf01 and sf02?
In this scenario, domain0's local faces have a one-to-one relationship with "shared faces" (i.e. face00 corresponds to sf01 and face01 corresponds to sf02). When would this not be the case?

Thanks in advance for your thoughts and responses!

What exactly is a face neighbor (referred to by mfem::ParMesh::GetNFaceNeighbors(), mfem::ParMesh::GetFaceNbrGroup, etc.)? Is this just a term for a parallel group that spans one or more faces?

A "face neighbor" is an MPI rank corresponding to a mesh partition that shares a face with the local mesh partition.
In the example you include, each domain should have two face neighbors, since each domain borders two other domains with shared faces.

What exactly is a shared face (referred to by mfem::ParMesh::GetNSharedFaces() and mfem::ParMesh::GetSharedFace(int))? Does this term refer to faces that lie on abutment surfaces between domains?

Yes, that is correct. A shared face is a face that lies on the boundary of elements contained in two different mesh partitions.

Does each shared face correspond to a local face on a particular local domain? If not, what are some cases where a domain knows about a shared face with no local corresponding local face?

I believe that every shared face should correspond to a local face.

To make these questions a bit more concrete, consider the following 4-domain problem:
Y

^ (0, 2)        vvsf23
|   +-----------++-----------+
|   |    face20>||<face30    |
|   |           ||           |
|   |  domain2  ||  domain3  |
|   |           ||           |
|   |vface21    ||    face31v|
| s>+-----------++-----------+<s
| f>+-----------++-----------+<f
| 0 |^face01    ||    face11^| 1
| 2 |           ||           | 3
|   |  domain0  ||  domain1  |
|   |           ||           |
|   |    face00>||<face10    |
|   +-----------++-----------+
|           sf01^^         (2, 0)
+----------------------------->  X

For domain0, are the face neighbors domain1 and domain2?

Yes.

For domain0, are the shared faces sf01 and sf02?

Yes.

In this scenario, domain0's local faces have a one-to-one relationship with "shared faces" (i.e. face00 corresponds to sf01 and face01 corresponds to sf02). When would this not be the case?

In general, there will be more local faces than shared faces. In your example, domain0 has two shared faces, and two faces that are not shared (left and bottom). That being said, every shared face should correspond to a local face. Note, however, that each domain might have a different numbering of the shared faces (e.g. sf01 could be shared face i on domain 0, and shared face j on domain 1).

Excellent explanation, @pazner; thank you! On point (3), I've been reviewing some client code that had checks for cases when a shared face had no local equivalent, which is why I asked the question. Your statements of (1) "all shared faces correspond to a local face" and (2) "not all local faces correspond to a shared face" makes much more sense to me. Thanks again!

@pazner Can you find the time to turn this into an article?  If not I can get to it sooner or later as you already did most of the work.

@pazner Can you find the time to turn this into an article? If not I can get to it sooner or later as you already did most of the work.

It would fit under the umbrella of #1740, which keeps getting pushed further down the to-do list…


az extension add: "Unknown extension type. Only Python wheels are supported."

Describe the bug
Command Name
az extension add
Errors:
The command failed with an unexpected error. Here is the traceback:

Unknown extension type. Only Python wheels are supported.
Traceback (most recent call last):
  File "/home/alling/lib/azure-cli/local/lib/python2.7/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/home/alling/lib/azure-cli/local/lib/python2.7/site-packages/azure/cli/core/commands/__init__.py", line 608, in execute
    raise ex
ValueError: Unknown extension type. Only Python wheels are supported.

To Reproduce:

az extension add --source azure-devops

Expected Behavior
I was hoping the extension would install correctly.
Environment Summary
Linux-5.0.0-38-generic-x86_64-with-Ubuntu-19.04-disco
Python 2.7.16
Shell: bash

azure-cli 2.0.81

Additional Context
When I first encountered the error, I had Azure CLI 2.0.79. I updated to 2.0.81 to see if that would help; my Azure CLI now has Python 2 instead of Python 3:
$ az --version
azure-cli                         2.0.81

command-modules-nspkg              2.0.3
core                              2.0.81
nspkg                              3.0.4
telemetry                          1.0.4

Python location '/home/alling/lib/azure-cli/bin/python'
Extensions directory '/home/alling/.azure/cliextensions'

Python (Linux) 2.7.16 (default, Oct  7 2019, 17:36:04)
[GCC 8.3.0]

Legal docs and information: aka.ms/AzureCliLegal

* DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020.
A future version of Azure CLI will drop support for Python 2.7.

Your CLI is up-to-date.

Hi @jsntcy , could you please help to check this ?

add to S166.

@SimonAlling,
If you run help command az extension add -h, you'll see the following help messages and examples

You can see that if you want to install extension by name, you need run az extension add --name azure-devops instead of az extension add --source azure-devops

@SimonAlling,
If you run help command az extension add -h, you'll see the following help messages and examples

You can see that if you want to install extension by name, you need run az extension add --name azure-devops instead of az extension add --source azure-devops

Aha. I think az should definitely warn if --source is used with a non-URL then, instead of throwing a completely incomprehensible error. Although that may not be easily implemented if --source works with local files too.


Added documentation on versioning Dapr components

This PR adds documentation for when and how to create Version 2 of a component and beyond.
Resolves #526
PR for adding component versioning support is dapr/dapr#2757

Is this ready for approval @artursouza @yaron2 ?


Add netcat openbsd image

currently, the scaffolding chart uses trillian which rely on toolbelt/nc image. that image is amd64 only which then make the scaffolding chart requires amd64 node.
https://github.com/sigstore/helm-charts/blob/a80c33c8ca6f3c37d9b1dcb4dab14ca625f77831/charts/trillian/values.yaml#L160

closing as old/inactive. please re-open if necessary


[Feature Request] StyleCLIP GUI

Very impressive paper, amazing to see the model in action.
Would it be possible to add the GUI which was used in the youtube video to the repository?

The GUI code has been updated. Please refer to 'Editing via Global Direction' in the main page.


Handling of in-file negatives in ReProver

Hi, thanks for open releasing the source code of ReProver and providing a very helpful guide on training the model. I notice that the in-file negatives are critical for the performance of ReProver, as explained in the paper, and I'm trying to understand how this is implemented.
As far as I understand, given an example ex, this for-loop iterates over all premises that are present in the file where the context belongs, i.e., all premises in ex["context"].path.
https://github.com/lean-dojo/ReProver/blob/0dbb82e3507cb8303dbb550bdb96bfbbb37e1ced/retrieval/datamodule.py#L105-L112
Here is what I found a bit confusing: when ex["pos_premise"].path !=  ex["context"].path (i.e., when the premise is imported from some other file instead of defined/proved in the same file), all of these premises we are iterating on will be added to premises_outside_file, instead of premises_in_file. This seems a bit counter-intuitive, because these premises actually come from the same file as the context, could you please explain a bit more on this?

Hi,
Thanks for your interest in our work. "In-file negative" means the negative premise is from the same file as the positive premise. Therefore, if the positive premise is from the current file (i.e., ex["pos_premise"].path == ex["context"].path), all negative premises in the current file are in-file negatives.


simple-linked-list: use JUnit's @Rule feature

We've been migrating to using JUnit's ExpectedException @Rule feature instead of @Test(expected = SomeException.class). Change the occurrence of @Test(expected = SomeException.class) in SimpleLinkedListTest to make it use the @Rule feature instead.

and finally the last one


Raspberry Pi Pico not showing up as COM/ttyACM0 device

I just started working with the new Pico and run into some problems while trying to communicate with it over Serial UART.
The Pico doesn't show up neither as a com port on Windows nor as a ttyACM0 device in my ubuntu subsystem for Windows.
I tried it with two cables and two different Picos.
Then I checked if the cables were fine by plugging in an ESP32 instead. It was immediately recognized as a COM Port on Windows. I couldn't try it on the subsystem, since it stil doesn't show up as a ttyACM0 device. The article
https://www.scivision.dev/usb-tty-windows-subsystem-for-linux/
might suggest though, that these kind of devices are renamed in the subsystem.
Anyways, the Pico clearly doesn't show up as a COM Port! That makes it impossible to communicate via Serial. Anyone having an explanation or a fix?

I just started working with the new Pico and run into some problems while trying to communicate with it over Serial UART

Serial UART is a pair of GPIOs for RX and TX (GPIO0 and GPIO1 by default). Do you mean UART, or do you mean USB CDC?
You need to enable the USB CDC in your code (it's not enabled by default as you may want to use USB for other things). The hello_usb example has it enabled. If you program that example, do you now see Pico appearing as a USB serial device?

Great explanation, you were absolutely right, problem fixed ;.)

https://www.youtube.com/channel/UCA4j-J-TFW_9Dt4iTwIjtYQ
Once visit this channel for Raspberry Pi Pico Projects


location specified in config.yml not respected when using existing resource group

In what area(s)?

/area administration

/area ansible
/area autoscaling
/area configuration
/area cyclecloud
/area documentation
/area image
/area job-scheduling
/area monitoring
/area ood
/area remote-visualization
/area user-management

Expected Behavior
When specifying a location in the config.yml, az-hop is deployed in this location (independent of the location of the resource group used).
Actual Behavior
When using a pre-existing resource group, the location of that resource group takes precedence over the location specified by the user.
Steps to Reproduce the Problem
Create a resource group, e.g. in westus.
Tell az-hop to use that resource group for deployment, but ask to deploy in eastus.
It is quite straightforward to fix once accepted as a bug - I don't know whether there would be a reason to stick with the current behavior where the location of the resource group takes precedence.
cc @matt-chan

In the scenario mentioned above, one hits another issue when building images:
when giving the packer azure/arm plugin a destination resource group, it will create the VM in the region of that resource group (no way to change this, see issue).
Our workaround was to create a separate vnet in the resource group, build the image there, and then replicate it to the target region.

it's a best practice to deploy resources in the same location of the resource group, and usually RG are also named with the location code.

If the scenario is not going to be supported, it would be good to document the requirement that the location of the pre-existing resource group must match the location in the config.yml.

closed by https://github.com/Azure/az-hop/commit/aa0e5d7b1e23a4666352e9cd797706e12257c9f3


[5.2] Fixed phpdoc and condensed logic

The logic condensing was done by first replacing the two unneededly different exists checks, then using distributivity and de morgan laws to condense it.

Isset would have one problem, if you add a test:
$array = ['products' => ['desk' => null]];
$value = Arr::get($array, 'products.desk', false);
$this->assertNull($value);

the test would fail with isset because the result would be false yet the key exists with the value of null.

We already have that issue everywhere then?

If we take it then yes, there's quite some places where it would fail such test, like data_get helper etc.. Though I guess the need for null value is almost none.
And I noticed has should be updated in the same way get was :\

Kind of looks like change in behavior to me.

Indeed, Arr::has() should be made consistent with Arr::get().


As an Admin, I want to see the "Who is Listening" widget I added to an Engagement.

As an Admin
I want I want to see the "Who is Listening" widget I added to an Engagement
so that I know I added this widget and can move it above or below other widgets.
Acceptance Criteria
Scenario 1:
Admin created a widget and clicked the "Save & Close" button on the widget panel.
Scenario 2:
Confirm user interface to the visual design https://xd.adobe.com/view/7360b654-4a25-4140-9670-a56f4adabe7a-2633/screen/64369cc7-ca7d-40c8-b6b7-874a05917540/specs/
Scenario 3:
Admin sees a grey "card" with the following content on the Engagement window:
Column 1: Move icon (to move the Team Member up and down if other widgets are added.
Column 2: Label (16px bold): Widget Name
Column 3: "Edit" and "Delete" icons
Scenario 4:
Admin moves the card above and below other cards, if present, by clicking on the "move" icon and placing the card above or below other cards.
Scenario 5:
Admin clicks the edit button to go to the widget panel (https://app.zenhub.com/workspaces/met-ops-6254279dcfa60b0010ea5a0d/issues/bcgov/met-public/139).
Scenario 6:
Admin clicks the "Delete Icon". Modal to confirm deletion appears.
(https://app.zenhub.com/workspaces/met-ops-6254279dcfa60b0010ea5a0d/issues/bcgov/met-public/144)
Validation Rules?
(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

Hey team! Please add your planning poker estimate with Zenhub @djnunez-aot @jadmsaadaot @saravanpa-aot @tiagograf-AOT @VineetBala-AOT

Re-estimated this card after more information about "dragging" + "sorting" was brought up in Grooming.

Add two "fake" widgets as placeholders??

Admin is able to create multiple widget and drag to re-order them.
Both edit a widget and delete a widget is working as expected.
All delete icons are made standard to the "x" mark.


[internals]Remove includes and references to dpcc++ internals

This PR is meant to eliminate references to dpc++ internals in case hipSYCL is used. This is probably the messiest part of the entire porting process.
TODO: exact description of what happens here

closed in favour of #7


Refactoring FEELEventListenersManager.notifyListeners() .

@etirelli I prefer to submit this early to get your feedback please.
I've refactored the notifyListener logic in one place (a static method - a function).
I've used the Java 8's Supplier so the event to be dispatched is computed (created a new instance) if and only if the event manager is not null and there are listeners. This would keep the logic and optimization of "return early" as it was before, but instead of having it in several places, is just consolidated in the new function FEELEventListenersManager.notifyListeners(FEELEventListenersManager eventsManager, Supplier<FEELEvent> event)

Perfect! :)


Does Linkis plan to support delta lake or hudi?

Does Linkis plan to support delta lake or hudi

Sorry delta lake or  hudi are not in our roadmap, but you join Wedatasphere community and contribute you code. We will thank a lot.


all: to what extent should CUE support symlinks?

"Inspired" by https://github.com/cue-lang/cue/issues/3299, I don't think we have been explicit about the extent to which modules support (or otherwise) symbolic links.
Questions not limited to:

Should module loading follow symlinks at all? We already document that published modules don't support them: https://cuelang.org/docs/reference/modules/#zip-path-size-constraints
Could/should we distinguish between the main module or otherwise?
...

This issue might generate further issues for bugs/implementation.
End goal is that we should be clear in our documentation (exact location TBC) on the extent to which module loading does/doesn't support symbolic links.
See also #3298

In my case—the basis for the aforementioned #3299—I'm not creating these symbolic links deliberately in my primary source repository. Rather, I'm using my seh/rules_cue Bazel ruleset to evaluate the CUE files within Bazel's actions, and Bazel's normal sandbox preparation behavior involves creating a directory tree full of symbolic links to regular files sitting elsewhere, as an optimization against copying all of those files.

@seh - thanks for adding this context, extremely useful.

As a data point, I checked Go's behaviour in this regard:

Go accepts and reads symlinks locally, including when using a directory replace directive and in vendor directories.
Go silently drops symlinks when consuming from a network source, such as the Go proxy or a remote VCS source

Regarding support for Bazel's sandboxes, it wouldn't be much trouble to require that callers of the cue tool pass a command-line flag to enable tolerance for symbolic links, if you didn't feel that it was safe or fair to use that as the default behavior. If there was such a command-line flag, I'd have my Bazel ruleset pass it to the cue tool when invoking it inside of Bazel actions.

Should module loading follow symlinks at all?

Perhaps I jumped the gun by approving the patch for https://github.com/cue-lang/cue/issues/3298, which makes the loader follow symlinks locally. The way that issue was raised before this one, in the format of a bug report, didn't make it clear that it was a slightly open question.
Given that Go does this locally, doing the same seems fine to me. But given that symlinks cannot be published or consumed via a GOPROXY (nor a CUE registry), I think it would also be fine to leave them as unsupported in a consistent way.

Making a decision here should also close https://github.com/cue-lang/cue/issues/1672, hopefully.
Note that some people in that thread were wondering about symlink support for loading local packages, but it's not clear to me that any of them actually relied on it in the past.

But given that symlinks cannot be published or consumed via a GOPROXY (nor a CUE registry), I think it would also be fine to leave them as unsupported in a consistent way.

With the caveat that we would then need to understand/answer how things could/should work with Bazel. @seh how familiar are you with what Go does with respect to Bazel? Anything we should be learning from there?

Note that some people in that thread were wondering about symlink support for loading local packages, but it's not clear to me that any of them actually relied on it in the past.

I've been relying on it since first using CUE with Bazel three and a half years ago.

how familiar are you with what Go does with respect to Bazel? Anything we should be learning from there?

As far as I can tell from inspecting the directory trees created by the rules_go ruleset when I build Go programs with Bazel, every file presented to the Go toolchain is a symbolic link.
If we happen to have Bazel generate any files used as input to compiling or linking action, that artifact might wind up as a regular file sitting within that same sandbox's directory tree, but not necessarily.

My sense is that we keep things working as-is, by first tightening up what we mean by "as-is", and adding any missing tests.
So here is an attempt to define what "as-is" is/should be:

CUE does drops symlinks when writing module zip files (per https://cuelang.org/docs/reference/modules/#zip-path-size-constraints) and when reading them.

That second part of the sentence is worth us making sure with a test. Because it's possible to construct a "rogue" zip file that does include symlinks using the regular Unix zip command. Being really sure how CUE treats such a zip is important.
Note that the rule would also apply in the case of:
cue export $pkg@$version

As such, an embed "read" will only ever happen within the CUE module cache for a zip-based dependency.
That way we can say that if the CUE code did not come from a zip archive (working with a main module on disk, a directory-based replace directive, vendor, cue.mod/{pkg,gen,usr}, ...) then symlinks will work. This should ensure we leave the existing support for Bazel in place, and indeed make it more official via that definition.

by first tightening up what we mean by "as-is", and adding any missing tests.

When we have those tests, we should also verify how older CUE versions behaved, for example v0.5.0.

Following my comment in https://github.com/cue-lang/cue/issues/3299#issuecomment-2244581796, I have updated my comment above to state clearly that:

@embed directives will never follow symlinks.

This brings CUE inline with Go's behaviour with respect to embed.
@seh - please could I ask you to take a look at my conclusion above and raise any concerns you might have from a Bazel perspective?

please could I ask you to take a look at my conclusion above and raise any concerns you might have from a Bazel perspective?

The treatment of files in modules proposed above sounds like it would work fine with Bazel's sandbox technique, at least for files in modules that come from the same Bazel workspace. That would cover my use of modules thus far.
The restriction on embed may turn out to be onerous, in that one could write a CUE file that embeds a JSON file sitting right next to it on disk, but when Bazel prepares a sandbox for an action that involves these two files as input, it will create symbolic links to both. When the cue tool reads the CUE file—traversing the symbolic link to do so—it will find an @embed attribute mentioning a file that's present on disk as another symbolic link. If the cue tool then refuses to read that file, it appears to be behaving differently within the sandbox. Of course, the cue tool would have refused to read the symbolic link outside of the sandbox too, but that's not what the author intended to arrange.
I can imagine a softer but more complicated rule, something like: If we read the CUE file containing the @embed attribute through a symbolic link, then we'll look for the file mentioned in the @embed attribute via relative path from the target of the CUE file's symbolic link. In other words, for relative paths, the resolution base would be the CUE file's actual path, meaning the final target of any symbolic links that pointed to it.

@seh

The restriction on embed may turn out to be onerous, in that one could write a CUE file that embeds a JSON file sitting right next to it on disk, but when Bazel prepares a sandbox for an action that involves these two files as input, it will create symbolic links to both.

Given that Go seems to have exactly the same rule, do you know how Go manages to avoid that difficulty, by any chance?

do you know how Go manages to avoid that difficulty, by any chance?

In the rules_go Bazel ruleset, both the go_library and go_binary rules accept an "embedsrcs" attribute to designate the input files that are candidates for being embedded. The rules restrict the nominated dependencies to sit within the same Bazel package's root directory, which is a logical restriction; it's possible to mix both primary source files and files generated by other Bazel targets, so long as the targets produce output files that sit in that same directory.
rules_go prepares a so-called embedcfg file that it then supplies to the Go compiler via the -embedcfg command-line flag. You can see how the compiler uses that file in the readEmbedCfg function.
There's a lot of bundling up the files to be embedded and figuring out their relative paths. It's hard to follow what's going on, but I think it's mainly about working around the restriction on following symbolic links.

With the tests from https://review.gerrithub.io/c/cue-lang/cue/+/1198252 merged, I'm pushing the rest of the work here to alpha.3, as we are releasing alpha.2 today.

@seh

do you know how Go manages to avoid that difficulty, by any chance?

In the rules_go Bazel ruleset, both the go_library and go_binary rules accept an "embedsrcs" attribute to designate the input files that are candidates for being embedded. The rules restrict the nominated dependencies to sit within the same Bazel package's root directory, which is a logical restriction; it's possible to mix both primary source files and files generated by other Bazel targets, so long as the targets produce output files that sit in that same directory.
rules_go prepares a so-called embedcfg file that it then supplies to the Go compiler via the -embedcfg command-line flag. You can see how the compiler uses that file in the readEmbedCfg function.
There's a lot of bundling up the files to be embedded and figuring out their relative paths. It's hard to follow what's going on, but I think it's mainly about working around the restriction on following symbolic links.

That's all super helpful, thanks! I'm totally unfamiliar with Bazel so it's hard for me to know how much of this applies only to Go and how much might apply to CUE too, but it seems like we will probably need a similar mechanism to Go's -embedcfg so we can make embed directives work even when the embed targets are in another directory. Or... does Bazel know enough to be able to make symlinks to the embedded files too (and hence just supporting embedded files that are symlinks might be OK) ?

does Bazel know enough to be able to make symlinks to the embedded files too (and hence just supporting embedded files that are symlinks might be OK) ?

Bazel will create symbolic links to all the files nominated as "inputs" for an action that it's going to run, regardless of where the source files sit relative to each other either in the primary repository or as generated outputs from other actions. So long as we mention that the embedded files need to be inputs to the action that runs cue def or cue export, we'll get symbolic links to them in the sandbox that Bazel creates for the action.
The reason that rules_go wants the embedded source files specified in a separate attribute on the go_library or go_binary rule—that is, "embedsrcs" alongside the usual "srcs"—is so that it can arrange for telling compiler about them differently, assuaging its concerns about reading symbolic links.

I've retitled this issue to the much broader "to what extent should CUE support symlinks?"
With a view to this issue being closed with a holistic explanation of where CUE does/doesn't support symlinks, along with  brief rationale for each relevant point.
@rogpeppe is going to follow up with that summary.
We will also create further issues as needs be to capture outstanding bugs/work. e.g. if our aim is to support symlinks in such a way that things work for Bazel, we should have tests that lock that in.

@seh Do I have it right that you're happy with CUE's current behaviour with respect to symbolic links?

Do I have it right that you're happy with CUE's current behaviour with respect to symbolic links?

From what I've read, it sounds workable for use with Bazel. I'd like to try an example involving a mixture of static source and generated files that I can have Bazel run through cue export.

For the record, the executive summary of current (and proposed future) behaviour with respect to symlinks is as follows:
We allow and respect symbolic links except that we reject/ignore them whenever they become the contents of a module in a registry.
As such, symbolic links will not be unarchived from the contents of a module archive and will not appear in the module cache.
As another consequence of this behaviour, when we implement directory replace for modules (#2956), symbolic links will function inside the directory holding the replacement module.
Note: this behaviour covers all files within a module, including files embedded with the @embed directive.

We allow and respect symbolic links except that we reject/ignore them whenever they become the contents of a module in a registry.

Does this mean that symbolic links are only supported in local modules, but not registry modules?
This seems reasonable, I'm just a bit confused by the phrasing. 🙏

@infogulch correct. https://cuelang.org/docs/reference/modules/ says:

Symbolic links and other irregular files are ignored when creating zip files, since they aren’t portable across operating systems and file systems, and there’s no portable way to represent them in the zip file format.

so any symbolic links present are ignored when using cue mod publish. But since loading CUE files and packages does follow symlinks, as long as you load a module which wasn't fetched from a CUE registry (e.g. via git clone), they will work.

This seems reasonable, I'm just a bit confused by the phrasing. 🙏

We recently published https://cuelang.org/docs/concept/faq/symbolic-link-support/ - does its wording feel less confusing and (hopefully!) clearer?

Thanks for clarifying. Yes the docs are better.
Maybe it would be helpful to have a name to positively identify and distinguish the two different kinds/sources of modules -- like "registry module" vs "local module" -- then defining the behavior by reference to these names. I suspect an explanation of this form would be faster to grok and make it easier to derive the answers to such FAQ for oneself.
Is this the only difference between "local" and "remote" modules? If there are more features that distinguish them then maybe it would be worth naming.


Add tests for npm package  "codecoverage-tools"

Need to cover npm-package codecoverage-tools by tests

[x] utilities.ts
[x] codecoverageutilities.ts
[ ] codecoveragefactory.ts
[ ] codecoverageenabler.ts
[ ] codecoverageconstants.ts
[ ] cobertura\cobertura.ant.ccenabler.ts
[ ] cobertura\cobertura.gradle.ccenabler.ts
[ ] cobertura\cobertura.maven.ccenabler.ts
[ ] jacoco\jacoco.ant.ccenabler.ts
[ ] jacoco\jacoco.gradle.ccenabler.ts
[ ] jacoco\jacoco.maven.ccenabler.ts

Created a PR: https://github.com/microsoft/azure-pipelines-tasks-coverage-tools/pull/5

Created PR for files utilities.ts and codecoverageutilities.ts: https://github.com/microsoft/azure-pipelines-tasks-common-packages/pull/79

Created PR for remaining files: https://github.com/microsoft/azure-pipelines-tasks-common-packages/pull/145


click.discord.com on fakenews-gambling-porn

I am using the http://sbc.io/hosts/alternates/fakenews-gambling-porn/hosts file, with an auto update script that autofetches the file for me, today i was login in discord and recived the confirmation e-mail, however i was unable to login, because the email link is to click.discord.com, i disabled the host file and logged in, but I wanted to make sure that click.discord.com was there intentionally. I chose the one with no social media blocking because of reddit and discord. the regular discord domain remais unaffected.

I am sorry, but this is by design. click.discord.com is primarily used for tracking. As such, StevenBlack does not intend to allowlist it.
Please either allowlist it on your devices, or request Discord stop using this domain to tracking links in their emails.
Thank you

Thank you for this @Thiago-Assis-T, and thank you for the assist @iam-py-test.
As stated above, this isn't going to change.
Closing.

I see, thanks and sorry for not searching the issues and prs...
at the time it didn't seem like intentional, but now explained it does make sense!


Release of version <IP_ADDRESS> of NetworkingDsc

Releasing version <IP_ADDRESS>

This change is

Codecov Report

Merging #390 into master will increase coverage by <1%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #390    +/-   ##
======================================
+ Coverage      95%    95%   +<1%
======================================
  Files          27     28     +1
  Lines        2131   2195    +64
======================================
+ Hits         2040   2104    +64
  Misses         91     91


Essence Pouches  - incorrect inv space

🐛 Bug Report
RC trips only providing +89 suddenly after previously providing +216 for having all pouches.

Req 105 RC


Crashing w/ 0.7.6 Nitty Gritty & Mac Mail 16.0 on Monterey 12.6

Running Mac Mail Version 16.0 (36<IP_ADDRESS>.1) on Monterey 12.6 and using MailTrackerBlocker v0.7.6 Nitty Gritty.
No other plugins are in use.
My mail app crashes almost like clockwork daily until I disable the MTB plugin, and then it's rock solid.  Any way to fix?
Thank you.

I'm running the exact some setup without issue.
Could you post the crash report? You have to hit Report... then copy and paste the text under Problem Details and System Configuration. Looks like this:

Sorry, I had since removed the plugin since it made my MacOS Mail App unusable.  If at a later time I add back the latest version and it behaves the same way, I will be happy to provide the error/crash log. Thank you.


host: Add support for LE Set Data Related Address change command

Add API to send LE Set Data related Address change HCI command

@sjanc  , please take a look

Hi,
Could you rebase so that CI tests kick in?

Hi,
Could you rebase so that CI tests kick in?

Yes . done now.

@sjanc  , can you please take a look as have rebased the PR.

Hi,
Why not put this configuration in advertising parameters and handle it there? Instead of adding dedicated API that just wraps HCI command

Hi,
Why not put this configuration in advertising parameters and handle it there? Instead of adding dedicated API that just wraps HCI command

Thanks for the review. There is no harm in setting the reasons as part of advertising parameters and issuing this command.
But spec says "This command may be used while advertising is enabled".  This gives a thought , that this HCI command can be invoked later on also with a reason code as per use case which may not be provided when advertising was enabled? A standalone usage of sending the HCI command is possible. That is why created a separate API.  But please let me know if this understanding of mine is incorrect.

Hi,
sorry for late reply,  fair enough, so this can be separated API but I'd make some changes to it to follow NimBLE API convention more closely (and bit more future proof)


s3 - should be optional and s3_dir var should come from env

some people will serve files another way

Done


3D Physics RigidBody: distance on elevator not equal

Godot version
3.5.1.stable
System information
Windows 10
Issue description
I have an elevator (KinematicBody -> Box) going down and up, where my Rigidbody ball lies on it.
The 3D Physics engine (Godot and Bullet) calculates very different distances from my RigidBody to the KinematicBody when its going down or up. I would expect an equal distance.
Is this a bug?

Steps to reproduce
test project bellow
Minimal reproduction project
godot221024_3d_physics_elevator_test.zip

Try adjusting the collision safe margin: https://github.com/godotengine/godot/blob/2b1544b4f47bfeec71c552ce57ff8322ec3e3cfb/doc/classes/KinematicBody.xml#L157-L162

Hi Calinou, sync_to_physics=true fixed it, thank you


CMake: replace -c11 with -c1x for GCC 4.6 (resolves #11)

Solution taken from: https://stackoverflow.com/questions/16256586/how-to-enable-c11-on-later-versions-of-gcc
Not sure if the "old" flag works on all later versions of gcc or if a distinction is necessary.
For reference, the cross build target is based on Ubuntu 12.04, I think it's reasonable to still support it (-> https://github.com/japaric/cross/blob/master/docker/x86_64-unknown-linux-gnu/Dockerfile)
Resolves #11

TIL. Did that solve the problem?

Yes: https://travis-ci.org/bwasty/gltf-viewer/builds/279298696


fix(updateApi): apply flow for v2

Issue
https://github.com/gravitee-io/gravitee-cockpit/issues/1376
Description
Updating an API with mock policies doesn't update the flows for APIs in v2.

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.


[react-stately][useControlledState] Allow undefined params

Closes #1859
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests). (No existing way of checking types found, so I couldn't test this.)
[x] Filled out test instructions.
[x] Updated documentation (if it already exists for this component).
[x] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Try doing useControlledState(undefined, undefined, undefined) in typescript with strictNullChecks compiler option turned on. There should not be any TypeScript errors.
🧢 Your Project:
https://github.com/ChocolateLoverRaj/color-picker

Not sure about this - see my question
https://github.com/adobe/react-spectrum/issues/1890#issuecomment-841550833

Not sure about this - see my question
#1890 (comment)

@dannify This pull request fixes #1859, which fixes strictNullChecks errors on packages using @react-stately/utils. This pull request doesn't require the strictNullChecks compiler to be turned on for this package, which is what #1890 is about. This PR only adds 3 | undefineds to the code.

Yes but as you said, it only solves it for one package and would be introducing the method for solving this problem across all of our packages (even if we did it incrementally) so I want to look at alternative ways to solve the problem as a whole.

@danify while it may be hard to solve this problem for all packages, for now you are making it inconvenient for people who do use strictNullChecks.

Correct me if I'm wrong but without this fix you can't really use this utility as intended in a TS codebase with strict or structNullChecks set to true? Was really looking forward to a clever drop-in solution.

please merge this

I turned on our strict type checking for this file, I believe this PR to be wrong. I've opened a PR to address it here https://github.com/adobe/react-spectrum/pull/3926


[iOS] "Project Name" was compiled with optimization - stepping may behave oddly; variables may not be available.

Hi.
I have been receiving the message:
[PROJECT NAME] was compiled with optimization - stepping may behave oddly; variables may not be available.
This is happening on iOS when I send a message to the websocket server. When the cordova socket server receive the message the app crash. According to my investigation the problem is due to how the libPocketSocket.a was optimized during the build process.
The same error was reported here using others libraries.

https://stackoverflow.com/questions/32772573/project-name-was-compiled-with-optimization-stepping-may-behave-oddly-varia
https://stackoverflow.com/questions/45078851/optimization-stepping-may-behave-oddly-ios-unity

I've been using this versions:
Cordova (Cordova CLI) : 8.0.0
Cordova Platforms: ios 4.5.5
iOS Deployment Target: 10.0
Here the error, pointing to PSWebSocketDriver._initialFrame

I am triying to recompile PocketSocket.
Does anybody have an idea how to solve this issue?

Closing old issue. Feel free to reopen.

Hi @rsax, I'm having the same issue. Did you solve it somehow?


Getting error while calling from App engine

Hi,
Can you please help to solve this
I am trying to call below function on Google AppEngine development server and getting the error.
But without appengine getting the record details from salesforce.
func init() {
	// Init the force
	forceApi, err := force.Create(
		"v39.0",
		"****************************************",
		"*******",
<EMAIL_ADDRESS>		"******",
		"*******",
		"production",
	)
	if err != nil {
		log.Fatal(err)
	}

	// Get somCustomSObject by ID
	someCustomSObject := &SomeCustomSObject{}

	err = forceApi.GetSObject("a0K0I00000DlwBQ", nil, someCustomSObject)
	if err != nil {
		fmt.Println(err)
	}

	fmt.Printf("%#v", someCustomSObject)

I am getting below error
the runtime process for the instance running on port 57472 has unexpectedly quit
2018/08/21 15:16:24 Error sending authentication request: Post https://login.salesforce.com/services/oauth2/token: http.DefaultTransport and http.DefaultClient are not available in App Engine. See https://cloud.google.com/appengine/docs/go/urlfetch/

App Engine Standard requires you to use the URL Fetch service to make HTTP requests. https://cloud.google.com/appengine/docs/standard/go/issue-requests
Unfortunately go-force doesn't support swapping out the Default HTTP Transport.
The easiest way to get around this would be to use App Engine Flexible which allows for the Default HTTP Client.
Alternatively some work was done by @jjordan to support setting your own http client in https://github.com/nimajalali/go-force/pull/39. However this will only set the http client globally and can/will run into race conditions if used in app engine for each request.
ctx := appengine.NewContext(r)
client := urlfetch.Client(ctx)
force.HttpClient = client

Ideally go-force would have a construct to set the HTTP Client per instance of go-force as outlined in #44, unfortunately I don't have the time to do this right now. PR's are always welcome.

@nagaraja-sv Good news! With the new go111 runtime on App Engine Standard you should be able to do this.
https://blog.golang.org/appengine-go111


Update introduction.md

Fix a typo.

Pull Request Test Coverage Report for Build 1

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 87.85%

Files with Coverage Reduction
New Missed Lines
%

lib/tortoise/package/connect.ex
1
88.24%

Totals

Change from base Build 39:
-0.2%

Covered Lines:
564

Relevant Lines:
642

💛  - Coveralls

Thanks. At least I got the file name right :)


About code

Hello,thank your great project! I come again!
In the modules/RFRNet.py, the class RFRNet ,what is the work of self.RFRModule.att.att.att_scores_prev = None         self.RFRModule.att.att.masks_prev = None?
Looking forward your reply

This part is for initializing the attention scores of KCA in each feed forward process. During testing, this line of code is not important. But during training, without this line of code, the attention score will be messed up.

Thank your reply!

But Why use three attin the code self.RFRModule.att.att.att_scores_prev = None ?Why not use aatt? Example,self.RFRModule.att_scores_prev = None .

First .att is because the AttentionModule is part of the RFRModule.
Second .att because KnowledgeConsistentAttention is part of the AttentionModule. The AttentionModule is a module that combines KnowledgeConsistentAttention with standard (before attention) to create a combination thru a learnable point wise (kernel size 1) convolution layer (the combiner).
And finally, att_scres_prev and masks_prev in KnowledgeConsistentAttention is kind of like an initial parameter that is initialized at the beginning of an inpainting process. A bit similar in idea to how we initialize the hidden state in the decoder in a LSTM/GRU model.
Just my 2 cents.

First .att is because the AttentionModule is part of the RFRModule.
Second .att because KnowledgeConsistentAttention is part of the AttentionModule. The AttentionModule is a module that combines KnowledgeConsistentAttention with standard (before attention) to create a combination thru a learnable point wise (kernel size 1) convolution layer (the combiner).
And finally, att_scres_prev and masks_prev in KnowledgeConsistentAttention is kind of like an initial parameter that is initialized at the beginning of an inpainting process. A bit similar in idea to how we initialize the hidden state in the decoder in a LSTM/GRU model.
Just my 2 cents.
Thank your reply！  Good lucky


[FLINK-28369][table][python] Support PARSE_URL in Table API

What is the purpose of the change
Support instr and locate built-in functions in Table API.
Brief change log

Support PARSE_URL built-in functions in Table API.
Support PARSE_URL built-in functions in Python Table API.

Verifying this change
This change added tests and can be verified as follows:

Added test that validates that PARSE_URL in Table API work
Added test that validates that PARSE_URL in Python Table API work

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

@flinkbot run azure


IPv6 test fixes

Use getaddrinfo() to find localhost address/family for tests
Use try/finally in Test_nb_quit_with_conn to avoid hit-enter prompt on a failure

BSD doesn't seem to like this change.

Yeah, I'll look into that tonight, hopefully.


Initial version of lammps kokkos

Github says there are some conflicts we need to work out.

Conflicts fixed!

Thanks guys!


⚠ Bofrost.com has degraded performance

In a8a0a80, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1959 ms

Resolved: Bofrost.com performance has improved in 9b8f98c.


[SPARK-47968][SQL] MsSQLServer: Map datatimeoffset to TimestampType

What changes were proposed in this pull request?

This PR changes the datatimeoffset -> StringType mapping to datatimeoffset -> TimestampType mapping as we use mssql-jdbc for Microsoft SQL Server. spark.sql.legacy.mssqlserver.datetimeoffsetMapping.enabled is provided for user to restore the old behavior.
Why are the changes needed?

With the official SQL Server client, it's more reasonable to read it as TimestampType, which is also much more compliant with other jdbc datasources
Does this PR introduce any user-facing change?

Yes, (please refer to the first section)
How was this patch tested?

new tests
Was this patch authored or co-authored using generative AI tooling?

no

Irrelevant test failure in pyspark connect
ERROR StatusConsoleListener An exception occurred processing Appender File
 java.lang.IllegalArgumentException: found 1 argument placeholders, but provided 0 for pattern `0, VisitedIndex{visitedIndexes={}}: [] r:0`
	at org.apache.logging.log4j.message.ParameterFormatter.formatMessage(ParameterFormatter.java:233)
	at org.apache.logging.log4j.message.ParameterizedMessage.formatTo(ParameterizedMessage.java:266)
	at org.apache.logging.log4j.core.pattern.MessagePatternConverter$SimpleMessagePatternConverter.format(MessagePatternConverter.java:120)

Thank you @dongjoon-hyun
Merged to master.


feat: 🎸 add new large button size for jumbotrons/heroes

Preview:

Use-case:

👋 Thanks for creating a pull request! 🚀 Checkout the storybooks we've created for it: chlorophyllreactangular

it seems like your change introduces a new class name "large" but it does not seem to remove the "size-lg" class which applies the same styles. I noticed that there is also a modal component which does a similar thing so maybe there needs to be a better standard for class names regarding sizing for chlorophyll before we proceed with this change (or perhaps as part of this PR?. @vsjolander any thoughts on this?

it seems like your change introduces a new class name "large" but it does not seem to remove the "size-lg" class which applies the same styles. I noticed that there is also a modal component which does a similar thing so maybe there needs to be a better standard for class names regarding sizing for chlorophyll before we proceed with this change (or perhaps as part of this PR?. @vsjolander any thoughts on this?

Oh missed this before reviewing and merging... Yes I agree we should set a standard..
To be honest I hadn't seen the size-lg class before 🙈 Maybe this could be quite nice to actually have a [property]-[value] standard for these things. We can tie it to what the property name is in Figma and what the prop is named in React or Angular.
@splashdust @Maximilian-R do you have any input on this?
Since this has to be refactored everywhere I merge these changes since they are good enough for now! But would like to set a standard for sure!


Add constraint dependencies to pyproject.toml

Resolves #4467.
Summary
This PR implements the following

Add tool.uv.constraint-dependencies to pyproject.toml
Support to refer tool.uv.constraint-dependencies in uv lock
Support to refer tool.uv.constraint-dependencies in uv pip compile/install

These are analogues of the override features implemented in #3839 and #4369.
Test Plan
Add test.

Thanks, this is looking great! Do you mind adding the analogous changes to crates/uv/src/settings.rs? See overrides_from_workspace.

I modified crates/uv/src/settings.rs to reference tool.uv.constraint-dependencies.

Incredible! We had one use-case where we might have been forced to use the pip interface, I didn't see anything in the docs, but luckily Google surfaced this PR! Works perfectly.


Add Typia Support to nest js event patterns and message patterns

query on main repo
https://github.com/samchon/typia/issues/697
currently nestia supports only or rest api (get,post,put ....)
but nest also have microservice decorators Link
@MessagePattern
@EventPattern
it will be very helpfull for add typia decorater support for  this two...

Can you show me an example and detailed feature what you want?

Ok
On Tue, 4 Jul, 2023, 05:27 Jeongho Nam, @.***> wrote:

Can you show me an example and detailed feature what you want?
—
Reply to this email directly, view it on GitHub
https://github.com/samchon/nestia/issues/433#issuecomment-1619271219,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJM3EQSE4Y4PGKF2MLHIS43XONMABANCNFSM6AAAAAAZZW3S6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

So in here sending an event to microservice

and listens the event on microservice

there is not type validation support for @MessagePattern and @EventPattern.
we can make something like @TypedMicroCalls.Message and @TypedMicroCalls.Event right ?
to make validations on both ends ?

Can you suggest a well-designed interface about that in @nestia/fetcher and generated SDK side?

@denniarems you can just write a wrapper decorator for messagepattern which takes in a typia assertion function. I don't think there's any need for nestia to implement this

@jmroon Thanks for replying. @denniarems Do you agree?

@samchon  @jmroon  Can you give an example of what this wrapper decorator would look like? Thanks! :)


[spi_device] Write Enable instruction not handled in hardware for flash emulation

SPI flash devices typically have an immediate response to Write Enable / Write Disable instructions. Currently, this command must be uploaded to firmware, so subsequent Read Status commands may not see the effects of Write Enable, due to the latency of firmware's response.
We're not aware of flows in the wild that check the Write Enable Latch (WEL) after a WREN instruction, so the impact of this OT-specific quirk may not be significant. However, it is a deviation from the flash parts we're trying to emulate. If time allows, recommend having this opcode detected in hardware and update WEL.
Note: The de facto standard for the write-enable latch (WEL) is bit 1 of the status register.
CC @eunchan @tjaychen @alphan

Note that the lower severity comes from an assumption that multiple commands can queue up in the FIFO. If this is not the case, it may become critical to handle these instructions in hardware, else there will be a race with firmware.

This will be handled as part of #12137 and #12145

Closing now as features are baked in to SPI Device IP


New Extension: Upstash

Description

Displays your Upstash resources
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

hi @pernielsentikaer,

I added the error message
I fixed the command names as you said

Thanks for reviewing and giving feedback 😍


fixed mixing use of value and label

As it's the same text both for label and value in your sample data.

Thanks for the fix!


DMA for l552

Hi,
are there any plans to implement the DMA for l552? I was not able to find any working DMA solution.
Best
Thomas

No. I think I tried, but ran into PAC-related issues. Probably not a huge lift, but I don't have time ATM. PRs accepted.


Question about findNeighbors

It looks like this returns only contacts that the node knows about.  The Kademlia spec refers to a "node lookup" that hits its closest nodes with FIND_NODE RPC's to find closer nodes.  Is that implemented here?
Ah - I see that's implemented in SpiderCrawler.  OK, gotta see how/when that's called.  Sorry for the premature question, I'm trying to map the Kademlia spec to various implementations (and yours is at the top of readability and clean, across multiple languages I'm looking at) and the thing that's confusing me at the moment in the spec is when the crawl occurs (always, or just for FindNode, or for a specific other call?) and to what recursion depth FindNode crawls to (this last one is particularly of interest because I could see the crawler never ending.)

The crawler ends when it can't find any nodes closer than ones it has previously seen (see here).  If you have any other questions - please feel free to email me (trying to keep the issues clean except for possible issues).

Thank you Brian.  Do you have a direct email?  I'm in the process of
writing a C# implementation for Code Project, both as a contribution to the
community and as a way of deeply understanding the Kademlia specification
(there seems to be two specs!)  As I'm going through this process, I'm
finding that I'm referencing your code more and more as the authority
implementation.  I find your work to be excellent and helps to answer many
questions.  And I definitely envy Python and its ability to handle numbers
as large as 2^160 - in C#, I would have to resort to using the BigInteger
class!
Regards,
Marc
www.marcclifton.com
518.721.8353
|
www.higherorderprogramming.com
Change the way you interact with the world
On Mon, Aug 28, 2017 at 4:09 PM, Brian Muller<EMAIL_ADDRESS>wrote:

The crawler ends when it can't find any nodes closer than ones it has
previously seen (see here
https://github.com/bmuller/kademlia/blob/master/kademlia/crawling.py#L97).
If you have any other questions - please feel free to email me (trying to
keep the issues clean except for possible issues).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bmuller/kademlia/issues/30#issuecomment-325465723,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADUDtDvZhXV6cYv3x-DcqIFJYUwKeEN3ks5scx6IgaJpZM4PEt4n
.

Hey @cliftonm - thanks so much!  Glad you're finding the lib so useful!
Feel free to email the address on my profile page https://github.com/bmuller
Thanks!


When i open two Projects at the same time then git in not working in second Project.

@garvitjoshi please provide more detailed steps. What do you mean by 'open two projects at the same time'. What do you mean by 'git not working'.

![screenshot from 2017-05-11 12-33-29_li 5]
(https://cloud.githubusercontent.com/assets/15026629/25936959/765974dc-3647-11e7-975b-db4b18222f10.jpg)
Hello @egamma here I attach an image in which my two different projects are open in vscode. but one of them not showing my git branch(that is my second Project that means before that I already open different project and that is my first project ).

Can you try out our insider release?

I want to say that sometimes it's working sometimes not. I think it's a small bug. and sure I'll check it in insider release. and one more thing when I install insider release I want to install all extension which was installed on my previous vscode and that is ridiculous for me. so, I think you can do one more thing that is login or signup in vscode and when a user install extension so he/she can access all his extension by the help of simple login in vscode means he/she can see it's installed extensions in vscode.

Copy ~/.vscode/extensions to ~/.vscode-insider/extensions.

Thanks, buddy you save my lots of time. for ~/.vscode/extensions to ~/.vscode-insider/extensions.

I've got the same issue since I updated from 1.11.0 to 1.12.1.
It happens fairly systematically for me that the first instance of vs code functions correctly, but any further instances have the git issue.
So when running code path_to_project1 and then code path_to_project2 project1 has git functionnality and project2 doesn't.
A project started first:

The same project started second:

Interestingly enough, sometimes if I close the first instance, the second one will refresh and git will function again.
I tried the insider release though, and was no longer able to reproduce the issue.

I tried the insider release though, and was no longer able to reproduce the issue.

Great.
Closing as seems fixed in Insiders. Please confirm @garvitjoshi


WIP: [chore] update and refactor configurations.

Update packages and configurations.
Upgrade Path (for changed or removed APIs):

None

Acceptance Checklist:

[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 86.697% when pulling b21ac5039910e55dc53b246ade8af92537bee51b on diasbruno:chore/update-and-refactor-configurations into 1b561fc54f107df583281667eb92e7975ec33ba8 on reactjs:v4.

Thanks, @konekoya. Version 4 is on the way. :)

Wow, that's really cool! Can't wait to see it 💯


[feature request]Need inspect command to get the detailed information of container

Issue Description
We need inspect command to get the detailed information of container
Describe what happened:
Describe what you expected to happen:
How to reproduce it (as minimally and precisely as possible):
1.
2.
3.
Anything else we need to know?:
Environment:

pouch version (use pouch version):
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

#dibs


🐛 Camera FPS throttles on low light, and torch doesn't always work

What's happening?
I am using a frame processor on a Pixel 6a/Note 9. I have simplified the frame processor to just not actually perform any calculations. The camera normally runs at 30 FPS according to the graph, but when I cover the camera (with a cloth, my finger, putting it on a table, etc.) the FPS drops to 15. I have tried to disable as much auto stuff as possible on the camera.
Another issue is that the torch does not turn on, even when specified "on" in the camera's props. This happens regardless of the other props. If I edit the file and hot update my app while it's running (in dev mode) it turns on the flashlight. However, if I close and reopen the app, the flashlight once again does not turn on.
These systems worked in v3.9.2 on Android and are currently working in v4 on iOS (iPhone 15pm, iOS 17.x and iPhone 11, iOS 17.x), so I believe these issues are exclusive to Android and v4.
Reproduceable Code
const device = useCameraDevice('back');

const frameProcessor = useFrameProcessor(() => {
  'worklet'
}, []);

const format = useMemo(() => {
  return getCameraFormat(device, [{
    fps: 30
  }]);
}, [device]);

return (
  <Camera
    isActive
    style={StyleSheet.absoluteFill}
    device={device}
    torch='on'
    frameProcessor={frameProcessor}
    enableFpsGraph
    pixelFormat='yuv'
    fps={30}
    format={format}
  />
);

Relevant log output
N/A

Camera Device
{
  "formats": [],
  "sensorOrientation": "landscape-left",
  "hardwareLevel": "full",
  "maxZoom": 8,
  "minZoom": 1,
  "maxExposure": 20,
  "supportsLowLightBoost": false,
  "neutralZoom": 1,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsFocus": true,
  "supportsRawCapture": false,
  "isMultiCam": false,
  "minFocusDistance": 10,
  "minExposure": -20,
  "name": "0 (BACK) androidx.camera.camera2",
  "hasFlash": true,
  "hasTorch": true,
  "position": "back",
  "id": "0"
}

Device
Pixel 6A (Android 14), Note 9 (Android 10)
VisionCamera Version
4.0.1
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[X] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

The camera normally runs at 30 FPS according to the graph, but when I cover the camera (with a cloth, my finger, putting it on a table, etc.) the FPS drops to 15

This is intended behaviour on Android, devices automatically throttle their FPS to allow more light to reach the sensor.
Also please leave the issue title as prefered in the template.

Relevant log output
N/A

This is literally the only thing I would've needed to investigate the torch issue.

Yes you can reopen once you have logs

Sorry, one last thing. Is the throttling intended behavior even when the lowLightBoost prop is set to false? It was my understanding that the throttling would only happen when that was set to true.
Also, I just wanted to say that this is one of the best react-native libraries IMO and I'm sure everyone appreciates the amount of work you put into maintaining and constantly updating and fixing things!

Is the throttling intended behavior even when the lowLightBoost prop is set to false? It was my understanding that the throttling would only happen when that was set to true.

Yea it was usually only enabled when lowLightBoost is enabled, but since I migrated from my custom Camera2 implementation to CameraX, this now is no longer configurable. So I guess we just have to accept it, maybe I'll create a feature request in the Google issue tracker but they only have setTargetFps(...), no min or max.

Also, I just wanted to say that this is one of the best react-native libraries IMO and I'm sure everyone appreciates the amount of work you put into maintaining and constantly updating and fixing things!

Thank you so much, much appreciated!
Hope you don't take offense in me closing issues without logs, but otherwise this just gets way too messy :)

Hi Marc, I wanted to touch back on this issue. It seems as though CameraX doesn't let you change the low light boost option manually because it's wrapping the Camera 2 hardware API (?) or something like that. Either way, I was able to get it to behave correctly by adding this code to the frame processor output configuration in https://github.com/mrousavy/react-native-vision-camera/blob/f8b40fd7c7df33d9436ce62cdb2eaa01a652c238/package/android/src/main/java/com/mrousavy/camera/core/CameraSession.kt#L347-L358
val analyzer = ImageAnalysisBuilder().also { analysis ->
  if (fpsRange != null) {
    val camera2Interop = Camera2Interop.Extender(analysis)
    camera2Interop.setCaptureRequestOption(
      CaptureRequest.CONTROL_AE_TARGET_FPS_RANGE,
      fpsRange
    )
  }

  // ...
}

I also needed to add the opt in annotation for the interop:
@OptIn(ExperimentalGetImage::class, ExperimentalCamera2Interop::class)
@SupressLint("RestrictedApi")
@Supress("LiftReturnOrAssignment")
private fun configureOutputs(configuration: CameraConfiguration) {
  // ...
}

I'm not sure of the stability but so far I haven't experienced any issues. As far as I'm aware, this should only affect the FPS range of the auto exposure which is what's causing the low light boost to decrease the FPS even when set to false in the <Camera /> component.
I've also tested with setting low light boost to true and it works as expected because I'm just using the fpsRange value that has the lower range as fps / 2 when low light boost is set to true.
I don't plan on submitting a PR because I don't know enough about this library to holistically know what this change would affect, but for my purposes it seems to work. If you think this change would be valuable let me know and I'd be happy to submit a PR -- I definitely want to contribute to this library in some way after all the time and energy it has saved me!

thanks for testing & confirming that btw

and thanks for your sponsorship! ❤

I'm glad it was able to help. Thanks for taking the time to look through it and for all the work you're doing on this library!


Spyder not working

My Spyder does not open and crashes on startup (With the popup indicated python stopped working)
Error Message on running spyder from Anaconda Console:
(base) C:\Users\ShellyGarments>spyder
Assertion failed: Protocol wrong type for socket [10041] (C:\ci\zeromq_154902559
4292\work\src\ip.cpp:417)
I’m using windows 7 and spyder 4.

Hi @dhruv-speedcuber, thanks for the report.
Could you please share the requested information on the Issue Template (it was there when you opened it)
<!--- **PLEASE READ:** When submitting here, please ensure you've completed the following checklist and checked the boxes to confirm. Issue reports without it may be closed. Thanks! --->

### Issue Report Checklist

* [ ] Searched the [issues page](https://github.com/spyder-ide/spyder/issues?q=is%3Aissue) for similar reports
* [ ] Read the relevant sections of the [Spyder Troubleshooting Guide](https://github.com/spyder-ide/spyder/wiki/Troubleshooting-Guide-and-FAQ) and followed its advice
* [ ] Reproduced the issue after updating with ``conda update spyder`` (or ``pip``, if not using Anaconda)
* [ ] Could not reproduce inside ``jupyter qtconsole`` (if console-related)
* [ ] Tried basic troubleshooting (if a bug/error)
    * [ ] Restarted Spyder
    * [ ] Reset preferences with ``spyder --reset``
    * [ ] Reinstalled the latest version of [Anaconda](https://www.anaconda.com/download/)
    * [ ] Tried the other applicable steps from the Troubleshooting Guide
* [ ] Completed the **Problem Description**, **Steps to Reproduce** and **Version** sections below

## Problem Description

### What steps reproduce the problem?

1.
2.
3.

### What is the expected output? What do you see instead?

### Paste Traceback/Error Below (if applicable)
<!--- Copy from error dialog or View > Panes > Internal Console --->

```python-traceback

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

Thanks

Please update to the latest Spyder version (4.1.3) and run there
spyder --report-segfault

After it crashes, please run again
spyder --report-segfault

Then a dialog will be shown that will allow you to upload the crash report here to Github.
If no dialog appears, please look for a file called faulthandler.log in Spyder's configuration directory (C:\Users\<your user>\.spyder-py3 on Windows; /Users/<your user>/.spyder-py3 on macOS; or /home/<your user>/.config/spyder-py3 on Linux) and upload it here.

Hi ccordoba12!
I ran the command "spyder --report-segfault" twice. This is the error message it displays:-
"usage: spyder [options] files
spyder: error: unrecognized arguments: --report-segfault"

Issue Report Checklist

[done ] Searched the issues page for similar reports
[done ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[done ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[done ] Could not reproduce inside jupyter qtconsole (if console-related)
[done ] Tried basic troubleshooting (if a bug/error)

[done ] Restarted Spyder
[done ] Reset preferences with spyder --reset
[done ] Reinstalled the latest version of Anaconda
[ done] Tried the other applicable steps from the Troubleshooting Guide

[done ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
My Spyder does not open and crashes on startup (With the popup indicated python stopped working)
Error Message on running spyder from Anaconda Console:
(base) C:\Users\ShellyGarments>spyder
Assertion failed: Protocol wrong type for socket [10041] (C:\ci\zeromq_154902559
4292\work\src\ip.cpp:417)
I’m using windows 7 and spyder 4.
What steps reproduce the problem?

Opening spyder from anaconda.
Opening spyder from anaconda prompt.

What is the expected output? What do you see instead?
It should open spyder but instead it shows a dialog box that says python has stopped working.
Paste Traceback/Error Below (if applicable)

(base) C:\Users\ShellyGarments>spyder
Assertion failed: Protocol wrong type for socket [10041] (C:\ci\zeromq_154902559
4292\work\src\ip.cpp:417)

PASTE TRACEBACK HERE

Versions
Spyder version: 4.0.1
Python version: 3.7.6
Qt version: 5.9.7
PyQt version: 5.9.2
Operating System name/version: Windows 7 64-bit
Dependencies
I don't know what are dependencies.
Thanks

I ran the command "spyder --report-segfault" twice. This is the error message it displays:-
"usage: spyder [options] files
spyder: error: unrecognized arguments: --report-segfault"

That's why I said:

Please update to the latest Spyder version (4.1.3)

So please do it and do that again.

But i’m unable to update spyder.

@dhruv-speedcuber try running
conda update anaconda
conda install spyder=4.1.3

"> Please update to the latest Spyder version (4.1.3) and run there

spyder --report-segfault

After it crashes, please run again
spyder --report-segfault

Then a dialog will be shown that will allow you to upload the crash report here to Github.
If no dialog appears, please look for a file called faulthandler.log in Spyder's configuration directory (C:\Users\<your user>\.spyder-py3 on Windows; /Users/<your user>/.spyder-py3 on macOS; or /home/<your user>/.config/spyder-py3 on Linux) and upload it here."

I tried uploading the file 'faulthandler.log.old' but Github is showing the message that "We don't support that file type."

I tried uploading the file 'faulthandler.log.old' but Github is showing the message that "We don't support that file type."

Please change the extension from .log to .txt and try again

I opened the file with FreeFileViewer. The file was empty.
And i also opened “faulthandler.txt” but it was also empty.


I2C Wiring of Shuttleboard

Hi guys,
I am using the I2C scanner for Arduino IDE (https://playground.arduino.cc/Main/I2cScanner) on an Adafruit Metro Express and can't get it to recognize the BMP388 at all. On an Arduino Uno I sometimes get it to work. I am using to 4.7k Ohm pull-up resistors on the SDA and SCL lines. Any idea why the MPL3115A2 alti on the upper image is recognized with the same wiring and the BMP388 is not? Is the wiring right?
Thank you,
Casey

Hi @Casey10110,
The board is connected upside down. In addition, You need to supply both VDD and VDDIO. SDO is the I2C address select and should be connected to either VDDIO, or GND. The CSB pin should be tied to VDDIO.

Ha! I forgot about the upside down part, I actually ended up fixing that after I took these pictures, but I was getting the same results. Thank you SO MUCH for helping me out here, I will give that a try ...

OK, I am getting the same result when wired up (as I understand it) like in the datasheet, on both an Arduino Uno and an Adafruit Metro Express:

Is this wiring right? What am I missing.

The line connected to A0 should be connected to 3.3V.

This still isn't working. I actually have two different shuttle boards from you guys and for one, it finds a device at every address, and with the other, it finds no devices with the following wiring:

Any more ideas?

Hi @Casey10110,
Please refer the connection table below,

Shuttle pin number
Purpose
Connection in I2C

1
VDD
3.3V

2
VDDIO
3.3V

3
GND
GND

4
SDO (I2C addr SEL)
GND or 3.3V

5
SDI
SDA

6
SCK
SCL

7
CSB
3.3V

In addition, make sure that you use a 3.3V board to communicate with the sensor as the sensor has a maximum voltage tolerance of 3.6V. Any I2C pull-ups would in addition have to be connected to 3.3V.

Frustrating, the wiring you describe there is exactly what I have on the top image and it still doesn't work. The board has 3.3v logic.

@Casey10110,
Could you modify the I2C scanner code regarding the transmission to,
Wire.beginTransmission(address);
Wire.write(0x00);
error = Wire.endTransmission();

Super strange guys ... same exact result. I really appreciate you trying to help me here. I have no idea why it isn't working. I have two different BMP388 shuttleboards from you guys, and I am using two totally different boards to run it: UNO and METRO Express. Same result in every combination. Anybody else here had success with either of these boards? I can't get it to work.

Do you guys have any other ideas of why this isn't working ... nobody is chiming in here. Could it be that both boards are defective?

OK thank you very much for testing it. I guess I will have to buy another board and give it another shot. Perhaps I did end up damaging them.

OK, I bought another board, wired it up, and had the exact same result. This board never touched a 5V device, so it is a different problem. I suppose I will take this over to an Adafruit forum, as nothing seems to help over here and I am using a Metro Express M0.

Hi @Casey10110,
Have you already checked the continuity of the wires and the breadboard that you are using?


Fixes for card overflowing issue

Fixes Issue

**My PR closes #502 **
Changes proposed
What were you told to do ?
I was told to fix the issue of Club card overflowing at the bottom of the page. This was the issue screenshot !

What did you do ?
I made some component changes and added a few div to contain the issue and changed 'postition' variant for them. I also had to change the padding and gapping for the card from % to px and eliminate auto calculation for all the responsive modes !

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[X] This PR does not contain plagiarized content.
[X] The title and description of the PR is clear and explains the approach.

Screenshots

I tried to apply some changes, @IAmTamal have a look >
That's in 100% screen resolution >
Change you wanted >

Originally >

I personally feel that the previous one looked better. Lemme know which one should I keep ?


side bar scroll

Side bar dont show scroll when browser size is less to bar height, this is hidden. thanks for your help.

Can you elaborate a little bit on this one?

When the lateral menu is higher than the window size does not appear scroll to display the options at the end of the menu ; the content exceeds the window is being hidden and you can not select these options. In the version startbootstrap -sb -admin" scroll the menu works correctly .


Added link to Dedalow / NTT blog post

Added link to Dedalow / NTT blog post
Signed-off-by: Carlos Mendible<EMAIL_ADDRESS>

Closing since already added in: https://github.com/dapr/community/pull/214


Set up the environment for rkt stage2 (container).

Hi Bharani - With this change - is the nginx container coming up ?


WIP: Refactor the  component

Original PR: https://github.com/artsy/emission/pull/1055
As always, a couple of my small refactor attempts ended up being a larger fix 😅 Basically what this PR does are:

moves the Ends ... or Live ... label to the <Timer> component
replaces the hard-coded "YYYY-MM-DDTHH:mm:ss+-HH:mm" format specifier with moment.IOS_8601 that's more robust
converts the time to a "timezone-ed" date and shows the month, date, and hour in the user's time-zone (added moment-timezone to implement this)

Now one of the tests for the <BidResult> component depends on the machine's local timezone. We should figure out how to avoid test polutions.
Remianing Todos

[x] fix the tests that depend on the local time zone marked as pending

Fails

:no_entry_sign:

🃏 FAIL in BidResult-tests.tsx

renders winning screen properly

Snapshot has changed

Full message

Error: expect(value).toMatchSnapshot()
Received value does not match stored snapshot 1.

Snapshot

Received

@@ -94,11 +94,11 @@
undefined,
]
}
>
Live

      Jan 1, 7am

      Jan 1, 12pm
    </Text>
    <Text
      accessible={true}
      allowFontScaling={true}
      ellipsizeMode="tail"

at Object. (/home/travis/build/artsy/emission/src/lib/Components/Bidding/Screens/tests/BidResult-tests.tsx:31:16)
at Object.asyncFn (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/jasmine_async.js:82:37)
at resolve (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/queue_runner.js:52:12)
at Promise ()
at mapper (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/queue_runner.js:39:19)
at promise.then (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/queue_runner.js:73:82)
at

renders timer and error message when bid is low

Snapshot has changed

Full message

Error: expect(value).toMatchSnapshot()
Received value does not match stored snapshot 1.

Snapshot

Received

@@ -155,11 +155,11 @@
undefined,
]
}
>
Live

    Jan 1, 7am

    Jan 1, 12pm
  </Text>
  <Text
    accessible={true}
    allowFontScaling={true}
    ellipsizeMode="tail"

at Object. (/home/travis/build/artsy/emission/src/lib/Components/Bidding/Screens/tests/BidResult-tests.tsx:51:16)
at Object.asyncFn (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/jasmine_async.js:82:37)
at resolve (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/queue_runner.js:52:12)
at Promise ()
at mapper (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/queue_runner.js:39:19)
at promise.then (/home/travis/build/artsy/emission/node_modules/jest-jasmine2/build/queue_runner.js:73:82)
at

  Generated by :no_entry_sign: dangerJS

I'll go ahead and merge this PR since this has been open for quite a long time and I don't want this to be floating around.


Metrics ignored when using model.add_loss() (like in VAE example)

Hello,
I'm working with a network similar to the VAE defined in this example, and I've noticed that when a model is defined like:
>>> model = Model(inputs, outputs)
>>> model.add_loss(custom_loss)
>>> model.compile(optimizer=optimizer, metrics=['acc', custom_metric])
>>> model.fit(x_train)  # The model does not require explicit target, like an autoencoder

the metrics seem to be ignored.
I've tried debugging the problem, but it seems that the metric-defining function itself never gets called.
A solution to this is to define a second model identical to the first, but with a loss passed to compile() and an explicit target passed to evaluate():
>>> # Define two models
>>> model_1 = Model(inputs, outputs)
>>> model_2 = Model(inputs, outputs)
>>>
>>> # Compile the two models separately
>>> model_1.add_loss(custom_loss)
>>> model_1.compile(optimizer=optimizer)
>>> model_2.compile(optimizer='...', loss='...', metrics=['acc', custom_metric])
>>>
>>> # Fit one, evaluate the other
>>> model_1.fit(x_train)
>>> metrics = model_2.evaluate(x_test, x_test)[1:]
>>> print(metrics)
[acc_value, custom_value]

but besides being inconvenient, this also means that there is no way of monitoring the metrics during the training of the first model.
I'm on Keras 2.1.4, Tensorflow 1.5.0.
Is there a workaround for this or should I just hack a solution together like the one I tried above?
Thanks,
Daniele

I have same question and any progress?

I am still facing the same problem. any progress ?

@emnajaoua model_1 is compiled with the custom loss that you add via 'add_loss', model_2 is compiled with any usual loss (e.g. MSE) and the metrics. Since the two models share the same weights, training model_1 and evaluating model_2 will give the desired behavior (just ignore the loss in model_2).

@danielegrattarola Thank you for the clarification. I didn't know previously that by instantiating the models , they will share the same weights.

Hey, here's a dirty work around this issue

model.compile('adam')

# add your custom metric
model.metrics_tensors.append(K.mean(metric_tensor))
model.metrics_names.append("my_custom_metric")

Note: add this code after you compiled your model

Wow, ok. A big thanks to @tik0 and @May4m here. I'm working on the same VAE example and wanted to do (what I thought would be) the dead-simple task of tracking the KL portion of the loss and the reconstruction portion of the loss separately during training. Have been banging my head against a wall for hours and had no idea why my metrics were being completely ignored.
@tik0 maybe I'm just misunderstanding but does line 443 still line up with the conditional that was causing the problem? I'm not seeing the connection but I 100% believe that there's a non-sensical conditional check in there somewhere since May4m's workaround works.
FYI for clarity, the "metric_tensor" portion of the code snippet that @May4m provided is where I put my custom metric function, which can take more arguments than just (y_true, y_pred). So I'm doing something like the following:
model.metrics_tensors.append(calc_mse_alone(inputs, outputs, input_dim))
model.metrics_names.append("mse")

model.metrics_tensors.append(calc_kl_alone(z_mean, z_log_var))
model.metrics_names.append("kl")

Thanks for help everyone!

@sometimescasey one way to track the KL portion could be by making a custom KL loss function that "hacks" the value of y_true to be always None
Therefore your model should return the reconstruction and the latent_variable :
model = tf.keras.Model(image, [reconstruction, latent_variable], 'VAE')
You can create your custom KL function as:
def CustomKL(y_true=None, y_pred=None):
     return compute_KL(y_pred)

Assuming the layers that output reconstruction and latent_variable are called reconstruction and latent_variable you can then define the loss as a dictionary:
all_losses = {'reconstruction': 'mse', 'latent_variable': CustomKL}
Finally you can pass this to model.compile
model.compile(Adam(), all_losses)
Then model.fit should track all the losses separately


Luisb90/ngx navbar

Summary
Added a navbar component with configurable nav items. An animated sliding bar indicates which nav item is currently active. Added a new demo page to showcase the component.
Checklist

[x] *Added unit tests
[x] *Added a code reviewer
[x] Updated the demo page
[x] Included screenshots of visual changes

*required

Code and tests look good but there is some change detection funny business happening when the component is initialized to an index > 0

added a routing example to the demo page and fixed up the init behavior. also ran latest prettier

Looks good, a few comments/questions:

Can we add code examples in the demo page?
Our left nav component is called ngx-nav-menu, and this is called ngx-nav. Should we consider giving them more distinguishable names now that we have two different types of navs?
Is the height correct? The icon doesn't seem vertically centered, and the component seems taller than what  our toolbars are.

Updated the demo page with code examples

Well the top level component is called ngx-navbar. I renamed the subcomponent from ngx-nav to ngx-navbar-item, is that better?

good catch, updated the height to match the height of the navbar in platform

@marjan-georgiev


point away from alea for physics models

Several look to alea to understand our signal or background model, this adds a short text to point out that alea takes this from otherwhere

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 90.731%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1439

Relevant Lines:
1586

💛  - Coveralls


Slight typo in the examples

Issue in ./help/edge/data-collection/collect-commerce-data.md

Thank you for reporting this issue. We are reviewing the documentation and will update accordingly.
Tracking internally: https://jira.corp.adobe.com/browse/PLAT-110689

Documentation has been updated.
https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/collect-commerce-data.html?lang=en#examples


word Blanks

Challenge Word Blanks has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function wordBlanks(myNoun, myAdjective, myVerb, myAdverb) {
  var result = "";
  // Your code below this line

  string.result = myAdjective + " " + myNoun + " " + myVerb + " " + myAdverb;
  // Your code above this line
  return result;
}

// Change the words here to test your function
wordBlanks("dog", "big", "ran", "quickly");

ReferenceError: string is not defined
Please use the Help chat room for getting challenge related help. Happy Coding!

@Pujachaubey  your code worked for me .


[XamarinProfiler-MAC]: Accessibility: Color Contrast: MAS1.4.3: Copy rights text in About Xamarin Profiler is not having color contrast ratio of 4.5:1

Steps to Reproduce

Follow the pre-requisite to launch the xamarin profiler application.
Navigate to "Xamarin Profiler" menu tab and invoke it.
Navigate to "About Xamarin Profiler" menu intem under "Xamarin Profiler" and invoke it.
This will invokes the "About Xamarin Profiler" Popup window.
Verify the color contrast ratio for "Copy right" text in About Xamarin Profiler

Pre-Requisite:
1.Install Xamarin Profiler.
2.Launch Visual Studio.
3.Create a project and build the solution.
4.Navigate to Run Menu Tab and Invoke it. Navigate to "Start Profiling" option and invoke it.
5.This will invokes "Xamarin Profiler" application.
Expected Behavior
Color contrast ratio should be minimum 4.5:1
Actual Behavior
Color contrast ratio is less than 4.5:1 i.e, 3.4:1
See the screenshots attached
User Impact
Low vision user will feel difficult in seeing the text
Screenshot

Environment
macOS High Sierra OSX version: 10.13.4
Visual Studio for Mac Enterprise version: 7.5.2(build 40)
Xamarin Profiler version: 1.6.3-400

Log File

Please add the following labels to this bug:
A11yMAS
Accessibility
MAS1.4.3
Xamarin-Profiler-MAC
Wipro


React Three Fiber

Before you start, please make sure to:

[X] Read the doc
[X] Have tried the latest version
[X] Search to see if your issue already exists
[X] Look for / ask questions on Stack Overflow

What problem does this feature solve?
Hi there, I really like what you've created! Would it be possible for you to also provide versions for React Three Fiber?
What does the proposed API look like?
React Three Fiber

Hello, this project is vanilla, there's no way preventing you from using it in any framework.

i am getting an error
when using it in this code , this is nextjs alone without react three fiber
import React from "react";
import WebGLFluid from "webgl-fluid";
const index = () => {
WebGLFluid(document.querySelector("canvas"), {
// options
});
return ;
};
export default index;

i am getting an error
when using it in this code , this is nextjs alone without react three fiber
import React from "react"; import WebGLFluid from "webgl-fluid";
const index = () => { WebGLFluid(document.querySelector("canvas"), { // options }); return ; };
export default index;

here is the code

Repo

It's a common error in SSR project, you should make sure to load the plugin when window is avaliable.
Only minimal reproduction is acceptable, you should make sure it's not caused by your own codes, thanks.

Tried everything but fails all the time
here is my code
import React, { useEffect } from "react";
import WebGLFluid from "webgl-fluid";
const index = () => {
useEffect(() => {
if (typeof window !== "undefined") {
// Your function that uses the window object goes here
WebGLFluid(document.querySelector("canvas"), {
// options
});
}
}, []);
return ;
};
export default index;

It was in react but i need to use it in react-three-fiber

Sorry, you confirmed that you've searched Stack Overflow, so what's the conclusion?
There are so many similar questions like https://stackoverflow.com/questions/55151041/window-is-not-defined-in-next-js-react-app.

The reproduction should be a minimal and whole link, check https://antfu.me/posts/why-reproductions-are-required.
You may find the problem yourself while creating that.


Normalize IAM JSON policies to facilitate comparison

https://github.com/iasql/iasql/blob/main/src/services/aws-diff.ts is not working as expected

https://github.com/iasql/iasql/blob/main/test/common/aws-diff.ts

https://steampipe.io/blog/normalizing-aws-iam-policies-for-automated-analysis
https://github.com/turbot/steampipe-plugin-aws/blob/main/aws/canonical_policy.go

This is needed for aws_sqs mapper to avoid an infinite loop on policy change.


Fixed #27060 -- Take indexes into account in inspectdb command

Ticket #27060.

Looks good to me, thanks!

Introspecting index type is currently only supported by PostgreSQL. Introspecting the index type would lead to having a vendor check for "postgresql" and hard-coding "btree" (postgresql specific term) similar to what we had discussed earlier and doing the same in the tests.
I suggest adding a comment/warning at the beginning of the generated file instead until we have a stable API to introspect for index types for the supported backends. The ticket can be kept open adding a comment about the work left, if that would be more appropriate.

buildbot, test on oracle.

I'm not sure if we should let inspectdb create indexes until we can introspect index type. Could you ask for opinions on django-developers?

Started a discussion on the mailing list - https://groups.google.com/forum/#!topic/django-developers/IKohkDzC4bE

Do you plan to return to this soon or should we close it for now?

I am back on it. Just started working on it yesterday.

I think we might see too much models.Index appear in certain cases. I'm thinking about PostgreSQL text/varchar and gist indexes on geometry fields. It would be nice to add tests about those cases, too (gis_tests/inspectapp for GIS tests).

Will come back to it afterwards, if possible.


ccsearch extension is broken

ccsearch search extension is broken and does not work.

Fixes #21
Reason:
API to fetch the search keyword invokes inputField.value property as function
call and hence throwing up exception during runtime
Fix:
inputField.value is a property can therefore should not be invoked as function
Tested on chrome and firefox

Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Thanks for fixing this!


pass through gap data (target/met) values with rounding to 4 decimal digits [MRXN23-601]

https://vizzuality.atlassian.net/browse/MRXN23-601

@andresgnlez thank you for reviewing the tiny changes in this PR. I have checked the way this works and it all looks ok - one thing I should mention is that because of reasons, the ORM gives us these values as numbers-in-a-string now (basically, because the possible precision of the db types for these values may not "fit" within JS numeric types) -- so while this "works", I wanted to make you aware of this in case you can think of any possible caveats/edge cases with this.
Or maybe I should "just" re-cast these numbers-in-a-string to proper JS numbers in the API, and avoid getting numbers in weird formats to API clients to start with... I'd do this next week

@hotzevzl happy to test this once is available in m23 instance, AFAIK the change is exclusive of the gap-data endpoint, isn't it? Let me know if you plan to extend this change through the codebase, if so, I might need to take a deeper look as we might be using Number methods straightforward in some cases or just the fact of having arithmetic operations between strings and number (they should work, but in JS world anything could happen 😬 ) scares me.


Add exercism/maintainers-admin team as codeowner

The tooling is essential to the functioning of v3. To help ensure that any changes work well with the v3 website, the exercism/maintainers-admin team is added as a codeowner.
See https://github.com/exercism/exercism/issues/5400

I don't have write permissions on this repo, so could you @ynfle merge this?


v7.3 Q's re patterns:

In Draft PR https://github.com/ECMA-TC49-TG2/csharpstandard/pull/61, I've added all the edits to support the addition of patterns.
During my research, I came across the following text on some web site that claims to be pattern-related:

In C# 7.3 we added the following contexts [https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-7.3/expression-variables-in-initializers]  in which a pattern variable may be declared:

If the expression is in a constructor initializer, its scope is the constructor initializer and the constructor's body.
If the expression is in a field initializer, its scope is the equals_value_clause in which it appears.
If the expression is in a query clause that is specified to be translated into the body of a lambda, its scope is just that expression.

As I didn't understand how this might impact my patterns spec, I'm creating this issue for someone else to look at this list.

I have completed spec'ing the V7.3 feature to add 3 extra places in which out variables and pattern-generated local variables are permitted. The edits for these were applied to PRs 44 and 61. As such, this issue can be closed without further action.


Updated a screenshot

Changes proposed in this pull request:

One updated screenshot.

#sign-off

@geschwei please can you merge this?


[#8399] fix broken image link

ref: #8399

 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.


Push nightly image to dockerhub

fixes #4704

This change is

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-nightly

test-me-please

The build with only new stage worked fine: https://jenkins.cilium.io/job/Cilium-PR-Nightly-Tests-All/144/ , images are pushed here: https://hub.docker.com/r/cilium/nightly/tags/

test-nightly

test-nightly

test-me-please

test-nightly

test-nightly

test-nightly

Couldn't we use something like https://docs.docker.com/docker-hub/builds/#remote-build-triggers? (Search for Remote Build triggers at the end)

I didn't see an option to specify the tag the image will have. Can you give it the tag somewhere? @aanm
Separately, @nebril @eloycoto, since we are building the image again outside the VMs anyway, it might be simpler to just have dockerhub do it. I had forgotten that we don't push images up normally (the pushes we have now are to the internal repository for each test run). Whether we build remotely or push the local image, we have a dependency on dockerhub and the connection to it. It might be more reliable, however, to make a small request versus uploading our 9GB image :/
What do you think?

I realise I had asked about pushing up the exact same image that we tested with at some point. Since that isn't happening anyway, and won't happen for a while, doing even less work locally is probably better.

test-nightly

@nebril Updated the nodes with the correct docker-compose that does not affect other jobs. https://github.com/cilium/cilium/pull/4795
Tested this on nightly and LGTM and no issues with docker-compose.  Please move the comments and should be ready for merging.

@raybejjani it's on the image from the link I've pasted

@raybejjani builds in 2 minutes on jenkins host, and it weighs around 200MB
I can look into remote build triggers, but at this point nightly image is practically ready.

test-me-please

Hit #4383

test-me-please

test-me-please

Oh, nevermind then. I thought all the images were the same and large.

test-me-please