subscription with fragments does not fire properly

Following the resolver example here, if you call a subscription with a fragment as follow:
subscription {
  publications {
    mutation
    node {
      ...Fields
    }
  }
}

fragment Fields on Post {
  id
  title
}

It will returns a response right away with a null data such as the one below and does not listen for changes.
{
  "data": {
    "data": {
      "publications": null
    }
  }
}

Removing the fragment keeps the connection on and listening, and the mutations are triggered properly on changes.
Someone else can confirm?
$ prisma --version
prisma/1.3.3 (linux-x64) node-v8.7.0

Edit: One more thing, this issue does not occur when we use the prisma generated subscriptions with fragments (at the database level).

+1 I have the same issue.

I am also able to replicate this issue.

I also ran into this, same issue: when replacing the fragment with regular fields, all works fine, but after introducing a fragment into the client-side query, it

creates one spurious websocket response containing just 'null'

returns a response right away with a null data

does not fire up after a change should have triggered an event
works, when regularly connecting the database prisma directly.
In the logs I additionally find these lines:  query: Promise {
      <rejected> TypeError: Cannot read property 'variableDefinitions' of undefined
  at Object.<anonymous> (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:64:155)
  at step (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:40:23)
  at Object.next (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:21:53)
  at //node_modules/graphql-tools/dist/stitching/delegateToSchema.js:15:71
  at new Promise (<anonymous>)
  at __awaiter (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:11:12)
  at Object.delegateToSchema (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:49:12)
  at Proxy.<anonymous> (//node_modules/prisma-binding/dist/src/Handler.js:54:36)
  at formatValue (util.js:430:38)
  at formatProperty (util.js:831:11) },
   mutation: Promise {
      <rejected> TypeError: Cannot read property 'variableDefinitions' of undefined
  at Object.<anonymous> (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:64:155)
  at step (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:40:23)
  at Object.next (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:21:53)
  at /node_modules/graphql-tools/dist/stitching/delegateToSchema.js:15:71
  at new Promise (<anonymous>)
  at __awaiter (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:11:12)
  at Object.delegateToSchema (//node_modules/graphql-tools/dist/stitching/delegateToSchema.js:49:12)
  at Proxy.<anonymous> (//node_modules/prisma-binding/dist/src/Handler.js:54:36)
  at formatValue (util.js:430:38)
  at formatProperty (util.js:831:11) },

and many or these: ```
(node:20312) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 24): TypeError: Cannot read property 'variableDefinitions' of undefined
(node:20312) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 26): TypeError: Cannot convert a Symbol value to a string

Hope this helps somehow?

I am able to replicate this with apollo-link-* and graphql-tools. Most likely a bug in graphql-tools, will work on isolating the issue further.

I'm getting the same error in query object. TypeError: Cannot read property 'variableDefinitions' of undefined.
I can only see this error when I console.log the prisma instance. Despite the error, prisma-binding is seems to be working fine.

When using a query with subscribeToMore, this can really add a lot of duplication in the client code. Would be nice to see this get some attention.

@marktani I have this issue as well. @divyenduz provided a reproduction repo

Found the issue. The underlying subscriptions work correctly with fragments on the server, it's just an issue with GraphQL Playground.
It seems when a fragment is placed inside the query, instead of sending it over the WebSocket, it sends it in a POST request

@marktani You closed #1810 stating that this issue provides a reproduction. Do you have everything you need to tacke this? Let me know if you still need a clean repro and I will set it up
The duplicate code issue is really getting out of hand in our codebase. It leads to a lot of the following situations:

devs forgetting to update both fragment and subscription when adding / renaming fields => hours wasted until realizing their mistake
devs forgetting or not knowing that the fragmenting subscription issue exists => hours wasted until they realize the framework is broken here

@divyenduz While trying to setup a repro I think I figured out the root cause for this issue:

In short when subscriptions have fragments but NO name prisma returns null and closes the subscription. I have created a separate issue for this here: https://github.com/prisma/prisma/issues/2942
And when using the prisma-bindings we call the subscription without the initially given name hence we get a null response
This also explains why:

this works in your repo as you are NOT using prisma-bindings to pass through the subscription
copying the subscriptions from app to database playground works just fine

Quick sanity check:
https://eu1.prisma.sh/public-silvermole-100/subscription-fragment/dev
The following breaks:
fragment PostFragment on Post{
  id
}
subscription {post{node{  ...PostFragment  }}}

While this works just fine:
fragment PostFragment on Post{
  id
}
subscription SomeName{post{node{  ...PostFragment  }}}

So I found the cause for the newly seen type error:

While<EMAIL_ADDRESS>do solve the null return issue for subscriptions (with name) and fragments (2.1.3 still returns null for subscriptions with fragments)
but at the same time 2.1.4 introduces the new type error (mentioned above) bug for ALL subscriptions. See issue https://github.com/prisma/prisma-binding/issues/229

Applying the fix mentioned in the issue thread for the type error (in my node modules folder) I can confirm that :

subscription with fragments and NAME now work as expected
still same issues for subscriptions with fragments and NO name #2942

Note:
The type error is actually part of the graphl-bindings not prisma-bindings itself

Closed as duplicate of https://github.com/prisma/prisma/issues/2942 and https://github.com/prisma/graphql-playground/issues/846.


Retire Rachael from community team

r? @steveklabnik

Rachel is too busy for community team work with her job at IronWorks, and so asked us to retire until things change.


Create new BB: News Image Gallery

This is a Building Block for our upcoming News/Magazine Kit. For anyone who wants to contribute some building blocks to the site, feel free to assign this to yourself to let us know you're taking this one on!
Description/Interaction: A simple image gallery / slider that includes a short description. The Building Block doesn't have to follow the example exactly, feel free to position things however you like.
Include at least: Image slider, share/social links, description area.
Use "media" as category in your yml file.
Example from usatoday.com:

Ohk will take a look this weekend... Ready to take this up... Please assign me in!!!

@IamManchanda you got it!

@IamManchanda We're aiming to get the News kit out by the end of today, do you think you'll be able to knock this one out by today? If not, feel free to assign it to me!

@canterberrie .... ohk assigned you this one if this is urgent ....
I will do that another one you do this :D

@IamManchanda thanks!

If this missed the deadline and isn't urgent now I would like to take this up back!!!
Thanks @rafibomb @canterberrie

Dang @IamManchanda do you even sleep bro? ;)
We decided to delay the actual marketing release of the new Kit to monday, and I didn't see a PR for this before end of day, so I think it's yours if you want it.

lol ... i have a habit of sleeping 6 hours a day ..... currently in office ( saturday-half day ) ... will look to do this ... by tonight or tomm. morning! :D


bug

i use mitm for check requests, so sometimes script make request with joined strings.
i try using sript for github.com , and i see this:
<IP_ADDRESS>:37246: GET https://github.com/
200 OK 39.23k
<IP_ADDRESS>:37250: GET https://github.com/
200 OK 39.25k
GET https://github.githubassets.com/assets/compat-bootstrap-edde9aec.jshttps://github.githubassets.com/assets/compat-bootstrap-edde9aec.js
404 Not Found 30b
GET https://github.githubassets.com/assets/github-bootstrap-e9911286.js
200 OK 122.5k
GET https://github.githubassets.com/assets/compat-bootstrap-edde9aec.js
200 OK 9.42k
GET https://github.githubassets.com/assets/frameworks-564f5a6e.jshttps://github.githubassets.com/assets/frameworks-564f5a6e.js
404 Not Found 30b
GET https://github.githubassets.com/assets/frameworks-564f5a6e.js
200 OK 48.33k
GET https://github.githubassets.com/assets/github-bootstrap-e9911286.jshttps://github.githubassets.com/assets/github-bootstrap-e9911286.js
404 Not Found 30b
So few request contains of 2 urls

Hi,
can you provide the command on terminal you used?

python3.6 SubDomainizer.py -u https://github.com/ -k

This should be fixed please check and let me know.


Encourage scope granting in GraphiQL

WHY are these changes introduced?
When a developer changes the access scopes for their app, and wants to continue to prototype and build, they almost certainly will need the merchant of their dev store -- themselves! -- to grant said access. For the app home, a refresh will do the job with declarative scopes. But lots of building now happens in GraphiQL, and this doesn't have the same behaviour.

WHAT is this pull request doing?
Firstly the token used by GraphiQL is refreshed often now, so its scopes should always be up to date with those granted by the dev store.
This PR adds a couple of helpful nudges:

if the access scopes in the in-use app toml don't match those that GraphiQL's access token is attempting to use, this is a sign that the developer has changed them. we show a message in the top-bar of GraphiQL encouraging the dev to run shopify app deploy
after running shopify app deploy, if the developer has changed their access scopes within their newly released app version, we show a next step about granting these new access scopes in their dev store

How to test your changes?

Run shopify app dev, and launch GraphiQL
Leaving dev running, go to your app toml, and add a new scope, save the file
The banner shown above should appear. If you change the scopes back, it will disappear.
With changed scopes, run shopify app deploy. Choose to create and release a new version
The confirmation message should mention going to your dev store, as per the above

Post-release steps

n/a
Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

Is it possible to show a different message in GraphiQL when the granted scopes are out of sync with the deployed scopes?

I'm not sure -- we should be able to get at https://shopify.dev/docs/api/admin-graphql/2023-10/objects/App . If requested/available scopes represent the granted and deployed scopes then maybe it's possible?

Confirmed a comparison to requested might do it. Will look


use mise instead of make

Update Github Workflows, Tests And Dependencies
This pull request includes several significant modifications:

Updated python.yml workflow file to specify working on the
'pocketsizefund' library, use setup-poetry action for setting up python, and
use 'mise-action' for setup and run stages of unit tests, lint, dead code,
and package publishing jobs.
Updated rust.yaml workflow file to use 'mise-action' for setup in linting,
formatting and unit test jobs, and change the run command from 'make rust'
to 'mise run'.
Removed content from Makefile, including setup commands and implementation
details concerning various tasks like linting, unit testing, and dead code
detection, all of which can be handled in mise.
Updated compose.yaml under 'infrastructure/pricemodel' to build the
'pricemodel' service on the 'linux/amd64' platform.
Moved pocketsizefund/config/config.py to pocketsizefund/config.py since this is how it is
being imported in the APIs.
Updated the version of 'pocketsizefund' package from '0.1.1' to '0.1.2',
and added 'pytest' as a dev dependency in its pyproject.toml file. Updated
the 'poetry.lock' file to reflect these changes.
Updated the tests under 'pocketsizefund' package to import the 'config'
directly from 'pocketsizefund' rather than from 'config' module.

#235  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @chrisaddy and the rest of your teammates on  Graphite


fix ee gluster image

Codecov Report
Patch and project coverage have no change.

Comparison is base (bef5de7) 38.64% compared to head (b143c50) 38.64%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #704   +/-   ##
=======================================
  Coverage   38.64%   38.64%
=======================================
  Files          33       33
  Lines        3959     3959
=======================================
  Hits         1530     1530
  Misses       2283     2283
  Partials      146      146

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How many hours does compling codes take?

I started compling codes, 2 hours ago according to README.md.
The compiler stucked in 16%.
Is it abnormal case? or it always take more than 2 hours?

Compilation on CPU is shorter. On GPU, it is around 10 mins.

Then, it went something wrong.
@zaemyung Could you give us the details?

 The experimental flag '--expt-rel
axed-constexpr' can be used to allow this.
(Many more warnings)
[ 16%] Linking CXX static library libmteval.a
[ 16%] Built target mteval

I'm using the latest Eigen (eigen-eigen-8416483b0fbc) and Cuda-9.0.
Both boost and cmake are compiled from source.

Please follow the details at this page for the recommended version of eigen https://dynet.readthedocs.io/en/latest/install.html

Managed to compile the code by using Eigen installed with:
hg clone https://bitbucket.org/eigen/eigen/ -r b2e267d
Thanks for your help!


docs: Update and create index.md

After seeing the Roblox Studio post, I wanted to use FastNet2, so I went into the document, but it seemed to be unfinished, so I looked at GitHub, but index.md did not exist or was not written properly, so I modified or re-created index.md so that I could enter each page.

Thanks for letting know its just failure when building the docs.

Thank you for updating the document.


Remove SVN from Mx10 docs

Copied over from this private PR: https://github.com/mendix/Mendix10-docs/pull/8
Please replicate all comments yourself here, as they cannot be ported over.

@ConnorLand
I see that some of the changes in this PR are to unversioned documents in the AppStore.
I think some of the changes which remove Git entirely might be too much as many customers will not be migrating to Git for some time and SVN is still available in previous versions of Mendix.
Can you have a look at this again - I can discuss it with you if necessary.

@ConnorLand I see that some of the changes in this PR are to unversioned documents in the AppStore. I think some of the changes which remove Git entirely might be too much as many customers will not be migrating to Git for some time and SVN is still available in previous versions of Mendix.
Can you have a look at this again - I can discuss it with you if necessary.

Actually - have looked again and it seems to be OK.


Work queue

Current implementation has a "queue" of 1. This is obviously dumb.
We should use a circular queue / FIFO of... 16?

Fixed via bae1d25ded2b8e1b6fa7439ef41ec6adcd8a9998


[ZEPPELIN-5015] Update shiro to 1.7.0

What is this PR for?
This updates shiro to 1.7.0
What type of PR is it?

Improvement

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5015

How should this be tested?

Travis-CI: https://travis-ci.com/github/Reamer/zeppelin/builds/202702821

Questions:

Does the licenses files need update? Only the used version
Is there breaking changes for older versions? No
Does this needs documentation? No

Relates to #3895

LGTM


NetVips file opening issue

Describe the bug
I want to generate tiles from mosaic, i am passing arguments to console but i got this error
"NetVips is unable to open input image.
An attempt was made to load a program with an incorrect format. (Exception from
HRESULT: 0x8007000B)"
Expected behavior
The expacted behvaiour will be the tiles in output folder
Screenshots

Desktop (please complete the following information):

OS: [Windows 8]

Hello.
What exactly do you mean by mosaic, Is it a set of GeoTIFFs? Currently, the only supported input data extension is .tif (GeoTIFF). Also, please tell me the arguments you were using.

yes i am passing a .tif image. and passing just input location and temp directory path and output directory path

Could you please provide that GeoTIFF?

i can not upload  .tif files here because Github does not support .tif files

Consider compressing GeoTIFF into .zip archive and uploading it into Github, or using file sharing systems (e.g. Google Drive).

You can copy .zip from here ,here is google drive link
https://drive.google.com/open?id=1qQbNoBoOlYFcgTk0Cv-ZyqVqdrNstUSm

Thank you for your data. I found out the error, it's similar to #3 issue. I'll contact NetVips developer and fix this as soon as I can.

Feel free to reopen issue if you have some questions remaining.


Tutorial needed

this plugin seems to be quite helpful, however, I don't manage to set it up.
A quick guide on how to set it up would be great.

Maybe I find some time over the holidays.
Can you give me a hint on how your project is setup, so I can tailor the guide accordingly.
Are you using Maven or Gradle?

Gradle on windows 10.
I tried to add your lugin as a dependency the same way as I added the pdf or diagram plugin. nothing happened.
then I checked out your example. It ran and started firefox but firefox did not navigate to a page.
Maybe I also find some time to investigate further and try it with ubuntu...

Firefox is not navigating because the screenshot plugin uses an outdated version of selenium webdriver.
I need to change how web driver is provided to the plugin in order to be able to keep up with the fast rhythm at which new webdriver versions are released.
see also #11 and #9


ThetaForecaster now works with initial_level

Reference Issues/PRs
Fixes #692
What does this implement/fix? Explain your changes.
ThetaForecaster works when passed an initial_level, passed initialization_method parameter to ExponentialSmoothing
Does your contribution introduce a new dependency? If yes, which one?
NA
What should a reviewer concentrate their feedback on?
Is this a better fix or should I receive it from the user?
Refer: https://github.com/alan-turing-institute/sktime/issues/692#issuecomment-811197573
For all contributions

[ ] I've added myself to the list of contributors.
[x] I've added unit tests and made sure they pass locally.

@mloning, yeah, I noticed that too. I'll look around and get back to you.

Update: I was busy with some college work + assignments for the past few days. Sorry for the delay, this is on my radar this week.

Thanks for the update @yashlamba and no worries

Hi @mloning, I can confirm that the model is passing the correct parameters to ExponentialSmoothing and it does make some impact on the predictions (not very significant to fail our test). I debugged and checked this within the statsmodel ExponentialSmoothing call and the initial_level is correctly set and I am assuming that nothing will go wrong after that.
One thing I would like to point out is, this isn't something other implementations pass as a parameter, for instance, statsmodel implicitly sets data[0] as the initial level.
https://github.com/statsmodels/statsmodels/blob/557ee695c09542103e0da37dc9b6ed23b766c9be/statsmodels/tsa/forecasting/theta.py#L259-L261
and darts doesn't use this as a parameter too, https://unit8co.github.io/darts/generated_api/darts.models.theta.html.
My suggestions:

We can change our implementation to inherit ThetaModel from statsmodel.
We can merge this PR to fix the current API and open an issue for this.

Thanks @yashlamba - I suggest to merge this now. There is some ongoing discussion on refactoring the Theta model in #854, perhaps we can take that into account there.

Ok thanks @yashlamba - now merged!


Querying the STAC API for several models at the same time

Hi,
I am new to planetary computer and I am looking for an advice how to load several climate models at the same time. I am using nasa-nex-gddp-cmip6 data and I found this example for one model:
search = catalog.search(
collections=["nasa-nex-gddp-cmip6"],
datetime="1950/2000",
query={"cmip6:model": {"eq": "ACCESS-CM2"}},
)
items = search.get_all_items()
len(items)
However I need more than just "ACCESS-CM2'. For example also: 'ACCESS-ESM1-5', 'BCC-CSM2-MR', 'CESM2', 'CESM2-WACCM'. Could you please let me know of the syntax to load all or at least several climate models at the same time?
Many thanks,
Ivana

You would want
    query={
        "cmip6:model": {"in": ["ACCESS-ESM1", "ACCESS-CM2"]},
    },

This uses the fragment extension, where you can find the full list of operators / values.
In [3]: search = catalog.search(
   ...:     collections=["nasa-nex-gddp-cmip6"],
   ...:     datetime="1950/2000",
   ...:     query={"cmip6:model": {"in": ["ACCESS-ESM1", "ACCESS-CM2"]}},
   ...: )
   ...:
   ...: len(search.item_collection())
Out[3]: 51

Thank you very much. By the same logic, would it be possible to query at same given models and given variables (it does not seem to be work):
query={"cmip6:model": {"in": ["ACCESS-CM2", "ACCESS-ESM1-5", "CESM2"]},
"cmip6:variable": {"in": ["tasmax", "tas"]}
}

What would querying by variable mean here, and what's the motivation for querying on it? Something like "only return the times with a tasmax variable?
That isn't possible with the STAC items as they are today, since you can only query on item properties and things like tasmax are the keys of the assets. We could add some kind of variables field like ["tasmax", "tas", ...] with the list of variables. I'm not sure whether the STAC API specification supports queries on lists though (like "contains any" or "contains all").
For now, you can achieve this in python with something like
items = catalog.search(...)
keep = [item for item in items if item.assets & {"tasmax", "tasmin"}]

This will need to be fixed in the upstream stactools package. I opened https://github.com/TomAugspurger/nasa-nex-gddp-cmip6/issues/1 to track it.


Set default world fy_ice_world and make it fly

[ ] set default world - https://github.com/kodadot/nft-gallery/issues/1193
[ ] missing navmesh @rchovatiya88
[ ] positioning picture frames on the map
[ ] adding portals/teleports to the map
[x] place 3d models on top of island

Www.onerawartist.com
I built a business in the last 3 years haha ^^, you were there guys when it all started @vikiival @yangwao .
Lem me know if you need anything


Additional Properties not identified

In a prior version (v0.1.1), the specific additional properties were identified in the error message when additionalProperties keyword was set to false in the schema.
This no longer appears to be the case in v2.  Was this feature removed?  Is there way to retrieve the name of the additional property that is the source of the exception?

Hi @Arqu.  I was investigating this issue to see if this something I can address (I am a bit of a noob here).
There are two places where I believe the feature needs enhancement.   I had a couple ideas on how to address this, but would like your thoughts.  One easy way would be to pass key instead of data to AddError(), the second would be add in the property name to the error message.  This would be similar to the error message in regular fields.  The field name is included in the message in double quotes.
Both of these could end up being breaking changes as it changes the behavior.  So wondering if you had more insight on how to approach this.
https://github.com/qri-io/jsonschema/blob/08d62a2939dc09a375c7f2ffa66e7b29fa8c2a7b/keywords_object.go#L328-L331
https://github.com/qri-io/jsonschema/blob/08d62a2939dc09a375c7f2ffa66e7b29fa8c2a7b/keywords_object.go#L671-L674


[Do not merge] Disable webchat on the tax credits page

This page will be the first to transition to a new implementation that we want to test with HMRC.
This shouldn't be merged/deployed before the new implementation on alphagov/contacts-frontend is also ready to go: https://github.com/alphagov/contacts-frontend/pull/50

This isn't going to be the first page for implementation anymore, although it'll come later in the transition.
Going to close this pull request for now. We can re-open it when this page is ready to transition.


Remove AdditionalBuildOptions from Stages and Templates

Description
Prototypes removing AdditionalBuildOptions from YML stages and templates and -DshadeSpark from Cosmos Spark POMs as the only usage of AdditionalBuildOptions was configuring -DshadeSpark. -DshadeSpark was a fix for a build parallelization issue where running concurrent project shading, which happens with azure-cosmos-spark_3-1_2-12 and azure-cosmos-spark_3-2_2-12 run concurrently, and the version of maven-shade-plugin is updated to the latest version to verify that the issue has been resolved.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

/azp run java - cosmos - tests

/azp run java - cosmos - spark

@FabianMeiswinkel / @xinlian12 any concerns about this change with regards to Cosmos Spark?

Thanks @alzimmermsft  for answering. PR looks good to me. Good to sign off from cosmos side unless @xinlian12  has any feedback.

/check-enforcer override


Renamed model metadata attributes to ensure uniqueness #273

Proposed changes:

renamed metadata attributes of components to ensure the attributes are not overlapping between the components. fixes #273

Status:

[x] ready for code review
[x] there are tests for the functionality
[x] documentation updated
[x] changelog updated

What happens if someone uses two intent classifiers? Is this something we should allow without throwing an error?

It will work without issues (only the persistence won't work). The last classifier in the pipline will override the result of the previous one. So there is not a real use case here (but for the future we might do something like: "take the ouput from the classifier that is most confident").
Either way, this should be fixed since it also avoids cases where a mitie classifier got persisted and a sklearn classifier is supposed to load that.


ensinArr should return longest match

https://github.com/NaturalNode/natural/blob/8071055f103f2d9fead395c5b823e0b247fb13a7/lib/natural/stemmers/porter_stemmer_es.js#L54
as in the original algorithm is explained, this function should return the longest match/suffix.
This function will return the first suffix it finds which could be shorter that the one it should outputs. This makes failure in lot of words.
endsinArr(word, suffixes)
    {
        var matches = [];
        for(var i in suffixes) {
            if(this.endsIn(word, suffixes[i])){
                matches.push(suffixes[i]);
            }
        }
        var longest = matches.sort(function (a, b) {
            return b.length - a.length;
        })[0];

        if(longest){
            return longest
        } else {
            return '';
        }
    }

if you could work this into a PR id happily merge, dont have much time right now to really work on it and test it

Spanish stemmer has been updated.


Improve cbor type inclusion detection during codegen

Previously we werent detecting that the richtext facet features union needed to have the special union cbor type encoding set on it. This was because the 'walk' function we use to recursively set this field didnt cross schema boundaries, and even if we did that shallowly, we could have already processed the referenced schema and not actually passed the flag down recursively. So now as a hack i'm just calling the walk-set function twice. This is obviously bad, and I think we should just rewrite the codegen code instead of trying to improve it, it was written before several large lexicon refactors and its super messy as a result.

Empty $type has been remedied, also resulted in some cleanups on a bunch of other types. It's still not perfect but its good enough to get search processing going again


Decrease CI time to run tests

It can be up to an hour (or worse: cancelled) to run the main tests. It should be less than 10 minutes, ideally only a few.
Move to Circle CI or pay GitHub.

Seems that using self-hosted runners is not supported yet (Hope they support this soon according to this reply)
A paid plan is not an option because we can't upgrade the machine. The current specs of the runners are:

2-core CPU
7 GB of RAM memory
14 GB of SSD disk space

@Gamenot Consider moving to CircleCI?


3.0.x portal build

What does this PR do?
Fixes traffic_portal build issues in addition to updating ca-certificates in all builds.  These had been fixed in master recently.
Which TC components are affected by this PR?

[ ] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[x] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] Other _________

What is the best way to verify this PR?
Check all that apply

[ ] This PR includes tests
[ ] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

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


Add missing READMEs & Update package.json in all RN packages

Summary:
This diff adds missing README files for all public RN packages.
Changes:
For all public RN packages:

Add Missing READMEs

Update package.json in all RN packages to add:

Issues, Bugs urls
Keywords and Homepage urls to respective pkgs

Changelog:
[INTERNAL][ADDED] - Add missing README files for all public RN packages.
[INTERNAL][CHANGED] - Update package.json in all RN packages to add required fields.
Test Plan:

yarn lint && yarn flow && yarn test-ci --> should be green

This PR is stacked on "Update Node.js to v16".

[ ] TODO: Rebase once that PR is merged.

Update: Had some free time, so rebased & resolved the conflicts 😅.
@hoxyq I've left self review above explaining why particular changes are done.
Also about adding more info to respective READMEs, I guess (contributors/maintainers) can iteratively do that as per convenience and shouldn't be a blocker for merging.
cc: @cortinico

Addressed suggestions re: jest testing syntax 👍


Syncing update FJ > Refresh

Pulls FJ changes into Refresh
Review

@sebworks
@jimmynotjim

Nothing standing out to me :+1:

LGTM


[BUG]: Missing/Bugged texture for leaves in 1.19.2, latest forge and mod version.

Bug Description
a video will explain it better.
Typical purple and black missing texture block instead of the leaves.
Looking at the top allowed me to see which mod was in cause
This could be due to Passable Foliage 🌳
https://www.curseforge.com/minecraft/mc-mods/passable-foliage
could also not be linked to your mod, in which case I apologise...
Logs and Crash Reports
the log is too heavy, I had to use Mega for it:
https://mega.nz/file/MdBkUSjR#MTINOQxep1Pru_N-dazmGGYg6UgwYzhqeins1rnM0iE
Screenshots and/or Videos
https://user-images.githubusercontent.com/111076631/226139188-4351840b-14ec-4296-ae19-26f4b2a6920d.mp4
Bug Reproduction
Find the specific leaves, it seems like. (found underground, mixed with the Lost Cities mod's railing)
Expected Behavior
Normally textured leaves
Minecraft Version
1.19.2
Mod Version
1.73.0
Modpack
Other

@Daltaxy It seems another mod is indeed interfering. If I try this with just occultism + dependencies the leaves are normal.
If you can find out which mod causes it (by removing mods until it works) you can create a ticket there and link them to this issues s I can work with them to fix it

@Daltaxy it was indeed closed as inactive (I try to keep the issues that are not feature requests decluttered to know what to focus on). That said, if you do find additional info feel free to ping me here so I can reopen the investigation!

In case anyone has this issue in the future like I did in 1.20.1, The mod that was causing the issue for me was the Better Foliage Renewed mod, once I removed that mod it fixed this issue.


Update version in CITATION.cff automatically

Describe the bug
The version field in CITATION.cff isn't updated automatically.
To reproduce the bug
Steps to reproduce the behavior:

Compare the versions in ./pom.xml and ./CITATION.cff (both from current develop state, same is true for main):

https://github.com/hexatomic/hexatomic/blob/a963811f480ec6fdb93a63f2072cf31e5b90af82/pom.xml#L7
https://github.com/hexatomic/hexatomic/blob/a963811f480ec6fdb93a63f2072cf31e5b90af82/CITATION.cff#L11
Expected behavior
Both files show the same version.
This could be done by automatically updating CITATION.cff on pushes to the respective branches, at specific checkpoints, i.e., after releases, when the version is updated via the GitFlow Maven plugin. (CFF will not reflect version perfectly in all granularity for all commits, but this is fine.)

This is an action currently under development that may solve this: https://github.com/atrisovic/update-cff. @sdruskat is in touch with the developers.

This has been solved by using the Maven CFF Plugin


feat: support to set an alternative image owner

This is useful when contributors want to test their pull request. And even they could use their pull request before it got merged.

This would break running goreleaser locally, though I really like making this easier to fork. Think you could fix the Makefile as well so goreleaser still works when not run in Github Actions? :pray:

Goreleaser could work well without GitHub Actions. Because I provided the environment variables.

Yes thank you this looks good!  :heavy_check_mark:


Fix no answer provided bug in dashboard

Currently, /dashboard/applications shows No answer provided for all application answers, even those that had an answer.

Fake news - bug was already fixed


Integration is using deprecated DEVICE_CLASS_* constants

This custom integration uses deprecated DEVICE_CLASS_* constants in its codebase.
The DEVICE_CLASS_* constants have been deprecated and replaced in Home Assistant Core 2021.12 (over a year ago). I would highly suggest updating/migrating this integration to the new enums.
For example, for the device classes supported by the sensor platform, there is now a SensorDeviceClass enum. So if a sensor previously used the DEVICE_CLASS_ENERGY constant, it should now use SensorDeviceClass.ENERGY. Other platforms (like binary_sensor, and number) provide similar enumerations for their supported device classes.
The migration thus only consists of replacing constants with an enumeration member and is, therefore, very low impact and should be fairly straightforward. I did noticed some have been migrated recently; however, there are still cases remaining in this repository (sensor.py).
If I can help resolve any questions regarding this change or migration, feel free to ask or respond to this issue. I'm happy to help!
Kindest regards,
../Frenck

Is this why Eforsyningen has stopped working?

If it stopped working, it wouldn't be because of this specific report/change.

Oh, okay, I suddenly had all my Eforsyning Entities say unavailable, reloading was, of cause, ineffective, any ideas?

No, as said, not related to this issue, sorry 🤷

Thanks frenck.  This is a good help to stay updated.
Actually I just made a release of the integration where I made updates to the sensors to use the new enums, and try to use the "suggested_unit" attribute.  I'll take a look through the remaining code to catch left-overs.

@kpoppel It looks odd? Using some of those features you mentioned in your last comment, require a user to use minimal version of Home Assistant (e.g., suggested_unit was introduced fairly recently).
Yet, your hacs.json doesn't limit or guard a minimal Home Assistant version:
https://github.com/kpoppel/homeassistant-eforsyning/blob/main/hacs.json

Thanks for letting me know.  HA is really a moving target and as a 1%-time developer on this code it is not easy to stay on top :-)  I will read up o this aspect of Hacs too.
Actually if you don't mind I'd like to ask you  a question on this unit conversion?  The issue #43 requests the UI to show values in MWh.  The API returns values in kWh consistently, but there are some values which some find useful to be displayed in MWh.  I though the suggested_unit would enable some form of setting on the sensor to change the unit displayed, but that is not how this works I guess.  How would I go about this?
I can ofc. scale everything from the API to be i MWh and some to be in kWh by disrupting historical data, but really I believe this should be a UI thing, not a base data unit thing.

but there are some values which some find useful to be displayed in MWh

Use can change the unit to anything they like in the entity setting themselves, Home Assistant will convert the units for them. If they like to show it in Wh, that is possible too 🤷

I though the suggested_unit would enable some form of setting on the sensor to change the unit displayed, but that is not how this works I guess.

That is not what that is. It suggest the unit Home Assistant should use for the sensor. This is only read the first time the sensor is created and added to the registries.
For example, 3D printers use degrees celsius for temperatures everywhere in the world. As Home Assistant will use Celsius or Fahrenheit for temperatures automatically based on the user settings. These 3D printer temperature sensors would previously end up being displayed as Farhenheit for our American users.
The suggested unit function, allows 3D printer integrations to say: Hey, whatever else, this sensor should be using Celcius. Home Assistant will honor this when creating the sensor. If a user decides he still want Farhenheit, the user can change it in the entity setting to override (and HA will again take care of conversion).

Ah okay.  I guess I will leave it in there so new installations will have MWh suggested... and set minimum HA version to 2022.12 where I think this first appeared? (I am looking through home-assistant/core to figure out when this actually was)
This entity setting for selecting the unit of display, where is that?  If i fx. go to one of the sensors it doesn't seem like the unit can be changed there?

This entity setting for selecting the unit of display, where is that?

Right there on that screen. Is has been rolled out for many units already, but apparently not yet for energy. Should not take to long anymore, as every release new unit conversion have been added the past months.
../Frenkc

Oh okay.  I will roll out 2023.1 on my test instance to see if it is there then.  That would solve that issue by itself then.
It is very friendly of you to help out with these questions. Thank-you.

I will roll out 2023.1 on my test instance to see if it is there then.

It is not in 2023.1, just checked myself. Maybe 2023.2 🤷
However, that does not change the way integration should handle thing. Integration should represent data as-is as much as possible.

It is very friendly of you to help out with these questions. Thank-you.

Yeah, sure, no problem! 👍
../Frenck

Thanks for address the original reported issue btw! Awesome!
../Frenck


Fix fsspec download

Testing ds = load_dataset("audiofolder", data_files="s3://datasets.huggingface.co/SpeechCommands/v0.01/v0.01_test.tar.gz", storage_options={"anon": True}) and trying to fix the issues raised by fsspec ...
TODO: fix
    self.session = aiobotocore.session.AioSession(**self.kwargs)
TypeError: __init__() got an unexpected keyword argument 'hf'

by "preparing storage_options" for the fsspec head/get

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[BACKLOG-36417]Updated browse in SSTableOutput Step

:white_check_mark: Build finished in 1m 37s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 114, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


Confusing docs for OrientationBuilder

https://docs.flutter.io/flutter/widgets/OrientationBuilder-class.html says

Builds a widget tree that can depend on the parent widget's orientation (distinct from the device orientation).

https://flutter.io/cookbook/design/orientation/ says

In order to determine the Orientation of the screen, we can use the  OrientationBuilder Widget.

What is the difference between

screen orientation
device orientation
parent widget's orientation?

It would seem to me that the cookbook is confusing terms. The orientation of the screen (which I would think is synonymous with device) should be retrieved via MediaQuery.of(context).orientation.
OrientationBuilder doesn't reflect the orientation of the device / screen at all, but rather if the parents width is greater than its height as detailed in the source comment:

A widget's orientation is simply a factor of its width relative to its height. For example, a [Column] widget will have a landscape orientation if its width exceeds its height, even though it displays its children in a vertical array.

@brianegan

Good call, I'll fix that up!

Proposed solution here: https://github.com/flutter/website/pull/1120

Gotcha... I've pushed another update, please let me know what you think.

LGTM 👍

In any case use "MediaQuery.of(context).orientation". It is much better than OrientationBuilder. OrientationBuilder unexpectedly changes orientation when GridView is primary and the focus is on a TextField. It slows down the SliverAppBar significantly.


Vendor in latest containers/storage and containers/buildah

Should fix the issue on Windows platform.
Lots of other fixes and enhancements.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

LGTM

@TomSweeneyRedHat @baude @giuseppe @vrothberg PTAL

/lgtm

LGTM assuming happy tests.


Update to hyperlink: Under To Add Contacts: 1. "Use this CSV template to make"

Description of the change: Update to hyperlink: Under To Add Contacts: 1. "Use this CSV template to make"
Reason for the change:
Link to original source:

Closes #

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.34 out of 35 committers have signed the CLA.:white_check_mark: Whatthefoxsays:white_check_mark: richbachman:white_check_mark: arshadkazmi42:white_check_mark: ksigler7:white_check_mark: geekysrm:white_check_mark: ThiruPraveen18:white_check_mark: nathan78906:white_check_mark: mollyfriederich:white_check_mark: dharmendra-lingaiah:white_check_mark: daniloff200:white_check_mark: abdullah-K:white_check_mark: jvogit:white_check_mark: hmbrown64:white_check_mark: michizhou:white_check_mark: crweiner:white_check_mark: StrikerRUS:white_check_mark: Jeremyyang920:white_check_mark: anujs3:white_check_mark: cemurray:white_check_mark: aroach:white_check_mark: spencerbyw:white_check_mark: rawkode:white_check_mark: kylearoberts:white_check_mark: anchepiece:white_check_mark: kstolte:white_check_mark: jessicaannpopp:white_check_mark: techgaun:white_check_mark: thisaaronm:white_check_mark: justinwhall:white_check_mark: Nerdwood:white_check_mark: hugovk:white_check_mark: duncanleung:white_check_mark: mauricetmeyer:white_check_mark: h-a-r-s-h-a:x: lpresgroveYou have signed the CLA already but the status is still pending? Let us recheck it.


Bump version to 2.13.0

I'd love to include #521 before releasing. It's a pretty uncontroversial set of changes that fix a couple of bugs I introduced recently.


Invalid bundle ID for container error

I got this problem when try out. Can you give me a solution to fix this?

Hi! This looks like the application bundle ID might not be associated with your CloudKit container. You can check in Xcode under "Signing & Capabilities" to ensure it's configured correctly, and this document has some more details on what's involved.

Regarding this issue, first, you need to make sure that the containerIdentifier in Config.swift is correct.
Additionally, it's important to note that I found that regardless of whether modifyRecordZones is successful or not, UserDefaults.standard.set(true, forKey: "contactZoneCreated") will be executed in the following code:
    /// Creates a custom CKRecordZone and saves it to the database if needed,
    /// checking `UserDefaults` if this has been done before on this device.
    private func createContactsZoneIfNeeded() async throws {
        guard !UserDefaults.standard.bool(forKey: "contactZoneCreated") else {
            return
        }

        let newZone = CKRecordZone(zoneID: contactsZoneID)
        _ = try await database.modifyRecordZones(saving: [newZone], deleting: [])

        UserDefaults.standard.set(true, forKey: "contactZoneCreated")
    }

This means that even if you correct the error in Config.swift later, you still won't be able to create a zone.
The viable solution is to manually create the zone in CloudKit Dashboard or use UserDefaults.standard.set(false, forKey: "contactZoneCreated") in your code to enable modifyRecordZones to run again.


Proposal - publish an index in Collection remove event

Right now, there doesn't appear to be any way to get the index of the removed element.
collection.on('splice', (collectionevent) => {
     const index  = collection.getArray().indexOf(collectionevent.element);
})
collection.on('remove', (collectionevent) => {
    // no way to get index of removed element
})

The use case would be lets say I have a list of elements for layers. If one layer gets removed, I'd like to update that list by removing the index of the list element that should be removed. But that's not really possible without some sort of index property.
This proposal would add the index to the collectionevent's, so that I can automatically get the index for inserted and removed elements.
Thoughts?

Hi @roemhildtg,
It's a good idea ! see #8964


groupBy sorting behaves not as expected with granularity != 'all'

I ran this query:
{
  "queryType": "groupBy",
  "dataSource": "wikipedia",
  "intervals": [
    "2015-08-14/2015-08-15"
  ],
  "granularity": {
    "type": "period",
    "period": "PT1H",
    "timeZone": "Etc/UTC"
  },
  "aggregations": [
    {
      "name": "Count",
      "type": "count"
    }
  ],
  "dimensions": ["newPage"],
  "limitSpec": {
    "type": "default",
    "limit": 7,
    "columns": [
      {
        "dimension": "Count",
        "direction": "descending"
      }
    ]
  }
}

and got this result:
[ {
  "version" : "v1",
  "timestamp" : "2015-08-14T00:00:00.000Z",
  "event" : {
    "newPage" : "false",
    "Count" : 8609
  }
}, {
  "version" : "v1",
  "timestamp" : "2015-08-14T00:00:00.000Z",
  "event" : {
    "newPage" : "true",
    "Count" : 478
  }
}, {
  "version" : "v1",
  "timestamp" : "2015-08-14T01:00:00.000Z",
  "event" : {
    "newPage" : "false",
    "Count" : 7439
  }
}, {
  "version" : "v1",
  "timestamp" : "2015-08-14T01:00:00.000Z",
  "event" : {
    "newPage" : "true",
    "Count" : 378
  }
}, {
  "version" : "v1",
  "timestamp" : "2015-08-14T02:00:00.000Z",
  "event" : {
    "newPage" : "false",
    "Count" : 6537
  }
}, {
  "version" : "v1",
  "timestamp" : "2015-08-14T02:00:00.000Z",
  "event" : {
    "newPage" : "true",
    "Count" : 327
  }
}, {
  "version" : "v1",
  "timestamp" : "2015-08-14T03:00:00.000Z",
  "event" : {
    "newPage" : "false",
    "Count" : 5061
  }
} ]

It seems like the results from the different granularities (2 per hour in this case) are concatenated together and never resorted. The limit is then applied to the entire (non sorted list) making it useless.
The workaround (for anyone interested) and the expected action is:
{
  "queryType": "groupBy",
  "dataSource": "wikipedia",
  "intervals": [
    "2015-08-14/2015-08-15"
  ],
  "granularity": "all",
  "aggregations": [
    {
      "name": "Count",
      "type": "count"
    }
  ],
  "dimensions": [
    {
      "type": "extraction",
      "dimension": "__time",
      "outputName": "timestamp",
      "extractionFn" : {
        "type" : "timeFormat",
        "format" : "yyyy-MM-dd'T'HH':00:00Z",
        "timeZone" : "Etc/UTC",
        "locale" : "en"
      }
    },
    "newPage"
  ],
  "limitSpec": {
    "type": "default",
    "limit": 7,
    "columns": [
      {
        "dimension": "Count",
        "direction": "descending"
      }
    ]
  }
}

There are actually two separate uses for groupBy that are being muddled up here.

One is that granularity functions more like it does in topN and returns a separate groupBy per granularity with it's own limit in a nested JSON data structure.
Is that granularity functions just like another dimension in the dimensionSpec (which is what I was trying to do here)

My proposed solution to this issue.

Add a resorting step when granularity != 'all'
Add a flag that would allow the user to get a topN like group by out with one group by per granularity bucket (with its own limit) (solves 1)
Add a dimension extractionFn so that the user can use the syntax of the GranularitySpec to bucket in the dimensions list avoiding the hack used above (solves 2)

This looks related to https://github.com/druid-io/druid/issues/701 and https://groups.google.com/d/msg/druid-development/BSpDmAq-7Jk/_W3q00kkwMIJ
can you confirm or refute if these look similar?

Fwiw the way groupBy granularity and limitSpec are supposed to work now is that results are first grouped in their granular buckets (so, one set of groupings for each day if you have granularity "day"), then they are sorted within their granular buckets, then the limit is applied to the global list of results starting from the first granular bucket.
Whether or not this is useful behavior is left as an exercise to the reader.
I agree that it seems weird that the sorting is done within granular buckets, but the limiting is done globally. It would probably make more sense to do both within the buckets or both globally. If they're both local then it acts like your (1). If they're both global it acts like your (2).

@drcrallen I read those issues and they do not look related but I might be missing something. I am aware of how zero filling works and this is not in play here because there is data in all those buckets.
I think the root problem here is that groupBy returns results in it's own special way. groupBY is the only query type which uses the key 'event' in the return. groupBy tries to de-nest itself (unlike topNs) but does not go all the way since it forgets to resort.

Whether or not this is useful behavior is left as an exercise to the reader.

It isn't

for (1) it would also be nice to change the flatness of groupby and get a nested data-structure like topN maybe with a flag?

related #1780

+1

+1

+1

+1

+1

-1 to nested data structures; relational is easier to consume

Fwiw when you group by FLOOR(__time TO X) then Druid SQL will run a query similar to @vogievetsky's suggested workaround. The reason is because that's more like what SQL semantics would expect.

For anyone watching, I'd suggest using Druid SQL, since it has the behavior you would expect. (Under the hood it will issue a granularity 'all' groupBy query and then include a timestamp_floor expression as one of the dimensions)

@gianm Thanks for the suggestion about using granularity all in conjunction with an extraction function on the __time dimension, and it really works - but I noticed (in my version of Druid at least) that it's a loooot slower.
Version 1 "Basic Granularity"
  "granularity": "day",
  "dimensions": []

Version 2: "JS Dimension"
"granularity": "all",
"dimensions": [{
  "type": "extraction",
  "dimension": "__time",
  "outputName": "day",
  "outputType": "STRING",
  "extractionFn": {
    "type": "javascript",
    "function": "function (milliseconds) { return new Date(milliseconds).toISOString().replace(/..:..:......Z/, '00:00:00.000Z') }"
  }
}]

Version 3: "Time Format Dimension"
"granularity": "all",
"dimensions": [{
  "type": "extraction",
  "dimension": "__time",
  "outputName": "day",
  "extractionFn": {
    "type": "timeFormat",
    "format": "yyyy-MM-dd"
  }
}]

Average Query Durations in MS
Small-Size Dataset
Basic Granularity 1230ms
JS Dimension 2430ms
Time Format Dimension 2570ms
Medium-Size Dataset
Basic Granularity 3370ms
JS Dimension 6940ms
Time Format Dimension 11780ms
Large-Size Dataset
Basic Granularity 21090ms
JS Dimension 51090ms
Time Format Dimension 50890ms
Is this an inefficiency only present in older versions of Druid (v0.9.2)?
Am I doing something wrong?
Is it that the native granularities are preoptimized in a way that I can't get with manually-implemented granularities?
This performance penalty is serious enough that it doesn't quite qualify as a solution for my use-case. Unfortunately.

Hi @alflennik, the native granularities are indeed somewhat more optimized. This is something that I expect will not be true in the future as we bring more optimization to the expression system.

@gianm Thanks for the reply! After thinking on it a while I figured out a good way in my system to make a time-based dimension available for the unusual situations that demand it while 99% of the time relying on the native granularities.


3.5e SRD incompatibility errors

If you are using 3.5e SRD system, this module shows (at least) two errors due some kind of incompatibility:
If you choose the option to let players drag the mission rewards and drop it to their character sheets, the rewards should disappear from the mission log and appear in the character sheet. Also, a message should appear in the GM screen about it.
However, in the 3.5 SRD system, if a player drags and drops a reward, it still remains in the mission log and the player can drag and drop it multiple times, creating copies of the rewards. Also, none message appears in the GM screen about it.

Hi @ilore thanks for submitting this issue. Please see #1 regarding FQL going into maintenance mode. I'm releasing a continuation of the quest log as a new module with significantly upgraded tech hopefully before the v9 launch of Foundry around the beginning of the new year. There will be an easy upgrade path. There likely will be few if any additional releases of FQL. It's rock solid right now.
I did however investigate this issue as of course it affects FQL and the new quest log. It turns out that the D35E game system does not call the super method for _onDrop in the base Foundry ActorSheet which it extends. The hook that the quest log uses to implement removing the item and posting the notification fires in the parent / Foundry ActorSheet base class.
You can see the _onDrop implementation in the D35E code here and notice that super._onDrop is not invoked:
https://github.com/Rughalt/D35E/blob/master/module/actor/sheets/base.js#L2382
So technically it is an oversight / issue w/ D35E by not deferring to the base class implementation of ActorSheet. That or if a wholly custom implementation is necessary then D35E should explicitly fire the same hooks as the base ActorSheet class which it doesn't presently. So FQL or any other module that depends on the dropActorSheetData hook will fail to work.
Not really anything I can do on the FQL / quest log side of things except post a bug / issue in the D35E repo.
Thanks for finding this though! Erg... I wonder how many other game systems this may do a similar thing / cause the same issue.
Alas right now just disabling drag & drop for rewards until a fix is in place with the D35E game system is pertinent.

@ilore; good news... Looks like Rughalt just addressed the issue with D35E game system, so hopefully in the next release of D35E things will work correctly. Do keep in touch after the next update to the system if the problem persists.
For the time being I'm going to close this issue.


[Bug]: Development store preview on Plus Sandboxes

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Extension
Expected behavior
When activating the "Development store preview" feature in an app extensions panel, new draft features should appear in the Theme Editor given by the command npm run shopify app dev

Actual behavior
On Plus Sandboxes, this does not work, npm run shopify deploy is mandatory to see new features.
It's annoying when you have to work on features linked to Plus only features (like B2B for instance)
Verbose output
➜ npm run shopify app dev -- --store=b2b-accounts.myshopify.com --verbose

><EMAIL_ADDRESS>shopify
> shopify app dev --store=b2b-accounts.myshopify.com --verbose

2024-04-17T10:20:04.603Z: Running command app dev
2024-04-17T10:20:04.620Z: Getting a random port...
2024-04-17T10:20:04.626Z: Random port obtained: 62539
2024-04-17T10:20:04.668Z: cloudflared already installed, skipping
...

Reproduction steps

Run the following command to any Plus Sandbox store :

npm run shopify app dev

Add a new component in the extension

Command output shows the component is uploaded

It does not appear in the Theme Editor, even after reloading the page

Operating System
Mac OS
Shopify CLI version (check your project's package.json if you're not sure)
3.59.0
Shell
zsh
Node version (run node -v if you're not sure)
v20.11.1
What language and version are you using in your application?
Node

hi @bastos71 thanks for reporting this issue and for your patience 🙏 first -- do you have the correct permissions to use dev sandbox stores for this plus merchant?? you'll need a staff account
next, can you share all the verbose logs of app dev, including when you modify a theme app extension?? i only see the beginning of the logs in the issue description
lastly, can you also confirm your folder structure matches the expected structure of an app?? if app dev isn't run in the correct directory, your changes may not be picked up while developing
thanks for your help as we investigate your issue!

Hello @mgmanzella !
This Shopify Plus instance is a sandbox one I created from our partner dashboard, so I guess there wouldn't have any issue about right access ?
For the logs, I voluntarily gave only the first lines for several reasons :

full log was really long 😬
it was not different from the log I get with a classic Shopify instance

If you still want full log, let me know, and I'll try to send it 👍
For the folder structure, my app was not created with shopify cli, but everything works with a classic Shopify instance, so I guess the problem should not come from there ?

If you still want full log, let me know, and I'll try to send it 👍

yes pls! and make sure it includes logs of when you're modifying your theme app extension. if you're having trouble sending it over a github issue, feel free to DM me in the partners slack @Morisa Manzella

This Shopify Plus instance is a sandbox one I created from our partner dashboard, so I guess there wouldn't have any issue about right access ?

yeh looking at your account you're the owner so there shouldnt be any issues. does app dev work for a non plus development store?? is that what you mean by a classic Shopify instance??

Hi @mgmanzella, just to add: for me it works when I create a plus sandbox store directly, but it doesn't work if I create a plus sandbox organisation and then create plus sandbox stores within the org.

👋 Hey @bastos71 @knjshimi,
Thank you for reporting this!
I could reproduce this issue with new apps in the CLI 3.59; however, I can no longer reproduce it in 3.61, as we've updated the infrastructure that uploads theme app extensions.
Could you please confirm if 3.61 is also working for you? If so, we may close this issue :)
I really believe this is going to work, but in case it doesn't, feel free to DM me on Partners Slack (@Guilherme Carreiro) with the --verbose logs.
Thanks again :)


Issues with determinism between production-mode and dev mode

(Similar issues must be investigated when switching between wasmtime and wazero on feature/wazero branch)
Running the following commands show determinism issues:
SERVER-SIDE: from latest firehose-ethereum v1.4.3, pointing to eth-mainnet blocks
fireeth start firehose --substreams-enabled=true --substreams-state-store-url=/tmp/states [...]
dev-mode:
rm -rf /tmp/states && substreams run -e localhost:9000 --insecure https://github.com/streamingfast/substreams-uniswap-v3/releases/download/v0.2.7/substreams.spkg graph_out  -t 12369800  | grep -vE '(^TraceID|all.done)' | jq -s<EMAIL_ADDRESS>returns "Pool"
prod-mode:
rm -rf /tmp/states && substreams run -e localhost:9000 --insecure https://github.com/streamingfast/substreams-uniswap-v3/releases/download/v0.2.7/substreams.spkg graph_out  -t 12369800 --production-mode  | grep -vE '(^TraceID|all.done)' | jq -s<EMAIL_ADDRESS>returns "Transaction"

Possibly linked, in feature/wazero branch, even when using wasmtime as the runtime:
SERVER-SIDE: from firehose-ethereum branch feature/wazero-parallel
fireeth start firehose --substreams-enabled=true --substreams-state-store-url=/tmp/states [...]
dev-mode:
rm -rf /tmp/states && substreams run -e localhost:9000 --insecure https://github.com/streamingfast/substreams-uniswap-v3/releases/download/v0.2.7/substreams.spkg graph_out  -t 12369800   | grep -vE '(^TraceID|all.done)' | jq -s<EMAIL_ADDRESS>returns  "PoolDayData"
(this is different than both values from the v1.4.3 branch)

This has been fixed in feature/wazero branch. Merging to develop soon.

Fixed https://github.com/streamingfast/substreams/pull/229


Clean up interaural_time_difference function

Look at comments
Clean up code

Function is removed from Toolbox and no part of https://github.com/sfstoolbox/sfs-deprecated-code


tuled.tsv updated

I think it would also make sense to run cldfbench lexibank.makecldf and add the resulting changes in cldf/ to this PR.

@LinguList Both, overleaf and google drive, have an API. So fetching the files from there could implemented in download. What do you think?

@robert
there is one more treebank:
https://github.com/UniversalDependencies/UD_Makurap-TuDeT/tree/dev
On Wed, Mar 17, 2021 at 3:11 PM Robert Forkel @.***>
wrote:

@LinguList https://github.com/LinguList Both, overleaf and google
drive, have an API. So fetching the files from there could implemented in
download. What do you think?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tupian-language-resources/tuled/pull/27#issuecomment-801113119,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALNZPK5PY3DRTOZM57XRYXTTEC2CVANCNFSM4ZKRERLA
.

sorry for the late answer, @xrotwang, I know the google drive api rather
well, but you need to have an access token. So I do not know if this can
be done without this (that shows your account). It would of course be
extra convenient, to use the download command, but then locally, with
local access tokens, right?

This can be handled from within the cldfbench command!

@StasReichert, I ran into much earlier errors, which need to be checked first. Do you use a virtual environment, as recommended for your cldfbench code?
My error points to problems in the concept list.

  File "/home/mattis/.envs/lb-1/bin/cldfbench", line 8, in <module>
    sys.exit(main())
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/__main__.py", line 78, in main
    return args.main(args) or 0
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/pylexibank/commands/makecldf.py", line 23, in run
    with_dataset(args, 'makecldf', dataset=dataset)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/cli_util.py", line 82, in with_dataset
    res = func(*arg, args)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/pylexibank/dataset.py", line 217, in _cmd_makecldf
    super()._cmd_makecldf(args)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/dataset.py", line 214, in _cmd_makecldf
    self.cmd_makecldf(args)
  File "./lexibank_tuled.py", line 71, in cmd_makecldf
    idx = '{0}_{1}'.format(concept['NUMBER'], slug(concept['ENGLISH']))
KeyError: 'NUMBER'

This happens when running cldfbench lexibank.makecldf lexibank_tuled.py --concepticon-version=v2.4.0 --clts-version=v1.4 --glottolog-version=v4.3
The error points to a missing column NUMER in our etc/concepts.tsv, which has not been added there, if you check the header. The first row should be NUMBER, so please check that the google docs is correct here.

Another error, having fixed the first one:
Traceback (most recent call last):
  File "/home/mattis/.envs/lb-1/bin/cldfbench", line 8, in <module>
    sys.exit(main())
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/__main__.py", line 78, in main
    return args.main(args) or 0
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/pylexibank/commands/makecldf.py", line 23, in run
    with_dataset(args, 'makecldf', dataset=dataset)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/cli_util.py", line 82, in with_dataset
    res = func(*arg, args)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/pylexibank/dataset.py", line 217, in _cmd_makecldf
    super()._cmd_makecldf(args)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/dataset.py", line 214, in _cmd_makecldf
    self.cmd_makecldf(args)
  File "./lexibank_tuled.py", line 101, in cmd_makecldf
    SubGroup=row['SubGroup'],
KeyError: 'SubGroup'

This shows that the etc/languages.tsv file has lost the SubGroup column, which was there originally, and it seems I did not include it when trying to fix it. It should be included in the google docs from now on, as we had this in earlier versions.

Another error:
Traceback (most recent call last):
  File "/home/mattis/.envs/lb-1/bin/cldfbench", line 8, in <module>
    sys.exit(main())
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/__main__.py", line 78, in main
    return args.main(args) or 0
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/pylexibank/commands/makecldf.py", line 23, in run
    with_dataset(args, 'makecldf', dataset=dataset)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/cli_util.py", line 82, in with_dataset
    res = func(*arg, args)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/pylexibank/dataset.py", line 217, in _cmd_makecldf
    super()._cmd_makecldf(args)
  File "/home/mattis/.envs/lb-1/lib/python3.9/site-packages/cldfbench/dataset.py", line 214, in _cmd_makecldf
    self.cmd_makecldf(args)
  File "./lexibank_tuled.py", line 107, in cmd_makecldf
    sources[row['ID']] = row['Sources'].split(',')
KeyError: 'Sources'

This shows that we used Sources not Source before, so Source should be renamed to Sources, also in the google sheet.

@lingulist I am correcting the errors right now. ASAP I Stas will
commit the corrected files
On Wed, Mar 17, 2021 at 11:09 PM Johann-Mattis List <
@.***> wrote:

@LinguList commented on this pull request.
My updates fix the errors.
I added a checker for bibliographies, please check the overleaf, they give
you also a warning on duplicate bibtex keys, and there are some!

Reply to this email directly, view it on GitHub
https://github.com/tupian-language-resources/tuled/pull/27#pullrequestreview-614827305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALNZPK3CLX4FMTBDF7Q72ZDTEESCZANCNFSM4ZKRERLA
.

@LinguList, we have applied all the changes you suggested to the tsv files and with your patch the code runs without any problems on my computer (I did have to add a minuscule change to lexibank_tuled.py so that it runs on Windows; I run everything in a virtual environment, just as you told me to back in October).
I have pushed the results into the languages_and_data branch and the only error remaining is the "* BIBTEX MISSING " entry, whose source we could not figure out so far.

Nice, @StasReichert, the errror warning does not have a key, so the key is empty, so this means, in the languages.tsv, you have one line ending in a comma, or two commas one after the other. These need to be fixed (again on google doc, then submitted here).

@LinguList we have found the error in the sources. Just as you said, it was in the languages.tsv file. We had to add sources to five languages that had empty cells in the column "Sources" and that did the trick. In the process we also eliminated another repeated entry. I hope we have thus cleaned our data and prepared it to be processed further.

I'll merge now. @xrotwang, I think this is all we need to get started now, right? Adding API support to download for the google docs and overleaf is something we could/should do later.

ok. nice.

yes, this is clearly a mistake
On Thu, Mar 18, 2021 at 3:24 PM Robert Forkel @.***>
wrote:

@.**** commented on this pull request.
In cldf/languages.csv
https://github.com/tupian-language-resources/tuled/pull/27#discussion_r596919028
:

+Kepkiriwat,Kepkiriwat,kepk1241,,,,-11.66,-61.25,,,

+Kuruaya,Kuruaya,kuru1309,,,,-3.09561,-52.2303,,,
+TupiAustral,Tupí Austral,tupi1274,,,,-23.95,-46.38,,,
+Makurap,Makurap,maku1278,,,,-11.8701,-64.3201,,,
+Matanau,Matanau,,,,,-6.0372,-60.48,,,
+Mbya,Mbya,mbya1239,,,,-26.0188,-52.711,,,
+Mekens,Mekens,saki1248,,,,-13.054,-62.0927,,,
+Monde,Monde,sala1273,,,,-12.0499,-61.25,,,
+Munduruku,Mundurukú,mund1330,,,,-8.41095,-57.691,,,
+Nheengatu,Nheengatu,nhen1239,,,,1.04503,-66.9646,,,
+NtogapidItogapuk,Ntogapid-Itogapuk,,,,,-10.452133,-61.66003,,,
+OldGuarani,Old Guaraní,,,,,-26.25,-54.29,,,
+Omagua,Omagua,omag1248,,,,-3.53,-69.17,,,
+Parakana,Parakana,para1312,,,,-4.64681,-50.0621,,,
+Parintintin,Parintintin,tenh1241,,,,-7.92626,-61.936,,,
+Piripkura,Piripkura,,,,,-61.01505,-9.70581,,,
Piripkura has the coords confused. Should be -9.70581,-61.01505.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tupian-language-resources/tuled/pull/27#pullrequestreview-615449708,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALNZPK3XETEHLC4KGZYIPJLTEIEIJANCNFSM4ZKRERLA
.


Class that corresponds to each color

Hello,
@hangzhaomit thanks for the Pytorch implementation on ADE20K dataset!
I wonder if there is a way to know which classes correspond to each color in the .png image we get as a result. Would you be so kind to provide me with any information about it?
Thank you in advance

https://github.com/CSAILVision/semantic-segmentation-pytorch/blob/master/data/object150_info.csv
"idx"

Thanks @shlykov2! I can see, for example, that idx "1" corresponds to class "wall"... but how can i know the color in the image that corresponds to them?

load img with scipy imread (as i did, idk about other libraries) astype "uint8" and check values there. 1's, for instance, will stand for wall :) and etc

I load the img but I don't seem to understand how to use the mask in order to get the values I need. I am new to neural nets and matlab. Can you give me any other tips?

Hope this helps,
https://docs.google.com/spreadsheets/d/1se8YEtb2detS7OuPE86fXGyD269pMycAWe2mtKUj2W8/edit?usp=sharing

Yes great! That is exactly what I was looking for!
Thank you very much!

Hope this helps,
https://docs.google.com/spreadsheets/d/1se8YEtb2detS7OuPE86fXGyD269pMycAWe2mtKUj2W8/edit?usp=sharing

Thank you! Can I share this Google Doc with everyone?

Hope this helps,
https://docs.google.com/spreadsheets/d/1se8YEtb2detS7OuPE86fXGyD269pMycAWe2mtKUj2W8/edit?usp=sharing

Thank you! Can I share this Google Doc with everyone?

Yeah sure!
If you think it will be helpful to others, you can even update the repo with this Google Sheet.


[Event Request] Application “Tests-Data Exchange”, Codeunit 139157 "Invoice Premapping Tests"

[Event Request] Application “Tests-Data Exchange”, Codeunit 139157 "Invoice Premapping Tests"

Could you please insert an OnTestInitialize-Raiser at the beginning of the procedure Initialize?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


KAFKA-6054: Fix upgrade path from Kafka Streams v0.10.0

This is the port of #4746 (0.10.1), #4758 (0.10.2), #4761 (0.11.0), #4768 (1.0), and #4773 (1.11) to trunk`.

Note: 1.0 was the first branch that did contain upgrade system tests already -- I just added the new once -- we can consider to consolidate them in this PR already. LMKWYT.

If we decide to cleanup tests in 1.0/1.1, those changes need to be added to this branch, too. System tests: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1605/
Note: we cannot add upgrade tests for 1.1 yet, as 1.1 is not released yet. I have a branch ready and will open PR after 1.1 is released to add those missing tests.
This PR does not implement KIP-268 completely, but only port parameter upgrade.from -- for new metadata version 3 and "version probing" there will be a separate PR (#4636).
\cc @bbejeck @vvcephei

retest this please

Updated this PR and triggered system tests: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1660/
Note, this does only port the 1.1 branch PR but does not yet add new tests on purpose. Upgrading the metadata to version 3 will be a separate PR after this one is merged.

Rebasing broke the system tests. Pushed some fixed. Retriggered: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1664/


libinput: 1.9.4 -> 1.10.0

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/zx5s9rsk3jh7n9vlx7824chzd54fw3nd-libinput-1.10.0/bin/libinput -h got 0 exit code
ran /nix/store/zx5s9rsk3jh7n9vlx7824chzd54fw3nd-libinput-1.10.0/bin/libinput --help got 0 exit code
ran /nix/store/zx5s9rsk3jh7n9vlx7824chzd54fw3nd-libinput-1.10.0/bin/libinput --version and found version 1.10.0
found 1.10.0 with grep in /nix/store/zx5s9rsk3jh7n9vlx7824chzd54fw3nd-libinput-1.10.0
found 1.10.0 in filename of file in /nix/store/zx5s9rsk3jh7n9vlx7824chzd54fw3nd-libinput-1.10.0

cc "@codyopel @wkennington"

Success on aarch64-linux (full log)
Partial log (click to expand)
/nix/store/91lnssrna8lal9y4d56hlnryj3lqbn0g-libinput-1.10.0/libexec/libinput/libinput-measure-touch-size: interpreter directive changed from "/usr/bin/env python3" to "/nix/store/9yr86q335k2k5ccznfcxsw0dq11zrwsw-python3-3.6.4/bin/python3"
/nix/store/91lnssrna8lal9y4d56hlnryj3lqbn0g-libinput-1.10.0/libexec/libinput/libinput-measure-touchpad-pressure: interpreter directive changed from "/usr/bin/env python3" to "/nix/store/9yr86q335k2k5ccznfcxsw0dq11zrwsw-python3-3.6.4/bin/python3"
/nix/store/91lnssrna8lal9y4d56hlnryj3lqbn0g-libinput-1.10.0/libexec/libinput/libinput-measure-touchpad-tap: interpreter directive changed from "/usr/bin/python3" to "/nix/store/9yr86q335k2k5ccznfcxsw0dq11zrwsw-python3-3.6.4/bin/python3"
checking for references to /build in /nix/store/91lnssrna8lal9y4d56hlnryj3lqbn0g-libinput-1.10.0...
shrinking RPATHs of ELF executables and libraries in /nix/store/zan9az8qi7mi7w8wcf2dqxz136q8frfl-libinput-1.10.0-dev
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/zan9az8qi7mi7w8wcf2dqxz136q8frfl-libinput-1.10.0-dev/lib
patching script interpreter paths in /nix/store/zan9az8qi7mi7w8wcf2dqxz136q8frfl-libinput-1.10.0-dev
checking for references to /build in /nix/store/zan9az8qi7mi7w8wcf2dqxz136q8frfl-libinput-1.10.0-dev...
/nix/store/91lnssrna8lal9y4d56hlnryj3lqbn0g-libinput-1.10.0

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘libevdev-1.5.7’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/development/libraries/libevdev/default.nix:14 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Changelog: https://lists.freedesktop.org/archives/wayland-devel/2018-February/036957.html

Either Github is confused, or I am confused. There seems to be 27 commits associated with this PR. I don't see an obvious link between them so I'm assuming this is a mistake. I will push the original commit by hand to staging.

@obadz This branch was based on master but is targetted to staging. The 26 commits are commits that are not on staging.

@jtojnar, ah thanks. I'm glad I just pushed the one to staging then. cheers.


ByteTrack output doesn't contain all detection results

I used another detector to get detection results and augmented ByteTrack to use those at every frame instead of using ByteTrack's detector. However, the tracking output from ByteTrack doesn't reflect all of the detections that I supplied. Here is an example of 2 frames from ByteTrack:
1,4,1105,374,1138,474,40.86,-1,-1,-1
1,5,182,398,211,498,95.27,-1,-1,-1
2,5,181,401,210,498,90.31,-1,-1,-1
2,7,862,380,903,478,80.75,-1,-1,-1

And here are the detection results I supplied for frames 1 and 2 respectively
left,top,right,bottom,class,confidence
1105,374,1135,476,person,40.861221
1061,382,1087,466,person,45.817993
877,376,918,475,person,72.918678
179,398,215,498,person,95.273239
917,381,948,480,person,95.795319

left,top,right,bottom,class,confidence
820,377,854,473,person,66.302063
146,409,173,470,person,66.384544
857,381,901,479,person,80.749580
180,402,212,499,person,90.314484

As you can see, the BytTrack results only show 2 objects per frame but in the detection results I supplied, frame 1 has 5 objects and frame 2 has 4 objects.
What I essentially did was store all of the bounding boxes + confidence scores and from these detection results and input them into tracker.update() instead of outputs[0] (https://github.com/ifzhang/ByteTrack/blob/main/tools/demo_track.py#L191). Is there a reason why all of the detections are not being shown? Thanks for the help!

Have you solved this problem?

Similar issue.

Well, it is because only high score detection bbox can init new tracks, and if detection bbox's score is below the assigned threshold , it will be skipped. As the code indicate:
if (track->score < this->high_thresh)  // 0.6
continue;

Is there a fix for this? C++ Tracker does not track properly even with 0.9 confidence.


The domain of era:inCountry is unnecessarily restrictive

Currently the domain of era:inCountry is the union of VT and OP.
However, the actual use is broader.
1 | era:OperationalPoint
2 | geosparql:Feature
3 | wgs:SpatialThing
4 | era:VehicleType
Apart from that to allow for a higher interoperability and re-use, the era ontology should "learn" but not be coupled with the current dataset.
Suggestion: remove domain declaration and for orientation list in the note the typical expected domain classes, based on the current data set.

Fixed in #10


typescript inside .vue files

Nowhere in the Typescript support section of the documentation is described that you can use <script lang="ts"> inside .vue files when using typescript.
I think it would be good to add an example.

Thanks for the feedback @gonerodes! We definitely will be enhancing our TypeScript documentation especially with Vue 3 coming soon. I'll add this to the backlog since we're currently in the midst of a migration guide as well as prepping for Vue 3 doc release.


PHP Notice: A non well formed numeric value encountered

Minor issue:
[05-May-2023 09:58:45 UTC]
PHP Notice:  A non well formed numeric value encountered
in /var/www/html/site/assets/themes/fw-child/functions.php on line 1873

fixed - please review for correct formatting

Yes, it works!  Thank you so much @phil-evans!
Closing this resolved issue.


External Model Alias

Extends the Code's aliasing system to work in the ExternalModel as well, as required by the hybrid project.
This might be able to wait for dataobject-rework to be merged to devel.

Remaking merge request, hoping not to have to rebase.


Demo - Publish Artifacts

[x] Publish serverless-nextjs-router
[x] Publish microapps-publish
[x] Publish microapps-datalib
[ ] Publish CDK Construct

[x] NPM
[x] NuGet
[ ] PyPI
[ ] Maven

Maven and PyPi will be published later


4.0 beta

Resolves #217, resolves #210 (via middleware)
Todo:

Allow integrations to be installed, uninstalled and configured at runtime
Allow modules to be 'services' (that is, no I/O, only start/stop)
Add onload/unload module events - all ES6 code should extend EventEmitter so we get events by default.
Allow I/O interception (middleware). Also useful for services.
Gracefully handle non-existent integrations
Fix help https://github.com/concierge/help/pull/1
Fix admin https://github.com/concierge/admin/pull/1
Fix disable https://github.com/concierge/disable/pull/1
Fix lolphp https://github.com/concierge/lolphp/pull/1
Fix programmer https://github.com/concierge/programmer/pull/1
Fix pickup https://github.com/concierge/pickup/pull/1
Fix joke https://github.com/concierge/joke/pull/1
Fix insult https://github.com/concierge/insult/pull/1
Fix quote https://github.com/concierge/quote/commit/8a695888dea157964cfc6a2d25eb20811861a0a6
Update KPM https://github.com/concierge/kpm/pull/6
Documentation updates
Module unloading infinite loop when a failure occurs
Config as an unloadable service
Integration config migration

Wishlist:

Async module loading deferred to 4.1

Decoupled GUI
Async loading calls

Fixed:

Local files that could not be resolved would be installed via NPM
Loopback would not work unless using ES6 style integrations

@phillipadsmith @ParasDPain @Awarua- @p0358 if there are any additional changes you want made for the beta branch other than what is still TODO, now would be a good time to mention them.

My wishlist atm is just persistent heroku and a twitter listener....and I think both can be done with the current functionality in Concierge?

@mrkno Thank you for the ping and patience with my response. Finally had some time to dive back into this today. The list above looks great. Nothing to add at the moment.

@mrkno Maybe a bit late, but nice feature would be integration break detection. Last time facebook-chat-api likes to break oftenly and then Facebook bot just doesn't work after the error until Concierge is restarted. It could try to automatically reload integration instead. Or facebook integration alone could get something like that.

@phillipadsmith cool, just file an issue/create a further PR if you retrospectively think of anything.
@ParasDPain I'll see what I can do. No promises... I'm also slowly looking into the facebook-chat-api problem but it takes aaaaaggggeees to reproduce.

@mrkno Just mentioning, the documentation can be stylistically updated for the integration configurations to be consistent with the rest of the docs but if integrations will be moved into their own repos after this PR's merge, then these changes are not important.
Tutorials will be a good addition as well but I'd need this PR to be merged before I can accurately write them, so they are better off in their own PR.

@ParasDPain I was thinking of either redirecting the Wiki to the repo documentation (probably moving the KPM table to the KPM repo which makes sense) or the documentation in the repo to the Wiki. It would reduce the duplication.

@mrkno I fully agree. A common source will be easier to maintain as well. Keeping the docs within the source code allows quick offline access to the docs than keeping them in the Wiki.
And the KPM table will be within the kpm module's wiki? or within it's source code? It'll be difficult to update within the source code.
Speaking of modules, I noticed _FirstRun() within core/platform.js has hard-coded module links. It'd be great if they are loaded from a separate config file somewhere so it's easier to customize installs during deploys as well.

@ParasDPain a config file, or similar to the KPM table (some common but changeable online table which is referenced). You already require network access to be able to install the modules anyway so I don't see any harm pointing at an online table other than complexity.

@mrkno Fair enough but if the table is a config file, all new entries will generate a lot of PRs. Although, a JSON syntax definitely makes it easier to parse and maintain.

@ParasDPain there is now a means to override the default installs, as per https://github.com/concierge/Concierge/blob/a2fede44c300f4fd8b81fe104339b47fe64435f0/doc/DefaultCommands.md#custom-defaults

@mrkno Great! This will make managing the broken heroku build much more easier.


for the missing file of install.sh. When I use the commandline of wget to download the install.sh file, I got a 404 error. Is there anyone can help to resolve it?

Checklist before submitting an issue

[ ] This issue does not happen on Spoon.
If your issue happens on Spoon too, it originates from Spoon (not from webSpoon). Please look at Pentaho Community Forums, or seek help at Hitachi Vantara Community, or submit an issue at Pentaho JIRA).
[ ] I searched for existing issues at here and there.

Expected Behavior
Actual Behavior
Screenshots and error messages are helpful.
Steps to Reproduce the Problem

Specifications
Server
If deployed as a Docker container

Docker tag (e.g., hiromuhota/webspoon:<IP_ADDRESS>):

Else

OS (e.g., Mac OS X 10.12.6):
Java (e.g., Oracle JDK 8u151):
Servlet container (e.g., Apache Tomcat 8.5.20):
webSpoon (e.g., version: <IP_ADDRESS> or commitId: 0211d84b):

Client

OS (e.g., Mac OS X 10.12.6):
Browser (e.g., Google Chrome 64.0.3282.140):

Me too~

Hi, I also encountered this problem, but it was resolved by downgrading the version. Here is a working version I found during my research, hopefully it can help you。。。。
https://raw.githubusercontent.com/HiromuHota/webspoon-docker/<IP_ADDRESS>/install.sh


feat: Cart Empty Message component

This PR adds a CartEmptyMessage component.
It will render a Cart Empty message, with a button to Continue Shopping, when a user is viewing their cart with nothing in it.
Issue in the starterkit: https://github.com/reactioncommerce/reaction-next-starterkit/issues/138

@willopez addressed your notes, ready for another look

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Improve README: fix grammar

Signed-off-by: Soumya Ranjan Mohanty<EMAIL_ADDRESS>

Coverage remained the same at 34.361% when pulling e6fb34eba4baa64637be2feba8905609f134a2c9 on geekysrm:readme-fix into 9f0e6af3e7d98bdc7f9d74cded187aca9cbbb38f on OpenBazaar:master.

Thanks for the contribution, @geekysrm


Requesting a transfer fails if no accounts with active key are present

Solved in https://github.com/MattyIce/steem-keychain/commit/6458f040926469bef6e5407981a9efac1aa1fca1


Data quality rule joining multiple data sources.

Is your feature request related to a problem? Please describe.
If I have two different data service e.g. 2 Postgres DBs is it possible to have a data quality test case or rule that checks the relation between fields of these two DBs. E.g. Value of column X in table 1 of service A should not exceed Value of column Y in table 2 of service B. The sources could be diverse as well. E.g. Postgres joined with Kafka.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
I may have to create a datasource using something like Presto that joins multiple data sources, and create such a rule on it. But since Presto may not support some data sources like Db2 properly, this may not work.
Another option is dbt, but that is an overkill if the data quality rule joining two sources, that I want, is fairly simple - which will mostly be the case.
Additional context
Thanks. The context here is that we are looking to keep all our data quality rules central. Easier to govern and spot if any group or service deviated from the overarching business rule. Or broke a pattern.

@upenbendre you can build a sql query to compare this right? We already have support for custom sql test

I haven't found documentation on how to create a custom sql test

Looking for documentation on how to create a custom SQL test that joins multiple data sources

I got a "Page not Found" on https://docs.open-metadata.org/openmetadata/ingestion/workflows/data-quality/tests#table-custom-sql-test

@upenbendre the link has moved. Here it is 👉 https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality/tests#table-custom-sql-test


Fix get_drag_data not overridable in some Controls

Fixes #75118

This still doesn't make them fully overridable. Does it make sense to enforce the default behavior of the control over the user-defined behavior?

This still doesn't make them fully overridable. Does it make sense to enforce the default behavior of the control over the user-defined behavior?

Default Control method is calling Callable set by set_drag_forwarding or script virtual method, so it should be overridable.

Yes, but that only happens if the C++ override doesn't return before that. I.e. in RTL if selection.drag_attempt && selection.enabled, then user overrides are never reached.

Could be something like this I guess
https://github.com/godotengine/godot/blob/161d028ae89acb578cfcd4f29bfe9ac205459e8b/scene/gui/text_edit.cpp#L3049-L3056

That makes sense to me. Do you plan to make this change? I'm not insisting on either way, just want it to be a clear decision that we understand. It can also be valid that these internal triggers for dragging should always take priority.

Yeah I'll change it.

Thanks!

Cherry-picked for 4.0.2.

Label still not calling _get_drag_data.

Change mouse_filter to something different than Ignore.


SUBMARINE-887. Fix some front-end apperance

What is this PR for?

notebook table modify to sync with other pages
the color of the first row of experiment table
delete redundant description in each page.
Some title with each page.

What type of PR is it?
[Improvement]
Todos
What is the Jira issue?
https://issues.apache.org/jira/projects/SUBMARINE/issues/SUBMARINE-887
How should this be tested?
cd submarine-workbench/workbench-web
npm install
npm start

Screenshots (if appropriate)

notebook table

experiment table

remove description(Template as example)

New appearance of Manager pages

Questions:

Do the license files need updating? No
Are there breaking changes for older versions? No
Does this need new documentation? No

@kevin85421


Custom metric namespace name missing

I'm trying to create custom metrics with custom namespaces, but the custom namespace names are not shown on Azure portal - Application Insights - Metrics tab. In the screenshot you can see 3 different custom namespaces, though their names are missing.

Here is the line which sends the metric values via TelemetryClient:
telemetryClient.GetMetric(new MetricIdentifier("MyNamespace", "MetricName")).TrackValue(new Random().Next(1, 5));
Could you please help me what am I doing wrong, or let me know if this is a bug. Thank you in advance.

Hello, can you please provide two things:

what's your SDK version?
Can you please provide us the json object that's being sent from your application? You can capture this from the console output of Visual Studio while debugging, or using a tool like Fiddler. We want to see what was sent to our ingestion to identify is this an ingestion/parsing bug or did the sdk fail to send the custom metric name. You'll want to remove your ikey from your json before sharing.

Please, let me know if you any other questions.

Hello, thanks for your answer.
My Microsoft.ApplicationInsights version is 2.13.1.
Here is the JSON sent (namespace is included):
{
   "name":"Microsoft.ApplicationInsights.xxx.Metric",
   "time":"2020-02-28T10:33:01.0000000Z",
   "iKey":"xxx",
   "tags":{
      "ai.cloud.roleInstance":"DESKTOP-xxx",
      "ai.internal.sdkVersion":"m-agg2:2.13.1-12554"
   },
   "data":{
      "baseType":"MetricData",
      "baseData":{
         "ver":2,
         "metrics":[
            {
               "ns":"MyNamespace",
               "name":"MetricName",
               "kind":"Aggregation",
               "value":1,
               "count":1,
               "min":1,
               "max":1,
               "stdDev":0
            }
         ],
         "properties":{
            "_MS.AggregationIntervalMs":"60000"
         }
      }
   }
}

Surprisingly, today when I checked on Azure Portal, the metric namespace names are shown magically, although I didn't change anything on our side. Was something fixed on your side?

Thanks again.

Based on this I don't think there was an SDK bug, and you're on the latest version of our SDK. :)
Our UX team has daily deployments so it's possible that they broke something and then rapidly fixed it. To be honest, I wouldn't know.
I'm sorry you were affected, but I'm happy to hear your issue has been resolved!
I'm going to go ahead and close this issue, but if you have additional questions please don't hesitate to reach out.


coin.rotate bugs...

This means losing the account. right?

Hey - this isn't a Pact issue. But, to answer your question, yes, this does mean the account will be unrecoverable.

This is an issue for the coin contract in chainweb.


Improve the pointer size checking

When using the or-tools in a new Xcode project, there is a compilation error for the size of the pointer. In constraint_solveri.h
inline uint64 Hash1(void* const ptr) {
#if defined(ARCH_K8) || defined(__powerpc64__) || defined(__aarch64__)
  return Hash1(reinterpret_cast<uint64>(ptr));
#else
  return Hash1(reinterpret_cast<uint32>(ptr));
#endif
}

None of the macros are defined in clang. The checking from platform_macros.h in the Protobuf is better. I tried to build from the source to check the macros but the cmake settings were quite messy on OS X. I could not finish the build even after multiple patches.

I pushed a fix for that.
Thanks for the suggestion.


Multi page invite flow

[x] fix copy with newer one
[x] fix tests
[x] style full name box
[ ] add some progress indicator?
[ ] don't allow submit if you already have an account
[x] think about ux for checkboxes on mobile, too easy to accidentally hit links
[x] reduce margin below preview text
[ ] ensure submitting works
[ ] provide some feedback if it fails
[ ] ensure redirect does happen on success
[ ] ensure redirect makes sense in terms of UX

Desktop gif

Mobile gif

@markulrich  This works except the checkboxes look weird on safari/mobile safari

@osdiab is it better than what we have no? lez land!!

ah running into some 403 issues on submit, fixing that. Also i fixed the checkbox sizes

For some reason logging in on request invite page doesn't seem to work on desktop safari incognito. checking mobile sfari


make scheme level access control on csv optional

This PR makes the schema level access control implemented here (https://github.com/apache/incubator-superset/pull/5787) configurable.
@mistercrunch @youngyjd @john-bodley

If you don't want to have the access control, you can  just leave the list empty
https://github.com/apache/incubator-superset/blob/e72e1ec7b5cf069e4bc2d2a1b05f626ba279f320/superset/forms.py#L65

Codecov Report

Merging #6206 into master will decrease coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #6206      +/-   ##
==========================================
- Coverage   76.91%   76.86%   -0.06%
==========================================
  Files          47       47
  Lines        9393     9396       +3
==========================================
- Hits         7225     7222       -3
- Misses       2168     2174       +6

Impacted Files
Coverage Δ

superset/config.py
92.42% <100%> (+0.05%)
:arrow_up:

superset/forms.py
82.53% <100%> (-9.27%)
:arrow_down:

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 dcf048c...e72e1ec. Read the comment docs.

@youngyjd Our deployment overrides the security manager and doesn't have schema level permissions so this goes against the grain. Let's leave your changes on by default but still make it optional.

I discussed this more with teammates and you're right. We will make this change internally without making the open source code too messy.


vendor: Fix reqrsp_interface dependency

Fixes issue where bender fails to find correct path for the reqrsp_interface ip.

Thanks @fischeti! Looks good, I think we should merge even though the Banshee build seems to fail conistenly.