adding vscoq language server

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@vbgl failure in coq-community/coq-nix-toolbox#163 is spurious, I think this is ready for a merge.

The dune, ocaml, and findlib inputs are brought implicitly by buildDunePackages.
Are you sure you need all bash, hostname, time?

I blindly copied the flakes here https://github.com/coq-community/vscoq
@rtetley what do you think?

@maximedenes, not sure about this. What do you think ?

@maximedenes when you have fixe minutes can you check this out ?


Array contains -> includes, fix bug, closes #294

This PR swaps the existing Array.prototype.contains polyfill for the one in MDN, which passes all our tests and additionally a new test case which failed with our existing polyfill.

Hooray, fixed travis.


Missing patch for enabling stylus on kepubs

Maybe I'm doing something wrong, but the patch mentioned here seems to be missing from the patches available for the latest firmware for the Kobo Elipsa?

Hi, thx for the reply, I did notice that comment but wasn't sure what was implied as it seems to not work on my .kepubs, I'll do some more tests and see just why it fails here.
Feel free to close the ticket as it's not an issue with kobopatch in this case.

What's KCC?


ucasal.txt

Se agrega universidad

@cristiansueldo First stage of verification passed, official domain for Universidad Catolica de Salta is ucasal.edu.ar as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


Support yaml, yamlc output

Original PR https://github.com/Azure/azure-cli/pull/12234
This PR:

Move yaml and yamlc output from Azure CLI to knack to unify output formats into one place
Add Unicode support in yaml output, like こんにちは
If stdout is a not tty, override jsonc with json, yamlc with yaml to remove color

Just one question. Even if this PR is merged, this won't work until you remove the inherited logic in azure-cli-core. Right? I mean this get_formatter part.

yes


Adding responseTemplate and responseTopic to webhook creation

This is a patch to address what has been discussed here: https://github.com/spark/particle-api-js/issues/21
@brycekahle

@acasas would you mind signing the CLA? Just ping me when you have!

Just did @brycekahle

Thanks!


Visualize Progress

a progress bar can be implemented using:
progressbar doit_prog color:red

Getting progress from amazon s3 in .net:
https://docs.aws.amazon.com/AmazonS3/latest/dev/HLTrackProgressMPUDotNet.html

for more direct communication between MaxScript and C#
https://forums.cgsociety.org/t/dotnet-and-dll/1424856/4


[table config] new metrics don't show up in explore

After creating a new calculated column or metric from the modal table config in Explore View, the new metric/column is not available. User must manually refresh Explore view to choose newly created metric
Repro:
Click on datasource to edit
Create new metric
Save (brings back to Explore view)
Look for new metric
Not there

Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Superset version
v.031
Expected results
Actual results
Steps to reproduce

Same thing happen to us.
Clicking on the datasource, Edit datasource, changing SQL in the advanced settings doesn't bring new metrics on the visualisation.
On columns, Sync columns from source is not available.
If I click on view query I get something like this:
SELECT month AS month,
                old_metric AS old_metric
FROM
  (SELECT DATE_TRUNC('month', date_time) AS month,
          COUNT(DISTINCT column_1) AS old_metric,
          COUNT(DISTINCT column_2) AS new_metric
   FROM table
   GROUP BY 1) AS expr_qry
WHERE month >= '1919-06-13 00:00:00'
LIMIT 1000;

So the query is not updated with the new column in my modified SQL query.

+1 for this problem

Column should be synced even if for views


updateOnSelectorChange not supporting jQuery like selectors

Hi,
I have a table that is inside a div with an ID and would like the custom scrollbar to update when that table changes.
I would like to have like updateOnSelectorChange: "#mydivID table" , so it only updates when that specific table changes, rather than doing updateOnSelectorChange: "table", which works but will update on every table resize, which is not efficient.
Am I doing anything wrong?
Any way to do this / will you plan to add support for this?

Never mind, it supports jQuery like selectors, but it only searches for children inside MCS container.


[Bug] Typing errors when using openapi types

Describe the bug
When defining a parameter and using a type such as openapi.Integer(), typing checks fail because there's no available overload that matches.
Screenshots

To Reproduce
from sanic_ext import openapi

...

@app.route("/")
@openapi.parameter("scope", openapi.Integer())
async def do_stuff(*_, **_):
    ...

Expected behavior
There's no typing errors.
Environment (please complete the following information):

OS: Windows 10 Home 21H1
Browser: N/A
Version: sanic-ext 22.1.2

Additional context
N/A

I seem to be able to fix this issue by adding default values in the following method overload:

Go for it :muscle:


JS Dev Center metadata

@diberry : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@diberry: I'm sorry - only the author of this article, @KesemSharabi, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Hi @diberry - Would you make this content update in the private repo? Thank you! We'll close this PR.


Change rich-text to richText?

Discussed in https://github.com/tinacms/tinacms/discussions/2184

Originally posted by jeffsee55 November  1, 2021
We want to get away from kebab-case for all of the schema.ts properties for consistency, this one is currently the only primitive that has it

This will have to wait until we support versioning

[ ] Mark rich-text as deprecated in it's type def
[ ] Cast rich-text to richText during validate (behind the scenes)


User settings show empty options

Unable to change settings because user settings show nothing. I'm using Firefox 61.0.1

This issue was encountered on Firefox 62, but works fine in Chromium.
In Firefox, if you hit the tab button to navigate by keyboard to the option for default user settings, the options will appear.

Thanks for the report, @govvin. I haven't been able to reproduce this on Firefox for Mac 61.0.1, 61.02, or 62.0, but it sounds like you're on Linux, correct?

Yes, on Linux.

Is this related to / the same as #437 ?

The missing user settings should now be fixed, but please do reopen if you experience problems again. Thanks again for reporting.


Compact header feature breaks the header size

Compact header feature breaks the header size and makes drop down menu, search option and setting inaccessible.

This was fixed in a commit today, I'll push the fix to the Play Store shortly


(mkdocs) Create shim

App is not accessible after install, it creates script in python folder.

This is actually not an issue as Python scripts dir is in the PATH. I didnt refreshenv.

ah, the usual mistake I also quite often do.


METRON-116 Fastcapa Rename and Improved Documentation

Renamed packet capture to fastcapa to distinguish it from pycapa.
Improved fastcapa README to show use of test environment at deployment/vagrant/fastcapa-vagrant.
Made sensor-test-mode role configurable so that it could be used in deployment/vagrant/fastcapa-vagrant.

Will reopen once conflicts resolved with master reorg.


[Feature]: Reduce number of plots from modes of variability

Is your feature request related to a problem?
Suggested by @zhangshixuan1987 at https://github.com/PCMDI/pcmdi_metrics/pull/1112#issuecomment-2328128362 and discussed in https://github.com/PCMDI/pcmdi_metrics/pull/1112#issuecomment-2328424624.
Describe the solution you'd like
Maybe plot option can be elaborated to plot_eof, plot_additional_eofs, and plot_cbf?

Hi Jiwoo,
I think a clearer group of the output figures can be enough to address the confusions. Here is my idea:

Take SAM, PSA1 and PSA2 as examples,  they were first three modes of EOF analysis from either sea level pressure or 500hPa geopotential height.
In theory, we expect that the first, second and third EOFs are corresponding to SAM, PSA1 and PSA2, respectively. Therefore, to my understanding, we can group the output figures into three groups:
*   “Mode pattern”:  save the expected EOF pattern (theoretical), i.e. EOF1 from reference and model as they are supposed to be the SAM.
*   “Best Matching EOF pattern”: i.e. the EOF patterns that can best match  expected EOF pattern (theoretical) for SAM, PSA1 or PSA2.
*   “EOF Pool”: the first three leadings EOFs in reference and model as additional information

I am just sharing the thoughts from me as a references for you, and my group maybe not optimal.
However, split plot option to plot_eof, plot_additional_eofs, and plot_cbf also sounds good to me as it ineed allows users to decide if they want the addental figures.
Thank you!
With best wishes,
Shixuan
Shixuan Zhang| Pacific Northwest National Laboratory
Earth Scientist, Atmospheric, Climate, & Earth Sciences Division
p.<PHONE_NUMBER>
www.pnnl.govhttps://www.pnnl.gov/science/staff/staff_info.asp?staff_num=9376
From: Jiwoo Lee @.>
Date: Tuesday, September 10, 2024 at 15:23
To: PCMDI/pcmdi_metrics @.>
Cc: Zhang, Shixuan @.>, Mention @.>
Subject: [PCMDI/pcmdi_metrics] [Feature]: Reduce number of plots from modes of variability (Issue #1120)
Check twice before you click! This email originated from outside PNNL.
Is your feature request related to a problem?
Suggested by @zhangshixuan1987https://github.com/zhangshixuan1987 at #1112 (comment)https://github.com/PCMDI/pcmdi_metrics/pull/1112#issuecomment-2328128362 and discussed in #1112 (comment)https://github.com/PCMDI/pcmdi_metrics/pull/1112#issuecomment-2328424624.
Describe the solution you'd like
Maybe plot option can be elaborated to plot_eof, plot_additional_eofs, and plot_cbf?
Describe alternatives you've considered
No response
Additional context
No response
—
Reply to this email directly, view it on GitHubhttps://github.com/PCMDI/pcmdi_metrics/issues/1120, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIAWVFUZKGIBTH2WPADTWHDZV5WMPAVCNFSM6AAAAABN7WAM2OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTQMBUG4YTQMQ.
You are receiving this because you were mentioned.Message ID: @.***>

I have added two figures (examples shown as below), which summarize the mode and compare to the reference dataset. While it is not reducing number of plots (actually add 2 more..), @kristinchang3 and I can make this multi-panel figure accessible from the PMP html viewer, so users are not necessarily finding needed figure through multiple plots unless they need to look in details.
Result from the CBF methodology:

Result from the traditional EOF methodology:

@zhangshixuan1987 any feedback would be appreciated. Please also feel free to reopen this issue or open a new issue if needed.


Copy packages from prod to autopush for ARLE testing pipeline

This should completely isolate the two environments.

/approve


[SQL] az sql db: Add --preferred-enclave-type argument

Related command

az sql db create
az sql db show

Description

Adds support for PreferredEnclaveType parameter for Database CRUD operations.

Testing Guide

az sql db create --preferred-enclave-type "VBS"
az sql db show

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

@evelyn-ys Thanks for the review. Yes, for the new parameter I upgraded the SDK locally and then used the new api version 2022-05-01-preview API version. The failing tests worked fine locally, when I recorded them. Anything I need to do to fix the 3 failing checks?

@vidit-msft, Where did you get the new SDK with 2022-05-01-preview API version? I didn't see any new SDK released with that new API version in https://pypi.org/project/azure-mgmt-sql/#history.
If there is no public SDK with 2022-05-01-preview API version, you cannot support this feature in Azure CLI as Azure CLI depends on public SDK.

@jsntcy I requested a private python SDK build [resource-manager] Python: 'Release of Database Services - 2022-05-01' · Issue #3574 · Azure/sdk-release-request (github.com) and used it for updating azure cli commands and record tests. Can I request a public SDK release and then we can merge this PR?

Once you use the public SDK, you need test all SQL tests lively (There are many tests for SQL as many teams contribute to SQL commands) to avoid regression, if there is no issue, we can merge.
I'm not sure if you have enough time to run those tests as you may need some time to get the public SDK. If you cannot catch this sprint, we probably postpone it to next sprint (one month later).

@jsntcy I talked to the Python SDK team and they released a new python sdk https://pypi.org/project/azure-mgmt-sql/4.0.0b6/ which relies on 2022-05-01-preview API version. Should I bump up the azure-mgmt-sql version in Azure-CLI and re-record the tests now?

Sure pls bump SDK version if it's required for this feature.
We have an internal pipeline for bumping version, see https://github.com/Azure/azure-cli/blob/dev/doc/how_to_bump_SDK_version_in_cli.md

@evelyn-ys I don't seem to have access to the Regression test pipeline mentioned in azure-cli/how_to_bump_SDK_version_in_cli.md at dev · Azure/azure-cli (github.com). I have already requested access for it. When I bumped up the sdk version and tried to run all the sql tests, I see some failures i.e 29 failed and 45 tests passed. How do we make sure all tests pass with the bumped up sdk version to proceed forward?

Did you rerun all tests with --live and then saw the 29 failure tests? You need to figure out why they failed and fix one by one.

You need contact other teams to rerun those failed tests lively. (The root cause is that some resources in tests are hardcoded instead of creating dynamically)

@evelyn-ys All the checks pass now, can we please merge this PR and have it be part of the Azure-CLI January release?


Validation passes if CodeableConcept bound to value set does not contain system and code

For example, the AdverseEvent.severity field has a required binding to a value set of system+code values.
To Reproduce
// This validates successfully (but it doesn't seem like it should)
AdverseEvent adverseEvent1 = AdverseEvent.builder().actuality(AdverseEventActuality.ACTUAL)
.subject(Reference.builder().reference(String.of("Patient/1234")).build())
.severity(CodeableConcept.builder().coding(
Coding.builder().code(Code.of("othervalue"))
.build()).build()).build();
// This fails validation
AdverseEvent adverseEvent2 = AdverseEvent.builder().actuality(AdverseEventActuality.ACTUAL)
.subject(Reference.builder().reference(String.of("Patient/1234")).build())
.severity(CodeableConcept.builder().coding(
Coding.builder().system(Uri.of("otheruri")).code(Code.of("othervalue"))
.build()).build()).build();
Expected behavior
The following rules apply when required bindings are used with the CodeableConcept data type:
* at least one Coding element SHALL be present
* one of the Coding values SHALL be from the specified value set
* text can be provided as well, and is always recommended, but is not an acceptable substitute for the required code
If a required binding is applied to an element with maximum cardinality > 1, the binding applies to all the elements.

In addition to code, Coding, and CodeableConcept fields, validation will be done against Quantity, Uri, and String fields as well that have a binding to a value set. Validation rules for Quantity fields will follow those of Coding fields as described above, while validation rules for Uri and String fields will follow those of Code fields.
Also, the new configuration property, fhirServer/core/extendedCodeableConceptValidation, has been created to control how coding validation is enforced during object construction. The default value is true, meaning the new "extended" validation rules as described above will be enforced during object construction, including syntax-only validation for elements with a required binding to the http://hl7.org/fhir/ValueSet/all-languages or http://hl7.org/fhir/ValueSet/ucum-units value sets. If the config property is set to false, then "old" coding validation rules will be enforced, meaning only CodeableConcept fields with a required binding to a value set will be validated, and only Codings within the CodeableConcept field that contain both a system value and a code value will be validated.


Difficulty installing mxnet

Hi, I am having difficulty in installing the mxnet R package on BERT console for interfacing with Excel, and am wondering if you can offer some guidance...
I am using a 32-bit Excel, and have installed the BERT Excel tool from ( https://bert-toolkit.com/ ).  I then proceeded to install the mxnet package with the lines below...
cran <- getOption("repos")
cran["dmlc"] <- "https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/R/CRAN/"
options(repos = cran)
install.packages("mxnet")
Then I receive the message saying..
Package which is only available in source form, and may need compilation
of C/C++/Fortran: 'mxnet'
These will not be installed
I then tried a different set of lines...
install.packages("drat", repos="https://cran.rstudio.com")
drat:::addRepo("dmlc")
install.packages("mxnet")
Which appeared to be working, but then had the following messages when I tried library("mxnet")...
Error in library("mxnet") : there is no package called 'mxnet'
In addition: Warning message:
package 'mxnet' is not available (for R version 3.4.1)
I also tried installing mxnet in R Studio on Mac, and I got the an error message advising that i tis not installed for arch i386.  Presumably it means 32-bit systems?
I am wondering if anyone experienced this before?
Thanks.

Hi, a quick update...
On BERT Console.., I tried...
install.packages("https://github.com/jeremiedb/mxnet_winbin/raw/master/mxnet.zip", repos = NULL)
And I got the below error message...
Error: package 'mxnet' is not installed for 'arch = i386'
Which is similar to the error I got on Mac...
Am wondering if anyone knows how I can get round this?
Thanks, Eric.

The issue is, like you suspected, that only 64-bit installation is supported right now. Could be a good pretext to move to 64 bit:)

As @jeremiedb  said, we only provide the 64-bit installation now.


Greenkeeper/@types/chai 4.0.7

Coverage remained the same at 73.333% when pulling 830d8d91e6c23e1a452d164bf1e728e141e12f0d on<EMAIL_ADDRESS>into 22ce3035bdce448b267d6fe7d4919a6d289d8688 on master.


Error "cannot import name 'TypeAliasType' from 'typing_extensions'" when importing openai just after installation

Confirm this is an issue with the Python library and not an underlying OpenAI API

[X] This is an issue with the Python library

Describe the bug

ImportError                               Traceback (most recent call last)
Cell In[38], line 1
----> 1 import openai
      2 import os
      4 opai.api_key = os.getenv("OPENAI_API_KEY")

File D:\Anaconda\envs\py38\lib\site-packages\openai\__init__.py:8
      5 import os as _os
      6 from typing_extensions import override
----> 8 from . import types
      9 from ._types import NoneType, Transport, ProxiesTypes
     10 from ._utils import file_from_path

File D:\Anaconda\envs\py38\lib\site-packages\openai\types\__init__.py:5
      1 # File generated from our OpenAPI spec by Stainless.
      3 from __future__ import annotations
----> 5 from .edit import Edit as Edit
      6 from .image import Image as Image
      7 from .model import Model as Model

File D:\Anaconda\envs\py38\lib\site-packages\openai\types\edit.py:6
      3 from typing import List
      4 from typing_extensions import Literal
----> 6 from .._models import BaseModel
      7 from .completion_usage import CompletionUsage
      9 __all__ = ["Edit", "Choice"]

File D:\Anaconda\envs\py38\lib\site-packages\openai\_models.py:20
     18 import pydantic
     19 import pydantic.generics
---> 20 from pydantic.fields import FieldInfo
     22 from ._types import (
     23     Body,
     24     IncEx,
   (...)
     31     HttpxRequestFiles,
     32 )
     33 from ._utils import (
     34     is_list,
     35     is_given,
   (...)
     39     strip_not_given,
     40 )

File D:\Anaconda\envs\py38\lib\site-packages\pydantic\fields.py:24
     21 from pydantic_core import PydanticUndefined
     22 from typing_extensions import Literal, Unpack
---> 24 from . import types
     25 from ._internal import _decorators, _fields, _generics, _internal_dataclass, _repr, _typing_extra, _utils
     26 from .config import JsonDict

File D:\Anaconda\envs\py38\lib\site-packages\pydantic\types.py:33
     31 from annotated_types import BaseMetadata, MaxLen, MinLen
     32 from pydantic_core import CoreSchema, PydanticCustomError, core_schema
---> 33 from typing_extensions import Annotated, Literal, Protocol, TypeAlias, TypeAliasType, deprecated
     35 from ._internal import (
     36     _core_utils,
     37     _fields,
   (...)
     41     _validators,
     42 )
     43 from ._migration import getattr_migration

ImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (D:\Anaconda\envs\py38\lib\site-packages\typing_extensions.py)

To Reproduce
import openai
then error happens
the typing_extensions version is 4.8.0(latest)
Code snippets
No response
OS
windows
Python version
Python 3.8.16
Library version
openai v 1.2.4

This stack trace comes from pydantic, what pydantic version do you have installed?

pydantic

2.5.0

Are you using databricks? There are known issues with their environment breaking things https://github.com/openai/openai-python/issues/751

Are you using databricks? There are known issues with their environment breaking things #751

No, As far as I know, we didn't use databricks.
Actually, I haven't heard of that before.

What version of Anaconda are you on?

What version of Anaconda are you on?

23.1.0

Was able to fix this issue by upgrading to Python 3.11

Was able to fix this issue by upgrading to Python 3.11

First, Thank you very much for point out the way to walk through
If possible, can you show me the reason for this bug?

@rattrayalex @RobertCraigie can you re-open this issue? It's still an unresolved issue - a compatibility issue with Python versions before 3.11 where the pypi.org index promises support from 3.7.1 onwards.

The openai package works for me on Python 3.8, can you share any more details about your environment?

This is probably an issue with pydantic or typing_extensions versions. In the pyproject.toml, it says one can use
    "pydantic>=1.9.0, <3",
    "typing-extensions>=4.7, <5",

but I got this same error in an environment with

typing_extensions 4.10.0
pydantic 2.6.2

though not in one with

typing_extensions 4.8.0
pydantic 1.10.13

There were several other differences between the envs, but this might be a start towards narrowing down versions of these libraries that work.

This is probably an issue with pydantic or typing_extensions versions. In the pyproject.toml, it says one can use
    "pydantic>=1.9.0, <3",
    "typing-extensions>=4.7, <5",

but I got this same error in an environment with

typing_extensions 4.10.0
pydantic 2.6.2

though not in one with

typing_extensions 4.8.0
pydantic 1.10.13

There were several other differences between the envs, but this might be a start towards narrowing down versions of these libraries that work.

This worked.

I still see this issue :
Python version: 3.11 Pydantic version: 2.7.0 typing-extensions version: 4.11.0
Error : ImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/typing_extensions.py)

I still see this issue : Python version: 3.11 Pydantic version: 2.7.0 typing-extensions version: 4.11.0  Error : ImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/typing_extensions.py)

Install below version of libraries:
pydantic==1.10.11
typing_extensions==4.5.0

I still see this issue : Python version: 3.11 Pydantic version: 2.7.0 typing-extensions version: 4.11.0  Error : ImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/typing_extensions.py)

Install below version of libraries: pydantic==1.10.11 typing_extensions==4.5.0

Thanks @saurabhtiger, I managed to make it work with pydantic==1.10.11 typing_extensions==4.7.0 since openai latest version have a requirement typing_extensions >= 4.7.0

while importing this libraries:
import os
from apikey import apikey
import streamlit as st
from langchain.llms import OpenAI
from langchain.prompts import PromptTemplate
from langchain.chains import LLMChain, SequentialChain
from langchain.memory import ConversationBufferMemory
from langchain.utilities import WikipediaAPIWrapper
error occoured:
ImportError                               Traceback (most recent call last)
Cell In[31], line 9
7 from langchain.prompts import PromptTemplate
8 from langchain.chains import LLMChain, SequentialChain
----> 9 from langchain.memory import ConversationBufferMemory
10 from langchain.utilities import WikipediaAPIWrapper
File ~\anaconda3\lib\site-packages\langchain\memory_init_.py:29
1 """Memory maintains Chain state, incorporating context from past runs.
2
3 Class hierarchy for Memory:
(...)
27     AIMessage, BaseMessage, HumanMessage
28 """  # noqa: E501
---> 29 from langchain_community.chat_message_histories import (
30     AstraDBChatMessageHistory,
31     CassandraChatMessageHistory,
32     ChatMessageHistory,
33     CosmosDBChatMessageHistory,
34     DynamoDBChatMessageHistory,
35     ElasticsearchChatMessageHistory,
36     FileChatMessageHistory,
37     MomentoChatMessageHistory,
38     MongoDBChatMessageHistory,
39     PostgresChatMessageHistory,
40     RedisChatMessageHistory,
41     SingleStoreDBChatMessageHistory,
42     SQLChatMessageHistory,
43     StreamlitChatMessageHistory,
44     UpstashRedisChatMessageHistory,
45     XataChatMessageHistory,
46     ZepChatMessageHistory,
47 )
49 from langchain.memory.buffer import (
50     ConversationBufferMemory,
51     ConversationStringBufferMemory,
52 )
53 from langchain.memory.buffer_window import ConversationBufferWindowMemory
File ~\anaconda3\lib\site-packages\langchain_community\chat_message_histories_init_.py:137, in getattr(name)
135 def getattr(name: str) -> Any:
136     if name in _module_lookup:
--> 137         module = importlib.import_module(_module_lookup[name])
138         return getattr(module, name)
139     raise AttributeError(f"module {name} has no attribute {name}")
File ~\anaconda3\lib\importlib_init_.py:126, in import_module(name, package)
124             break
125         level += 1
--> 126 return _bootstrap._gcd_import(name[level:], package, level)
File ~\anaconda3\lib\site-packages\langchain_community\chat_message_histories\sql.py:6
3 from abc import ABC, abstractmethod
4 from typing import Any, List, Optional
----> 6 from sqlalchemy import Column, Integer, Text, create_engine
8 try:
9     from sqlalchemy.orm import declarative_base
File ~\anaconda3\lib\site-packages\sqlalchemy_init_.py:12
8 from future import annotations
10 from typing import Any
---> 12 from . import util as _util
13 from .engine import AdaptedConnection as AdaptedConnection
14 from .engine import BaseRow as BaseRow
File ~\anaconda3\lib\site-packages\sqlalchemy\util_init_.py:15
12 from typing import TYPE_CHECKING
14 from . import preloaded as preloaded
---> 15 from ._collections import coerce_generator_arg as coerce_generator_arg
16 from ._collections import coerce_to_immutabledict as coerce_to_immutabledict
17 from ._collections import column_dict as column_dict
File ~\anaconda3\lib\site-packages\sqlalchemy\util_collections.py:38
35 import weakref
37 from ._has_cy import HAS_CYEXTENSION
---> 38 from .typing import is_non_string_iterable
39 from .typing import Literal
40 from .typing import Protocol
File ~\anaconda3\lib\site-packages\sqlalchemy\util\typing.py:56
54     from typing_extensions import TypeGuard as TypeGuard  # 3.10
55     from typing_extensions import Self as Self  # 3.11
---> 56     from typing_extensions import TypeAliasType as TypeAliasType  # 3.12
58 _T = TypeVar("_T", bound=Any)
59 _KT = TypeVar("_KT")
ImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (C:\Users\titik\anaconda3\lib\site-packages\typing_extensions.py)
how to solve this??

while importing this libraries: import os from apikey import apikey
import streamlit as st from langchain.llms import OpenAI from langchain.prompts import PromptTemplate from langchain.chains import LLMChain, SequentialChain from langchain.memory import ConversationBufferMemory from langchain.utilities import WikipediaAPIWrapper
error occoured:
ImportError Traceback (most recent call last) Cell In[31], line 9 7 from langchain.prompts import PromptTemplate 8 from langchain.chains import LLMChain, SequentialChain ----> 9 from langchain.memory import ConversationBufferMemory 10 from langchain.utilities import WikipediaAPIWrapper
File ~\anaconda3\lib\site-packages\langchain\memory__init__.py:29 1 """Memory maintains Chain state, incorporating context from past runs. 2 3 Class hierarchy for Memory: (...) 27 AIMessage, BaseMessage, HumanMessage 28 """ # noqa: E501 ---> 29 from langchain_community.chat_message_histories import ( 30 AstraDBChatMessageHistory, 31 CassandraChatMessageHistory, 32 ChatMessageHistory, 33 CosmosDBChatMessageHistory, 34 DynamoDBChatMessageHistory, 35 ElasticsearchChatMessageHistory, 36 FileChatMessageHistory, 37 MomentoChatMessageHistory, 38 MongoDBChatMessageHistory, 39 PostgresChatMessageHistory, 40 RedisChatMessageHistory, 41 SingleStoreDBChatMessageHistory, 42 SQLChatMessageHistory, 43 StreamlitChatMessageHistory, 44 UpstashRedisChatMessageHistory, 45 XataChatMessageHistory, 46 ZepChatMessageHistory, 47 ) 49 from langchain.memory.buffer import ( 50 ConversationBufferMemory, 51 ConversationStringBufferMemory, 52 ) 53 from langchain.memory.buffer_window import ConversationBufferWindowMemory
File ~\anaconda3\lib\site-packages\langchain_community\chat_message_histories__init__.py:137, in getattr(name) 135 def getattr(name: str) -> Any: 136 if name in _module_lookup: --> 137 module = importlib.import_module(_module_lookup[name]) 138 return getattr(module, name) 139 raise AttributeError(f"module {name} has no attribute {name}")
File ~\anaconda3\lib\importlib__init__.py:126, in import_module(name, package) 124 break 125 level += 1 --> 126 return _bootstrap._gcd_import(name[level:], package, level)
File ~\anaconda3\lib\site-packages\langchain_community\chat_message_histories\sql.py:6 3 from abc import ABC, abstractmethod 4 from typing import Any, List, Optional ----> 6 from sqlalchemy import Column, Integer, Text, create_engine 8 try: 9 from sqlalchemy.orm import declarative_base
File ~\anaconda3\lib\site-packages\sqlalchemy__init__.py:12 8 from future import annotations 10 from typing import Any ---> 12 from . import util as _util 13 from .engine import AdaptedConnection as AdaptedConnection 14 from .engine import BaseRow as BaseRow
File ~\anaconda3\lib\site-packages\sqlalchemy\util__init__.py:15 12 from typing import TYPE_CHECKING 14 from . import preloaded as preloaded ---> 15 from ._collections import coerce_generator_arg as coerce_generator_arg 16 from ._collections import coerce_to_immutabledict as coerce_to_immutabledict 17 from ._collections import column_dict as column_dict
File ~\anaconda3\lib\site-packages\sqlalchemy\util_collections.py:38 35 import weakref 37 from ._has_cy import HAS_CYEXTENSION ---> 38 from .typing import is_non_string_iterable 39 from .typing import Literal 40 from .typing import Protocol
File ~\anaconda3\lib\site-packages\sqlalchemy\util\typing.py:56 54 from typing_extensions import TypeGuard as TypeGuard # 3.10 55 from typing_extensions import Self as Self # 3.11 ---> 56 from typing_extensions import TypeAliasType as TypeAliasType # 3.12 58 _T = TypeVar("_T", bound=Any) 59 _KT = TypeVar("_KT")
ImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (C:\Users\titik\anaconda3\lib\site-packages\typing_extensions.py)
how to solve this??

refer to above comments

i am facing the same issue; and i have seen above comments. the issue is bit different kindly help me with it,thanks.
iImportError: cannot import name 'TypeAliasType' from 'typing_extensions' (/opt/conda/lib/python3.10/site-packages/typing_extensions.py)
downgrading typing extension and pydantic shows the following errors:
albumentations 1.4.10 requires pydantic>=2.7.0, but you have pydantic 1.10.11 which is incompatible.
albumentations 1.4.10 requires pip install typing_extensions==4.9.0, but you have typing_extensions==4.5.0 which is incompatible.

if i go with the typing_extensions==4.5.0 and  pydantic>=2.7.0, it shows the first error typeAlias error

pydantic==1.10.11 typing_extensions==4.7.0
I tried to install this previous versions and it didn't like it. So I installed:
!pip install pydantic>=2.5.0 and !pip install typing_extensions>=4.6.0
Then I restarted the Kernel from my env and it did work!


Fix trigger for debug_session.*  events

Right now we're collecting trigger = "python" when it should be launch, test or attach (https://github.com/microsoft/vscode-python/blob/aa5defc63e3ab680646c7bffda8e2611cdaef901/src/client/telemetry/index.ts#L346)

Checked our telemetry events, the new property value appears for Insiders installs.


selection.extend is called on selection without ranges

Summary
In our application we have multiple draft-js instances. When users try to drag entities from one editor to the other, the selection state is temporarily lost and we end up with the following error:
Failed to execute 'extend' on 'Selection': This Selection object doesn't have any Ranges.
We were able to recreate the issue and the following PR fixes the issue by verifying that the selection has ranges.
Test Plan
This particular file does not appear to have any active spec files, but I did confirm that the solution works for both when there is a selection and when there is not an active selection.

Our application includes multiple draft-js instances as well that are encountering this exception upon startup of the application for all users after upgrading to Chrome 58, leaving React in a broken state (i.e. app is unresponsive/hangs).  We've verified that this pull request addresses the issue.

@flarnie Any change you could merge in either:
https://github.com/facebook/draft-js/pull/1190
https://github.com/facebook/draft-js/pull/1192
https://github.com/facebook/draft-js/pull/1203
They are all addressing the same issue. I don't care if it's mine you choose, as long as the bug is squashed!!!
Much appreciated!

This is one of many great fixes we want to pull into Draft - I'm working on https://github.com/facebook/draft-js/issues/1244 in order to unblock landing things on Github again, but @spicyj might want to look at those fixes. We have also been looking into this bug internally.
Hoping to get some of these things landed and released soon, thanks for your work on this!

Awesome, thanks @flarnie, much appreciated!

So, I have also seen this but am pretty unconvinced that the fix is correct. Based on my reading of the code, we always add a range immediately before calling .extend here – so .rangeCount should never be zero. One time when I was able to reproduce this, it also seemed like calling .addRange again (even though it had already been called) fixed the selection's state so that .rangeCount was then 1.
If you have a consistent repro of this, could you try checking if you also see that? I'm thinking when we call addRange it could be something like:
selection.addRange(range);
if (selection.rangeCount === 0) {
  selection.addRange(range);
}

even though that doesn't make too much sense. It sounds like a Chrome bug to me. We can add a workaround for browser bugs but I like to understand them first – and finding a way to fix the selection instead of silently failing (as your proposal does) seems better.

Thanks @spicyj, I was able to reproduce the issue and your suggestion worked!!! I updated the PR.

Would anyone here be interested in digging through to figure out why Chrome has this issue? If you're feeling adventurous it might make sense to build Chromium from source and add logging to the Selection.prototype.addRange method to understand why it fails the first time but works the second time.

@sarmstrong - Since this looks like it's a Chrome bug, we'd like to get a non-Draft repro case and file a bug with Chrome. Then we can add a comment next to this work-around that references the bug report.
With that addition we would be happy to merge this. Thanks for your patience and let me know if you have questions. Thanks! 🙏

To be clear: it would be really helpful if anyone here could come up with a minimal repro of this issue without using Draft that demonstrates the issue. I'm not sure on the exact circumstances that make the bug reproduce, but if someone has time to try making something that would be helpful. I'd try:

make a page with one button and two contenteditable divs
when the button is clicked, set the selection into the first contenteditable div (using the same addRange+extend strategy as here), then set the selection into the second
try to figure out how to make it throw?

If anyone here has time to look into it that would help us out a lot. Otherwise, we'll hopefully have time to try ourselves sometime in the next few weeks.

Just an update - none of the core Draft.js folks have time this week to debug the Chrome bug causing this, and we'd still like to get more info there and file a bug with Chrome before adding this work-around to Draft.js. This PR is still on our radar, and we're happy to help with reviews or discussion if someone can continue looking into this.

From my understanding you still need a consistent reproduction? I can try and carve out some time this week and see if I can throw something together, would that help getting it out the door?

Sorry, one of my colleagues just informed me that I misread the request, I think I might be able to reproduce within the context of draft, but I'm not quite sure where to start w/o it and probably won't be able to find the carve out.

Sorry accidentally closed this, after our scrum planning for the week, it doesn't look like I'll be able to get to this, alternately, we were able to get ourselves unblocked for the time being by refactoring some of the surrounding code so the request has become less urgent.

Just an update - we are starting to investigate filing a Chrome bug, and so if anyone picks this up please post here. ccing @paopaoF who may be picking this up

The most obvious way to maybe repro doesn't throw for me:
  <button id="button">boom</button>

first contenteditable

second contenteditable

I've been lurking on this issue because I had experienced this error myself around the time it was first reported. But, I just noticed that it's not popping up for me any longer. There's a chance its due to a code change on my end, but I'm wondering if Chrome may have fixed this already, especially given @spicyj's inability to repro just now?

@kgoggin Unfortunately I can still repro in Chrome 62.0.3175.0 canary with
function getFreshEditorState(text) {
  return EditorState.createWithContent(ContentState.createFromText(text));
}

class Demo extends React.Component {
  state = {
    editorStateFoo: getFreshEditorState('Foo'),
    editorStateBar: getFreshEditorState('Bar'),
  };

  handleClick = () => {
    this.setState(state => ({
      ...state,
      editorStateFoo: EditorState.moveFocusToEnd(getFreshEditorState('Foo')),
      editorStateBar: EditorState.moveFocusToEnd(getFreshEditorState('Bar')),
    }));
  }

  render() {
    return (

        <DraftEditor editorState={this.state.editorStateFoo} />
        <DraftEditor editorState={this.state.editorStateBar} />
        <button onClick={this.handleClick}>Ruin everything</button>

    );
  }
}

ReactDOM.render(
  <Demo />,
  container
);

and clicking the button.

THIS IS RELEVANT https://github.com/facebook/draft-js/blob/744e9b4eb4810797a93c66591fea6f9cac533b4b/src/component/handlers/edit/editOnBlur.js#L25-L33
That happens (synchronously) when we add the range causing the second contenteditable to be focused. Which is why there are no ranges after we call it.
This might not actually be a Chrome bug!

Changing editOnBlur to read:
  if (isWebKit && getActiveElement() === document.body) {
    const selection = global.getSelection();
    const editorNode = editor.refs.editor;
    if (
      selection.rangeCount === 1 &&
      containsNode(editorNode, selection.anchorNode) &&
      containsNode(editorNode, selection.focusNode)
    ) {
      selection.removeAllRanges();
    }
  }

fixes this I think. Will verify at Facebook and commit a permanent fix if so.

Is it possible to add this fix to 0.10 release as well? I'm experiencing an indexSize Error on selection.extend in IE11 when applying a entity on the editor state.
    // the reference needs to be added after the current selection, so we first need to create a new selection
    var newSelectionThatStartsAfterTheCurrentSelection = currentSelection.merge({
        anchorOffset: currentSelection.focusOffset,
        focusOffset: currentSelection.focusOffset
    });

    // insert empty text as a placeholder at that selection, to contain the reference icon that is displayed in the editor
    // after the word the user selected for the reference
    var newContentStateWithExtraSpaceAndReference = Modifier.insertText(
        newContentStateWithEntity,
        newSelectionThatStartsAfterTheCurrentSelection,
        ' ',
        undefined,
        lastCreatedEntityKey
    );

    return EditorState.push(newEditorStateWithEntity, newContentStateWithExtraSpaceAndReference, 'apply-entity');

Or does anyone know a workaround? I tried using forceSelection, this works in IE but causes problems later on when getting the active selection.

Has this fix been implemented yet in an available version? This is causing major headaches for people using an editor I built which has been functioning just fine for the past year. Basically can't do anything from within the editor that leads to focus being removed from the editor without an error being thrown. Buttons within the editor for initiating various types of edits are all throwing this error, and some url links which contain hash links within the page are also causing problems.
I've also moved on to React v16 now, and the issue is persisting.

@flarnie is hoping to do a 0.10.1 release soon which will include this fix.

It will be 0.10.2, and thanks @sophiebits - I'm waiting for https://github.com/facebook/draft-js/pull/1378 to land.

hello, this fix is not released yet ?

Hi @michelson -
Based on the logs and reports I have access to, this bug was fixed in v0.10.2 of Draft.js.
See the changelog for 0.10.2 - https://github.com/facebook/draft-js/releases/tag/v0.10.2

Fix pesky "This Selection object doesn't have any Ranges" bug (@sophiebits in 96688e10 and 036e3a84)

The fix was added by @sophiebits in https://github.com/facebook/draft-js/commit/036e3a848e3593c97f4c3011e1ddc045e128a7af under a feature flag, and the flag was opened/removed in https://github.com/facebook/draft-js/commit/96688e10b22a778c76e03009da4b9f3d05eba5f7
If you are still seeing this error in Draft v0.10.2 then please open a new issue and provide a repro case plus any other info you have.
Thanks!

HI @flarnie, thanks for your reply. I think I've hitting a related issue then.
not sure if it's my implementation. I've a custom component which has an input text field to edit the data from the component itself. The problem arises when I type outside the component, in other words, when I type over the editor text. For some reason when I type back (blur editor) in the input I get a chrome warning: [Deprecation] The behavior that Selection.addRange() merges existing Range and the specified Range was removed. See https://www.chromestatus.com/features/6680566019653632 for more details. and the typing on the input field gets clumsy
how could I clean the ranges properly in order to make this work in Chrome?
in firefox works fine

you can see video example at http://recordit.co/9690tkLIzh

Similar issue still exists.
Faced with this in Safari (only) when Draft.js is updating the editor state.
The error which I see: IndexSizeError: The index is not in the allowed range.
My solution / hack:
  const nativeSelectionExtend = Selection.prototype.extend;

  Selection.prototype.extend = function (...args) {
    try {
      return nativeSelectionExtend.apply(this, args);
    } catch (error) {
      console.log('Selection error.', error);
    }
  };

It works properly for me. Maybe will be useful for somebody as well.

Similar issue still exists.
Faced with this in Safari (only) when Draft.js is updating the editor state.
The error which I see: IndexSizeError: The index is not in the allowed range.
My solution / hack:
  const nativeSelectionExtend = Selection.prototype.extend;

  Selection.prototype.extend = function (...args) {
    try {
      return nativeSelectionExtend.apply(this, args);
    } catch (error) {
      console.log('Selection error.', error);
    }
  };

It works properly for me. Maybe will be useful for somebody as well.

Which file did you add this code?

@lvdang
Actually, in any file. But better to add in any root file, which will be initialized only once to avoid incorrect behavior during hot reload.
Or to make sure you can add additional check:
if (Selection.prototype.extend.toString().includes('[native code]')) {
  const nativeSelectionExtend = Selection.prototype.extend;

  Selection.prototype.extend = function (...args) {
    try {
      return nativeSelectionExtend.apply(this, args);
    } catch (error) {
      console.log('Selection error.', error);
    }
  };
}

@shpakkdv  - thanks


Add support for kitty icat image preview

Kitty terminal provides image preview fucttion which is ...well a bit more high res than the current one.So maybe an option to get it would be nice.

Since my goal is to make GPTerminal as portable as possible, it doesn't make much sense for me to add this functionality since it may not work for most terminals, though I am open to suggestions for another solution to the low resolution previews!


started conversion to TokenAddress instead of TokenCode

#WIP
Converting tokencode to tokenaddress

Closing in favour of #230


App should remember the sleep time set

When I close the App after setting the sleep time and consequently setting notifications, when I reopen the App, it should open with the time I had set already, but this doesn't happen currently.
It would be nice to see the already set time when the App is reopened.

The application should open with your default wake up time set to the current wake up time. I was thinking of storing a temp time just in case the preference of the user was different then the time they had chosen for that particular night.

Yes, having user preferences for such stuff should be good. You just have to plan out the UI/UX for this so that it's easy for the user to manage his/her preferences and also know the default settings


Add offscreen page limit

Summary
I need this so deeply https://developer.android.com/reference/androidx/viewpager2/widget/ViewPager2#setOffscreenPageLimit(int)
Basically, I have a ton of things rendered on pages and do not want to optimize it, because it leads to some minor glitches
Before:
https://streamable.com/psex6e
After:
https://streamable.com/nq5yvb
Test Plan
Doesn't have too much impact unless the app is really packed with components.
Compatibility

OS
Implemented

iOS
❌

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[x] I added the documentation in README.md
[x] I updated the typed files (TS and Flow)

Oh god, now i see that you reverted to viewpager1.
So it won't be working.
What was the motivation beyond reverting this?

Oh god, now i see that you reverted to viewpager1.
You can point to next branch
What was the motivation beyond reverting this?
Lots issues regarding to touching events.


Fixes windows and make tests presubmits

Issue #, if available:
Description of changes:

The windows update logic was flawed in the way it was trying to get the config layer to pull put the buildinfo. This switches to skopeo instead using buildx for this part.
Fixes the golang make tests by mocking the version instead of relying on the one set in the makefile. this will allow us to avoid having to update these data files everytime we bump go versions.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Attribute to rename generated method names

While we're adopting is-macro in tbot, we found that translation to snake_case may yield a bit unexpected results around digits. For this enum, I would expect that the generated is_ method would be named is_video_mp4, not is_video_mp_4 (notice the underscore before the number):
#[derive(Is)]
pub enum MimeType {
    …
    /// The `video/mp4` MIME type.
    VideoMp4,
}

Such cases should probably be left to humans, because one might actually expect an underscore inserted between a word and a digit. I suggest an attribute, setting which changes the generated method names:
#[derive(Is)]
pub enum MimeType {
    …
    #[is(root = "video_mp4")]
    VideoMp4,
}

With this attribute, Is would generate is_video_mp4 instead of is_video_mp_4. If it were possible for this variant, it would also emit expect_video_mp4 and video_mp4 instead of expect_video_mp_4 and video_mp_4. This can be extended in the future with ability to choose names for each method or change their prefixes. The only downside to this is a more complicated implementation. Also, if this is going to be implemented, we should probably come up with a better name than root.
(by the way, we really appreciate this crate for generating expect_ and taking methods, and also that we don't have to manually implement is_ methods 😀)

I fixed it and published<EMAIL_ADDRESS>You can rename the variant like is(name = "video_mp4")


feat: restructure core by component

What this PR changes/adds
move all the core folders into the core folder, grouped by the component they are needed by:
core
├── common
│   ├── base
│   ├── boot
│   ├── policy-engine
│   └── policy-evaluator
├── control-plane
│   ├── contract
│   ├── control-plane-core
│   └── transfer
├── data-plane
│   ├── data-plane-core
│   └── data-plane-framework
├── data-plane-selector
│   └── data-plane-selector-core
└── federated-catalog
    ├── federated-catalog-cache
    └── federated-catalog-core

Why it does that
To accomplish project structure review
Further notes

All the chickens are coming home to roost :chicken: :rooster: :chicken:
As already reported in #1832: we need to untangle the policy knots, let's talk about this in the discussion: #1836
I'm not really sure why boot and base are separated, they could be the same module, and they are used pretty much always together (unifying them plus refactoring the policy ones could avoid that ugly common folder)
inlined selector-store into selector-core, as it was only a default provider for the DefaultDataPlaneInstanceStore
inlined catalog and substituted by federated-catalog-core
introduced control-plane-core and inlined defaults, as it was pretty straightforward. Seems like the core module of a specific component is the right place where to declare default components to-be registered by extensions
I have a doubt about selector-api and selector-client, they are extensions used to build a data-plane-selector, but at the same time could a data-plane-selector exist without them? if not, I would put them as core modules for data-plane-selector, but they are completely fine as exception as they are.

Linked Issue(s)
Closes #1809
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1842 (9f41c38) into main (9841a4e) will decrease coverage by 56.59%.
The diff coverage is 0.00%.

:exclamation: Current head 9f41c38 differs from pull request most recent head 08e398d. Consider uploading reports for the commit 08e398d to get more accurate results

@@              Coverage Diff              @@
##               main    #1842       +/-   ##
=============================================
- Coverage     67.48%   10.89%   -56.60%
- Complexity        0      483      +483
=============================================
  Files           778      778
  Lines         16602    16603        +1
  Branches       1084     1084
=============================================
- Hits          11204     1809     -9395
- Misses         4930    14709     +9779
+ Partials        468       85      -383

Impacted Files
Coverage Δ

...dataspaceconnector/core/CoreServicesExtension.java
0.00% <ø> (ø)

...onnector/core/base/CommandHandlerRegistryImpl.java
0.00% <ø> (ø)

...aspaceconnector/core/base/OkHttpClientFactory.java
0.00% <ø> (ø)

...core/base/RemoteMessageDispatcherRegistryImpl.java
0.00% <ø> (ø)

...r/core/base/agent/ParticipantAgentServiceImpl.java
0.00% <ø> (ø)

...econnector/core/base/policy/PolicyContextImpl.java
0.00% <ø> (ø)

...ceconnector/core/base/policy/PolicyEngineImpl.java
0.00% <ø> (ø)

...ctor/core/base/policy/RuleBindingRegistryImpl.java
0.00% <ø> (ø)

...taspaceconnector/core/base/policy/ScopeFilter.java
0.00% <ø> (ø)

...nector/core/defaults/DefaultServicesExtension.java
0.00% <ø> (ø)

... and 646 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

boot vs base: they're separate because they serve distinct purposes: boot takes care of runtime boostrap and extension loading, whereas base provides some basic (but optional) features. Some runtimes will only require the boot module for bootstrapping, but will not need the base module. Thus having them separate still makes sense to me.

ok

selector-store: as per the (updated) documentation, a default provider for a service should be in its own extension, even if it does not use any other injected fields.
control-plane-core: I would rename the ControlPlaneCoreExtension to something like DefaultStoresExtension or something to clearly state what it's doing.
federated-catalog-core is empty, except for a build file. on purpose?

These three points are strictly related, in my opinion every component should have a "core" extension that defines the base services and the default ones, for the control plane is ControlPlaneCoreExtension, and for the data-plane-selector is DataPlaneSelectorExtension.
data-plane and federated-catalog have no default services, that's why their -core module is just a BOM build file.
Having a -core module that gathers the base needed dependencies and that provides the default services will permit extenders to just add that dependency on their build file and then extensions on top of it (this idea could be part of #1596).
Seems a clean pattern to me

selector-api and selector-client: architecturally, a data-plane-selector should not need them. For example when running the selector embedded. They are only needed when the selector runs in its own process (e.g. as pod in a K8s). If there is currenlty a dependency it should be cleaned up (in another PR, I can help out in that regard)

Ok

minor nit: in some files the Copyright seems to have been captured by BMW :) e.g.  ControlPlaneCoreExtension - the original Copyright is by Microsoft. could have happened in others as well.

Fixed

I like the -core module pattern, that is fine.
However:

selector-store: as per the (updated) documentation, a default provider for a service should be in its own extension, even if it does not use any other injected fields.

The problem there is that it is the same extension (DataPlaneSelectorExtension) that does the @Inject-ing and @Provider-ing of the same service (i.e. DataPlaneInstanceStore), which - according to the documentation - should be avoided. For now it would be sufficient to just have another extension in the data-plane-selector-core module, that only contains the provider method. As a future enhancement, that should to be cleaned up further, e.g. by renaming the store to InMemory-, and providing it from another module etc.

federated-catalog-core is empty, except for a build file. on purpose?

These three points are strictly related, in my opinion every component should have a "core" extension that defines the base services and the default ones, for the control plane is ControlPlaneCoreExtension, and for the data-plane-selector is DataPlaneSelectorExtension. data-plane and federated-catalog have no default services, that's why their -core module is just a BOM build file.

OK that's fine, but now we have
federated-catalog-cache <-- contains code
federated-catalog-core <-- contains only the bom

could we just merge/move everything from -cache over to -core?


Countdown Background

Title and Issue number

Title : Website Count Down Page Background invisible
Issue No. : #221
Code Stack : CSS
Close #221

Video (mandatory)

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have updated the projectData.json file for my contribution
[ ] I have added the img of my project in the assets/img section

Additional context (Mandatory )
Are you contributing under any Open-source programme?

CodePeak'23

@Preeti8021  great! But please remember to give screenshot or video about the changes you did from next time 😊

Sure, thank you 😊


Upload Validator Separator token in tags

I have uploaded the validator forValidator for separator token in tags    https://github.com/osmlab/osmlint/issues/233
@Rub21   Could you please check it?

@dannykath  could you clean up the comments and also add the description in readme.m


phpexcel to phpspreadsheet package update

Updated the project from old PHP excel to phpspreadsheet

@ddeboer hi, can u merge this?

HI @sankarsuda, you can use portphp/spreadsheet instead. I’m keeping this repository on PHPExcel for backwards compatibility.


Update supply script to use correct profile directory

Connected to #22
This PR updates the Conjur buildpack to install the secret retrieval script into profile.d instead of .profile.d.
It also updates the README to improve the examples for using the buildpack.
Jenkins build: https://jenkins.conjur.net/job/cyberark--cloudfoundry-conjur-buildpack/job/22-supply-profile-dir/

@izgeri, did you also want a chance to review these updates?


Assets Naming Convention

The component names (App.vue, Hello.vue) don't match to the Assets Naming Convention described in the docs.
Should be lowercase app.vue and hello.vew right?

@aristidesfl No, PascalCase is one of the acceptable options and either way, those conventions do not apply to file names.

@chrisvfritz the documentation has kebab-case file names and doesn't say the convention doesn't apply to them.

The documentation explains why the conventions exist and what Vue is doing, so that if you think about it, there would be no reason for them to apply to file names. And as I said before, it's a moot point anyway. Even if you chose to interpret file names as having to conform to the same conventions, PascalCase IS one of the acceptable options listed.

Vue explains the technical reasons why the convention exists, but that is not the only reason a convention might exist.
If the section of the documentation which talks about technical enforced conventions exemplifies naming of related things (file names) which could also benefit from a convention they are relevant even if for a different reason.
PascalCase does NOT seem to appear in any of the examples of the section. Many other naming conventions would also be acceptable. But maybe using case insensitive file names isn't such a bad idea because of file system incompatibility and version control.
Nevertheless, maybe it is not a good idea for the documentation to promote a different convention than the one used in the official templates, one way or another.


Tags Pinyin input method problem－－标签拼音输入法问题

The label when using Pinyin input method, found that most can only play three words, and more than three will automatically enter, seek to resolve under author
Thank you hope to get the author's reply
标签使用拼音输入法时，发现最多只能打三个字， 而且超过三个会自动enter，求作者解决下

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35514896-tags-pinyin-input-method-problem?utm_campaign=plugin&utm_content=tracker%2F16419772&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F16419772&utm_medium=issues&utm_source=github).

不太明白，可以截图或者截一段视频么？


[FEATURE]: useLiveQuery skip param

Describe what you want
I'm running into an issue where I have to create an unnecessary child component to handle cases where a dependent variable has yet to be defined.
I think it could look something like this:
export const useLiveQuery = <T extends Pick<AnySQLiteSelect, '_' | 'then'> | SQLiteRelationalQuery<'sync', unknown>>(
	query: T,
	{skip}: {skip: boolean} // <---- Take in skip boolean
) => {
	const [data, setData] = useState<Awaited<T>>(
		(is(query, SQLiteRelationalQuery) && query.mode === 'first' ? undefined : []) as Awaited<T>,
	);
	const [error, setError] = useState<Error>();
	const [updatedAt, setUpdatedAt] = useState<Date>();

	useEffect(() => {
		const entity = is(query, SQLiteRelationalQuery) ? query.table : (query as AnySQLiteSelect).config.table;

		if (is(entity, Subquery) || is(entity, SQL)) {
			setError(new Error('Selecting from subqueries and SQL are not supported in useLiveQuery'));
			return;
		}

		let listener: ReturnType<typeof addDatabaseChangeListener> | undefined;

		const handleData = (data: any) => {
			setData(data);
			setUpdatedAt(new Date());
		};
                // Adding the skip check here allows for validation above but prevents the query from firing and listener from registering
                if (skip) return;
		query.then(handleData).catch(setError);

		if (is(entity, SQLiteTable) || is(entity, SQLiteView)) {
			const config = is(entity, SQLiteTable) ? getTableConfig(entity) : getViewConfig(entity);
			listener = addDatabaseChangeListener(({ tableName }) => {
				if (config.name === tableName) {
					query.then(handleData).catch(setError);
				}
			});
		}

		return () => {
			listener?.remove();
		};
	}, [skip]);

	return {
		data,
		error,
		updatedAt,
	} as const;
};

A developer may want to know if something has been skipped, so we may need to handle that case as well, but I think keeping it simple to start would be best.
I could open a PR and check all of this out if the above seems acceptable?

I was just looking for this feature. Would be great for this to be merged or something like this to be supported.


Request to add the Desikan-Killiany-Tourville human brain labeling protocol

It would be really nice to add the Desikan-Killiany-Tourville brain labeling protocol that is now used by default by the Mindboggle (http://mindboggle.info) and FreeSurfer software packages.
Here is a list of the labels:
http://mindboggle.readthedocs.io/en/latest/labels.html
Here is the primary reference article:
101 labeled brain images and a consistent human cortical labeling protocol
Arno Klein, Jason Tourville. Frontiers in Brain Imaging Methods. 6:171.
http://dx.doi.org/10.3389/fnins.2012.00171

Thank you for pointing me to this.  I'll ping you again if I have more questions/updates. Best!

@satra @binarybottle cc @jgrethe
I think that I have interpreted what is going on in mindboggle.mio.DKTprotocol correctly. I have produced two files, one for the DKT regions and sulci and one for the mindboggle labels (i.e. the set from DKTprotocol.label_numbers and DKTprotocol.label_names). The source file that does the transformation is https://github.com/tgbugs/pyontutils/blob/master/pyontutils/parc_mndbgl.py.
A first pass at the output can be seen on the parcellation branch in dkt-labels.ttl and mndbgl-labels.ttl. The artifacts can be seen here and here in parcellation-artifacts.ttl.
I do not know whether you want to deal with, nor how to deal with, representing the pair lists that define the sulci in the ontology. I'm guessing that it is probably best to leave that to mindboggle?
Please let me know it seems like I am on the right track. Thanks!

@tgbugs - the labels change from DKT to DTK near the sulcal transition in the ttl file.
regarding the label themselves. the DKT protocol is exactly the same protocol in mindboggle and freesurfer. so in some sense they will share these labels and any software that uses the freesurfer or mindboggle atlases.
regarding how to turn the sulci into rdf relations we will have to introduce a specific notion of bounded by to associate sulci to the labels. but this starts getting into the weed of anatomical provenance for any parcel. hopefully that's something that can be standardized into a set of concepts across atlas creation.

@satra
I'm working on a notion of landmarks for naming in parcellation schemes. Right now it is only developed for point based landmarks, but it should generalize to curves on a surface or 1d curves in a 3d space. The 'unbounded parcellation region' rightmost in the image in https://github.com/SciCrunch/NIF-Ontology/blob/master/docs/brain-regions.org#tables, is equivalent I think. If we classify the sulci labels as being attached landmarks of that sort can we safely leave the specification of their contour to the implementations?

@tgbugs - will have to think about this one a bit. over the years, we have defined sulci using various methods. almost all of them end up equivalent to having neighboring landmarks, but not always. and those landmarks are not always regions. in mindboggle, because we rely on the DKT atlas, we can use it in a way to find the central sulcus.
however, see: https://www.coursera.org/learn/medical-neuroscience/lecture/wJ4kL/finding-the-central-sulcus for an alternate method.
i think key question is how methods like this get operationalized ? and perhaps more importantly how do two or more different approaches to getting at the same concept get treated equivalently or result in differences.

I agree about the importance of how a term is operationalized. I don't think we want to full operationaliziation in the ontology, but we do want to provide terms that experts can say do or do not map to some operationalization.
At the end of the day we want to be able to determine whether two concepts are scientifically equivalent. Hopefully it shouldn't matter which method we use to identify a sulculs, if it is a real thing there should be more than one way, but in order to demonstrate that scientifically we will want/need ontology terms that take the methodology into account, so that the provenance of the identification can be explicit, so that, for example, we can demonstrate the equivalence of a gross anatomically identified central sulcus and a mindboggle identified central sulcus.
I think that the goal for the ontology should probably be to link to a definition of the operationalization if one exists. So for the DKT sulci that would be the labels files or similar. Does this seem reasonable?

@tgbugs - sounds reasonable

@satra cc @jgrethe
I fixed the k/t switch and have switched to source the FreeSurfer ids directly from their git repo. They are now in freesurfer-labels.ttl.
Two questions:

All of the naming is provisional, at the moment. Do you know if there are commonly used abbreviations for the freesurfer labels as a whole? Also any other suggestions with regard to naming for this?
Since I am now source most of the labels from FreeSurfer directly does it still make sense to set up DKT under the mindboggle organization, (given that, for the moment, DKT is the only terminology associated with the mindboggle org)? I imagine that you would be one of the admins on that when we get that functionality implemented.


Breaking change: Fix initialising bug

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


_get_python_function_name does not work with classes

System Info
LangChain : v0.0.231
Who can help?
@hwchase17
Information

[X] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
Issue
convert_to_openai_function does not work as intended:

Classes are not supported
Any function without its source is not supported

Reproduce
from dataclasses import dataclass
from langchain.chains.openai_functions.base import (
    convert_to_openai_function,
)

@dataclass
class System:
    name: str
    ram: int

convert_to_openai_function(System)

Expected behavior
When calling langchain.chains.openai_functions.base.convert_to_openai_function, the subsequent call to _get_python_function_name fails because it tries to read source code (and cannot find it).
Something much simpler would be to access the __name__ attribute of the callable.

out of curiosity, any reason you're using data class instead of pydantic BaseModel for this?

I use dataclasses because:

it's built in the standard library (same reason for the attrs library)
I didn't encountered a use case where I needed more features

if pydantic is what requests is to urllib, i'll definitely look into it though


New labels as a part of testng-adaptor improvements

according to #558 and #610 requests, there were added additional labels for further adaptor improvements and plugins development;
testng-adaptor will now supply 4 additional labels into TestCases for easier filtering by suites / groups / classes / test names.

@baev please review it; not sure why it failed on first commit; seems like a network issue on npm processing.

@sskorol thanks for all the work!


Resetting the model doesn't if validation is used and field is invalid

In another try to reset a form, I do `formData = {}' to clean it.
However, I have noticed that this doesn't work for invalid fields using validation (email for instance)
Here's an example.
Try to set an invalid value on Email and click "Reset".

Yeah, because it's invalid, it technically doesn't have a value, so angular wont update the $viewValue. This is an angular problem. You may just have to update the $viewValue yourself :-(

OK I understand. What is the best way to reset a form then?

Great question... #168 is wondering about supporting this in the core... I think it may be nice. Basically it would require making a copy of the model on first render, then exposing some kind of function (probably on options) that could be called to reset the model to its original state. Would have to handle the model property of fields as well... Do you think that angular-formly is the right place to do that?

Alright, I think I've got this fixed. If you could please try this out, that would be great. I've made a beta release that has this feature. Please let me know if this fixes the issue for you. npm install<EMAIL_ADDRESS>

Sorry, should have given an example or docs. Here you go!
http://angular-formly.com/#/example/form-options/reset-model

I think they are 2 cool options! ;)
However, with this beta, my code broke! :D But it was because I was using the forms inside a popup toggled with ng-show, and my model was null at the beginning (I was using the null value to show/hide the popup). So I had the idea to use ng-if instead, and miraculously, my previous problem of models not being reset was gone even without using resetModel()! ^^
Then I am wondering if the resetModel method wouldn't be a good place to reset the validation.show flags if they were set after the form initialization. What do you think?

Ok, that's good to know. It shouldn't break if your model is null. I'll fix that. resetModel shouldn't impact the actual field itself. That wouldn't make sense in the api. And I was thinking about adding a resetFields method, but I don't think that would really make sense either...
Let me fix the null problem and then I think we're good to release this officially. What do you think?

Yeap it is OK for me.

There you go. Officially in 5.2.0!

Update, use 5.2.1 instead...

Hi @kentcdodds, any news about resetFields method?
I really need the option to swap my fields...
Think about it, that would be amazing! we could have 20 dynamics forms and only html line.
The formFields will be update via controller...

@SagiMedina, this is being tracked in #246. Unfortunately it's not as easy as you might think...

Thanks a lot for your fast response!
I'll check...
btw thank you for this amazing module!!


Referer header value change when submitting a form with JS

If you submit a form without JS the Referer headers is the correct URL including the query string, but if you use the Form component with JS the Referer is set to the pathname only and it strips the query string
Without JS
Referer: http://localhost:3000/write?id=6092de7ab361c7ceac921cc2

With JS
Referer: http://localhost:3000/write

does this still happen @sergiodxa?


Error with mne.bem.make_watershed_bem using the development version of Freesurfer

In the process of creating the boundary-element model meshes, I run into the following error when executing mne.bem.make_watershed_bem('fsaverage', overwrite=True) with the development version of Freesurfer (note that the error does not appear in the stable version):
File "/home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/nibabel/freesurfer/io.py", line 179, in read_geometry coords = np.fromfile(fobj, ">f4", vnum * 3).reshape(vnum, 3) ValueError: cannot reshape array of size 92098 into shape (650288644,3)
The complete console output is the following:
Running mri_watershed for BEM segmentation with the following parameters:

SUBJECTS_DIR = /usr/local/freesurfer/subjects
SUBJECT = fsaverage
Results dir = /usr/local/freesurfer/subjects/fsaverage/bem/watershed

Running subprocess: mri_watershed -useSRAS -surf /usr/local/freesurfer/subjects/fsaverage/bem/watershed/fsaverage /usr/local/freesurfer/subjects/fsaverage/mri/T1.mgz /usr/local/freesurfer/subjects/fsaverage/bem/watershed/ws

Mode:          use surfaceRAS to save surface vertex positions
Mode:          Saving out BEM surfaces

*********************************************************
The input file is /usr/local/freesurfer/subjects/fsaverage/mri/T1.mgz
The output file is /usr/local/freesurfer/subjects/fsaverage/bem/watershed/ws

*************************WATERSHED**************************
Sorting...
      first estimation of the COG coord: x=127 y=142 z=110 r=85
      first estimation of the main basin volume: 2635318 voxels
      global maximum in x=96, y=97, z=106, Imax=255
      CSF=16, WM_intensity=110, WM_VARIANCE=0
      WM_MIN=109, WM_HALF_MIN=109, WM_HALF_MAX=110, WM_MAX=110
      preflooding height equal to 25 percent
done.
Analyze...

      main basin size= 2220668 voxels, voxel volume =1.000
                     = 2220668 mmm3 = 2220.668 cm3
done.
PostAnalyze...
      ***** 0 basin(s) merged in 1 iteration(s)
      ***** 0 voxel(s) added to the main basin
done.

****************TEMPLATE DEFORMATION****************

      second estimation of the COG coord: x=129,y=126, z=109, r=12780 iterations
^^^^^^^^ couldn't find WM with original limits - expanding ^^^^^^

   GLOBAL      CSF_MIN=19, CSF_intensity=38, CSF_MAX=51 , nb = 38178
 (2) Problem with the least square interpolation in GM_MIN calculation.

                     CSF_MAX  TRANSITION  GM_MIN  GM
    GLOBAL
  before analyzing :    51,      44,        21,   67
  after  analyzing :    42,      44,        44,   49
      mri_strip_skull: done peeling brain
      highly tesselated surface with 10242 vertices
      matching...78 iterations

*********************VALIDATION*********************
curvature mean = -0.012, std = 0.010
curvature mean = 75.679, std = 7.749

No Rigid alignment: -atlas Mode Off (basic atlas / no registration)
      before rotation: sse = 5.32, sigma = 9.30
      after  rotation: sse = 5.32, sigma = 9.30
Localization of inacurate regions: Erosion-Dilation steps
      the sse mean is  6.22, its var is 11.52
      before Erosion-Dilatation  3.79% of inacurate vertices
      after  Erosion-Dilatation  0.00% of inacurate vertices
      Validation of the shape of the surface done.
Scaling of atlas fields onto current surface fields

********FINAL ITERATIVE TEMPLATE DEFORMATION********
Compute Local values csf/gray
Fine Segmentation...37 iterations

      mri_strip_skull: done peeling brain

Brain Size = 2029869 voxels, voxel volume = 1.000 mm3
           = 2029869 mmm3 = 2029.869 cm3

      outer skin surface matching...173 iterations

******************************
Saving /usr/local/freesurfer/subjects/fsaverage/bem/watershed/ws
done
mri_watershed utimesec    288.051490
mri_watershed stimesec    0.183948
mri_watershed ru_maxrss   472268
mri_watershed ru_ixrss    0
mri_watershed ru_idrss    0
mri_watershed ru_isrss    0
mri_watershed ru_minflt   91446
mri_watershed ru_majflt   0
mri_watershed ru_nswap    0
mri_watershed ru_inblock  0
mri_watershed ru_oublock  35688
mri_watershed ru_msgsnd   0
mri_watershed ru_msgrcv   0
mri_watershed ru_nsignals 0
mri_watershed ru_nvcsw    5558
mri_watershed ru_nivcsw   3861
mri_watershed done
Traceback (most recent call last):
  File "mne_processing.py", line 52, in <module>
    mne.bem.make_watershed_bem('fsaverage', overwrite=True)
  File "</home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/mne/externals/decorator.py:decorator-gen-45>", line 2, in make_watershed_bem
  File "/home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/mne/utils/_logging.py", line 89, in wrapper
    return function(*args, **kwargs)
  File "/home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/mne/bem.py", line 1128, in make_watershed_bem
    read_metadata=True)
  File "</home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/mne/externals/decorator.py:decorator-gen-36>", line 2, in read_surface
  File "/home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/mne/utils/_logging.py", line 89, in wrapper
    return function(*args, **kwargs)
  File "/home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/mne/surface.py", line 580, in read_surface
    ret = _get_read_geometry()(fname, read_metadata=read_metadata)
  File "/home/rbcx/miniconda3/envs/eeg/lib/python3.6/site-packages/nibabel/freesurfer/io.py", line 179, in read_geometry
    coords = np.fromfile(fobj, ">f4", vnum * 3).reshape(vnum, 3)
ValueError: cannot reshape array of size 92098 into shape (650288644,3)

For now, the only solution I found was to use the stable version (6.0.0) of Freesurfer.

apparently it's the surface file produced whose format has changed and
causes nibabel reader to crash. Can you share the file?
It's more likely to be a nibabel issue than an MNE issue.

I don't think this will fix any development version surface reading

I mean I don't think my PR did

This is a FreeSurfer bug, see https://github.com/freesurfer/freesurfer/issues/699

Thanks for the info @larsoner


cachedQueries field in usage insights is not getting updated

See the issue description for cloudwatch for some background info. That issue affects redshift and athena when going through the async query flow. This is because we bypass cache in DataSourceWithAsyncBackend when performing an async query.

It's currently not being cached because when we implemented the async queries, we didn't want to cache when we sent a response for a still running query to the frontend. (In async queries the frontend polls periodically until it gets a done response) If we cached a still running response, then the query would never finish. It depends on how the code is laid out, but the solution would probably be to only cache "done" responses with actual data.

Done in https://github.com/grafana/grafana-aws-sdk/pull/85 , https://github.com/grafana/grafana/pull/71682 , and #17


Fix typo “enviroment”

develop :)

Based on the merge conflict, it looks like this has already been fixed in develop via #187.
Do we have a process for moving things into main and releases? That typo fix is about a year and a half old, so we should probably get it out into the world soon 🙂

Already fixed on the develop branch, closing unmerged as a duplicate of https://github.com/conda-incubator/setup-miniconda/commit/8ca9e40cc6af21c75a0d82fde604ad61fb01cf49 🙈


Help Needed : How to parameterize the file name in QAFTestDataProvider

Hi Team,
I have a requirement to parameterize the csv file name in the QAFTestDataProvider. But it needs to be a constant. I tried using a String variable. But i was not able to do that.
@QAFDataProvider(dataFile = {File will be selected during run time})
Could you please let me know if there is any way to do this?
Best Regards,
CK

Please refer documentation, you can find information on how to override data provider.

Hi @cjayswal ,
Thank you very much :) That was my bad. I should have checked the documentation :)
Appreciate you taking your time to answer :)
Kindest regards,
CK


Device Request for: Mi Air Purifier 2H

Hi Merdok,
Sorry in advance, if I post this in the wrong section. Would it be possible to add support for Xiaomi Air Purifier 2H; zhimi.airpurifier.mc2 .

Hi,
unfortunately the zhimi.airpurifier.mc2 is not a miot device. It uses the old miio protocol.

Hi,
I see. I appreciate the quick response and wish you and the project well.

Hi, i actually found a way to support older devices with the miot protocol. You should now be able to control the Mi Air Purifier 2H using this plugin from version 0.9.0. But for that device you need to specify your MicCoud credentials.  You can try it out and let me know!

Thanks for taking the time to implement the miot protocol! I have salvaging Github for a newer and maintained plugin. I'll try it out and update you later. Thanks again!

I followed the instructions where I filled the required fields hereby Device ID, Token and Mi Account ID + Password (Tried with/without Force Micloud ID).
Please let me know, if I should follow other procedures for installation or reporting logs.
Log:
[31/05/2021, 01:28:35] [miot] [AirPurifier] Connected to device: zhimi.airpurifier.mc2
[31/05/2021, 01:28:35] [miot] [AirPurifier] Setting up device!
[31/05/2021, 01:28:35] [miot] [AirPurifier] Doing device specific setup
[31/05/2021, 01:28:35] [miot] [AirPurifier] Device requires MiCloud! Trying to connect!
[31/05/2021, 01:28:38] [miot] [AirPurifier] Successfully connected to MiCloud!
[31/05/2021, 01:28:38] [miot] [AirPurifier] Doing initial property fetch
[31/05/2021, 01:28:38] [miot] [AirPurifier] Device setup finished! Device ready, you can now control your device!
[31/05/2021, 01:28:38] [miot] [AirPurifier] Getting device info from MiCloud!
[31/05/2021, 01:28:54] [miot] [AirPurifier] Poll failed 3 times in a row! Stopping polling and trying to reconnect!
[31/05/2021, 01:28:54] [miot] [AirPurifier] Connected to device: zhimi.airpurifier.mc2
[31/05/2021, 01:28:54] [miot] [AirPurifier] Setting up device!
[31/05/2021, 01:28:54] [miot] [AirPurifier] Doing device specific setup
[31/05/2021, 01:28:54] [miot] [AirPurifier] Device requires MiCloud! Trying to connect!
(node:23607) UnhandledPromiseRejectionWarning: TypeError: Cannot convert undefined or null to object
at Function.keys ()
at ZhimiAirPurifierMc2._setupDeviceInternal (/usr/local/lib/node_modules/homebridge-miot/lib/protocol/MiotDevice.js:104:16)
at ZhimiAirPurifierMc2.setupDevice (/usr/local/lib/node_modules/homebridge-miot/lib/protocol/MiotDevice.js:233:7)
(Use node --trace-warnings ... to show where the warning was created)
(node:23607) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:23607) [DEP0018] 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.

Ok, seems that there are still some smaller issues which I need to resolve. Btw, what server is your device on? The more far away the server the worst the connection will be. You will have around the same delay as in the xiaomi home app.

I am connected to the DE server. I tried setting it to None and afterwards DE.

Can you also please post a homebridge debug log? I am interested to see if the poll failed due to high latency or another issue...

Hopefully, I have used the debug mode correctly on homebridge.

[31/05/2021, 17:51:48] [miot] [AirPurifierX1] Connected to device: zhimi.airpurifier.mc2
[31/05/2021, 17:51:48] [miot] [AirPurifierX1] Setting up device!
[31/05/2021, 17:51:48] [miot] [AirPurifierX1] Fetching device info.
[31/05/2021, 17:51:48] [miot] [AirPurifierX1] Doing device specific setup
[31/05/2021, 17:51:48] [miot] [AirPurifierX1] Device requires MiCloud! Trying to connect!
[31/05/2021, 17:51:48] [miot] [AirPurifierX1] Login in to MiCloud with username XXXXXX
[31/05/2021, 17:51:48] [miot] [AirPurifierX1] Got device info! Device firmware: 1.4.3_23101
[31/05/2021, 17:51:50] [miot] [AirPurifierX1] MiCloud - Login step 1
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] MiCloud - Login step 2
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] MiCloud - Login step 3
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] Successfully connected to MiCloud!
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] Doing initial property fetch
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] Splitting properties into chunks. Number of chunks: 1. Chunk size: 14
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] Device setup finished! Device ready, you can now control your device!
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] Getting device info from MiCloud!
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] Device connected!
[31/05/2021, 17:51:51] [miot] [AirPurifierX1] Successfully saved device info!
[31/05/2021, 17:51:53] [miot] [AirPurifierX1] Got device info from MiCloud:
undefined
[31/05/2021, 17:51:56] [miot] [AirPurifierX1] Splitting properties into chunks. Number of chunks: 1. Chunk size: 14
[31/05/2021, 17:51:56] [miot] [AirPurifierX1] Error on initial property request! FetchError: network timeout at: https://api.io.mi.com/app/miotspec/prop/get
[31/05/2021, 17:51:58] [miot] [AirPurifierX1] Poll failed! No response from device! Error: Error: No response or response empty!
[31/05/2021, 17:52:01] [miot] [AirPurifierX1] Splitting properties into chunks. Number of chunks: 1. Chunk size: 14
[31/05/2021, 17:52:06] [miot] [AirPurifierX1] Splitting properties into chunks. Number of chunks: 1. Chunk size: 14
[31/05/2021, 17:52:06] [miot] [AirPurifierX1] Poll failed! No response from device! Error: FetchError: network timeout at: https://api.io.mi.com/app/miotspec/prop/get
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Poll failed! No response from device! Error: Error: No response or response empty!
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Poll failed 3 times in a row! Stopping polling and trying to reconnect!
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Trying to reconnect
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Device diconnected!
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Connected to device: zhimi.airpurifier.mc2
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Setting up device!
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Doing device specific setup
[31/05/2021, 17:52:08] [miot] [AirPurifierX1] Device requires MiCloud! Trying to connect!
(node:25350) UnhandledPromiseRejectionWarning: TypeError: Cannot convert undefined or null to object
at Function.keys ()
at ZhimiAirPurifierMc2._setupDeviceInternal (/usr/local/lib/node_modules/homebridge-miot/lib/protocol/MiotDevice.js:104:16)
at ZhimiAirPurifierMc2.setupDevice (/usr/local/lib/node_modules/homebridge-miot/lib/protocol/MiotDevice.js:233:7)
(Use node --trace-warnings ... to show where the warning was created)
(node:25350) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:25350) [DEP0018] 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.

It seems like the device which you are trying to control is not available on the specified server? You said that your xiaomi home app is configured for Germany, right? Did you specify the property country to de, like country: "de"?

Ahhhh, i just noticed that i currently ignore the country and always connect to the Chinese server🤦  Well in that case that explains your issue, even if you specified the country... I will correct that today and post an update later which should fix that.

@BigConspiracy Please try out version 0.9.1. The country should now properly be used which you specified in the config.json.,

Sorry for the late reply. I just updated and restarted. It works perfectly!
Thank you very much. If I stumble upon anything, I'll update you :-)

I receive this error when trying to access the settings for the plugins besides that everything seems to be working :)

Good to hear that it is working now :)
And sorry about the settings issues, somehow that sneaked in... It should be fixed in version 0.9.2

I appreciate the support for older Mi devices even though that you didn't had to. I can see that you are constantly adding new devices (changelog) and must say. Thank you! You should post something or let someone be apple to buy you a coffee at least!

Thanks! That is true, I initially did not plan to support older devices with the plugin, but thanks to the MiCloud I can use the miot protocol to control even the older devices which makes this pretty straightforward. The biggest part was just to implement the MiCloud connection...
Anyway, there is a "Sponsor" link on the front page of the repository which can be used to buy me a coffee🙂 But I guess it is only visible on desktop.


Many to one input

The models accept a list of images and not only one image.

Baselines now accept as input list_of_image_ids -> caption


CredentialEventTypes.OfferReceived does not exist for typeof CredentialEventTypes

From tutorial https://aries.js.org/guides/0.4/tutorials/issue-a-credential#3-listening-for-incoming-credentials the following error is displaying
holder.events.on<CredentialStateChangedEvent>(CredentialEventTypes.CredentialStateChanged, async ({ payload }) => {
    switch (payload.credentialRecord.state) {
      case CredentialEventTypes.OfferReceived:
        console.log('received a credential')
        // custom logic here
        await holder.credentials.acceptOffer({ credentialRecordId: payload.credentialRecord.id })
      case CredentialState.Done:
        console.log(`Credential for credential id ${payload.credentialRecord.id} is accepted`)
        // For demo purposes we exit the program here.
        process.exit(0)
    }
  })

hi! Thanks for reporting this issue. It actually should be CredentialState.OfferReceived, nice catch!
Would you like to create a PR for this in the docs? Otherwise I'd be happy to pick this up.

@blu3beri apologies for late reply, I will try to create a pull request for the next one :)


Creating the encrypted disks while creating a new VM

Is this functionality available in Azure? As I cannot find any document saying if we can create the encrypted disks while creating a new VM. Also this must be supported in ARM templates too.

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

ID: d7c63605-95f5-0953-3cf6-1e9c50532c1d
Version Independent ID: 8731daa8-2c15-78f7-adac-151401c13b6c
Content: Enable Azure Disk Encryption for Windows IaaS VMs
Content Source: articles/security/azure-security-disk-encryption-windows.md
Service: security
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@Tarvinder91
Thanks for your feedback! We will investigate and update as appropriate.

@Tarvinder91 No, the VM needs to be pre-provisioned for Disk Encryption.  Please post this as a feedback https://feedback.azure.com/forums/347535-azure-security-center. This will allow the community to upvote and for the product team to include into their plans. "This Product" button in at the bottom section of the document now to take you directly to the appropriate feedback page.

Idea posted. Thanks.

@Tarvinder91 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Telnet Library: allow control over connection timeout

Aims to implement issue #2079. This still missing specific tests, but I should be able to create them soon. I've just fixed current tests to work with the new argument. Tests passed on my local machine.

Admin, can CI be enabled?

New arguments to keywords and library __init__ must be last (and have a default value) to avoid backwards compatibility issues. That rule can be broken in major releases if there are strong reasons, but even then it would require a deprecation period.

@jussimalinen, can you take care of reviewing and testing this PR when it gets more ready?

Updates to Telnet documentation may affect Libdoc tests that use Telnet as their test data. It would be great if you @vkruoso could run those tests and verify did something broke. I can help fixing tests if that turns out to be lot of work. It's not really related to Telnet anyway.

We plan to release RF 2.9.1 tomorrow. I doubt there's time to get this in, but we'll probably create 2.9.2 still before 3.0.

I've updated this PR to include tests and fix the issues pointed by you. The libdoc test suites were fixed to consider the new parameter. I think this is complete, but let me know if something is missing or we need more improvements.

Looks very good. A couple of comments:
Adding a default timeout to 2 minutes is a backwards incompatible change. We could break stuff from existing tests which rely on existing timeout behaviour and that is bad. So this should be changed so that by default is no timeout given to telnetlib.Telnet.init_. (So that underlying socket timeout is used in the end.)
Also, please add yourself to the AUTHORS.txt file!

 I've updated the PR. Code in the init method looks ugly to me, though. Can you think on a better way to do it?
I'm already in the AUTHORS file! :)

Thanks for the pull request! We went through it with @pekkaklarck and I added a few line comments.
We are not getting the socket.timeout with the address used in the tests. The trick of starting a python process that binds to a localhost port could maybe used to test the timeout functionality? It hopefully works consistently.

Thanks for the feedback @jussimalinen and @pekkaklarck!  I'll try to provide an update on this until the end of this weekend!

I'm taking a look at this and have some observations. I've tried your approach with no success in my local machine: instead of a socket.timeout exception I'm getting socket.error (connection refused) error. This seems reasonable as there is no call to listen on the socket so the server should deny any connection attempt. It seems odd that the behavior is the opposite in your machine. I'm running python 2.7.6, maybe that is the reason?
The initial idea is really not good because when trying to connect to a local address, packets will be sent to the gateway and behavior should differ depending on router configurations.

I thought both Jussi and I were able to get socket.timeout but now that I test it I get socket.error. If we cannot figure out how to test this reliably, it is fine to leave it untested. The change itself is pretty trivial anyway.

I've updated the PR removing the trap server. Will try to think about a way to test it reliably, but in any case it sounds reasonable if we can not figure it out. After the next release this will for sure be tested in a daily basis.

This looks good as it is. Thanks! I will add this feature to you contributions in AUTHORS

Thanks for the merge. Sorry I did not had the time to investigate further. Looking forward to use it in the next release tough.