binaries built by roc at different times should be identical

Reproducible things are nice to work with :)
Currently, the binaries still contain a timestamp and perhaps other flaky metadata.

readelf --all reveals the following diff in preprocessedhost:

A very similar diff is seen in the final binaries.

passing the --optimize flag reduces this diff.
roc-built binaries are actually identical if they are built in the same folder, changing the folder changes debug info.
Asking zig to strip debug info currently breaks the surgical linker.


Document the argument outputPath

Hello and thanks for this awesome package,
I just upgrade my app from webpack 1 to 2 and I loosed some time to fix image render threw webpack-dev-server
What is the current behavior?
I though that the outputPath was a relative path to the folder where this plugin will save my files, from where the webpack.config file is. And that's not the case. The file will be moved to output.path (webpack config key) + your outputPath.
What is my expectation?
As an end user, I don't want to guess what is the behaviour of yours arguments. Can you explain on your README what is the purpose of each arguments ?

@serut Mind to spin up a quick PR about this 😛 ?

If I was sure to be to able to explain it, would be glad to create the PR, but that's not the case ...

@serut kk I will address it then when I have time, but it's no problem in case the first attempt isn't 💯 though 😛


Allow only 1 comment per account

Ticket: Closes #1075
Test: inf
New behavior:

If you have commented on a claim before, the channel-selector will be clamped to that channel.

There might be more than 1 channel if commented in the past.

This includes blocked comments, i.e. if the creator blocked you, you will not see your comment, yet your channel-selector is clamped to the used channel.
EXCEPTION: you can use other channels if it's your own claim (for now).

Approach

Run comment.List over all your channels on the specific content. This covers nested replies and pagination (sweet).

So, if the total is non-zero, mark that channel(s) as having commented on the claim.
Only fetch this once per content claim.

In the comment channel-selector, clamp the list to this value.

eba8000 to d674792

Fixed the F5 scenario causing the selector to unclamp (have to wait for channel_list first)


Switched to @tryghost/{debug,logging}, dropped logging DI

no issue

@tryghost/ignition is dead and we're moving to individual packages
@tryghost/logging means we no longer need DI for logging from consumer apps

🙋🏻♀ Don't forget to add @tryghost/logging as a dep. Just saying cos I saw it

Ignore me - different packages 😅


Add YASA Solr plugin into solr.cool website

Hi, I'm wondering whether it's suitable to put the YASA Solr plugin in the website solr.cool, YASA is "Yet Another Solr Admin" that serves in multiple modes to replace the original Solr Admin, you can find more details here: https://github.com/yasa-org/yasa

@epugh already submitted PR #23 and it's live as of now :-)

Thanks


Component :- Masthead :- On mobile search icon should not be visible on clicking hamburger icon.

Issue Description :- On mobile devices when user clicks on 'Hamburger menu' icon in that case search icon or profile icon should not be visible where as in stage env clicking on hamburger icon search icon is visible.
Steps to reproduce the issue

Enter url in mobile browser.
Click on 'Hamburger menu' icon.
Check if search icon is visible or not.

OS:- iOS 12, 13  Android 8,9
Browsers:- Chrome, Safari , UC browser.
URL :- https://ibmdotcom-react-staging.mybluemix.net/?path=/story/components-masthead--with-platform

@RobertaJHahn @Praveen-sr @chetankan
PR https://github.com/carbon-design-system/ibm-dotcom-library/pull/2797

@RobertaJHahn : Retested on stage env it is working fine now.


Add TP standalone dockerfiles

What does this PR (Pull Request) do?
Adds a standalone Dockerfile for Traffic Portal.
I'm not sure what the status of the standalone Dockerfiles is, but I wrote this for myself, and it was useful to me when the CiaB was having issues. So I figured I'd make a PR, in case it's useful to anyone else.
No tests, standalone Dockerfile.
Standalone Dockerfiles aren't in the read-the-docs documentation, but they have a README.md. I added documentation to the readme.
Includes CHANGELOG entry.

[x] This PR is not related to any Issue

Which Traffic Control components are affected by this PR?
Standalone Dockerfiles
What is the best way to verify this PR?
docker build --no-cache --rm --tag traffic_portal:3.0.x --build-arg=RPM=traffic_portal.rpm .
docker run --name tp --hostname tp --net cdnet --publish 40443:443 --env TO_SERVER=my-traffic-ops-fqdn --env TO_PORT=443 --env DOMAIN=cdnet --detach -- traffic_portal:3.0.x

If this is a bug fix, what versions of Traffic Ops are affected?
Not a bug fix.
The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3526/
Test PASSed.


Conversations list in Swift Example.

Pull request checklist

[X] All tests pass. Demo project builds and runs.
[X] I have resolved any merge conflicts.
[X] I have followed the coding style, and reviewed the contributing guidelines. Confirmation: 💪😎👊

This fixes issue #___.
What's in this pull request?

Added Conversations list with example group Conversation and Regular conversation.

@GianniCarlo Here is the conversations list back.

[Current coverage][cc-pull] is 61.14%

Merging [#1655][cc-pull] into [develop][cc-base-branch] will not change coverage

@@            develop      #1655   diff @@
==========================================
  Files            62         62
  Lines          2262       2262
  Methods         634        634
  Messages          0          0
  Branches        136        136
==========================================
  Hits           1383       1383
  Misses          808        808
  Partials         71         71

[][cc-pull]

Powered by Codecov. Last updated by [da9d834...ee64fb5][cc-compare]
[cc-base-branch]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/compare/da9d834d5095105ab24a5e39d5e263fee3b50332...ee64fb58eb770b95e9adc715f504ed939ce3a38f
[cc-pull]: https://codecov.io/gh/jessesquires/JSQMessagesViewController/pull/1655?src=pr

Nice!, @MacMeDan did you get a chance to check out my [pull request] (https://github.com/jessesquires/JSQMessagesViewController/pull/1639) about locations?

@GianniCarlo I have not yet I am waiting for a few pull requests to get merged and then I will take a look.

No worries 👍
On Wednesday, 8 June 2016, Dan Leonard<EMAIL_ADDRESS>wrote:

@GianniCarlo https://github.com/GianniCarlo I have not yet I am waiting
for a few pull requests to get merged and then I will take a look.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jessesquires/JSQMessagesViewController/pull/1655#issuecomment-224693559,
or mute the thread
https://github.com/notifications/unsubscribe/ANdYM9IbdAvIHKlwvkA0eAyUKIKA1Z2wks5qJxE_gaJpZM4IwSVM
.

--
You can contact me privately!
Message me now
https://messenger.criptext.com/private/imrur3bn9h4yw7aegrd7k3xr
Gianni Carlo

Hey @jessesquires I updated this guy with all the changes from develop. Is there anything else that we need for this guy.

Yae and all the checks passed.

👍


Support GraphQL

What does this pull request do?
Support GraphQL
And I'm not sure what span_type it should be.
Related issues
closes #ISSUE

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

Expand to view the summary

Build stats

Build Cause: [Pull request #850 opened]

Reason: The PR is not allowed to run in the CI yet

Start Time: 2020-06-03T11:14:43.762+0000

Duration: 4 min 50 sec

Commit: dc02abae5edd2d41728d41662e48a8b3729c80ab

Steps errors
Expand to view the steps failures

Name: Error signal

Description: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permission

Duration: 0 min 0 sec

Start Time: 2020-06-03T11:18:30.090+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-06-03T11:18:06.011Z]  > git checkout -f dc02abae5edd2d41728d41662e48a8b3729c80ab # timeout=15
[2020-06-03T11:18:06.077Z]  > git remote # timeout=10
[2020-06-03T11:18:06.090Z]  > git config --get remote.origin.url # timeout=10
[2020-06-03T11:18:06.094Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T11:18:06.098Z]  > git merge c1303bce53b28f30bff6430776085a6ea435d208 # timeout=10
[2020-06-03T11:18:06.152Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-06-03T11:18:06.164Z]  > git config core.sparsecheckout # timeout=10
[2020-06-03T11:18:06.167Z]  > git checkout -f c87dbe63ff0e15148aba342f291005b83256d808 # timeout=15
[2020-06-03T11:18:09.754Z] Commit message: "Merge commit 'c1303bce53b28f30bff6430776085a6ea435d208' into HEAD"
[2020-06-03T11:18:09.754Z] First time build. Skipping changelog.
[2020-06-03T11:18:09.754Z] Cleaning workspace
[2020-06-03T11:18:09.821Z]  > git --version # timeout=10
[2020-06-03T11:18:09.845Z] fatal: bad object daa756c96f4c7a41f6585e1fee8a821a6ad8a31a
[2020-06-03T11:18:09.753Z]  > git rev-parse --verify HEAD # timeout=10
[2020-06-03T11:18:09.757Z] Resetting working tree
[2020-06-03T11:18:09.757Z]  > git reset --hard # timeout=10
[2020-06-03T11:18:09.784Z]  > git clean -fdx # timeout=10
[2020-06-03T11:18:10.659Z] Masking supported pattern matches of $JOB_GCS_BUCKET or $NOTIFY_TO
[2020-06-03T11:18:10.744Z] Timeout set to expire in 1 hr 0 min
[2020-06-03T11:18:10.775Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.
[2020-06-03T11:18:11.183Z] [INFO] Number of builds to be searched 10
[2020-06-03T11:18:11.367Z] [INFO] 'shallow' is forced to be disabled when running on PullRequests
[2020-06-03T11:18:11.423Z] Running in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-850/src/github.com/elastic/apm-agent-python
[2020-06-03T11:18:11.468Z] [INFO] gitCheckout: Checkout SCM PR-850 with default customisation from the Item.
[2020-06-03T11:18:11.504Z] [INFO] Override default checkout
[2020-06-03T11:18:11.573Z] Sleeping for 10 sec
[2020-06-03T11:18:21.735Z] using credential f6c7695a-671e-4f4f-a331-acdce44ff9ba
[2020-06-03T11:18:21.760Z] Wiping out workspace first.
[2020-06-03T11:18:21.768Z] Cloning the remote Git repository
[2020-06-03T11:18:21.768Z] Using shallow clone with depth 3
[2020-06-03T11:18:21.768Z] Avoid fetching tags
[2020-06-03T11:18:21.777Z] Cloning repository git@github.com:elastic/apm-agent-python.git
[2020-06-03T11:18:21.800Z]  > git init /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-850/src/github.com/elastic/apm-agent-python # timeout=10
[2020-06-03T11:18:21.818Z] Fetching upstream changes from git@github.com:elastic/apm-agent-python.git
[2020-06-03T11:18:21.818Z]  > git --version # timeout=10
[2020-06-03T11:18:21.828Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T11:18:21.832Z]  > git fetch --no-tags --progress -- git@github.com:elastic/apm-agent-python.git +refs/heads/*:refs/remotes/origin/* # timeout=15
[2020-06-03T11:18:22.987Z] Cleaning workspace
[2020-06-03T11:18:22.999Z] Using shallow fetch with depth 3
[2020-06-03T11:18:22.999Z] Pruning obsolete local branches
[2020-06-03T11:18:23.654Z] Merging remotes/origin/master commit c1303bce53b28f30bff6430776085a6ea435d208 into PR head commit dc02abae5edd2d41728d41662e48a8b3729c80ab
[2020-06-03T11:18:22.969Z]  > git config remote.origin.url git@github.com:elastic/apm-agent-python.git # timeout=10
[2020-06-03T11:18:22.973Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-06-03T11:18:22.979Z]  > git config remote.origin.url git@github.com:elastic/apm-agent-python.git # timeout=10
[2020-06-03T11:18:22.985Z]  > git rev-parse --verify HEAD # timeout=10
[2020-06-03T11:18:22.988Z] No valid HEAD. Skipping the resetting
[2020-06-03T11:18:22.989Z]  > git clean -fdx # timeout=10
[2020-06-03T11:18:22.998Z] Fetching upstream changes from git@github.com:elastic/apm-agent-python.git
[2020-06-03T11:18:22.998Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T11:18:23.005Z]  > git fetch --no-tags --progress --prune -- git@github.com:elastic/apm-agent-python.git +refs/pull/850/head:refs/remotes/origin/PR-850 +refs/heads/master:refs/remotes/origin/master # timeout=15
[2020-06-03T11:18:23.653Z]  > git config core.sparsecheckout # timeout=10
[2020-06-03T11:18:23.784Z] Merge succeeded, producing 217418fc1973c2c00548d5030c677a3a82bc9c47
[2020-06-03T11:18:23.785Z] Checking out Revision 217418fc1973c2c00548d5030c677a3a82bc9c47 (PR-850)
[2020-06-03T11:18:23.826Z] Commit message: "Merge commit 'c1303bce53b28f30bff6430776085a6ea435d208' into HEAD"
[2020-06-03T11:18:23.826Z] First time build. Skipping changelog.
[2020-06-03T11:18:23.826Z] Cleaning workspace
[2020-06-03T11:18:23.896Z]  > git --version # timeout=10
[2020-06-03T11:18:23.910Z] fatal: bad object daa756c96f4c7a41f6585e1fee8a821a6ad8a31a
[2020-06-03T11:18:23.656Z]  > git checkout -f dc02abae5edd2d41728d41662e48a8b3729c80ab # timeout=15
[2020-06-03T11:18:23.701Z]  > git remote # timeout=10
[2020-06-03T11:18:23.710Z]  > git config --get remote.origin.url # timeout=10
[2020-06-03T11:18:23.721Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T11:18:23.724Z]  > git merge c1303bce53b28f30bff6430776085a6ea435d208 # timeout=10
[2020-06-03T11:18:23.776Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-06-03T11:18:23.783Z]  > git config core.sparsecheckout # timeout=10
[2020-06-03T11:18:23.787Z]  > git checkout -f 217418fc1973c2c00548d5030c677a3a82bc9c47 # timeout=15
[2020-06-03T11:18:23.825Z]  > git rev-parse --verify HEAD # timeout=10
[2020-06-03T11:18:23.837Z] Resetting working tree
[2020-06-03T11:18:23.838Z]  > git reset --hard # timeout=10
[2020-06-03T11:18:23.872Z]  > git clean -fdx # timeout=10
[2020-06-03T11:18:24.871Z] Masking supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD
[2020-06-03T11:18:25.486Z] + git fetch<EMAIL_ADDRESS>+refs/pull/*/head:refs/remotes/origin/pr/*
[2020-06-03T11:18:26.934Z] Archiving artifacts
[2020-06-03T11:18:27.686Z] + git rev-parse HEAD
[2020-06-03T11:18:28.046Z] + git rev-parse HEAD
[2020-06-03T11:18:28.356Z] + git rev-parse origin/pr/850
[2020-06-03T11:18:28.408Z] [INFO] githubEnv: Found Git Build Cause: pr
[2020-06-03T11:18:28.719Z] Masking supported pattern matches of $GITHUB_TOKEN
[2020-06-03T11:18:29.793Z] [INFO] githubPrCheckApproved: Title: Support GraphQL - User: RyanKung - Author Association: FIRST_TIME_CONTRIBUTOR
[2020-06-03T11:18:30.111Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet
[2020-06-03T11:18:30.111Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permissions can do so.)
[2020-06-03T11:18:30.320Z] [INFO] Let's stop build #1. The PR is not allowed to run in the CI yet
[2020-06-03T11:18:30.351Z] Sleeping for 5 sec
[2020-06-03T11:18:31.467Z] Stage "Sanity checks" skipped due to earlier failure(s)
[2020-06-03T11:18:31.652Z] Stage "Test" skipped due to earlier failure(s)
[2020-06-03T11:18:31.739Z] Stage "Building packages" skipped due to earlier failure(s)
[2020-06-03T11:18:31.825Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-06-03T11:18:31.913Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-06-03T11:18:32.002Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-06-03T11:18:32.042Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-06-03T11:18:32.131Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-06-03T11:18:32.229Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-06-03T11:18:33.263Z] Running on worker-854309 in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-850
[2020-06-03T11:18:33.385Z] [INFO] getVaultSecret: Getting secrets
[2020-06-03T11:18:33.475Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-06-03T11:18:35.481Z] + chmod 755 generate-build-data.sh
[2020-06-03T11:18:35.481Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-850/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-850/runs/1 ABORTED 230288
[2020-06-03T11:18:35.481Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-850/runs/1/steps/?limit=10000 -o steps-info.json
[2020-06-03T11:18:37.299Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-850/runs/1/tests/?status=FAILED -o tests-errors.json
[2020-06-03T11:18:38.008Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-850/runs/1/log/ -o pipeline-log.txt

Just signed Contributor Agreement

Hi @RyanKung
this is awesome, thank you very much! We do have some planning work done for GraphQL, but this mostly pertains to the server side. You can find that here: https://github.com/elastic/apm/blob/master/docs/graphql.md. Maybe some of it could be relevant for the client side too.
As for the span type/subtype/action, I'd personally go with external/graphql/query. There is some prior art in the Node.js agent, where they went with db/graphql/execute, though.
To be honest, I'm not super familiar with GraphQL, so I'll have to read up and play around a bit with it before I can give you a proper review. This is probably going to take a few days, sorry about that!

Regarding CLA, it still fails because you used a different email address for signing the CLA than what you use for committing. Could you either sign the CLA again with the email address you used for committing, or amend the commits with the email address you signed the CLA with? Sorry about that!

Hi @RyanKung
this is awesome, thank you very much! We do have some planning work done for GraphQL, but this mostly pertains to the server side. You can find that here: https://github.com/elastic/apm/blob/master/docs/graphql.md. Maybe some of it could be relevant for the client side too.
As for the span type/subtype/action, I'd personally go with external/graphql/query. There is some prior art in the Node.js agent, where they went with db/graphql/execute, though.
To be honest, I'm not super familiar with GraphQL, so I'll have to read up and play around a bit with it before I can give you a proper review. This is probably going to take a few days, sorry about that!

Thanks for response, this PR is also for server side. And I will try to refine this PR according to the document. But do we really needs to show such detail informations like lex, parse, validate? Maybe just execute is good enough?

@beniwohli Thanks & Merged, According to the document, the TX name should be changed when getting a GraphQL request. So I have to modify those framework middlewares. Here is what I'm working on now.  It may cost few days.
Support setup TX name when content-type = application/graphgl

[x] Support Django middleware
[x] Support Flask
[ ] Support aioHttp

Unittest for framework middlewares

[ ] Django
[ ] Flask
[ ] aioHttp

@RyanKung I wonder if instead of having to add support for all frameworks, we could hook into a deeper part of the GraphQL core library. Having played around with the debugger a bit. The document_from_string methods of the different backends seem to be a good candidate. We could e.g. write an instrumentation like this (get_graphql_tx_name would need to be modified to take a document instead of the unparsed document string)
import elasticapm
from elasticapm.instrumentation.packages.base import AbstractInstrumentedModule
from elasticapm.utils.graphql import get_graphql_tx_name

class GraphQLInstrumentation(AbstractInstrumentedModule):
    name = "graphql"

    instrument_list = [
        ("graphql.backend.core", "GraphQLCoreBackend.document_from_string"),
        ("graphql.backend.cache", "GraphQLCachedBackend.document_from_string"),
    ]

    def call(self, module, method, wrapped, instance, args, kwargs):
        graphql_document = wrapped(*args, **kwargs)
        transaction_name = get_graphql_tx_name(graphql_document.document_ast)
        elasticapm.set_transaction_name(transaction_name)
        return graphql_document

Something similar would need to be done for the new graphql-core package, maybe here? https://github.com/graphql-python/graphql-core/blob/master/src/graphql/execution/execute.py#L245

@beniwohli Wow, change TX name in hooks is simpler than modify all framework support. I'll try it, Thanks. Maybe I should create a new PR for clear?

@beniwohli For now this PR is only support graphene2&graphql-core2.
I tried to support graphql-core3, but got some wired behavior when adding more than two methods of graphql.execution.executor.ExecutionContext to instrument_list such as:
class GraphQLExecutorInstrumentation(AbstractInstrumentedModule):
    name = "graphql"

    Instrument_list_2 = [
      ...
    ]

    instrument_list_3 = [
        # For graphql-core 3
        ("graphql.execution.execute", "ExecutionContext.execute_operation"),
        ("graphql.execution.execute", "ExecutionContext.execute_fields"),
    ]

    instrument_list = instrument_list_2 + instrument_list_3

    def call_graphql_2(self, module, method, wrapped, instance, args, kwargs):
       ...

    def call_graphql_3(self, module, method, wrapped, instance, args, kwargs):
        name = "GraphQL"
        info = ""

        if method == "ExecutionContext.execute_operation":
            print(method)
        if method == "ExecutionContext.execute_fields":
            print(method)

        with capture_span(
                "%s.%s" % (name, info),
                span_type="external",
                span_subtype="graphql",
                span_action="query"
        ):
            return wrapped(*args, **kwargs)

    def call(self, module, method, wrapped, instance, args, kwargs):
        if method in dict(self.instrument_list_2).values():
            return self.call_graphql_2(module, method, wrapped, instance, args, kwargs)
        if method in dict(self.instrument_list_3).values():
            return self.call_graphql_3(module, method, wrapped, instance, args, kwargs)

Only one of those method will be executed, and the whole result will be None on unittest:
@pytest.mark.integrationtest
def test_fetch_data(instrument, elasticapm_client):
    query_string = "{succ{yeah},err{__typename}}"

    schema = graphene.Schema(query=Query)

    elasticapm_client.begin_transaction("transaction.test")
    with capture_span("test_graphene", "test"):
        result = schema.execute(query_string)
        assert result.data == {"succ": {"yeah": "hello world"}, "err": {"__typename": "Error"}}

E           AssertionError: assert None == {'err': {'__typename': 'Error'}, 'succ': {'yeah': 'hello world'}}
E             +None
E             -{'succ': {'yeah': 'hello world'}, 'err': {'__typename': 'Error'}}

Hi, @beniwohli
I think graphene3 is in beta stage, so maybe we can only support 2.0 version for now. Graphene3&graph-core3 supporting can be another pull request.

Hi @beniwohli
Thanks for reply.

* only capture top level graphql executions (the `GraphQL QUERY allProducts` in this case)

GraphQL query may contains complex/composed queries. A execution may cross a lot of Objects, so I think only top level is not enough for showing complex details.

* or not capture executions that take very little time. Capturing spans does have some overhead, and if the operation itself is only fractions of a millisecond, we're adding an undue percentage of overhead.

I added a list of basic type, such as int, str or float  (https://github.com/elastic/apm-agent-python/pull/850/files#diff-a0bf214d1c9543ef09f978bf6e29eda7R55).
It may avoid capture executions that take very little time. How do you think about it?

Is there anything I can do to contribute towards this? We are going to move our GraphQL API out of develop and into production in a few weeks, and having native APM support would be invaluable.

Just flakey test failures. Merging.

@jamesthomasdavidson if you have the time, it would be great if you could give the current master branch a try and see if it fulfills your needs :)


Expose lookup function to template engines?

Hello,
As I realised(from js docs and implementation )  you intend to keep lookup function private. I do believe that it could be useful if they get exposed to template engines, so that they can have the same behaviour with multiple view folders rather than reinventing the wheel in each of them.

ahm ok got  it anybody can create a View, the constructor will ran the lookup and then you can  use myview.path to retrieve. Actually it would be ideal to extend from that view, call it's constructor and inherit the path but I guess the template engine I am using doesn't want to  rely on express.


New logo needed!

The present logo is too simplistic and does not convey graphically the essence of ASCII Media Player.
Needed a new logo that is:

Minimal (or not if it is really impressive)
Conveys the essence of ASCII Media Player and text based interfaces in general
In SVG format

Please discuss and show the logo first in the discussion here before raising a PR.

Hello @PK-cod3ch3mist, I have an idea for the ASCII Media Player logo. Basically I think we can design a colourful play button and run it through the python script to get a ASCII style logo. What do you think about it?

Sounds good! Submit a PR regarding this, and let me see if the logo works.

Hi @yashee99. I think we should not run the logo through the ASCII media player script. This is because the logo is generally viewed at small sizes and thus any detail of the ASCII characters would be lost, making their presence meaningless. So in your PR, submit the original design you thought.

Hi @yashee99. I think we should not run the logo through the ASCII media player script. This is because the logo is generally viewed at small sizes and thus any detail of the ASCII characters would be lost, making their presence meaningless. So in your PR, submit the original design you thought.


Is there any special reason that this project is based on rafter instead of riak_ensemble?

hello, thanks for making this project available. I think it is the awesome idea, I really like the API to detect the primary replica for a set of keys. The only question / concern that I have is the use of rafter. My understanding is that any development of rafter is discontinued and it is not a prod ready. Is there any chance to port this to riak_ensemble instead?
Regards, Roman

Hi Roman,
Support for riak_ensemble is also being added. I submitted a patch for ensemble recently that means riak_governor is effectively provider agnostic now. Rafter is the default but riak_ensemble can be configured as a replacement. I should note that some further work is required for the riak_ensemble version and it is being done as I type...
I hope this helps!
Cheers,
Darach.

This would be super awesome, I can't wait to see ensemble support added.many thanks for replying.
Regards, Roman

Hi Roman,
could you elaborate more about rafter not being ready for prod?
Please notice that riak_governor is using only a subset of rafter or riak_ensemble, which is leader election.
As far as I tested different scenarios with rafter it behaved really really well.
Cheers,
Lukasz


fix DebouncedInput (and delay handling) and change handlers

During the review in a prior PR, a bug in DebouncedInput was discovered, namely that if the delay (which is a prop) changes, the component behavior will not change to debounce (or not) since the behavior is set only in the constructor.
Along the way, there were a few other low-hanging fruit to address, so I did those in a limited capacity.

Closed as stale.


Is this repo moving? (broken link)

I notice at https://github.com/Microsoft/monaco-editor there is a link to mono-editor-samples which is broken. But that repo has issues disabled (apologies for raising here). I'd imagine either that link should point here, or you were intending moving this repo over also.

Yes, I'm about to move this repo too. Sorry about that! :)

Cheers, obviously I found it anyway (and samples work great).


[NetSend] attribute does not work for base type IEnumerable<T> but works for List<T>

Other types should be tested as well.

I think it was never meant to be, to send IEnumerable types.


Configurable ratelimit

Has some weird looking code but trust me, it works.
Uses environment variables for config.
Defaults I came up with, dunno how logical but they make some sense:
USE_RATELIMIT=1
REQ_PER_MINUTE__GLOBAL=100
REQ_PER_MINUTE__REDIRECT=25
REQ_PER_MINUTE__CLIENT_ORIGINAUTH=5
REQ_PER_MINUTE__CLIENT_AUTHWITHSERVER=10
REQ_PER_MINUTE__CLIENT_AUTHWITHSELF=25
REQ_PER_MINUTE__CLIENT_MAINMENUPROMOS=20
REQ_PER_MINUTE__CLIENT_SERVERS=100
REQ_PER_MINUTE__SERVER_ADDSERVER=5
REQ_PER_MINUTE__SERVER_HEARTBEAT=60
REQ_PER_MINUTE__SERVER_UPDATEVALUES=20
REQ_PER_MINUTE__SERVER_REMOVESERVER=5
REQ_PER_MINUTE__ACCOUNT_WRITEPERSISTENCE=50

To save on code complexity, if ratelimit is enabled but it is unset for a certain endpoint, it will fallback to the global value and then if global is also unset to 9999 to disable for that route.

:rockeyebrow: merge when?

(this would be pretty useful paired with the multiple instances code)


SSL cipher issue with Chrome and Firefox

I ran into an issue where both Chrome and Firefox is citing SDPY security issue due to how nginx setup the SSL cipher.
I setup the site using the default --letsencrypt argument.
Chrome would give me a blank page with an ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY error. Firefox does something very similar.
I looked up on it online and it seems to has to do with the ssl cipher setting in nginx.
If I pull up nginx using cat nano /etc/nginx/nginx.conf, the ssl cipher argument is listed as follows:
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA2$

A blog from Jeff Geerling pointed out that HTTP/2 is more strict with how SDPY transport layer works.
And the solution seems to be to change the cipher to the following:
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:AES256+EECDH:AES256+EDH';

This seems to work for me and I can access my site via https via Chrome and Firefox now.
Additional Details:

[x] lsb_release -a

No LSB modules are available.
 I did an "ee stack install" and looked at the nginx.conf
The SSL cipher changed since the last time I use EE.
Here's the comparison between the new and old cipher. If you look at it, the old cipher has two extra characters. That must be the issue.
New Cipher
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHADHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!ECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;
Old Cipher (working):
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;

We are cleaning up issue tracker and closing this issue because we won't be able to contribute to this discussion further.
I can only say HTTP2 should be preferred over SPDY
Please use http://community.rtcamp.com/c/easyengine for future support questions.


Add vertical scrolls

Hey there, thanks for the PR but help me understand what problem you are trying to solve?
Also, you're using a deprecated and since then already removed API getDOMNode and have not added any tests for your code.

Hi frontendphil.
The problem was that I needed to be able to control scrolling in the mentions element. The current behavior is to simply continuously increase the height of the mentions DIV, which was a very undesirable behavior.
The main changes were small: a single CSS change to make the MentionInput DIV element relative position instead of absolute; and made the MentionInput DIV element's top position equal that of the textarea's scrollTop.
The reason for the, now, out-dated getDomNode was because the actual code change was from last year, I just never made a PR. And, since this was a UI-ish change, I didn't add a test. I've had problems in the past with doing UI tests for React.

Alright, could you please first base your changes on the latest version of our code base? Looking at your code, I can see that this is not the case.
Furthermore you are accessing a ref (input) inside a render method, which is discouraged. Please put this code inside a lifecycle hook.

Closing this for inactivity.
(Also, it should already be possible to add vertical scrolling in user land by wrapping the mentions input in a div with fixed height and overflow: auto. Syncing scroll positions does not seem to be the best solution.)

@jfschwarz I'm not sure this fixes the problem as the mentions list popover will be hidden inside the scroll. If we want vertical scroll but allow the metions list to bleed out of the scroll, we will need a different solution.


[New Model] Ess supplier request1.0.0

Description

-->
Closes #57

MS2 Criteria
(to be filled out by PR reviewer)

[ ] the model validates with the BAMM SDS SDK in the version specified in the Readme.md of this repository by the time of the MS2 check  (e.g., 'java -jar bamm-cli.jar -i <path-to-aspect-model> -v ). The  BAMM CLI is available here and in GitHub
[ ] use Camel-Case (e.g., "MyModelElement" or "TimeDifferenceGmtId", when in doubt follow https://google.github.io/styleguide/javaguide.html#s5.3-camel-case)
[ ] the identifiers for all model elements start with a capital letter except for properties
[ ] the identifier for properties starts with a small letter
[ ] all model elements at least contain the fields "name" and "description" in English language.
[ ] no duplicate names or preferredNames within an Aspect (e.g. a Property and the referenced Characteristic should not have the same name)
[ ] the versioning in the URN follows semantic versioning, where minor version bumps are backwards compatible and major version bumps are not backwards compatible.
[ ] use abbreviations only when necessary and if these are sufficiently common
[ ] avoid redundant prefixes in property names (consider adding properties to an enclosing Entity or even adapt the namespace of the model elements, e.g., instead of having two properties DismantlerId and DismantlerName use an Entity Dismantler with the properties name and id or use a URN like io.catenax.dismantler:0.0.1)
[ ] fields preferredName and description are not the same
[ ] preferredName should be human readable and follow normal orthography (e.g., no camel case but normal word separation)
[ ] name of aspect is singular except if it only has one property which is a Collection, List or Set. In theses cases, the aspect name is plural.
[ ] units are referenced from the BAMM unit catalog whenever possible
[ ] use constraints to make known constraints from the use case explicit in the aspect model
[ ] when relying on external standards, they are referenced through a "see" element
[ ] all properties with an simple type have an example value
[ ] metadata.json exists with status "release"
[ ] file RELEASE_NOTES.md exists and contains entries for proposed model changes

MS3 Criteria
(to be filled out by semantic modeling team before merge to main-branch)

[ ] All required reviewers have approved this PR (see reviewers section)
[ ] The new aspect (version) will be implemented by at least one data provider
[ ] The new aspect (version) will be consumed by at least one data consumer
[ ] There exists valid test data
[ ] In case of a new (incompatible) major version to an existing version, a migration strategy has been developed
[ ] The model has at least version '1.0.0'

@bs-jokri : Please review
@BenediktMuellerIML , @jacewski-bosch : fyi

Modeling_Team

Note: The model requires the shared aspect io.catenax.notification_header/1.0.0/NotificationHeader.ttl in order to validate. This shared aspect is provided in another PR, which needs to be merged before.
https://github.com/eclipse-tractusx/sldt-semantic-models/pull/128/files


Add homebrew installation to documentation

$ brew tap simonw/datasette
$ brew install simonw/datasette/datasette
$ datasette --version
datasette, version 0.46

Originally posted by @simonw in https://github.com/simonw/datasette/issues/335#issuecomment-672088880

Also need to talk about how you install plugins.

.. and confirm if brew tap ... is even needed if you run brew install simonw/datasette/datasette

Here's a pattern for installing plugins:
$ datasette plugins
[]
$ /usr/local/opt/datasette/libexec/bin/pip install datasette-vega
Collecting datasette-vega
  Using cached datasette_vega-0.6.2-py3-none-any.whl (1.8 MB)
Requirement already satisfied: datasette in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette-vega) (0.46)
Requirement already satisfied: click~=7.1.1 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (7.1.2)
Requirement already satisfied: click-default-group~=1.2.2 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (1.2.2)
Requirement already satisfied: Jinja2<2.12.0,>=2.10.3 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (2.11.2)
Requirement already satisfied: hupper~=1.9 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (1.10.2)
Requirement already satisfied: pint~=0.9 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (0.14)
Requirement already satisfied: pluggy~=0.13.0 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (0.13.1)
Requirement already satisfied: uvicorn~=0.11 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (0.11.8)
Requirement already satisfied: aiofiles<0.6,>=0.4 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (0.5.0)
Requirement already satisfied: janus<0.6,>=0.4 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (0.5.0)
Requirement already satisfied: asgi-csrf>=0.6 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (0.6.1)
Requirement already satisfied: PyYAML~=5.3 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (5.3.1)
Requirement already satisfied: mergedeep<1.4.0,>=1.1.1 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (1.3.0)
Requirement already satisfied: itsdangerous~=1.1 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (1.1.0)
Requirement already satisfied: python-baseconv==1.2.2 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from datasette->datasette-vega) (1.2.2)
Requirement already satisfied: MarkupSafe>=0.23 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from Jinja2<2.12.0,>=2.10.3->datasette->datasette-vega) (1.1.1)
Requirement already satisfied: setuptools in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from pint~=0.9->datasette->datasette-vega) (49.3.1)
Requirement already satisfied: packaging in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from pint~=0.9->datasette->datasette-vega) (20.4)
Requirement already satisfied: h11<0.10,>=0.8 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from uvicorn~=0.11->datasette->datasette-vega) (0.9.0)
Requirement already satisfied: websockets==8.* in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from uvicorn~=0.11->datasette->datasette-vega) (8.1)
Requirement already satisfied: httptools==0.1.* in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from uvicorn~=0.11->datasette->datasette-vega) (0.1.1)
Requirement already satisfied: uvloop>=0.14.0 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from uvicorn~=0.11->datasette->datasette-vega) (0.14.0)
Requirement already satisfied: pyparsing>=2.0.2 in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from packaging->pint~=0.9->datasette->datasette-vega) (2.4.7)
Requirement already satisfied: six in /usr/local/Cellar/datasette/0.46/libexec/lib/python3.8/site-packages (from packaging->pint~=0.9->datasette->datasette-vega) (1.15.0)
Installing collected packages: datasette-vega
Successfully installed datasette-vega-0.6.2
$ datasette plugins
[
    {
        "name": "datasette-vega",
        "static": true,
        "templates": false,
        "version": "0.6.2",
        "hooks": [
            "extra_css_urls",
            "extra_js_urls"
        ]
    }
]

I added the datasette install name-of-plugin command in #925 mainly to simplify the process of installing plugins if Datasette itself was installed using homebrew.

https://github.com/simonw/datasette/blob/5126ecb1267ed3850bf3b0ab270accd031a02e79/docs/installation.rst#using-homebrew


Array Parameter Not Accepted

module test #(
  parameter int BobaCount = 2,
  parameter int unsigned NumBobaDrinkers[BobaCount] = '{default: '1}
)();
endmodule

Slang appears to parse this correctly
{
            "name": "NumBobaDrinkers",
            "kind": "Parameter",
            "addr":<PHONE_NUMBER>520,
            "type": "int unsigned$[0:1]",
            "initializer": {
              "kind": "StructuredAssignmentPattern",
              "type": "int unsigned$[0:1]",
              "defaultSetter": {
                "kind": "UnbasedUnsizedIntegerLiteral",
                "type": "bit[0:0]",
                "value": "1'b1",
                "constant": "1'b1"
              },
              "constant": "[32'd4294967295,32'd4294967295]"
            },
            "value": "[32'd4294967295,32'd4294967295]",
            "isLocal": false,
            "isPort": true,
            "isBody": false
          }

UHDM
  |vpiParamAssign:
  \_param_assign: , line:3:26, endln:3:69
    |vpiParent:
    \_module_inst: work@test (work@test), file:/build/work/c1bbcd50d3a1889f0b030bf78b08a73369eb/google3/platforms/hls/xls/modules/gfc/sge_addr_unroller/syn/test.sv, line:1:1, endln:5:10
    |vpiRhs:
    \_array_expr:
      |vpiParent:
      \_param_assign: , line:3:26, endln:3:69
      |vpiTypespec:
      \_array_typespec: , line:3:13, endln:3:52
      |vpiExpr:
      \_constant:
        |vpiDecompile:1
        |UINT:1
        |vpiConstType:9
      |vpiExpr:
      \_constant:
    |vpiLhs:
    \_parameter: (work@test.NumBobaDrinkers), line:3:26, endln:3:41

@kamilrakoczy

Seems to be issue in Surelog. Reported: https://github.com/chipsalliance/Surelog/issues/3803

https://github.com/chipsalliance/Surelog/issues/3803 is fixed.
Please propagate the fix

@mglb , please confirm you can proceed here.

Hi @alaindargelas , we're looking into this

As can be seen in https://github.com/chipsalliance/Surelog/issues/3803
the UHDM printer by default doesn't show all the details, and the array_typespec looks empty while it acutally references a proper typespec.
I've used surelog -sv -d uhdm -d vpi_ids -parse test.sv.
I can see that the typespec refers to id:12:
  |vpiParamAssign:
  \_param_assign: , id:102, line:3:26, endln:3:69
    |vpiParent:
    \_module_inst: work@test (work@test), id:106, file:/home/user/YOSYS/systemverilog-plugin/test.sv, line:1:1, endln:5:10
    |vpiRhs:
    \_array_expr: , id:98
      |vpiParent:
      \_param_assign: , id:102, line:3:26, endln:3:69
      |vpiTypespec:
      \_array_typespec: , id:12, line:3:13, endln:3:52
      |vpiExpr:
      \_constant: , id:92, line:3:66, endln:3:68
        |vpiDecompile:4294967295
        |vpiSize:32
        |UINT:4294967295
        |vpiConstType:9
      |vpiExpr:
      \_constant: , id:92, line:3:66, endln:3:68
    |vpiLhs:
    \_parameter: (work@test.NumBobaDrinkers), id:109, line:3:26, endln:3:41

I've searched for id:12 and found this:
    |vpiTypespec:
    \_array_typespec: , id:12, line:3:13, endln:3:52
      |vpiParent:
      \_parameter: (work@test.NumBobaDrinkers), id:6, line:3:26, endln:3:41
      |vpiRange:
      \_range: , id:7, line:3:42, endln:3:51
        |vpiParent:
        \_parameter: (work@test.NumBobaDrinkers), id:6, line:3:26, endln:3:41
        |vpiLeftRange:
        \_constant: , id:8
          |vpiParent:
          \_range: , id:7, line:3:42, endln:3:51
          |vpiDecompile:0
          |vpiSize:64
          |UINT:0
          |vpiConstType:9
        |vpiRightRange:
        \_operation: , id:10, line:3:42, endln:3:51
          |vpiParent:
          \_range: , id:7, line:3:42, endln:3:51
          |vpiOpType:11
          |vpiOperand:
          \_ref_obj: (work@test.NumBobaDrinkers.BobaCount), id:9, line:3:42, endln:3:51
            |vpiParent:
            \_operation: , id:10, line:3:42, endln:3:51
            |vpiName:BobaCount
<EMAIL_ADDRESS>          |vpiOperand:
          \_constant: , id:11
            |vpiSize:64
            |INT:1
            |vpiConstType:7
      |vpiElemTypespec:
      \_int_typespec: , id:5, line:3:13, endln:3:25

To me it looks as if the problem is now solved in Surelog, and we're going to update the Surelog submodule in yosys-systemverilog to integrate the changes.


Matrices are ignored if group or matrix ID contain uppercase characters

The string normalizations
https://github.com/mmikaitis/anymatrix/blob/70886ee31a36053846aafafa186c367cbaae1351/anymatrix.m#L181
https://github.com/mmikaitis/anymatrix/blob/70886ee31a36053846aafafa186c367cbaae1351/anymatrix.m#L185
eems to cause issues with
anymatrix('scan')

as groups and matrices containing capitals are ignored.

These lines only remove capitalization in the arguments and commands to anymatrix, so it should not impact the scanning of the filesystem with anymatrix('scan'). I tried to change core/hesfull01 to core/Hesfull01 and it seems to work (scan finds the new matrix with a capital 'H'). Could you give an example of them problem you are facing with scan? The issue could be somewhere in the scanning functions, starting at line 294. Many thanks.

Yes, the scan would probably work, but then I think you'd then get an error if you tried to generate the matrix with
anymatrix('core/Hessful01')

Something similar should happen if you changed core to Core.

Yes, that seems to be a problem. Looking at a user manual, only properties are case-insensitive, while matrix and group names are case sensitive. Fix merged. Many thanks.

Great, thanks!


Make chaos probes independent of nature of experiment

Today the chaos probes (httpProbe, CmdProbe, K8sProbe) are defined at the chaosengine level, but implemented/supported only within native litmus experiment.  However, as a chaos orchestrator which is experiment-implementation agnostic, these probes should be usable whichever chaoslib the users prefer to use.

This issue tracks the implementation of the probes at the runner level / as a process that runs in before/after/in-parallel with the actual experiment execution.

cc: @sumitnagal

This is now supported via the workflow paradigm within LitmusChaos. One could define a steady-state checker running as a separate action within a larger workflow that also runs native and non-native litmus chaos experiments.


Fix implicit retain warnings

          1 Warning

:warning:
Any source code changes should have an entry in CHANGELOG.md or have #trivial in their title.

  Generated by :no_entry_sign: Danger


selfhost: Array can't be initialised with size from instance function

To reproduce:
class C {
    public e: [f64]

    public function f(mut this) throws {
        .e = [0f64; .n()]
    }

    function n(this) => 1
}

Error message:
 7 |     public function f(mut this) throws {
 8 |         .e = [0f64; .n()]
                          ^- Type 'unknown' is not convertible to an integer. Only integer values can be array fill size expressions.
 9 |     }

This works with the Rust-based compiler.

I was having a look at this, the Rust compiler I think has the same type situation but just worked because it doesn't type check it.
This code I ended with I think is a similar case:
struct C {
    public function f(this) => .n()
    public function n(this) => 2
}

function main() {
    mut e: i64 = 0

    let c = C()
    e = c.n() // works
    e = c.f() // unknown type
}

Where I guess the type inference isn't propagated.

This issue no longer reproduces :)


Under what conditions will a parachain or thread be irrecoverable?

Content request
Cataloging conditions here. Please add ideas or ask questions!
Are you willing to help with this request?
Yes!

<@dan.shields:matrix.parity.io> Let's say all collators go dead and all db is lost. What then?
What if all block history is lost, but a pruned to 1 node was available, should be recoverable. But only if that one block is not corrupted to build a POV from to bring on top of. Right?

Your parachain network should have multiple nodes

<@dan.shields:matrix.parity.io> Under what conditions will a parachain or thread be irrecoverable?

If you loose all state

<@bkchr:matrix.parity.io> There is no difference

The difference is the implied nature of needing fewer nodes than a normal blockchain all the way down yo just a handful of aura nodes , because "security is not their job" perhaps the docs should emphasize that consensus security is not, but everything else is, especially state.
You need a robust node network for this, not just one node your team operates.

<@bkchr:matrix.parity.io> If one entity is controlling all collators, it could also happen that they mess something up and delete everything :P

Well but AFAIK the aura extension naively configured is what implies a ventral and minimal collator set.
Perhaps that is the systemic issue that tripped me up?


Vagrant shuts down the VM even with KEEP_RUNNING=true: is this expected?

The README says that KEEP_RUNNING=true results in Vagrant staying up, but is that what was meant?   The real consumer of time is starting up the VM every time, so I was hoping that that what was meant.
Is it possible to keep the VM running between tests?

Hi,
yes, the KEEP_RUNNING variable is used to keep VM running between the tests. Last time I ran the tests this was working.
One thing that wasn't emphasized in the readme: KEEP_RUNNING=true should go at the beginning of the line that runs the tests. So, the following code is a one liner: KEEP_RUNNING=true ./run_tests.
KEEP_RUNNING=true on a line by itself wont work.

Yes, putting the variable before the command is pretty standard, but does it keep the VM running between executions of the run_tests script, or just between tests if you run have multiple tests that the script kicks off?
If I run KEEP_RUNNING=true ./run_tests and I have only one test for it to run, should the VM stay up so that the next time I run KEEP_RUNNING=true ./run_tests it doesn't need to start up again?  Or should it only stay running between multiple tests that are all run the the same KEEP_RUNNING=true ./run_tests command?

Yes, it should keep the VM running between the executions of the run_tests script.
I think this should clarify how things work. If KEEP_RUNNING=true is present, vagrant VM will NOT be halted after the run_tests script.

ok, I'll try to test again when I get home, but I'm quite sure the VM was going down after run_tests.  Are you seeing it stay up?


Ruby: unit test imports should import mixin services as well

Codecov Report

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

@@           Coverage Diff            @@
##             master   #1202   +/-   ##
========================================
  Coverage      86.1%   86.1%
- Complexity     3708    3709    +1
========================================
  Files           372     372
  Lines         14693   14693
  Branches       1637    1638    +1
========================================
  Hits          12652   12652
  Misses         1603    1603
  Partials        438     438

Impacted Files
Coverage Δ
Complexity Δ

...transformer/ruby/RubyImportSectionTransformer.java
96.29% <100%> (ø)
15 <0> (+1)
: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 23b6d57...d6a30e2. Read the comment docs.


Why is this test flaky?

https://travis-ci.org/twosigma/Cook/jobs/81488613
It's those circuit breaker tests!

Looks like meta transaction tests?
--
Cheers,
Leif
On Tue, Sep 22, 2015 at 12:44 AM, David Greenberg
<EMAIL_ADDRESS>wrote:

Assigned #38 to @leifwalsh.
Reply to this email directly or view it on GitHub:
https://github.com/twosigma/Cook/issues/38#event-415314459

The failure is up above.  MT is just chatty.

Gah. Will look tomorrow.
--
Cheers,
Leif
On Tue, Sep 22, 2015 at 12:47 AM, David Greenberg
<EMAIL_ADDRESS>wrote:

The failure is up above.  MT is just chatty.
Reply to this email directly or view it on GitHub:
https://github.com/twosigma/Cook/issues/38#issuecomment-142130390

These are also flaky: https://travis-ci.org/twosigma/Cook/jobs/81510292

Yep.  There's a tradeoff between flakiness and speed.  We can make the
timeouts and sleeps bigger to reduce flakiness.
On Mon, Sep 21, 2015 at 10:10 PM, David Greenberg<EMAIL_ADDRESS>wrote:

These are also flaky: https://travis-ci.org/twosigma/Cook/jobs/81510292
—
Reply to this email directly or view it on GitHub
https://github.com/twosigma/Cook/issues/38#issuecomment-142159766.

--
Cheers,
Leif

Here's a few thoughts:

increase timeouts by 50-100%?
allow a callback to be attached to the main timeout, and have the other
bits wait on that callback?
switch them to "integration" tagged tests to not run by default (but run
in CI)?

On Tue, Sep 22, 2015 at 4:54 AM Leif Walsh<EMAIL_ADDRESS>wrote:

Yep. There's a tradeoff between flakiness and speed. We can make the
timeouts and sleeps bigger to reduce flakiness.
On Mon, Sep 21, 2015 at 10:10 PM, David Greenberg <
<EMAIL_ADDRESS>wrote:

These are also flaky: https://travis-ci.org/twosigma/Cook/jobs/81510292
—
Reply to this email directly or view it on GitHub
https://github.com/twosigma/Cook/issues/38#issuecomment-142159766.

--
Cheers,
Leif
—
Reply to this email directly or view it on GitHub
https://github.com/twosigma/Cook/issues/38#issuecomment-142217978.

It seems the CI environment is slow, the parameters right now work pretty well (for my workstation) for interactive purposes.  I think increasing timeouts is the right approach but if you have a better idea for something callback-based, I'd support that.  The system itself has a time component though, so I think you actually need timeouts to happen, you just have to pick them larger so that jitter doesn't cause flakiness.

Could you make the timeouts attempt to look up an environment variable like CIRCUIT_BREAKER_TEST_TIMEOUT_MULTIPLIER, and then we can just make that 5 or 10 in Travis?

sure
On Tue, Sep 22, 2015 at 11:23 AM, David Greenberg<EMAIL_ADDRESS>wrote:

Could you make the timeouts attempt to look up an environment variable
like CIRCUIT_BREAKER_TEST_TIMEOUT_MULTIPLIER, and then we can just make
that 5 or 10 in Travis?
—
Reply to this email directly or view it on GitHub
https://github.com/twosigma/Cook/issues/38#issuecomment-142322700.

--
Cheers,
Leif

Ok, hopefully that's all of them, and all the math still works out, and that factor is high enough.

Not good enough yet it seems.

Maybe only certain durations should get increased, like wait times to stable states?
Is it possible to script the interaction, so that there's an order to the steps, and a timeout? You could make a map from step-name to promises, and then have a state machine deliver those promises to have thread-safe, rudimentary orchestration by means of blocking calls to deref. Or maybe that wouldn't help much; I haven't read the tests too closely.

There is already sequencing, though done differently than you described.
If this doesn't fix it I think we should disable these tests until I get back and have a chance to merge the other fixes that didn't make it into the open-source snapshot.  The tests try to test general-ish behavior without being too specific to the underlying implementation, but in order to be fast they have to be kind of specifically tuned.  This is annoying because the state is kind of hard to make general statements about; this may be a design decision we should revisit.

@dgrnbrg I have a green build (for circuit breaker stuff) in https://travis-ci.org/twosigma/Cook/builds/81792099, now trying to improve travis logs a bit.  A metatransaction test are now failing, probably need to use ex-data instead of assuming it's got .getCause() but that's just a guess.

@dgrnbrg tests now look good, you may want to peek at the build I linked above though.  Travis logs are nicer too (maven ones aren't perfect, but aren't worse).  Please merge if you like it or complain if you don't.

awesome!


API suggestion for GetDeclarations, GetToolTipTextAlternate, etc.

Currently the API requires that a list of identifier names be sent to the compiler services in order to get a list of declarations, tooltips, methods, etc. Example:
Code being worked on
let x = ...
x.y.z.

Intellisense code
// Get declarations (autocomplete) for a location
let decls =
    checkFileResults.GetDeclarationsAlternate
      (Some parseFileResults, 2, 6, inputLines.[1], ["x"; "y"; "z"], "")
    |> Async.RunSynchronously

It would be nice if the API would just figure out the names ["x"; "y"; "z"]

Closing old feature request - we don't need to track these as we will gradually improve the API


Added .node file support for Node based platforms to enable Node-API use

Changes Made
This pull requests adds an esbuild plugin and some tweaks to the Remix compiler to allow the import of .node files in Remix's loaders and actions. While motivated by me by the desire to write Rust helper functions for server side modules, this was also mentioned in this other pull request for .node imports in remix-tailwind.
I have started a discussion here, but as of now hasn't generated much traffic.
Benefits
The primary benefit I see is the ability to run other language's code on your server easily in Remix. This could be done in Rust using napi-rs, in Python, or in C.
Limitations
One of the biggest limitations is that it can only run on Node based platforms. Napi-rs is currently working on Deno support, so we may see this come there as well.  I am happy to write Docs about it, and it will be a part of my Remix Conf talk!
The esbuild plugin is a bit messy, being written in JS instead of TS, and I am not sure of the best way to test this automatically. Feedback and any style tweaks are welcome.
Testing
I have modified the Rust example in the main repo with to generate a sum() function with napi-rs and use that to perform the addition that example does. The repo for this is here. There are a few build steps as described in that README that must be performed, depending on the platform you're running Remix on.

I've run into this issue, thanks for adding support! I started a disucsion about this awhile but no body ever commented. Hopefully you get more traction!
https://github.com/remix-run/remix/discussions/2560

I've run into this issue, thanks for adding support! I started a disucsion about this awhile but no body ever commented. Hopefully you get more traction!
#2560

I hadn't seen your discussion before, I suspect the reason it didn't get much traction is that it's a somewhat niche feature. Perhaps after Remix Conf we'll get a bit more interest, but I'm fairly confident I can get this merged after I write some docs and do some celeanup

@benwis Code changes should go against dev.
Can you please rebase your branch onto dev & set the base branch to dev as well?

Closing this so that I can pull from my fork's dev branch against the remix dev branch. New PR here:


Fix AppModule

Fixes proposal from https://github.com/bukhalo/nestjs-telegraf/pull/806

LGTM, thx!


Set a User-Agent HTTP header

This is in no way an official an endorsement of this project by Boxine, but personally I think it's awesome!
This night, one user sent about 1-2 requests every second which modify a Tonie over and over with the same content without waiting for it to be done transcoding.
For privacy reasons, Boxine does not associate the HTTP user-agent with detailed logging data (we just group it into android app, iOS app, other for these logs), but based on the extremely high frequency I am certain the user-agent Apache-HttpClient/4.5.5 (Java/1.8.0_275) is responsible.
This project should set an HTTP-user agent like spotify-toniebox-sync (v1.2.3) so that Boxine can report the bugs to the project causing it. After all, somewhere there is likely a user wondering why their Tonie never finishes transcoding.

Totally valid point. Will add it to: https://github.com/maximilianvoss/toniebox-api/issues/7 as it is part of the API handler which is used.


field "ontsnapt" pushed to gbif?

here is an issue encountered whilst planning field work on species for RadIUS with @fleurpet many locations are in a captive/cultivated setting (gardens, captivity etc.) which is super useful to know (and preferably we would also like to have this filtering option in the early alert system).
So, is this checkbox with ontsnapt mapped to GBIF? If not, can we make that happen? To note we absolutely want these records as they are informative on size of captive population, pathways, introduction efforts etc. How is this dealt with? Sorry if this was already taken into account @peterdesmet . As you know we are also trying to convince iNaturalist to publish the captive/cultivate records in a separate dataset.

With the ontsnapt checkbox, do you mean information that the observer indicated at observation level? That info is not mapped to Darwin Core as it was deemed confusing with the status at species level (which is used as a filter to include/exclude records in the exoten datasets).

Yeah, that info is not included in the Darwin Core mapping, but the observation is (in contrast with iNat).

Ok, i chewed on it and I think in general that is ok because

the checkbox is not consistently checked by observers
we dont want to miss any potentially relevant records
from a management point of view tackling what is in cultivated setting (so at the source of future invasions) makes a lot of sense
the checkbox is not consistently applied/asked by validators (cf. what does 'ontsnapt' actually mean, 'captive/cultivated' is much more clear, you could brand all garden escapes that are encountered in the wild as 'ontsnapt' or take a more conservative approach and only consider those where there is still a clear link with the cultivated setting for instance a dumped garden compost heap or a nearby urban planting)
for the early alert system, users can always go to the original record and see for themselves whether the observation was branded as an escape


Accessing OpenAI API fails

I configured openAI API and it works fine in bash but not using the app:
GptFile returns:
Traceback (most recent call last):
  File "/usr/local/bin/openai", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/openai_cli/cli.py", line 24, in complete
    result = client.generate_response(prompt, model)
  File "/usr/local/lib/python3.10/site-packages/openai_cli/client.py", line 36, in generate_response
    response.raise_for_status()
  File "/usr/local/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.openai.com/v1/completions```

GptRun returns:

```Run with: Make a doctring for DESeq2
Make: *** No rule to make target `a'.  Stop.
Traceback (most recent call last):
  File "/usr/local/bin/openai", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/openai_cli/cli.py", line 24, in complete
    result = client.generate_response(prompt, model)
  File "/usr/local/lib/python3.10/site-packages/openai_cli/client.py", line 36, in generate_response
    response.raise_for_status()
  File "/usr/local/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.openai.com/v1/completions```

Does this happen with all files? Also what prompt did you give?
Your token is in ~/.config/openai.token?

@Melclic
Does this happen with all files? Also what prompt did you give?
Your token is in ~/.config/openai.token?

Hi @0xStabby,

Does this happen with all files?

It does happen with all files (python, simple text files, etc...)

Also what prompt did you give?

Not sure what you mean by that? The commands I used that cause the problem are :GptRun and : GptFile

Your token is in ~/.config/openai.token?

It is indeed. I can use the bash command to call the openAPI so I know its working

Hmm okay, so from my testing I get this error when the file is there but the token is not correctly set.
What openai-cli command works? Could you show an example.
My ~/.config/openai.token(obfuscated):

The command that runs for gpf (:GptFile) is
let output = system("(echo '" . prompt . "'; cat " . currentFile . ";) | openai complete - -t $(cat ~/.config/openai.token)")

Basically echo "the file" | openai complete - -t $(cat ~/.config/openai.token)
So echo the file piped to openai complete then using the output of the openai.token file for the api token.
See if this command works, double the output of cat ~/.config/openai.token.
Just wondering if maybe you have set an environment variable to use openai with and that's why those commands are working but the openai.token is maybe set incorrectly.

Okay, I just added in support to use the env var if it exists, if not then will fall back to the openai.token.
Perhaps this update will just solve it for you without any extra fiddling
https://github.com/0xStabby/chatgpt-vim/commit/4e289a35255d614eeef5bea50f41a76c8a41e972

Yup that did it! Thanks a lot

Awesome! Great to hear!


When iscurved is true, the bottom data arc is out of bounds

Is there any way or method to control it ？？？

Try to add clipData: FlClipData.all(), to your LineChartData widget.

Try to add clipData: FlClipData.all(), to your LineChartData widget.

Try to use preventCurveOverShooting, and preventCurveOvershootingThreshold in your LineChartBarData

Try to use preventCurveOverShooting, and preventCurveOvershootingThreshold in your LineChartBarData


Support Json deserialization with Jackson

Android target environments do not support Jaxb deserialization of Xml. Support deserialization from Json.

Included in 1.4.0 release


Request for help in regards to implementation of the project

Hi,my name is Atharva I am working on a project that is very similar to this one but am facing difficulties in the understanding of the project.Is it possible for you to share any material or references that would help us in implementing our project.Please let me know.
Thanking You.

The associated paper and presentation to this github repo are online: http://richzhang.github.io/colorization/


Post comments

User shall be able to post comment on story details page.

done and merged to dev.


Discord-starboards breaking changes

Hey, I just pushed a new update on the discord-starboards develop branch. It fixes many bugs and introduces new features like the NSFW channel filter, custom emojis, ...
Unfortunately it may break your code.
Consider updating your code and let me know if you encounter any bugs. If all goes well, let me know and I'll merge the develop branch to the main branch.
Have a nice evening,
Simon.
PS: The delete and deleteStarboard methods have changed

Will check it out soon, Thanks for letting me know! For now I'll leave this issue open so I don't forget lol.

Will check it out soon, Thanks for letting me know! For now I'll leave this issue open so I don't forget lol.

I will close this issue now, I'll open an issue on your repo if I encounter any bugs :)

I will close this issue now, I'll open an issue on your repo if I encounter any bugs :)


스토리북 storysource 적용

🤔 해결하려는 문제가 무엇인가요?
close #85
스토리북을 통해 컴포넌트 사용 방법을 확인하기 편하도록 하고 싶었어요
🌄 스크린샷

code 탭에서 해당 스토리 컴포넌트의 코드를 확인할 수 있어요
📚 참고
https://github.com/storybookjs/storybook/tree/master/addons/storysource

Codecov Report
Patch and project coverage have no change.

Comparison is base (7567dfa) 97.89% compared to head (e58fe43) 97.89%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #97   +/-   ##
=======================================
  Coverage   97.89%   97.89%
=======================================
  Files          28       28
  Lines         190      190
  Branches       32       32
=======================================
  Hits          186      186
  Misses          4        4

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


Roll Flutter Engine from 94023d711db3 to 6c367e7533c5 (3 revisions)

https://github.com/flutter/engine/compare/94023d711db3...6c367e7533c5
2024-06-25<EMAIL_ADDRESS>Roll Dart SDK from 65ab2f2cf0d3 to 38bb74f63829 (1 revision) (flutter/engine#53570)
2024-06-25<EMAIL_ADDRESS>Roll Skia from 04133a5bf21f to ea8ec1a618b0 (3 revisions) (flutter/engine#53569)
2024-06-25<EMAIL_ADDRESS>Roll Skia from da1ea4eb0270 to 04133a5bf21f (2 revisions) (flutter/engine#53566)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Inverse Sync

Sync appears to work in the the direction of the child only.
I've added to the bottom of the subchart class:
 # inverse sync         self.run_script(f'''             {self.id}.chart.timeScale().subscribeVisibleLogicalRangeChange((timeRange) => {{                 {sync_parent_id}.chart.timeScale().setVisibleLogicalRange(timeRange)             }});             syncCrosshairs({sync_parent_id}.chart, {self.id}.chart)         ''')
I'd like to able to sync series with different time frames (like 1min and 5sec), but that seems out of scope for the underlying.

Hey @krazatchu,
I wanted this behavior when I was first implementing sync, however after testing with each chart synced to one another, scrolling behavior became quite buggy as each chart moves the other in a loop. This could potentially be solved by only subscribing to the chart which is currently being hovered over.
As for timeframe sync, the current implementation only moves the charts by their logical range (bar index) and doesn't pay attention to the timeframes of the charts. I think this could be implemented by keeping track of the time in the centre of the logical range, and then setting the logical range of the chart with a different timeframe to be centered around that time. But you would need to keep track of the number of bars in the visible range, so that zooming in/out works as normal.
Feel free to contribute,
Louis

Sync will now work both ways in the latest version; I'm going to hold off on the timeframe sync for now as it doesn't appear highly requested.
Louis


[DIR-654] broadcasts e2e test

I think your updates are all good

@sebxian I made a suggestion on how we can dynamically generate a schema. Thanks to TypeScript it was not so straight forward as it should be :) Feel free to update variable names or even revert the commit completely.
@porleaaron I made a tiny change in your test to replace your pickRandomElements function against the faker.helpers.arrayElements. I appreciate your implementation, but I bet you just did not know that faker has these on board (with a lot of other cool helpers btw!). For a cleaner code base, I think it's best to just use the faker ones as we already have the package anyway

@stefan-kracht thanks for the changes, that looks very good :rocket:


gp does not own its data

Hi,
I am using emcee to maximize a likelihood function to which I pass a celerite2.GaussianProcess object. I store the chain in a h5 file. When I start the emcee sampling from scratch there is no issue, but if I restart the sampling loading the h5 file then the gp.compute() instruction throws this error:
  File ".../python3.6/site-packages/celerite2/core.py", line 313, in compute     self._t, self._diag, c=self._c, a=self._a, U=self._U, V=self._V   File ".../python3.6/site-packages/celerite2/terms.py", line 157, in get_celerite_matrices     c.resize(J, refcheck=False) ValueError: cannot resize this array: it does not own its data
How can I fix it? Thanks

I expect this has more to do with how you're setting up the model when you restart - rather than anything to do with loading the chain. How are you saving the GP and log probability function between runs. Are you pickling it? See if you can put together a very simple example that reproduces this issue and we'll see what we can do.

You find the example below. It's basically a copy/paste of the example in https://celerite2.readthedocs.io/en/latest/tutorials/first/, with the difference that the gp.compute() is inside the log_prob function, because in general i need to optimize a jitter term to add to yerr (I haven't implemented it in the example). I have also put the sampler in a pool.
The example raises the same exception as my code at the very first run of the sampling. It doesn't even need to load a previous h5 file. I don't understand why, yet it would be good to know what I'm doing wrong in the example.
`
import numpy as np
import celerite2
from celerite2 import terms
import emcee
from multiprocessing import Pool
np.random.seed(42)
t = np.sort(
np.append(
np.random.uniform(0, 3.8, 57),
np.random.uniform(5.5, 10, 68),
)
)  # The input coordinates must be sorted
yerr = np.random.uniform(0.08, 0.22, len(t))
y = (
0.2 * (t - 5)
+ np.sin(3 * t + 0.1 * (t - 5) ** 2)
+ yerr * np.random.randn(len(t))
)
true_t = np.linspace(0, 10, 500)
true_y = 0.2 * (true_t - 5) + np.sin(3 * true_t + 0.1 * (true_t - 5) ** 2)
Quasi-periodic term
term1 = terms.SHOTerm(sigma=1.0, rho=1.0, tau=10.0)
Non-periodic component
term2 = terms.SHOTerm(sigma=1.0, rho=5.0, Q=0.25)
kernel = term1 + term2
Setup the GP
gp = celerite2.GaussianProcess(kernel, mean=0.0)
gp.compute(t, yerr=yerr)
prior_sigma = 2.0
freq = np.linspace(1.0 / 8, 1.0 / 0.3, 500)
omega = 2 * np.pi * freq
def set_params(params, gp):
gp.mean = params[0]
theta = np.exp(params[1:])
gp.kernel = terms.SHOTerm(
sigma=theta[0], rho=theta[1], tau=theta[2]
) + terms.SHOTerm(sigma=theta[3], rho=theta[4], Q=0.25)
gp.compute(t, diag=yerr**2 + theta[5], quiet=True)
return gp
def neg_log_like(params, gp):
gp = set_params(params, gp)
return -gp.log_likelihood(y)
def log_prob(params, gp,t,yerr):
gp = set_params(params, gp)
gp.compute(t, yerr=yerr)
return (
    gp.log_likelihood(y) - 0.5 * np.sum((params / prior_sigma) ** 2),
    gp.kernel.get_psd(omega),
)

np.random.seed(5693854)
solnx=np.array([ 4.65372782e-03, -3.41545599e-01,  7.00008984e-01,  1.94361891e+00, 6.05832782e-01,  3.75539832e+00, -7.87383431e+00])
coords = solnx + 1e-5 * np.random.randn(32, len(solnx))
backend = emcee.backends.HDFBackend('backend.h5')
with Pool(processes=4) as samplerPool:
sampler = emcee.EnsembleSampler(
    coords.shape[0], coords.shape[1], log_prob, args=(gp,t,yerr),pool=samplerPool, backend=backend
)

state = sampler.run_mcmc(coords, 200, progress=False)

`

I can look more closely later, but what if you use the globally defined gp instead of passing it as an argument. I can see a problem here where, even though each subprocess has its own instantiation of the GP, passing it as an argument is causing it to be pickled and unpickled which could cause problems (and definitely be slower!).

I can confirm that my suggestion seems to fix things. This must be something to do with how the arrays are getting passed around by multiprocessing. We can leave this issue open for that, but it might be nice to set up a simpler example that doesn't depend on emcee directly. The issue is multiprocessing!

can you show me your working example? i'm trying to use the gp as a global
variable with no success (likely because i'm such a bad coder)
On Fri, Sep 23, 2022 at 5:02 PM Dan Foreman-Mackey @.***>
wrote:

I can confirm that my suggestion seems to fix things. This must be
something to do with how the arrays are getting passed around by
multiprocessing. We can leave this issue open for that, but it might be
nice to set up a simpler example that doesn't depend on emcee directly. The
issue is multiprocessing!
—
Reply to this email directly, view it on GitHub
https://github.com/exoplanet-dev/celerite2/issues/70#issuecomment-1256330864,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQ5BY2HB3GKVGUKXTLFOWDV7XA7XANCNFSM6AAAAAAQT3YL7A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sure thing! Here's how I edited your code: https://gist.github.com/dfm/b2b6cdfc61c4de8b5594e636e3c5c70f

I implemented your solution in my code and it fixed the issue. Also, it is ~10% faster! Thanks twice!
As for this issue, you can close it if you prefer, and I give you the copyright to simplify and publish my example blaming it on multiprocessing. Unfortunately I wouldn't know how to simplify it.
Thanks again


bootstrap4 SpeciesListsController

Turn SpeciesListsControllerTests green,
except assertions that fail because of incomplete UI.
Those assertions are isolated at the end of a single test method:
test_presence_of_links_to_modify_species_list

Coverage decreased (-0.009%) to 82.461% when pulling 0cb8c75d66c8628fe0f14e47d78e6fb2ea3e7337 on 173432669-jdc-bootstrap4-species_lists_controller into 712e215e0eb6b29149be2cbac4ce9e736d3b4055 on bootstrap-4.

Thanks! I'll double-check and try again.
On Thu, Jun 25, 2020 at 3:19 PM andrew nimmo<EMAIL_ADDRESS>wrote:

@nimmolo commented on this pull request.
In test/controllers/species_lists_controller_test.rb
https://github.com/MushroomObserver/mushroom-observer/pull/589#discussion_r445869902
:

get species_lists_path

Above causes ActionController::UrlGenerationError:

No route matches {:action=>"/species_lists", :controller=>"species_lists"}

Hi Joe,
from what you've got here, and from my own rake routes, get
species_list_path seems to be working OK... remember the singular one
needs an :id, so it should be get species_list_path(:id) and return
"/species_lists/:id"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/589#discussion_r445869902,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALDFDVWSB67J2DA5SR2RLRYPENXANCNFSM4OIVXT5Q
.

Glad to hear that I'm not the only one going bonkers.
I'll see if I can make some progress using IntegrationControllerTest
inheritance.
On Thu, Jun 25, 2020 at 4:40 PM andrew nimmo<EMAIL_ADDRESS>wrote:

@nimmolo commented on this pull request.
In test/controllers/species_lists_controller_test.rb
https://github.com/MushroomObserver/mushroom-observer/pull/589#discussion_r445895402
:

get species_lists_path

Above causes ActionController::UrlGenerationError:

No route matches {:action=>"/species_lists", :controller=>"species_lists"}

Yes! This is what has been driving me bonkers.
It is what drove me on a 2-day detour to figure out how Rails recommends
running controller tests, and that's how i landed on using a different
class inheritance for IntegrationControllerTest instead of
FunctionalTestCase.
However, I've been totally flummoxed trying to get that to work too. It
does generate paths correctly, but then generates other errors, such as
where it says :index and :show paths need a login. They don't.
Generally speaking, i'd have more faith investing time in the integration
test approach, since this has gotten all the attention from the rails
development team for the last 5 years. But it remains to be discovered, how
to make it work in our app. I've only gotten a few tests working with it.
And all our working tests are with the old way, so that carries more weight.
Still, maybe try inheriting from the new class for
species_lists_controller and see if you can find the way?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/589#discussion_r445895402,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALDFH7P45GYM3T75SHSIDRYPN67ANCNFSM4OIVXT5Q
.

I'm turning this back to draft while I work in Integration testing.

Glad to hear that I'm not the only one going bonkers. I'll see if I can make some progress using IntegrationControllerTest inheritance.
…
On Thu, Jun 25, 2020 at 4:40 PM andrew nimmo @.> wrote: @.* commented on this pull request. ------------------------------ In test/controllers/species_lists_controller_test.rb <#589 (comment)> : > + # get species_lists_path + # Above causes ActionController::UrlGenerationError: + # No route matches {:action=>"/species_lists", :controller=>"species_lists"} Yes! This is what has been driving me bonkers. It is what drove me on a 2-day detour to figure out how Rails recommends running controller tests, and that's how i landed on using a different class inheritance for IntegrationControllerTest instead of FunctionalTestCase. However, I've been totally flummoxed trying to get that to work too. It does generate paths correctly, but then generates other errors, such as where it says :index and :show paths need a login. They don't. Generally speaking, i'd have more faith investing time in the integration test approach, since this has gotten all the attention from the rails development team for the last 5 years. But it remains to be discovered, how to make it work in our app. I've only gotten a few tests working with it. And all our working tests are with the old way, so that carries more weight. Still, maybe try inheriting from the new class for species_lists_controller and see if you can find the way? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#589 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALDFH7P45GYM3T75SHSIDRYPN67ANCNFSM4OIVXT5Q .

I'm turning this back to draft while I work in Integration testing.

Temporarily giving up on changing inheritance, and changing to Ready for Review so that what's been do so far can get merged.

Back to Draft. I reopened this by mistake:
62 tests, 268 assertions, 10 failures, 46 errors, 0 skips

SpeciesListControllerTest is green.
Controller should be refactored.
I plan on doing easier stuff now, creating a Pivotal Story for more serious work later.

Again, great work. (so much work!)

Temporarily made this a Draft PR so that I change how I deal with tests that failed because of incompleteness of the UI.

I will probably merge this PR this evening or later tonight;
I'm now working on the ProjectsControllerTest. There are some references to SpeciesList, and I don't want to do the same thing twice, or trip over my own changes in another branch.


Initial review

My app is complete, please review. /cc @codepathreview

I've corrected the readme/gif

I've added a gesture based color picking dialogue.

Amazing work John! Way to take it to the next level!
This pre-work is a preview of our weekly project process. Generally, weekly projects take about 5 hours to complete the required features and an additional 5 hours to complete the optional features. In general, we've seen that the more hours you log, the quicker you improve your proficiency with iOS.
The purpose of this project was to begin to explore Xcode and to get a broad overview of iOS development using Swift. For example, in this project, we explored the following concepts:
Code styling in Swift. You can find some code styling guides here:
Ray Wenderlich Swift Style Guide
Github Swift Style Guide

Views are created in Storyboard, Interface Builder, or programmatically, but they have the same goal: instantiate, initialize, and layout view objects. We use IBOutlets to give names to view objects, similar to giving unique ids to divs in HTML.
We registered for touch events, which can be done programmatically or via IBActions.
We explored NSUserDefaults, one of the four persistence strategies in iOS.
View controllers have a set of methods that are called when it loads, appears, or disappears. These are called view controller lifecycle methods.

Do your views look good on iPhone 4, 5, and 6? We will cover in class how to use Auto Layout to robustly design your views for different screen sizes and OS versions.
After this assignment, you should understand the purpose of IBOutlets and IBActions as well as the basics of designing views and programmatically interacting with the views from the controller.
Charlie Hieger
CodePath


Update DB to local replica (DevEnv)

Description
DBの参照先をレプリカに変更。
Type of change

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[ ] I have checked backward/forward compatibility that may cause regarding this change.

なるほど！
ありがとうございます🙇♂🙇♂


Friction does not work on heightmaps and mesh terrain [Harmonic]

When using any model on a static heightmap, objects slide without friction regardless of surface tags. Tested on Harmonic with the Moon DEM, Portuguese Ledge, and a custom mesh .dae of a Martian terrain. Robots had proper friction only on primitive geometry (box, cylinder, plane), and sometimes worked on very flat meshes.

I also noticed this problem too.

Is this true with the Bullet physics engine as well?


HamzaMath

some math blocks for calculators

You cant use eval, its dangerous and can run JS code.
alert("see what I mean?")
Also, the calculate blocks are useless as you can use the "abs" block from operators. You could just add the other blocks to the Math extension

Oh yeeeah a message popping on your screen to simply say something is
sooooo dangerous. Sooooo many bad things could happen. It deeefinetely be
such a catastrophe.
On Thu, Oct 3, 2024, 8:18 PM SharkPool @.***> wrote:

You cant use eval, its dangerous and can run JS code.
alert("see what I mean?")
Also, the calculate blocks are useless as you can use the "abs" block from
operators. You could just add the other blocks to the Math extension
—
Reply to this email directly, view it on GitHub
https://github.com/TurboWarp/extensions/pull/1702#issuecomment-2392601141,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANYWUKLD3ED7SEAPDQOBWXTZZXUGHAVCNFSM6AAAAABO6XO4G2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSGYYDCMJUGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@Drago-Cuven now you're real silent :trollface:


fix(backend-proxy-middleware): set credentials from .env file

Fixes https://github.com/SAP/open-ux-tools/issues/558

Thanks @tobiasqueck, thanks @Klaus-Keller


fix: Icon for toolbar button "user" - cms ui

changed the user svg icon to settings svg icon. (ss below)

fix issue#https://github.com/plone/volto/issues/5119

Sorry, it is not literal username but the authenticated user's username.

Sorry, it is not literal username but the authenticated user's username.

Are we talking about this username ?

Sorry, it is not literal username but the authenticated user's username.

@stevepiercy are we talking about this username ?

Yes.

Sorry, it is not literal username but the authenticated user's username.

@stevepiercy are we talking about this username ?

Yes.

@stevepiercy got it now !
ps: i also changed the svg (now it is configuration svg).
Welcome to Plone 6!.webm

Please ensure tests pass locally before pushing commits and requesting a code review. Thank you!

@stevepiercy I am sorry to mention you like this but i tried various approaches to solve this but everytime I would get the same error in checks 'i18n'
please look at my code and tell me what i did wrong. (as I'm new to open source contribution)

You can read more about Volto contributing at Translations and Code quality for the failing CI checks. These must pass. It is best to do these locally before pushing commits.

@MoazMirza-13  the tests fail because of 2 reasons:

you need to run:
yarn prettier:fix
yarn lint:fix
https://github.com/plone/volto/actions/runs/6633850565/job/18022304159#step:5:7
if you look to the left you will see 2 services that fail prettier and eslint
https://github.com/plone/volto/blob/main/package.json#L48
here you will see all the scripts that you can run with yarn
You need to run
yarn test
to run jest tests
https://github.com/plone/volto/actions/runs/6633850548/job/18022304459#step:5:3543
You will see that Jest is configured to save a snapshot which is tested against.
Thus you need to update the test with the latest markup by pressing: u after the test
fails.
Once you commit the test snapshot update and the linting it will finally be green.

@ichim-david I think Volto's documentation on what commands need to be run needs to be reviewed and updated.

Code quality, which has links to the three pages:
Linting
Testing
Acceptance testing

@ichim-david I think Volto's documentation on what commands need to be run needs to be reviewed and updated.
* [Code quality](https://6.docs.plone.org/volto/contributing/index.html#code-quality), which has links to the three pages:

* [Linting](https://6.docs.plone.org/volto/contributing/linting.html)

* [Testing](https://6.docs.plone.org/volto/contributing/testing.html)

* [Acceptance testing](https://6.docs.plone.org/volto/contributing/acceptance-tests.html)

Yup I looked at them after I saw your comments that @MoazMirza-13 should study but I noticed that they didn't document any of the ways to run the commands from the repo which are configured correctly using the proper rules.
This is why I wanted to give actual pointers on how to look and what to run.
There are so many moving parts with documentation now that I don't even know when to work on such a thing,
we will talk about this later.

I created a new issue https://github.com/plone/volto/issues/5341. It can be worked on at any time.

@MoazMirza-13 the tests fail because of 2 reasons:

you need to run:
yarn prettier:fix
yarn lint:fix
https://github.com/plone/volto/actions/runs/6633850565/job/18022304159#step:5:7
if you look to the left you will see 2 services that fail prettier and eslint
https://github.com/plone/volto/blob/main/package.json#L48
here you will see all the scripts that you can run with yarn
You need to run
yarn test
to run jest tests
https://github.com/plone/volto/actions/runs/6633850548/job/18022304459#step:5:3543
You will see that Jest is configured to save a snapshot which is tested against.
Thus you need to update the test with the latest markup by pressing: u after the test
fails.
Once you commit the test snapshot update and the linting it will finally be green.

@ichim-david thanks for this yarn prettier:fix command, it worked

@stevepiercy @sneridagh Has the Volto team discussed this? I understand the arguments for why the current icon/menu is confusing, but I'm not clear on whether there is consensus on how to change it, and if there is, I think it should wait for a major version (we shouldn't just change a major UI element in a patch release).

@davisagli I don't think the Volto Team discussed it. I put it on the agenda for our next meeting.
I discussed it with the Classic UI team and here is the result of that discussion: https://github.com/plone/volto/issues/5119#issuecomment-1727737649.

@stevepiercy @sneridagh Has the Volto team discussed this? I understand the arguments for why the current icon/menu is confusing, but I'm not clear on whether there is consensus on how to change it, and if there is, I think it should wait for a major version (we shouldn't just change a major UI element in a patch release).
@davisagli  I don't think that anyone mentioned that this will be merged as part of a patch release.

I think the fact that this issue was solved in a way is a good thing, then it's up to Victor and / or the volto team to discuss when this fix should be merged.
Ex one of my pull requests regarding some a11y changes Victor though it's a breaking change that will go in 18 only https://github.com/plone/volto/pull/5294 that doesn't mean I shouldn't have worked on it thinking that it would not make It to 17 but simply that I wanted to fix something and then it's up to you guys to decide when it's  fitting to be merged.

@davisagli @stevepiercy @ichim-david Indeed, this has to be discussed and approved by the Volto Team.
/cc @plone/volto-team

Some considerations, if we make this change, it should be done in Classic as well under the same premises.
/cc @plone/classicui-team
FTR, that icon is not the one that Quanta defines, it should be the "cog":
https://www.figma.com/file/YpaRSKjFcFaAkVYnTSVGuz/Volto-UI-–-Quanta?type=design&node-id=1812-1140&mode=design&t=QKPrqnfZ3DRdox43-4

In 90% of the cases the users don't have the Manager / Site Administrator role. Thus, the menu will not contain the Site Setup or any admin settings. In this case, the user icon is more suitable, as it is only about the user profile, preferences and logout.

Also replacing the user <Name> with Settings seems a major drawback to me.

@MoazMirza-13 I am going to close this pull request. Based on the discussions from all of the core developers it seems that it's simply better to keep the current behavior than to change the icon and text due to the permissions of users.
Thank you for your attempt to fix this issue, your code was good enough to merge but upon further review of the problem it's better to keep current behavior.


Error with opencv

Hi,
I have a compilation error related to libopencv_imgcodecs.
By modifying line 74 (CMakeLists.txt) as follows, the compilation is error-free :
FIND_PACKAGE(OpenCV COMPONENTS core highgui imgproc imgcodecs REQUIRED)
But now, by executing the "../../build/bin/AppKeyframes -s sensor.yml -k keyframes.yml" command, I get the following error: Failed to load settings from file 'true'!
What step could I have forgotten?
Regards

I guess you are using OpenCV3? The command line parser has changed there, something like the following should work:
../../build/bin/AppKeyframes -s=sensor.yml -k=keyframes.yml

Yes, I use OpenCV 3.2 (with Debian Buster).
The new command works perfectly. Thank you.
Regards.

To avoid such confusions in the future, I am going to allow OpenCV3 only. Thanks for your quick feedback and the fix above.

Hi I am trying to compile intrinsic 3D using Windows OS and Visual studio 2013 and I compiled the AppKeyframes successfully in debug mode X64 but when I run the program it will create fusion folder but now extracted keyframes and the values of sensor_config and sensor_config_fille show Error reading characters of string as show in the attachment could some one could give some suggestion it would be helpful


Update netty dependencies to use the netty-bom

JAVA-4710

Patch: https://spruce.mongodb.com/version/6304c3b6a4cf470c7d90a30d

Same failure with tcnative.  The BOM is pulling in 2.0.53, so that version doesn't work either.  So we have to roll back somewhere between 48 and 52 unless we can figure out why.