pytg: INFO CLI did not responde

The problem
Hi all!
Log output:
ConnectionResetError: [Errno 104] Connection reset by peer
2017-12-15 10:10:06,661 pytg: INFO CLI did not responde.
Actual behaviour
Tell us what happens instead.
Your environment
ubuntu:16.04

Component
Version

python
3.5.2

pytg
0.4.10

OS
`Linux d3360e5bd9d9 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce
Detailed steps to reproduce the issue.
# coding=utf-8

import time
import os

from pytg import Telegram
from pytg.utils import coroutine

import requests
from pytg import exceptions
from datetime import datetime
import logging
from socket import error as SocketError
logging.basicConfig(level=logging.INFO, format='%(asctime)s %(name)s: %(levelname)s %(message)s')

def post_to_db(post):
    # do something

def main():
    home_dir = os.environ.get("TELEGRAM_HOME")
    port = os.environ.get("TELEGRAM_PORT")

    tg = Telegram(
        telegram="/tg-cli/telegram-cli",
        port = int(port),
        pubkey_file="/tg-cli/tg-server.pub",
        home_directory=home_dir)
    receiver = tg.receiver
    sender = tg.sender

    try:
        receiver.start()
    except Exception as e:
        logging.info("cannot start receiver for receive new messages: {error}".format(str(e)))
        receiver.stop()
        quit()

    try:
        receiver.message(message_func(sender))
    except SocketError as e:
        logging.info("cannot receive new messages: {error}".format(str(e)))
        receiver.stop()
        sender.safe_quit()
    except Exception as e:
        logging.info("cannot receive new messages: {error}".format(str(e)))
        receiver.stop()
        sender.safe_quit()

    receiver.stop()
    sender.safe_quit()

@coroutine
def message_func(sender):
    try:
        while True:
            msg = (yield)
            try:
                sender.status_online()
                msg = dict(msg)
                # print (msg)
                if msg.get("event") != "message":
                    continue
                if msg.get("text") is None:
                    continue
                elif "from" in msg:
                    post_to_db(post)
                elif "to" in msg:
                    post_to_db(post)
                elif "sender" in msg:
                    post_to_db(post)
                else:
                    quit()
            except exceptions.NoResponse:
                quit()
    except KeyboardInterrupt:
        quit()
    except Exception as e:
        print (e)
        logging.info("could not receive new messages: {error}".format(str(e)))
        quit()
    except GeneratorExit:
        # pass
        quit()
    else:
        # pass
        quit()

if __name__ == '__main__':
    main()

Heya, could you set the logging level to logging.DEBUG instead of logging.INFO, to give more information?
Also, using logging.exception("whatever") will print you the stacktrace of an Exception, giving me a bit more to work with as print (e) does.


MWPW-143591 Fix Contextual Search Duplicates

Allows feed config in contextual search authoring for customized card results
Fixes duplicates in contextual search

Resolves: MWPW-143591
Test URLs:
Milo:

Before: https://main--milo--adobecom.hlx.page/drafts/methomas/contextual-search
After: https://methomas-search-exclude--milo--adobecom.hlx.page/drafts/methomas/contextual-search

Bacom Blog

Before: https://main--bacom-blog--adobecom.hlx.page/uk/drafts/methomas/?martech=off
After: https://main--bacom-blog--adobecom.hlx.page/uk/drafts/methomas/?milolibs=methomas-search-exclude&martech=off

Blog:

Before: https://main--blog--adobecom.hlx.live/
After: https://main--blog--adobecom.hlx.live/?milolibs=methomas-search-exclude&martech=off

Looks good. Are there any tests that should be updated?

Not that I can see. Unit tests pass and code coverage looks good.

Looking good from what I can see.
I am having trouble reproducing the duplicate results. I saw your notes in the Jira ticket, but still wasn't able to see that in action. Any other tips?

Looking good from what I can see. I am having trouble reproducing the duplicate results. I saw your notes in the Jira ticket, but still wasn't able to see that in action. Any other tips?

@rgclayton It's easiest to see the duplicate results when you search something very specific. For example, on Adobe Blog, try "christian cowan". On bacom blog, I was testing with "adobe launches customer journey".
It happens most often on the first search, so if you're still not seeing it, refresh the page and search again.

Note: I have the "critical" label because that's the priority of the ticket, added by the PM. The due date is Thurs, March 14.

FYI There was a bug found where the search results take longer to show for certain queries. PM said that it wasn't a blocker for launch, so we'll create a ticket and follow up later.


Respond to linting errors and enable CI linting

With #1450, we will be getting back to performing linting on contributed code. Because we haven't been linting code for a while, there are a lot of outstanding issues that need to be resolved before we can start using linting as a metric for code quality.
The ultimate goal of this ticket is to ensure that we can run automated linting via Travis, against all applications except projects/ and builds/. Any pull requests that address linting errors should reference this ticket for tracking.
When contributing linting clean up pull requests, keep pull requests reasonably small, don't address multiple applications needlessly. Grouping cleanup efforts across applications like this will more likely create conflicts that will slow down clean up efforts.
Linting will be run from Tox, clean up efforts only need to address the problems in those errors. See http://docs.readthedocs.org/en/latest/tests.html for more information on our test suite.
refs #1424

See #1522

Was fixed with the merge of #1522.


Clarify cancelling synchronous operations as well.

I noticed that this repo talks a lot about async when it comes to cancellation. I wanted to make sure it also considered synchronous use cases.
A good cancellation primitive needs to not only be asynchronous, but also synchronous.
I say this because it would be nice if this cancellation primitive could be used to free up resources for things like EventTarget in the DOM. EventTargets can have handlers registered, triggered, and unregisted completely synchronously.
Likewise, this cancellation primitive would be useful for push-based architectures. (I'd definitely try to leverage it for RxJS), and those can be synchronous.
Consider the following example (also on codesandbox here), that deals with a design where a synchronous push stream needs to be cancellable:

/**
 * Returns a function that pushes a range of numbers as fast as possible via a callback.
 * @param {number} start The start of the number range
 * @param {number} end The end of the number range
 */
function range(start, end) {
  return (callback, cancelToken) => {
    for (let n = start; n < end && !cancelToken.cancelled; n++) {
      callback(n);
    }
  };
}

/**
 * Transforms a simple push stream type (like `range` returns above)
 * into a new push stream that will only emit `count` values.
 * @param {number} count The number of values to take
 */
function take(count) {
  return sourceFn => {
    return (callback, cancelToken) => {
      let i = 0;
      sourceFn(value => {
        if (i++ < count) {
          callback(value);
        } else {
          cancelToken.cancel();
        }
      }, cancelToken);
    };
  };
}

/**
 * A function for chaining push streams together.
 *
 * @param {function} source The push stream function that is the source
 * @param  {...any} fns transforms for the push stream functions (like `take`)
 */
function compose(source, ...fns) {
  return (callback, token) =>
    fns.reduce((prev, fn) => fn(prev), source)(callback, token);
}

/**
 * A push stream we can test with, only
 * takes 30 values from an infinite source.
 */
const source = compose(
  range(0, Number.POSITIVE_INFINITY),
  take(30)
);

// set up the token (again, just a simple example impl)
const token = new CancelToken();

// test out cancellation
source(n => console.log(n), token);

Yes, it's a contrived example, and there's probably more functional composition up there than is really necessary to convey the point. But the high-level point is, in my experience with cancellation, cancellation needs to happen synchronously and also needs to set a flag that can be examined synchronously.

cancellation needs to set a flag that can be examined synchronously

I could not agree more.
Whether the push-based event source is synchronous or not, I want to be sure (make it a provable invariant!) that it does not fire any cancelled callbacks immediately after I did the cancellation. To implement such a component in user land code, the only viable approach I can see is to check such a flag right before calling the callback.


AVRO-2553: Remove unnecessary note from the Python docs

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"

https://issues.apache.org/jira/browse/AVRO-2553
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No additional test since it's just a documentation fix. I ran ant in the doc directory and confirmed the fixed document was generated as expected.
Commits

[x] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

Funky error in the CI, restart.


Student Feedback

Kenneth was helpful and was able to help individually if needed
Suggestion for spreading the class is relevant, 3x7h does not match the cognitive science knowledge about the length of our attention span and ultradian brain cycles

Thanks. Moved comments to #7 so will close it here (but it will still be saved for later use)


[Event Request] Codeunit 76 "Purch.-Get Drop Shpt."

Could you please add the Purchase Header on these 2 events ?
OnCodeOnAfterSalesLineSetFilters(SalesLine);
OnCodeOnAfterSalesLineSetFilters(PurchHeader,SalesLine);
OnCodeOnBeforeProcessPurchaseLine(SalesLine, IsHandled);
OnCodeOnBeforeProcessPurchaseLine(PurchHeader,SalesLine, IsHandled);

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


⚠ Bofrost.at has degraded performance

In 7a1056e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2532 ms

Resolved: Bofrost.at performance has improved in 78a0490.


make global http client worker threads configurable

ref #3301

The code could be review now. :)

Thanks @zhxiaogg !   does io.druid.guice.http.JettyHttpClientModule.HttpClientProvider need modified as well? (I haven't ever really dug into the http client provider code before)

@drcrallen yes, it also needs to be modified, the default thread pool for jetty http client is configured by maximum 200 threads. The code has been changed.

As a side note, I couldn't find where the http configs are documented. There may need to be a ticket to add that somewhere in the docs.

opened a new issue for documentation. cc @drcrallen

They're documented in broker.md, properties like "druid.broker.http.readTimeout".

Ah, nevermind, that's only the client the broker uses to talk to data nodes. The other client used for other stuff doesn't have its configs documented.


Add bomb pot functionality

Added functionality for bomb pots; there may be some edge cases I haven't covered (e.g. 2-person bomb pots?) and unconvinced that I'm handling BTN functionalities too well, but bomb pots are rarer, so this should suffice for now. Looks like the rest of the code works fine when diff'ing with past.

Hm. It appears there are some issues with button assignment, which is what worries me the most.
$ diff ConvertedPNLog-2024-05-02-0455-1.0-2.0-Hold\'em\ No\ Limit.txt PokerNowLogConverter/ConvertedPNLog-2024-05-02-0455-1.0-2.0-Hold\'em\ No\ Limit.txt
2664c2664
< Table 'PNLogConverter' 10-max Seat #9 is the button
---
> Table 'PNLogConverter' 10-max Seat #8 is the button

5719c5719
< Table 'PNLogConverter' 10-max Seat #4 is the button
---
> Table 'PNLogConverter' 10-max Seat #8 is the button

I am unsure why the difference is so dramatic.


Added support for tags

I love your theme, so I added the support for one of the default taxonomy in GoHugo : tags.
I also added documentation in the exampleSite, and the theme variants.
I only doubt about the CSS, if anyone have a better idea don't hesitate :-)

I am very interested by this feature. Can I help?

There's a couple of things if you would like to contribute.

Review the code
Run the branch on the example site or your own sites and test functionality

I notice @pdelaby added tags to the sample site however when this MR was opened the netlify build was not working. Could you rebase this against master to kick a fresh build? It will render an entirely new copy of the example site along with the changes.

@matalo33 Thanks. I currently run a rebased version of @pdelaby's work on a private project and it works fine (except that I have to restart the server when I touch to taxonomies, but I think it's a limitation from hugo itself).
Here are some screenshots showing how it looks:

After clicking on a tag, it looks like this:

As far as I'm concerned, I think it looks good overall. If I had anything to say, I would say that the taxonomy page (third screenshot) is not very good looking, but I'm not sure how to improve it. At very least, punctuation is incorrect in english and should be fixed.
I don't have much to say on the implementation itself. It looks correctly written to me however I don't contribute a lot to Hugo themes.
There are obvious typos in the English docs, I'll mention the ones I find. Yet, the french version looks perfect.

Thanks for the help @gilbsgilbs :-)  Sorry for the english typos.
We are using this feature on our projects (with a forked repository for now) for 4 months now, and found no bugs yet. Some insights about it :

the tags are case insensitive,
you can search the tags, wich is really cool,
on the taxonomy page, we miss a feature which woud show the number of pages with the tage ( "my first tag (8)", "my second tag (2)", but I don't know how to implement it.

During edition (hugo server -D), I don't have to restart the hugo server to see taxonomy changes (add/remove a tag). What do you mean by "touch to taxonomies" ?

What do you mean by "touch to taxonomies" ?

It's quite easy to reproduce:

Run the server
Create a new taxonomy that doesn't already exist
Click on the taxonomy link
Enjoy the 404
Restart the server
F5
Everything works

As I said, I'm pretty sure hugo is at fault here.
$ hugo version
Hugo Static Site Generator v0.54.0/extended linux/amd64 BuildDate: unknown

Works very well. I really like the styling of the nametag element on the content pages. I agree that the taxonomy page could use some more work. I am not a designer though :)
Some sample tag pages from other themes:
https://themes.gohugo.io//theme/hugo-theme-jane/categories/themes/
https://themes.gohugo.io//theme/hugo-flex/tags/shortcodes/
https://themes.gohugo.io//theme/hugo-w3-simple/tags/interesting/
https://themes.gohugo.io//theme/mero/tags/markdown
@pdelaby Please could you address the pull request feedback already provided?

we would show the number of pages with the tage ( "my first tag (8)", "my second tag (2)", but I don't know how to implement it.

Some of the examples above include this feature, however we can track this as a future improvement to get the feature released sooner than later.

Thanks for everything @pdelaby. If you could just get this branch rebased and ready for merge I'm happy to proceed.

Thanks :-)
So, just to be sure, the 4 commits on top of the updated master (upstream/master) ?

My bad, actually I could do this myself! Thanks again


during installation, check the existence of the latest patch and install it

A new installer has been developped in Python, that install the latest patch.
Fixed in commit eee4ce6


[iOS/Android] missing translation for French language

Hi all! Translation is missing for this screen for French language and maybe for other!
    "@stripe/stripe-identity-react-native": "0.2.1",
    "@stripe/stripe-react-native": "0.31.1"

Hi @nicolasdevienne this is a new screen we recently introduced and translation should be available soon, will update in the ticket when translation is available.

fixed in https://github.com/stripe/stripe-identity-react-native/releases/tag/v0.2.2


The class methods are being rendered as heading level 2 (h2) instead of heading level 4 (h4) in docs

Tagged against the wrong project.


Error "java.net.UnknownHostException: carts-db: Try again" on kuberenetes setup

Add labels appropriate to the issue
kubeadm version v1.7.3
Newtork plugin weave net
Describe the expected behaviour and the actual behaviour
Carts-db should have been found as it is deployed correctly.
Describe steps to reproduce the problem

Setup kubernetes cluster
install weave net plugin
create sock-shop namespace using "kubectl create namespace sock-shop"
deploy sock-shop either using manifest files or complete-demo.yml file, e.g. "kubectl apply -f complete-demo.yaml"
run the command "kubectl get logs carts-container-name-in-your-setup -n sock-shop"
2017-08-17 12:17:01.137  INFO [carts,,,] 13 --- [-carts-db:27017] org.mongodb.driver.cluster               : Exception in monitor thread while connecting to server carts-db:27017

com.mongodb.MongoSocketException: carts-db: Try again
at com.mongodb.ServerAddress.getSocketAddress(ServerAddress.java:188) ~[mongodb-driver-core-3.2.2.jar!/:na]
at com.mongodb.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:50) ~[mongodb-driver-core-3.2.2.jar!/:na]
at com.mongodb.connection.SocketStream.open(SocketStream.java:58) ~[mongodb-driver-core-3.2.2.jar!/:na]
at com.mongodb.connection.InternalStreamConnection.open(InternalStreamConnection.java:114) ~[mongodb-driver-core-3.2.2.jar!/:na]
at com.mongodb.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:128) ~[mongodb-driver-core-3.2.2.jar!/:na]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111-internal]
Caused by: java.net.UnknownHostException: carts-db: Try again
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) ~[na:1.8.0_111-internal]
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928) ~[na:1.8.0_111-internal]
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323) ~[na:1.8.0_111-internal]
at java.net.InetAddress.getAllByName0(InetAddress.java:1276) ~[na:1.8.0_111-internal]
at java.net.InetAddress.getAllByName(InetAddress.java:1192) ~[na:1.8.0_111-internal]
at java.net.InetAddress.getAllByName(InetAddress.java:1126) ~[na:1.8.0_111-internal]
at java.net.InetAddress.getByName(InetAddress.java:1076) ~[na:1.8.0_111-internal]
at com.mongodb.ServerAddress.getSocketAddress(ServerAddress.java:186) ~[mongodb-driver-core-3.2.2.jar!/:na]
... 5 common frames omitted

also the front-end access using http://<master_ip>:30001 shows similar to shown in the issue 717.

Hi @amar123deep.
I've faced a similar problem and worked around it by deploying with the complete-demo. It's usage is documented in Deploying Sock Shop on any Kubernetes cluster.
Note that, if you use the complete-demo.yaml, you'll have to create the sock-shop namespace -- as complete-demo does not include it (#733).

For future reference: if anyone runs into this issue, please check that all of the containers/services are up and running. The user-sim container can start before the other services are ready.

Further testing: the java.net.UnknownHostException seems like a timing error - it's only reproducible in my D4M, or on very small EC2 instances where the services are slow to start up.
Closing, pending further info.


Make long distance jumps less complex

This image explains it better than I could with words.

A [count]j would be much more understandable.

The current weights should make this work, however since other motions end up much closer to the goal, the heuristic causes step-by-step movement not to be considered.
Something such as the Bellman-Ford algorithm would fix that problem, however there would be a huge performance hit.


refresh indexes to avoid weird pandas errors

Codecov Report

Merging #28 into master will increase coverage by 1.58%.
The diff coverage is 87.5%.

@@            Coverage Diff            @@
##           master     #28      +/-   ##
=========================================
+ Coverage   68.62%   70.2%   +1.58%
=========================================
  Files          10      10
  Lines        1294    1299       +5
=========================================
+ Hits          888     912      +24
+ Misses        406     387      -19

Impacted Files
Coverage Δ

pybmpdb/dataAccess.py
83.42% <100%> (+5.34%)
:arrow_up:

pybmpdb/summary.py
46.06% <83.33%> (+0.48%)
:arrow_up:

pybmpdb/tests/test_dataAccess.py
89.94% <0%> (+1.18%)
:arrow_up:

pybmpdb/info.py
65.3% <0%> (+16.32%)
:arrow_up:

Continue to review full report at Codecov.

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


property "items" ignored in type definitions

definition obj_conversation from slack api swagger scheme

returns type any

fixed in release 1.5.0


Textarea element using md-input when binding model has initial state as dirty in IE

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Textarea element using md-input when binding model has initial state as pristine in IE
What is the current behavior?
Textarea element using md-input when binding model has initial state as dirty in IE
What are the steps to reproduce?
Using md-input on textarea element and bind model into it.
Plunker example: https://plnkr.co/edit/SQ3o6X19M6isDB3ShFSK?p=preview
Inspect Address textarea in browser development tool. md-input-container element has ng-pristine class in Chrome/Firefox/Edge while it has ng-dirty class in IE
Which versions of Angular, Material, OS, browsers are affected?
Material: 2.0.0-beta1
Browser: IE11

This looks like an angular forms issue since the same thing happens with a plain textarea not inside a md-input-container. Please open an issue at https://github.com/angular/angular


Amplify.API.mutate(of:, type: .delete) / Amplify.DataStore.delete GraphQL $input only contains model.ID

API, Datastore, Bug / Enhancement
I'm having trouble using API/Datastore '.delete' with the new (preview) Amplify plugins.
My problem is that GraphQL endpoint only receives ID as $input when deleting an item through the new plugins.
I am using some custom resolvers at AppSync level, and I need more attributes to be sent with the GraphQL deletion request as input.
This affects to any custom defined input DeleteModelInput{} schema definition as well (independently of using custom resolvers),  plus I guess this may affect as well to @models without ID as index with normal (non-versioned) API plugin, and Datastore (depending on AppSync service delete operation implementation for versioned datasources).
This use case works fine with previous (sdk) API, but I find it a limitation for the new plugins.
Related files:

GraphQLDocument+DeleteSyncMutation.swift: only ID attribute is added to the input.
https://github.com/aws-amplify/amplify-ios/blob/389cb6e5d708553287265314d294af0b15af6c96/AmplifyPlugins/Core/AWSPluginsCore/Model/GraphQLDocument/GraphQLDocument%2BDeleteSyncMutation.swift#L60-L69

GraphQLDocument+Mutation.swift: in case it is a create or update mutation all attributes are added, but in the event of delete mutation only ID attribute is added to the input.
https://github.com/aws-amplify/amplify-ios/blob/389cb6e5d708553287265314d294af0b15af6c96/AmplifyPlugins/Core/AWSPluginsCore/Model/GraphQLDocument/GraphQLDocument%2BMutation.swift#L61-L73

Error I get:

GraphQL response
Got failed result with GraphQL service returned a successful response containing errors: [Amplify.GraphQLError(message: "Variable \'input\' has coerced Null value for NonNull type \'ID!\'", locations: Optional([Amplify.GraphQLError.Location(line: 1, column: 34)]), path: nil, extensions: nil)]
CloudWatch log:

db265507-e825-7a19-pm8e-ad37t78549ut GraphQL Query: mutation DeleteModel($input: DeleteModelInput!) {
  deleteModel(input: $input) {
    id
    attr1
    attr2
    attr3
    attr4
    attr5
    createdAt
    owner
    updatedAt
    __typename
    _version
    _deleted
    _lastChangedAt
  }
}, Operation: null, Variables:
{
    "input": {
        "id": "D1626D8C-D0E0-4D75-A31B-7D7936285C38"
    }
}

CloudWatch log should include all attributes:

db265507-e825-7a19-pm8e-ad37t78549ut GraphQL Query: mutation DeleteModel($input: DeleteModelInput!) {
  deleteModel(input: $input) {
    id
    attr1
    attr2
    attr3
    attr4
    attr5
    createdAt
    owner
    updatedAt
    __typename
    _version
    _deleted
    _lastChangedAt
  }
}, Operation: null, Variables:
{
    "input": {
        "id": "D1626D8C-D0E0-4D75-A31B-7D7936285C38",
         "attr1": "...",
         "attr2": "....",
         "attr3": "...",
        ...,
        ...
    }
}

Hello @drochetti !
I have stumble upon a specific API/Datastore behavior I was not expecting. Could you have a look at it?
Thank you very much in advance.

I have opened a Feature Request to go further on this, so input per operation can be customized as with previous API category (sdk) was doable.
https://github.com/aws-amplify/amplify-cli/issues/3109

Could you provide us with the schema or documentation around having multiple input fields, in addition to the id? If you are trying to delete the model by the identifier, why do you need to specify the attributes values as well?

Could you provide us with the schema or documentation around having multiple input fields, in addition to the id? If you are trying to delete the model by the identifier, why do you need to specify the attributes values as well?

Hello,
You may achieve your use case by crafting a custom GraphQL request as mentioned in our documentation here:
https://docs.amplify.aws/lib/graphqlapi/advanced-workflows/q/platform/ios/
Please let us know if this works or if you have other questions.

Please see above usage for how to achieve your use case


Add user profiles, inter-user messaging, and a moderated message board for studies

It would be a nice to add some social networking to Qiita to encourage users to interact and collaborate on studies.
We could have a page for each user where they can provide information about themselves, their research, links to papers, etc. and a list of public studies they're a part of (harvested from the same query we do when populating the studies view).
We could also enable a basic inter-user messaging system and/or a moderated comment section on study pages so users would be encouraged to directly ask questions about studies and coordinate more.

Facebook or Google hangouts anyone? BTW why do you consider this medium? Wondering cause I see it as nice to have AKA low!

Haha, well, I labelled it as a medium as it's something to consider pre-publication/official launch. It's not a workshop priority, but I'm considering creative ways to make Qiita a place people want to interact with and visit frequently.
What do you think @wasade ?

I spoke with Pieter last week as well as several users over the course of the last few months and this would definitely a nice feature to have pre-publication to support robust usage.
@wasade suggested that an alternative would be to have an API hook so studies could be referred to or embedded in some way from other platforms as an alternative which also seems fine. Anything to support usage, collaboration, and meta-analysis is good.


prevent out of bounds index < 0

This is really useful for removing items only if they are found in the array:
var arr = ['a', 'b', 'c']
remove(arr, arr.indexOf('d'))
arr // ['a', 'b', 'c']

Awesome. Released in 1.0.2


KeyError: 'last_hidden_state'

System Info
optimum-1.16.2

Who can help?
@michaelbenayoun
@JingyaHuang
@echarlaix
Information

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

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[X] My own task or dataset (give details below)

Reproduction (minimal, reproducible, runnable)
export model and predict code
`
pretrained_model_path = './checkpoints/bge-base-zh'
export_model_path = './checkpoints/onnx'
# model = ORTModelForFeatureExtraction.from_pretrained(pretrained_model_path, from_transformers=True)
tokenizer = AutoTokenizer.from_pretrained(pretrained_model_path)

# optimizer = ORTOptimizer.from_pretrained(model)
# optimization_config = OptimizationConfig(optimization_level=99, optimize_for_gpu=True)  # enable all optimizations
#
# # apply the optimization configuration to the model
# optimizer.optimize(
#     save_dir=export_model_path,
#     optimization_config=optimization_config
# )
# provider = "CUDAExecutionProvider"

model = ORTModelForFeatureExtraction.from_pretrained(export_model_path, file_name="model_optimized.onnx")
vanilla_emb = SentenceEmbeddingPipeline(model=model, tokenizer=tokenizer)
pred = vanilla_emb("你好")
print(pred[0][:5])

`
Expected behavior
use  bge-base-zh model than have two errors

onnxruntime.capi.onnxruntime_pybind11_state.InvalidArgument: [ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Invalid Feed Input Name:token_type_ids
File "/mnt/data/work/.conda/envs/torch_env/lib/python3.8/site-packages/optimum/modeling_base.py", line 90, in call
return self.forward(*args, **kwargs)
File "/mnt/data/work/.conda/envs/torch_env/lib/python3.8/site-packages/optimum/onnxruntime/modeling_ort.py", line 960, in forward
last_hidden_state = outputs[self.output_names["last_hidden_state"]]
KeyError: 'last_hidden_state'

I fixed the bug and create a PR.
PR: https://github.com/huggingface/optimum/pull/1674
I tested it locally with the changes on your model and it works.
Full example notebook:
https://github.com/satishsilveri/Semantic-Search/blob/main/Optimize_SBERT/BAAI_bge_base_zh.ipynb


Add base html tag to the iframe when building

Most of the time, we host our storybooks in a subpath of the domain. So resources started with / doesn't work properly.
So, we need add a <base> tag with a proper subdomain (and the path) to the iframe. This needs to be done, when building the storybook.

This should go in the head tag right? Adding custom head content is already possible with the head.html

Yeah. That's a good idea as well.
But, I need to make this pretty simple by providing an argument when we are building the storybook.

Got it. I will work on this.

We don't need now.
See: https://getstorybook.io/docs/configurations/serving-static-files#absolute-versus-relative-paths


feat(generic): add Sliding

What?
add Sliding
https://laravel.com/docs/9.x/collections#method-sliding
Why?
It's on the todo list
How?
using slice ranges to accumulate the windows

Codecov Report
Base: 97.99% // Head: 98.02% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (fda99e0) compared to base (9fb17aa).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #73      +/-   ##
==========================================
+ Coverage   97.99%   98.02%   +0.02%
==========================================
  Files           7        7
  Lines         999     1011      +12
==========================================
+ Hits          979      991      +12
  Misses         14       14
  Partials        6        6

Impacted Files
Coverage Δ

generic.go
100.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


unit tests for filters

Last test with detecting face (Kirill's implementation) fails for some reason. I've checked the output, it draws a rectangle to a found face, but I can not understand why assertion for not equal input and output fails. Plz check it.
All other tests run okay, all computations are made by hands and work fine.

Accidentally pushed these changes with other commit.


Added a minimal zoom change for refreshing the cluster

Sometimes the clustering is refreshing even if the zoom is almost invisible.
This cause the PopoverView to close, I needed to make it less sensitive.
Not sure if you need this PR, up to you :ok_hand:

@CWalig, thanks for the contribution!


[FEATURE] Projects cards

Description
We can make card like feature for projects same as contributors cards
The projects details can be fetched from project.json file
Enhancement can be added for the cards styling using tailwind
Screenshots

who want to work on this?

Hi @FrancescoXX ,
I can take this

done thanks


Getting error during tns build android

Hi,
We just started using google maps and after adding the plugin  we are getting the following error message. We made sure the "Google play services and Google Repository" was installed. I am trying to build the android app in Mac. Please let me know how I can resolve this error.
Thanks
What went wrong:
Execution failed for task ':transformClassesWithDexForF0F1F2F3F4F5F6F7F8Debug'.

com.android.build.api.transform.TransformException: com.android.ide.common.process.ProcessException: java.util.concurrent.ExecutionException: com.android.dex.DexException: Multiple dex files define Lcom/google/android/gms/internal/zzbzv;

Hi,
Same here having problem building in Android.
{N} Cli = 3.3.0
tns-core-module = 3.3.0
tns-Android = 3.3.1
tns-ios = 3.3.0
Thanks.

Usually that means you're using another plugin which is using a different version of the Google Play Services sdk.  Set the googlePlayServicesVersion per the instructions to match the plugin's versions.
FYI - this is currently broken in tns-Android version 3.3.0 (@see https://github.com/NativeScript/android-runtime/issues/878) - but should have been fixed in 3.3.1

Hi @dapriett dapriett,
project.ext {
googlePlayServicesVersion = "+"
}
After adding the code above to my app.gradle file, another issue encounter during build it does not continue and hangs up. The last line in the error the last task it did.
Did this:
tns platform remove android
tns platform add android
tns build android
Error:

adding jar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-local-notifications/platforms/android/libs/localnotlib.jar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/Chart-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/List-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/Feedback-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/Common-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/Input-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/Data-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/Gauges-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/nativescript-pro-ui/platforms/android/Primitives-2017.1.1030-dev-release.aar
+ adding aar plugin dependency: /Users/Dennis/MetrobankSpace/MobileBankingSystem/node_modules/tns-core-modules-widgets/platforms/android/widgets-release.aar

Environment version:
{N} Cli = 3.3.0
tns-core-module = 3.3.0
tns-Android = 3.3.1
tns-ios = 3.3.0
regards,
Dennis


Does not warn or error on conflicting version requirements

For example, if the pipfile specifies a dependency with version <=2.5.1, while the same package also occurs as a transitive dependency with version >=2.6.0, then both pipfile and pipfile.lock will agree that the version is 2.5.1, but it will silently install 2.6.0 in the virtualenv, without showing any warnings or errors about the conflicting requirements.

Hey, thanks for checking in on this. We're currently aware of this and tracking the progress in #298. We have an open PR that will attempt to make this a little less subtle, but there are a couple snags that still haven't been resolved. pip itself doesn't actually handle the transitive dependency problem, but pipenv's behaviour is currently even more out of line than pip. We'll hopefully have this sorted in a future release.


[AutoPR cognitiveservices/data-plane/ComputerVision] Analyze brands

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5141

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2978


⚠ Bofrost.be has degraded performance

In 687aa28, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1416 ms

Resolved: Bofrost.be performance has improved in e4a5957.


Polyline tooltips seem inconsistent

Here are a bunch of polylines with tooltips bound to them:
https://www.dropbox.com/s/1bwladr9kmr128e/leaflet-polyline-tooltip.mov
Note that the tooltips appear at the top-left of rectangular polylines, but at the center-left-ish? of non-rectangular ones.
I was trying to set the offset of tooltips to be the center of the polylines, but since the offset added to the default position of the tooltip, and that default position seems inconsistent, it's hard to add to.
Related, it looks like the tooltip.offset option is meant to be in pixels, but that means you need to change it after every pan/zoom? Seems like it should be a lat/long instead, then it could be set once per layer.

Note that the tooltips appear at the top-left of rectangular polylines, but at the center-left-ish? of non-rectangular ones.

I bet that's the first defined point in your dataset.

I was trying to set the offset of tooltips to be the center of the polylines

What do you mean by "center"? Centroid? Midpoint (point at the middle lf the length of the line? Something else? Please be specific, the vocabulary here is confusing.

The centroid would be ideal, but I was trying to put it at the center point of the geometry's bounding box. I was struggling to do that because it's not clear what the offset property is relative to.
It seems like it would be easier to work with if you could just set its absolute position, like L.Popup.setLatLng.
I'm generating these polylines in maybe a weird way, by getting a Path element from an SVG DOM, and collecting points along its length. I guess if the first point in my list is the "origin" I could figure it out based on that?
const points = [];
const len = path.getTotalLength();
let j = 0;
while (j < len) {
  const point = path.getPointAtLength(j);
  points.push([-point.y, point.x]);
  j += 1;
}

const opts = { smoothFactor: 1 };
const polyline = L.polyline(points, opts).addTo(this.map);
polyline.bindTooltip('stuff')

The centroid would be ideal

No, you don't want to use centroids for polylines, as the centroids will most probably be far away from the polyline. Polygons are a bit better, but do check https://blog.mapbox.com/a-new-algorithm-for-finding-a-visual-center-of-a-polygon-7c77e6492fbc

It seems like it would be easier to work with if you could just set its absolute position, like L.Popup.setLatLng.

Hhhmm, something similar but for tooltips makes a lot of sense. Perhaps @perliedman can shed some light on why the tooltip interface doesn't have that?

Not entirely sure why it isn't in the docs, but since Tooltip as well as Popup inherits DivOverlay, they both do have setLatLng. Example: http://playground-leaflet.rhcloud.com/tuta/edit?html,output
Having said that, for this case interaction doesn't really work as I would expect. It sounds like a latLng option or similar would be good.
@yohanboniface do you have any input on this, I think you put some thought into the tooltip API, but perhaps this use case didn't come up?

Tooltip are positionned with latlng like other divoverlays, yes.
You basically have:

position, in latlngs (comes from getCenter/getLatlng at the moment, see below for a suggestion)
anchor in px and depends on the layer it self (comes from _getAnchor, only used for Markers)
offset in px, and depends on the tooltip itself

It should be totally possible to use setLatlng on the tooltip.
One option I'm thinking of now is to allow passing the latlng as an option of bindTooltip, so it's easier to set it (instead of needed to create the tooltip by hand).

As workaround, have you tried something like (not tested):
layer.bindTooltip('xxx').openTooltip(layer, yourlatlng)

I decided I'd rather have the tooltip at the mouse position, and follow the mouse. I was able to get that working.
https://www.dropbox.com/s/ph7i6aiy6u3rezu/leaflet-polyline-tooltip-follow.mov
So really this bug should be "how do I position a tooltip with absolute coordinates?", and the answer is "use openTooltip(<LatLng> latlng?)". It just took a while to figure it out.
if (!this.tooltip) {
  if (this.defaultZoneLayer) {
    this.tooltip = this.defaultZoneLayer.bindTooltip('', { direction: 'right' });
  }
}

if (this.tooltip) {
  if (hits.length) {
    this.tooltip.setTooltipContent(hits.join('<br>'));
    const pos = { clientX: e.clientX + 10, clientY: e.clientY };
    this.defaultZoneLayer.openTooltip(this.map.mouseEventToLatLng(pos));
  } else {
    this.defaultZoneLayer.closeTooltip();
  }
}

Ok, good discussion.
It sounds to me like this has been cleared up now. Can we close, or are there things in Leaflet that should be addressed?

Seems like it could be closed, but it might be worth considering unifying the tooltip/marker APIs, since they're conceptually so similar.

Agreed, I think further unification would be cool, even though they're already pretty close.
I'm closing this issue now, since contains quite a lot of noise. Let's open a new issue if we have actionable suggestions for improving the tooltip/popup APIs.

Hi @endquote,
For the use case where you want the Tooltip to follow the mouse, it seems to me that the sticky option might be what you need:
http://playground-leaflet.rhcloud.com/wele/1/edit?html,output
myShape.bindTooltip('tooltipText', {
  sticky: true // If true, the tooltip will follow the mouse.
});

You may also use it in combination with offset and direction options.


Add utilities to quickly generate test setups

This PR is based on earlier work by @franziskuskiefer and includes the means to create configurations for clients and groups, as well as a function to create a TestSetup from these configurations.
As a showcase, I've changed the padding test such that it makes use of the new testing setup.
I've also changed the visibility of some select functions, please let me know if you think there's a better way of handling things.
Not everything is super refined here, so please let me know if there is something I should improve. Keep in mind, though, that this is only meant for tests. I'm sure we'll know more once we've tried using this framework for other tests.

This is still marked as 'draft'. You should mark it as 'ready for review' before requesting a review, otherwise it's unclear if you are still going to make changes to it.
I'm hesitant to make more fields of the group public. If they are needed in integration tests, then the integration tests might be better off as unit tests. Integration tests are there to test the public API primarily.

Ah, sorry. I thought GitHub was smart enough to send out the review requests only after it was marked "Ready for Review".

I'm not sure we actually need tests here. Each test that we implement with this testing framework should be a test in and of itself, shouldn't it?

I'm not sure we actually need tests here. Each test that we implement with this testing framework should be a test in and of itself, shouldn't it?

There is no way to know if the code you wrote behaves correctly if you don't test it. We always need tests for any code. In scenarios where unit tests are difficult to write, it might be ok to go for integration tests only. Here however it's very easy to test this with a unit test:
#[test]
fn test_setup() {
    let test_client_config_a = TestClientConfig {
        name: "TestClientConfigA",
        ciphersuites: vec![CiphersuiteName::MLS10_128_DHKEMX25519_AES128GCM_SHA256_Ed25519],
    };
    let test_client_config_b = TestClientConfig {
        name: "TestClientConfigB",
        ciphersuites: vec![CiphersuiteName::MLS10_128_DHKEMX25519_AES128GCM_SHA256_Ed25519],
    };
    let group_config = GroupConfig::default();
    let test_group_config = TestGroupConfig {
        ciphersuite: CiphersuiteName::MLS10_128_DHKEMX25519_AES128GCM_SHA256_Ed25519,
        config: group_config,
        members: vec![test_client_config_a.clone(), test_client_config_b.clone()],
    };
    let test_setup_config = TestSetupConfig {
        clients: vec![test_client_config_a, test_client_config_b],
        groups: vec![test_group_config],
    };
    let _test_setup = setup(test_setup_config);
}

The test is not successful, so there is a high likelihood something is wrong in the setup function 😄

After some debugging using your setup_test function, I think it's not the setup function that's at fault here, but the fact that there's no decode implemented for PathSecret, which we need in GroupSecrets.decode(...).

I still think that any test we implement using this test framework is a test of the test framework as well as a test of whatever it is that it is testing. So your test function certainly helped, but we would have noticed the same thing as soon as we started using the setup function for other tests, wouldn't we?

I understand what you're saying and I don't want to dodge the responsibility for my code. However, I think the way to go would have been to pick another test to translate to use the setup function, i.e. one that make a bit more thorough use of setup. Other than the padding test, that is. That would make that test a test for the setup function.


Add ENTER ESC hotkeys

Add the ability to close the window that displays the zoomed version of the line selected using enter or discard it using escape.

This is no longer necessary since the plot was integrated into the interactive window.


feat: Autogen CCI config from manifest. YML manifest. Simplify YBP.

This contains some fairly hefty changes to how we build.

build_manifest.json is now build_manifest.yml (leaner and we can add comments!)
build_manifest.sh is gone. bootstrap_docker.sh knows what to build depending on what you ask it to build. WIP

Fixup args.

.circleci/config.yml is now autogenerated from .circleci/config.template.yml and build-system/cci_gen. WIP

Deployment stuff not yet there
Tests need "additional dependencies"
Hook to run it before commit needs adding.

Remove some unneeded installs from barretenberg/cpp/dockerfiles/Dockerfile.wasm-linux-clang
jq removed from repo as installed by default in ubuntu. But... yq isn't on our spot AMI, so adding for now.
We shift to using docker buildkit with DOCKER_BUILDKIT=1 being set. Needed so we can have different .dockerignore files for the same build dir. Also it's just the newer, faster way.
build_manifest.yml is more expressive. You can:

Request a job run on a spot by setting spot property to number of vcpus.
Attach test jobs to a build job.
Specify test commands simply as script and args to run (no messing with cond_spot_blah).

yarn-project-base now doesn't need to have every workspace listed in it. The dockerignore file ensures only the package.json and tsconfig.json files are in the context.
yarn-project now has a Dockerfile at root that builds upon the above. It includes the full workspace, builds it, checks formatting, and runs all the unit tests in parallel on a 64 core machine (e2e and canary tests excluded).
Various tweaks to various files to make formatting, tests etc pass in this way.

TODO

WIP stuff above.
Remove unneeded Dockerfiles etc from yarn-project projects.
Move noir-contracts noir (non ts code) up to top of repo.
Move aztec-nr (non ts code) to top of repo.
Fix up some comments/readme stuff that's not ready.

@charlielye Hmm there was errors on yarn-project-base-deps. Changed this to FROM<PHONE_NUMBER>00.dkr.ecr.eu-west-2.amazonaws.com/yarn-project-base but seems funky, what was creating this image before?

I note the comments about using docker image steps instead of content hash. Seems a bit odd. Surely if you're wanting to test the docker stack we can do with a commit. It feels a bit bad to do stuff in docker steps as it will always be redundant with the non-docker flow

Looks like cond_run_test is not longer callable. Had to go before looking into it.


Use less severe log level when handle SIGTERM or SIGINT

User can get confused by exit 1 after Shutdown method
of http server finishes.

Coverage remained the same at 60.078% when pulling d1c68f015c86d94fbecfdef29268e9575d694a19 on stgleb:less_severe_logging into 3dad26616173a7cafab4dc50f563a28560f8c47f on supergiant:master.


move fixStatsType to utils; add unit tests

Codecov Report

Merging #123 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #123   +/-   ##
======================================
  Coverage    99.8%   99.8%
======================================
  Files           6       6
  Lines        1020    1020
======================================
  Hits         1018    1018
  Misses          2       2

Impacted Files
Coverage Δ

rtcpeerconnection.js
99.76% <100%> (-0.01%)
:arrow_down:

util.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


V1.4.1RC4: Landing detector not working properly in all situations

After triggering auto-landing the vehicle landed on a slope surface. Doing so, I face a strange sequence of state changes:

Can you share a log for this please?

Another short landing test shows that failsafe was triggered again, after landing was detected:

For this the log is: http://logs.uaventure.com/view/FLCCUajbQcMbRZYCqtJ8M8

I looked at all the data that could trigger a take-off detected and I can't see which one would have triggered it. If you can debug this further with some printfs that would be helpful.

Maybe this issue occurs, because the vehicle is still wobbling (roll rate, pitch rate) on sloppy surfaces due to the relative high thrust during auto-landing.  The takeoff is detected about 1/2 second after landing. Maybe a time hysteresis would help here.

@julianoes Additionally I've found out, that after auto-landing, the state is switched back to position hold (the state was in when triggering auto-landing):

Additionally RollRate and PitchRate were quite high during landing.

Any update?

Fixed for me with current master

Thanks.


Graylog chart fails to start - chown: changing ownership of '/usr/share/graylog/data/journal': Operation not permitted

Is this a request for help?: No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Version of Helm and Kubernetes:

Helm v2.13.1
Kubernetes v1.14.1

Which chart: stable/graylog
What happened:
Graylog fails to start because Init Containers provided by the chart do not correctly adjust file permissions in some cases.
More specifically, when PVs are automatically provisioned by a storage class (such as OpenEBS), the location of the PV on disk is inaccessible unless mounted in a container. This makes it difficult to workaround, since it is not possible to chown the PV data from outside the runtime.
The graylog container will start after its initContainer, but fail nonetheless because its user cannot chown the journal directory:
chown: changing ownership of '/usr/share/graylog/data/journal': Operation not permitted
Current master is
Launching graylog-0 as master
pod/graylog-0 labeled
Starting graylog
Graylog Home /usr/share/graylog
Graylog User graylog
JVM Options -Djava.net.preferIPv4Stack=true -XX:NewRatio=1 -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow -Xms1024g -Xmx1024g
2019-04-27 04:05:49,687 INFO    [CmdLineTool] - Loaded plugin: AWS plugins 3.0.1 [org.graylog.aws.AWSPlugin] - {}
2019-04-27 04:05:49,693 INFO    [CmdLineTool] - Loaded plugin: Collector 3.0.1 [org.graylog.plugins.collector.CollectorPlugin] - {}
2019-04-27 04:05:49,694 INFO    [CmdLineTool] - Loaded plugin: Threat Intelligence Plugin 3.0.1 [org.graylog.plugins.threatintel.ThreatIntelPlugin] - {}
2019-04-27 04:05:49,788 ERROR   [CmdLineTool] - Invalid configuration - {}
com.github.joschi.jadconfig.ValidationException: Parent directory /usr/share/graylog/data/journal for Node ID file at /usr/share/graylog/data/journal/node-id is not writable
	at org.graylog2.Configuration$NodeIdFileValidator.validate(Configuration.java:302) ~[graylog.jar:?]
	at org.graylog2.Configuration$NodeIdFileValidator.validate(Configuration.java:284) ~[graylog.jar:?]
	at com.github.joschi.jadconfig.JadConfig.validateParameter(JadConfig.java:215) ~[graylog.jar:?]
	at com.github.joschi.jadconfig.JadConfig.processClassFields(JadConfig.java:148) ~[graylog.jar:?]
	at com.github.joschi.jadconfig.JadConfig.process(JadConfig.java:99) ~[graylog.jar:?]
	at org.graylog2.bootstrap.CmdLineTool.processConfiguration(CmdLineTool.java:351) [graylog.jar:?]
	at org.graylog2.bootstrap.CmdLineTool.readConfiguration(CmdLineTool.java:344) [graylog.jar:?]
	at org.graylog2.bootstrap.CmdLineTool.run(CmdLineTool.java:178) [graylog.jar:?]
	at org.graylog2.bootstrap.Main.main(Main.java:50) [graylog.jar:?]

What you expected to happen:
The StatefulSet provided by the chart already has an initContainer that makes a few adjustments to the journal volume. The chart can be easily patched to include a quick shallow chown.
How to reproduce it (as minimally and precisely as possible):
Install this chart providing a PV that points to a journal directory owned by root.
Anything else we need to know:
Hold my beer. PR coming up.

I'm cross relating this to the Graylog container repo.
I'm not sure what's the best way to resolve this:

Make the Graylog container immune to this problem (issue #76 on their side)

Implement a workaround in this chart, but that means introducing an implicit complexity into the chart (see PR thread).

This should be fixed by https://github.com/helm/charts/pull/12983. No longer an issue in my opinion.


'MRZScannerFactory' is not abstract and does not implement abstract base class member public abstract fun create(p0: Context?, p1: Int, p2: Any?): PlatformView

Class 'MRZScannerFactory' is not abstract and does not implement abstract base class member public abstract fun create(p0: Context?, p1: Int, p2: Any?): PlatformView defined in io.flutter.plugin.platform.PlatformViewFactory
flutter_mrz_scanner-2.0.0/android/src/main/kotlin/io/github/olexale/flutter_mrz_scanner/FlutterMrzScannerPlugin.kt: (30, 5): 'create' overrides nothing

facing the same issue with Flutter 3

It's error from null safety of kotlin
please try below in FlutterMrzScannerPlugin.kt
class MRZScannerFactory(private val messenger: BinaryMessenger) : PlatformViewFactory(StandardMessageCodec.INSTANCE) {
override fun create(context: Context?, id: Int, o: Any?): PlatformView {
    return MRZScannerView(context!!, messenger, id)
}

}
Attention
Context?
context!!
From detail, you can see PlatformViewFactory source code:
public abstract PlatformView create(@Nullable Context context, int viewId, @Nullable Object args);

Class 'MRZScannerFactory' is not abstract and does not implement abstract base class member public abstract fun create(p0: Context?, p1: Int, p2: Any?): PlatformView defined in io.flutter.plugin.platform.PlatformViewFactory
.pub-cache/hosted/pub.dartlang.org/flutter_mrz_scanner-2.0.0/android/src/main/kotlin/io/github/olexale/flutter_mrz_scanner/FlutterMrzScannerPlugin.kt: (30, 5): 'create' overrides nothing


[Feature] Waveform keyboard seek to start/end

Problem
Some keyboard navigable audio/video seek bars are able to be jumped to the start or end of the audio by using cmd/super + left/right or home/end. We don't currently implement this.
Description
Add the ability to seek to the start or end of the audio using the keyboard either through meta + left/right or home/end
Additional context
I got this idea checking out this other media player's implementation: https://github.com/IET-OU/mediaelement/commit/25eb64a2097f25bffd5c1420807f5605cbe4e0b0#diff-219f920a90e9fec6455e5cb6863cf6e51831182cd586184b53e5ae3a4e94b32aR102-R108
Implementation

[ ] 🙋 I would be interested in implementing this feature.

I see the value of being able to seek-to-start so as to replay a song. But since we don't have a playlist feature, I'm interested to know how the seek-to-end would be different from just pausing the track.


[Feature] Changing href of main logo

Problem
As there's already an open issue #97 I'd like to add to it. When the user clicks on the logo of the webpage it redirects to https://creativecommons.org/ instead of reloading the archive page which is not good navigation, so my view is that when we click on the logo we should get reloaded archive page and there should be a button "about us" which redirects to https://creativecommons.org/.
Implementation

[x] I would be interested in implementing this feature.

Hey @cmaguluri1305 ,
Nice catch. The idea of reloading the page archive page is pretty reasonable, you can check out issue #68 as it also focuses on a similar idea.
The second part which is "about us button" is already fixed in the issue #68 by @adidevs.

is this implementation already done or not?

Hey @cmaguluri1305 , this is indeed a good issue to put forward. Also, it can be better to change the logo altogether and create a new one for the CC Resource Archive if the maintainers agree to the same. This shall improve the site aesthetic and UX.
Also, the "Creative Commons Resource Archive" header shall be definitely be refactored in the Vocabulary migration and it is then that the logo can be updated along with the href. We can consider an interim solution until then I guess.

I'm closing this and suggest any further convo move to the other mentioned Issues here :)


fix(err):typescript errors fixed (partially)

partially fixed

will try to do the rest later tonight


Minor typo in cht.exe usage description

[spelling]  delimetered
Output of cht.exe on Windows 11
PS C:\Users\smc123\Scoop\apps\cht\current> cht

Usage: C:\Users\smc123\scoop\apps\cht\current\cht.exe  [options...] <URL>
(  without http:// or file:// scheme using cheat.sh server  )
Options:
 -Q, --query       space delimetered arguments are parts of query
 -T, --no_colors   disabling coloring globally

PS: Not tryin' to nitpick here... Love the work that you've done with this concept! Thank you. Will definitely check the open issues and offer some time/code/effort here.

@muenchenscott Even make a pull request, fixing the typo


[Infra][Testing] Update infrastructure to support E2E Test

Objective
Enable E2E Consensus, Scaling & State Sync Tests.
Origin Document
Failure #1; Installing dependencies

Failure #2; Scaling Actors

Goals

Enable scaling actors on DevNet
Enable E2E tests in CI that involve scaling actors

Deliverable

[ ] Search for all TODO(#964) in the codebase and tend to them
[ ] Enabling scaling actors in DevNet
[ ] Update the Makefile targets to have checks pass both on local and remote environments

Non-goals / Non-deliverables

Add new tests
Disable existing tests

Testing Methodology

[ ] E2E Test Locally: make test_e2e
[ ] E2E Test Remote: Add e2e-devnet-test to PR

Creator: @Olshansk
Co-Owners: @okdas @red-0ne

@okdas This is the ticket I was referring to in the weekly sync today.


wip generate updated images list

closing in favor of https://github.com/rancher/rancher/pull/22302


Change the repo to use the latest description from config.json

It currently uses the description manually entered with the first version submissions, which I think we can get rid of in favor of the description in config.json.

Closing as a duplicate of #200


[Feature] Add BasicVSR++

Paper: BasicVSR++: Improving Video Super-Resolution with Enhanced Propagation and Alignment
3 champions + 1 runner-up in NTIRE 2021.

@innerlee may have a look.

Dropping blow 80% is not good

@ckkelvinchan Please add this method to the repo's README


Added listServicePrincipalId

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[X] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[X] No refresh required for updates in this PR

Contribution checklist:

[X] I commit to follow the Breaking Change Policy of "no breaking changes"
[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[X] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[X] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[X] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[X] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[X] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@ikanni, ARM review is waiting until the NewApiVersionRequired label has been addressed. If you want to add a new API to an existing API version, you will need to get breaking change approval. I've added the breaking change label which gives the instructions for requesting breaking change approval. Otherwise, please put the new API into a new API version.

@ikanni, ARM review is waiting until the NewApiVersionRequired label has been addressed. If you want to add a new API to an existing API version, you will need to get breaking change approval. I've added the breaking change label which gives the instructions for requesting breaking change approval. Otherwise, please put the new API into a new API version.

@mentat9 Thank you Chris for reviewing this PR! We got the breaking change approval. Could you please review and add your comments?

@ikanni, ARM review is waiting until the NewApiVersionRequired label has been addressed. If you want to add a new API to an existing API version, you will need to get breaking change approval. I've added the breaking change label which gives the instructions for requesting breaking change approval. Otherwise, please put the new API into a new API version.

@mentat9 Thank you Chris for reviewing this PR! We got the breaking change approval. Could you please review and add your comments?

@mentat9 Thank you Chris for reviewing! I will reply tomorrow.

@ikanni, ARM review is waiting until the NewApiVersionRequired label has been addressed. If you want to add a new API to an existing API version, you will need to get breaking change approval. I've added the breaking change label which gives the instructions for requesting breaking change approval. Otherwise, please put the new API into a new API version.

@mentat9 Thank you Chris for reviewing this PR! We got the breaking change approval. Could you please review and add your comments?

@mentat9 Thank you Chris for reviewing! I will reply tomorrow.

@mentat9 Thank you Chris for sign off!

@ruowan Could you please help in merging this PR?


FTP & SFTP EC2 machines cleanup not working in AWS, when running example_load_file DAG

FTP & SFTP EC2 machines cleanup not working in AWS, when running example_load_file DAG

@vatsrahul1001 can you mention the PR where this has been fixed?


some how boot simulator command sticks and generates files again

After running build_simulator command i see ~/sim_device/1 folder is generated. But after tests finished when i delete this file i see that it is generated again.Some how it is sticked and generates files again and again. How can I prevent that?

@okanerdogan84  - this is an issue i have witnessed as well, and i am not entirely sure of why it happens. deleting the whole workspace folder a few seconds before a run seems to do the trick for me.

@okanerdogan84  - if you need to make this automated, try clearing out the directory before your tests begin at the start of the script.


⚠ Secret Website 3 has degraded performance

In 9833c88, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2303 ms

Resolved: Secret Website 3 performance has improved in 711c191.


[SourceKit/SwiftLang] Keep sourcekitd response alive for variant lifetime

This PR contains two changes to SwiftLang, the Swift layer exposing SourceKit in Swift:

Make each Variant keep a strong reference to its SourceKitdResponse context. This is needed because sourcekitd_variant_t is only safe to use while the sourcekitd_response_t it was retrieved from (wrapped by SourceKitdResponse) is still alive.
Expose the new Data variant SourceKit APIs that were added to support returning the Syntax tree in a binary format in SwiftLang.

@swift-ci please test

Could we also cherry-pick this to swift-5.0-branch afterwards? It's useful to verify syntax tree binary format in a toolchain.


Update documentation

[x] installation guide

[ ] Update Application guides including how to make input

[x] Classification
[x] Training
[ ] DeepQ Learning
[ ] Tizen
[ ] Mnist
[ ] KNN
[ ] Logistic Regression

:octocat: cibot: Thank you for posting issue #443. The person in charge will reply soon.

@jijoongmoon Please update which applications have been documented. If all are done, let's close this.


Test Result Management

The management of test case results need to be defined.

Clear definition which test results will be created,
definition of the procedure to create certification (how to deal with multiple test case result and with different parameter settings?)
do we need signing of test results?
report generation

see test report feature included in release 3.0.0


[devseed] Create a helm chart called jupyterhub-home-nfs (or similar)

To integrate the NFS quotas into 2i2c infrastructure, we need a helm chart that sets up the required resources via kubernetes. This issue tracks creating that helm chart.
For now, the chart should just handle setting up these resources on AWS, and should be enabled by config that looks like:
jupyterhub-home-nfs:
  aws:
    enabled: true
    aws-key-one: foo
    aws-key-two: bar

Compatibility with GCP and Azure can be tackled in future work.
Also, the EBS volumes should be setup assuming that the cluster are single zone. Multi-zone support can be tackled later.
Definition of Done

[ ] A new helm chart containing the jupyterhub-home-nfs resources exists

Helm repo is here: https://github.com/sunu/jupyter-home-nfs


Use canonical name for search-api instead of legacy search.

This is a breaking change because of the way the test helpers currently work, but I have PRs to fix all the occurrences of the legacy search name throughout alphagov ready to go once this is released, so it should be seamless.
Cleaning this up now means there's one less thing to trip over for Replatforming.

Turns out this needs a Puppet change as well. alphagov/govuk-puppet#11870


Add Push Image to Openshift local cluster as option for image

As of now we have option Push Image to kind cluster which works with kind cluster. We also need an option for Push Image to Openshift local cluster which sync image from podman machine instance to openshift Local instance.
Moved from https://github.com/containers/podman-desktop/issues/2263

I miss feedback that the task started (ongoing) and finished. Is this also the case for Kind?


gh-12: Allow passing of tagMap and typeMap args

I'm not too familiar with the code base, but this looks good to me and fixes the issues we encountered with mitmproxy! :)


🏗 Add validation before country code update

We need to ensure the country code being passed into the supabase function is a valid country.
https://github.com/Thenlie/Streamability/blob/develop/src/supabase/profiles.ts#L239
This should be created as a util function with a unit test to ensure it works.

Closed by #614


Add 404 template matching the original hyde theme

After https://github.com/getzola/zola/issues/571 was closed, this provides a 404 page like the original theme.
Solves #16

Perfect, thanks


This version of Terraform has an outdated GPG key

Issue:
I followed the instructions as per the README on how to install the project's binary file, proceeding to place it on my $PATH, returning this following error afterward:
Full logs:
sh awsls vpc -a tags  | grep Name=vpc | awsrm

failed to install provider (aws): 2 problems:
- registry.terraform.io: This version of Terraform has an outdated GPG key and is unable to verify new provider releases. Please upgrade Terraform to at least 0.12.31 to receive new provider updates. For details see: https://discuss.hashicorp.com/t/hcsec-2021-12-codecov-security-event-and-hashicorp-gpg-key-exposure/23512
- open ~/.awsrm/terraform-provider-aws_v3.16.0_x5: text file busy
Error: failed to launch provider (): fork/exec : no such file or directory

This bug seems to refer to this thread on Hashicorp's forums
Something curious to be noted is that my machine's Terraform is at v15.x already. So it might have something to do with the project dependencies.
All the best.

Thanks @gruberdev for opening the issue. I'll update awsrm to the newest Terraform AWS Provider version and let you know when done.

Hi @gruberdev again, I switched to a newer Terraform AWS Provider in https://github.com/jckuester/awsrm/releases/tag/v0.2.0. Let me know if awsrm works for you know. Thanks!

Hi @gruberdev again, I switched to a newer Terraform AWS Provider in v0.2.0. Let me know if awsrm works for you now. Thanks!

I will test soon enough in a clean environment to report back to you, thanks for keeping my updated!

It worked perfectly, thanks @jckuester!


Replace Audio5js with Howler to improve mobile background media playback

Replace audio player which is used to

play atmo audios
play audio hotspots of linkmap page

The audio page already uses VideoJS to allow text track display.
Howler uses WebAudio API on modern browsers which allows partially working around autoplay limitations on Safari and mobile browsers:

Add a button which is displayed initially to enable background media playback. This first user interaction is needed to unlock the audio context.
Use unlocked audio context to play sound of muted background videos.
No longer disable atmo on mobile devices.

Coverage remained the same at 99.363% when pulling 34b55a0af243bad6127a69c31f19279bdd61ccd8 on tf:autoplay-muted-bg-videos-2 into 2e1de1092a6b60d9eff4082341d7adcb3c593a7c on codevise:master.

@tilsammans We are currently testing this on a staging system. Could you also take it for a spin?

Have been fighting with some subtle bugs inside Howler. Optimistic that these can be solved.


[Release] Damascus 1.2.0

[ ] Wiki pages: config and guardrails
[ ] Edit changelog

Config instructions added to Wiki, with reference to Guardrails for details on JSON structure.

Prepare to launch!


Update cert chain

I promise I'll add documentation on wtf I did if we can prove this worked.

:+1:

I added docs to the README.


Build failure with musl libc due to use of obsolete makecontext

Build failure on Alpine Linux:
${LDCMD:-gcc} -pthread -m64 -Wa,--noexecstack -Wall -O3 -Os -fomit-frame-pointer -Os -fomit-frame-pointer -g -Wa,--noexecstack -L.  -Wl,--as-needed \
        -o apps/openssl apps/asn1pars.o apps/ca.o apps/ciphers.o apps/cms.o apps/crl.o apps/crl2p7.o apps/dgst.o apps/dhparam.o apps/dsa.o apps/dsaparam.o apps/ec.o apps/ecparam.o apps/enc.o apps/engine.o apps/errstr.o apps/gendsa.o apps/genpkey.o apps/genrsa.o apps/nseq.o apps/ocsp.o apps/openssl.o apps/passwd.o apps/pkcs12.o apps/pkcs7.o apps/pkcs8.o apps/pkey.o apps/pkeyparam.o apps/pkeyutl.o apps/prime.o apps/rand.o apps/rehash.o apps/req.o apps/rsa.o apps/rsautl.o apps/s_client.o apps/s_server.o apps/s_time.o apps/sess_id.o apps/smime.o apps/speed.o apps/spkac.o apps/srp.o apps/storeutl.o apps/ts.o apps/verify.o apps/version.o apps/x509.o \
         apps/libapps.a -lssl -lcrypto -lz -ldl -pthread
/usr/lib/gcc/x86_64-alpine-linux-musl/8.2.0/../../../../x86_64-alpine-linux-musl/bin/ld: ./libcrypto.so: undefined reference to `getcontext'
/usr/lib/gcc/x86_64-alpine-linux-musl/8.2.0/../../../../x86_64-alpine-linux-musl/bin/ld: ./libcrypto.so: undefined reference to `setcontext'
/usr/lib/gcc/x86_64-alpine-linux-musl/8.2.0/../../../../x86_64-alpine-linux-musl/bin/ld: ./libcrypto.so: undefined reference to `makecontext'
collect2: error: ld returned 1 exit status

The getcontext, setcontext and makecontext were marked obsolescent in POSIX.1-2001 and removed from POSIX.1-2008, which means that OpenSSL is not portable to any modern libc.

The temporary workaround is to add no-async configure option when using musl-libc.

#7420.

#7420 is merged. Closing. For the record, yes, I reproduced the problem and confirmed the fix.

We are compiling openssl with ASYNC and no-async operation will not work with us.
Can someone help me here ASAP?

I find it slightly strange that you must have ASYNC support if you are upgrading from 1.0.2 - because ASYNC support did not exist in 1.0.2. If you really must have it, then it looks like you're out of luck...you don't seem to have getcontext/setcontext/makecontext support in your libc - which is an absolute requirement for that functionality to work. You either have to swap to some other libc, or disable async.


[FEATURE] Align API of standalone usage of Step.process() with Pipeline.run() parameters arguments

Is your feature request related to a problem? Please describe.
Within the docs, we do advertise that people can use Steps as Standalone components, which prove useful for quick demos, prompt engineering etc, but the API usage doesn't align with passable parameters like within Pipeline.run(). This would help with iteration and building demos.
Describe the solution you'd like
I would expect the Step. process() to potentially take a parameters argument or define a separate method for standalone usage, like Step.run() which does (assuming Step. process() is used within the Pipeline.run() and changes might be difficult.
Describe alternatives you've considered
Looking into the source code and define/overwrite parameters through attribute assignment before calling Step. process().
Additional context
N.A.

Hi, it's true that in the docs maybe we show that Steps and Tasks can be used as standalone components, but they are designed to work within a Pipeline. It's not bad, but we have make clear that using an Step as standalone component should be only for quick testing or understanding how the step works.
Step runtime parameters have two ways of being set: via attributes or via set_runtime_parameters method. I think the problem is specifically with Tasks, in which the parameters of the LLM.generate method are programatically set in the library as runtime parameters of the task (this is because each LLM have different generation parameters) but they are not attributes of the Tasks, therefore the only option to set those parameters is using set_runtime_parameters method.
We can improve the docs around the Tasks to make clear that to set the generation parameters, set_runtime_parameters method has to be used:
task = MyTask(llm=MyLLM(...))
task.load()
task.set_runtime_parameters({"llm": {"temperature": 0.7}})

or allow passing parameters in the process method of the Tasks, but I'm not so convinced with this option because as I mentioned before, the Steps and Tasks are meant to be used within a Pipeline not as standalone components.

@gabrielmbmb, I think it would be clearer to unify the API usage and still emphasise they are intended to be used for testing instead of using something different like set_runtime_parameters.
I assumed that people who want to do something advanced and know what they are doing will use the Pipeline class but people who want to do something simple to create a basic demo or test can be facilitated a bit easier by unifying the API IMO.
Not sure if there are technical reasons behind it or a more philosophical one but for me the first flow is easier, assuming people are going to abuse Steps during testing anyhow.
task = MyTask(llm=MyLLM(...))
task.load()
task.process(
    parameters={"llm": {"temperature": 0.7}})
)

vs
task = MyTask(llm=MyLLM(...))
task.load()
task.set_runtime_parameters({"llm": {"temperature": 0.7}})
task.process()

I just realised that someone can do:
task = MyTask(llm=MyLLM(generation_kwargs={"temperature": 0.7, "max_new_tokens": 2048}))
task.load()

I think that should be enough if someone wants to use the task as a standalone component. We can update the examples to include generation_kwargs.


Create Tree/Bush scense; update map; update autotiles

Added Tree and Bush Scenes (moving them around is awkward and ysort doesn't work)
Updated the pathway autotiles.
Made an atlas of the grass tiles so that they're randomly placed.
Updated the starting map with some ideas.

using inherited scenes for maps now
bush and tree ysort works now.


feat: Removed tabs revamp feature flag

Description
This PR will remove tabs revamp feature flag and make it available for every users.
Fixes #32955
Automation
/ok-to-test<EMAIL_ADDRESS>@tag.IDE"
:mag: Cypress test results

[!TIP]
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8830422427
Commit: 3c1b14d493f62e7d92ad16e80e9e8f6b33217be7
Cypress dashboard url: Click here!

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

Summary by CodeRabbit

Refactor

Removed the feature flag for the IDE tabs revamp, simplifying the rendering logic and component behavior across various IDE components.
Streamlined the handling of tabs in the IDE, eliminating conditional feature flag checks and associated conditional rendering.
Adjusted test suites to align with the removal of the feature flag, ensuring consistency in component behavior testing.

/build-deploy-preview skip-test=true

/build-deploy-preview skip-test=true

/build-deploy-preview skip-test=true


Autoproperties full support

I really like the implementation !!
I will be merging this but later I will change the way it works to avoid use of both autoproperties and fields and also to allow properties in the general way, but your implementation make the use of autoproperties a simple task
Thanks a ton !!
Marcos


✨  Install kustomize also in Mac OS.

Tests automatically install and use own copy of 'kustomize' binary. Current installation script  does this for linux only, even that all tests run properly on Mac OS too.
This change adds 'kustomize' binary installation also on Mac OS.
Tested: make test

/ok-to-test

/approve
/test golint
/test-integration

/test unit


[fix]:Build script not rerun when target rustflags change

What does this PR try to resolve?
Fixes https://github.com/rust-lang/cargo/issues/13003

@weihanglo @epage I haven't found a better way to limit environment variables to what the build script requires. This seems to require first confirming which environment variables the build script cares about, but I haven't figured out how to confirm this.I will keep looking and if you have any suggestions it would save a lot of time, thank you.
The test cases are from anyhow, I hope it will be helpful for understanding.

Note that we'd also need tests for this. Ideally a test is by itself in the first commit, showing the problem (by passing). The second commit fixes the problem and updates the test. The change in the test helps show that we are testing the right thing and what the intended change was.

If we understand it correctly，
first commit, showing the problem (by passing) is https://github.com/rust-lang/cargo/pull/13560/commits/dc88e341f734c0fc2883b2a599811a7f0499853a
second commit fixes the problem and updates the test is https://github.com/rust-lang/cargo/pull/13560/commits/b3c42f6839466e4790e544ec7586adb6e6db8ee0

If you want to limit the environment variables to those required by the build script, then you need to determine which environment variables are required by the build script.
I haven't come up with a better solution other than progressive scanning (and I don't think this is the right kind of solution), and it's harder than I thought it would be if I wanted to do it.
Also, more information about whether unnecessary reconstruction occurred might have been better.
Honorable @weihanglo @epage

The current revision will collect in target extra flags to pass to rustc.
Thanks for the discussion in issue, it has been very beneficial for me. Is there still a revision I need to make?

@bors r+

:pushpin: Commit db7afeba4e415626d78eb3f2e6005fa303f82f59 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit db7afeba4e415626d78eb3f2e6005fa303f82f59 with merge bd1cf584af2c356eeb3980c3c9bb0fea190ed633...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing bd1cf584af2c356eeb3980c3c9bb0fea190ed633 to master...


Abstract away DB in AtxBuilder

Motivation
Step 1 of the Activation Service PoC #6354
Description
Abstract away accesses to the state DB in the ATX builder by using a AtxService interface, which provides access to:

the last ATX of the identity,
a fresh positioning ATX,
any ATX requested by ATXID.

Blobs of the built ATXs are preserved in a new table in the local DB for re-gossipping them later at the re-gossip intervals.
Test Plan

TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

bors try

bors cancel

bors merge

bors try

bors try


Allow exporting the raw rules

I've been considering using this library for my application as it saves me the effort of writing yet another robots.txt parser, but the only way of interfacing with the rule-set is through the allowed function. My app has its own custom URL matcher, so I would like to be able to export all the raw rules as exposed by robots (that match my user agent), and import them in my pattern matching logic.
I'm thinking of just exposing a rules() function that returns the contents of the private rules field, possibly as an iterator of tuple (Allow|Disallow, raw rule glob string). Would you be open to a PR?

Thanks for the pull request - even including a test! =] I think this is a good idea but want to double check assumptions.
As you note, the raw robots.txt rule is likely what's most desired by library users.
The pull request is looking good but currently the as_str function can produce a different rule to the raw one as it might output the regex reduction (i.e. /x***y/ is reduced to /x*y/ as seen in test_robot_many_star_rule_simplifier).
By making pattern public in MinRegex (i.e. add pub here) we can expose the raw rule and Robots::rules could iterate over the pattern of each rule.
I presume exposing the raw rule, as seen in robots.txt, would be the most common use case.
Exposing the regex rule can be left until requested / later as it's also a tad more complicated given the fast regex path in MinRegex.
If you'd like to make the suggested change above, potentially adding the /x***y/ case to your test to ensure we get back the original rule, that'd be great! Otherwise I'll get around to it when next I'm able.
Thanks for the contribution so far as this is definitely a useful addition.

Sure, I'll try and update my PR with your suggestion

But to be honest, I wouldn't mind, and perhaps prefer, to have the simplified pattern returned than the original one, if the robots.txt patterns are nonsense.
I wonder if I should document that the rules function does actually return simplified patterns, and not the original ones verbatim? I'm not sure which approach is preferable.

I may forge ahead with providing a way of accessing the raw rules as extracted from the robots.txt file whilst we think about the idea of returning a regex compatible rule.
The reason the regex compatible rule is complicated is, revisiting the code, there are actually three paths for rules:

"startswith" matching (i.e. not a regex, just string matching)
A star fast path which I've implemented to handle "/a/*/b" (and the pathological "/a/*****/b")
A full regular expression when "$" is used

For your use case how would you want to use the boiled down rule? I could provide a way to convert the raw rules to reduced regular expressions in the rule itself. This is not yet done currently as those regular expressions are only constructed if they're necessary (i.e. they miss the other shortcut paths).

I honestly don't want to make this too complicated just for my use case, unless it's something you would like to add and expand yourself. My pattern matching code uses a slightly different syntax than robots, so the glob/regex hybrid the rules() function would spit out is good enough as I would have to convert it anyway. If your code already does some simplification (such as collapsing adjacent globs into one), that's even better.
So in summary, for my use case, just having access to that rules function, which might not return what's present in robots.txt verbatim, is perfectly fine.


Updating removed values in values.yaml

The removed values caused a render error because the values were referenced in templates/service.yaml. Please see issue #30 for more information on this.

closing.  While this addressed the underlying issue, the intent was to remove the [admin] section entirely as this was deprecated.  This should be fixed via #33


Bump torch-mlir to b3942ff

https://github.com/llvm/torch-mlir/commit/b3942ff984cdb44e3f5e17194632d0bfc6a613cc

What do you think of this as a fix for now?
https://github.com/llvm/torch-mlir/pull/3685 @ScottTodd

What do you think of this as a fix for now? llvm/torch-mlir#3685 @ScottTodd

LGTM! We still need to get some of the existing Python tests actually running in IREE that would catch issues like this: https://github.com/iree-org/iree/issues/16624 . Fine to proceed with that sort of fix for now, but I'd like to have the test coverage proving things still work.

Okay, I've updated to the commit which removes the problematic import. Will look for newly passing onnx tests and update as necessary.

@ScottTodd Lmk if this looks good to you!


Added category and company

Added "Education technology" category and "DreamShaper" company

Thanks @andrepintado! :star:


..

I think the API is already very descriptive .. We wouldn't want to add such a breaking change without a compelling reason.

Hey,
As you like but I found Instagram different than Twitter kindly check Twitter code snippet:
        case userHandle(String)
        case userId(String)

That why I changed it.

I see .. perhaps it makes sense to only remove it for username(username:) because it is redundant there. The rest are fine, since even in Twitter case, we have some labels based on the need.


”Căianu Mic”, ”Căianu Mare” are listed in the drop-down menu

Description:
When user writes ”Căianu Mic”, ”Căianu Mare” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Căianu Mic"

Expected results
The location appears in the drop-down menu as "Căianu Mic, Bistrița-Năsăud (Căianu Mic)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Căianu Mare"

Expected results
The location appears in the drop-down menu as "Căianu Mare, Bistrița-Năsăud (Căianu Mic)".


Issue Fix #21 (Addressing 24LC04/08/16) incomplete

The addressing bug fix in #21 is incomplete.
It corrects the addressing in function _beginTransmission(). When using the 24LC04/08/16, the same address calculation must also be applied in function _ReadBlock(), Line 349 when calling
uint8_t readBytes = _wire->requestFrom(_deviceAddress, length);
With the current implementation, _ReadBlock() always accesses the first 256bytes of the EEPROM.

Hi thjean,
Can you make a PR ? if not I can do it later this week / weekend.

Hi Rob,
Thank you for coming back to the issue report. Unfortunately, I'm a total noob regarding a PR in Git, so it's probably easier for you to take over :).
Here is my local fix, probably not the most elegant one.

First, I added a var in I2C_eeprom::I2C_eeprom(const uint8_t deviceAddress, const uint32_t deviceSize, TwoWire *wire)

_devAddressBlk = deviceAddress;

In void I2C_eeprom::_beginTransmission(const uint16_t memoryAddress), I changed the two lines

uint8_t addr = _deviceAddress | ((memoryAddress >> 8) & 0x07);
  _wire->beginTransmission(addr);

in the else-path of   if (this->_isAddressSizeTwoWords) to
    _devAddressBlk = _deviceAddress | ((memoryAddress >> 8) & 0x07);
    _wire->beginTransmission(_devAddressBlk);

and finally in uint8_t I2C_eeprom::_ReadBlock(const uint16_t memoryAddress, uint8_t* buffer, const uint8_t length), I use the newly introduced var _devAddressBlk instead of _deviceAddress

  uint8_t readBytes = _wire->requestFrom(_devAddressBlk, length);
I tested my local fix with a 24LC16B (Microchip), the addressing scheme seems to be identical to the one used by STM chips. The write operation was already ok as it just uses the combined address for _beginTransmission().
I did not test the fix with a two words address size EEPROM, as I currently do not have one at hands. As _devAddressBlk is intialized with deviceAddress, _ReadBlock() should remain functional.

Created a develop branch in which I added a minimal fix in _readBlock() only.
Can you verify it works for you?
It might not be the final version yet, but lets first tackle the problem, then try to optimize it.

Good catch by the way, appreciated!

Thank you for creating the development branch.
The fix works perfectly for the Microchip 24LC16. It should work with double-byte addressing EEPROMs as well, however I could not verify that due to lack of chips.

The change is made as local as possible so it should not affect the types that use 2 words.

I will merge it later this week, so if you find other issues they might be included too

Btw thanks for creating this library. I highly appreciate the update() functions, as they significantly help preserving device lifetime.

There might be better ways to safe lifetime. Sometimes you just do not need to write every change back to EEPROM.
Imagine that your project could detect a power failure, and has enough energy (backup battery or capacitor) to store the latest values.

Fixed in 1.5.0


Implement google schema markup (only 2 questions added at the moment)

I wrote a script that adds schema markup to the pages generated. Schema markup refers to this

Why is this useful?
Schema markup improves the SEO, it's basically code (semantic vocabulary) that you place on your website to help the search engines return more informative results for users.
I tested it using a ngrok server created from my local repo.

test can be done on https://search.google.com/test/rich-results
Right now it's only written for 2 items. You would probably want to review the text I wrote because it needs to be rephrased.
I will write the code for the next few, or extrapolate the one written for now.
Also please use Github Desktop.

There are some clear improvements that need to be made before this will be merged to production

Seems this should just be rendered as part of the page. I'd look to add the question and answer as optional yaml frontmatter, then create a  tag that pulls in that data and outputs the

closing until I go trough some of the changes suggested by @johnpyp

done the changes and reopened it. Here's another preview showing how it would look on live.
Thank you all for your feedback.

@Steven-Bonnell-II Is this something you want and are willing to maintain? I can't think of anything less I want to do than asking myself questions and writing them out about your philosophy content for every page you create.

@Steven-Bonnell-II Is this something you want and are willing to maintain? I can't think of anything less I want to do than asking myself questions and writing them out about your philosophy content for every page you create.

plz no bully https://youtu.be/iYRcPjKTKm8?list=PLFs19LVskfNzQLZkGG_zf6yfYTp_3v_e6&t=17181
If its too much work I can also try to write an algorithm to generate them:
Something like:
Question: "What does Destiny think about TITLE" where TITLE would be each H2 on each section
Answer: Take the first Phrase from each section that starts with "I ... " and insert it here as an answer.
Example - philosophy My Foundational Beliefs
Question: "What does Destiny think about My Foundational Beliefs"
Answer: "I have a video where I break down how I construct my philosophical worldview, which I highly recommend watching for a fleshed-out understanding of my position."
However this approach would leave little room for customization and the result might not be satisfactory every time ... The safest way would be to handwrite each question.

It's possible you could just have one set of questions/answers for every page on the site.
It might not match up with the exact page that shows up in google results, but you don't have to constantly update it when you make new pages.
(I don't know if google will ding you for having questions/answers that they don't think match the specific page)

It's possible you could just have one set of questions/answers for every page on the site.
It might not match up with the exact page that shows up in google results, but you don't have to constantly update it when you make new pages.
(google might ding you for having questions/answers that they don't think match the specific page)

the way its made right now is that it only injects it in the specific page. Right now it only works with philosophy questions, a new ID need to be injected for each page when the questions are ready for said page


Dump exp_pkt and rcvd pkt if they don't match

To enable dumping, set

dataplane.dump_pkts_on_mismatch = True
in your test.

@antoninbas @pbhide : thanks for the comments, just pushed a change addressing your comments.

I still don't think this is the right way of doing this:

there should be an easy way of disabling this at runtime when starting ptf
for some verify functions (e.g. verify_packet) this seem like a strange thing to have. If I only care about making sure one packet is received and I do not care about extra packets, why should I get a "mismatch packet" log for every one of these extra packets
I believe providing a command line option to enable users to log every packet received would make more sense, would be easier to use and would provide the same amount of information in the log. One can then navigate to the test case location in the logs and look at which packets were received.

in case the test case fails, we just need to look at the logs to figure out why. To add logging function for all packets makes more sense.