Service not auto-starting

First - thanks so much for this!  Helped us solve a significant roadblock.
Windows 7 machine, all permissions on the files are correct (users/admins have modify access - user logging on is in local admin group).
When we realized that the service was stopped - we started it via 'start-service DNSagent' and it started just fine - no errors (event log shows 'successfully started').  All DNS issues resolved.
I will try to reproduce.
This is the event log error:
Service cannot be started. System.UnauthorizedAccessException: Access to the path 'C:\DNSAgent\options.cfg' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost) at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost) at DnsAgent.Program.ReadOptions() at DnsAgent.Program.Start(String[] args) at DnsAgent.Program.Service.OnStart(Str...
If you have any thoughts, would be appreciated!  If all else fails I can make the files 'everyone' accessible, but not sure how that'd solve the issue.

As a follow-up - I am able to reproduce the issue - service fails to start.  After more digging I found that the files were showing with 'unblock' buttons in their properties.  After unblocking all of the DNSagent files, I am now getting Symantec Endpoint warnings 'our information on this file is inconclusive'.  You can allow the file to run, but this completely breaks auto-start functionality.  :(
Closing this issue since it has nothing to do w. DNSagent.

Re-opening, perhaps something else is up.  We have completely removed Symantec from the machine, still getting that error.
I also gave full control to 'everyone' for all files in that dir, no change.  This is ONLY for the service auto-start.
I'll dig into it, but kinda stumped...hard to troubleshoot since it's only on auto-start.

Try changing the startup type to "Automatic (Delayed Start)" and log on account to Local System to see if this would help.
By default, "Automatic (Delayed Start)" will start in 2 minutes after the last "Automatic" service is started.
Sorry I haven't tested very much about running it as a service... and this project hasn't been updated for quite a while. I'm considering to make some improvements on this project recently. If you have any other problems, please let me know :-)

Will try that out.  The only practical problem with delayed start is that without DNS, not much works, haha.  So if you're using this as your machine's primary DNS server, stuff like Slack, domain-related things, etc won't work for 2min.  If it successfully auto-starts, will be better than a kick in the pants.

Yeah, delayed start was the only change I made - working now.
Perhaps there is some pre-req that needs to fire up before DNSagent?  Possible to make it last in the list of auto starting service?


AppEngine deployment

What I'm trying to achieve
Deployment to Appengine
Describe a proposed solution
see app.yaml file
I have the front end and backend running but have some minor errors remaining that seem to be either around postgress not being populated and so graphql possibly has no responses.
I populate the DB as follows:
`
#!/usr/bin/env bash
DJANGO_SETTINGS_MODULE=saleor.settings python3 manage.py migrate
DJANGO_SETTINGS_MODULE=saleor.settings STATIC_URL='/static/' python3 manage.py collectstatic --noinput
DJANGO_SETTINGS_MODULE=saleor.settings python3 manage.py populatedb
DJANGO_SETTINGS_MODULE=saleor.settings python3 manage.py createsuperuser
`
Screenshots or mockups

Postgress DB Images

Attached some logs:
scratch_1.txt
Appengine config:
app_debug.txt

SUCCESS: Querying the backend graphql directly gives:
2020-06-29 23:55:01.352 BST OPTIONS 200 0 B 1 ms Chrome 83 /graphql/ <IP_ADDRESS> - "OPTIONS /graphql/" 200 undefined "https://rila-dev-281513.ew.r.appspot.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36"
{  httpRequest: {   latency: "0.001s"      protocol: "HTTP/1.1"      referer: "https://rila-dev-281513.ew.r.appspot.com/"      remoteIp: "<IP_ADDRESS>"      requestMethod: "OPTIONS"      requestUrl: "/graphql/"      status: 200      userAgent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36"     }  insertId: "1uvsg46g38fkl5t"    jsonPayload: {   appLatencySeconds: "0.001"      latencySeconds: "0.001"      trace: "3c48f4cc63b9cf2a55e3611d647ca04f"     }  labels: {   appengine.googleapis.com/instance_name: "aef-saleor--backend-20200629t232956-c1n6"      appengine.googleapis.com/trace_id: "3c48f4cc63b9cf2a55e3611d647ca04f"      compute.googleapis.com/resource_id: "6808918004187255653"      compute.googleapis.com/resource_name: "5fcf56a2f5ee"      compute.googleapis.com/zone: "europe-west1-d"     }  logName: "projects/rila-dev-281513/logs/appengine.googleapis.com%2Fnginx.request"    receiveTimestamp: "2020-06-29T22:55:05.979261431Z"    resource: {   labels: {    module_id: "saleor-backend"        project_id: "rila-dev-281513"        version_id: "20200629t232956"        zone: ""       }   type: "gae_app"     }  timestamp: "2020-06-29T22:55:01.352Z"    trace: "projects/rila-dev-281513/traces/3c48f4cc63b9cf2a55e3611d647ca04f"   }
result:
{   "data": {     "products": {       "edges": [         {           "node": {             "id": "UHJvZHVjdDo3Mg==",             "name": "Apple Juice"           }         },         {           "node": {             "id": "UHJvZHVjdDo3NA==",             "name": "Banana Juice"           }         },         {           "node": {             "id": "UHJvZHVjdDo3OQ==",             "name": "Bean Juice"           }         },         {           "node": {             "id": "UHJvZHVjdDoxMTU=",             "name": "Black Hoodie"           }         },         {           "node": {             "id": "UHJvZHVjdDoxMTY=",             "name": "Blue Hoodie"           }         }       ]     }   } }

FAILED: Queries to the backend from the store front end gives:
2020-06-29 23:55:01.412 BST POST 400 332 B 13 ms Chrome 83 /graphql/ <IP_ADDRESS> - "POST /graphql/" 400 332 "https://rila-dev.ew.r.appspot.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36"
{
httpRequest: {
latency: "0.013s"
protocol: "HTTP/1.1"
referer: "https://rila-dev.ew.r.appspot.com/"
remoteIp: "<IP_ADDRESS>"
requestMethod: "POST"
requestUrl: "/graphql/"
responseSize: "332"
status: 400
userAgent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36"
}
insertId: "1d4gfocg10iogcf"
jsonPayload: {
appLatencySeconds: "0.012"
latencySeconds: "0.013"
trace: "78fb095cb6e6fd0b2df766b2fc"
}
labels: {
appengine.googleapis.com/instance_name: "aef-saleor--backend-20200629t232956-bmf7"
appengine.googleapis.com/trace_id: "78fb095cb6e6fd0b2df766b2fca8cd0c"
compute.googleapis.com/resource_id: "1083391943357485923"
compute.googleapis.com/resource_name: "73eab4d1474d"
compute.googleapis.com/zone: "europe-west1-c"
}
logName: "projects/rila-dev/logs/appengine.googleapis.com%2Fnginx.request"
receiveTimestamp: "2020-06-29T22:55:06.558607339Z"
resource: {
labels: {
module_id: "saleor-backend"
project_id: "rila-dev"
version_id: "20200629t232956"
zone: ""
}
type: "gae_app"
}
timestamp: "2020-06-29T22:55:01.412Z"
trace: "projects/rila-dev/traces/78fb095cb6e6fd0b2df766b2fca8cd0c"
}


Get object type from FieldNode in a GraphQL validator

I'm writing a authorization component to validate GraphQL queries.
Using the ValidationContextobject I manage to get the operation type (mutation/query), operation name and the non-scalar field names contained in the query.
What I need is to get the GraphQL type of these non-scalar fields.
Here is the code I'm using for the validator (using Typescript):
let entitiesArray:Array<string> = new Array<string>()

function getRecursiveSelectionSetNodes (selSetNode:SelectionSetNode) {
  selSetNode.selections.forEach ((node:FieldNode, index, array) => {
    if (node.selectionSet) {
      entitiesArray.push(node.name.value) // I could push the whole node, and make an array of nodes if necessary
      getRecursiveSelectionSetNodes (node.selectionSet)
    }
  })
}

export const authorizeQuery = function authorizeQuery (context: ValidationContext): any {

  let opNode:OperationDefinitionNode = getOperationAST(context.getDocument())

  let opType = opNode.operation
  console.log ('_________________ AUTH OPERATION TYPE: ', opType)

  let opFieldNode:FieldNode = <FieldNode>opNode.selectionSet.selections[0]
  let opName = opFieldNode.name.value

  console.log ('_________________ AUTH OPERATION NAME: ', opName)

    let selSetUser:SelectionSetNode = opFieldNode.selectionSet
  // Selected fields by the user
  // Here, first-level nodes will be objects requested by the query
  // The nodes without a nested "SelectionSet" node will be scalar
  // Nodes with a nested "SelectionSet" are non-scalar that need to be checked

  getRecursiveSelectionSetNodes (selSetUser)

  console.log ('_________________ AUTH ENTITIES: ', JSON.stringify(entitiesArray))

  return []

}

This code returns the field names, not the type, so I need to map the field name "users" with the graphQL type "User[]", and so on, so I can perform authorization based on the graphql type being requested.
Any ideas?

Hi @cdelgadob I think you'll be more likely to get an answer on the graphql-js repository, which is also where the visitor that is used by validation rules is defined.


Download FreeWallet.exe - Where?

Where to go to Download FreeWallet.exe?
I did a search for .exe file under code and was not able to locate.

Try visiting the freewallet.io website and clicking the "Download for Windows" link which will take you directly to the github release page where you can download the .exe
https://github.com/jdogresorg/freewallet-desktop/releases


feat: support twig namespaces with : in component name

I recently discovered this extension while looking for a 'slots' solution in twig, which this extension does very well. I am working on integrating twig-components into a project that allows plugins to register additional components, so they might not all be stored in one main directory. Initially I tried out initializing the plugin by passing a twig namespace as the component directory, like @components, which actually works decently well on its own. I can continue to register additional template directories under that namespace and reference twig files in any of them. This is just a project for my immediate team (for now), but I do see complications if more than one plugin inadvertently adds a twig template with the same filename.
In order to prevent this, I think it would be useful to be able to optionally specify a namespace along with the component name in the opening block tag. When including a component, the component name can contain one : which allows a twig namespace to be specified. Example: {% x:namespace:component.name %}
{# includes<EMAIL_ADDRESS>#}

{% x:mds:accordion with {title: 'Twig Components'} %}
	{% slot:content %}
Are Awesome!
%{ endslot %}
{% endx %}
{# or #}
<x-mds:accordion title="Twig Components">
	<x-slot name="content">
Are Awesome!
</x-slot>
</x-mds:accordion>

I was not too familiar with how twig actually parsed everything, but I did some research and took a look at how the parser in twig-components works and ended up making a couple small additions:

parseComponentName now appends @ to the initial item in the path if it finds a : in the initial component name (before any . directory markers)
I moved the short while loop that looks for dashes into its own function called getNameSection.
getComponentPath checks if a namespace is included before appending root directory.

I saw one issue that mentioned namespaces, but it was primarily about subdirectories. I considered trying to use that but to me it makes sense to take advantage of a feature twig has rather than having to nest files in an extra folder level. I made more progress than I originally thought I would, so I figured I would submit it as a PR and start a discussion about how useful others would find this.

Looks good!

Do you think is possible to add a test?
Have you tried with twig attributes? which add a : before the name, for example:

<x-my-button :name="'this is ' ~ 'twig'"/>

@giorgiopogliani Thanks! That's a really good point, I had not tested the :attr expression syntax with the x-tags. I went ahead and created some tests that include that as well as a couple other variations, and they all look good. I have also added a section to the readme with a short explanation as well.


Add support for documenting member variables

Current doctool will discard any information given for member variables as e.g. in #4563. We need to:

tweak doctool to have it parse and merge the contents of <member> tags properly (likely easy)
tweak the editor to have it display this information in the offline help
tweak the makerst.py script to have it display this information in the online help

By comparing with the code for <constant>, it should not be too hard to implement I think.

@bojidar-bg Could you handle tweaking makerst.py too?

@akien-mga ~ I think this works too, based on https://github.com/godotengine/godot/blob/master/doc/tools/makerst.py#L455


Feature/engine обсуждение движка

Coverage remained the same at 75.51% when pulling ad6ef805033cf5fde14a9bb6761110845c1d5dfe on feature/engine into c175bd11b95d6bec3e434afd3c22c02892654789 on master.

Coverage remained the same at 75.51% when pulling e01bdd473d98697afb69f92f2082ad1b0390bdff on feature/engine into c175bd11b95d6bec3e434afd3c22c02892654789 on master.


Enable Custom filtering

There may be occasions when you wish to search data presented to the end user in your own manner, common examples are number range search (in between two numbers) and date range search.

Hello Gabriel, I'm working on the vue-datasource from zero code, with this new features, but at the moment there is no support.
Check the new features comming here https://medium.com/@coderdiaz/vue-datasource-da794b8e724


Safari Embed Issues

Exporting does not work

This is due to Safari security settings not allowing window.open() when not directly associated with a button press event.
One possible fix is to have the "export" button immediately open a window and then change the URL of the window accordingly once it has received a response from our server

CSS styling messed up when Dev Console is open

Dev console does not like the @apply marker

Update: Possible fix does not work. Must be associated with a button click event which dart doesn't seem to bind very smoothly.

Addressed.


[don't merge] Map opened archetypes to the instructions defining them.

What's in this pull request?

This is an alternative implementation of opened archetypes mapping, based on some comments from PR https://github.com/apple/swift/pull/2707
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing

Platform
Comment

All supported platforms
@swift-ci Please smoke test

All supported platforms
@swift-ci Please smoke test and merge

OS X platform
@swift-ci Please smoke test OS X platform

Linux platform
@swift-ci Please smoke test Linux platform

Validation Testing

Platform
Comment

All supported platforms
@swift-ci Please test

All supported platforms
@swift-ci Please test and merge

OS X platform
@swift-ci Please test OS X platform

OS X platform
@swift-ci Please benchmark

Linux platform
@swift-ci Please test Linux platform

Lint Testing

Language
Comment

Python
@swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

Introduce a helper class SILOpenedArchetypesTracker for creating and maintaining such mappings.
These mappings are constructed on demand and used by SILCloner, sil-inliner, sil-verifier and other optimizer passes to properly handle opened archetypes.

@swift-ci Please test Linux

swift-package test failures seem to be unrelated.

@rudkx @atrick Is it more inline with your ideas of rebuilding the map on-demand?

Architecturally this is vastly simpler than adding hooks inside SILFunction. It is also simpler in terms of the work actually being done during compilation. The implementation is complicated and awkward because you now need to pass a tracker into SILCloner, and I'm not sure this is really useful as an Analysis either. AFAICT this mapping is really a just utility to be used within SILVerifier. SILCloner does need to be passed a mapping from opened type to open_existential, but only for the types involved in it's own substitution list, which I think could be provided directly by the inliner. I don't know why you need to pass over the function searching for open_existential to build that map. (probably missing something)

Is this obsolete?

It is obsolete now.  Closing.


Chart tooltips aren't announced

This is related to OfficeDev/microsoft-teams-ui-component-library#142 since the implementation here would be the same.
This may mean it's worth considering #35 if that might offer a fix out of the box.

Looks like Chart.js v3 doesn't offer any help announcing tooltips either. Chart.js's documentation on accessibility is not at all comprehensive and doesn't mention tooltips at all.


Bad rendering of btn-outline-light under navbar-dark

With the following html code:

                LintoCop

            Sign in

Hovering the button makes this:

I don't think this is the expected behavior. :-)

Hi @Soullivaneuh I am confuse. I can't reproduce it. Here is your exact same code running on 4-beta:
https://codepen.io/andresgalante/pen/NaRMvN

Duplicate of #23351.


Fixed #26763 - Control rendering of add/change/delete_related admin buttons

In certain cases, displaying the add/change/delete icons on related fields in the Django admin is undesirable, but this behavior can't currently be overridden. This patch allows configuration of which buttons to display by passing kwargs into formfield_for_db. If you are OK with the approach, I can write tests and add docs. Let me know if I should pursue. Thanks!

Not sure this exact implementation would work because "If kwargs are given, they're passed to the form Field's constructor." Won't these new arguments be unexpected there?

I will fix, test, and update the PR. Thanks folks.

Okay, please send a new PR when you return to it.


Two "Singly Linked List" programs in documentation

📚 Documentation
(A clear and concise description of what the issue is.)
Have you read the [Contributing Guidelines on Pull Requests]
(https://github.com/TesseractCoding/NeoAlgo/blob/master/CONTRIBUTING.md#reporting-new-issues)?
Yes, I've read the guidelines.
(Write your answer here.)
There are 2 links of "Singly Linked List" one with Python and another with C++ in C++ documentation.
As a GSSOC21 Participant , I would like to remove the python link/file from the documentation for c++.

Please assign me this issue @bhav09

@Saatvik21  Please make sure you follow the issue template before opening any issue!

All the best @Saatvik21 :)

All the best @Saatvik21 :)

Sir please add GSSOC label for this issue.


What are the Methods/functions in Soft Assertion?

Hello,
I want the execution to continue even if the assertion validation fails.
So choosing the soft assertion like mentioned in the below link:
https://npm.runkit.com/assertion-soft
However, I am unable to find the methods which can be used for validate the actual value against the expected value.
The below code is throwing error saying "TypeError: assertionSoft.equal is not a function":
var assertionSoft = require("assertion-soft")
var assertResult = assert.equal(("expected",
"actual", 'Element check for the ' + element + ' is failed');
Please provide the relevant method.

assertion-soft is deprecated and has been replaced with const assert_warning = require('reassert/warning');.
assert_warning(false, "warning bla bla..."); will not throw but only print the "warning bla bla..." message with the stack trace.
Feel free to re-open.

Thanks for the reply. Request you to reopen the issue:
Using assert_warning is not validating the actual versus expected value.
Also, in the runkit its throwing the error.
Could you please provide a correct syntax to verify the actual value versus the expected value.
Please find the attached screenshot of the run kit:

In https://npm.runkit.com/reassert
run
var assert_warning = require("reassert/warning")

assert_warning(false, "bla bla");

Hi brillout,
We are using Cucumber Framework and test cases have been written in Feature Files.
Basically we want to achieve 2 objectives as below:

There are 10 steps(lines)of assertion in the feature file and 5th line fails, the execution should still continue and execute 6th to 10th steps.
In the report the failed step(i.e 5th Step) should be clearly marked as "Failed". Thus we can clearly make out 9 out of 10 steps passed and 1 failed.

Can we achieve this using "var assert_warning = require("reassert/warning")"   ????

Sounds like reassert is not what you are looking for


Create model package

Hi,
In this method, it is possible to better manage the codes, also this method is the Best Practice in Django-based development.

I rebase this branch onto 'main' and there aren't any merge conflicts.


Add osquery package back

Project description

osquery is a SQL powered operating system instrumentation, monitoring, and analytics framework.
osquery exposes an operating system as a high-performance relational database. This allows you to write SQL-based queries to explore operating system data.
https://github.com/osquery/osquery

The project has been deleted from packages in this MR: https://github.com/NixOS/nixpkgs/pull/74081.
Metadata

homepage URL: https://osquery.io/
source URL: https://github.com/osquery/osquery
license: Apache-2.0 and GPL-2.0
platforms: Linux, macOS, Windows, and FreeBSD

Looks like there is little interest, you are the first to mention it since 2019 so if you are not ready to maintain it, I wouldn't hold my breth.


[Darwin] MTRDeviceControllerStorageDelegate should support bulk store/fetch

This adds bulk store/fetch in the MTRDeviceControllerStorageDelegate, and the MTRDevice attribute storage implementation is changed to use it for bulk reads and writes if the storage delegate supports it.

Pushed wrong branch. closing this and will make new PR.


[JAVA] maven add the flight-core failed

Describe the usage question you have. Please include as many useful details as  possible.
I add these in the pom.xml
<dependencies>
      <dependency>
          <groupId>org.apache.arrow</groupId>
          <artifactId>flight-core</artifactId>
          <version>${arrow.version}</version>
      </dependency>
  </dependencies>

In building, it will occur the problem
Exception in thread "main" java.lang.StackOverflowError
	at org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:343)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)
	at org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:347)

What is wrong in my setting?
Component(s)
Java

What version of maven, what is the value of ${arrow.version}, and is it possible to share the full pom.xml?

Thanks.
I grabbed a copy of Apache Doris and put your pom.xml in place of fe/fe-core/pom.xml.
I can't fully build for other reasons, but at least maven gets past package resolution and gets to compilation of fe-core, so I'm not able to reproduce here.
Do you happen to have a branch to look at?
(Also, it looks like Doris uses very old versions of Arrow? 9.0.0 is somewhat recent but I saw 7.0.0 in the build as well.)

Thanks! I can reproduce now. Let me see...

It seems something like https://issues.apache.org/jira/browse/MNG-6737
Doris appears to pin gRPC 1.30.0 in this commit but Flight uses 1.47.0. If I change Doris's pin to 1.47.0 it appears to get past dependency resolution. (Compilation fails but I'm not running the full build script so I probably have something else wrong.)

@Cai-Yao it sounds like from the other issue that you got past this problem?

@Cai-Yao it sounds like from the other issue that you got past this problem?

Thanks for your reply, I still haven't located the cause of this problem and I am currently solving it by:
<dependency>
    <groupId>org.apache.arrow</groupId>
    <artifactId>flight-core</artifactId>
    <scope>system</scope>
    <systemPath>${pom.basedir}/libs/flight-core-9.0.0.jar</systemPath>
</dependency>

I'm not very good at JAVA and will ask the Doris guys for help later to see if it's a problem with some dependencies.

The Maven dependency issue introduced by Apache Doris into Arrow Flight has been resolved.
Here: https://github.com/apache/doris/pull/24314
This issue can be closed, thanks @lidavidm

Great, glad to hear it!


Adding Microsoft Autogen + generated figure visualizer support ?

@Mshz2  - Can you provide more details on the ask?

@Mshz2 - Can you provide more details on the ask?

Sure.
As the Autogen project repository shows:

It would be great to also plot the agents responses.


The 0-1 Knapsack Problem.

I would like to add the 0-1 Knapsack problem, a very famous Dynamic Programming algorithm.

@heisenberg-2505 I have assigned this issue to you. Whenever you're done with the implementation, please submit a PR for it against the reorganise branch along with a unit test.

The .hpp file will be the algorithm, and the .cpp file (in the test directory) will be the unit test.

I have written the unit test but the make file is not running/compiling my unit test file.
The code in my test file is -
#define 0_1_KNAPSACK_TEST
#include "third_party/catch.hpp"
#include "algorithms/dynamic_programming/0_1_knapsack.hpp"
TEST_CASE("BASE CASES", "[knapsack]") {   REQUIRE(knapsack (10, 3, [11, 21, 31], [1, 2, 3]) == 0); }
#undef 0_1_KNAPSACK_TEST

Do we need to make changes to some other file to make this work?

I don't have the code in front of me so will have to answer your question later, but have you tried compiling using CMake? There are several examples in CMakeLists.txt of how to compile the unit test files.

Where is the file you mentioned above, is located?

Closed in #191.


Support for Kubernetes v1.16

Ref to the Changelog: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.16.md

@gardener/gardener-maintainers , should we consider EOL for v1.10 before v1.16 adoption?

Why do we have to remove 1.10 before adopting 1.16? At the moment it doesn't harm (code complexity-wise), and we still don't have an upstream policy for such deprecations/removals. So, I wouldn't do it now, particularly not as prerequisite.

I have pushed the feature/kubernetes-1.16 branch for the necessary adaptations.


add controller helper to help us when looking for action of a specific route

Hey @taylorotwell
Suppose we deal with an application that has many route() helpers all over Tests and source code.
When we face route() helpers in our code, it's hard to detect the controllers that are related to these helpers, especially when we deal with some dirty code or some huge application, it gets harder.
At the moment we must use php artisan route:list | grep "ROUTENAME" if we want to find the related controller but this way has more complex and even many developers don't know what they can do.
As a solution, I think if we have a controller() helper this help us overcome this situation.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Wait for volume state to become available before trying to attach

Fixes #147 by retrying the AttachVolume operation.

Close as we will do this in volume provisioner


Add data prop to FService::Base#Check

hey,
everytime myself and my colleages use the FService::Base#Check method we end up with the problem of not being able to pass a custom data to the resulting Result. In the end, we end up writing code very similar to what the gem does in the method definition.

Nice addition! I was planning to add this very patch! Thanks!


Use elemental to build raw images

Signed-off-by: Itxaka<EMAIL_ADDRESS>

arm is broken :(

arm is broken :(

Now it should be possible to run a PR with an elemental bump and use the updated elemental to build the ISOS and disks, it should make testing easier.


--p command line option should support taking a full path or directory.

This would allow you to specify a tsconfig.json that has a different name.
If you specify a directory, it should first try to resolve tsconfig.json. If it can't find it, it should find the first tsconfig*.json file
References: https://github.com/Microsoft/TypeScript/issues/2868#issuecomment-95262429

What benefit can we get when tsc automatically search tsconfig*.json files? What should happen when there are multiple tsconfig* files except tsconfig.json?

since my request #5705 got closed I am writing here:

let's add a parameter that points to whatever configuration file we please: --configuration c:\foo\bar\myproject.csproj

let's add a parameter that points to whatever configuration file we please: --configuration c:\foo\bar\myproject.csproj

@aleksey-bykov can you elaborate on what is the expectation here? do you expect tsc to read the .csproj? where would the infrormation be stored?

i am saying the developer should be free to specify any file that has a valid tsconfig JSON content even if the name itself doesn't make any sense

i see, so why not use --project as in the OP?

because it's already taken it would be a breaking change

not really, we can check if it is a file path use it, if it is a directory append "tsconfig.json" before reading the file.

true, good catch

Thanks @SaschaNaz ! :tada:


[dunfell][gatesgarth][harknott][master] ogre

fixes:
ERROR: Nothing PROVIDES 'virtual/libgl' (but ros2-foxy-dunfell/meta-ros/meta-ros-common/recipes-devtools/ogre/ogre_1.12.8.bb DEPENDS on or otherwise requires it)
mesa-gl PROVIDES virtual/libgl but was skipped: one of 'vulkan opengl' needs to be in DISTRO_FEATURES
ERROR: Nothing PROVIDES 'libglu' (but ros2-foxy-dunfell/meta-ros/meta-ros-common/recipes-devtools/ogre/ogre_1.12.8.bb DEPENDS on or otherwise requires it)
libglu was skipped: missing required distro feature 'opengl' (not in DISTRO_FEATURES)
ERROR: Nothing RPROVIDES 'ogre-dev' (but ros2-foxy-dunfell/meta-ros/meta-ros-common/recipes-devtools/ogre/ogre_1.12.8.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'ogre-dev'
NOTE: Runtime target 'ogre-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ogre-dev']
ERROR: Nothing RPROVIDES 'ogre' (but ros2-foxy-dunfell/meta-ros/meta-ros-common/recipes-devtools/ogre/ogre_1.12.8.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'ogre'
NOTE: Runtime target 'ogre' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ogre']

Signed-off-by: Martin Jansa<EMAIL_ADDRESS>

Small additional fix for https://github.com/ros/meta-ros/pull/817

Merged in other branches as well.
84e1ae74e..3a5efdcc5  dunfell -> dunfell-next
eb5f2b40c..ae1ee2e77  gatesgarth -> gatesgarth
eb5f2b40c..ae1ee2e77  gatesgarth -> gatesgarth-next
3262c4778..e0b1ad480  hardknott -> hardknott
3262c4778..e0b1ad480  hardknott -> hardknott-next
3262c4778..e0b1ad480  master -> master
3262c4778..e0b1ad480  master -> master-next


Added apply_query() + other specs; fixed build_cte() spec.

Also refactored apply_query() a little. The escape_query() function will always receive a Query struct afaics so I removed the second clause.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Verify all agents for all sims working

It appears many agents are not working out of the box. We should verify all of them and add the necessary documentation,

For example:
$ python train_randomwalker_DRAMSys.py
Traceback (most recent call last):
  File "/home/oss-arch-gym/sims/DRAM/train_randomwalker_DRAMSys.py", line 11, in <module>
    from arch_gym.envs import dramsys_wrapper
  File "/home/oss-arch-gym/arch_gym/envs/dramsys_wrapper.py", line 19, in <module>
    from acme import specs
ImportError: cannot import name 'specs' from 'acme' (unknown location)

We need to add something like os.sys.path.insert(0, os.path.abspath('../../acme')) like in train_ppo.py under sims/DRAM

Noting here that @manan-garg1504 is working with @aadyapipersenia04 to add acme to install script for this issue

@AditiR-42 I was trying to run astra-sim after a clean install, but now the submodule cloning fails:
$ git submodule update --init --recursive  sims/AstraSim/astrasim-archgym
fatal: remote error: upload-pack: not our ref 53574d2f1d20e26d5143eb0ff0c98b6af338da61
fatal: Fetched in submodule path 'sims/AstraSim/astrasim-archgym', but it did not contain 53574d2f1d20e26d5143eb0ff0c98b6af338da61. Direct fetching of that commit failed.

Does the documentation need to be updated?


Trigger causes issue with platform limits

Hi there, I have a few triggers that are deployed to do rollups. When records are inserted on cloned en mass the logs show the trigger causes MAX CPU time errors. Is there a way to bulkify or @future the trigger? I could use scheduled rolllups but I find that they lack accuracy and records don't always get included in the job

Please delete this issue.


[spec violation] super without a constructor doesn't throw

@ariya If the super property doesn't have a contructor, it should throw an syntax error. There are many examples on this if you are looking into the specs.
All this should fail:
class A {
    foo() {
        super()  // Invalid 'super()'.
    }
}

class A {
    static foo() {
        super()  // Invalid 'super()'.
    }

    static prototype() {  // Invalid method.
    }
}

function foo() {
    super()  // Invalid `super`.
    super.foo()  // Invalid `super`.
}
var foo = function() {
    super()  // Invalid `super`.
    super.foo()  // Invalid `super`.
}

function wrap() {
    function foo(a = super(), b = super.foo()) {  // Invalid 'super'.
    }
}

Reference: http://www.ecma-international.org/ecma-262/6.0/#sec-class-definitions-static-semantics-early-errors

Thanks for the report @nowindowsowrking!

Hi @ariya, is this fixed? I would like to look into it, if not.

@hzlmn Not fixed yet, feel free to give it a try.


PSR-7 Support

extended https://github.com/99designs/http-signatures-php/pull/19

added custom HttpMessageFactory to avoid query string being reordered.
added some more type hints for methods.

:+1:

looking forward to seeing this merged, any feedback?

ping @vinkla
tests only fail because somehow my removal of php 5.3 from .travis.yml didn't 'work', maybe cuz it's a PR ...

Yeah, some of the dependencies require >=5.4.

The psr7 package require at least >=5.4.0.

@vinkla @navitronic could you guys review this and merge?

IMO we should even drop 5.4. PHP 5.5 will also be see end of life soon.

Hi @rubensayshi,
I'd pretty much missed this.
Will review over the weekend and get back to you.
cheers,
Adrian

@rubensayshi Thanks again for this, I have merged this into my PR and am doing some tweaks to it, hoping to merge it into master and have a new release available soon.

awesome! let me know if there's anything I can do to help, review or test!
also once you have it stable I can update https://github.com/99designs/http-signatures-guzzlehttp/pull/8 which also works as a good extra test before you merge it ;-)


Fix web route prefix wrapped twice

Signed-off-by: yeya24<EMAIL_ADDRESS>

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Fixes #2483
Changes

The web route prefix is registered twice.
Verification

Tested in my local env and here

While I am trying to fix this, I found that web route prefix is not well handled for the routes other than /api/v1. I already implemented a fix for that, but I am not sure whether that fix should be included in this PR. So I opened #2486

Thanks on working on this :heart:
First of all do we know what commit introduced this bug? I think we should fix all, but on release-0.12 branch first so we can embed this fix to 0.12.1 or 0.12.2
cc @squat

Let us know when you wake up, we can talk offline.

Also question how @fengzixu or we can help with this if you are busy. (:

Hmm, the original issue mentions #2208 but that doesn't seem like the cause to me

@yeya24 let's make this PR against the release-0.12 branch and then we'll merge that branch back into master once we cut the release. Let me know if you want to make the PR, otherwise I can prepare it

I think Ben is US time zone, so if we want to have it sooner we need to do
it alone.
On Tue, 21 Apr 2020 at 08:13, Lucas Servén Marín<EMAIL_ADDRESS>wrote:

@yeya24 https://github.com/yeya24 let's make this PR against the
release-0.12 branch and then we'll merge that branch back into master once
we cut the release. Let me know if you want to make the PR, otherwise I can
prepare it
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/thanos-io/thanos/pull/2484#issuecomment-616998365,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVA3O4NAWO33ZGSWKUTDJDRNVBS7ANCNFSM4MMZS3XA
.

@yeya24 let's make this PR against the release-0.12 branch and then we'll merge that branch back into master once we cut the release. Let me know if you want to make the PR, otherwise I can prepare it

@yeya24 let's make this PR against the release-0.12 branch and then we'll merge that branch back into master once we cut the release. Let me know if you want to make the PR, otherwise I can prepare it

Thanks. Please do it. ❤

Cool on it

superseded by https://github.com/thanos-io/thanos/pull/2489
This fix will make in into master when the release-0.12 branch is merged into master after the release


Why return the error in Warning and Error method?

There are some problem with me. So, when i using the see.Error() and see.Warning method in IDEA, some message that   "unhandled message" in my eyes.I'm feel so bad.Can you tell me why return the error in these method. My be i can change it.

Project looks abandoned.  No life in two years.


Peering Client on FABRIC

I am including a new tool in FABRIC that allows users to perform experiments using PEERING

A little late to the party, but you can review these notebook changes with GitNotebooks too: https://gitnotebooks.com/fabric-testbed/jupyter-examples/pull/264
I think it offers some advantages over what you're currently using.


Issue 1247

#1247
Replaced the ScaleOutputError with a MissingRequiredOutput error when a required output file is not found.
Added a new UnexpectedMultipleOutputs error that is raised when multiple files are found for a singular output.

@JohnPTobe Good catch. Fixed the settings file.


WIP on expected price impact

Fixes #255 .
Changes proposed in this PR:

handle simple and advanced cases
added number of ocean amount to remove
compute number of shares needed
calculate the slippage

Balance should be the amount of ocean, not pool shares
You will receive ocean, not pool shares.

So considering what we discussed before, for the simple flow balance will be in ocean, but for the advance flow it will remain in pool shares. right?

Apparently i was wrong, i updated the issue. We go back to the slider and implement what is described in the issue.

Should be like this

I corrected, so now we have:

I'll push the changes in a moment.
Also, kept the original helper content. For advanced, should we say "You will receive minimum" or keep it simple?

You will receive minimum

Functionality-wise seems to be all good now.
In both, simple & advanced we need to get the token numbers aligned again:

They need to be aligned like so where numbers are always on one row:

Most likely through making the font-size for those headings smaller. Which then implies doing the same on all the other screens, like Add/Trade so all those output headings stay consistent.
Other than that, #455 should then make the tests succeed again


DQCP Product Issue

Describe the bug
This page says

The scalar product * is quasiconvex when one of its arguments is nonnegative and the other is nonpositive, and it is quasiconcave when its arguments are both nonnegative or both nonpositive. Hence, the product of two nonnegative quasiconcave functions is quasiconcave, and the product of a nonnegative concave function and a nonpositive convex function is quasiconvex.

Consider the following code:
#!/usr/bin/env python3
import cvxpy as cp

x = cp.exp(cp.Variable(pos=True))
y = cp.exp(cp.Variable(pos=True))
p = cp.multiply(x, y)
x
y
assert p.is_dqcp()

which gives output:
>>> x
Expression(CONVEX, NONNEGATIVE, ())
>>> y
Expression(CONVEX, NONNEGATIVE, ())

Based on the description on the page the scalar product "is quasiconcave when its arguments are both nonnegative".
Expected behavior
x and y satisfy the condition listed, but the result is not DQCP. x and y also seem to satisfy the more formal conditions listed higher on the page.
Version

OS: Ubuntu 18.04.2 LTS
CVXPY Version: 1.0.24

Additional context
I think either the disciplined evaluator or the textual description has a mistake.

Hey Richard — thanks for writing up your issue so clearly.
The scalar product atom, , is quasiconcave when its arguments are nonnegative. This means that x * y is quasiconcave when x and y are nonnegative. So exp(x) * exp(y) is quasiconcave in x’ = exp(x) and y’ = exp(y), but not necessarily in x and y. In particular, exp(x) * exp(y) doesn’t satisfy the composition rule because xy is quasiconcave and increasing in its arguments (when they are nonnegative), but exp(x) and exp(y) are convex. On the other hand, you’ll find that sqrt(x) * sqrt(y) is correctly parsed as quasiconcave.
Does that make sense?

Thanks. If I follow you correctly, this problem (product of non-negative convex forms) cannot be translated into a quasiconvex form. I believe this makes sense, but it takes some squinting at the documentation to find that argument. Perhaps a counter-example there would make it clearer.

Yes, that's correct. I've added a small clarification to the documentation, which should be reflected on the website within a few days.


how to change xeditable color while data change in angular JS X-editable

I have editable text , if user edits value say from 10 to 20 , editable colour should change from Default colour (Blue) to Green ..
This will help user to identify that there was a change made

I think you could add something like this to your editable link:
ng-class="{your_class: your_item >= 10 && your_item <= 20}


investigate removing parentnode reference

need to check if we can do it without the parentnode. this would reduce memory footprint

well, after looking at it for a while, I don't really think it is doable, and if so, without losing perf.


Fix installation with rubygems 3.4+

Rubygems 3.4.0 introduced a change that cleans the build artifacts from the ext directory. However, this gem depends on the compiled C function being there as a shared object, so would break with an output similar to:
🕙 14:23:02 ❯ docker run -it --rm -v (pwd):/app -w /app ruby:3.2.0 bash
root@72d3ddb49511:/app# gem install levenshtein-ffi
Fetching levenshtein-ffi-1.1.0.gem
Fetching ffi-1.15.5.gem
Building native extensions. This could take a while...
Successfully installed ffi-1.15.5
Building native extensions. This could take a while...
Successfully installed levenshtein-ffi-1.1.0
2 gems installed
root@72d3ddb49511:/app# irb
irb(main):001:0> require 'levenshtein-ffi'
/usr/local/bundle/gems/ffi-1.15.5/lib/ffi/library.rb:145:in `block in ffi_lib': Could not open library '/usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein.bundle': /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein.bundle: cannot open shared object file: No such file or directory. (LoadError)
Could not open library '/usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein.so': /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein.so: cannot open shared object file: No such file or directory.
Could not open library '/usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein.dylib': /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein.dylib: cannot open shared object file: No such file or directory.
Could not open library '/usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein': /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/../ext/levenshtein/levenshtein: cannot open shared object file: No such file or directory
	from /usr/local/bundle/gems/ffi-1.15.5/lib/ffi/library.rb:99:in `map'
	from /usr/local/bundle/gems/ffi-1.15.5/lib/ffi/library.rb:99:in `ffi_lib'
	from /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/levenshtein.rb:10:in `singleton class'
	from /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/levenshtein.rb:4:in `<module:Levenshtein>'
	from /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/levenshtein.rb:3:in `<top (required)>'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from /usr/local/bundle/gems/levenshtein-ffi-1.1.0/lib/levenshtein-ffi.rb:1:in `<top (required)>'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:160:in `require'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:160:in `rescue in require'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:149:in `require'
	from (irb):1:in `<main>'
	from /usr/local/lib/ruby/gems/3.2.0/gems/irb-1.6.2/exe/irb:11:in `<top (required)>'
	from /usr/local/bin/irb:25:in `load'
	from /usr/local/bin/irb:25:in `<main>'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- levenshtein-ffi (LoadError)
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from (irb):1:in `<main>'
	from /usr/local/lib/ruby/gems/3.2.0/gems/irb-1.6.2/exe/irb:11:in `<top (required)>'
	from /usr/local/bin/irb:25:in `load'
	from /usr/local/bin/irb:25:in `<main>'

when required.
This PR runs make install when installing the gem to place the complied file into the $LOAD_PATH, and then instructs ffi-lib to search for it in there. This appears to fix the issue.

Hi @triarius - Thanks for this! I took a look at how other gems with native extensions are handling this and made https://github.com/dbalatero/levenshtein-ffi/pull/11

@thekendalmiller sounds like the right thing to do. I'll leave this up in case some people want it.


x/playground: result not cached when using Go 1.20

What version of Go are you using (go version)?
1.20 on the playground
Does this issue reproduce with the latest release?
With 1.20, but not 1.19
What operating system and processor architecture are you using (go env)?
Playground
What did you do?
Ran the code from @rsc new blog post (link) multiple times.
Whole file:
// Note that this program will print one answer
// consistently on the Go playground due to caching.

package main

import (
	"fmt"
	"math/rand"
)

func main() {
	fmt.Println(rand.Perm(37)[:10])
}

What did you expect to see?
The same result when running multiple times, as written at the top of the file:
// Note that this program will print one answer
// consistently on the Go playground due to caching.

What did you see instead?
Different results.

cc @@toothrot

I think this is to be expected, 1.20 now automatically seeds numbers for us, where in 1.19, the seed would always be 1 and print this number in each run, it is not related to cache I believe
5577006791947779410 (this number is printed in every version below 1.20) https://go.dev/play/p/qCp3lxxXQ_A?v=goprev

@mrwormhole the playground is, or at least was, to my knowledge supposed to be deterministic so that results don't change over time and can be cached (even sleeps are actually cached and emulated in the browser!)

I'm not sure what is to be expected from the playground in this regard either.
In the about section there is: In the playground the time begins at 2009-11-10 23:00:00 UTC (determining the significance of this date is an exercise for the reader). This makes it easier to cache programs by giving them deterministic output.
So it looks like only the time is deterministic. But before go 1.20, using math.Rand was indeed also deterministic.
On the other hand, crypto/rand was never deterministic, afaik.

Thanks for the report.
Caching does indeed appear to be broken, though I don't think this is specific to 1.20. I can take a look.

This is the expected behaviour in Go 1.20. Please take a look at the Go 1.20 minor library changes.
The [math/rand](https://tip.golang.org/pkg/math/rand/) package now automatically seeds the global random number generator (used by top-level functions like Float64 and Int) with a random value, and the top-level [Seed](https://tip.golang.org/pkg/math/rand/#Seed) function has been deprecated. Programs that need a reproducible sequence of random numbers should prefer to allocate their own random source, using rand.New(rand.NewSource(seed)).

Programs that need the earlier consistent global seeding behavior can set GODEBUG=randautoseed=0 in their environment.

The top-level [Read](https://tip.golang.org/pkg/math/rand/#Read) function has been deprecated. In almost all cases, [crypto/rand.Read](https://tip.golang.org/pkg/crypto/rand/#Read) is more appropriate.

If you add the rand.Seed(1), the result in Go 1.20 is exactly the same as Go 1.19.
func init() {
    rand.Seed(1)
}

https://go.dev/play/p/ZrxLwB7yS5A

@roger2hk This is not about the change in the behaviour of math/rand but about the playground not caching the program execution.


Update to mui v5 from material-ui v4

This upgrades material-ui v4 to mui5. Additionally it provides an upgrade script for plugin authors to automate the process of updating their plugins.

[X] Sidebar doesn't collapse properly
[X] Styles are ported to the v5 flavor
[x] Select, TextField, and FormControl components show the same style (not contained) as before
[x] The logo's sidebar button (in mobile view) is not showing up
[x] Autocomplete filter (like on Namespaces view) is broken, doesn't filter.
[x] get snapshot testing working with generated mui class names
[x] update snapshots
[x] headlamp-plugin webpack config can work with mui v5 (add similar existing config with new mui paths)
[x] consider keeping material-ui v4 available to plugins for backwards compat. (keep exporting them for plugins, and have material ui 5 working). Seems to work so far in my testing. It was decided to just support mui 5.

[x] next round of mui5 fixes

[x] rebase
[x] add https://mui.com/material-ui/migration/migration-v4/ to commit
[x] update mui packages to latest versions
[x] cod mod new files
[x] fix typescript issues
[x] fix test failures / typecheck errors
[x] Fix TopBar background color in dark mode
[x] fix broken plugin tests

[x] update plugins/index.ts to remove importing material ui.
[x] headlamp-plugin updates
[x] tests pass

[x] remove material-ui
[x] Bring in other commits from old PR
[x] headlamp-plugin upgrade should also update user plugins to mui v5. Add codemods headlamp-plugin
[x] do headlamp-plugin alpha release 0.8.0-alpha.0
[x] upgrade example plugins,` and retest them all.
[x] In dark theme, the links always have the underline

Whilst testing plugin upgrades, some fixes and improvements were required.

[x] improvements to headlamp-plugin upgrade

[x] do package upgrades more robustly.
[x] documentation for headlamp-plugin upgrade
[x] have an alpha tag, and a command line option to select it, so it is easier to test headlamp-plugin alpha pre-releases.
[x] provide migrations for a few typing issues with mui and plugins (with SVG, and package upgrades) found testing plugins.

[x] a compatibility check. (disabled for now, because there is quite a level of compatibility already, TBD).

Visual UI issues remaining...

[x] blue text for custom cluster chooser (default one is fine)
[x] back button is on /settings is blue
[x] documentation tab on editor is broken
[x] switch border color is blue, on /settings theme switch
[x] the icons are slightly larger (app bar notification icon and /settings page icon), maybe not a problem.

[x] The cancel button in the snackbars should be red-ish, not purple

[x] The main color is apparently now black but should be blue as before. (See all switches/buttons for example)

How to use
Update packages and run headlamp again.
cd frontend
npm i
cd ..
make run-frontend

Testing done

[x] npm run lint passes
[x] npm run tsc passes
[x] npm run test passes
[x] headlamp-plugin tests pass
[x] smoke testing
[x] updating snapshot tests
[x] test old example plugins still work
[x] test example plugins headlamp-plugin upgrade
[x] test plugins repo plugins headlamp-plugin upgrade

@joaquimrocha I fixed the type checking, testing, and format checking. The Build Frontend job is now failing on the plugin tests.

wip

Good stuff!
I was browsing around and noticed there is a weird bug that causes the documentation tab when editing a resource to render a string and not the clickable elements

Updated a few things so the headlamp-plugin upgrade works for all example plugins, the ai, prometheus, and app-catalog plugins.
Added a modified compatibility check (disabled for now, more on that later).
rebased on main

Then I did a larger side by side visual comparison between main and this branch and found these:

[ ] blue cluster chooser
[ ] back button is on /settings is blue
[ ] documentation tab on editor is broken
[ ] switch border color is blue, on /settings theme switch
[ ] the icons are slightly larger (app bar notification icon and /settings page icon), maybe not a problem.
[ ] in dark mode, app bar is a dark grey rather than completely black
[ ] action icons spacing is a bit off on pod detail view /c/minikubeThisisreallyLong/pods/default/keycloak-7b478749bc-ghvdn

Now I'm working on these visual issues.

@joaquimrocha I removed the console.log's and added a couple of missing signed-off-bys.

I'll look at these two now...

The cancel button in the snackbars should be red-ish, not purple
The main color is apparently now black but should be blue as before. (See all switches/buttons for example)

I pushed changes for these two...

The cancel button in the snackbars should be red-ish, not purple
The main color is apparently now black but should be blue as before. (See all switches/buttons for example)

The back button, and the theme change button are colored black & white individually now. So they look as they did before.

Thanks @illume , it's looking fine to me now! Merging now!


Enable multiple Reusable Conditions

This merge request allows multiple modules to be specified in reusable_conditions.

Do you have any suggestions @rsinger86?

This looks good, thanks. I'll probably make some minor style changes for consistency, but I'll get it released soon.


Update to newest femtovg/glutin/winit; fix clipboard on wayland

Closes #113
We should pin to femtovg 0.3.6 whenever it is released.

This PR now reverts part of the crates refactor - run-wasm needs to be in the repository root, otherwise it will create a target dir under crates, which prevents further builds from happening.

I'm not entirely sure what it'll take to support clipboard+wayland+baseview. I think a feature is missing in baseview to support getting the pointer necessary to initialize the clipboard context?

I'm not entirely sure what it'll take to support clipboard+wayland+baseview. I think a feature is missing in baseview to support getting the pointer necessary to initialize the clipboard context?

Last time I checked baseview didn't support wayland at all. I think it's just Windows, MacOS, and x11.

I was able to run the sample applications under wayland+baseview :)
But if it's not meant to be in scope, then this can be merged.

I was able to run the sample applications under wayland+baseview :)
But if it's not meant to be in scope, then this can be merged.

I checked with the devs and apparently baseview does not support wayland as I thought, so when you run the examples you're using xwayland. As such there is no way to get a wayland display pointer for the clipboard.
In which case I'm happy to merge this now if you are.


Layer optimization - Zoom levels

Work on once all layers are loaded.

@popkinj Can you provide an update on this one? (i.e. are you completing parts of this with what you're currently working on?)

I believe the logic for this is done.


Asset sidebar seems to have some local storage

The Chore
I think that when your position in the asset sidebar is saved.
So if I've been messing around in the sidebar, then done some trading, then go back to assets I open it already in withdrawals or in transfers etc.
I dont think this is ideal ... to me you would want to see the asset breakdown each time, I dont think we should be remembering this state.
Tasks

[ ]
[ ]

Additional details / background info

Will cover this as part of another ticket


Hot fix onlineRegistration issue

Decription
http://www.active.com/orangeville-on/water-sports/swimming-classes/cpr-recert-2030
The event can not be registration but the register now button shows.
Test Link
http://a3coreint15.dev.activenetwork.com/orangeville-on/water-sports/swimming-classes/cpr-recert-2030

Looks good to me.

Looks good now.


https://www.haskell.org/report/mono/2010 has not toc

while the non-mono variant has. Without a toc, this page is only half as useful.
Also, it is not clear what the sources for https://www.haskell.org/report are, and how that relates to https://www.haskell.org/onlinereport/haskell2010/

We're removing the former from the site, which should clear things up :-)


Add new archetypes.ImageEncoded with PNG and JPEG support

What

Part of https://github.com/rerun-io/rerun/issues/6844
Part of https://github.com/rerun-io/rerun/issues/3803

Has do-no-merge because of current merge-target.
PR train

Previous PR: https://github.com/rerun-io/rerun/pull/6882
Next PR: https://github.com/rerun-io/rerun/pull/6883

Coming in follow-up PRs:

Fix image picking, hovering, and visualization in spatial view
Switch to using ImageEncoded in all examples
Remove old code for storing JPEGs in tensors

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

I just realized there already is a class ImageEncoded in rerun_py/rerun_sdk/rerun/_image.py that I probably should remove…

@rerun-bot full-check

@rerun-bot full-check

@rerun-bot full-check

Fixes

#6520


Selection checkboxes can be added to the ranking, but not removed

When I add a selection checkbox column via the add column dialog, a selection column appears, but it cannot be deleted anymore (i.e. the option simply does not appear).  For rank columns (another support column), the removal works though.
To Reproduce

Open arbitrary ranking
Add selection checkboxes
Try to remove the column again --> remove is missing

Expected behavior
Removal is possible.
The remaining question is if only manually added selection checkboxes should be removable, or all. I would keep it simple and allow users to remove the initial selection checkboxes as well.

it was introduced by https://github.com/lineupjs/lineupjs/commit/c0a6170090927d2f4137362a5b63088b38e3def9


CodeCop: Rule AA0139 does not trigger for array elements

1. Describe the bug
The rule AA0139 (possible text overflow) does not trigger when the value that exceeds the length is an element of an array.
2. To Reproduce
See the code below:
    local procedure ParentFunction()
    var
        ValueOne: Code[20];
        ValueTwo: Code[40];
        Values: array [20] of Text;
    begin
        ChildFunction(ValueOne); // warning AA0139 is not issued - correct
        ChildFunction(ValueTwo); // warning AA0139 is issued - correct
        ChildFunction(Values[1]); // warning AA0139 is NOT issued - NOT correct
    end;

    local procedure ChildFunction(Code: Code[20])
    begin
    end;

3. Expected behavior
The rule should trigger if the array elements are of larger size
4. Actual behavior
The rule should trigger.
5. Versions:

AL Language: v10.0.673593
Visual Studio Code: 1.71.2

Thanks for reaching out. We’re focused on other things right now, but we’ve added this issue to our backlog. We’re planning to give the CodeCop engine and its rules an overhaul in a future major release. Thanks again!


Multitenancy or the ability to use multiple stores and not have model ids collide

Describe the feature
In my current use-case I use versioning on my models and I need to use it in such a way where different versions of models have the same ids and can co-exist side-by-side but with different values and relations.
One way to handle this would be by having different versions be on different stores so they can re-use the same models but exist in different databases.
I'm wondering if this is already possible.. is this something that repositories can achieve? And if not.. how much of a stretch would it be to add? Any tips on how I can get something similar to this working right now?
@CodeDredd I'd really appreciate if you could chime in and comment if this is already possible as this is a big problem that's currently on my desk and I have to act on it within a day or two.
Many thanks!
Additional information

[X] Would you be willing to help implement this feature?

Final checks

[X] Check existing discussions and issues.

@vesper8 Sorry for the late answer. I was moving to another location so i didn't had the time for my libaries.
But to get to your question. Yes it is possible. I thinik there is more than one solution to this.
Are you still interested in one since i am a bit late for the answer ?

Thanks for getting back. I understand you're very busy. I ended up finding another solution to my problem. I'll close this now. Cheers!


RHEL SBSA TF2 Backend Build

Goal: Incorporate SBSA builds/tests and extended the smoke tests for x86 and SBSA to include L0_sequence_batcher.
Server changes: https://github.com/triton-inference-server/server/pull/7595
PyTorch Backend changes: https://github.com/triton-inference-server/pytorch_backend/pull/139
TensorRT Backend changes: https://github.com/triton-inference-server/tensorrt_backend/pull/99

Okay, I believe I ended up finding a solution that's more straightforward. We now pass the results of the find command directly into docker cp so that we can copy the libs directly into the target folder. No messing around with files paths. No messing around with tar-ing. Let me know what you think.


MAINT: Delay pooch import error for scipy.datasets

Reference issue
See discussion from https://github.com/scipy/scipy/pull/15607#issuecomment-1215110575.
What does this implement/fix?
This will let users still do from scipy import * without raising an error, even though it is a bad practice. In case pooch is missing, an import error is only raised when a datasets method is called. Thanks @oscarbenjamin for suggesting the simple fix, this should not change anything else with datasets except for the error being postponed.
# Earlier without pooch installed
from scipy import datasets  # raises ImportError
# Now without pooch installed
from scipy import datasets # doesn't raise
datasets.face()  # but this will raise

cc @rgommers

@tylerjereddy Could you please create a datasets label as well? I guess only maintainers can create new labels. Thanks!

there you go

The refguide_check failure is unrelated.

Thanks @AnirudhDagar. I am not sure about the fix. I find it very strange to be able to import a module and cannot use anything from it. We would have other functions in the public API that would be fine, but here I am not so sure it makes sense to me.

Indeed we will have other functions in the public scipy.datasets API. For example, there will be a util method to clear the cache which will not depend on pooch, there will be a download all datasets method (which will depend on pooch), and certainly there will be more dataset methods in the future.
Another option is to raise an ImportWarning on import of the datasets module if pooch is unavailable and raise an import error only when a dataset function is called. This way, we are slightly more verbose, but still, postpone the error. What do you think of this?
This is a decision we need to make between not raising an import error on datasets module import (making from scipy import * still possible) vs raising on datasets module import if pooch is not found.


Create Event card to be used in events page

Figma link
TODO
Create a event card that will be used on the events page.
The description will change depending on the meet type.
Default Card view

Variants

Do we have to add APIs as well or it is just a front end?

Do we have to add APIs as well or it is just a front end?

This is just the design. API will come later with a different issue.


[ALLUXIO-2982] Remove .ms suffix from PropertyKey names

https://alluxio.atlassian.net/browse/ALLUXIO-2982

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16298/
Test FAILed.


ignore input during IME composition in VimNormalModeInputElement

Fixes #791.
Adapted from atom/autocomplete-plus's workaround for atom/atom#5414.
Specs adapted from atom/atom#8526 .

:+1:


Make initial size configurable and tie max size to it

@brushmate Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@brushmate Thank you for signing the Contributor License Agreement!

Thanks for your contribution. Let's move the alignment about resizing initialSize/resizing maxSize depending on which of these options were configured to ConnectionPoolConfiguration.Builder. We can change initialSize and maxSize types to Integer and pre-initialize both with null. In build() we can use the validation and determine the the right initialSize/maxSize.
In PoolingConnectionFactoryProvider, we should leave the type-adapting parsing as the generic type is intended for API-based configuration and URL-based parsing delivers all options as String.
In fact, I started working on this one in parallel so I suggest leaving out PoolingConnectionFactoryProvider from this PR.

I commited an update which contains only the intialSize/maxSize validation and defaults.
I was already thinking that there is a reason for the 'manual' option parsing but I could not figure out how connectionFactoryOptions.getRequiredValue(MAX_SIZE) could return anything else than an Integer.

Thanks a lot, that's merged and polished now.


tts node stoped working

[x] I have read and agree to the contributing guidelines.

Describe the bug
Text-to-Speech Node isn't working anymore, it was working a few days ago.
Elevenlabs as driver error:
NameError: name 'ElevenLabs' is not defined
OpenAI as driver error:
Error opening <_io.BytesIO object at 0x0000024D779E49A0>: File contains data in an unknown format.
To Reproduce
Use the example template.
Expected behavior
Preview audio.
Desktop (please complete the following information):

OS: Windows
Version 10

Additional context
Using the latest version of ComfyUI, all updated.

Hello @Bolsdip - can you share a screenshot of your Workflow? Thank you!

This looks like it's using the OpenAI text to speech instead of Eleven Labs.. do you have an OPENAI_API_KEY set in the griptape settings?

here's the eleven labs node:

Yes I have both of them setup in the settings.
Also, my workflow looked like that too with ElevenLabs as driver.
Did you do that just now?
It was working yesterday

Yes I tried it just before posting. Can you check your api key?

All setup ok and multiple credits availble.
I noticed if I use ElevenLabs as a driver, it uses up credits even though there's an error (NameError: name 'ElevenLabs' is not defined).
If I use OpenAI as driver it doesn't use up any credits just this error: "Error opening <_io.BytesIO object at 0x0000024D779E49A0>: File contains data in an unknown format.".
Also, I've tried reinstalling. Same errors.

Redownloaded ComfyUI and installed just Griptape, now it works.
Probably it was due to installing the other Text-to-speech nodes available, after I tested Griptape. Even though I've uninstalled them. I should have used different environments for each one.
Thanks for the help!

awesome, glad to hear it's working! :)


⚠ BeyondHD has degraded performance

In aeed605, BeyondHD ($BHD) experienced degraded performance:

HTTP code: 200
Response time: 1238 ms

Resolved: BeyondHD performance has improved in d51806b after 6 minutes.


Error Modifying HTML editor toolbar

Steps to replicate:

Navigate to Settings > HTML editor > HTML editor toolbar
Drag a button from the 'Available buttons' to 'Current toolbar'
An js error will be displayed:

toolbar.js:53 Uncaught TypeError: Cannot read property 'createDocumentFragment' of undefined
    at A (jquery.min.js:31)
    at Function.buildFragment (jquery.min.js:32)
    at s.fn.init.domManip (jquery.min.js:32)
    at s.fn.init.append (jquery.min.js:32)
    at s.fn.init.bH.fn.(:8081/vanilla/access/anonymous function) [as appendTo] (http://charliedesk:8081/vanilla/p/r/6.6.r54/com.equella.core/jquerycore/jquery.min.js:32:6601)
    at stopCallback (toolbar.js:53)
    at HTMLDivElement.stopAvailableCallback (toolbar.js:92)
    at b.(:8081/vanilla/access/anonymous function).(anonymous function)._trigger (http://charliedesk:8081/vanilla/p/r/6.6.r54/com.equella.core/jquerylib/jquery.ui.widget.min.js:11:5998)
    at b.(:8081/vanilla/access/anonymous function).(anonymous function)._trigger (http://charliedesk:8081/vanilla/p/r/6.6.r54/com.equella.core/jquerylib/jquery.ui.sortable.min.js:19:54)
    at b.(:8081/vanilla/access/anonymous function).(anonymous function)._trigger (http://charliedesk:8081/vanilla/p/r/6.6.r54/com.equella.core/jquerylib/jquery.ui.widget.min.js:11:891)```

@abidingotter I'm not sure what the "dynamicheighthack" was but even in 6.4 the code appeared to not be doing anything, can you confirm?

Dunno.  Does it make sure you can drag and drop onto a new line?
Or possibly it's an element with clear:both on it that always has to be last.


Add FieldMultivariateFunction and CalculusFieldMultivariateFunction

There are no field counterparts to MultivariateFunction, but it would be useful.

The vector and matrix versions should be added too.


Config node name conflict

Any chance you could rename the generically named config node to uhppoted-config
It causes a conflict with this package that has a Config node

Unfortunately I suspect this to be a braking change so should be a major version number bump
I have no idea if there is a way to migrate them in node-red
https://discourse.nodered.org/t/renaming-the-configuration-node-type-config-in-a-custom-node-best-practice/60041

Hmm - weird that it hasn't shown up before this! I'll have to look into it, but I suspect the short answer is going to be not easily. Unfortunately it would break a number of actively running systems that aren't mine so I'll have to figure out a migration path.
Am happy to create a separate branch with a renamed config node if you don't mind installing a development version locally?
Also - any idea why it conflicts with node-red-contrib-config ? That's typically just a local node created when somebody is experimenting.

node-red-contrib-config is another add-on package
I was developing on a flow on one system and found it a handy thing to install and use, unfortunately when it came time to migrate the flow to the production systems it conflicted with node-red-contrib-uhppoted which is already used in production for another flow
You can see here https://flows.nodered.org/node/node-red-contrib-config adds a node called config as apposed to a configuration node, most of which are named after what they are configuring

Yeah I'd be be happy to test a branch, and do understand its a change that would require a bump to say v1.0.0 for everyone else 😉

also just found this
https://flows.nodered.org/node/node-red-contrib-uhppoted/scorecard#
which shows the same conflict with a number of other packages

Great! Thanks for the info!
I should (hopefully) have a branch with the renamed config node ready in a day or two and then will get started on figuring out the options around migrating existing users/flows.

Hi,
Have posted a provisional fix to branch 11-config-node-name-conflict.
You'll have to install it locally and then update your flows to use the uhppoted-config node - the easiest I found is just to edit the flow JSON file and change the configuration node type directly from:
    {
        ...
        "type": "config",
        ...
    },

to
    {
        ...
        "type": "uhppoted-config",
       ...
    },

I think I originally assumed that NodeRED would namespace the nodes but it appears not and there are conflicts with other node names too.
Have created a discussion for the handful of other people that I'm aware of who are actively using this project, if you want to add any thoughts to that: RFC: prefixing all nodes with uhppoted- to avoid naming conflicts

Published v1.0.0 with the renamed nodes to NodeRED.
The scorecard isn't reporting any naming conflicts.

And (finally :-)) closing this ... feel free to reopen it if you need to.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67127

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/85845

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113390

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113556

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113490

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/114092

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/114408


feat(config): Add shardTestSuites config option

Currently the option shardTestFiles makes the tests run in parallel but by file, if we have tests that have some dependency on the previous one then this approach does not work.
shardTestSuites option will allow to run tests in different instances but grouped by suite.
The main goal of this feature is to reduce the time it takes to run tests on big applications that already have tests grouped by suites.
I am still testing this approach, but would be nice to have more feedback.
There is an example of how I am using this feature.
example to run your suites in two instances:
maxSessions: 2,
  multiCapabilities: [{
    'browserName': 'chrome',
    shardTestSuites: true,
    maxInstances: 2
  }],

Nice feature. I am also looking for it.

This is really interesting. Personally the need for having specs depend on one another feels like a smell, but I understand the pragmatic need for certain states to be maintained in large applications.
I made some minor stylistic notes but i'll defer judgement to people who know/care more about this feature than I.

@NickTomlin This is really handy for example for CRUD operations.
You may have a spec just for creating and testing all the exceptions and validations and then have another spec that test the Read view where you have to list and expect that previous inserted item to be listed to test search and edit on that same item.
Also you may have another spec to test creating but with another user type that my have more options than the previous user, it's good to be able to have more specs separated by context.
@sjelin Added test to ensure that it's running on same suite otherwise it would fail. :)

@juliemr Thanks for your feedback @ AngularConnect in London.
Can you give some feedback on this feature/approach? :)

Thanks for the test updates!  But you still need to add a test making sure that different suites are being run independently of each other (i.e. that your feature works).

Can you provide an example where you must have tests that depend on each other? It is usually a bad practice when this happens, and I don't think we should encourage this by adding a feature to allow this in the core library. However, you may prove me wrong with a good example.

@hankduan the example I have is from the company where I am currently working where the tests are taking in average 45min to run each build on a large AWS instance.
Some context:

We have our application separated by modules.
As good practice we try to separate the spec files by context/page
In average we try to test one PageObject on each spec file, so we end up with dependencies between files but is much easier to maintain and extend.

I don't want to get into specific details, but for example:
test/e2e/campaign
    - TestCreateItemFeature.js
    - TestListItemFeature.js
    - TestUpdateItemFeature.js
    - TestCreateInstanceOfItemFeature.js
    - TestEditInstanceOfItemFeature.js
    - TestPublishInstanceOfItemFeature.js

In this example:

Expect to be able to create an item.
Then expect that item to be available to test features of list, edit, filter and sort.
Then we expect to be able to create an instance of that item
Then we expect that instance to be available to test features of list, edit, filter, sort, publish.

It gets a bit more complicated, but I think this is a good example.
We also did some effort to enable to run each suite of tests (modules) independently, this would allow us to run them in parallel.
I've noticed you already support to run tests in x number of browser instances.
I thought this can be a native feature that Protractor could offer to run suites instead of running just individual test spec files.
This is a big feature for large projects and even smaller ones.
@sjelin about the tests:
I've created a really simple example where I navigate into one page on first spec file
And in the next spec file I am just checking if I am on that page
This prove that if the tests where being sharded by files each one would run on a separate browser instance and the second spec file would fail.
Ps: sorry for my delay on my reply.
Let me know if you need anything else.

I'll use your item tests as an example:
test/e2e/campaign
    - TestCreateItemFeature.js
    - TestListItemFeature.js
    - TestUpdateItemFeature.js

I would highly suggest reorganizing the tests in one of the following ways:
TestCreateItemFeature.js:
describe('create item', function() {
  it('creation test 1', testFunction1())
  it('creation test 2', testFunction2())
  it('creation test 3', testFunction3())
});

TestListItemFeature.js:
describe('list item', function() {
  beforeEach(function() {
    // create your items;
  });
  it('list test 1', testFunction1())
  it('list test 2', testFunction2())
  afterEach(function() {
    // delete your items;
  });
});

TestUpdateItemFeature.js:
describe('update item', function() {
  beforeEach(function() {
    // create your items;
  });
  it('update test 1', testFunction1())
  it('update test 2', testFunction2())
  afterEach(function() {
    // delete your items;
  });
});

So yes, this requires you to create and delete your items multiple times, but you will definitely run into issues if your tests start depending on each other. e.g.

once you set up your dependency (A->B->C), someone down the line could decide...C requires field 'x.foo' to be set, let's change that in 'A'; or B has a side effect that modifies field 'x.bar', so in C I should assert against the new value of 'bar'  etc, etc. Then later, your test C is impossible to read since it's require a state for items which was set up across multiples files as side effects. It's a huge rabbit hole to go down.
every time something is created, there's a purpose. i.e. you wouldn't have 100 items in your page when your test is to update one of the items. It makes debugging harder. Of course, you could decide to have a test where you're trying to select 1 item to update out of 100, but in this case your set up is intentional
and as a minor point, Jasmine/Protractor does not guarantee your test files to be run in any particular order, although it is in order at the moment

Lastly, by no means do I intend for you to have no dependency on different files. My point is for you to not have dependencies on different tests.
back to the example above, I could have a CreateItemPage.js page object.
var createItemPage = {
  goToPage: function () {
    browser.get('...')
  }
  createItem: function (...params) {
    $(...).sendKeys(param1);
    $(...).sendKeys(param2);
    $(...).sendKeys(param3);
    $(...).click();
  }
}

TestCreateItemFeature.js:
describe('create item', function() {
  it('creation test 1', function() {
    createItemPage.createItem('foo', 'bar', 34, 454);
    // assert...
  })
  it('creation test 2', testFunction2())
  it('creation test 3', testFunction3())
});

TestListItemFeature.js:
describe('list item', function() {
  beforeEach(function() {
    // create your items;
    createItemPage.createItem('item1', 'bar', 34, 454);
    createItemPage.createItem('item2', 'bar', 34, 34);
  });
  it('list test 1', testFunction1())
  it('list test 2', testFunction2())
  afterEach(function() {
    // delete your items;
  });
});

TestUpdateItemFeature.js:
describe('update item', function() {
  beforeEach(function() {
    // create your items;
    createItemPage.createItem('item1', 'bar', 34, 454);
    createItemPage.createItem('item2', 'bar', 34, 34);
  });
  it('update test 1', testFunction1())
  it('update test 2', testFunction2())
  afterEach(function() {
    // delete your items;
  });
});

@BernardoSilva You've got a great test for "Don't shard when I don't tell you to."  But you also need a test for "Do shard when do I tell you to."

Good feature:+1:

Hello, any updates on this?
@hankduan I also have a example why this would be great to have:
I'm working on E2E's for booking system where the user can actually buy tickets for rail and it's a complicated process because it's divided into steps where each step can be only accessed after previous one has been completed. To add a cherry on the top - on some steps we're calling external services that return data required for that step to be completed so using the shardFiles option is a no-no for me because it's simply not doable and this is why I hope this feature will be accepted. Other thing why it's not doable for me via shardFiles is when you start to book a ticket you get something like temporary reservation which will allow you to complete the process in certain amount of time, so I can't bypass that in any way and I'm forced to run tests in particular sequence.

I'm cleaning up stale PRs and features, and closing this one. Please open a new PR/issue if you feel it's still valid. Thanks!

@juliemr Please suggest when 'shardTestSuites' can be used. What changes will be required in spec file since I want to execute individual it blocks in parallel? Thanks in advance!


Pull Request for Maven Assignment.

I am submitting a pull request for the Maven/ Gradle assignment. For your kind consideration.

Nice work.


docs: Fix typo in theming example

It looks like typo was made because of naming convention used for pre-built theme (pink-bluegray)


spec is wrong for event_match.pattern push rule condition

https://matrix.org/docs/spec/client_server/r0.6.1#conditions says:

Patterns with no special glob characters should be treated as having asterisks prepended and appended when testing the condition.

This sounds like a disasterous idea (since it would mean rules with a condition of type == 'm.room.message' would also match events of type org.example.m.room.message). Fortunately it appears to be untrue.
(that said: synapse does implement some magic when the match key is content.body, where it searches for the search term anywhere in the event body, but also only matches complete words)

(the relevant code starts here: https://github.com/matrix-org/synapse/blob/v1.15.0/synapse/push/push_rule_evaluator.py#L132)

fixed by #3690


Develop Research Plan for new Receiver Dashboard

User story
As a ReportStream designer/researcher after the launch of the new Receiver Dashboard, I want to develop a plan for gathering feedback from users.
Background & context
Open questions

Does the new feature launch meet the need of our receivers to "see who is sending me data and how often?"
What do users like and dislike about the new feature?
(Internally) Is it important that we add this feature to the Universal Pipeline?

Working links
Acceptance criteria

[x] Research plan created and reviewed with design lead

Plan reviewed and a meeting is scheduled for handoff


PSS compliance

Towards https://github.com/giantswarm/roadmap/issues/2447

update security context for PSS compliance
update CHANGELOG

Checklist

[x] Update changelog in CHANGELOG.md.

Tested in gauss.


Korean page is linked to an invalid hyperlink.

In the [Create your first meta]paragraph, [Login to the account console] is linked to an invalid hyperlink.
https://docs.microsoft.com/ko-kr/azure/databricks/data-governance/unity-catalog/get-started#create-your-first-metastore

The English page's hyperlink is correct.
English page's hyperlink : https://accounts.azuredatabricks.net/login/
Korean page's hyperlink : https://accounts.cloud.databricks.com/
Please fix the wrong hyperlink path to the correct hyperlink path.

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

ID: 6e7dd177-0bec-3b6e-ade5-888c0c1f661a
Version Independent ID: 6e7dd177-0bec-3b6e-ade5-888c0c1f661a
Content: Get started using Unity Catalog - Azure Databricks
Content Source: databricks/data-governance/unity-catalog/get-started.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@hyungjin-han  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to address your issue and apologize for the delayed response. We are closing this issue, but if you feel that it's still a concern, please let us know directly at<EMAIL_ADDRESS>#please-close

The link seems up to date, so it may have been fixed already.
#please-close


Loosing connection all the time

Hi
I have installed this add on 3 days ago.
First of all it worked
Immediately as i Have  placed the ip address of the 4 heat module of my stove.
i got immediately all the readings
However, it only works randomly as the connection “comes and goes”
This is the image of “right now”:

Should i place a fixed ip address for the 4heat module in stove in the router ?
I have everything with the latest software
4heat module
Home assistant
Integration of 4heat
thanks in advance !!!
👌🙌

Hi,
Any news ?

Same problem here, due to this, my graphs look like this:

@ruialmeidinha you can try my fork.
I've set higher timeouts and changed error handling:

if the socket fails with an error that's not timeout, it will raise an exception and HASS will set values as unavailable
if the socket fails with timeout, it will send last valid values (sometimes even those 60 seconds are not enough... I guess it loves to sleep)

Sometimes it still timeouts, but for now less than 10 times per day, hence the last valid value logic:

You can just replace const.py and coordinator.py using VS Code addon in custom_components/4heat. These changes should eventually get overwritten once new "official" version comes out, I'll let it run for some more time and then create PR here - maybe I'll find some more things in that time.

Hi
@leoshusar
Many thanks for taking a look and trying to help
I have copied both const.py and coordinator.py  files from your fork, to my custom componets folder.
The behaviour is exactly the same....
Did I do what was expected, or did I do something wrong ?
Thanks in advance,

No problem!
You have to replace existing files and then restart Home Assistant so it actually loads them. Did you do this?

Yes, I did !

Hmm, what is in your logs?

4HEAT - Salamandra Pellets Combustion power changed to 120
14:39:36 - 13 minutes ago
4HEAT - Salamandra Pellets Combustion power changed to 7
14:33:37 - 19 minutes ago
4HEAT - Salamandra Pellets State changed to Standby
14:33:37 - 19 minutes ago
4HEAT - Salamandra Pellets Combustion power changed to 9
14:32:36 - 20 minutes ago
4HEAT - Salamandra Pellets State changed to Modulation
14:32:36 - 20 minutes ago
4HEAT - Salamandra Pellets Error turned off
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets State turned on
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20375 changed to 65
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20374 changed to 20
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20179 changed to 75
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20178 changed to 40
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20366 changed to 75
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20365 changed to 60
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20570 changed to 1
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20369 changed to 6
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20225 changed to 55
14:27:58 - 25 minutes ago
4HEAT - Salamandra Pellets UN 20230 changed to 65
14:27:58 - 25 minutes ago

Can you please explain whatare all these sensors eg. UN 20118, UN 20119, etc ?
Could they be the radiators from my pellets heater ?

In my logs is only this when it timeouts:

and that's my error message I added, this one doesn't set values to unavailable. Do you have somewhere in logs this exact message or something different?
There might be for example socket error / failed to connect or unexpected error, those are also mine.
Regarding those sensors - nobody knows yet. I decompiled the Android APK and they are not mentioned there too, I was able to find only 3:

30040 - Temperatura Ritorno (water returning to stove temperature?)
30044 - Temperatura Esterna (translator says "external")
40007 - Inputs

I think the best would be to check on the stove controller what changes to what value and match the value in HA, I'm planning to do that for mine.
But I also think some stove models can have some sensors missing, because my module doesn't report 30040 and 30044 at all.