Clarification needed

From the item description, this routine allows the driver to setup driver tracing and any related resources. The puzzler for me has to do with where do I park the pointers to these resources so that I can free them in CleanupTracing. Normally I would put resources in the appropriate extension such as DriverExtension, SrbExtension, etc. However, this routine is called by StorPort prior to the return from StorPortInitialize which is called from the driver in DriverEntry...our DriverExtension pointer has not yet been given to us. This happens at the next step FindAdapter. If the struct passed as the first pointer to DriverEntry (and subsequently passed to StorPortInitialize [and subsequently passed to InitializeTracing])  contains a pointer location for us to save our tracing allocated resources, then this page should document that. Presently, if tracing is to be used either a global must be used which is incompatible with multiple instance of the driver, or the driver will leak memory.
I am sure I am missing something simple and/or obvious, but, some clarification would help. Surely I am not the only one puzzled by this.

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

ID: fa837d0c-345b-8324-a85d-57509a71542c
Version Independent ID: 3b866097-878a-f845-d892-2c4b60c0c452
Content: HW_INITIALIZE_TRACING
Content Source: wdk-ddi-src/content/storport/nc-storport-hw_initialize_tracing.md
Service: unspecified
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

Hi @BenWestbrook, I received the following from the development team:
"we’re not expecting any resources to be needed to be able to initialize tracing. If miniport needs to allocate resource, then it’ll have to be a global as the callback is applicable to all instances of the driver."
Does this help answer your question?

From: aahill<EMAIL_ADDRESS>Sent: Wednesday, June 13, 2018 17:43
To: MicrosoftDocs/windows-driver-docs-ddi<EMAIL_ADDRESS>Cc: BenWestbrook<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-driver-docs-ddi] Clarification needed (#92)
Hi @BenWestbrook https://github.com/BenWestbrook , I received the following from the development team:
"we’re not expecting any resources to be needed to be able to initialize tracing. If miniport needs to allocate resource, then it’ll have to be a global as the callback is applicable to all instances of the driver."
Does this help answer your question?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/windows-driver-docs-ddi/issues/92#issuecomment-397111238 , or mute the thread https://github.com/notifications/unsubscribe-auth/ADgZ4wbk-8ailaxKXWIc80Z0f9Bnn0VGks5t8ZVbgaJpZM4UPUmj .  https://github.com/notifications/beacon/ADgZ4xfk5FiEg7-tavMq2ZLe_r4bh597ks5t8ZVbgaJpZM4UPUmj.gif

This does answer the question but not the problem. Clearly, the API would have provided access to the device extension if the development team anticipated the need.
However, there is a workaround if you do not need tracing in DriverEntry and FindAdapter. Shortly after the return from FindAdapter the function TracingEnableDisable is called, with the deviceExtension. Tracing can be enabled and allocations made at this point, and then cleaned up when called to disable tracing or driver unload.
Thank you for the follow up.
From: aahill<EMAIL_ADDRESS>Sent: Wednesday, June 13, 2018 17:43
To: MicrosoftDocs/windows-driver-docs-ddi<EMAIL_ADDRESS>Cc: BenWestbrook<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-driver-docs-ddi] Clarification needed (#92)
Hi @BenWestbrook https://github.com/BenWestbrook , I received the following from the development team:
"we’re not expecting any resources to be needed to be able to initialize tracing. If miniport needs to allocate resource, then it’ll have to be a global as the callback is applicable to all instances of the driver."
Does this help answer your question?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/windows-driver-docs-ddi/issues/92#issuecomment-397111238 , or mute the thread https://github.com/notifications/unsubscribe-auth/ADgZ4wbk-8ailaxKXWIc80Z0f9Bnn0VGks5t8ZVbgaJpZM4UPUmj .  https://github.com/notifications/beacon/ADgZ4xfk5FiEg7-tavMq2ZLe_r4bh597ks5t8ZVbgaJpZM4UPUmj.gif

No problem @BenWestbrook, glad I could provide some information. Thanks for posting your workaround, it'll help folks who look for similar info!


RunInference V1

Users of machine learning frameworks must currently implement their own transforms for running ML inferences. The exception is the TensorFlow RunInference transform. However, this is hosted in its own repo, and has an API that is exclusively geared towards the TensorFlow TFX library. Our goal is to add new implementations of RunInference for the two other popular machine learning frameworks: scikit-learn and Pytorch.
Please see main design document here.
Imported from Jira BEAM-13970. Original Jira may contain additional context.
Reported by: yeandy.

The following subtask(s) are associated with this issue: #21436, #21437, #21438, #21439, #21440, #21441, #21442, #21443, #21444, #21445, #21446, #21447, #21448, #21449, #21450, #21451, #21452, #21453, #21454


Takes too much of time when enter is hit at the start of the page.

I'm using atom on Macbook Air. I'm using version 1.33.0
While editing an already created page and try to create a new line on the top of the file atom doesnot respond.
It keeps saying wait or force close.
Immediate fix is much appreciated.

Thank you for contributing!
We require the issue template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests. Please open a new issue and fill out the template for us.
Thanks for understanding and meeting us half way :grinning:


Null pointer initialization. Redesign: typedef. Types correction.

This change is

Please fix merge conflicts and I will finish review.

Reviewed 7 of 17 files at r1, 1 of 3 files at r2.
Review status: 3 of 15 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

program/program.go, line 419 at r2 (raw file):

// IncudeHeaderIsExist - return true if C #include header is inside list
func (p *Program) IncludeHeaderIsExist(includeHeader string) bool {

IncludeHeaderExists

tests/struct.c, line 268 at r2 (raw file):

      { "write_bytes: ",            "Bytes written to storage:" },
      { "cancelled_write_bytes: ",  "Cancelled write bytes:"    },
    };

Can you add some tests to make sure these values are actually set?

Comments from Reviewable


HSEARCH-3523 + HSEARCH-3524 + HSEARCH-3525 + HSEARCH-3526 Allow integrators to pre-build Hibernate Search from Metadata + service registry, without a SessionFactory

https://hibernate.atlassian.net//browse/HSEARCH-3523
https://hibernate.atlassian.net//browse/HSEARCH-3524
https://hibernate.atlassian.net//browse/HSEARCH-3525
https://hibernate.atlassian.net//browse/HSEARCH-3526
Supersedes #1916.
So, this should be ready for review. Note that the Lucene backend is not ready for quarkus integration: I mainly worked on the Elasticsearch backend. We will have to open a follow-up ticket for Lucene.
@gsmet I made a change that should impact the Quarkus extension: I now use MethodHandles by default, and you need to substitute the code of org.hibernate.search.mapper.orm.model.impl.HibernateOrmBootstrapIntrospector#createPropertyHandleFactory in order to go back to java.lang.reflect (Method, Field). Replace the code of this method with this:
return PropertyHandleFactory.usingJavaLangReflect();

By the way, GitHub made a mess of the commits again, they are not in the right order...

Pull Request Test Coverage Report for Build 1

596 of 664 (89.76%)  changed or added relevant lines in 56 files are covered.
7 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.04%) to 88.679%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/client/impl/ElasticsearchClientUtils.java
14
15
93.33%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/dialect/impl/ElasticsearchDialectFactory.java
18
19
94.74%

backend/elasticsearch/src/main/java/org/hibernate/search/backend/elasticsearch/impl/ElasticsearchClientProvider.java
26
27
96.3%

engine/src/main/java/org/hibernate/search/engine/common/impl/BackendStartContextImpl.java
5
6
83.33%

engine/src/main/java/org/hibernate/search/engine/common/impl/IndexManagerBuildingStateHolder.java
29
30
96.67%

engine/src/main/java/org/hibernate/search/engine/logging/spi/MappingKeyFormatter.java
0
1
0.0%

mapper/pojo/src/main/java/org/hibernate/search/mapper/pojo/mapping/building/impl/PojoMapper.java
3
4
75.0%

engine/src/main/java/org/hibernate/search/engine/common/impl/BackendPartialBuildState.java
14
16
87.5%

engine/src/main/java/org/hibernate/search/engine/common/impl/SearchIntegrationPartialBuildStateImpl.java
39
41
95.12%

mapper/javabean/src/main/java/org/hibernate/search/mapper/javabean/mapping/impl/JavaBeanMappingPartialBuildState.java
4
6
66.67%

Files with Coverage Reduction
New Missed Lines
%

mapper/orm/src/main/java/org/hibernate/search/mapper/orm/model/impl/HibernateOrmRawTypeModel.java
1
87.64%

engine/src/main/java/org/hibernate/search/engine/common/impl/IndexManagerBuildingStateHolder.java
1
96.7%

mapper/orm/src/main/java/org/hibernate/search/mapper/orm/impl/HibernateSearchContextService.java
2
82.35%

engine/src/main/java/org/hibernate/search/engine/common/impl/SearchIntegrationImpl.java
3
76.0%

Totals

Change from base Build 173:
0.04%

Covered Lines:
16497

Relevant Lines:
18603

💛  - Coveralls

Addressed your remarks and rebased.

Discussed and approved on Zulip. Merged, thanks!


request for new EVP_DigestTransform API

Due to OpenSSL v3.0 deprecations qatlib can no longer use _Transform() APIs.
To resolve this, we'd like to request a new api
EVP_DigestTransform() to provide the intermediate hash for HMAC as previously provided by MD5_transform, SHAx_Transform, etc.
Example usage:
https://github.com/intel/qatlib/blob/878b00989b81625737df43ddb11a7e2f2377ea4c/quickassist/utilities/osal/src/linux/user_space/OsalCryptoInterface.c#L150
Note, the lower level APIs used here:
https://github.com/intel/qatlib/blob/878b00989b81625737df43ddb11a7e2f2377ea4c/quickassist/utilities/osal/src/linux/user_space/OsalCryptoInterface.c#L163
can be replaced by EVP APIs, but for the intermediate hash transform there is no EVP alternative available.

thanks for the rapid response

Marking as inactive, to be closed at the end of the 3.4 dev cycle, barring further input


OutOfMemory Java Heap error for ItemAttachments

for (int i = 0; i < attachments.size(); ++i)
{
    Attachment attachment = attachments.get(i);
    if (attachment instanceof FileAttachment)
    {
        FileAttachment fileAttachment = (FileAttachment) attachment;
        File file = File.createTempFile("ewsTest", ""); //$NON-NLS-1$ //$NON-NLS-2$
        fileAttachment.load(file.getAbsolutePath());

        // Do stuff with attachment
    }

    if (attachment instanceof ItemAttachment)
    {
        ItemAttachment itemAttachment = (ItemAttachment) attachment;
        itemAttachment.load(new PropertySet(ItemSchema.MimeContent)); // No file option?
        Item item = itemAttachment.getItem();
        if (item instanceof EmailMessage)
        {
            MimeContent mimeContent = item.getMimeContent();

            byte[] content = mimeContent.getContent(); // No stream option?
            // Write content to message.eml
        }
    }
}

The following line causes the exception with a message attachment that contains a large attachment
itemAttachment.load(new PropertySet(ItemSchema.MimeContent));
I'm able to get an item attachment by attaching an email message as an attachment.
A few questions:
Why doesn't the item attachment load not have an option to stream to file?
Is there a better way to save the email message attachment as an eml/msg/rfc822 file?
Is the solution to just increase the java memory (-Xmx2048m)?

Hi,
I'm able to reproduce this error. If the mime content is too big, the exception is thrown here :    this.content = Base64.decodeBase64(reader.readValue());
Is there a working solution in the community?

This issue has bitten one of our customers using our solution. It really needs the ability to stream to a file on disk rather than just consuming memory. Increasing RAM to 1 GB has avoided the problem, but it makes our solution much heavier than it normally needs to be on RAM use.


Select before insert

Hello!
I'm trying to switch from 0.3.2-patch7 to 0.3.2-patch10 and at the same time replace the usage of ru.yandex.clickhouse with com.clickhouse.
I noticed before each INSERT you're trying to perform prefetch column types, for example here - ClickHouseConnectionImpl.getTableColumns(). Yes, I investigated the code and understand the reason but is there ability to disable such behaviour? In that case you will use appropriate ClickHouseValue implementations based on the provided parameters or a custom implementation of the ClickHouseValue. (For example, at the moment there is no ability to customize SQL representation for inserting values.)
Why I'm asking about that? Firstly, because I know the types of data being inserted and don't want extra interaction with the database.
Thanks

Hi @AlexMAS, if you know the types, can you use input function like below? This way, the driver will simply parse the query to get metadata, instead of using additional query.
// create table mytable(id String, timestamp DateTime64(3), description Nullable(String)) engine=Memory

// 1. recommended as it performs the best
try (PreparedStatement ps = conn.prepareStatement(
    "insert into mytable select col1, col2 from input('col1 String, col2 DateTime64(3), col3 Int32')")) {
    // the column definition will be parsed so the driver knows there are 3 parameters: col1, col2 and col3
    ps.setString(1, "test"); // col1
    ps.setObject(2, LocalDateTime.now()); // col2, setTimestamp is slow and not recommended
    ps.setInt(3, 123); // col3
    ps.addBatch(); // parameters will be write into buffered stream immediately in binary format
    ...
    ps.executeBatch(); // stream everything on-hand into ClickHouse
}

@zhicwu Thank you for reply. Yes, the input() function works well but to be honest the query syntax in this case is quite verbose. It'll be great if you mention about the input() function in the project readme/wiki.
Then another question. Are there other alternatives besides the input() function. As I understand, JDBC Driver is just a wrapper over Client API? And we can use it directly. What is recommended way to work with ClickHouse? Are there any conceptual benefits to use JDBC (in terms of performance and resource management)?

Yes, the input() function works well but to be honest the query syntax in this case is quite verbose.

I agree. I wish ClickHouse supports prepared statement so that we don't have to do this.

It'll be great if you mention about the input() function in the project readme/wiki.

There's examples for batch insert at here but I guess it's hard to notice. Moving them to wiki is probably better.

Are there other alternatives besides the input() function.

If the data volume is not huge and you don't mind to keep them in memory(on ClickHouse server), you may try this but it will only make things unnecessarily complex.

As I understand, JDBC Driver is just a wrapper over Client API? And we can use it directly.

Yes, JDBC driver is a wrapper of Java client, and Java client hides implementation details like data format and protocol. Of course you can use Java client (examples) or more native approach to access ClickHouse like this. Alternatively, you can blend usage of JDBC and Java client, for instance: statement.unwrap(ClickHouseRequest.class).query("select 1").executeAndWait(), but it's not recommended because the code is no longer portable.

What is recommended way to work with ClickHouse? Are there any conceptual benefits to use JDBC (in terms of performance and resource management)?

It depends. If you prefer stable API and may change to a different database in the future, you'd better stay with JDBC and avoid non-standard syntax in SQL queries. If performance is critical and you can tolerate API changes(before 0.4.0), it's encouraged to use Java client. Performance-wise, JDBC is slower and it uses more memory compare to Java client. Below is the result took from here.
SELECT number FROM system.numbers_mt LIMIT 500000000

Name
Time
RAM

curl (C, HTTP, no deserialization)
3.7s
10M

clickhouse-client (Java, HTTP)
6.4s
121M

clickhouse-jdbc (Java, HTTP)
7.2s
120M

@zhicwu Thank you for so comprehensive reply! Probably the last question regarding Java Client API. How can I pass credentials (username and password)? I see overloads of the ClickHouseNode.of() but none of them accepts ClickHouseCredentials. Initially I expected something like this:
var credentials = ClickHouseCredentials.fromUserAndPassword("user", "password");
var node = ClickHouseNode.of("https://localhost", credentials);

Can I rely that the ClickHouseClient instance is thred-safe?

How can I pass credentials (username and password)?

Yes, you can add credentials in ClickHouseNode using its builder function, which helps when you need to connect to multiple nodes using different credentials.  You can also set default credentials at client level, for example:
ClickHouseClient client = ClickHouseClient.builder().defaultCredentials(...)...;
client.connect(<node>).query("select 1").executeAndWait();

Can I rely that the ClickHouseClient instance is thred-safe?

Yes it's thread safe. However, you probably don't have to create many client instances. Instead, you may reuse the client instance and create multiple ClickHouseRequest for queries. ClickHouseRequest is not thread-safe as of now.


fix(version): update fabric8-runtime-console to 0.13.0

There were the following issues with your Pull Request

Commit: 4ea7d232eefd872cb94cf85e79124eed6b08c9b0
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com


Review Sonar code smells

[ ] https://sonarcloud.io/project/issues?resolved=false&types=CODE_SMELL&id=hCaptcha_hcaptcha-android-sdk
[ ] https://sonarcloud.io/project/security_hotspots?id=hCaptcha_hcaptcha-android-sdk#

Can be closed after https://github.com/hCaptcha/hcaptcha-android-sdk/pull/68 merge, because we moving to our own configs/reports


Syntax Error

endpoints.gs is tossing a Syntax error on line 9081 now when you try to save the updated code on Google Scripts, looks like it may just be an extra bracket at the end? Seems to save fine and work properly if removed.

Good catch, fixed in 8dca879ed1329067c91580e5f4cd630527796d2c


[Topics] There are default values when user try to edit topic

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

When user try to edit topic after creation there are defaults values in edit topic settings view
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

Tested on http://pr2205.internal.kafka-ui.provectus.io/ branch, please merge.


find_messages not working

I'm trying to filter messages with your SDK but to no avail. What I'm trying to do:
mkm = Mkm(_API_MAP["2.0"]["api"], _API_MAP["2.0"]["api_root"])
response = mkm.account_management.find_messages(params={"unread": "false"})

But I always get a BAD REQUEST (400) error.
Ideally, I would like get this to work:
dt = datetime.datetime(2017, 1, 1)
response = mkm.account_management.find_messages(startDate=dt)

or even this:
response = mkm.account_management.find_messages(params={"startDate": "2017-01-01"})
But nothing seems to work. For reference, this is the API call I'm trying to do:
API-Find-messages
Thanks

From my understanding of the documentation if the unread parameter is used by itself it can only be set to true, so a 400 in that case it correct, probably they do so to avoid a too big response.
This one can't work, all parameters must be strings, there's no automatic conversion.
dt = datetime.datetime(2017, 1, 1)
response = mkm.account_management.find_messages(startDate=dt)

I've tried this exact request and it returned 2xx correctly for me, I can't reproduce the error.
response = mkm.account_management.find_messages(params={"startDate": "2017-01-01"})

What kind of error are you getting? Are you making a dedicated or a widget app? Widgets apps don't have access to any of the Account Management endpoints so that might be it.

Thanks for the fast reply. I have set up all the MKM_* environment variables and, in fact, I can do this without any issue:
response = mkm.account_management.get_all_threads()
I'm going to copy the whole script, just in case I'm missing some import or something:
#!/usr/bin/python3.4
from mkmsdk.mkm import Mkm
from mkmsdk.api_map import _API_MAP
import datetime

# Using API v2.0
mkm = Mkm(_API_MAP["2.0"]["api"], _API_MAP["2.0"]["api_root"])

response = mkm.account_management.find_messages(params={"startDate": "2017-01-01"})
print(response.status_code)
print(response.reason)
print(response.json())

And this is what I'm getting:
Traceback (most recent call last):
  File "messages-find.py", line 9, in <module>
    response = mkm.account_management.find_messages(params={"startDate": "2017-01-01"})
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/mkm.py", line 43, in __call__
    return self.resolver.resolve(api_map=self.api_map, **kwargs)
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/resolvers.py", line 61, in resolve
    return self.api.request(url=self.url, method=self.method, data=data, params=params, auth_params=auth)
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/api.py", line 42, in request
    return self.handle_response(response)
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/api.py", line 98, in handle_response
    raise exceptions.ConnectionError(response)
mkmsdk.exceptions.ConnectionError: Request failed
Status code: 400
Response message: Bad Request
b'{"mkm_error_description":"User with ID \\u00270\\u0027 doesn\\u0027t exist.","internal_error_code":null,"post_data_field":null,"http_status_code":400,"http_status_code_description":"Bad Request","rfc2616_description_link":"http:\\/\\/www.w3.org\\/Protocols\\/rfc2616\\/rfc2616-sec10.html"}'

So, basically a Bad Request (400) with some Exception that I can't understand (sorry I'm not a very fluent Python speaker...;-))

And, by the way, if I try this:
response = mkm.account_management.find_messages(params={"unread": "true"})
I get this:
  File "messages.py", line 16, in <module>
    response = mkm.account_management.find_messages(params={"unread": "true"})
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/mkm.py", line 43, in __call__
    return self.resolver.resolve(api_map=self.api_map, **kwargs)
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/resolvers.py", line 61, in resolve
    return self.api.request(url=self.url, method=self.method, data=data, params=params, auth_params=auth)
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/api.py", line 42, in request
    return self.handle_response(response)
  File "/tmp/magictests/py34proj/lib/python3.4/site-packages/mkmsdk/api.py", line 98, in handle_response
    raise exceptions.ConnectionError(response)
mkmsdk.exceptions.ConnectionError: Request failed
Status code: 400
Response message: Bad Request
b'{"mkm_error_description":"User with ID \\u00270\\u0027 doesn\\u0027t exist.","internal_error_code":null,"post_data_field":null,"http_status_code":400,"http_status_code_description":"Bad Request","rfc2616_description_link":"http:\\/\\/www.w3.org\\/Protocols\\/rfc2616\\/rfc2616-sec10.html"}'

Seems like in your messages list there is a user with an empty ID, wouldn't surprise me if it's an issue with their backend.
They either made some undocumented changes to their API and we're creating a bad request or they have some backend issue and this should technically be a 5xx and not a 4xx; given the returned error I believe it's on their end.
Either way I verified the SDK is working as expected, all parameters are used to make the requests and sent to their backend.
I don't know why there might be a user with an empty ID so I suggest you contact them so solve the issue.

I'm using a test user that only has 5 message threads. I've checked and all of them have a valid idUser. In fact, if there was an issue with an invalid idUser, I wouldn't get anything or an error, while using mkm.account_management.get_all_threads().
I don't have any other user to test with, but I trust you when you say it's working for you. I want to submit an issue to MKM, but they ask me for all of this:
To effectively help with any problems regarding API requests, we need the following information - as complete as possible and independent from any used programming language, libraries, frameworks, etc.:

- request method
- request URI
- complete request headers
- request body, if applicable
- HTTP status code
- complete response headers
- response body, if applicable

Can you help me provide them with all this information?

If you catch the ConnectionError you can recover the failing response and all the necessary information. ConnectionError.response is an instance of requests.Response.
try:
    response = mkm.account_management.find_messages(params={"unread": "false"})
except exceptions.ConnectionError as e:
    print(e.response)

Thanks for this SDK!
Sadly my skills are to low, that I can get it up running.
Maybe you can provide me some help?
If I try this short example:
`#!/usr/bin/python3.4

from mkmsdk.mkm import Mkm
from mkmsdk.api_map import _API_MAP

# Using API v2.0
mkm = Mkm(_API_MAP["2.0"]["api"], _API_MAP["2.0"]["api_root"])

response = mkm.account_management.account()
print(response.json())`

I receive:
  File "_MKM.py", line 6, in <module>
    mkm = Mkm(_API_MAP["2.0"]["api"], _API_MAP["2.0"]["api_root"])
KeyError: '2.0'

What do I do wrong?
Thx

Hi @MarcoPescado, I suggest you open an new issue with more information, so I can better help you and we keep this discussion on topic. :)

I have contacted MKM and they have confirmed it is a bug on their side. Their answer:

Unfortunately this is indeed an error and it exists for a while now. Fixing this is on our list, but I don't have an ETA for this yet.

So, nothing you (or me) can do about it, for now. I'm going to close the issue since it's not a bug on your SDK.

Thanks for the update. :)


aiohttp: Configurable client_max_size

Changes proposed in this pull request:

aiohttp: pass the client_max_size option to web.Application

The issue has been covered by #1173, closing.


Tests fail in non-interactive terminals

Hi,
some tests currently fail when ran in a non-interactive terminal which makes automated testing difficult.
I'm not sure this is expected since most of your tests use a fake Terminal on purpose, so I'm assuming the ones that don't should work even in a non-interactive term.
Can you fix it or is this something we should work around?
Here is the error:
running test
running egg_info
writing blessings.egg-info/PKG-INFO
writing top-level names to blessings.egg-info/top_level.txt
writing dependency_links to blessings.egg-info/dependency_links.txt
reading manifest file 'blessings.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'blessings.egg-info/SOURCES.txt'
running build_ext
blessings.tests.test_capability
Check that a capability lookup works. ... ERROR
blessings.tests.test_capability_without_tty
Assert capability templates are '' when stream is not a tty. ... ok
blessings.tests.test_capability_with_forced_tty
If we force styling, capabilities had better not (generally) be ... ok
blessings.tests.test_parametrization
Test parametrizing a capability. ... FAIL
blessings.tests.test_height_and_width
Assert that ``height_and_width()`` returns ints. ... FAIL
blessings.tests.test_stream_attr
Make sure Terminal exposes a ``stream`` attribute that defaults to ... ok
blessings.tests.test_location
Make sure ``location()`` does what it claims. ... ok
blessings.tests.test_horizontal_location
Make sure we can move the cursor horizontally without changing rows. ... ok
blessings.tests.test_null_location
Make sure ``location()`` with no args just does position restoration. ... ok
blessings.tests.test_zero_location
Make sure ``location()`` pays attention to 0-valued args. ... ok
blessings.tests.test_null_fileno
Make sure ``Terminal`` works when ``fileno`` is ``None``. ... ok
blessings.tests.test_mnemonic_colors
Make sure color shortcuts work. ... FAIL
blessings.tests.test_callable_numeric_colors
``color(n)`` should return a formatting wrapper. ... ok
blessings.tests.test_null_callable_numeric_colors
``color(n)`` should be a no-op on null terminals. ... ok
blessings.tests.test_naked_color_cap
``term.color`` should return a stringlike capability. ... ok
blessings.tests.test_number_of_colors_without_tty
``number_of_colors`` should return 0 when there's no tty. ... SKIP
blessings.tests.test_number_of_colors_with_tty
``number_of_colors`` should work. ... ok
blessings.tests.test_formatting_functions
Test crazy-ass formatting wrappers, both simple and compound. ... ok
blessings.tests.test_formatting_functions_without_tty
Test crazy-ass formatting wrappers when there's no tty. ... ok
blessings.tests.test_nice_formatting_errors
Make sure you get nice hints if you misspell a formatting wrapper. ... ok
blessings.tests.test_init_descriptor_always_initted
We should be able to get a height and width even on no-tty Terminals. ... FAIL
blessings.tests.test_force_styling_none
If ``force_styling=None`` is passed to the constructor, don't ever do ... ok
blessings.tests.test_null_callable_string
Make sure NullCallableString tolerates all numbers and kinds of args it ... ok

======================================================================
ERROR: blessings.tests.test_capability
Check that a capability lookup works.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/jo/compil/blessings-1.6/blessings/tests.py", line 47, in test_capability
    sc = unicode_cap('sc')
  File "/home/jo/compil/blessings-1.6/blessings/tests.py", line 31, in unicode_cap
    return tigetstr(cap).decode('latin1')
error: must call (at least) setupterm() first

======================================================================
FAIL: blessings.tests.test_parametrization
Test parametrizing a capability.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/jo/compil/blessings-1.6/blessings/tests.py", line 68, in test_parametrization
    eq_(TestTerminal().cup(3, 4), unicode_parm('cup', 3, 4))
AssertionError: u'' != u'\x1b[4;5H'

======================================================================
FAIL: blessings.tests.test_height_and_width
Assert that ``height_and_width()`` returns ints.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/jo/compil/blessings-1.6/blessings/tests.py", line 74, in test_height_and_width
    assert isinstance(t.height, int)
AssertionError

======================================================================
FAIL: blessings.tests.test_mnemonic_colors
Make sure color shortcuts work.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/jo/compil/blessings-1.6/blessings/tests.py", line 149, in test_mnemonic_colors
    eq_(t.white, color(7))
AssertionError: u'' != u'\x1b[37m'

======================================================================
FAIL: blessings.tests.test_init_descriptor_always_initted
We should be able to get a height and width even on no-tty Terminals.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/jo/compil/blessings-1.6/blessings/tests.py", line 254, in test_init_descriptor_always_initted
    eq_(type(t.height), int)
AssertionError: <type 'NoneType'> != <type 'int'>

----------------------------------------------------------------------
Ran 23 tests in 0.009s

FAILED (failures=4, errors=1, skipped=1)

same as #25

Hi @jquast, sorry about the duplicate bug. Do you think it's possible to merge this branch into master and make a new release?


Simplify methods

Right now most of the methods expect to receive instances of MLFlow, MLFlowExperiment and/or MLFlowRunInfo.
This makes calls unnecessarily verbose, as opposed to the python client, that manages a global state.
From our docs
using MLFlowClient

# Create MLFlow instance
mlf = MLFlow("http://localhost:5000/api")

# Initiate new experiment
experiment_id = createexperiment(mlf; name="price-paths")
exprun = createrun(mlf, experiment_id)

logmetric(mlf, exprun, "pricepath", pricepath)

From the MLflow Tracking QuickStart Guide
import mlflow

# Set our tracking server uri for logging
mlflow.set_tracking_uri(uri="http://<IP_ADDRESS>:8080")

# Create a new MLflow Experiment
mlflow.set_experiment("MLflow Quickstart")

# Start an MLflow run
with mlflow.start_run():
    # Log the hyperparameters
    mlflow.log_params(params)

    # Log the loss metric
    mlflow.log_metric("accuracy", accuracy)

The Python API is more concise, and the context manager also takes care of finishing the run even if the code inside fails.
If its something desirable, I can start working on adding extra methods for simplifying our API.

Hello @characat0.
The approach of MLFlowClient.jl is just to be a client, enabling direct communication to the mlflow instance REST API. This approach is followed to enable other ML platforms, just like MLJ.jl, to use it and take care of the context (see MLJFlow.jl).
Also we are trying to avoid "black magic" by stay pure functional.
I'm open to discuss this if you have a concern.

It is mostly syntactic sugar tbh, the same can be accomplished by a wrapper, maybe MLJFlow.jl is more suited for this discussion as you suggested.


Feature request: Add to modifers map

It'd be nice if I could add to the modifiers map/parse somehow so I could add arguments for custom filters, i.e. r for "rotate". r180 for example, would flip an image.

+1 - I forked the repo wanting to add a "padding" modifier, to maintain dimensions without cropping and just add white/black bars on the top/bottom or left/right to ensure the image.

I came upon this ticket too, while looking to see if this supports conversion (we have a bunch of PNGs from an API we use that we have to convert to JPG).

closing this ticket. also not looking to add conversion as it is outside of the scope of this project.


Confusion between config and configPath in next

I was trying kpt fn render and I provided a path to config option expecting that it would read from the path.
pipeline:
  mutators:
  - image: gcr.io/kpt-fn/apply-setters:unstable
    config: ./fn-config.yaml

But I received an error: error: failed to run pipeline in package . pipeline run: . missing Resource metadata which din't help me to figure out what's wrong. Sunil helped me with debugging and the mistake was that I passed path to config but it should be configPath.
pipeline:
  mutators:
  - image: gcr.io/kpt-fn/apply-setters:unstable
    configPath: ./fn-config.yaml

This worked.
I know the error message can be improved but I am not sure if we should provide so many options to enter the values in Kptfile. I would suggest to separate the function configs from Kptfile. Package consumers can just open the fn-values.yaml file and provide the inputs. Having too many options(config vs configPath vs configMap) is confusing. Having separate fn-values.yaml would make Cloud Code to provide authoring assistance where providing it though config option can't.

Are you suggesting we don't have inline KRM using config? There's prior art with Kustomize allow inlining, we should assess the pros/cons before deciding. I agree having separate resources enables schema validation.

Yes. Both inline config and configMap. When in doubt we can start simple with simple option configPath and add the support later for other 2 options. WDYT?

I think we need to keep configMap, otherwise simple cases are too verbose. configMap doesn't have the schema/validation problem (it's simple key/value).

@phanimarupaka and me had a chat about it. Two things discussed:

We don't have a strong use-case for inline config. So may be we don't support it initially and support it later. This can remove the confusion that Phani ran into.
Extending the configMap to generic function args where it can be take key-value where value can be any primitive type int, string, list-of-primitive-types. It can be even renamed to 'args`

An example

pipeline:
  mutators:
    - image: gcr.io/kpt-fn/apply-setters:unstable
      args:
          replicas: 2
          envs:
            - dev
            - staging
    - image: gcr.io/kpt-fn/set-namespace:unstable
      argsFile: ./ns.yaml

Different discussions:

naming: function config is part of functions spec. If we want to name this to args or params (both are better names than function config) everywhere, it will be a backwards incompatible change to function spec. I wouldn't have it be called different things in Kpefile schema versus Functions spec.
For non-primitive value (args), it still needs to be converted to a ConfigMap as part of ResourceList.functionConfig? If so, this sugar coating seems to be abusing ConfigMap. In those cases, we want a custom resource, no?

We should get rid of the concept of configMap both in Kptfile and accepting as function spec input. ConfigMap is extremely restrictive and simple inputs like replicas: 3 can't be passed via configMap as 3 is non-string there. We should have new CRD FunctionParams(or FunctionArgs) which has similar schema as configMap but is more expressive in-terms of allowing primitive types(and arrays). Most of the functions like apply-setters, search-replace, set-replicas(which might be developed in future) etc. can leverage FunctionParams to obtain more expressive inputs.

e.g.
pipeline:
  mutators:
    - image: gcr.io/kpt-fn/apply-setters:unstable
      functionParams:
          replicas: 2
          envs:
            - dev
            - staging

or
apiVersion: kpt.dev/v1alpha2
kind: FunctionParams
data:
  replicas: 2
  environments:
    - dev

Functions which need complex inputs can have their own CRDs.(apply-patch etc.)

2. For non-primitive value (args), it still needs to be converted to a ConfigMap as part of ResourceList.functionConfig? If so, this sugar coating makes it easier to abuse ConfigMap. In those cases, we want a custom resource, no?

Sorry, extending the config-map is wrong phrasing. Yes, It requires a custom resource. This can be achieved without changing the function spec though but it will require changes in the function SDKs (not sure if we can do that in backward compatible way). I also feel that it may eliminate the need for functions to define their custom CRDs for function config because configMap is too restrictive.

naming: function config is part of functions spec. If we want to name this to args or params (both are better names than function config) everywhere, it will be a backwards incompatible change to function spec. I wouldn't have it be called different things in Kpefile schema versus Functions spec (it's even more confusing I think). https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md

This is interesting because pkg consumers don't have to deal with the function spec much, so for them, the UX is the pipeline specification. However for function authors, they do have to deal with the UX in the pipeline and how it maps to the function spec. Need to think more about it... lower layer (function spec) is dictating the higher layer UX in this case.

For non-primitive value (args), it still needs to be converted to a ConfigMap as part of ResourceList.functionConfig? If so, this sugar coating makes it easier to abuse ConfigMap. In those cases, we want a custom resource, no?

Sorry, extending the config-map is wrong phrasing. Yes, It requires a custom resource. This can be achieved without changing the function spec though but it will require changes in the function SDKs (not sure if we can do that in backward compatible way). I also feel that it may eliminate the need for functions to define their custom CRDs for function config because configMap is too restrictive.

Sounds like you're saying this function config should be schema less? In the extreme, we can just pass a JSON object. That provides a lot of flexibility, but kind of losing the point of having KRM that can be consumed by other tooling, such as Cloud Code authoring assistance or validation.

naming: function config is part of functions spec. If we want to name this to args or params (both are better names than function config) everywhere, it will be a backwards incompatible change to function spec. I wouldn't have it be called different things in Kpefile schema versus Functions spec (it's even more confusing I think). https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md

This is interesting because pkg consumers don't have to deal with the function spec much, so for them, the UX is the pipeline specification. However for function authors, they do have to deal with the UX in the pipeline and how it maps to the function spec. Need to think more about it... lower layer (function spec) is dictating the higher layer UX in this case.

3 options:

Do nothing
Diverge terminology between wire format and Kptfile
Support multiple versions of ResourceList. After all, it's a KRM to enable us to evolve it over time.

For non-primitive value (args), it still needs to be converted to a ConfigMap as part of ResourceList.functionConfig? If so, this sugar coating makes it easier to abuse ConfigMap. In those cases, we want a custom resource, no?

Sorry, extending the config-map is wrong phrasing. Yes, It requires a custom resource. This can be achieved without changing the function spec though but it will require changes in the function SDKs (not sure if we can do that in backward compatible way). I also feel that it may eliminate the need for functions to define their custom CRDs for function config because configMap is too restrictive.

Sounds like you're saying this function config should be schema less? In the extreme, we can just pass a JSON object. That provides a lot of flexibility, but kind of losing the point of having KRM that can be consumed by other tooling, such as Cloud Code authoring assistance or validation.

It should have base schema which can be extended by package publishers so that Cloud Code can provide authoring assistance/validations.

naming: function config is part of functions spec. If we want to name this to args or params (both are better names than function config) everywhere, it will be a backwards incompatible change to function spec. I wouldn't have it be called different things in Kpefile schema versus Functions spec (it's even more confusing I think). https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md

This is interesting because pkg consumers don't have to deal with the function spec much, so for them, the UX is the pipeline specification. However for function authors, they do have to deal with the UX in the pipeline and how it maps to the function spec. Need to think more about it... lower layer (function spec) is dictating the higher layer UX in this case.

3 options:

Do nothing
Diverge terminology between wire format and Kptfile
Evolve ResourceList by providing both functionConfig and a new field called args/params. Eventually deprecate functionConfig.

@droot It's fine to remove config in favor of having configMap and configPath for now. It's always possible to add fields later, but can't remove them post-v1.

@Shell32-Natsu lets remove config field from the function input in the pipeline.

@Shell32-Natsu lets remove config field from the function input in the pipeline.

ACK

Since this impact the Kptfile schema, bumping up the priority for this one. Also, assigning it to @natasha41575 given that @Shell32-Natsu already has ton assigned in m3.


SASS language support

When declaring a <style lang="sass"> block, the brace-less SASS syntax doesn't seem to be properly recognized:

I think less is more... sass support is not planned, additional development cost of sass is too high, and I still focus on current existing features. (You can expect will have better support for pug)
If circumstances permit, you can consider convert to scss:
http://scss2sass.herokuapp.com/

Fair enough, I will likely convert to scss then, thank you

supported in 0.21.18.


[ownership] Make checked_cast_br, destructure_struct, and destructure_tuple real forwarding instructions

More changes so that we can eliminate the OperandOwnershipKindMap.

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 8cfc6bf881b9dce2729a0536deb1890b9b44f665

Turns out this is dependent on #34633

Build failed
Swift Test Linux Platform
Git Sha - 8cfc6bf881b9dce2729a0536deb1890b9b44f665

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - c7503feeddbf0c94fc28f20887badce40bf786fb

Build failed
Swift Test OS X Platform
Git Sha - c7503feeddbf0c94fc28f20887badce40bf786fb

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - c4adc64a75fad4fd532d89444faa49c12ffc3d09

Linux failure wasn't this commit. Was a missing module.

@swift-ci test linux platform

macOS is going to fail the same way. I am going to wait though, let it finish running /all/ the Swift tests up to that build breakage in tsc.  All the tests before swiftpm passed.


HyperLogLog commands support?

Is there any plan to add the HyperLogLog commands (PFADD, PFCOUNT, PFMERGE) to this client?

Fixed by https://github.com/go-redis/redis/pull/183


Typo in How do I find my rTorrent RPC url?

How do I find my rTorrent RPC url?
If you use ruTorrent, you most likely have an rtorrent RPC url at /path/to/rutorrent/RPC2. If you don't use ruTorrent then it's likely you'll have to set up the endpoint yourself with a web server.

/path/to/rutorrent/RPC2 is not a url path.  It's a directory path.  You probably mean http://user:pass@localhost/RPC2

I meant what I said, but I'll admit it was a bit unclear. Fixed


Add HtmlAttributes.ToString that renders the html

Otherwise you end up with weird stuff like: form.Write(navigation.Submit("text") rendering ChameleonForms.Component.ButtonHtmlAttributes

I'm very comfortable pulling this in, but I'm very curious about why you are using form.Write?

Well, a lot of my forms have just a single button. So I created an extension method that basically does:
using (var n = form.BeginNavigation()) {
    form.Write(f.Submit());
}

But then I had the class name printed instead of a button ;)

Another way is to get your extension method to return the IHtmlString from f.Submit()
That way you don't need to call Writr and you retain control of the output stream within your razor file.
--

On 28 Oct 2015, at 8:18 pm, Felipe Sateler<EMAIL_ADDRESS>wrote:
Well, a lot of my forms have just a single button. So I created an extension method that basically does:
using (var n = form.BeginNavigation()) {
form.Write(f.Submit());
}
But then I had the class name printed instead of a button ;)
—
Reply to this email directly or view it on GitHub.

Ah, that makes sense. BTW, is there an ETA or a list of issues to be finished before we get a new release? I don't see milestones in the issue tracker.

I'm just waiting for a PR review of #132 from @MattDavies and then we will release 2.0.

OK, thanks
On 28 October 2015 at 13:20, Rob Moore<EMAIL_ADDRESS>wrote:

I'm just waiting for a PR review of #132
https://github.com/MRCollective/ChameleonForms/pull/132 from @MattDavies
https://github.com/MattDavies and then we will release 2.0.
—
Reply to this email directly or view it on GitHub
https://github.com/MRCollective/ChameleonForms/pull/135#issuecomment-151898621
.

--
Saludos,
Felipe Sateler

FWIW, the suggestion didn't work, because the Navigation.Dispose method also writes to the stream directly, and thus the button ends outside the navigation section.

Ahh right of course. Good catch.

On 29 Oct 2015, at 3:45 am, Felipe Sateler<EMAIL_ADDRESS>wrote:
FWIW, the suggestion didn't work, because the Navigation.Dispose method also writes to the stream directly, and thus the button ends outside the navigation section.
—
Reply to this email directly or view it on GitHub.


Register formater for proto3 & allow lint action to be disabled

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

My bad, I opened the PR to the wrong repository.


Thinking about emissions data

The purpose of this issue is to document a discussion around how the virtual world in LDAR-Sim produces emissions. A number of factors motivate the need for this issue:

Emissions from the real world are represented in LDAR-Sim using real empirical data. All real-world measurement campaigns are incomplete in some way. For example, OGI surveys may miss large sources, while screening technologies may miss small sources. Raw emissions distributions from measurement campaigns are therefore not representative of reality, so using them as the basis for the virtual world is to create a biased model.
Measurements that go into LDAR-Sim can work in two ways - using bottom-up measurements of individuals leaks/events, or using site-level measurements. Bottom-up measurements are usually incomplete. Top-down are more complete, but miss anything below the detection limit and can't distinguish between fugitives and vents. Right now LDAR-Sim uses bottom-up measurements. Top-down measurements are probably better (include everything), but would need to be disaggregated into individual sources.
LPR is (must be) tied to the method used to collect empirical data for bottom-up. If the detection limit is high, the LPR will be an underestimate of the true LPR. Also, LPR conceptually doesn't apply to top-down measurements, which include regular design sources that are not "produced" according to an LPR but instead remain.
Efforts have been made to develop extremely comprehensive bottom-up inventories (e.g., Rutherford paper) that could be built into LDAR-Sim. It's going to be some work for someone to explore how this might play out/work. It would likely require important structural changes to LDAR-Sim to incorporate individual components, the right equipment, and standard facility types.
Significant amounts of top-down site level data also exists (e.g., Alvarez). Should we focus on using this data and disaggregating it?
The best solution might be to combine 4 and 5, doing what Rutherford et al., did but working backwards to disaggregate site-level emissions distributions into individual sources.

As more of a broader, philosophical question, should we focus on trying to reproduce reality or simply what's relevant in a policy context (i.e., OGI)? Trying to reproduce reality, especially anything below detection limits for OGI, is really difficult and likely not very important.
Other thoughts/considerations? @tbarchyn @KeeganShaw-GIS @soroushojagh @AkaMrmuffin @tybob-gough @c-vollrath

Sure I'll bite. I think LDAR Sim faces several challenges (some alluded to above):

LDAR is only applicable to one component of emissions - a full emissions management tool may have broader use cases.
Empirical data could (should) play a larger role. This circles out to the accuracy of the tool in evaluation case (e.g., is it right?), and in improvement case (e.g., can empirical data parameterize the model better)? Evaluation is pretty important for survival of the whole approach (LDAR Sim / FEAST, etc.) because models that are more accurate are more valuable. And of course missing out on new empirical data to make it better (e.g., at different scales), is a lost opportunity.

To revision LDAR Sim into a tool that is about emissions management, it may be worthwhile to brainstorm what such a tool should look like before adapting code. I think an emissions management toolbench is kind of 3 different components:

A digital twin of emissions, with variable fidelity. This is a full statistical representation of emissions from sites, incorporating data at various scales. For full disclosure, we're slowly working on this for pomelo - I'm really keen to build the statistics tools to mix scales of data because data at different scales is what we have a lot of and I'm so nervous about selective data curation as a tool of narrative control.
An evolution model for emissions at sites. What happens to emissions at these sites through time? This is probably mostly LPR, but the scope needs to be expanded if changing to emissions in general. I think the idea applies at site scale too, but probably can't call it LPR.
Treatment models, this is LDAR basically. Things that change the digital twin, but from the perspective of emissions in general, there is more than just LDAR that changes emissions. This feels like the most mature component. There has been so much effort on producing pretty detailed and deterministic treatment models for things like OGI - but really 1. and 2. have not received the same brainpower and the volume of empirical data beginning to emerge probably suggest 1. and 2. should be focus.

Same model applies to things like drug trials: 1 is all about measuring the people in the trial, 2 is all about modeling normal change over time, and 3 is all about the treatment (compared to a control). Drug trials differ from LDAR in that it is 100% empirical, but same idea.
But to circle out, my general thinking here is to think about how precisely to adapt LDAR Sim to evolve to (i) be more about emissions in general, and (ii) incorporate more empirical data.
The empirical data situation in methane is improving, but generally from science perspective remains super sketch - there is a real need for a serious and surly 'data czar' to understand precisely what any data means - it is not easy to use.


fix: perf improving in set style cache

close  https://github.com/dream-num/univer-pro/issues/2529
close  https://github.com/dream-num/univer/issues/3475

Now _getCellDocumentModel() is called too frequenctly.
_getCellDocumentModel() ---> fontString(font family) ---> set font cache matrix by font family.
Each render frame calc fontString(font family) in _getCellDocumentModel in _setStylesCache.
Return condition deps on fontString(font family). That costs a lot of time.
No need to do this. Just using font Matrix.

Pull Request Checklist

[ ] Related tickets or issues have been linked in the PR description (or missing issue).
[ ] Naming convention is followed (do please check it especially when you created new plugins, commands and resources).
[ ] Unit tests have been added for the changes (if applicable).
[ ] Breaking changes have been documented (or no breaking changes introduced in this PR).

@lumixraku 水平合并单元格后设置边框失败
2024_9_20 16_42_33 video.webm


Getting a misleading warning while running CI

Warning:

CI code:
      - name: Delete old packages # Ref: https://github.com/marketplace/actions/delete-old-packages
        uses<EMAIL_ADDRESS>        with:
          organization: xxxx
          keep: 4
          names: |
            xxxx
            xxxx
            xxxx
            xxxx

The new organization param is missing from the action.yaml, will fix!

Should be fixed in 0.3.1.


Create Something_button.html

Hey I have changed the code according to your request, Check it out
On Sun, 16 Apr 2023 at 23:23, N. K. K. @.***> wrote:

@.**** requested changes on this pull request.
In modules/buttons/Something_button.html
https://github.com/KwickerHub/frontend/pull/190#discussion_r1167987529:

+
+

   <button class="danger-button">

       Danger

what if this sever/url goes down some day? Let's build a powerful and
highly efficient system. Use svg for the icon. check recent buttons.
—
Reply to this email directly, view it on GitHub
https://github.com/KwickerHub/frontend/pull/190#pullrequestreview-1387008412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4QTZUIH763DGYWGTQ4SPB3XBQW2LANCNFSM6AAAAAAW7YWWTU
.
You are receiving this because you authored the thread.Message ID:
@.***>

First of all sorry, I have done 6 more projects which are not assigned to
me, actually really did'nt know about it, sorry for that
On Mon, 17 Apr 2023 at 00:58, Rakesh Penugonda @.***>
wrote:

Hey I have changed the code according to your request, Check it out
On Sun, 16 Apr 2023 at 23:23, N. K. K. @.***> wrote:

@.**** requested changes on this pull request.
In modules/buttons/Something_button.html
https://github.com/KwickerHub/frontend/pull/190#discussion_r1167987529:

+
+

   <button class="danger-button">

       Danger

what if this sever/url goes down some day? Let's build a powerful and
highly efficient system. Use svg for the icon. check recent buttons.
—
Reply to this email directly, view it on GitHub
https://github.com/KwickerHub/frontend/pull/190#pullrequestreview-1387008412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4QTZUIH763DGYWGTQ4SPB3XBQW2LANCNFSM6AAAAAAW7YWWTU
.
You are receiving this because you authored the thread.Message ID:
@.***>

you don't really need to apologize for that. I see it like an extra desire
to improve/learn....
I like your spirit.😊
On Mon, Apr 17, 2023, 05:25 Rakesh Penugonda @.***>
wrote:

First of all sorry, I have done 6 more projects which are not assigned to
me, actually really did'nt know about it, sorry for that
On Mon, 17 Apr 2023 at 00:58, Rakesh Penugonda @.***>
wrote:

Hey I have changed the code according to your request, Check it out
On Sun, 16 Apr 2023 at 23:23, N. K. K. @.***> wrote:

@.**** requested changes on this pull request.
In modules/buttons/Something_button.html
<https://github.com/KwickerHub/frontend/pull/190#discussion_r1167987529
:

+
+

Danger

what if this sever/url goes down some day? Let's build a powerful and
highly efficient system. Use svg for the icon. check recent buttons.
—
Reply to this email directly, view it on GitHub
<
https://github.com/KwickerHub/frontend/pull/190#pullrequestreview-1387008412
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A4QTZUIH763DGYWGTQ4SPB3XBQW2LANCNFSM6AAAAAAW7YWWTU

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/KwickerHub/frontend/pull/190#issuecomment-1510677324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOKWIBJ6NJT4HQDR5NPUDW3XBTA2FANCNFSM6AAAAAAW7YWWTU
.
You are receiving this because you commented.Message ID:
@.***>

However, I would advise that you focus on one issue and get your PR
accepted before you solve others.
It's easier that way...
On Mon, Apr 17, 2023, 10:08 Kenyor Ntem @.***> wrote:

you don't really need to apologize for that. I see it like an extra desire
to improve/learn....
I like your spirit.😊
On Mon, Apr 17, 2023, 05:25 Rakesh Penugonda @.***>
wrote:

First of all sorry, I have done 6 more projects which are not assigned to
me, actually really did'nt know about it, sorry for that
On Mon, 17 Apr 2023 at 00:58, Rakesh Penugonda @.***>
wrote:

Hey I have changed the code according to your request, Check it out
On Sun, 16 Apr 2023 at 23:23, N. K. K. @.***> wrote:

@.**** requested changes on this pull request.
In modules/buttons/Something_button.html
<
https://github.com/KwickerHub/frontend/pull/190#discussion_r1167987529>:

+
+

Danger

what if this sever/url goes down some day? Let's build a powerful and
highly efficient system. Use svg for the icon. check recent buttons.
—
Reply to this email directly, view it on GitHub
<
https://github.com/KwickerHub/frontend/pull/190#pullrequestreview-1387008412
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/A4QTZUIH763DGYWGTQ4SPB3XBQW2LANCNFSM6AAAAAAW7YWWTU

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/KwickerHub/frontend/pull/190#issuecomment-1510677324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOKWIBJ6NJT4HQDR5NPUDW3XBTA2FANCNFSM6AAAAAAW7YWWTU
.
You are receiving this because you commented.Message ID:
@.***>

will you accept my pull requests
On Mon, 17 Apr 2023 at 14:40, N. K. K. @.***> wrote:

However, I would advise that you focus on one issue and get your PR
accepted before you solve others.
It's easier that way...
On Mon, Apr 17, 2023, 10:08 Kenyor Ntem @.***> wrote:

you don't really need to apologize for that. I see it like an extra
desire
to improve/learn....
I like your spirit.😊
On Mon, Apr 17, 2023, 05:25 Rakesh Penugonda @.***>
wrote:

First of all sorry, I have done 6 more projects which are not assigned
to
me, actually really did'nt know about it, sorry for that
On Mon, 17 Apr 2023 at 00:58, Rakesh Penugonda @.***>
wrote:

Hey I have changed the code according to your request, Check it out
On Sun, 16 Apr 2023 at 23:23, N. K. K. @.***> wrote:

@.**** requested changes on this pull request.
In modules/buttons/Something_button.html
<
https://github.com/KwickerHub/frontend/pull/190#discussion_r1167987529
:

+
+

Danger

what if this sever/url goes down some day? Let's build a powerful and
highly efficient system. Use svg for the icon. check recent buttons.
—
Reply to this email directly, view it on GitHub
<

https://github.com/KwickerHub/frontend/pull/190#pullrequestreview-1387008412

,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/A4QTZUIH763DGYWGTQ4SPB3XBQW2LANCNFSM6AAAAAAW7YWWTU

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/KwickerHub/frontend/pull/190#issuecomment-1510677324>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AOKWIBJ6NJT4HQDR5NPUDW3XBTA2FANCNFSM6AAAAAAW7YWWTU

.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/KwickerHub/frontend/pull/190#issuecomment-1510981733,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4QTZULDBNUK7FKTPMRWTP3XBUCITANCNFSM6AAAAAAW7YWWTU
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


#32 Added basic contribution guidelines

Getting started with making a contribution to the project. A how-to with a few bits of advice on making a good PR. Tried to make the description friendly to new oss contributors...considering I'm part of that group.
Thanks and credit goes to @TalAter. I referenced his post here: https://github.com/TalAter/Progressive-UI-KITT/issues/1 to make the guidelines.

Good initiative! It would also be nice to have a part more focused on the stylistic rather than technical parts of commits and pr flow to keep a consistent history!

I'll do that next! Let me know of anything specific you want included.
Otherwise I'll just reference other repos contrib files and cross my fingers.

I think that's for @kenwheeler to decide. I just want something to lean against :)

Thanks for the mention @alavkx 👍
You might also want to have a look at the contribution guide itself: https://github.com/TalAter/annyang/blob/master/CONTRIBUTING.md

Awesome! Re: style, I'll get lint/test CI in place and that should manage that.

That would be a good place to start wouldn't it.. Ha. Thanks @talater


Report number of cores to dashboard

In order to properly calculate the CPU efficiency for multicore jobs, WMAgent needs to report number of cores to dashboard (this information is not available in the FJR at the moment).
Here is the message from Antonio Perez
from Julia's answer in the other thread ( https://hypernews.cern.ch/HyperNews/CMS/get/wmDevelopment/647/1.html )
it seems WMAgent reports TotalJobTime and TotalJobCPU. To allow the dashboard to correctly
calculate the CPU efficiency, we would need to add the number of cores to the report and coordinate
the change in the dashboard side.

Per discussion in https://hypernews.cern.ch/HyperNews/CMS/get/wmDevelopment/647/1/1/2/1/2.html and the rest of the thread, add NCores to the packet as suggested by Julia. Don't require this number to be reported by CMSSW.


test: add a test to capture incorrect after filtering in nested gql c…

…onnections
It looks like the where predicate is being assigned to the inner queries in addition to the level it is set on. Here's some example SQL output showing the issue for a query.
 Thanks, @michaelcaulley 🙏

@a8m of course. Thank you for the quick attention on this. We've really been enjoying using ent!


doc(manual test): update the setting name for drain node policy

Update the manual test plan since the setting has been changed

cc @longhorn/qa


Update charabia v0.7.2

fixes #3701
fixes #3689
fixes #3285

@irevoire, you need to write bors merge in a newline, otherwise bors cannot hear you 😢 🐶
bors merge

bors merge

bors merge


Fix panic due to missing logger

Obfuscator.log was uninitialized which was causing agent panic

What does this PR do?

In this MR I tried to fix a problem I faced using the dbm with mariadb.
Motivation

The agent was in a loop of constant restarts as it was crashing with panic
Additional Notes

I was not able to build the full project so I'm not sure that I've fixed the problem, however I want to use this PR to have your attention on this.
I have a datadog support case with my agent flare №1046589.
What is going on in there?

Python checks call an agent to obfuscate an explain of sql query (mariadb)
Agent fails to parse sql and calls o.log.Debugf (pkg/obfuscate/json.go:81)
o.log is undefined -> agent panics

Example of an explain result:
{
  "query_block": {
    "select_id": 1,
    "table": {
      "table_name": "<subquery3>",
      "access_type": "ALL",
      "possible_keys": ["distinct_key"],
      "rows": 206,
      "filtered": 100,
      "materialized": {
        "unique": 1,
        "query_block": {
          "select_id": 3,
          "table": {
            "table_name": "c2_",
            "access_type": "ALL",
            "possible_keys": ["IDX_6DEB6ACA19EB6921"],
            "rows": 206,
            "filtered": 100,
            "attached_condition": "c2_.client_id is not null"
          }
        }
      }
    },
    "table": {
      "table_name": "c0_",
      "access_type": "eq_ref",
      "possible_keys": ["PRIMARY"],
      "key": "PRIMARY",
      "key_length": "108",
      "used_key_parts": ["id"],
      "ref": ["dd.c2_.client_id"],
      "rows": 1,
      "filtered": 100,
      "attached_condition": "!<in_optimizer>(c0_.`id`,c0_.`id` in (subquery#2))"
    },
    "subqueries": [
      {
        "query_block": {
          "select_id": 2,
          "table": {
            "table_name": "c1_",
            "access_type": "range",
            "possible_keys": ["IDX_F6442ECA1B901A92"],
            "key": "IDX_F6442ECA1B901A92",
            "key_length": "109",
            "used_key_parts": ["client_id"],
            "rows": 49,
            "filtered": 100,
            "index_condition": "c1_.client_id is not null",
            "attached_condition": "c1_.start_date <= <cache>(current_timestamp())"
          }
        }
      }
    ]
  }
}

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

I managed to prevent the agent from crashing on my side by removing the !<in_optimizer> from plan on python side. I did it by updating /opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/mysql/statement_samples.py
--- statement_samples.py	        2023-01-03 11:45:49
+++ statement_samples_patched.py	2022-12-27 14:50:29
@@ -546,6 +546,15 @@
                 )

         normalized_plan, obfuscated_plan, plan_signature = None, None, None
+
+        def clean_plan(p):
+            if isinstance(p, str):
+                return p.replace("!<in_optimizer>", "")
+            elif isinstance(p, [int, float, bool]):
+                return p
+            return {k: clean_plan(v) for k, v in p.items()}
+
         if plan:
+            plan = clean_plan(plan)
             try:
                 normalized_plan = datadog_agent.obfuscate_sql_exec_plan(plan, normalize=True) if plan else None
                 obfuscated_plan = datadog_agent.obfuscate_sql_exec_plan(plan)


Length of responses keeps truncating

Despite continuing to search for a reasonable response or configuration, it is still not possible to control the cutoff event of ChatGPT responses despite using the API. In a certain length the response is simply cut off and it is not a matter of the IDE but the same behavior that exists on the ChatGPT web
Thank you
IAPython

@IAPython unfortunately, the token limits are set by OpenAI and there isn't anything this extension do to bypass that. Though, once the response is cut off due to length by the APIs, you could then ask it to continue with this prompt: Continue. I hope that answers your question.


Getting TypeError

Getting this TypeError:
beat_track() takes 0 positional arguments but 2 positional arguments (and 1 keyword-only argument) were given
Any thoughts?  Would love to use this program!

NM, complete uninstall of Anaconda and reinstall fixed issues.
Thanks!!!


No logger yields ThreadAbortException

Steps to reproduce
1. Implement calls to Google API, WITHOUT setting a logger through
ApplicationContext
2. Upload a video using the youtube API

Expected result?
1. Video uploads to youtube or exception is thrown as to why the upload could
not be handled

Actual result:
1. upload() inexplicably throws a ThreadAbortException. Due to the exception
being a ThreadAbortException, handling is practically impossible.

What version of the product are you using? <IP_ADDRESS>685
What is your operating system? 7
What is your IDE? VS2010
What is the .NET framework version? 4

Omitting a logger should have zero side effect aside from a lack of logs.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 18 Apr 2014 at 3:25

No activity here, closing. Feel free to reopen if seen again.


Spotio quits shortly after opening and is replaced with regular Spotify

@devinhalladay  @sandervankasteel Hey (fe)ma(le)n(s).
Love all the work you've done, it looks amazing, and I am super glad it's out in the open. But I have been having a major problem, I downloaded the app a few minutes ago. And although i have set my mac to automatically accept opening applications from foreign places, my computer still asked, but it opened anyways, so i thought that was fine. Anyway, I deleted my old Spotify and opened up the new one. It got interesting when Spotio launched, everything looked fine, but my albums weren't showing up and there was a considerable amount of lag (although that lag may be normal). On top of this, the app would close after a couple seconds of opening, immediately replaced by the old Spotify. It didn't matter how many times i tried, Spotio would just crash, (also seemed to change the app icon when i moved it to my desktop). Spotio played music fine and looked awesome, with the exception of the lag (maybe) and the missing albums. I was just wondering if you have a solution or feedback to all or any of my issues here?
spotio issue.mp4.zip
ZIP file containing mp4 video of my issue
Much Love
Wilco

Hi @WillDimarco,
The flashing that you are experiencing isn't weird to see. That's because of Spotio and how it's white background is applied.
But the main issue you are having, is that Spotio is replaced with a new version of Spotify. That's because of the internal updater of Spotify. In the past Spotify would only update the components it used but nowadays after an update is found, (on OS X / MacOS!) Spotify will replace it's whole application (and therefor, remove any modifications done by Spotio) by a new version of Spotify and restart the application. The only way to currently "fix" this, is to patch your own version of Spotify and sign it yourself on OS X / MacOS (see #23 for resigning your own application and see the README for building your own version of Spotify)
I hope to have some decent time at the end of the year, to finish up my external patcher application. So it's just a matter of "patching" up the Spotify application and Spotify should be white again.

Thank you so much! I will definitely look into those other issues to fix my own. Thanks again!
Wilco

No problem :+1:
@devinhalladay can you close this issue ?

i don't know how haha

Hey guys, thanks for working through this! @WillDimarco I apologize for all these issues; I released Spotio right as school started back up so I lost the opportunity to keep updating Spotio and the time to work on an updater application to patch files after Spotify issues an update. Hopefully this will come sooner or later (but, in the meantime, you may want to check out Pandora's new streaming service coming out in Q1 next year!! I have a friend working there and he's so excited for the release, plus their design is really great and feels like a second home after Rdio).
@sandervankasteel Thanks so so much for your help and upkeep in the issues here; I haven't even had the time to open Github for a few weeks so I appreciate it very much. If you're working on that updater/patcher application and need help, let me know and I'd be happy to lend a hand this month during my winter break from school! If not, I'm hoping I'll find some time to at least start it in the upcoming month or two.
Closing this issue now but feel free to keep discussion going afterward!

@devinhalladay No problem 👍  I wanna be able to have a minimal MVP code for the patcher done when my winter break from school is done. At first I think it will only support OS X, but that should give us at least a baseline on where Spotify is heading towards regarding updating and how we should structure our patcher application. So we could eventually set it up so it's multiplatform.


Fix vitest peerDependency

The current setting
"peerDependencies": {
   "vitest": "^0.31.0"
}

does not allow upgrading to vitest 0.32 .
You can test this here https://semver.npmjs.com/ . ^0.31.0 will not list 0.32

Hi, i'm experiencing the same issue, i can't upgrade vitest to 0.32.2
any updates?

@chaance Any chance of a release with this fix in it?

For those using a recent version of npm (16+) then you can add this to your package.json:
  "overrides": {
    "vitest": "^0.34.4"
  },

Just ensure the version matches what's in your devDependencies.


Update README.md - added todo list

added todo list;
suggest to add sample use cases;

@xfix because I've no idea how to use this repo as a library / runtime


How can I use Rawdog and LM Studio together?

Do you have instruction how to connect RawDog and LM Studion?

I haven't tried LM Studio but it looks like it can run an OpenAI-compatible local server. So set that up, and then set the llm_base_url and llm_model like you would for litellm:

(from https://github.com/AbanteAI/rawdog?tab=readme-ov-file#model-selection)


Bump version to 0.3.15

Thanks!
@bors r+

bors r+

bors retry
Network issues.

Released on GitHub & crates.io

Thanks a lot!


polyfill missing hexagons near pentagons

Demo: https://uber-common-public.s3-us-west-2.amazonaws.com/svc-vis-prototype/h3-grid/index.html
The app calls h3.polyfill to get hexagons that fill each OSM tile. The offending tiles here are
{
  "x": 87,
  "y": 153,
  "z": 8,
  "east": -56.25,
  "north": -33.13755119234615,
  "south": -34.30714385628804,
  "west": -57.65625,
}

{
  "x": 86,
  "y": 154,
  "z": 8,
  "east": -57.65625,
  "north": -34.30714385628804,
  "south": -35.4606699514953,
  "west": -59.0625,
}

Though the issue is observed at multiple zoom levels.

This PR provides a slow but correct fix to the core lib: https://github.com/uber/h3/pull/279
There's discussion in that PR about a faster, also correct algorithm that we plan to implement soon. If that gets a PR from @dfellis in the near term, we'll probably wait for it to land before the next release; otherwise, we'll release the slow version, which should fix this issue.

Fixed in #74


[BugFix] Fix the crash caused by DictMappingExpr rewrite

Signed-off-by: fzhedu<EMAIL_ADDRESS>What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #https://github.com/StarRocks/StarRocksBenchmark/issues/200
Problem Summary(Required) ：

fix 2 bugs in https://github.com/StarRocks/starrocks/pull/8950
add child in DictMappingExpr::rewrite may cause read-write conflicts;
DictOptimizeParser::rewrite_expr should create expression objects with longer lifespan than itself.
test:
manual tests: run the sql more than 100+ times on the issue env and results are ok.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test

run starrocks_admit_test


Scp shows a failure error when copying from local to remote

When drag/dropping a file from local to remote, the file seems to get copied but we see the following errors:

Error copying file:///Users/marwansulaiman/marwan/printserver/README.md to ts://nodes/marwan/~/Downloads: Error: Command failed: scp /Users/marwansulaiman/marwan/printserver/README.md marwan:~/Downloads
EOF

Taking the command on its own and running scp from my terminal, the same behavior occurs in that scp exits with 1 and says EOF.
scp -v /Users/marwansulaiman/marwan/printserver/README.md marwan:~/Downloads
Executing: program /usr/bin/ssh host marwan, user (unspecified), command sftp
OpenSSH_9.0p1, LibreSSL 3.3.6
debug1: Reading configuration data /Users/marwansulaiman/.ssh/config
debug1: /Users/marwansulaiman/.ssh/config line 6: Applying options for marwan
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files
debug1: /etc/ssh/ssh_config line 54: Applying options for *
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to marwan port 22.
debug1: Connection established.
debug1: identity file /Users/marwansulaiman/.ssh/id_rsa type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_rsa-cert type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_ecdsa type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_ecdsa_sk type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_ed25519 type 3
debug1: identity file /Users/marwansulaiman/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_ed25519_sk type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_xmss type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_xmss-cert type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_dsa type -1
debug1: identity file /Users/marwansulaiman/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.0
debug1: Remote protocol version 2.0, remote software version Tailscale
debug1: compat_banner: no match: Tailscale
debug1: Authenticating to marwan:22 as 'marwan'
debug1: load_hostkeys: fopen /Users/marwansulaiman/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: kex: client->server cipher<EMAIL_ADDRESS>MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:jgdeqLM15+cTtH9hd7m7GkvtNGzU/3+ZEnD6g0VG5GQ
debug1: load_hostkeys: fopen /Users/marwansulaiman/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host 'marwan' is known and matches the ED25519 host key.
debug1: Found key in /Users/marwansulaiman/.ssh/known_hosts:13
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: get_agent_identities: bound agent to hostkey
debug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identities
debug1: Will attempt key: /Users/marwansulaiman/.ssh/id_rsa
debug1: Will attempt key: /Users/marwansulaiman/.ssh/id_ecdsa
debug1: Will attempt key: /Users/marwansulaiman/.ssh/id_ecdsa_sk
debug1: Will attempt key: /Users/marwansulaiman/.ssh/id_ed25519 ED25519 SHA256:3qAEobsc1gP6B0GE8jxDFdGm9fvwjN+B2nGV95Tn3LU
debug1: Will attempt key: /Users/marwansulaiman/.ssh/id_ed25519_sk
debug1: Will attempt key: /Users/marwansulaiman/.ssh/id_xmss
debug1: Will attempt key: /Users/marwansulaiman/.ssh/id_dsa
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-256,rsa-sha2-512,ssh-rsa,ssh-dss>
debug1: SSH2_MSG_SERVICE_ACCEPT received
Authenticated to marwan ([<IP_ADDRESS>]:22) using "none".
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: pledge: filesystem
debug1: Sending environment.
debug1: channel 0: setting env LC_TERMINAL_VERSION = "3.4.19"
debug1: channel 0: setting env LANG = "en_US.UTF-8"
debug1: channel 0: setting env LC_TERMINAL = "iTerm2"
debug1: Sending subsystem: sftp
README.md                                                                               100%  110     2.5KB/s   00:00
EOF
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 2164, received 1628 bytes, in 0.3 seconds
Bytes per second: sent 6759.9, received 5085.5
debug1: Exit status 1

Fixed.


Osmosis Proto

Hello,
thank you so much for working on this awesome repository.
How much effort would it be to add Osmosis and Terra?
I tried running the build, but something fails. I was able to manually add some Osmosis related messages.
If it is easy to archive by adding it to the main.rs file maybe I do not need to implement it manually.
Thank you in advance.
Best regards,
Philipp

There's some ongoing discussion about this here: https://github.com/informalsystems/tendermint-rs/issues/654#issuecomment-1119466744
I suggested having a single repo where all of the protobufs could be managed consistently. So yes, I think it'd be a good idea to reuse the same infrastructure we have already for crates like tendermint-proto and cosmos-sdk-proto to be able to generate crates for the protos for other networks.

I think this makes a lot of sense. From a technical perspective, what exactly needs to be done to make the main.rs work for osmosis? Just adjust the paths or are blockchain specific customizations needed as well?

I got the cargo run to finish without errors with added paths for osmosis.

'../cosmos-sdk-proto/src/prost/osmosisd'
What about the process for the lib.rs and cargo.toml do they need to be edited manually, or is there a script for that as well?

thank you, I just separated the code from the cosmos-sdk-proto into osmosis-proto. I tested it with a few queries and it seems to work fine with the Osmosis gRPC endpoint I have.
How Osmosis is setup, the endpoint sometimes return google.protobuf.Any for that I will need to add some handcrafted code, so it can easily be casted into the type it acutally represents.
I will fork the branch you created and try to do a pull request.

@tony-iqlusion pull request is out https://github.com/cosmos/cosmos-rust/pull/239
Let me know if you like me to make any changes before you merge it.

Update:
See added osmosis specific cosmrs customization
I think this is a good way to do it. Let me know if you have any feedback.
Thanks and best regards,
Philipp

On another note: tx/msg.rs it would be great if the MsgProto implementations get generated by a script if possible. There are many types missing.

Closing this issue.

The MsgProto trait is gone. I assume you're referring to the TypeUrl trait?
Yes, that sure would be nice. There's an upstream issue about it on prost here:
https://github.com/tokio-rs/prost/issues/299

If there was a way to get a list of all the type urls we could write a script to write the matching implementations.
Might be something to look into in the future. For the time being I am okay, with adding the types I need manually.

It will hopefully get fixed upstream in the next release. There's already a few PRs.
If it really ends up continuing to be an issue we can look at automating it.


Unable to connect to Atlas due to DNS connectivity issues

I've run into an issue where connecting to Atlas using a mongodb+srv:// URL is failing on a specific set of AWS Windows 10 instances that my company uses for testing. We have a mix of C# and Elixir client code and only the Elixir code was failing.
I did some debugging to figure out what was going on, and found code in url_parser.ex that hardcodes <IP_ADDRESS> as the name server to use to lookup the records needed to decode the +srv URL. This AWS instance is pretty locked down and it is not allowed to access that server. This can be tested on the command line using nslookup.
A simpler reproducing case is to configure the Windows firewall to block connections to that specific address. Not a likely use case, but gives the same result.
I did some additional digging to figure out why the code was manually specifying a DNS server in the first place and found this issue, where apparently Erlang doesn't know how to properly retrieve the DNS configuration from the OS on Windows.
You can workaround this issue by manually setting \HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\NameServer to an approved name server so that Erlang will actually see the configuration (not desirable). I've also verified that changing the hardcoded value in url_parser.ex resolved the issue, but that's also not a real fix.
I tried using :inet_db.add_ns() to add additional configuration in our code prior to calling into the MongoDB driver, but that doesn't work. It looks like the inet_db configuration is scoped to an individual Erlang process. Changing it in one process doesn't affect others.
I'd appreciate thoughts on how to address this. It's an internal issue for us at the moment, and not a showstopper, but business ownership is concerned that this end users will start hitting this eventually.

Just bumping this up:
We are also experiencing problems connecting to Atlas. The actual error is:
[error] Mongo.Protocol (#PID<0.5272.0>) failed to connect: ** (Mongo.Error) tcp connect: non-existing domain - :nxdomain

Has there been an official solution for this problem?

@wizardone We've been using Atlas for years now and haven't seen this, but we're also not using mongodb+srv as our connection string. When did it start?
@JD-Robertson Sorry no one got back to this 2 years ago when you posted it! Is this still happening?


Ansible warning

TASK [sbs : Add SBS user] ******************************************************
[WARNING]: Option column_case_sensitive is not provided. The default is now
false, so the column's name will be uppercased. The default will be changed to
true in community.mysql 4.0.0.

confirmed working


[Question] The Buttons are not appearing on Kik when using Thumbnail Card.

SDK Language: NODE
SDK Version: 3.8.4
Development Environment: AZURE_BOT_SERVICE

Issue Description
The Buttons for other channels, (Skype, Facebook) appear when using the Thumbnail Card; however; on Kik they do not appear.
Code Example
let TestCard: builder.Message = new builder.Message(session)
    .addAttachment(new builder.ThumbnailCard(session)
    .title("Order")
    .text("Click the button to order")
    .images([builder.CardImage.create(session, "https://www.actualpicture.png")])
    .buttons([ builder.CardAction.openUrl(session, "https://www.test.com", "Order") ]);

Expected Behavior
Thumbnail Card appears with buttons.
Actual Results
Thumbnail card appears but there are no buttons.

@Tracet51 can you post your complete bot code so that we may better assist you?

@Tracet51 Kik acts a bit differently when it comes to the card display.  When you send a card with buttons to the Kik mobile app, the buttons do not display in the card itself, they are located underneath the text input field. See screenshot.
Card with buttons in WebChat component:

Card with buttons in Kik mobile app:

To view how different features will render in Kik and other channels, check out the Channel Inspector here: https://docs.botframework.com/en-us/channel-inspector/channels/Kik?f=Buttons&e=example1


Add Vagrantfile for running tests in development

👓 @ckwang8128
cc @spladug for visibility
Guess, check, google, repeat on puppet so feel free to be hard on me!

:nail_care: just a couple tiny questions. looks great. would you mind running puppet-lint on the puppetfile for style please?

💇

:fish:


Add "All Active Deployed Contracts" section

Took a stab at this... @kanewallmann - I just crawled https://github.com/rocket-pool/rocketpool/tree/master/contracts/contract for solidity contract names and dropped the ones that gave no address (non-deployed contracts, NO deployed contracts, old, types, tests...) -- would that miss anything?

The list on https://docs.rocketpool.net/developers/usage/contracts/contracts.html#interacting-with-rocket-pool is out of date.
Extra
rocketClaimNode
Missing
rocketDAONodeTrustedSettingsRewards
rocketMerkleDistributorMainnet
rocketMinipoolBase
rocketMinipoolBondReducer
rocketMinipoolDelegate
rocketMinipoolFactory
rocketNetworkPenalties
rocketNodeDistributorDelegate
rocketNodeDistributorFactory
rocketSmoothingPool
rocketUpgradeOneDotTwo

Lgtm


Add an error message about pre-release dependencies

From https://github.com/bundler/bundler/issues/4340, https://github.com/bundler/bundler/issues/2938, https://github.com/bundler/bundler/issues/4337
It would help reduce user confusion if the error message generated in that case explicitly stated that pre-release dependencies need to be explicitly listed in the gemfile

Checkin whether the conflicting gem has pre-release versions that satisfy all dependencies when rescuing the VersionConflict should be sufficient for this

Working on this.

@segiddins Could you perhaps explain further what you mean by Checkin whether the conflicting gem has pre-release versions that satisfy all dependencies
I've managed to reproduce the issue and rescue the VersionConflict exception from one of the cases in the issues linked above. Still not clear to me what to do moving forward though.

This should be fixed / unnecessary now - https://github.com/bundler/bundler/pull/6014 ensures we get the right behaviour for pre-releases.

 Discovered that was because one dependency has its own dependency on a pre-release gem. I had to define that dependency in my own Gemfile to bundle install successfully. Error message produced by bundler was completely useless of course. It was rails 5.2.0.rc1 btw.
Is there a reason why bundler won't fetch pre-release dependencies like that when they are defined in gemspecs?
I'm not even sure that's even an issue as it seems to work fine until I forced version on one of the gems. See: https://github.com/rails/rails-controller-testing/issues/37 Very confusing.

@GBH You're attitude in your comment is coming off as very rude and unfair to everyone that works on something you literally get for free. We have a Code of Conduct that applies to everyone participating in the Bundler repository and i recommend you review it before commenting here again. You've been warned.

@colby-swandale Sorry, didn't mean to come off rude, just frustrated. Edited. Cheers.

I’m on holiday without much internet for the next few days, but if you post a copy of a Gemfile and Gemfile.lock that’s failing to resolve as expected I’ll take a look into it when I’m back.
#6014 should have fixed this, so I’m a little confused.

@greysteil I can do even better.
Here's repo state when bundle install wont work: https://github.com/comfy/comfy-blog/tree/0ea3307e3fa86dd68edd8b8b62208c2e26a71c3c
Following commit added gem "rails", "~> 5.2.0.rc1" to Gemfile that got everything working.
Issue seems to be with:

A depends on B
B depends on C.rc1

Yet this got triggered by a gem that seems to be unrelated. Here's the error in full:
Bundler could not find compatible versions for gem "actionpack":
  In Gemfile:
    rails-controller-testing (~> 1.0.2) was resolved to 1.0.2, which depends on
      actionpack (>= 5.0.1, ~> 5.x)

    web-console (~> 3.5.1) was resolved to 3.5.1, which depends on
      railties (>= 5.0) was resolved to 5.0.0, which depends on
        actionpack (= 5.0.0)

Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    rails-controller-testing (~> 1.0.2) was resolved to 1.0.2, which depends on
      actionpack (>= 5.0.1, ~> 5.x) was resolved to 5.0.1, which depends on
        activesupport (= 5.0.1)

    web-console (~> 3.5.1) was resolved to 3.5.1, which depends on
      activemodel (>= 5.0) was resolved to 5.0.2, which depends on
        activesupport (= 5.0.2)

Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    web-console (~> 3.5.1) was resolved to 3.5.1, which depends on
      railties (>= 5.0)

Could not find gem 'railties (>= 5.0)', which is required by gem 'web-console (~> 3.5.1)', in any of the sources.

Sorry for taking so long to come back on this. I couldn't replicate it when I tried a couple of weeks ago and have just tried again and still can't - checking out https://github.com/comfy/comfy-blog/commit/95f3e677c62db1444a0ed4e0f574ab887c99daae I'm getting resolution after a couple of seconds. I'm on Bundler 1.16.1, Ruby 2.5.0, and Rubygems 2.7.6 - @GBH can you try updating Rubygems and let me know if the problem persists?

@GBH Ping

I won't be able to replicate error I got 1.5 years ago. Feel free to close 🤷♂

It sounds like this got fixed, just wanted to check with you just in case. Thanks.


re-introduce maybeReattachSlot in Composers

to fix reappearing of custom inspectors (b/243719086)

somehow these changes (https://team-review.git.corp.google.com/c/arcs-team/arcsjs-apps/+/1512785) got lost in the newer composers...
PS: i think we have some Composer classes that are no longer in use, should I file an issue to remove them?

I file an issue to remove them?

Yes please. Maybe a component of a slightly bigger 'Surface' cleanup?

For the record I messed this up in the first place because I built Default/Composer.js out of old parts.