[Bug]: Bump vue-demi to ^13.x.x to support Vue 2.7

Current Behavior
I'm using Nuxt 2 with Vue 2.7 to get composition API out of the box. Project breaks after installing web3-onboard/vue cause it installs vue-demi ^12.5 as dependency which tries to import from @vue/composition-api instead of just @vue.
Expected Behavior
Projects using Vue 2.7 don't break.
Steps To Reproduce
Install web3-onboard/vue into a project that depends on vue 2.7 and run the project.
What package is effected by this issue?
@web3-onboard/vue
Is this a build or a runtime issue?
Build
Package Version
latest
Node Version
"@web3-onboard/vue": "^2.1.4"
What browsers are you seeing the problem on?
Chrome
Relevant log output
These dependencies were not found:
* @vue/composition-api in ./node_modules/vue-demi/lib/index.cjs                                                              friendly-errors 13:15:09
* @vue/composition-api/dist/vue-composition-api.mjs in ./node_modules/vue-demi/lib/index.mjs

### Anything else?

_No response_

### Sanity Check

- [X] If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a [Minimal, Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example).

@ihorbond  Thank you for the feedback through this issue, we will look into adding this shortly. We will update here as soon as we have a fix out.

@taylorjdawson Did this get fixed when you were working on your Vue 2 example?

Yes! @ihorbond Please refer to our vuejs-v2 example and let me know if the configuration there solves your issues

Yes! @ihorbond Please refer to our vuejs-v2 example and let me know if the configuration there solves your issues

Your example depends on vue v2.16.2

@ihorbond is this issue still persisting? It looks like the example repo has a ^ within the vue versions so it should resolve to the latest minor version including 2.7.x

@ihorbond is this issue still persisting? It looks like the example repo has a ^ within the vue versions so it should resolve to the latest minor version including 2.7.x

Im not sure tbh, I found the workaround at that time and never looked back haha

Great to hear! I will close this issue for now with the example shared by @taylorjdawson above


Update dropbox.yaml

Update pricing based on: https://www.dropbox.com/business/plans-comparison
I used the prices from the "Standard" plan compared to the "Advanced" plan which is where SSO access starts.

Numbers look better for them now – the $18 plan is exempt because it only allows one user, and their SSO pricing came down. Still on the list. Thanks.


Fix recipe by adding version bound on setuptools because of numba

Checklist

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

@conda-forge-admin, please rerender


[OPENJPA-2788] addressing issue with anonymous parameters

So a slight adjustment to the hashcode and equals method of the ParameterExpression.
Not 100% sure it's right like this but it works.
I guess I'm not too familiar with the reason for the addition of the hashCode and equals in the first place.
The bottom line is that we must include in these hashCode and equals method the ability to handle the situation where the name is not specified.

@michaelwiles can you address @rmannibucau 's comment? Thanks!

I can flesh out the tests... add some more to validate various cases.
What would constitute an ambiguous parameter?
On Thu, 17 Oct 2019 at 10:05, Francesco Chicchiriccò <
<EMAIL_ADDRESS>wrote:

@michaelwiles https://github.com/michaelwiles can you address
@rmannibucau https://github.com/rmannibucau 's comment? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/openjpa/pull/42?email_source=notifications&email_token=AAODX5GJZFI2CT35DVHOZHDQPAMFZA5CNFSM4HIHX2FKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBPGNBQ#issuecomment-543057542,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAODX5H7A7Q6SLQLPFTY27DQPAMFZANCNFSM4HIHX2FA
.

--
see my blog:
http://analysis102.blogspot.com
http://audiblethoughts.blogspot.com
http://outsideofficehours.blogspot.com

From memory twice the same name with same type or not and same value or not - no more sure if both cases were needed, @struberg: do you recall?

Hi! sorry for taking so long! I opted for a slightly less impacting change. Anynomous params are now only treated as the same if they are the same instance.
The whole case is imo rather underspecified in the JPA spec. But I think it's now as good as it gets.


[SPARK-36378][SHUFFLE] Switch to using RPCResponse to communicate common block push failures to the client.

What changes were proposed in this pull request?

We have run performance evaluations on the version of push-based shuffle committed to upstream so far, and have identified a few places for further improvements:

On the server side, we have noticed that the usage of String.format, especially when receiving a block push request, has a much higher overhead compared with string concatenation.
On the server side, the usage of Throwables.getStackTraceAsString in the ErrorHandler.shouldRetryError and ErrorHandler.shouldLogError has generated quite some overhead.

These 2 issues are related to how we are currently handling certain common block push failures.
We are communicating such failures via RPCFailure by transmitting the exception stack trace.
This generates the overhead on both server and client side for creating these exceptions and makes checking the type of failures fragile and inefficient with string matching of exception stack trace.
To address these, this PR also proposes to encode the common block push failure as an error code and send that back to the client with a proper RPC message.
Why are the changes needed?

Improve shuffle service efficiency for push-based shuffle.
Improve code robustness for handling block push failures.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing unit tests.

cc @Ngone51 @mridulm  @otterc  @attilapiros @venkata91 @zhouyejoe for review.
A few minor changes that have visible performance improvements in our internal perf evaluation.
If needed, I can include the flame graphs in the jira to show more context about some of these changes.

Can one of the admins verify this patch?

On the server side, the usage of Throwables.getStackTraceAsString in the ErrorHandler.shouldRetryError and ErrorHandler.shouldLogError has generated quite some overhead.

Should be client side?

This PR has been extended with a slight protocol change so to communicate certain common block push failures to the client with an RPCResponse instead of exception stack traces.
This fixes the root cause of the 2nd and 3rd server side inefficiencies as well as making the block push failure handling more robust.
Would appreciate a fast review on this change so to commit the change before the planned 3.2 RC cut date on 08/10 as mentioned by @gengliangwang
cc @Ngone51 @mridulm @otterc @attilapiros @venkata91 @zhouyejoe @dongjoon-hyun

Ok to test

Test build #142191 has started for PR 33613 at commit 51841e4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46703/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46703/

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

Test build #142191 has finished for PR 33613 at commit 51841e4.

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

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

The test failure does not seem related to this patch.

Test build #142236 has started for PR 33613 at commit 81d70da.

@Ngone51 want to see if you have additional comments or thoughts on this PR.
Since @gengliangwang plans to cut 3.2 RC tomorrow, would be good to have this patch merged before that.

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

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46748/

@Victsm Please resolve the conflicts

LGTM if tests pass.

Ok to test

Test build #142284 has started for PR 33613 at commit edde291.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46792/

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

Test build #142289 has started for PR 33613 at commit 52b7093.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46797/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46797/

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

Test build #142289 has finished for PR 33613 at commit 52b7093.

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

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

Merged to master, had to resolve conflicts cherry-picking to branch-3.2
+CC @gengliangwang
Thanks for fixing this @Victsm !
Thanks for the reviews @Ngone51, @gengliangwang, @otterc, @venkata91, @zhuqi-lucas, @xkrogen

Test build #142284 has finished for PR 33613 at commit edde291.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

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

Hm, can this test failure:
sbt.ForkMain$ForkError: java.lang.AssertionError: Got a non-empty set [Failed to send RPC RPC<PHONE_NUMBER>491480151 to <unknown remote>: io.netty.channel.StacklessClosedChannelException]
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.assertTrue(Assert.java:42)
	at org.apache.spark.network.RpcIntegrationSuite.assertErrorAndClosed(RpcIntegrationSuite.java:394)
	at org.apache.spark.network.RpcIntegrationSuite.sendRpcWithStreamFailures(RpcIntegrationSuite.java:350)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
	at com.novocode.junit.JUnitRunner$1.execute(JUnitRunner.java:132)
	at sbt.ForkMain$Run.lambda$runTest$1(ForkMain.java:413)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

relate to this PR? Seems like this test started to fail after this change:

https://github.com/apache/spark/runs/3297511342
https://github.com/apache/spark/runs/3299079901

@Victsm, @venkata91, @zhouyejoe Please take a look at @HyukjinKwon's comment above.

@Victsm, @venkata91, @zhouyejoe Please take a look at @HyukjinKwon's comment above.

Ran RpcIntegrationSuite locally and it seems to succeed.

Looking at the test failure and the test itself, it seems that a io.netty.channel.StacklessClosedChannelException was thrown which is not in the hard-coded list of channel closed exceptions in RPCIntegrationSuite.
https://github.com/apache/spark/blob/ccead315b30764d10d8356fb0d5fce459f6e4f93/common/network-common/src/test/java/org/apache/spark/network/RpcIntegrationSuite.java#L383-L388
The fix could be to just add this exception type to the hardcoded list.
However, I also couldn't reproduce this test failure locally.

Checked on the Netty side.
So this io.netty.channel.StacklessClosedChannelException was introduced starting from Netty 4.1.52.
In April, Spark's Netty dependency got bumped from 4.1.51 to 4.1.63.
So I believe this issue started happening intermittently since that dependency version bump, and we indeed need to add this new exception type to the hardcoded list.

@HyukjinKwon @mridulm , raised PR #33713 for addressing the test failure.

Thanks for the investigation @Victsm, @venkata91 !


Remove zero border-radius on .jumbotron-fluid

See: http://v4-alpha.getbootstrap.com/components/jumbotron/#content

@vsn4ik This seems to be intentional. Per the docs:

To make the jumbotron full width, and without rounded corners, add the .jumbotron-fluid modifier class

Please correct me if there's something I'm missing.

@cvrebert Indeed, I had overlooked. Yet I think that the rounding must be processed variable $enable-rounded.

@vsn4ik The code uses the border-radius mixin, which takes care of that for us:
https://github.com/twbs/bootstrap/blob/2f257445c3d297077ce6dc06ff1b8559d36b6495/scss/mixins/_border-radius.scss#L3-L7

@cvrebert Why did .jumbotron-fluid set border-radius: 0?

Because that's what @mdo wanted for some reason.
@mdo Care to give your reasoning?

OK, still no reason @mdo?
Because that doesn't really make sense to put some border-radius then remove it if you go -fluid.
http://v4-alpha.getbootstrap.com/components/jumbotron/

The intention here is that the jumbotron extends from one edge of your viewport to another—with no gaps of any kind on either side. Thus, there should be no rounded corners for that.


Add DTDL to JSONifier

Dear Tyler,
I am currently using AL in my research and have recently explored the possibility of utilizing Digital Twins Definition Language v3 for the instantiation of some agents in AL 8.9. In addition to my research, I have observed that several major companies, such as Microsoft and Siemens, are increasingly adopting DTDL for digital twins.
Given that DTDL is JSON-LD based, I believe there is potential to advance support in this direction. Perhaps a separate "DTDLifier" could be developed to facilitate this integration.
I am very interested in contributing to this development if you decide to support DTDL. Please let me know if there is any chance to advance support for DTDL in AL 8.9.
Thank you in advance for considering this request. I look forward to your response.

Hi! Thanks for the suggestion! From my (admittedly superficial) knowledge of Azure Digital Twins and DTDL, the scope of what you're proposing can vary dramatically depending on the specifics.
From what I understand about ADT, you're describing the entire model through the DTDL (i.e., the environment, rules and relationships, actions, etc). From a high-level perspective, this is similar to what you're doing when defining a model through AL and the "languages" it provides (i.e., flowcharts, statecharts, Java code, etc.).
If your proposal is to have complete support for converting DTDL to an AL model, this is definitely out of the scope of this project. That would require not only parsing the DTDL but figuring out the AL equivalents and how you can 'map' from one to the other. For example, how to link defined Commands to some code in the user's model.
The other route I can think of is just to use DTDL for the structure of how it defines its objects. Essentially you'd use it as a schema specification for agent types you've already defined in AL, with a customized serializer for converting that structure to the agent type defined in the schema. Customized serializers is already something that's in the works, namely for a way to use JSON with a different structure than what JSONifier expects.
Let me know if I missed anything or what your thoughts are!

Hi,
thank you so much for the quick reply! You are right regarding the varying scope of my post so I want to narrow it down and explain my experience. I was looking into Manufacturing Ontologies, which ties together DTDL, W3C WoT and ISA95, as an ontology for my research project. We are trying to build Green Digital Twins for sustainable manufacturing of beverages and later food.
My approach was to look at the unit level of manufacturing equipment and have a description, which is relatively flexible. Using the newest version (v3) of DTDL enables that through components and modularity. This concept would be to have one DTDL per unit and use the key concepts in DTDL for a comprehensive description.

Interface: An interface defines the structure and capabilities of a digital twin. It specifies the properties, telemetry, commands, and relationships that a digital twin can have.

Property: Properties are attributes or state variables of a digital twin. They can be read-only or writable and have a specific data type, such as string, integer, or boolean.

Telemetry: Telemetry represents data emitted by a digital twin, typically time-series data from sensors or measurements. It can include data points like temperature, pressure, or status updates.

Command: Commands are actions that can be invoked on a digital twin. They allow you to trigger specific behaviors or operations on the digital twin, such as starting a process or updating a setting.

Relationship: Relationships define how digital twins are connected to each other. They represent the associations or dependencies between different digital twins, such as a device being part of a larger system.

Schema: Schemas define the data types used in properties, telemetry, and commands. DTDL supports primitive types (e.g., string, integer) as well as complex types like enums, objects, and arrays.

Component: Components allow you to modularize and reuse common definitions across multiple interfaces. They enable you to create reusable building blocks for your digital twin models.

Here's an example of a DTDL v3 model that represents a manufacturing machine:
{
  "@id": "dtmi:com:example:ManufacturingMachine;3",
  "@type": "Interface",
  "@context": "dtmi:dtdl:context;3",
  "displayName": "Manufacturing Machine",
  "contents": [
    {
      "@type": "Property",
      "name": "machineId",
      "schema": "string",
      "writable": false
    },
    {
      "@type": "Property",
      "name": "machineType",
      "schema": "string",
      "writable": false
    },
    {
      "@type": "Property",
      "name": "status",
      "schema": {
        "@type": "Enum",
        "valueSchema": "string",
        "enumValues": [
          {
            "name": "Idle",
            "enumValue": "idle"
          },
          {
            "name": "Running",
            "enumValue": "running"
          },
          {
            "name": "Maintenance",
            "enumValue": "maintenance"
          }
        ]
      },
      "writable": true
    },
    {
      "@type": "Telemetry",
      "name": "temperature",
      "schema": "double"
    },
    {
      "@type": "Telemetry",
      "name": "vibration",
      "schema": "double"
    },
    {
      "@type": "Property",
      "name": "productionRate",
      "schema": "integer",
      "unit": "units/hour",
      "writable": false
    },
    {
      "@type": "Relationship",
      "name": "hasOutputProducts",
      "target": "dtmi:com:example:Product;1"
    },
    {
      "@type": "Command",
      "name": "startProduction",
      "request": {
        "name": "productionSettings",
        "schema": {
          "@type": "Object",
          "fields": [
            {
              "name": "productType",
              "schema": "string"
            },
            {
              "name": "quantity",
              "schema": "integer"
            }
          ]
        }
      }
    }
  ]
}

In this example:
The @id property identifies the model as a manufacturing machine with version 3.
The displayName property provides a human-readable name for the machine.
The contents property defines the properties, telemetry, relationships, and commands of the machine:
Property elements represent the machine's attributes, such as machineId, machineType, status (an enum property), and productionRate.
Telemetry elements define the data points emitted by the machine, such as temperature and vibration.
The Relationship element hasOutputProducts indicates that the machine produces products, referencing the Product model.
The Command element startProduction defines an action to start the production process, accepting productionSettings as a request parameter with productType and quantity fields.
So in essence use DTDL to instantiate agents like with the JSONifer, just in a richer format that also enables other use cases.
A customized serializer for converting that structure to the agent is essentially what it boils down to.
I would love to help and am happy to hear that something is in the works to enable that. How can i help?

Thanks for the extremely detailed explanation, including the example that tied all the mentioned concepts together.

So in essence use DTDL to instantiate agents like with the JSONifer

The part I'm missing though is that the DTDL example you provided is in an interface, not an instance. What you're describing seems to be like a conversion from a DTDL model to an AnyLogic agent type definition. In other words, the library would create agent types themselves dynamically (in traditional Java terms, auto-generated classes). To do this currently would require reverse engineering the XML which makes up the source of an AnyLogic model (which has no guarantee to remain consistent) and is way more complex than what the Jsonifier does.
The only equivalent to the Jsonifier would be if you wanted to take a DTDL instance and import it to the sim to be converted to a pre-defined agent type, with parameters that would map to everything that could be provided by the DTDL instance. The property and telemetry would likely map nicely to parameters, though there's no way to make parameters read-only. You can define enums in the AnyLogic model; they'd just need to be predefined and match up with the naming from the DTDL model. Relationships are trickier because the library would need logic to figure out a way to map whatever value is in the relationship fields to what's in the AnyLogic model (again, pre-defined).
I'm curious to know which route you were thinking about going in! Knowing that will definitely help clarify the feasibility of this.

Thanks for taking the time and effort to my request! Sry for the delayed response, I could not find time up until now.
I completely agree with you,

create agent types themselves dynamically (in traditional Java terms, auto-generated classes)

is way beyond and not part of my request.
My train of thought was rather simple. From what I gathered a DTDL Interface describes a DT with its components. If I have a DTDL file of every unit I want to have a DT for (like a machine in manufacturing) the sum of DTDL files describe my manufacturing process in a way to be able to have digital twins of the whole process. If I wanted to have a simulation that is used for manufacturing optimization, everything that is needed for this to work should be already in the DTDL files (parameters, specification, states, etc.). So my idea was, why not use this detailed description of units and processes to instantiate agents in a simulation. So basically use DTDL not only for connecting machines to their DT, but also to instantiate agents in a simulation model that generates data needed to drive the DT. Of course this has limitation and agent types would have to be compatible in their composition to be instantiated with the files.
In a more structured way:
DTDL Interface. "Interface describes the contents (Commands, Components, Properties, Relationships, and Telemetries) of any digital twin. Interfaces are reusable and can be reused as the schema for Components in another Interface."

DTDL Interface:

Describes the structure and capabilities of a digital twin of a unit
Defines properties, telemetry, relationships, and components
Acts as a template or schema for instances

AnyLogic Agent:

Represents a unit in a simulation model
Has properties, behaviors, and can interact with other agents
Can be instantiated from a predefined type

The similarity lies in how both DTDL interfaces and AnyLogic agent types serve as templates for creating instances.

Properties: DTDL properties could map to AnyLogic agent parameters or variables.
Telemetry: Could be represented as variables or outputs in agents.
Relationships: Might be translated to the sequence of units and how agents flow from unit to unit. Alternatively connections
Components: Could map to populations of agents
Command: State charts, Events, etc.

An inspiration was this paper on how DTDL and OPC UA could map to each other Proposal of Mapping Digital Twins Definition Language to Open Platform Communications Unified Architecture
Maybe I'm barking up the wrong tree, but I thought I'll share this with you to see whether it has some merit to it.

Again, thank you for such a thorough explanation! I'm starting to see where my previous disconnect was, which I'll speak to first.
The Jsonifier implementation takes advantage of the API shared across all agents, notably the parameter functions (getParameter(name), setParameter(name, value), etc.) which are the main source of initialization targets; most other sources are assumed to be assigned as part of the dynamic logic.
What it seems like you're proposing is an extension of this, also initializing variable values, nested agents/populations, other attributes (e.g., position, speed), connections, schedule events, etc. This is feasible through a much more robust specification (the Jsonifier's intention is to be as simple/inutive as possible).
The more complicated aspect is that the way people define these in their model can vary. For example, sometimes a relationship is defined via a 'Link to agents' and other times with typed variables. This could be theoretically resolved through documentation though.
Where I'm still lost though is the practical, actual nuts and bolts of the implementation and workflow.

If I wanted to have a simulation that is used for manufacturing optimization, everything that is needed for this to work should be already in the DTDL files (parameters, specification, states, etc.).

But this is backwards, is it not? The simulation is essentially a replacement for the real-world equivalent + IoT devices.
To clarify with an example, say I'm wanting to monitor/control my house's temperature/its thermostat. My (limited) understanding is that the Azure DT workflow looks like this:

Define my house (e.g., room relationships/references, thermostat-command-schema) as a model in DTDL and upload that to Azure
Install IoT devices to send out temperature and be able to receive commands
Connect my IoT devices to the Azure DT
Now I can monitor the live temperature and change the thermostat (live) from here

In diagram form:
DTDL ----(uploaded to)----v
                         AZURE
Thermostat <--> IOT <--> DIGITAL TWIN <--> Me (remotely)
^________House_________^

With a simulation model, I'm not just defining the house but also recreating the physics of temperature propagation (or recreating the effects of it) and all the dynamics of the real world system (e.g., simulating how I respond and the points in which I override the set temperature). It also serves as where experimentation/data gathering happens via running experiments. In this way, it's like a replacement for the thermostat + IoT + Azure Digital Twin platform. You could actually create a DTDL model from a simulation model; whereas, the the other way around - uploading a DTDL model to a sim - is like trying to pass it to the IoT devices.
The other (maybe obvious) thing to note is that, unlike Azure DT, syncing to the real, live system only happens at once on startup. After this point, it's assumed it has all the rules and relationships of the system baked into it so that it can accurately play out one possible future trajectory of the environment.
I imagine the true intention is to rather take whatever is outputted by the IoT device, specifically in whatever data format the Azure DT expects as input (maybe this is still referred to as being in DTDL? I couldn't find many resources on actual integration with real systems) and have some library that can parse that and apply it to the sim(?)

Also, I did read through the paper you sent (I wasn't previously aware of OPC UA, so thank you!).
From what I gather, in terms of their relationship to a simulation model, the real-time data from both OPC UA-enabled devices or digital twins defined using DTDL could be used to feed into the sim as input on its startup; this would be in whatever data format/structure is outputted by each (or by the underlying IoT device, if you wanted to go that route too).

Thanks for thoroughly reading my post and your great answer.

But this is backwards, is it not? The simulation is essentially a replacement for the real-world equivalent + IoT devices.

the real-time data from both OPC UA-enabled devices or digital twins defined using DTDL could be used to feed into the sim as input on its startup

You have grasped my theory very well, but I want to discuss the practical nuts and bolts of implementation and workflow. I hope to build on your example and give you a perspective that illustrates my use case since it aims at a different goal than Azure.
I hypothesize that a digital twin defined in DTDL (or similar) & some initial data should also contain everything needed to be useable as an agent in a simulation. There will be practical limits to the implementation in AnyLogic, but I chose to go down this rabbit hole and explore these.
Based on your example: I want to monitor/control my house's temperature/its thermostat and use a simulation to check different configurations of environment, equipment, and usages.

Define my house (e.g., room relationships/references, thermostat-command-schema, radiators, HVAC, heat sources, cooling sources) in DTDL and instantiate Agents representing the units involved.
Get DTDL for multiple HVAC, radiators, etc.
Use real-world data from IoT devices to have an initial condition to test
run the model and see how a change in initial conditions or a unit/agent/DTDL would affect my room
Now I can choose whatever setup is the right one for me

In mermaid diagram form:
graph LR
    subgraph "DTDL Definition"
        A["Define House in DTDL"]
        A --> C(Rooms)
        A --> D(AirCon)
        A --> E(Radiators)
        A --> F(Heat Sources)
        A --> G(Cooling Sources)
    end
    subgraph "Agent Instantiation"
        H["Instantiate Agents from DTDL"] --> I(AirCon Agents)
        H --> J(Radiator Agents)
        H --> K(Heat Source Agents)
        H --> L(Cooling Source Agents)
    end
    subgraph "Real-World Data"
        M["Get Real-World Data (IoT)"] --> N(Initial Room Temperatures)
        M --> O(HVAC Settings)
        M --> B(Thermostat)
    end
    subgraph "AnyLogic Simulation"
        P["Run Simulation"] --> Q(Room Temperature Changes)
        P --> R(Energy Consumption)
    end
    subgraph "Analysis & Decision"
        S["Analyze Results"]
    end
    B --> P
    C --> H
    D --> H
    E --> H
    F --> H
    G --> H
    I  --> P
    J --> P
    K --> P
    L --> P
    N --> P
    O --> P
    Q --> S
    R --> S

I want to be able to use a file that is intended for digital twins to recreate similar digital twins in an AL model to simulate their behavior and track their metrics.
How data finds its way into the sim is my next obstacle, but getting agents configured based on DTDL into a sim would be a first step.
Thanks for taking the time to understand my question and I hope I was able to convey the rough idea.

You absolutely conveyed the rough idea, so thank you for that! The only bit I'm missing in terms of the feasibility of this is the actual nuts and bolts of the implementation.
Inline with the current example, I created this DTDL definition.
Because you said you were not trying to auto-generate the model itself, just instantiate it, I needed to build the AnyLogic model, pretending there was some pre-established rules about how the DTDL concepts map to the AnyLogic model, shown in the screenshot below. For this example, writable properties = variables; non-writable properties = parameters; interace = agent type; array of an interface = agent population.

And now comes the point where the AnyLogic library (i.e., JSONifier or a new one) would come into play. Based on my understanding, the spec doc shows all example implementations using normal JSON. Thus, me/the user would provide a JSON file like this one. Is my understanding correct here?

Thank you for your immediate reaction and efforts! From what i can see, you model looks similar to what I would have envisioned given the example we used. If you built the model to this extent, a simple JSON is enough to convey the agents properties into the sim. This is kinda similar to:
Property example(analog to the Telemetry example)
This is the semantic information about the sensor in DTDL you modeled. A simple Telemetry definition of a temperature measurement, with the data type double.
    {
      "@type": "Property",
      "name": "currentTemperature",
      "schema": "double",
      "displayName": "Current Temperature"
    },

When JSON is used to serialize Property data for e.g. initial conditions.
"currentTemperature": 42.5

Based on my understanding, the spec doc shows all example implementations using normal JSON. Thus, me/the user would provide a JSON file like this one. Is my understanding correct here?

In your "house" model, the semantics of the DTDL have already been built into the model, with the JSON als properties.
In my idea, a simulation user would have to built a model but their semantic connections, states in a state chart, etc. would  be brought in by provide a DTDL file, JSON-LD, to the appropriate agents, like your ihvac.json
Additionally, a "normal" JSON (or database connection), like yours, is used to fill in information for setting the properties within the agent. Like your mymodel.json
If I had correctly interpreted "the practical, actual nuts and bolts of the implementation and workflow." I would have also posted a screenshot of my current implementation, but better late than never.
This is my model for monitoring energy consumption, which is in an early stage and needs improvement.

with this example JSON (with some meaningless double for properties):
{
    "stateConsumptionRates": {
      "OFF": 0.5,
      "IDLE": 5.0,
      "WARMUP": 50.0,
      "RUNNING": 80.0,
      "COOLDOWN": 10.0
    },
    "stateProductionRates": {
      "OFF": 0.5,
      "IDLE": 1.0,
      "WARMUP": 0.5,
      "RUNNING": 3.0,
      "COOLDOWN": 1.0
    },
    "stateTimes": {
      "OFF": 0.5,
      "IDLE": 1.0,
      "WARMUP": 0.5,
      "RUNNING": 3.0,
      "COOLDOWN": 1.0
    },
    "stateInitialProperties": {
      "intialState": 1.0,
      "targetTemperature": 1.0,
      "intialLevel": 1.0
    },
    "unitProperties": {
      "capacity": 1.0,
      "efficiency": 1.0,
      "transferRate": 600.0
    },
    "unitSpecification": {
      "Type": "Conveyor",
      "manufacturer": "Custom",
      "model": "BeltConveyor"
    }
  }

It currently works ok with my custom JSON (above), like your DTDL: "Basic House HVAC (Implementation). Instantiating agents into a population works on a basic level with:
Equipment equipment = jsonifier.fromAgentJson(jsonFilePath, Equipment.class, targetPopulation);

However, the semantics of these agents to communicate and get processes working to have these agents act as interconnected units, like in manufacturing, is missing. In my understanding, this gap could be filled with DTDL for instantiation.
From what I read, the format JSON-LD is designed around the concept of a "context" to provide additional mappings from JSON to an RDF model. The context links object properties in a JSON document to concepts in an ontology. And this property is being used in DTDL v3 and can bring together semantics and parameters in a nice way.
When first encountering this property, I immediately thought of using this concept for simulation. I wanted to explore the possibility of using JSON-LD to not only "parse" properties but also semantic information like relationships and connections.
In my thought process, directly parsing DTDL could open up the possibility of a simpler base model with the necessary semantic information being implementable/instantiable from the "keywords" (lines with a @).
{
  "@id": "dtmi:com:example:ManufacturingMachine;3",
  "@type": "Interface",
  "@context": "dtmi:dtdl:context;3",
  "displayName": "Manufacturing Machine",
  "contents": [
    {
      "@type": "Property",
      "name": "machineId",
      "schema": "string",
      "writable": false
    },
    {
      "@type": "Property",
      "name": "machineType",
      "schema": "string",
      "writable": false
    },
    {
      "@type": "Property",
      "name": "status",
      "schema": {
        "@type": "Enum",
        "valueSchema": "string",
        "enumValues": [
          {
            "name": "Idle",
            "enumValue": "idle"
          },
          {
            "name": "Running",
            "enumValue": "running"
          },
          {
            "name": "Maintenance",
            "enumValue": "maintenance"
          }
        ]
      },
      "writable": true
    },
    {
      "@type": "Telemetry",
      "name": "temperature",
      "schema": "double"
    },
    {
      "@type": "Telemetry",
      "name": "vibration",
      "schema": "double"
    },
    {
      "@type": "Property",
      "name": "productionRate",
      "schema": "integer",
      "unit": "units/hour",
      "writable": false
    },
    {
      "@type": "Relationship",
      "name": "hasOutputProducts",
      "target": "dtmi:com:example:Product;1"
    },
    {
      "@type": "Command",
      "name": "startProduction",
      "request": {
        "name": "productionSettings",
        "schema": {
          "@type": "Object",
          "fields": [
            {
              "name": "productType",
              "schema": "string"
            },
            {
              "name": "quantity",
              "schema": "integer"
            }
          ]
        }
      }
    }
  ]
}

non-writeable "Property" would be parameters
writable "Property" would be variables
"Property" of type ENUM would be a state chart
"Telemetry" would be an output
"Relationship" would be a connection to another agent
"Command" would be an event or function
So, if my example could work like envisioned, you would model four agent types (Storage, Converter, Consumer, and Recoverer) with all the necessary bells and whistles for any units they are designed to instantiate. DTDL would do the specific setup for each agent.
Relatively "simple" model + DTDL => "digital twins" in model + JSON => initial condition for simulating "digital twins".
Your DTDL v2 files are quite close to what I tried to show with my DTDL v3, the key differences between DTDL v2 and DTDL v3
Fun fact, this also extends to the Web of Things (WoT) Thing Description , which is currently being merged with DTDL v3 to a universal standard for digital twins. A nice comparison between the two can be found here.
Sorry that it took so many interactions to convey this concept and idea, but I hope that I haven't missed something, and I'm curious what your thoughts are.

This is my model for monitoring energy consumption, which is in an early stage and needs improvement.

As you point out, this part of the concept is there and I've completely understood the significance of what you're doing here.

However, the semantics of these agents to communicate and get processes working to have these agents act as interconnected units, like in manufacturing, is missing. In my understanding, this gap could be filled with DTDL for instantiation.

This is where it becomes ambiguous again. What you're describing here would require users to already have the such logic/framework set up in their model. The DTDL you provide shows the definition, but not an implementation; to be able to pass the definition would require such a library to modify the actual AnyLogic model.
If it's believed I missing something, I'd be open to hearing what you think the actual logic of the library would look like (as in, pseudo code) - because providing that would really sync our understandings. Unfortunately my time at AnyLogic has come to an end. I'll be forking the repo after transferring it if you want to continue there and if I have personal time, I may look into exploring this further :) Otherwise, thanks for the great educational experience!


Disallow dollar char can be a useful switch for XM Cloud project and …

…other Docker projects where random string with $ throws up.ps1 error

For reference/background:
https://navansitecorenotes.blogspot.com/2023/02/adding-disallowdollar-as-switch-to-get.html
https://navansitecorenotes.blogspot.com/2023/01/pull-request-for-invalid-template-error.html

This is done, thanks

Is 10.2.8 expected soon? Just asking to include this feature in XM-Cloud and any other repos... thanks


Higher Precision Gradients from NWChem

Description
NWChem only prints gradients to an accuracy of 6 decimal places to stdout. I explored getting more accurate gradients from NWChem as a hope for allowing NWChem to work better with geoMETRIC. Reading gradients with higher accuracies did not seem to be the (only) issue with NWChem+geometric, but here is the result of that line of testing!
The full-accuracy versions of gradients are stored in checkpoint file of NWChem. The new code accesses and prints them using a Python script that runs during the NWChem execution.
See discussion here:
http://www.nwchem-sw.org/index.php/Special:AWCforum/st/id2155
I also implemented Hessian support while I was at it
Changelog description
Improved gradient output and added Hessian support for NWChem
Status

[] Code base linted
[ ] Ready to go

fyi @vivacebelles

To add some more detail, I just realized that NWChem rotates the coordinate system of the molecule. Anyone have experience with rotating gradients and Hessians for other codes?

Yup, I do it for Cfour. There's alignment machinery in qcel. Form an AlignmentMill, then there's methods for grad and hess (https://github.com/MolSSI/QCElemental/blob/52c81715d0975a444d419f85e2e681323755f566/qcelemental/models/align.py#L109-L141). Inputs are the internal geom and desired geom orientations, https://github.com/MolSSI/QCEngine/blob/master/qcengine/programs/cfour/harvester.py#L649-L653. Let me know if anything isn't clear.

Thanks, @loriab ! Rotating the gradients did the trick for getting NWC and geoMETRIC to work together!

I'm feeling paranoid, and am going to add in a test of a non-zero off-diagonal element


rust-analyzer-unwrapped: 2023-01-23 -> 2023-01-30

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for rust-analyzer-unwrapped is: A modular compiler frontend for the Rust language
meta.homepage for rust-analyzer-unwrapped is: https://rust-analyzer.github.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2023-01-30 with grep in /nix/store/qa1drshcg8sp92q8sd2vng86n2q2cb88-rust-analyzer-unwrapped-2023-01-30
found 2023-01-30 in filename of file in /nix/store/qa1drshcg8sp92q8sd2vng86n2q2cb88-rust-analyzer-unwrapped-2023-01-30

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
rust-analyzer
rust-analyzer-unwrapped
vscode-extensions.matklad.rust-analyzer
vscode-extensions.rust-lang.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qa1drshcg8sp92q8sd2vng86n2q2cb88-rust-analyzer-unwrapped-2023-01-30 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rust-analyzer-unwrapped https://github.com/r-ryantm/nixpkgs/archive/eedda7e8d87639c6ba65d0c177bbc5266a5fc790.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qa1drshcg8sp92q8sd2vng86n2q2cb88-rust-analyzer-unwrapped-2023-01-30
ls -la /nix/store/qa1drshcg8sp92q8sd2vng86n2q2cb88-rust-analyzer-unwrapped-2023-01-30/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

rust-analyzer
rust-analyzer-unwrapped
vscode-extensions.matklad.rust-analyzer

Maintainer pings
cc @oxalica for testing.

@ofborg build vscode-extensions.matklad.rust-analyzer


mitigate cve-2021-26701

https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-26701
just bumping version for system.text.encodings.web to mitigate the above cve.

@jjoekoullas Thanks for opening this. I just encountered the same issue. Do you know if there's a way to fix this locally, while we wait for this PR to be merged?

I ran into with nswag.msbuild.  Not really a good way around it for that - except maybe using a private nuget repo and publishing to it using this branch.
If it's just because you're referencing nswag in your project - just referencing an updated System.Text.Encodings.Web will get you past this.  That's actually what this fix is doing, just referencing an updating version since the problematic reference is in a dependency.

@jjoekoullas Unfortunately I also ran into this with nswag.msbuild :(
I may try the private nuget repo approach


Fixing hotkey drops in Linux

This PR addresses issue #302 .
hotkey_system.rs was rewritten so that the activation and deactivation of the hotkey system registers and unregisters the grabbing of the keys. Moreover, I added an (private) enum Hotkey that makes it possible to reduce the large amount of copy&paste code.
In the livesplit-hotkey crate, the linux module was slightly modified: the old functions register and unregister were replaced by
grab_all and ungrab_all. Also the window number is now calculated in grab_all and ungrab_all, which simplifies the Hook methods slightly.
I think that we should get rid of the set_split(keycode), set_skip, etc methods and instead make enum Hotkey public and use set_hotkey(hotkey,keycode) instead.

I've tested this patch on my machine like I should have done ages ago, and it seems to be working.
@CryZe this should be good to merge provided there's nothing else wrong with this.


How to provide string type for variable in Sway contract?

Motivation
Hi! I'm trying to implement the token standard and use strings from sway-libs in it, but I ran into a problem I don't understand how to pass the string from rust-sdk side.
I have found this code on your github, can you please tell me if you have code example that calls this function from rust-sdk?
I want to initial string values as variable

Also I tried to do it with a byte array, but I get this error:
thread 'main_test' panicked at 'called Result::unwrap() on an Err value: InvalidData("Type Struct { fields: [Bytes], generics: [] } contains nested heap types (Vec or Bytes), this is not supported.")', tests/harness.rs:20:59

This currently is not supported by the SDK. The issue can be tracked here and here

Closing as this has been resolved by https://github.com/FuelLabs/fuels-rs/pull/1042


Resolve implied URL to an absolute URL

Just like an implied photo is resolved to an absolute URL an implied URL should be resolved to one, so I copied the solution from photos and applied it to the implied URL:s as well.
Also double checked at http://microformats.org/wiki/microformats2-parsing#parsing_for_implied_properties that this is how it should be parsed.
Also have to say: Thanks for a great Node.js library! Likely wouldn't have done at all as much IndieWeb stuff without it lowering the barrier.

I am glad you found it it useful.
Thanks for this PR, not sure how I missed out adding the resolving of URLs in href.


[BUG] after the reboot, everything does not load

Describe the bug
I have to reinstall the launcher to make the profile work, in the trend for games, "surprise me" and displaying caps and other properties of games, is there any way to fix this? or is it a bug that will be removed with the update?
Steps to Reproduce
install - close - run - bug
Expected behavior
the solution to the problem
Screenshots

Operating System
Windows 10
Hydra Version
2.0.3
Additional Information
No response

Same problem

Same problem

Is there really no solution?

More information is needed to identify the problem. Describe which system you are using, characteristics, hydra log files, and so on.

@Rxflex, Windows 10, intel core i5-12400F, AMD RX 6600, 32 RAM
error.old.txt
error.txt
info.txt

@2pk1Mitrofanov Looks like steam refusing your requests, try to use vpn, its might help

It seems that some firewalls blocks Hydra HTTP requests. Check if you have Kaspersky or other firewalls.

Closing issue as no response in a long time


Infer false positive on array access

When accessing last element in an array, infer reports false positive 'ARRAY_OUT_OF_BOUNDS'.
$infer --version
Infer version v0.13.0-d850492
Copyright 2009 - present Facebook. All Rights Reserved.

$cat >test.c <<EOF
void test(void)
{
    char a[16];
    int b[16];

    a[sizeof(a)-1]=0;
    a[16/1-1] = 0;
    a[sizeof(a)/sizeof(*a)-1]=0;
    b[sizeof(b)/sizeof(*b)-1]=0;
}
EOF
$infer --no-filtering -- cc -c test.c
Capturing in make/cc mode...
Found 1 source file to analyze in /tmp/infer-out
Starting analysis...

legend:
  "F" analyzing a file
  "." analyzing a procedure

F.

Found 2 issues

test.c:9: warning: ARRAY_OUT_OF_BOUNDS_L2
  array `b` `of size 16` could be accessed with an index out of bounds at line 9, column 5.
  7.       a[16/1-1] = 0;
  8.       a[sizeof(a)/sizeof(*a)-1]=0;
  9. >     b[sizeof(b)/sizeof(*b)-1]=0;
  10.   }

test.c:8: warning: ARRAY_OUT_OF_BOUNDS_L2
  array `a` `of size 16` could be accessed with an index out of bounds at line 8, column 5.
  6.       a[sizeof(a)-1]=0;
  7.       a[16/1-1] = 0;
  8. >     a[sizeof(a)/sizeof(*a)-1]=0;
  9.       b[sizeof(b)/sizeof(*b)-1]=0;
  10.   }

Summary of the reports

  ARRAY_OUT_OF_BOUNDS_L2: 2

P.S. This is a followup on #706.

I can not reproduce this issue using infer v0.14.0-0bbdf63, suggest closing.

We fixed several things on sizeof that may be related to this issue indeed. Thanks!


fix(wash-lib): restore rust examples folder

Feature or Problem

Previous reshuffling of the examples directory has broken wash new, and while the newer (unreleased) code in wash-lib has the right paths, the currently released version of wash (and wash-lib, in particular 0.18.1) is broken.
This commit adds a soft link to fix the problem temporarily before a new version is out.
Resolves https://github.com/wasmCloud/wasmCloud/issues/1721
Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

@thomastaylor312 Ah a bit late but that comment in stale, will update it -- softlinks don't work with the way wash sets up the template, had to actually copy the real files


[2012-12-04] HtmlEditorField initializes multiple times

created by: mweimann
created at: 2012-12-04
original ticket: http://open.silverstripe.org/ticket/8069

The HtmlEditorField initializes multiple times.
Due to Ajax loading HtmlEditorFields HtmlEditorField::include_js(); is called in the page controller's init(). The HtmlEditorField.js is loaded at the page's template. Now tinyMCE gets initialized twice because window.onload contains
window.parent.tinyMCE.get('Form_doEdit_Text').onLoad.dispatch();

twice.
My guess is that tinyMCE initializes first by the tinyMCE scripts and then HtmlEditorField.js initializes tinyMCE a second time. This modification of the HtmlEditorField.js fix the issue for me:
if (window.tinyMCE == undefined) {
   tinyMCE.init(config);
}

I’m going to go out on a limb and say that this has been resolved by the TinyMCE 4 upgrade


[x] RegExp and [x] Change Case mess up, except if: [x] Replace once

Much like in previous versions or Rename-It, RegExp will usually (=with most regexp) not work as intended or at all, unless "Replace once" is checked as well.
I've seen this with several different types of Regular Expressions, this is just one example:
I was trying to simulate the "Word Case" replacement (because that one's broken too, see issue: #41 ) by means of RegExp.
Specifically, I was matching lower-case letters preceded by a space character:
" ([a-z])"
..and trying to replace them with
" \1"
..while having enabled the option: Change Case: UPPERCASE
As it turns out, this only works if the option "Replace Once" is also enabled.
See screenshot for clarification, upper is with "Replace Once" enabled, lower without. Observe the preview field:
http://i.imgur.com/35WLgNr.jpg

Note that this is NOT just a faulty preview, I have tried to actually run the rename like in the lower screenshot, and it fails with: ...problems have been detected.. invalid file name...contains forbidden characters...

I'm using v4 Alpha with the (highly appreciated) x64 context menu patch by Mr Pischedda

Nice bug report. It looks like the REGEX engine is built for ascii and giving ascii characters instead of unicode ones. The code is a big hack in the end so it might be from there. It's at https://github.com/wernight/renameit/blob/master/apps/Rename-It!/src/IO/Renaming/Filter/SearchReplaceFilter.cpp#L139 and using CString.MakeLower or MakeUpper.


Is there a way to disable some of the settings pages?

I tried simply blocking the pages already but that doesn't work I guess authenticate referes to some block I cannot include such requests in. I can probably disable it with a custom theme in the frontend but Im still searching for the locatino of those theme files inside the container. And I want to disable those functions in the backend too.
http://auth.xxxxxx.xx {
  respond /settings/sshkeys "Not accessible" 403
  respond /settings/gpgkeys "Not accessible" 403
  respond /settings/apikeys "Not accessible" 403
  respond /settings/connected "Not accessible" 403

  authenticate with myportal
})

@Loqova , I am actually working on the redesign of the settings page. May incorporate new features. What is the intent behind disabling the pages? Why did you choose to disable these particular pages?

I didn't disable it but wanted to. What I tried didn't work. For the sake of customizability. I have several use cases where I would only want to use this for simple auth + mfa without the ssh/gpg/api/connected features.

I didn't disable it but wanted to. What I tried didn't work. For the sake of customizability. I have several use cases where I would only want to use this for simple auth + mfa without the ssh/gpg/api/connected features.

@Loqova , makes sense. Will think how to enable/disable features.

I will be adding the following directive to Caddyfile:
disable settings [gpgkeys|sshkeys|apikeys|connected|mfa|password|general]

By default all sections of the "Settings" page are enabled. If disabled, then the section will not be visible in the UI.

@Loqova , it will be disabled everywhere.


Support for Gulp 4?

Hello, I have using your plugin for a couple of years and enjoying the benefits. However, I recently upgraded my Gulp version to 4, and the plugin doesn't seem to work any more. I was curious if there's an upgrade in the works to work with the new version.

Hi @lostPixels, thank you for using this plugin.
Actually I'm not using gulp anymore, and there is no plan to update this plugin to work with Gulp 4.
PR are al welcome.
But I think the effort to get the plugin works with 4 version should be low.
Let me to do a quick check.
Best

Hi @lostPixels,
On this branch 2.0.0 I upgraded to Gulp 4 and created a little working example.
Everything seem to works as expected.
Please give it a try and let me know.
best

Works great!


Only show link to contrib page from Community

Contributes to

#895
#770

Delists the Contribution page from the sidenav as part of the sidenav cleanup (pre-IA rework)
The Contribution page remains accessible, as it was before, from the community page

Previews:

https://deploy-preview-894--opentelemetry.netlify.app/docs/
https://deploy-preview-894--opentelemetry.netlify.app/docs/contribution-guidelines/

Note that the Contribution page itself needs rework, but that will be handled separately.

Merging based on @austinlparker's 👍 in https://github.com/open-telemetry/opentelemetry.io/issues/895#issuecomment-965805417


154 as an inpector i want to store all registration numbers

ref #154

Please, let's pause this until we hear from the client.

It is finished


Failed to connect account using Github

I am trying to sign up using my GitHub account and when I click "Link your GitHub account" I receive this error
Failed to connect account
Steps to reproduce:
Click Sign Up
Click JavaScript
Complete task
Click Link Your Github Account
Failed to connect account
I tried to find a solution using different browsers (Chrome, Firefox, and Safari) and I also went to GitHub settings and I revoked codewars as Authorized OAuth Apps a few times and I tried the steps above again and No luck.
Could someone @ codewars reset my account (my GitHub @giovannixdev) "maybe something got stuck half the way during the creation of my new account" using my GitHub username?

Did you sign up in July? https://www.codewars.com/users/giovannixdev
Can you try signing in instead of signing up?

Hi @kazk, I can't signing in either. I get this message
GitHub account is not linked to an existing Codewars user.
Could you reset my account to start from scratch?

I don't have the time to look into the data issue right now, but you should be able to send an email to reset password and log in using that. Can you try that first and let me know?
Once you're logged in, you should be able to reset GitHub account in settings.
If this doesn't work, I'll try looking into it later.

I sent 2 email's already to<EMAIL_ADDRESS>with all the information and screenshots and I have been waiting for a response for weeks.
I don't need to reset the password. My issue is that I can't signing in using my GitHub account. At this point please delete my account when you are available so I can create a new account using my Github account. Thanks!

I'm sorry no one responded, but I have no access to that email. Issues are tracked here.

I don't need to reset the password. My issue is that I can't signing in using my GitHub account.

I asked you to try it because you should be able to re-link GitHub account yourself after logging in with the password reset email. From there, you should be able to log in using GitHub account.
If you decide to try it, post a comment here with the results. Otherwise, I'll delete your account and close this issue later when I can.

Hi, @kazk I have tried that too and no luck. Yes please delete my account when you are available so I can create a new one with my github account. Thank you very much!

Deleted the account


crash on physical device

Hello,
The app crash on my iPhone.
I use a modal view with TextView.
But working fine on simulator.
regards,
Chris

Can you show me the crash log? I've tested it on physical devices and it didn't crash. Also, can I see your code?

(lldb)
Thread 1: EXC_BREAKPOINT (code=1, subcode=0x1d3a70f7c)
`struct AddNoteToCourse: View {
var course:Courses

var dbmanager = DBManager()

@State var title = ""
@State var notebody = ""
@State var isEditing = true

var body: some View {
    VStack {
        Rectangle()
            .foregroundColor(Color("PersoGray"))
            .frame(width: 30, height: 4, alignment: .center)
            .padding()
        HStack {
            Spacer()
            Button(action: {
                self.dbmanager.addNoteToCourse(Course: self.course, Title: self.title, Body: self.notebody)
            }) {
                Text("Add note to the course")
                    .foregroundColor(Color.white)
                .padding()
            }
            .padding(.trailing)
            .background(Color.blue)
        .cornerRadius(10)
        }
        TextField("Title", text: $title)
            .background(Color("PersoGray"))
            .padding()
        TextView(text: $notebody, isEditing: $isEditing)
        TextField("Title", text: $title)
            .background(Color("PersoGray"))
            .padding()
        Button(action: {
            self.dbmanager.addNoteToCourse(Course: self.course, Title: self.title, Body: self.notebody)
        }) {
            Text("Add note to the course")
        }
        Spacer()
    }
}

}`

I'm getting this same error when I try to display the TextView in a sheet. Unfortunately, this isn't a bug on my end but instead it's a bug in SwiftUI. I hope this gets fixed soon, and I also hope you can find a workaround for now. Sorry about this!


How to add custom ros message to visualize

Hi , I'm trying to visualize 3D world mapping with data that comes from my custom ros messages. I tried to trace the code; it seems I need to modify https://github.com/cruise-automation/webviz/blob/master/packages/webviz-core/src/types/Messages.js and https://github.com/cruise-automation/webviz/tree/master/packages/webviz-core/src/panels/ThreeDimensionalViz . Is there any guide for how to add ros messages or any body to help?
Regards.

I would recommend having a ROS node that converts your messages into one of the standard ROS message formats, which are the same as the message formats supported by rviz: https://github.com/cruise-automation/webviz/blob/6623f080b2bee11144df1bb70c2ac93db51a37fa/packages/webviz-core/src/panels/ThreeDimensionalViz/SceneBuilder/index.js#L450


Migrate to TypeORM

Currently the orm implementation is a abstraction of Sequelize, however this comes with some issues as their model system is not conducive to repository pattern and is not typescript designes so there is some weirdness there.
There is a new ORM in progress called TypeORM which offers nearly every feature required, and in typescript. This will greatly improve velocity to beta.
Currently they only support MySQL, so while we would prefer to use Postgres for the native uuid and schema support it's probably better to just go with MySQL(MariaDB) for the time being while the adapter is still being written.
Considerations

@Table & @Column decorators will need to be either renamed or moved to the DatabaseStore as they don't make sense on the common isomorphic model (doesn't make sense for the frontend to be registering column/table attributes when it doesn't care). As decorators are just functions, it's probably easy to just rename/move them with new decorators
No UUID type in mysql - this can be handled (temporarily) with just a varchar column. not idea, but ok for beta
No schemas - this feature of Postgres was going to be used to separate modules out for easy migrate/destroy. This can be emulated with table name prefixes for MySQL? Drop tables like

rename @Table & @Column
As I understood you want to abstract frontend model from database implementation. But there is no frontend model. There is also no a backend model. There is a single model that is and frontend and backend model (correct me if I got you wrong). And since its same model it most probably will share its origin between each other.
Also how do you plan to rename it? Don't think its a good idea for two reasons: first because users will confuse when read orm documentation where there will we different decorators and second - no metter how you rename it - you can't hide that its a database decorators - relations, decorator options will expose what it is anyway.
Btw just to mention that you can also store schema in separate files. But of course its not as convenient as with decorators.
No UUID type in mysql - this can be handled (temporarily) with just a varchar column. not idea, but ok for beta
I think in the future orm can implement id generation strategies. These strategies can include uuid, auto increment and other strategies generation by orm.

Hey @pleerock yep you've understood the architecture correctly - models are common to frontend and backend (same source).
I agree with the concern about renaming decorators, however I'm thinking that it may be a bit more than renaming. Due to how the ModelStore pattern works, the storage engine implementation could be anything from relational db, to nosql, to redis to localstorage, remote api etc etc. The implementation is also platform independent. For that reason the model should be defining more abstract properties like @StoredProperty in place of column. (For the database store that would be the @Column decorator).
It's true that no matter what I name it, there will be some bias towards the datatypes looking like database columns, but in general, between database, redis, nosql, localstorage and json, the greatest granularity is required for relational databases, and so every "column" type can be mapped to those datatypes.
On UUID's, I don't actually really care about uuid generation - in a distributed infrastructure it's better to have the client generate the uuid than the server. It's also really useful for handling queueing systems as the client can already have the id reference to an object that will (probably) be stored at some point.
Thanks for the input 😄

Hey @pleerock yep you've understood the architecture correctly - models are common to frontend and backend (same source).
I agree with the concern about renaming decorators, however I'm thinking that it may be a bit more than renaming. Due to how the ModelStore pattern works, the storage engine implementation could be anything from relational db, to nosql, to redis to localstorage, remote api etc etc. The implementation is also platform independent. For that reason the model should be defining more abstract properties like @StoredProperty in place of column. (For the database store that would be the @Column decorator).
It's true that no matter what I name it, there will be some bias towards the datatypes looking like database columns, but in general, between database, redis, nosql, localstorage and json, the greatest granularity is required for relational databases, and so every "column" type can be mapped to those datatypes.
On UUID's, I don't actually really care about uuid generation - in a distributed infrastructure it's better to have the client generate the uuid than the server. It's also really useful for handling queueing systems as the client can already have the id reference to an object that will (probably) be stored at some point.
Thanks for the input 😄


feat: change createRef to useRef

Types

[x] 💄 Code Style Changes

Background or solution

🤖 Generated by Copilot at b4caffc

Replaced createRef with useRef in several components to avoid creating new refs on every render and to be consistent with the React hooks style (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
Removed unused createRef imports from RecycleTree.tsx, extension-tree-view.tsx, markers-tree.view.tsx, outline.tsx, and search.view.tsx (link, link, link, link, link)
Added useRef imports to opened-editor.tsx and output.view.tsx where it was used (link, link)

close #2899
Changelog

🤖 Generated by Copilot at b4caffc
This pull request refactors various components in the opensumi/core repository to use the useRef hook instead of the createRef function for creating and accessing refs. This improves performance, readability, and consistency of the code. The pull request also removes some unused imports and adds a missing one.

@winjo 冲突处理一下


Add duration formatter for numeric data

CATEGORY
Choose one

[ ] Bug Fix
[x] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
This PR adds a number formatter based on pretty-ms for formatting time durations that was added to superset-ui in version 0.12.1(https://github.com/apache-superset/superset-ui/pull/209). The following formatters are available:

DURATION: 66000 => 1m 6s, 66111 => 1m 6.1s (rounded to 1 decimal point)
DURATION_SUB: 66100.40008 => 1m 6s 100ms 400µs 80ns, 100.40008 => 100ms 400µs 80ns

SCREENSHOT

TEST PLAN
Tested locally
REVIEWERS
@etr2460 @kristw @mistercrunch

Removed second and minute formatters, as putting a constant multiplier to convert from min/sec to ms in a metric is trivial. Also added separate option for showing sub-second durations.

Codecov Report

Merging #8136 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8136   +/-   ##
=======================================
  Coverage   65.96%   65.96%
=======================================
  Files         486      486
  Lines       23030    23030
  Branches     2541     2541
=======================================
  Hits        15192    15192
  Misses       7704     7704
  Partials      134      134

Impacted Files
Coverage Δ

superset/assets/src/setup/setupFormatters.js
0% <ø> (ø)
:arrow_up:

superset/assets/src/explore/controls.jsx
42.85% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


If you count, you get 245 flags.

Expected
We must have the same exact number of flags in the flags.png sprite, which is used for the component (https://github.com/Semantic-Org/Semantic-UI/blob/master/dist/themes/default/assets/images/flags.png)
Result
Instead, we got 2 more. One of these are the Catalan (Catalonia), which you can see appearing under the Canadian flag (1st col, 36th row). I can't spot the last one.

You can get Catalan flag by adding
i.flag.es.ca:before, i.flag.catalonia:before {     background-position: 0 -936px }

It's what I already did but you get this output anyway:

I think they should improve it :/

Here you have an example: https://jsfiddle.net/31d6y7mn

Yeah of course, the Flag component, internally uses the "i" html tag, which uses those classes, but if you change one of those flags with the names you say "es ca" or "catalonia", doesn't work. You can try it in there:
https://codesandbox.io/s/4t34j?module=/example.js&file=/example.js:160-166

https://codesandbox.io/s/semantic-ui-example-g5wwo
I imported App.css on index.js, and added a flag with the other one.

I did a PR in Fomantic-UI, the active fork of Semnatic-UI
https://github.com/fomantic/Fomantic-UI/pull/1549

Yeah thanks, I hope they fix it soon because as you can see in the codesandbox link you provided before, console output show us the warning.

Yes, the problem is with types of React-Semantic, now with Fomatic-UI v3 (https://github.com/fomantic/Fomantic-UI/blob/master/ROADMAP.md) will have React types also!

Yeah thanks, I hope they fix it soon because as you can see in the codesandbox link you provided before, console output show us the warning.

We most probably won't merge the above mentioned PR. (Technical reasons described at https://github.com/fomantic/Fomantic-UI/pull/1549#issuecomment-652402724)
But even, if we would , as you are referring to an error in SUI-React, it would have to be patched there, otherwise you will still encounter the error message you are referring to.
If you want this fixed, you have to raise an issue at https://github.com/Semantic-Org/Semantic-UI-React

Thank you, I've posted it in there.


Cannot execute the 0.7.0 binary on linux_arm64

Just downloaded restic_0.7.0_linux_arm64.bz2 from the releases section; bunzip worked fine but executing the binary does not:
bash: ./restic_0.7.0_linux_arm64: Kann die Binärdatei nicht ausführen: Fehler im Format der Programmdatei
Downloading with wget instead of browser makes no difference.
Followed the exact same steps with the restic_0.6.1_linux_amd64.bz2 release and everything just works.

Uhm, are you sure you have the right binary? It looks like you're trying to execute an arm64 binary on amd64, is that what you want?

I don't have a Linux/arm64 ready, but the extracted binaries look fine to me:
$ file restic*

restic_0.6.1_linux_amd64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
restic_0.6.1_linux_arm64: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, stripped
restic_0.7.0_linux_amd64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
restic_0.7.0_linux_arm64: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, stripped

Arrrghhh. Yes. Sorry...

Don't worry, I'm glad we could find the issue so quickly.


[LinearProgress] Add determinate and indeterminate classes to root element

[x] I have followed (at least) the PR section of the contributing guide.

Fixes #13713
Solution

Add indeterminate class to the root element
Add determinate class to the root element

@alxsnchez It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!

@alxsnchez There is a lot to be done, your help is welcomed :)


pipeArgs needs more details

Too much time have I wasted on trying to figure out what pipeArgs is and what are the meanings of its parameters. This document doesn't provide any useful information.
What is the debugInfo.remoteMachineId in pipeArgs? Is it the same as the top level one? I tried to put the same value in it but it doesn't work at all.

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

ID: 1a7a4e8b-d422-93b1-e042-55c2acbf8ef3
Version Independent ID: 0d55f5d8-846e-3282-b580-9b7770053958
Content: Configure CMake debugging sessions in Visual Studio
Content Source: docs/build/configure-cmake-debugging-sessions.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@esweet fyi, is this something you can clarify?

I think you tagged the wrong person?
On Thu, Mar 12, 2020, 19:59 Colin Robertson<EMAIL_ADDRESS>wrote:

@esweet https://github.com/esweet fyi, is this something you can
clarify?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/cpp-docs/issues/1973#issuecomment-598496819,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFUGOXEAPUDBVVMQRORMKDRHGAOVANCNFSM4LGAVXAQ
.

@esweet Yes, my apologies. The reference was intended for @esweet431 but I hit Tab too quickly.

Sorry for the confusion. You don't need to manipulate debugInfo.remoteMachineName in pipeArgs - or any other parameters of the pipeArgs object - in order to debug. remoteMachineName (at the root level) is what you should be using to set the remote system you are deploying to and debugging on. pipeArgs can be used to export the DISPLAY variable or run a script/command before the execution of gdb, but those are both entirely optional.

Thank you for your patience as we work through our backlog. We have received more issues than we can manage at this time. We are closing issues based on their severity, how broadly applicable they are, and whether there is enough information provided to act on the issue. If you believe that this issue should not have been closed, please add a comment explaining why by 3/8/2024. We appreciate your contribution and encourage you to propose changes using public PRs, or submit feedback through our updated control at the top of the page, as we phase out Git Issues for this repo. For more information on our feedback systems, see https://aka.ms/ContentUserFeedback.


Message with gramatical error

[akka://MarvinExecutorSystem/user/pipelineActor] All artifacts from [evaluator] where saved with successful!! [ListBuffer(Done)]

hey guys @jpfaria @lucasbm88 , i think this error belongs to marvin-engine-executor repository

Fixed in last version of engine-executor!


Cache length.

^

I like using Array#forEach for this kinda thing. Makes for some seriously clean code.
x.forEach(function(i) {
  sum += i;
});

Or get rid of sum all together by reducing the array:
return x.reduce(function(prev, curr) {
  return prev + curr;
});

@ryanseys I would have voted for reduce but it's slower, could have linked to a jspref but it's down.

V8 caches the length for you, so this is moot. While I usually use forEach, it's intentionally using a for-loop to be as fast as possible. forEach and similar methods aren't very optimized in V8 yet and comes with the overhead of calling a function for each iteration.

:+1:


delete java vtocc

Java vtocc currently is not being used and tied to bson rpc.
Please use VTGate based java client instead.

LGTM good cleanup.


Provide a command for step 7 - Import the public key of the private_key_jwt issuer.

Provide a command for step 7 - Import the public key of the private_key_jwt issuer in this doc [1]. Which cert to import in to which?
[1] https://docs.wso2.com/display/IS550/Private+Key+JWT+Client+Authentication+for+OIDC

This issue is valid for IS5.5.0/Alpha3 as well need to fix this under step 10 in the current doc [1]
[1]. https://docs.wso2.com/display/IS550/Private+Key+JWT+Client+Authentication+for+OIDC

Updated the doc [1] with the command to import public key of the private_key_jwt issuer
[1] https://docs.wso2.com/display/IS550/Private+Key+JWT+Client+Authentication+for+OIDC


Create Maharot file

Tnx to all

closing, as this appears to be empty. If this is needed, please feel free to re-open 🙇


The id attribute is removed from source markup

Describe the issue

### Introduction

We provide an API that allows you to automate the process and integrate your software with our service.
...

Will produce html without id attr for section:
...

Procedure version
<EMAIL_ADDRESS>Reproduction link
No response

Reference: https://imzbf.github.io/md-editor-rt/en-US/demo#🔒 Compile-time Prevention of XSS


Errors parsing escaped chars

My toml file content:
[tool.pylint.MASTER]
ignore-paths = [
    # don't allow file path with "/."
    "^.*\/\..*$",
    "^.*node_modules.*$",
    "^.*build.*$",
    "^.*dist.*$",
]

It leads to following errors when I run pylint:
Failed to load 'pyproject.toml': Reserved escape sequence used (line 69 column 1 char 1303)
Failed to load 'pyproject.toml': Reserved escape sequence used (line 69 column 1 char 1303)

I clearly see the issue in toml online parser:

But fixing it with \\ leads to a wrong regexp:

What could I do?

Looks like I could use triple quotes


moved AwsS3DiscoveryProcessor to where it should live

Yeah ... I was tempted. You think that would be ok here?

Yeah I think so, stability index 1 and it's a fairly low impact and simple move

Alright, updated!


DNN-8513: Create a new extension point in the DNN core at the Database Connection Level.

Refer to this PR #1401 for details.
Jira DNN-8513

I would like the ability to break away from using the standard SqlConnection, and switch to using ReliableSqlConnection for Azure sites. I would also like the ability to set up retry policies when performing database operations.
I have/will be including a code fix that adds a new extension point at the database connection layer. We can then use a custom database connection that will allow us to use ReliableSqlConnection and the RetryManager functionality that Azure provides, without having to bring those things into the DNN Core.
I have created an AzureSqlConnection Provider to test this functionality, which can be found here: https://github.com/JoshuaBradley/DnnAzureSqlConnectionProvider.

@mitchelsellers these obsoleted public methods are already removed in 9.2.0 since they were deprecated pre v7.0. Therefore, this addition won't have a breaking change from 9.2 to 10.0.
As for fixing the conflict, someone has to take care of that as I'm no longer affiliated with DNN Corp.

@mitchelsellers, I've rebased this onto development, and moved the config change from 9.2.0 to 9.3.0 (I didn't see anywhere that referenced the 9.2.0 config file, does that get run automatically based on version number?).  I also reverted the DataProvider.cs changes which were unnecessary.

The config files are copied at compile time from Dnn.Platform\DNN Platform\Website\Install\Config folder to Dnn.Platform\Website\Install\Config

@dnnsoftware/tag Input on this?


[ci] Run tests on Ubuntu

The test-linux job in GitHub Actions actually ran on macOS-latest, so I changed it to use ubuntu-latest and the official Swift docker container. I added a matrix so in the future multiple versions of Swift could be tested using the same job. As far as I remember, Swift on Ubuntu requires to specify --enable-test-discovery for both build and test, so I added it to the build step as well.

To speed up the CI on both macOS and Linux, I'd suggest to add caching as well: https://github.com/actions/cache/blob/main/examples.md#swift---swift-package-manager

To speed up the CI on both macOS and Linux, I'd suggest to add caching as well: https://github.com/actions/cache/blob/main/examples.md#swift---swift-package-manager

Whoops. Good catch, thanks for the contribution! Failing on building PapyrusAlamofire which is iOS only.
Was experimenting keeping all the libraries in a single repo for sanity sake, but that should probably be in a separate repo since it causes tests to fail, gonna rip that out and then merge this in.

Whoops. Good catch, thanks for the contribution! Failing on building PapyrusAlamofire which is iOS only.
Was experimenting keeping all the libraries in a single repo for sanity sake, but that should probably be in a separate repo since it causes tests to fail, gonna rip that out and then merge this in.

Wooo, (actual) Linux tests passing now! Thank you, @slashmo !

Wooo, (actual) Linux tests passing now! Thank you, @slashmo !


notif: Replace flutter_local_notification createNotificationChannel with pigeon

Work towards #351

Thanks for the review @chrisbobbe, pushed a new revision PTAL :)

Thanks for the review @gnprice, pushed a new revision.

Thanks for the review @gnprice, pushed a new revision, PTAL.

Oh and a different commit-message nit — the commit series looks like this:
1f641b7c7 notif: Add createNotificationChannel method to pigeon bindings
2af238ba4 notif: Add createNotificationChannel method to pigeon bindings
b35b73c28 notif [nfc]: Remove unused test harness for parts of flutter_local_notifications
So the first commit message is duplicated.
I think you intended the second commit to have the message it had in the last revision:
notif: Replace flutter_local_notification `createNotificationChannel` with pigeon

Updates #351

So I'll put that message back.
This is probably also a good moment for a reminder that I highly recommend setting up and using a graphical Git client, like gitk. Especially when doing a rebase, or operations like splitting up commits, a graphical client can be extremely helpful for getting a clear picture of what the old and new branch look like. I think if you'd used gitk or similar when self-reviewing your revision, you'd probably have immediately spotted that the commit message on the second commit had gotten clobbered.


Help

Hi,
Can someone help me with setup? I'm not experienced with this.
MAYBE I can pay for it.

Most likely nobody can help you, as most likely you don't have a method to load the driver to the kernel.


Updated .travis.yml to cache bundler and cocoapod files.

Closes #3570 (WIP DO NOT MERGE)

This pull request has been superseded by #3578


invalid module name in go.mod

What steps did you take:
go get github.com/vmware-tanzu/carvel-ytt@v0
What happened:
go get<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/k14s/ytt
                but was required as: github.com/vmware-tanzu/carvel-ytt

What did you expect:
Ability to get the module or install the binary with go install
Anything else you would like to add:
Requires to update module name in go.mod. Without this change, nobody will be able to use ytt as a go library or install it simply using go install standard command.
Environment:

ytt version (use ytt --version): N/A
OS (e.g. from /etc/os-release): Ubuntu 20.04 LTS + GO 1.17.6

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Carvel started out as a suite named "k14s" short for Kubernetes Tools.
Some time back, VMware formally sponsored this project and adopted it into its OSS program. The repository was moved at that time, but the module was not renamed.
We have been tracking this across the suite in vmware-tanzu/carvel#153, but haven't yet made it a priority.
Apologies for the inconvenience. Given that we're seeing more and more folks reach for a programmatic integration, I've prioritized doing this rename, soon: #585
In the meantime, feel free to rely on GitHub's redirection service:
go get github.com/k14s/ytt@v0

FWIW, we have some preliminary guidance around integrating with ytt in this way: https://github.com/vmware-tanzu/carvel-ytt/blob/develop/examples/integrating-with-ytt/apis.md

We'll be tracking the rename work in #585; closing this issue, for now. @cboitel, if you need more support here than this, please feel free to continue the conversation here.


Alpha filter merge with PX4 version

For the battery filter time abstraction in PX4 https://github.com/PX4/Firmware/pull/14551/ I implemented the same filter there and am now merging the two versions here.
It's the best of both sides I think except I couldn't do the NAN checks because matrix::Vectors do not support isfinite checks. So I have to take care with the PX4 callers that they never run NAN through the filter.
Sidenote: While working with the unit tests I missed the gtest colors so I added them with GTEST_COLOR=1 like in PX4.

It was quite a hassle to get make format use clang-format version 9.0.1. It would helpful if the CI output would directly show what's broken in the style or it's easier to adopt the style check locally.

Why exactly is that diff CI check failing?

Why exactly is that diff CI check failing?

This should fail if there is behavioral changes in the code. You need to re-run the test locally and commit the changes to the file it makes.

Yeah but I want to find out why/what changed in it. Do I just revert things and see where it changes?

Basically yes, it is a final safety check for PRs that should be non-functional changes.

My solution to not spend the day fiddling with docker because my compiler uses slightly different printf formating is to revert back to the internal definition of alpha_mathieu = 1 - alpha_matthias which results in no numerical differences. I used the other definition because almost all places where I could find the filter definition it was this way but in practise it doesn't matter if you know which way it is. And the time abstraction formula is the just dt / (dt + tau) instead of tau / (dt + tau) which leaves the setParameters inteface the same.
Any opinions? Anyone up for a review?

If you're planning to use this everywhere it probably makes sense to move it out of EKF to the top level of ecl.

If you're planning to use this everywhere it probably makes sense to move it out of EKF to the top level of ecl.

That makes sense. I wasn't sure about the structure of ecl. I think it's actually my first contribution.

maybe adding isfinite checks in Matrix would make things easier?

@jkflying That would allow having that nan checks in the templated filter. But I was thinking about the real case where you get nans and suddenly the filter would silently not update anymore making you think your data is still available and filtered working with a stale output. When I followed the history behind that nan check it seems it was just precautiously added for one case and then copy-pasted to all battery filters in a refactor.

Thanks @bresch !! 👍


dentate full surface workflow

The challenge here is generating inner/outer surfaces despite the DG being so thin.

also for the nativesurf workflow #327, need an approach to obtain midthickness surfaces without holes too..
I'm looking into different surface reconstruction algorithms, and it seems like the Ball-pivoting algorithm is a good choice (could work generally for both dentate and hipp).. it relies on us having some surface normal estimates, which we actually are able to get quite cleanly (from gradient of the IO coords), and the algorithm inherently deals with open surfaces, and we could control the smoothness by the ball radius.
original paper:
http://mesh.brown.edu/taubin/pdfs/bernardini-etal-tvcg99.pdf
some python implementations:
https://github.com/rodschulz/BPA
https://github.com/Lotemn102/Ball-Pivoting-Algorithm
the open3d implementation looks like the most useful one:
https://www.open3d.org/docs/latest/tutorial/Advanced/surface_reconstruction.html
(as an aside, this and some of the other surface generation techniques could be useful for computing the shrink-wrap surface that we could use to obtain a better gyrification measure @Nima )


In next: Label rotation and magnification not responding to arguments.

Dear L. Heitzmann,
I am unable to rotate my labels by changing the argument.
A snippet of the code I have:
resonator_label = gdspy.Label('Index: ' + str(resonator_frequencies.index(sorted_frequencies[i])) + ' frequency: ' + str(resonator_frequencies[i] / 1e9) + ' GHz', (bounding_box_x, bounding_box_y), 'o', rotation = 45, layer = labels_layer)
Let me know if it is my mistake :P
Kind regards,
Daan

Hello Daan, your code is correct.
The problem is that LayoutViewer doesn't support displaying labels with rotation due to a limitation in the Tkinter Canvas widget. From my experience, KLayout doesn't support this either.


Feature -> Watch Direct Model Changes

updates the date picker view if the model was updated in the parent scope

This PR have no documentation. Should be made a change to the readme file, including this attribute, so that every developer can see this behaviour.

Sorry. Added some documentation with the best explanation of a use-case I could come up with.

Still uncomplete, sorry, the build is missing. Use Grunt to build the changes made to the project.

My bad. Done!

Thanks

Would you be so kind to let me know when the new release is expected?


Without clicking user read new message and reply

I want to get new messages after connection and respond accordingly is it possible any guide.

I have done this my bot is running here: https://www.youtube.com/watch?v=BTlMerin54o


[FR]: Add Support for Custom Light/Dark Tones in Color Composables

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the problem
Currently, there are no color composable functions that allow users to set custom light and dark tones or colors for their applications. This issue proposes the addition of two new composable functions to address this gap.
Describe the solution

Add a Color.tone composable function that accepts custom light and dark tone values, allowing users to dynamically set the tones for their app's color scheme.

Add a lightDarkColor composable function that accepts custom light and dark colors as parameters, enabling users to define custom colors for light and dark modes.

Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Usefulness of Color.tone Function:
The Color.tone function is useful because it allows developers to create a more personalized color scheme for their apps. It provides flexibility by accepting custom light and dark tone values, making it easier to adapt the app's appearance to different preferences and design requirements.
@Composable
fun Color.tone(
  @IntRange(from = 0, to = 100) lightTone: Int,
  @IntRange(from = 0, to = 100) darkTone: Int,
): Color {
  val isDarkMode = MaterialTheme.isDarkMode
  return if (isDarkMode) {
    // Apply the custom dark tone to the color
    // ...
  } else {
    // Apply the custom light tone to the color
    // ...
  }
}

Usefulness of lightDarkColor Function:
The lightDarkColor function is valuable because it allows developers to define custom light and dark colors for their app's theme. It grants the ability to create unique and visually appealing designs that can adapt to different lighting conditions.
@Composable
fun lightDarkColor(
  lightColor: Color,
  darkColor: Color,
): Color {
  val isDarkMode = MaterialTheme.isDarkMode
  return if (isDarkMode) {
    // Use the custom dark color in dark mode
    darkColor
  } else {
    // Use the custom light color in light mode
    lightColor
  }
}


cellery build command usage is wrong

Usage:
cellery build  [flags]
As per that, only the cell file is mandatory. But if you run that command, you will find that the -t /: is also mandatory.
So usage should be:
cellery build

Fixed as per the last comment by madhuka. Thanks for the contribution @MadhukaHarith92


Last Finalized Snapshot Detection and Alert System

Is your feature request related to a problem?
There is no system setup to notify when a master node has not been processing snapshots or has gone down.
Describe the solution you'd like
The /health endpoint of the core-api should periodically query the protocol state contract for the current epoch and compare the epochId against active projects to detect how many epochs have passed since the last finalization. If any sampled projects have not finalized within a reasonable time (20-30 epochs?), then pooler will send a Slack alert notifying of a failure to finalize.
Describe alternatives you've considered
It might be worth exploring an external monitoring service that tracks the status independently since finalization requires submissions from multiple master nodes. However, it would be possible to get additional information for specific nodes if the monitoring is done internally.

The associated PR has been reviewed by me. Ideally would need another review from one of the @PowerLoom/backend-engineering team members before merging. Moving completion date to this week, Tuesday EOD.

Moving completion date to allow for final review of changes mentioned here: https://github.com/PowerLoom/pooler/pull/77#pullrequestreview-2024355389

@Seth-Schmidt update this please ^

merged to nms_master: https://github.com/PowerLoom/pooler/pull/77
closing


ja: Make docs/concepts/workloads/controllers/_index.md follow v1.19 of the original text

This is a Feature Request

What would you like to be added
Update docs/concepts/workloads/controllers/_index.md to follow v1.19 of the original (English) text.
Why is this needed
content/ja/docs/concepts/workloads/controllers/_index.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/tree/dev-1.19-ja.1/content/ja/docs/concepts/workloads/controllers/_index.md
Original
https://github.com/kubernetes/website/tree/release-1.19/content/en/docs/concepts/workloads/controllers/_index.md
diff between translated and v1.19
https://gist.github.com/421c7c642399ce6bbde938feb84d35fc
Note
Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/triage accepted

/assign

/close