Panic in internal.(*ExecCommand).Start when -c flag is not specified

Hi!
I've been testing this tool but ran into an issue. When I run the tool I can navigate to a task that has ECS exec enabled, but when I select the container to exec into the program panics like this:
? Select a task: panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1553488]

goroutine 6 [running]:
github.com/tedsmitt/ecsgo/internal.(*ExecCommand).executeInput(0xc00031caa0)
        github.com/tedsmitt/ecsgo/internal/exec.go:264 +0x88
github.com/tedsmitt/ecsgo/internal.(*ExecCommand).Start.func1()
        github.com/tedsmitt/ecsgo/internal/exec.go:72 +0x1e5
created by github.com/tedsmitt/ecsgo/internal.(*ExecCommand).Start
        github.com/tedsmitt/ecsgo/internal/exec.go:58 +0xee

I'm able to work around this by manually specifying the shell to run like ecsgo -c /bin/sh, which according to the README should be the default command.

Hey @j-boivie thanks for raising this! I'm currently on vacation so will look at this when I get back next week 😄 In the meantime could you provide some details to help troubleshoot such as:

Number of containers in the task
Container names
Container image details

Thanks again!

Hi,
Sorry for the late response, from my testing I've noticed that this happens on every task I connect to, no matter names, number of containers in the task etc. I've tested this across two different AWS accounts as well.
The only thing I can think of is that all of the ECS resources typically have hyphens in the name, and that they all run some variant of debian:-slim or python:-slim as base image.
Another thing I noticed is that the tool doesn't return a list of all services on the cluster, although I can see all tasks when selecting *.  I'm only ever getting a list of 10 services, so I'm guessing that the reason is that this call here doesn't handle a paginated response from the ECS api: https://github.com/tedsmitt/ecsgo/blob/95178ae50b5d102c5ffea4eb3f5723c6fad40353/internal/exec.go#L123-L126
But I can raise another issue for that if needed.

@j-boivie No problem! Thanks for the additional info.
Based on the error message it looks like this is the offending line:
https://github.com/tedsmitt/ecsgo/blob/95178ae50b5d102c5ffea4eb3f5723c6fad40353/internal/exec.go#L264
Would I be right in assuming these tasks are running on an EC2-backed ECS cluster? I suspect that the PlatformFamily value may only be available in Fargate tasks. I have just tested this and I can recreate the problem. I'm writing up a fix now.
RE: Pagination you're absolutely right, I've not implemented this yet embarrassingly, it has been on my todo for too long 😓 If you could raise a new issue for this that'd be great!

@j-boivie No problem! Thanks for the additional info.
Based on the error message it looks like this is the offending line:
https://github.com/tedsmitt/ecsgo/blob/95178ae50b5d102c5ffea4eb3f5723c6fad40353/internal/exec.go#L264
Would I be right in assuming these tasks are running on an EC2-backed ECS cluster? I suspect that the PlatformFamily value may only be available by default in Fargate tasks, and might have to manually be specified for tasks with EC2 launch type. I have just tested this and I can recreate the problem. I'm writing up a fix now.

You're absolutely right, somehow I had forgotten that Fargate was a thing... 😅, but that seems reasonable.

RE: Pagination you're absolutely right, I've not implemented this yet embarrassingly, it has been on my todo for too long 😓 If you could raise a new issue for this that'd be great!

Roger that, will create a new issue 👍

@j-boivie I've just pushed the fix for this in release 0.4.4, can you let me know if all looks good on your side? 😁

All good here, thanks a lot for the fix! 🙇


[FEATURE] Proposal - Deep Learning Model Uploading and Inference

What / Why
What are we building?
The ML-Commons plugin allows user to upload deep learning models and use them to make inference.
Why are we building it?
In many domains like NLP, computer vision etc. the deep learning algorithms overwhelm the traditional machine learning algorithms. For OpenSearch customers who are planning to use machine leaning algorithms or using some traditional machine learning algorithms for their bussiness, deep learning is definitely a good way to improve their systems.
How do we know?
What matters most to OpenSearch?
Bring deep learning models into OpenSearch. Deep learning is increasingly affecting our lives. More and more customers want to use deep learning technology to improve their systems. This feature brings an opportunity for customers to apply deep learning models in OpenSearch for their business.
What does the customer experience look like?

Train the model through a deep learning framework, like Pytorch.
Save the model to TorchScript.
Upload the model through ML-Commons plugin API.
Run the predict API provided by ML-Commons plugin to get the result.

High-level user stories:

As a forecasting user, I want to apply deep learning algorithm like deepAR so that I can improve the forecasting accuracy for my business.
As a NLP user, I want to apply deep learning algorithms so that I can leverage the state-of-the-art NLP technologies to improve my systems.

What are the risks and assumptions?
The format of model
There are pretty many deep learning frameworks to train models, like PyTroch, TensorFlow, MXNet etc. They are not compatible for the model’s format. We could start with TorchScript and ONNX as PyTorch is a very popular deep learning framework and ONNX is a standard format across various deep learning frameworks.
The computation cost
We have the limitation on the size of model. Supporting distributed inference or not need to be considered.
Dedicated ML node with GPU
If no dedicated node, we should have more restrict limitation on resources for the models.
ARM support
Support like AWS Graviton.

You could look at ONNX Runtime for deploying ONNX models. It has a Java API and is used in production in Java in a number of companies (and also in other search engines). It's designed specifically for inference, and is frequently faster than pytorch. There are a number of configuration options for constraining the execution environment it runs in, and it can exploit GPUs if they are available. We have a wrapper around it in Tribuo so you could maintain uniformity in the interfaces if that's helpful, though going through Tribuo's interfaces would add some overhead for dense data vs using it directly from Java.
(Full disclosure: I wrote the initial version of the ONNX Runtime Java API and now maintain it in the ONNX Runtime project)

Thanks Adam for your comments. You are right, actually we already put ONNXRuntime on our plan and we are still evaluating it.

Ok. Let me know if there are issues with the way the Java bits work, we can fix them (though ONNX Runtime is on a quarterly release cycle so new features will have to wait till the next release). For example we've not added support for writing outputs to preallocated user buffers yet and that may be relevant for high throughput applications.

I've encountered errors while converting PyTorch models to ONNX in the past due to non-existent parallels in ONNX for certain PyTorch functions/operations. I think this should be taken into consideration too.
Also, in my experience, a typical ML / DL pipeline looked like this :
data source -> data pipeline -> write to *opensearch* -> fetch from *opensearch*, at a later date  -> feature engineering -> hit API for inference -> write results to *opensearch*
We can skip the first 3 steps since they are not entirely related to DL / ML but the remaining steps can be implemented in the ml-commons.
I think the easiest and most feasible first feature would be to add functionality to select certain columns to send to an external API and then write whatever prediction is returned to a column in an index. This will alleviate the necessity for an external program to fetch data from opensearch and then send it to the inference server and then write the results back into opensearch, which I think is a great starting point while also letting the developers some time to familiarize themselves with the internals of opensearch before jumping into more complex tasks and features.
To reduce the complexity of the above, we can start with basic numeric columns without any preprocessing, assuming that any such steps as standardization or scaling will be done in the inference API itself.
Sorry for any confusion.

@jngz-es thanks for putting this proposal together. I'm very excited about this work. I have some questions/comments:

Are we planning to extend the REST API to support uploading without cluster restarts?
What are the different methods we want to expose?
If we are doing the REST API, I'd suggest we explore building a UI in dashboards to facilitate the upload/management.
How does this fit in with something like using Hugging Face's Pytorch Transformers?

@kgcreative would love your thoughts ^^^

Thanks for your comments @elfisher . Add my thoughts here.

Are we planning to extend the REST API to support uploading without cluster restarts?
What are the different methods we want to expose?

Yes. We plan to build several new APIs to support custom model:

User can use upload model API to upload their own model to OpenSearch (will split the model into smaller chunks and save to ML model index).
Then call load model API to load model into memory.
Once model loaded, they can call some inference API.
If model no longer needed, user can call unload model API to remove model from memory.

If we are doing the REST API, I'd suggest we explore building a UI in dashboards to facilitate the upload/management.

That's a good suggestion. And we do plan to build some UI to support model management/uploading. But considering our resources, we may plan tasks in phases. How about we prioritize the REST API first, then UI if no enough resources to work in parallel?

How does this fit in with something like using Hugging Face's Pytorch Transformers?

Good point. Huggingface model is considered. If we don't have enough resources, we plan to support some Huggingface model first like some NLP models. We can extend the scope to support more models later. What do you think?

Is there a reason for this to be implemented in Java?
Why not dedicate a node for inference and have it implemented in Python. It can be an internal node so users call the OpenSearch APIs through master nodes which delegate requests to inference nodes just like search requests are delegated to data nodes. Having an inference python node will broaden the spectrum of ML/DL capabilities to include.

I saw this is moved to 2.4 on the roadmap. I'm updating the label accordingly and adding the roadmap label

Feature Review check-in notes:
The team will work with the docs team to create the corresponding doc issue, and document the type of model that will be supported. Additionally, feedback was given to enable GPU acceleration for deep learning. The UX action item is to work on user-flow requirements in parallel while the API work is occurring.

just to check, have you guy laid out the possibility of using something like https://www.deepdetect.com/ ?
it has a few tutorial on how to integrate deep detect outputs directly to elastic.

just to check, have you guy laid out the possibility of using something like https://www.deepdetect.com/ ? it has a few tutorial on how to integrate deep detect outputs directly to elastic.

@diegodorgam Not familiar with deepdetect. Can you share the tutorial link? If possible, that will best if you can summarize how deep detect integrate with elastic.

Is there a reason for this to be implemented in Java?
Why not dedicate a node for inference and have it implemented in Python. It can be an internal node so users call the OpenSearch APIs through master nodes which delegate requests to inference nodes just like search requests are delegated to data nodes. Having an inference python node will broaden the spectrum of ML/DL capabilities to include.

@asfoorial Very sorry that missed your comment, good suggestion. We thought about this option. We find it challenging to  package all these python dependencies and build roburst/safe/scalable solution for all platforms. Maybe it's not so hard to do such customization work for one user manually. But seems not so easy to build easy solution that user can just install and run just like what OpenSearch does now. But welcome any detailed solution for this option.

@ylwu-amzn have you considered embedding Python executing within JVM using https://github.com/ninia/jep?

@ylwu-amzn have you considered embedding Python executing within JVM using https://github.com/ninia/jep?

Yes, @jngz-es did some research on jep before, it has some compatibility issue with some CPython extensions which may cause JVM crash. So we didn't choose jep.

Yes, just like @ylwu-amzn mentioned, we did some testing on jep. From our side, it brought some unavailability issues.

I think the focus should be directed towards universal runtimes like ONNX which support a large range of other libraries such as TensorFlow and PyTorch. This also enables indirect support for other derivative libraries like HuggingFace Transformers without explicitly writing code for them.
With that being said, sorry I am out of the loop but are there any discussions / progress on the Feature Engineering aspect of Machine Learning? Since ML models expect the data to be in a certain format, there should be in-built transformations that help to transform the data (tokenization, tokens to embeddings, standardization, custom functions?) suitable for the selected model. The case for custom development of select libraries can be made here, such as HuggingFace Transformers, that provide "processors" or "tokenizers" that help in transformation of input into the desired format.
I think I am reiterating some of these from the RFC in #123 (changed my github handle, same guy).

hi, @ashim-mahara , thanks a lot for your suggestion.
We have released model serving framework as experimental feature in 2.4, check this doc https://opensearch.org/docs/latest/ml-commons-plugin/model-serving-framework/
In 2.4, we support text embedding model and we support the standard huggingface tokenizer. You can find example model in our code(link). Unzip the example model, you can find it contains model torchscript file and tokenzier.json file. The tokenizer.json file is from Huggingface, which defines tokenization logic.
Will the tokenzier.json file meet your requirements? Feel free to share your use cases and add your suggestion here

Can the ML Commons Plugin be used for Getting Better Search Results or other tasks only ?

@hamzashabbir11 you can use the neural-search plugin, which internally uses ML Common models, to get better search results

Okay, Thanks for your answer @asfoorial . I am a beginner in OpenSearch. I am using it to get better search results for an E-commerce app.  How can I implement neural search and are there any resources you can share?

@hamzashabbir11 it is not very straightforward, but you can start here https://opensearch.org/docs/latest/neural-search-plugin/index/

hi, all, thanks for your valuable feedback and suggestions.
From 2.5, ml-commons supports running model on GPU, refer to this doc https://opensearch.org/docs/latest/ml-commons-plugin/gpu-acceleration/ or https://github.com/opensearch-project/ml-commons/blob/2.x/docs/model_serving_framework/GPU_support.md
From 2.5, we support ONNX model too. You can find text embedding examples (by 2.5, we only support text embedding models) on this doc https://github.com/opensearch-project/ml-commons/blob/2.x/docs/model_serving_framework/text_embedding_model_examples.md
After model loaded and running in model serving framework, you can use neural search plugin to do semantic search, refer to https://opensearch.org/docs/latest/neural-search-plugin/index/
Note: the model serving framework and neural search still experimental now. Welcome to try and provide your feedback. Let's build a better product together!

It seems that the future version of OpenSearch plans to provide the function of MLOps. Does it right?
Now CRUD for the model has been implemented. However, there are still many problems in model management:

Supporting for multiple model file formats: model from TensorFlow, paddle paddle
Supporting different forms of model input: image, video, graph (custom JSON object), and 3D point cloud

@hexbo Thanks for your suggestions, really great points!
We do have plan to support MLOps. Is it something valuable to you? Appreciate if you can share more details and your suggestions for this. Like what function you need, what pain point do you have now etc.
For supporting more model formats and inputs suggestion, yes, we will support more. Do you have some priority list for these? Like which model format/input type we should support first to support your use case?

@ylwu-amzn Yeah, I always use Tensorflow to develop the DL model. At present, the market share of TensorFlow is also high, I hope that OpenSearch can support the model file of TensorFlow in the recent version update.

Yeah，tf2onnx can do this. But tf2onnx can't automatically convert my model.


Spike - Initial indexer initialization plugin design

Description
As part of the new Data Persistence Model to be implemented across Wazuh, we want to develop a plugin for the Wazuh Indexer to ensure that all of its requirements are ready during its initialization. The initialization process would consist of these currently identified requirements (these may change):

Creating the stateless stream indices and their index templates (mappings and settings).
Creating the stateful indices and their index templates (mappings and settings).
Creating the agent index and its index template (mappings and settings).
All necessary users and their minimum permissions (RBAC).
Rollover + alias configuration for stream indices.

On this spike, we will design, build and test a PoC of this plugin.
The goal of this issue is to collect the knowledge base to scaffold a Wazuh Indexer plugin for development, interact with its life cycle, automatically test its features and explore these capabilities:

create indices and index templates (mappings)
communicate and interact with other plugins, for example, Index Management

Functional requirements

The plugin's uses OpenSearch's lifecycle to initialize the features mentioned above.
The plugin includes error handling to notify the users of errors in an understandable manner.
The Wazuh Indexer will not allow indexing until it's being initialized correctly.

Implementation restrictions

We will use Java as the programming language.
The initialization plugin will be included in the Wazuh Indexer packages by default.

Plan

[x] https://github.com/wazuh/wazuh-indexer-plugins/issues/2
[x] https://github.com/wazuh/wazuh-indexer-plugins/issues/3
[x] https://github.com/wazuh/wazuh-indexer/issues/265
[ ] https://github.com/wazuh/wazuh-indexer/issues/270

We'll continue defining the remaining ECS compliant templates as part of the MVP stage.


Corrupt user object after logging in and out (using Core Data)

When I was developing an application using your library, I stumbled upon a problem where the object representing the current logged in user became corrupt. I noticed that after logging out and then logging in again, the relations to the currently logged in user suddenly disappeared.
When I was trying to solve the problem I saw that it also appeared in your todos example project. Here is a reproduction of the problem using your own todos app:

Go to meteor-ios-todos.meteor.com and make sure you have an account on the website
Run the todos example project in the iOS simulator and do the following steps inside the running iOS app
Log in to your account

Create a new list and open it
Mark your list as private
Add one or more todo items
Go back to the overview and log out
Log in again to the same account
Open your newly created private list
Notice that your todo item(s) from step 6 are gone

Can you help me solve this problem?

Thanks for reporting this. I looked into it, and it seems this is due to the way inverse relationships are handled in METIncrementalStore. When a referenced object is deleted and added again (as happens when you log out and back in), a referencing object that contains a relationship field (e.g. List.userId or Todo.listId) is not marked as updated. I'll try to get a fix in for this tomorrow.


Elasticsearch 2.3.3 support

I think the Elastic people just wait until you update knapsack, and then deploy a new point release. :)
Please add support for the 2.3.3 release when you get a chance.
Thanks!

I just pushed out knapsack plugin release <IP_ADDRESS> for Elasticsearch 2.3.3

Ubuntu 14.04.4 LTS 64-bit
$ ./bin/plugin install http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/<IP_ADDRESS>/elasticsearch-knapsack-<IP_ADDRESS>-plugin.zip
-> Installing from http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/<IP_ADDRESS>/elasticsearch-knapsack-<IP_ADDRESS>-plugin.zip...
Trying http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/<IP_ADDRESS>/elasticsearch-knapsack-<IP_ADDRESS>-plugin.zip ...
Downloading ..............................................................................................................................................................DONE
Verifying http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/<IP_ADDRESS>/elasticsearch-knapsack-<IP_ADDRESS>-plugin.zip checksums if available ...
Downloading .DONE
ERROR: the version needs to contain major, minor and revision, and optionally the build: null

Thanks, The uploaded archive had a broken plugin-descriptor.properties file. I uploaded a fixed plugin zip under the same URL  http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-knapsack/<IP_ADDRESS>/elasticsearch-knapsack-<IP_ADDRESS>-plugin.zip


Add Dogma to help keep code format consistent.

Configured with a set of rules that is a little more lenient so as to be compatible with some existing code adapted from Ecto and Postgrex.

Coverage remained the same at 94.118% when pulling 0d2e6914feffd7c3b259de037d7075aea34b410f on dogma into 2e2a051e50c532c77bce64136025c43d9114da0f on master.

Coverage remained the same at 94.118% when pulling 0a890cd7eb73b1c28bda1d621f4ab090a5ddbeb1 on dogma into 2e2a051e50c532c77bce64136025c43d9114da0f on master.

Coverage remained the same at 94.118% when pulling 0a890cd7eb73b1c28bda1d621f4ab090a5ddbeb1 on dogma into 2e2a051e50c532c77bce64136025c43d9114da0f on master.

Coverage remained the same at 94.118% when pulling 0a890cd7eb73b1c28bda1d621f4ab090a5ddbeb1 on dogma into 2e2a051e50c532c77bce64136025c43d9114da0f on master.


Incompatible with Python>=3.10 (AttributeError: module 'collections' has no attribute 'Mapping')

Issue: error thrown on module import
>>> import frozendict
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/crypt0xyc/projects/starknet-arb/.venv/lib/python3.10/site-packages/frozendict/__init__.py", line 16, in <module>
    class frozendict(collections.Mapping):
AttributeError: module 'collections' has no attribute 'Mapping'

Proposed solution for Python 3.10 compatibility
replace collections.Mapping with collections.abc.Mapping

Hello @crypt0xyc . Project has moved here: https://github.com/Marco-Sulla/python-frozendict


Add auto rejoin functionality to party plugin

Add the option for players to opt into automatically rejoining their previous party upon login. This is useful for groups of friends that frequently play together, and don't want to remember to rejoin their party every time they launch the game.
Summary of changes:

Adds a config option for the user to opt into automatically rejoining their previous party.
Adds a hidden config option to track if automatic party rejoining should be skipped. Upon the user manually leaving the party through the leave button, this flag is set to true. Upon joining a party again, this flag is set back to false.
Adds checks on the onGameStateChanged event to check 1. If the game state is LOGGED_IN 2. If the player is not currently in a party 3. If the player has a previous party ID 4. If the player has opted into automatically rejoining their previous party 5. If automatically rejoining the previous party has not been disabled due to the player manually leaving the party.

If all checks are successful, a call is made to party.changeParty() with the user's previous party ID.

https://github.com/runelite/runelite/pull/15176#issuecomment-1161837688


[publisher] Resources view's rate limiting policies are not ordered properly.

Limiting policies are not not sorted in proper manner and they appear as a random ordering style.

related issue https://github.com/wso2/product-apim/issues/6166


Document the Lines format.

Describe what needs to be documented.
I couldn't find any documentation on the Lines format. It looks like a simple text format for describing lines, which would be generally useful.
Is the documentation missing?
Yes, the documentation is missing. We should add a "Getting Data into VisIt" manual into our Sphinx documentation. We could start with some of the high level content from the existing ancient manual and then add something for Lines. I personally would like to have it start with easy-to-use examples and only get into the more complex examples using Silo or writing a plugin to read your own data later. We need to have the common stuff first. Curve, PlainText and text VTK files would probably be next. Visit_writer would be next.

It seems like there are two types of information that we want documented here.

File format basics for reading data into VisIt.
Further developing VisIt to handle more types of data.

It seems like the second case belongs in the Developer Manual (?), but where do we put the first case? Or is this proposed "Getting data into VisIt" section it's own thing that exists outside of the GUI, CLI, and Developer manuals?

related to #4170


[FileDropper] Designed file dropper

Context
According to Focus philosophy, the filedropper component need to be designed. I made my own version for the project (with a text that can be modified)
Here the result :

Actual behaviour
No real design is proposed.
Expected behaviour
Some css to design it !
Versions
"focus-components": "^0.7.10-rc4",
"focus-core": "^0.12.1-rc3",
"focus-file": "^0.1.2",
Tips
Here the code that i made to have the result :
.upload {
  background: white url("../img/upload.png") no-repeat;
  background-position: center;
  opacity: 0.2;
  text-align: center;

  .dropzone {
    background: inherit;
    border: none;
  }
  [data-focus=file-upload] [data-focus=file-upload-dropzone] {
    border-radius: 10px;
    cursor: pointer;
  }
}

.upload:after {
  color: black; //#959595;
  font-size: 20px;
  position:relative;
  bottom: 30px;
  text-transform: uppercase;
  content: "Cliquez pour selectionner un fichier ou deposez le ici";
  pointer-events: none;
  margin-left: 10px;
  margin-right: 10px;
}

Limits :
The text given in css cannot be translate, doesn't handle accents.
The function "pointer-events: none;" that allows to click through the text isn't handled in IE
The background opacity that colors my stuff in grey also affect the picture of loaded file.
I think the text parameter should be given through params to the file loader to solve a lot of problems.

nice :+1:

@Pandakls Can you put this issue on the focus-file project thanks!

https://github.com/KleeGroup/focus-file/issues/16


Download binaries for all platforms and architectures

Hi there! First of all, thank you for this implementation.
I am planning to use it in an app built with Electron, so during the build process, all the Vosk binaries are needed, as the builds are made for different OSs. Currently, to handle this, we use the yarn flag --ignore-platform, which downloads all available binaries for libraries that have this type of differentiation.
I have modified the postinstall script to detect if this flag is used and to download all binaries accordingly. If the flag is not detected, the behavior remains the same as before, with only the binaries for the current platform and architecture being downloaded.
I believe these changes will make the build process more versatile and convenient, especially for projects that need to support multiple platforms. Please review the modifications, and let me know if there are any adjustments or improvements you would suggest. I am happy to make any necessary changes.
Thank you for considering this contribution!

Thank you, bro.


prisma deploy Unknown command "deploy"

I followed up procedure in readme.
but prisma deploy failed.

I did
npm install -g prisma
And, run the following commands:
cd react-apollo/server yarn install prisma deploy

I catch that its reason is prisma version.
update prisma version to 2.22.0
server\package.json
{  ...   "dependencies": {     "@prisma/client": "^2.22.0",    ...   },   "devDependencies": {     "@prisma/cli": "^2.22.0",     ...   } }
And then remove directory server\prisma\migrations
And type prisma migration deploy on cmd


INT B-20706 I-13246 remove super admin update ability

Agility ticket
Issue ticket
Summary
Removing an admin's ability to make other admin's Super Admins because it's easier/safer if we manually update the database instead?
How to test

Access admin
Confirm you can no longer make other admins super admins

Screenshots

508

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 3a0ea3d9a4e69f6def2845b13eb4fe9414aa540b

@danieljordan-caci  Should a super admin still be able to make an admin super or not? Or this is only granted from CACI Tier 3?

@danieljordan-caci Should a super admin still be able to make an admin super or not? Or this is only granted from CACI Tier 3?

They should not be able to - reason for this PR is removing that capability. I got it wrong in the first PR. They are deciding that we will need to manually update the DB to make other admins super admins.


AKS clusters using Azure CNI should use Azure CNI Overlay

Rule request
Suggested rule change
AKS clusters using Azure CNI should use Azure CNI Overlay networking which currently is in preview. Azure CNI Overlay currently has some limitations that must be taken in consideration.
With Azure CNI Overlay, the cluster nodes are deployed into an Azure Virtual Network subnet, whereas pods are assigned IP addresses from a private CIDR logically different from the VNet hosting the nodes. Pod and node traffic within the cluster use an overlay network, and Network Address Translation (via the node's IP address) is used to reach resources outside the cluster. This solution saves a significant amount of VNet IP addresses and enables you to seamlessly scale your cluster to very large sizes. An added advantage is that the private CIDR can be reused in different AKS clusters, truly extending the IP space available for containerized applications in AKS.
Applies to the following
The rule applies to the following:

Resource type: [Microsoft.ContainerService/managedClusters]

Additional context
Azure CNI Overlay preview
Azure CNI Overlay
Template reference

@bengeset96 Nice, we just need to understand how this aligns to the Well-Architected Framework? What pillar do you feel this falls into.
@ms-sambell What are your thoughts?

@BernieWhite
Performance efficiency pillar. I think many of the topics supports overlay, particularly Consider scalability and Plan for capacity.
Disadanvatages with Azure CNI Overlay so far as I know are following:

Does not work well with virtual nodes.
When you have resources outside the cluster that needs to reach pods directly.
Application Gateway as an ingress controller is not supported.
Windows not supported.

Might be "sketchy" to implement this rule, but I also feel it could add some value for those that want to run explicitly with Preview baseline.
Would be great to get feedback from @ms-sambell as well.

@ms-sambell
Any toughts that you would like to share?

Hey @bengeset96  - My notifications are muted so I missed this (will fix it).
So the new CNI overlay network is great but there are some limitations right now. So I don't think we can create a generic rule to recommend all customers use it. I believe one of the limitations is the AppGateway add-on breaks.
There's a good story around writing a recommendation for customers using Kubernetes to review it though, so maybe that's an awareness rule? or a rule that assesses if the app-gateway add-on isn't enabled to recommend it.

Yes, awareness would be fine for this. Agreed upon this, I'll try to create something and we'll see if it fits.

Hey @ms-sambell
I've started on looking on this and I can see that there are two ways to deploy AGIC for an AKS cluster. With the trough AKS approach as an add-on it seems that I can just look out for properties.addonProfiles.ingressApplicationGateway.enabled -eq $true, but for the Helm option I'm really struggling to find out what to look for. Any idea?


Actions visible in REPL and history

Add ability to have commands and action output to REPL and history
Examples:

install/uninstall/load/unload packages
source files
change working directory via dropdown or project menu

this can be an option i.e. silent/visible since some may prefer less output to REPL

When using the setwd in solution explorer (right click or ctrl+alt+h), the operation does not print to history or REPL

Debugger stepping is also not reflected, unlike RS.

Depends on VS Update 3


Make registry authentication default for 401 Authorized.

From https://github.com/GoogleCloudPlatform/minikube-build-tools-for-java/issues/96
This is necessary for registries like Docker Hub.
How: Pass authorization credentials as a provider into the HTTP request factory.

Fixed in https://github.com/GoogleContainerTools/jib/pull/437


Consider supporting dynamic run steps

In the run mode, we make some restrictions such as reps requiring a pure argument for number of repetitions, while we could be more permissive since these are just tests that aren't translated to Apalache at all. We should consider the pros and cons of support this.

Thank you for looking into this!
For me as a user, I am happy to use the "scheduler" solution Igor suggested.
However, I do think that solution is more work in simple cases like just iterating over a list with reps,
and it might be nice to have this. However, I think it mostly depends on how much implementation work it is,
and I personally wouldn't prioritize this highly on my feature wishlist.

since these are just tests that aren't translated to Apalache at all.
This worries me a bit - which operators are not translated to Apalache? I didn't see any indication of this in the language docs. I am indeed using .then in the actions of a spec, and this makes me unsure whether it's meant to be usable there

This worries me a bit - which operators are not translated to Apalache? I didn't see any indication of this in the language docs. I am indeed using .then in the actions of a spec, and this makes me unsure whether it's meant to be usable there

The operators in run mode are not meant to be translated to apalache, as there are no such a thing as a run in TLA+. You can check them here: https://github.com/informalsystems/quint/blob/main/doc/lang.md#runs.
Sorry that this is not clear. We also want the effect checker to prevent usages of the run-level operator inside actions, but this was never prioritized.
For then specifically, it is equivalent to TLA's \cdot, which I personally think is useful. However, neither the Apalache devs (my team) and the TLC devs agree, so \cdot is unsupported in both model checkers. IIRC, @konnov said he doesn't see anything preventing the implementation of that, so perhaps one day we'll have it. For now, I recommend rewriting those actions without then or any other run operators, specially if you plan on using Apalache.

I think I have changed my opinion on this subject a bit. What happened is that in a project, I changed the protocol logic a bit, which effectively resulted in tests failing because I required every process at some points to do an additional step. As a result I needed to update all the concerned runs and tests, that is, figuring out where the tests hit a deadlock first, add additional steps there, and see whether there is another deadlock later, and repeat (I will write a separate issue on better user experience for writing tests, soon).
But what I would have prefered doing is having a way to tell quint to let everyone take steps (just calling the same action) until a certain condition is met (e.g., all the in-buffers are empty, and everyone has a specific value in its variable).
I think the ability to do that, will allow us to write tests (perhaps they are not really tests anymore but objects that we can use as we use tests in CI today) that require less maintenance if small changes in the protocol happen. In particular, in distributed systems, adding steps that result in stuttering doesn't seem to be uncommon, and not having to rewrite tests all the time seems to have big potential for saving time.
Effectively, what I am asking for is the feature to define a scheduler, that is, some way to decide on the next step, depending on the current state. Now, a fully-fledged scheduler syntactically might look totally different from a run: For instance, I might want to write a run that goes through 3 rounds of consensus. In a standard run, it is clear that syntactically, the steps of round 1 are at the top of the run, and the steps of round 3 they are at the bottom. I think this structure is super useful when using runs for onboarding and documentation. However, if a scheduler is a function of a state to the next step taken, this structure might go away, as we write functions differently from how we write runs and it might be less suitable for documentation purposes.
So I guess we should think about an extension of runs, perhaps call them "scenarios", that are more or less runs, but have some concepts that allow some sort scheduling, while maintaining the overall structure. The initial point of the discussion in this issue (having the argument of reps depending on the state; instead of being it pure) might be just one example. Perhaps we could also have a construct "repeat until" whose exit condition depends on the state.
I think that such "scenarios" would be a great extensions to runs, that could reduce the maintenance cost of executable specs in the long run. So it would be great to prioritize at least some initial steps into this direction.


feat(memoize): add different resolver strategies

Current dependencies on/for this PR:

main

PR #44

PR #45

PR #46   👈

This comment was auto-generated by Graphite.

Current dependencies on/for this PR:

main

PR #44

PR #45

PR #46   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: gGsyykimwILQL3Y4iKoV


added Arduino-DumbDisplay

added https://github.com/trevorwslee/Arduino-DumbDisplay

@ArduinoBot issue should be fixed


Laravel 5.3. Does it support?

I'm not getting the automatic validation class here
{!! BootForm::open() !!}
  {!! BootForm::text('First Name', 'first_name')->placeholder('John Doe') !!}
  {!! BootForm::submit('Submit') !!}
{!! BootForm::close() !!}

Am I missing something here?
PS: Oh by the way, thanks for creating this package.

Works fine in Laravel 5.3 for me. Check your validator is working correctly, maybe {!! var_dump($errors) !!} will give you an idea of what's going wrong.


Add /r/rawtxinfo/:transaction_id endpoint

This endpoint bypasses the index and acts as a proxy to get raw transaction
data from bitcoin cli
Response from bitcoincore_rpc is converted into a defined structure in this
codebase to help with compatibility

#4108 for more context

Same issue as #4100. We should only return the raw hex encoded transaction similiar to how the /r/metadata only return the hex encoded CBOR.

Hello @raphjaph, we've explained in the issue #4108 why a raw txhex might be problematic if a new transaction type is introduced. The inscriptions will not be able to decode those new transactions and the calculations will start to fail after that. A raw cbor is fine since cbor decoding will not change but txhex decoding may change with bitcoin upgrades.
For this reason we thought a minimal endpoint with fields that are also used in sat tracking and must be used in a utxo based system can be included in the response since they'll very likely stay the same.


Migrate to version 1.0.0-pre1

This PR migrates the base  and core dependencies to version 1.0.0-pre1.
It also migrates to the latest available web and jdbc-storage dependencies (1.0.0-SNAPSHOT and 0.10.80-SNAPSHOT respectively).
The PR includes changes from https://github.com/SpineEventEngine/todo-list/pull/67 and https://github.com/SpineEventEngine/todo-list/pull/66 which could not be merged due to problems with Travis status checks.

@dmdashenkov PTAL.

As discussed, we will release jdbc of version 1.0.0-pre1 before updating this repository.

@dmdashenkov PTAL.

@alexander-yevsyukov, please help us with the Travis status check here.


Can't login to account

Details
A few months ago I created an account for the content shown at https://pi-spec-test.readthedocs.io/en/latest/, but now I can’t get back into that account. Maybe I don't have the correct user name, because when I try to log in with what I think are correct credentials I get new account setup. Can you send me the login name associated with the content mentioned above, or provide other information that would help me log in?
Expected Result
Log into account and see source files for existing project.
Actual Result
All login attempts take me to new account setup.

This is the current owner https://readthedocs.org/profiles/kwshaw1/

Thanks, I was now able to reset the password and log in.

 Kevin

From: Santos Gallegos<EMAIL_ADDRESS>Sent: Tuesday, March 19, 2019 8:50 AM
To: rtfd/readthedocs.org<EMAIL_ADDRESS>Cc: Shaw, Kevin W<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [rtfd/readthedocs.org] Can't login to account (#5498)
This is the current owner https://readthedocs.org/profiles/kwshaw1/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rtfd/readthedocs.org/issues/5498#issuecomment-474436418, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUVRLO--vhnFLSN3ZI3ONu16CdBkBYTIks5vYQcYgaJpZM4b8ezO.


Bloomberg Quotes not working

Hello! Thank you for continuing to develop FinAnSu! It's really great!
I just wanted to bring to your attention that the latest version, <IP_ADDRESS>, does not parse Bloomberg quotes properly! Yahoo and Google work just fine, but unfortunately I need to track shares that are on exchanges currently only on bloomberg :(
The function seems to be working because I get the #wait symbol, but just returns a blank cell.
Thanks very much!

I get the same #WAIT error message when I retrieve the data from Google. It is on excel 2013.

I have got the same problem as rockingstar, using Excel 2010: #wait for Google and blanks for Bloomberg and Yahoo.
If anyone know how to fix it, it would be very helpful
Thanks


Storage account requirements should be more clear at documentation

Hello!
I'm working in a case which customer has requested help to set this extension to store data in a storage account located in a different subscription, because at portal screen (shown below) only storage accounts at same subscription can be selected:

The problem is that using a json template with either powershell or az CLI, we can set WAD to use a storage account in a different subscription. Errors does not occur.
The problem is, after to set this, later if we go to the portal, we cannot save and edit anything due to storage account configuration displays at summary, the storage account from other region, but at Agent configuration, storage account settings are empty:

If click on storage account name, we have this error:

Storage account tab configuration:

So, if there is a restricted requirement to have a storage account at same subscription to configure WAD, once we can see that portal does not work very well, using one from other sub causes these weird behaviors at portal, this should be more clear at documentation because we can set WAD, using a json template, pointing a SA from other region and no errors occurs.
Thanks in advance!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 47d0e17c-742d-1984-b18b-63b469625889
Version Independent ID: 7a274676-8cf2-449c-c722-3e31f19aafd9
Content: Install and configure Windows Azure diagnostics extension (WAD) - Azure Monitor
Content Source: articles/azure-monitor/agents/diagnostics-extension-windows-install.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @bwren
Microsoft Alias: bwren

@rafatecoy -  Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can update the document accordingly.

Sorry for delay in getting to this. Once you add configuration that the portal isn't able to support, I think you're going to need to perform any additional configuration also using templates since the portal. You can do complete configuration of WAD using ARM templates. I'll add a note to the article.
#please-close

Hello @bwren, I only want to add an additional thing here. Because, I got another case with similar issue with weird behaviors at portal while configure this extension and, on this one, the storage account was not on same region of VM. They were both at same subscription. Based on our findings here on this new case and additional things shared, I would conclude the following:

To proper manage this subscription at portal under "Diagnostic Settings", both VM and storage account need to be on same subscription and region.
If storage account is neither at same region nor subscription of VM, then, we need to manage using json/xml templates and powershell/az cli.


Add linux support

Closes #7

It now compiles, but unfortunately a problem finding the dynamic libraries when running:
$ ./bin/conche
./bin/conche: error while loading shared libraries: libCommander.so: cannot open shared object file: No such file or directory

Very odd error

@kattrali It's because .conche/lib isn't in library search paths. I can probably make conche exec do this, just requires you have an installed version of conche.

Closing out this issue as Conche is deprecated for the Swift Package Manager (SPM). Instead you can use SPM (https://github.com/Conche/Conche/commit/78708a9556b00d602de4c3e518a7f201b55a519b).


Fix Fixnum deprecation warnings.

Fixnum is being deprecated and merged with Bignum into Integer
(http://blog.bigbinary.com/2016/11/18/ruby-2-4-unifies-fixnum-and-bignum-into-integer.html)
This PR replaces Fixnum with Integer (in the tests) and fixes the
deprecation warnings

Excellent! :) Thanks @patrickdavey.

What's the file file:memdb1?mode=memory&cache=shared? ;)

I can't quite remember but you can use the blame feature of github to find out what the related commit was. I think it was to do with simulating race conditions.

It has added with this PR and it looks like SQLite file.

Not according to the files list: https://github.com/swanandp/acts_as_list/pull/282/files

I can see it.

Ah I see! Sorry it doesn't really stand out at all in the list does it. I've committed a removal directly to master.

No problem! Thanks!

My apologies for that :( I should have been more careful, usually am but it slipped through! Thanks @krzysiek1507 for pointing that out, and @brendon for fixing it.

Hey no worries :D We haven't released a gem yet anyway :)


datamodel: create base structure for datamodel

Create a base structure for the DataCite based datamodel. This aligns with the records datamodel inside cookiecutter-invenio-instance (previously self-contained in cookiecutter-invenio-datamodel).
It contains:

JSON Schemas
Elasticsearch mappings
Loaders
Serializers
Deserializers

NOTE: There's still a lot of discussion to be had on what should be internal and what metadata, etc. This just aims to have a clear code structure of the datamodel and a starting point to add more fields.
Closes https://github.com/inveniosoftware/invenio-rdm-records/issues/6

NOTE*: I think both commits can be squashed in one

@fenekku addressed all your comments :) Thanks a lot!
Just reminds the keyword. I would create an issue and leave as it is for now, to be consistent with cookiecutter (which was the point of the issue). And have a further discussion on the keywords/subjetc(s)/etc. and change as a result in the future. What do you think?


send_webauthn_code(): use jannson

it would be nicer iff send_webauthn_code() would use jansson to build a JSON object that is then printed into the JS code. Until now, the Uint8Array didn't work out with this.

I see no easy way to cast the json array into Uint8Array, and the jansson-based code doesn't look better than snprintf(), so drop this.


remove references to IJulia in getting_started.rst

As discussed in #472

Yup, no need to mention IJulia


testDelete the JOB show syntax (now we use TVF) and add tvf case

Add TVF case, tvf query Insert task adds JobId
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Modified links to the tutorial

Description

Related to https://github.com/ESMValGroup/ESMValTool_Tutorial/issues/281
Link to documentation: https://esmvaltool--3236.org.readthedocs.build/en/3236/quickstart/index.html

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Documentation is available
[x] 🛠 Tests run successfully
[x] 🛠 All checks below this pull request were successful

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

My review was 5 minutes late :smile: :blush:

My review was 5 minutes late smile blush

"never late, never free, never me, so I dub thee unforgiven" - as Metallica said about your review in Unforgiven 1 (1991) :laughing:


Repomanager RNA changes

WIP - not ready for review
Rebase of Sean's changes in #1368 on to master

abandoning for now


What are the suggested heuristics for 3PC deprecation relief

What are the exact suggested heuristics for 3PC deprecation relief and what is the timeline for deprecating this work-around?

Hi @mrvanes, for details please see the Intent to Prototype here: https://groups.google.com/a/chromium.org/g/blink-dev/c/Eeh2pE0DRaE/m/1BJyBlCUAAAJ which links to the explainer: https://github.com/amaliev/3pcd-exemption-heuristics/blob/main/explainer.md
Note that this is still being developed and we haven't yet committed to which specific heuristics will be shipped at what timeline. The preliminary target for implementation is Chrome M120, which is in Canary right now. You can follow along on the Chromestatus page: https://chromestatus.com/feature/5181771549507584

and what is the timeline for deprecating this work-around?

Ah, I misread this to ask about the timeline for shipping. While we intend to work with the other browsers to deprecate the heuristics, we don't have a clear target date yet, as that work depends on a variety of external ecosystem considerations such as site adoption of new technologies.

Thank you for the pointers. From Key Use Cases I presume that the heuristics will only mitigate breakage of embedded 3rd party cookies on site-A? Does that mean that 3PC for POST redirects from site-B to A using SameSite=None (SAML Authentication Response flow) are exempt from the planned 3PC deprecation changes anyway?

Yes, that's correct. We've written about this in https://github.com/DCtheTall/standardizing-cross-site-cookie-semantics/blob/main/README.md#top-level-cross-site-post-requests (which we're working to turn into a more official WebAppSec WG Note).
Top-level cross-site POST requests will continue to carry SameSite=None cookies for now, though I personally would be interested in finding ways to increase security of these requests in the long term as well.

Thx, final question, a bit out of scope: I couldn't find any references to the rumoured link-decoration deprecation write-ups which would break SAML as well, do you have any pointers to that work as well?

The only thing that comes to mind are the bounce tracking mitigations we published some time ago, see https://github.com/privacycg/nav-tracking-mitigations/blob/main/bounce-tracking-explainer.md for an explainer. Would be interesting to know if that's affecting any of your flows.

Thank you, the information was very helpful but I think I was looking for the linked information called Link decoration and Navigational tracking.


Enhancement: allow a restricted alphabet for regex output

This would just be passed through to the characters and text calls.  However you'd also have some annoying validation overhead to give sensible error messages, if you don't want to fail with incomprehensible health-check errors.
You would also need to decide and document whether the alphabet applies to all output (including literals and groups), or only wildcards.  Personally I'd go with the only-wildcards option, as this is much easier to validate - but it then requires clear documentation that the alphabet argument does not wholly restrict output.

Well, thing is that if you want to use only particular characters in some places, you specify it as ranges in regex. The exception here is character classes which can mean different things depending on whether unicode is enabled or not. So, my plan is to detect if unicode is/should be enabled and use appropriate configuration for generator strategies.
So, how to detect if unicode should be enabled? I see 3 ways:

Add a second argument which would be regex flags.
If you pass compiled regex instead of string, flags can be derived from it.
Lastly, you can use (?iLmsux) to control flags right from inside pattern string.

Flags include support for IGNORECASE, LOCALE, MULTILINE, DOTALL and UNICODE.
@Zac-HD That covers support for unicode in a more elegant way than passing keywords arguments to characters or texts strategies. If you have any concerns to that, please

Yep, that sounds like a better way to do it.  I'd avoid the extra argument as less elegant than deriving flags from the regex itself.
Options two and three are both nicely elegant.  Ideally you could handle both, but equally important is to provide clear errors on things that you don't handle, especially to avoid incorrect output.  For example, the new (?imsx-imsx:...) group in Python 3.6 would be nice to include, OK to leave out, and bad to get wrong.  (I think the existing error is probably sufficient and correct behaviour, but worth checking)

Oh, thank you for pointing that out. I will definitely try to implement support for separate settings for a subsection of regex in corresponding Python versions.

That being said, I will close this issue and recreate it with proper title and summary of proposed changes we came so far.

Create #3 to track support for regex flags.


Generate browser builds on release

Just wondering if it wouldn't be better if you added browser support by generating a browser release using Browserify yourselves (using the standalone option), and then optionally publishing the package to Bower too?
That way people can consume Knwl.js on the frontend using either method without having to force them to make a browserify build themselves.
If you'd like, I could set up a PR with a basic Gulp system to get the ball rolling?

Hi, @thomastuts! The browser builds for Knwl.js are available in the ./dist directory.


Add ability to blink LED

"Pins" class needs a new name, but that can be done separately.

Looks good to me


feat: add newline to trigger release action

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(solana): add sendTransaction functionality

Implement sendTransactionSolana
Add Solana token support under feature flag

Pitfalls:
Please hold off on merging this PR until the issue with balances in Swap has been resolved.


302 redirect reported as 404 broken link

I check the url http://store.meizu.com/ by HtmlUrlChecker, it report the broken link http://ordercenter.meizu.com/list/index.html with a HTTP_404 brokenReason, but it's a redirect link, not a 404.
Here is the result param in the HtmlUrlChecker link callback function.
{ url:
   { original: 'http://ordercenter.meizu.com/list/index.html',
     resolved: 'http://ordercenter.meizu.com/list/index.html',
     redirected: 'https://login.flyme.cn/vCodeLogin?useruri=http%3A%2F%2Fstore.meizu.com%2Fmember%2Flogin.htm?useruri=http://ordercenter.meizu.com/list/index.html&sid=unionlogin&service=&autodirct=true' },
  base:
   { original: 'http://store.meizu.com/',
     resolved: 'http://store.meizu.com/' },
  html:
   { index: 11,
     offsetIndex: 9,
     location: { line: 51, col: 44, startOffset: 2842, endOffset: 2893 },
     selector: 'html > body > div:nth-child(1) > div:nth-child(1) > div:nth-child(2) > ul:nth-child(1) > li:nth-child(2) > a:nth-child(1)',
     tagName: 'a',
     attrName: 'href',
     attrs:
      { class: 'topbar-link',
        href: 'http://ordercenter.meizu.com/list/index.html',
        target: '_blank' },
     text: '我的订单',
     tag: '<a class="topbar-link" href="http://ordercenter.meizu.com/list/index.html" target="_blank">' },
  http:
   { cached: false,
     response:
      { headers: [Object],
        httpVersion: '1.1',
        statusCode: 404,
        statusMessage: 'Not Found',
        url: 'https://login.flyme.cn/vCodeLogin?useruri=http%3A%2F%2Fstore.meizu.com%2Fmember%2Flogin.htm?useruri=http://ordercenter.meizu.com/list/index.html&sid=unionlogin&service=&autodirct=true',
        redirects: [Object] } },
  broken: true,
  internal: false,
  samePage: false,
  excluded: false,
  brokenReason: 'HTTP_404',
  excludedReason: null }

This is also happening to me. An example is a shortened URL from goo.gl...

Please show me your link.http.response.redirects Array.

As the response url, it returns the correct final destination after resolving the shortened URL, but the statusCode is 404. The http.response.redirects returns the following:
[  {  headers:  {  'content-type': 'text/html;  charset=UTF-8',  'cache-control': 'no-cache, no-store, max-age=0, must-revalidate',  pragma: 'no-cache',  expires: 'Mon, 01 Jan 1990 00:00:00 GMT',  date: 'Fri, 21 Oct 2016 09:09:23 GMT',  location: 'http://www.pordata.pt/Portugal/Res%C3%ADduos+urbanos+de+recolha+indiferenciada+e+selectiva-1104',  'x-content-type-options': 'nosniff',  'x-frame-options': 'SAMEORIGIN',  'x-xss-protection': '1;  mode=block',  server: 'GSE',  'accept-ranges': 'none',  vary: 'Accept-Encoding',  connection: 'close'  },  httpVersion: '1.1',  statusCode: 301,  statusMessage: 'Moved Permanently',  url: 'http://goo.gl/q0bKDz'  }  ]

I have the same problem here.  The 302 will reported as 404 regardless it redirect successfully or not.

Try installing the v0.8.0 (pre-release) branch:
npm install https://github.com/stevenvachon/broken-link-checker#v0.8.0

A lot has changed and it may have been fixed (?).

Got error right after "Getting links from"  :/
(node:18433) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'length' of undefined
(node:18433) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@howar31 sorry about that. I'd pushed my incomplete changes on the file:// work. Using v0.8.0 will have to wait, then.

Or you could try the previous commit without those changes:
npm install https://github.com/stevenvachon/broken-link-checker#f7ac9a7541482e3c49422aaaf034b6385fff9c5b


feat(#228): automatically get recent issues if none assigned

Fixes #228

Current dependencies on/for this PR:

main

PR #229   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 3, 4:34 PM GMT+1: @MartinBernstorff merged this pull request with Graphite.


8% battery usage by PowerLauncher in 24 hours

Environment
Windows build number: 10.0.18363.836
PowerToys version: 0.18
PowerToy module for which you are reporting the bug (if applicable): PowerLauncher/PowerToys Run

Steps to reproduce
Check in Windows Settings for "which apps are affecting your battery life"
See if PowerLauncher features at a high percentage
Expected behavior
I wouldn't expect it to use much battery at all.  I don't think I've even USED it in the past 24 hours.
Actual behavior
Windows tell me it's used 8% of my battery, which is obviously excessive, and it shows this has all been in the background.  Something seems wrong here.
Screenshots

tracking in #3208


Translatable, is field "id" required in translatable class?

Hi, i already have database with the following structure:
Content:
- id

ContentTranslation:
- content_id (id from table Content)
- language ("en", "de", etc.)
- title (title in specific language)
- description (content in specific language)

I got error:

field id not found
Is the field "id" required too in this table with translation? cause i already have fields "content_id" and "language" which are primary keys (but i have to remove @ID annotation to work cause of error "Single id is not allowed on composite primary key in entity").

I have the same problem, did you solve it?

No, i didn't find answer, so i just add this field "id" to database and set it as primary key, removing primary from previous columns (content_id, language).

I solved this problem and created PR #348

Resolved by #348
Impelmted in https://github.com/KnpLabs/DoctrineBehaviors/pull/442


How to set a different artifact name pattern

Hello,
the private repository at my company provides binaries with different name patterns than those allowed by this library.
I need a way to construct the binary name dynamically using the version of the package being installed. Something like this:
SASS_BINARY_NAME=linux-x64-57_binding-v{$version}.node
Also, the name pattern should be for the whole name of the artifact, no need to append stuff, limiting the names we can give...
Is something like this currently possible?

You can deploy your binary directly with a proper name we expect into vendor/linux-x64-57/binding.node file and this should work.
We don't support patterns in the names like this.


Scanner example not working on TinyDuino

I am using a rev 2 TinyDuino BLE shield. I am trying to run the scanner example (BGLib_scaner.ino). I have modified the line 59:
SoftwareSerial bleSerialPort(3, 4); // RX, TX

to account for the fact that the serial ports are connected to pin 3 and 4 according to the [official tutorial] (http://community.tiny-circuits.com/tutorials/using-the-bluetooth-low-energy-tinyshield-rev-2).
But it is not working as expected. From my iPhone I am running BLE explorer in peripheral mode to advertise alert notification service. But when I enter '2' from the serial monitor of the TinyDuino, I just get the output - -->	gap_set_scan_parameters: { scan_interval: 0xC8, scan_window: 0xC8, active: 1 }, but no actual advertising data.
I am not sure if I am doing anything wrong. Any help would be appreciated!
Thanks for making this library available.

I am having the same problem.


modules: trusted-firmware-a: introduce new module

Add trusted-firmware-a as a module.
This PR is related to https://github.com/zephyrproject-rtos/zephyr/issues/46105

@SgrrZhf Would basing this off the Corstone-1000 make more sense, since there is an 'ecosystem' image available for that already for Linux and Windows, and it can be downloaded directly from Arm without license management, or authentication (making it very CI friendly: https://developer.arm.com/downloads/-/arm-ecosystem-fvps)?
The Corstone-1000 ecosystem FVP is configured with:

An M0+ bootprocessor (code available in TF-M)
N x Cortex-A35 cores
A secondary Cortex-M3 based on the SSE-050 Subsystem

We're (Linaro) currently exploring enabling the M3 on this board in Zephyr, using TF-M for the M0+ boot, and eventually we'd like to enable the A35 so that we have an option for A+M on Zephyr communicating with each other, so we can likely help with some of the technical burden here. @povergoing has my contact details if you want to discuss how we can avoid duplicating development efforts on this, if you agree Corstone-1000 FVP might be a good choice.

There needs to be samples and tests that exercise this feature.

Got that

@SgrrZhf Would basing this off the Corstone-1000 make more sense, since there is an 'ecosystem' image available for that already for Linux and Windows, and it can be downloaded directly from Arm without license management, or authentication (making it very CI friendly: https://developer.arm.com/downloads/-/arm-ecosystem-fvps)?

@microbuilder Great idea, no problem, Corstone-1000 is a very powerful platform. I think @SgrrZhf would like to create an issue to plan the future work, including enabling v8A SMP and sure A35 with TF-A and so on. We will contact you if there is some issue:)

@SgrrZhf Would basing this off the Corstone-1000 make more sense, since there is an 'ecosystem' image available for that already for Linux and Windows, and it can be downloaded directly from Arm without license management, or authentication (making it very CI friendly: https://developer.arm.com/downloads/-/arm-ecosystem-fvps)?

Free to connect us if you need any help.
BTW, we also need the @stephanosio's help to make it into CI.

BTW, we also need the @stephanosio's help to make it into CI.

I can look into that as part of https://github.com/zephyrproject-rtos/zephyr/pull/45099.

There needs to be samples and tests that exercise this feature.

Could I create a directory 'samples/tfa-integration' and add a sample named 'hello_world'.  I will make more PR to enable more features such as PSCI later.
In this sample, I enable TFA. This sample will print messages like this and demonstrate that TF-A + zephyr is ok.
huizha01@5d2d7be9157a:/workdir/zephyr/build-docker$ west build -t run
-- west build: running target run
[0/1] FVP_Base_RevC-2xAEMvA:
terminal_0: Listening for serial connection on port 5000
terminal_1: Listening for serial connection on port 5001
terminal_2: Listening for serial connection on port 5002
terminal_3: Listening for serial connection on port 5003

Info: FVP_Base_RevC_2xAEMvA: FVP_Base_RevC_2xAEMvA.bp.flashloader0: FlashLoader: Loaded 168 kB from file '/workdir/zephyr/build-docker/tfa/fvp/release/fip.bin'

Info: FVP_Base_RevC_2xAEMvA: FVP_Base_RevC_2xAEMvA.bp.secureflashloader: FlashLoader: Loaded 25 kB from file '/workdir/zephyr/build-docker/tfa/fvp/release/bl1.bin'
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.7(release):v2.7.0-1-g371004ba9
NOTICE:  BL1: Built : 04:10:00, Jun  7 2022
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.7(release):v2.7.0-1-g371004ba9
NOTICE:  BL2: Built : 04:10:02, Jun  7 2022
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v2.7(release):v2.7.0-1-g371004ba9
NOTICE:  BL31: Built : 04:10:05, Jun  7 2022
*** Booting Zephyr OS build zephyr-v3.1.0-167-ge78f1ec86872  ***
Hello World! fvp_base_revc_2xaemv8a

There needs to be samples and tests that exercise this feature.

Could I create a directory 'samples/tfa-integration' and add a sample named 'hello_world'. I will make more PR to enable more features such as PSCI later.
In this sample, I enable TFA. This sample will print messages like this and demonstrate that TF-A + zephyr is ok.
huizha01@5d2d7be9157a:/workdir/zephyr/build-docker$ west build -t run
-- west build: running target run
[0/1] FVP_Base_RevC-2xAEMvA:
terminal_0: Listening for serial connection on port 5000
terminal_1: Listening for serial connection on port 5001
terminal_2: Listening for serial connection on port 5002
terminal_3: Listening for serial connection on port 5003

Info: FVP_Base_RevC_2xAEMvA: FVP_Base_RevC_2xAEMvA.bp.flashloader0: FlashLoader: Loaded 168 kB from file '/workdir/zephyr/build-docker/tfa/fvp/release/fip.bin'

Info: FVP_Base_RevC_2xAEMvA: FVP_Base_RevC_2xAEMvA.bp.secureflashloader: FlashLoader: Loaded 25 kB from file '/workdir/zephyr/build-docker/tfa/fvp/release/bl1.bin'
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.7(release):v2.7.0-1-g371004ba9
NOTICE:  BL1: Built : 04:10:00, Jun  7 2022
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.7(release):v2.7.0-1-g371004ba9
NOTICE:  BL2: Built : 04:10:02, Jun  7 2022
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v2.7(release):v2.7.0-1-g371004ba9
NOTICE:  BL31: Built : 04:10:05, Jun  7 2022
*** Booting Zephyr OS build zephyr-v3.1.0-167-ge78f1ec86872  ***
Hello World! fvp_base_revc_2xaemv8a

Any suggestions @stephanosio

Any suggestions @stephanosio

@SgrrZhf The sample(s) should be more comprehensive than just "hello world." Take a look at https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/tfm_integration for example.
@carlocaione and @microbuilder probably have some idea as to what sample(s) should be there.

Any suggestions @stephanosio

@SgrrZhf The sample(s) should be more comprehensive than just "hello world." Take a look at https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/tfm_integration for example.
@carlocaione and @microbuilder probably have some idea as to what sample(s) should be there.

tfm_ipc is probably the simplest example, and you should demonstrate a basic call from NS->S->NS: https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/tfm_integration/tfm_ipc

@carlocaione and @microbuilder probably have some idea as to what sample(s) should be there.

Well, having SMP working (thus PSCI) is also a good prof that TF-A is working correctly.
A long time ago I also added a PSCI test in ./tests/arch/arm64/arm64_psci that should be good enough IMO.

Agreed with both, but shell we let @SgrrZhf pick only one of two options as the sample for this PR and then enable another one in the next PR? @microbuilder @stephanosio @carlocaione

Hi, @carlocaione @stephanosio  @microbuilder
I'm finished.
Maybe I should put those fix patches to another PR to reduce the current PR's size?
What do you think about it?

I'm fine with this but IIUC given that you are modifying the west.yml file adding a new remote this cannot be merged as is.

I'm fine with this but IIUC given that you are modifying the west.yml file adding a new remote this cannot be merged as is.

Hi @carlocaione
I added a temporary remote for testing, and the result is that all tests passed.
I wonder when could TF-A be forked into Zephyr's github org. Should I remove the temporary remote from west.yml now?

Hi @carlocaione I added a temporary remote for testing, and the result is that all tests passed. I wonder when could TF-A be forked into Zephyr's github org. Should I remove the temporary remote from west.yml now?

@stephanosio @nashif who should fork TF-A? Given that I assume @SgrrZhf is going to maintain it, is that something that he can do himself?

Yes, @povergoing and I volunteer to maintain this(TF-A).

Hi @carlocaione I added a temporary remote for testing, and the result is that all tests passed. I wonder when could TF-A be forked into Zephyr's github org. Should I remove the temporary remote from west.yml now?

@stephanosio @nashif who should fork TF-A? Given that I assume @SgrrZhf is going to maintain it, is that something that he can do himself?

It would be much better that if there is something we could do it ahead, haha :)

https://github.com/zephyrproject-rtos/trusted-firmware-a has been created.

We need to add West project: trusted-firmware-m entry in the MAINTAINERS file.

We need to add West project: trusted-firmware-a entry in the MAINTAINERS file.
Got it.

Hi @stephanosio, would you like to take another look?


Cannot turn off auto-retry plugin via config file

What are you trying to achieve?
disable auto-retry plugin: https://codecept.io/basics/#auto-retry
I see it is set globally since 2.4, I am using: 2.4.3
And this is part of my config:
 plugins: {
    ...,
    retryFailedStep: {
      enabled: false
    },
  }

What do you get instead?
verbose log:
    [1] Retrying... Attempt #2
    [1] Retrying... Attempt #3
    [1] Retrying... Attempt #4
    [1] Retrying... Attempt #5
    [1] Retrying... Attempt #6
    [1] Error | Error: Text "testtesttest" was not found on page after 1 sec
waiting for function failed: timeout 1000ms exceeded

what I have in test:
await I.waitForText('testtesttest', 1);

@DavertMik is there a possibility to turn off auto-retry plugin globally for a project?

@grzegorzprzybylo Hi! Thank you for issue!
I check this moment today)

This looks like a major issue but I could not reproduce it.
Here is my output log:
      I fill field "user[password]"<EMAIL_ADDRESS>      › [Browser:Error] Failed to load resource: the server responded with a status of 422 (Unprocessable Entity)
    Emitted | step.passed (I fill field "user[password]"<EMAIL_ADDRESS>    Emitted | step.finish (I fill field "user[password]"<EMAIL_ADDRESS>    Emitted | step.start (I fill field "q", "aaa")
      I fill field "q", "aaa"
    [4] <within> Error | Error: Field "q" was not found by text|CSS|XPath
    Emitted | step.failed (I fill field "q", "aaa")
    Emitted | step.finish (I fill field "q", "aaa")
    [4] <within> Error | Error: Field "q" was not found by text|CSS|XPath
    Emitted | step.failed (I click "button")
    Emitted | step.finish (I click "button")
    [4] <within> Error | Error: Field "q" was not found by text|CSS|XPath
    [4] <within> Error | Error: Field "q" was not found by text|CSS|XPath
    Emitted | step.failed (I see "There were problems creating your account.")
    Emitted | step.finish (I see "There were problems creating your account.")
    [4] <within> Error | Error: Field "q" was not found by text|CSS|XPath
    Emitted | step.failed (I click "Explore")
    Emitted | step.finish (I click "Explore")
    [4] <within> Error | Error: Field "q" was not found by text|CSS|XPath
    Emitted | step.failed (I see in current url "/explore")
    Emitted | step.finish (I see in current url "/explore")
    [4] <within> Error | Error: Field "q" was not found by text|CSS|XPath
    [4] <within> Starting <teardown> session
    Emitted | test.failed ([object Object])
    Emitted | test.finish ([object Object])
    [4] <teardown> Stopping recording promises
 › <screenshotOnFail> Test failed, saving screenshot
 › Screenshot is saving to /home/davert/projects/codeceptjs/examples/output/register.failed.png
  ✖ FAILED in 1644ms

Here is my config:
    retryFailedStep: {
      enabled: false,
    },

Please provide an example which we could reproduce.
Or share more information on your setup, maybe the issue is in your config...

I can check it with some fresh install, once I have more info I will paste it here, thanks!

@DavertMik @Vorobeyko
looks like when I am using custom helper method it occurs, please see repo with example https://github.com/grzegorzprzybylo/ccjs-test

Hi, I am using resemble helper. Same issue.


Dev mistermotvey

New version 0.0.4! Added functions to delete users through the range, as well as reduced the amount of information displayed for the admin panel

Wwwwwow!!! This is perfect


Some small fixes and refactorings

Make variables local to function (setup.sh).
Use stackage latest LTS by default or fallback to user's one.
Extract stack install list of packages to the STACK_LIST variable.
Remove info messages from stack_resolver function.
Remove hdevtools from STACK_LIST.
Small refactorings (move "Aborting..." to exit_err, add exit_err_report function).

Accept this after travis PR to let it test these changes. ;)

Thanks again, you're making this project so much better.


Updates for SMBIOS Spec version 3.7.0

Including changes from 3.6.0

+1 thanks for bringing this up to date. nit: Maybe the comment is for 3.7.0 instead of 3.6.0

Includes changes from both 3.6.0 and 3.7.0. Though with 3.6.0 some of the changes were already integrated into smbios-lib through a 3.5.1, which no longer is listed on DMTF's site.


Document configuration file

It would be nice to have a page in the documentation where all the configuration options are listed in completeness.

Done.


Remove string formatting from data passed too Domoticz

Describe the bug
I want to use te powergeneration read from the device tot calculate and upload to pvoutput.org
In the calculation I get the following error: "attempt to perform arithmetic on global 'PowerGeneration' (a string value)".
After adding the command "print(" ----- PowerConsumption = " .. PowerConsumption .. " W"); I found out that to the value a W is added. This makes the value a string value.
Can you remove the W?
To Reproduce
Install following script:
`` - /home/pi/domoticz/scripts/lua/script_device_calculate_consumption.lua
-- This script collects the values below from Domoticz
--   * The Power and energy values (import and export) from a smartmeter
--   * The Power and energy values from a Solar power inverter
-- It then calculates the consumed power and energy from the values above with the formula's
--   * EnergyConsumption = EnergyGeneration + EnergyImport - EnergyExport
--   * PowerConsumption = PowerGeneration + PowerImport - PowerExport
-- It then updates a virtual device which displays the consumed power and energy in Domoticz

-- Domoticz IDX and names of the needed devices
local GenerationDeviceName = "GoodWe solar - Power"     -- Device name of the Generated energy
local EnergyDeviceName = "..................."    -- Name of the energy device that shows imported and exported energy
local ConsumptionIDX = ....                              -- IDX of the energy device that shows calculated Consumption
local ConsumptionDeviceName = "Calculation"             -- Name of the energy device that shows calculated Consumption

-- Require parameters
local http = require("socket.http")

-- Script parameters
PowerGeneration = 0     -- in Watts
EnergyGeneration = 0    -- in Watt hours
PowerImport = 0         -- in Watts
EnergyImportLow = 0     -- in Watt hours
EnergyImportHigh = 0    -- in Watt hours
EnergyImport = 0        -- in Watt hours
PowerExport = 0         -- in Watts (toegevoegd)
EnergyExportLow = 0     -- in Watt hours
EnergyExportHigh = 0    -- in Watt hours
EnergyExport = 0        -- in Watt hours
PowerConsumption = 0    -- in Watts
EnergyConsumption = 0   -- in Watt hours
Debug = "YES"           -- Turn debugging on ("YES") or off ("NO")

-- Lua Functions
function update(device, id, power, energy, index)
commandArray[index] = {['UpdateDevice'] = id .. "|0|" .. power .. ";" .. energy}
end

-- CommandArray
commandArray = {}
-- Generated
PowerGeneration, EnergyGeneration = otherdevices_svalues[GenerationDeviceName]:match("([^;]+);([^;]+)")
if Debug=="YES" then
print("  ----- ---- ---- ---- ---- ---- ---- ---- ---- ");
print("  ----- PowerGeneration = " .. PowerGeneration .. " W");
print("  ----- EnergyGeneration = " .. EnergyGeneration .. " Wh");
print("  ----- ---- ---- ---- ---- ---- ---- ---- ---- ");
end
    -- Imported/Exported
    EnergyImportLow, EnergyImportHigh, EnergyExportLow, EnergyExportHigh, PowerImport, PowerExport = otherdevices_svalues[EnergyDeviceName]:match("([^;]+);([^;]+);([^$
    EnergyImport = EnergyImportLow + EnergyImportHigh
    EnergyExport = EnergyExportLow + EnergyExportHigh
    if Debug=="YES" then
            print("  ----- PowerImport = " .. PowerImport .. " W");
            print("  ----- EnergyImport = " .. EnergyImport .. " Wh");
            print("  ----- EnergyImportLow = " .. EnergyImportLow .. " Wh");
            print("  ----- EnergyImportHigh = " .. EnergyImportHigh .. " Wh");
            print("  ----- PowerExport = " .. PowerExport .. " W");
            print("  ----- EnergyExport = " .. EnergyExport .. " Wh");
            print("  ----- EnergyExportLow = " .. EnergyExportLow .. " Wh");
            print("  ----- EnergyExportHigh = " .. EnergyExportHigh .. " Wh");
    end

    -- Calculate consumption
    PowerConsumption = PowerGeneration + PowerImport - PowerExport
    EnergyConsumption = EnergyGeneration + EnergyImport - EnergyExport
    if Debug=="YES" then
            print("  ----- PowerConsumption = " .. PowerConsumption .. " W");
            print("  ----- EnergyConsumption = " .. EnergyConsumption .. " Wh");
    end

    -- Update consumption device in Domoticz
           PowerConsumption = PowerGeneration + PowerImport - PowerExport
    EnergyConsumption = EnergyGeneration + EnergyImport - EnergyExport
    if Debug=="YES" then
            print("  ----- PowerConsumption = " .. PowerConsumption .. " W");
            print("  ----- EnergyConsumption = " .. EnergyConsumption .. " Wh");
    end

    -- Update consumption device in Domoticz
    if devicechanged[EnergyDeviceName] then
            update(ConsumptionDeviceName, ConsumptionIDX, PowerConsumption, EnergyConsumption, 1)
    end

return commandArray
``
After running you will find
Expected behavior
You would expect to get the following result:
2019-10-12 22:35:37.731 Status: LUA: ----- ---- ---- ---- ---- ---- ---- ---- ----
2019-10-12 22:35:37.731 Status: LUA: ----- PowerGeneration = 1 W
2019-10-12 22:35:37.731 Status: LUA: ----- EnergyGeneration = 2426100.0 Wh
2019-10-12 22:35:37.731 Status: LUA: ----- ---- ---- ---- ---- ---- ---- ---- ----
But instead I get:
2019-10-12 22:35:37.731 Status: LUA: ----- ---- ---- ---- ---- ---- ---- ---- ----
2019-10-12 22:35:37.731 Status: LUA: ----- PowerGeneration = 1W W
2019-10-12 22:35:37.731 Status: LUA: ----- EnergyGeneration = 2426100.0 Wh
2019-10-12 22:35:37.731 Status: LUA: ----- ---- ---- ---- ---- ---- ---- ---- ----
Screenshots
If applicable, add screenshots to help explain your problem.
Domoticz environment (please complete the following information):

Domoticz Version: [e.g. 4.10717]
Python Version: Python 2.7.13 (default, Sep 26 2018, 18:42:22)

Additional context
Add any other context about the problem here.

Domoticz itself can handle the input as it is currently passed, so not really a bug. Labeled it as enhancement for now.

Please try the fix in #3, I'd like to hear back if this solves the problem with PVOutput.

Dear Dylian, beste Dylian,
Thanks for adjusting. Dank voor het aanpassen.
I would like to test it, bu cannot find the files. Ik wil graag testen, maar helaas kan ik de bestanden niet vinden.
Where to find, I expect on GitHub. Waar vind ik de bestanden, zou denken op Github.
Thanks/bedankt!
Pieter
Op 15 okt. 2019, om 02:53 heeft Dylian Melgert <notifications<EMAIL_ADDRESS>het volgende geschreven:
Please try the fix in #3https://github.com/dylian94/domoticz-GoodWeSEMS/pull/3, I'd like to hear back if this solves the problem with PVOutput.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dylian94/domoticz-GoodWeSEMS/issues/2?email_source=notifications&email_token=ACH4FIVIUK2BKXUT4MFHRATQOUICFA5CNFSM4JAEJGF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBHBSKI#issuecomment-541989161, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACH4FIXC2FTSE7RMJLOR7TDQOUICFANCNFSM4JAEJGFQ.

You can click the download link in my previous post.

Hello Dylian94,
Yes it resolved the problem for the double W in power. There is still the same problem for the voltage "-- Voltage (v6) = 230.2V V" in the script "script_time_upload_to_PVoutput" Can you please solve that as well?
Thank you, Pieter
Op 1 nov. 2019, om 13:41 heeft Dylian Melgert <notifications<EMAIL_ADDRESS>het volgende geschreven:
You can click the download link in my previous post.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dylian94/domoticz-GoodWeSEMS/issues/2?email_source=notifications&email_token=ACH4FIQSOOU7J532LSFLMULQRQPXNA5CNFSM4JAEJGF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC22BJI#issuecomment-548774053, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACH4FIXXFWMPEWBRS2YAA6DQRQPXNANCNFSM4JAEJGFQ.

Hello Dylian94,
Maybe it is resolved when I also use the other file “Domoticz.pyi”, but I cannot find the original to replace.
So where should it be placed.
Thank you.
Pieter

Hello Dylian94,
Maybe it is resolved when I also use the other file “Domoticz.pyi”, but I cannot find the original to replace.
So where should it be placed.
Thank you.
Pieter
Op 9 nov. 2019, om 22:32 heeft Pieter van der Gulik <pvdgulik<EMAIL_ADDRESS>het volgende geschreven:
Hello Dylian94,
Yes it resolved the problem for the double W in power. There is still the same problem for the voltage "-- Voltage (v6) = 230.2V V" in the script "script_time_upload_to_PVoutput" Can you please solve that as well?
Thank you, Pieter
Op 1 nov. 2019, om 13:41 heeft Dylian Melgert <notifications<EMAIL_ADDRESS>het volgende geschreven:
You can click the download link in my previous post.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dylian94/domoticz-GoodWeSEMS/issues/2?email_source=notifications&email_token=ACH4FIQSOOU7J532LSFLMULQRQPXNA5CNFSM4JAEJGF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC22BJI#issuecomment-548774053, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACH4FIXXFWMPEWBRS2YAA6DQRQPXNANCNFSM4JAEJGFQ.


Update to open alert on new window

Closes https://github.com/sourcegraph/sourcegraph/issues/30518.
How to test

Run yarn run generate --languages=typescript && yarn --cwd generated-typescript run serve
Go to sourcegraph.com
Remove WebHoverOverlay.dismissedAlerts from localStorage
Add "sourcegraph/typescript": false to user settings -> extensions
Open any TypeScript file and hover over a token
Make sure "Learn more ..." open on a new tab
Don't forget to remove "sourcegraph/typescript": false

We also thought about making this more generic (to automatically open all external links in a new tab), but then we went with this single fix.

Thanks a lot! (Not sure if the .vscode/settings.json should be in here? But doesn't hurt, i guess.)

Sorry, fixed! Thanks for catching it! It should not be committed; my local extension auto-added it.

I think you can go ahead and merge, too, @erzhtor


Slack init message

Proposed changes:

Allow slack channel to support welcome message pattern by forwarding to init intent automatically when a user interaction with chatbot starts
fixes #7366
Status (please check what you already did):
[] added some tests for the functionality
[✅] updated the documentation
[✅ ] updated the changelog (please check changelog for instructions)
[✅] reformat files using black (please check Readme for instructions)

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

Thanks for submitting a pull request 🚀 @rgstephens will take a look at it as soon as possible ✨

hi @tmbo - yes I m aware of that. But you are kind of proving my point by your reply.

we have session_started event that we emit if a new conversation is started
If you read the article that I provided (and I can provide more as a proof) the good default behavior of chatbot should be that it actively send the 1st message to user.

Which current solution using session_started is incapable of. This solution will only react to user's first message. Which is putting the burden on user having him/her understand what the chatbot can do or having to ask the obvious question what can you do for me?
The burden of having to figure out the "init" of the user is not that hard. Bottom line - this behavior is optional and this fact is clearly documented in changed doc files.

@tmbo any updates on this? :D

I agree that there is a use case for this and that it is earlier than what we currently call "SessionStarted". I do think that we need a more general approach to this though, that works across channels.
I don't think using a special intent is the right approach for this for different reasons:

you'd be able to create stories that start with init and some that don't, but what is the difference?
to generalize this and to be able to get access to as much information about the user as possible, you'd want to have access to more meta information when writing this initial message. You might want to look up the user in a DB and respond with user-specific information, e.g. "Hey there Sara, you got 3 bills awaiting payment, do you want me to make a transfer?"
backwards-incompatible (at least in its current implementation)

I think we should at least think about more generalisable/alternative approaches to support this use case, e.g.

add an event that gets triggered before a user initializes a conversation, on chat window open
move the sessionstarted event to get triggered earlier

@tmbo - I like your ideas - they make sense to me.

I think we should at least think about more generalisable/alternative approaches to support this use case, e.g.

add an event that gets triggered before a user initializes a conversation, on chat window open
move the sessionstarted event to get triggered earlier

which of those 2 makes more sense from your point of view? I could understand both but maybe for the purpose of compatibility there could be a new event called sessioninitiated?
Something like that? When I get some time I would look into it and try to implement this (I hope that I find the right place in code :P )


Update HttpRequest logging

I made the same PR on the upstream branch, but seeing as that one is seemingly unmaintained, I'm making this here as well: https://github.com/blendle/zapdriver/pull/41 The other PR contains the description of the changes.

Feel free to also tag along https://github.com/blendle/zapdriver/pull/42.

Thank you very much for your contribution!

Feel free to also tag along blendle#42.

Do you mind opening the PR here?


fail to build llvm 6.0.0:Invalid cross-device link

RUST_BACKTRACE=1 llvmenv build-entry 6.0.0
Download: http://releases.llvm.org/6.0.0/llvm-6.0.0.src.tar.xz
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 18, kind: Other, message: "Invalid cross-device link" }
stack backtrace:
0:     0x5584273fd95c - backtrace::backtrace::trace::h12afcd4f49378dd1
1:     0x5584273fcee2 - backtrace::capture::Backtrace::new_unresolved::h92c6cd9e4e754865
2:     0x5584273fca0f - failure::backtrace::internal::InternalBacktrace::new::hfb19e4189742a117
3:     0x5584273fcc91 - <failure::backtrace::Backtrace as core::default::Default>::default::hddfd451558b22cb7
4:     0x5584273fccc8 - failure::backtrace::Backtrace::new::hcf3c736e958043fe
5:     0x5584271f8b62 - llvmenv::entry::Entry::checkout::h76d7443acf079d5f
6:     0x5584272069bc - llvmenv::main::hc950b30536fe8523
7:     0x5584271f0dc6 - std::rt::lang_start::{{closure}}::h0967c90a560327c1
8:     0x55842741b6c2 - std::rt::lang_start_internal::{{closure}}::hfeaf84249dc76f81
at libstd/rt.rs:59
- std::panicking::try::do_call::hf721aa74f3e4f06b
at libstd/panicking.rs:310
9:     0x558427444df9 - __rust_maybe_catch_panic
at libpanic_unwind/lib.rs:103
10:     0x5584274292e5 - std::panicking::try::h7ce97b72b588c2e6
at libstd/panicking.rs:289
- std::panic::catch_unwind::h2bf76b2cd658ccf1
at libstd/panic.rs:392
- std::rt::lang_start_internal::hc6c1baa40749df74
at libstd/rt.rs:58
11:     0x558427207f63 - main
12:     0x7fe419019a86 - __libc_start_main
13:     0x5584271d3ca9 - _start
14:                0x0 - ', libcore/result.rs:983:5
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: std::sys_common::backtrace::print
at libstd/sys_common/backtrace.rs:71
at libstd/sys_common/backtrace.rs:59
2: std::panicking::default_hook::{{closure}}
at libstd/panicking.rs:211
3: std::panicking::default_hook
at libstd/panicking.rs:227
4: std::panicking::rust_panic_with_hook
at libstd/panicking.rs:477
5: std::panicking::continue_panic_fmt
at libstd/panicking.rs:391
6: rust_begin_unwind
at libstd/panicking.rs:326
7: core::panicking::panic_fmt
at libcore/panicking.rs:77
8: core::result::unwrap_failed
9: llvmenv::main
10: std::rt::lang_start::{{closure}}
11: std::panicking::try::do_call
at libstd/rt.rs:59
at libstd/panicking.rs:310
12: __rust_maybe_catch_panic
at libpanic_unwind/lib.rs:103
13: std::rt::lang_start_internal
at libstd/panicking.rs:289
at libstd/panic.rs:392
at libstd/rt.rs:58
14: main
15: __libc_start_main
16: _start

Is there anywhere try to create a hard link on the disk?
How to solve this problem?

I'm seeing this same issue on Linux

I reproduce it. It seems due to std::fs::rename:

This will not work if the new name is on a different mount point.

I am fixing it...

I've released 0.1.9. Please re-open if not fixed.


Figure out why Featured Channels doesn't always update

Related code: https://github.com/GramyPomagamy/gsps-layouts/blob/main/src/extension/featured.ts

It's not a problem within our layouts. The same issue happens when using the https://api.furious.pro/featuredchannels/bot/ api manually on a brand-new account with freshly created integration. I guess we'd have to find another extension for that or drop the functionality.

I've dropped an email to<EMAIL_ADDRESS>let's see what it brings

The issue has been resolved by the Featured Channels developer on his end.