Word wrap or horizontal scroll in result

I have problem that I couldn't read entire error log in result tab
I saw download options, it's absolutely helpful to send entire error file for debugging to other teammates.
But I think it would be nicer if it has word wrap feature or at least a horizontal scroll to help us read without downloading the error json first.
Thank You!

Thanks for reporting this issue. The linewrapping extension is missing. I'll add that for the next version.

Fixed in v4.5.1


Create worker subdirectory for worker docker image

fixed #3

@davemasselink Thank you for pointing this out. I updated my branch.


Unable to store Japanese text in Qdrant on Windows environment

While I can successfully store and retrieve English and other Latin-based characters, I encounter timeout errors when trying to store Japanese text. After investigating the issue, it appears that character encoding problems are causing the program to hang.

The issue can be resolved by configuring the PYTHONIOENCODING environment variable in the MCP server settings.
{
  "qdrant": {
    "command": "uvx",
    "args": [
      "mcp-server-qdrant",
      "--qdrant-url",
      "http://localhost:6333",
      "--qdrant-api-key",
      "your_api_key",
      "--collection-name",
      "your_collection_name"
    ],
    "env": {
        "PYTHONIOENCODING": "utf-8"
    }
  }
}

@panda666x Thanks for providing the answer! Could you please describe your env? At least the OS would be helpful. I'd love to reproduce it!

OS is Windows 11. Also, this might be a Japan-specific issue. In Japan, the default character encoding of the OS appears to be Shift-JIS.


Web App update method is not updating resource configuration

Package Name:  @azure/arm-appservice
Package Version:  15.0.0
Operating system:  macOS Sonoma Version 14.5
[x] nodejs

version:  20.14.0

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://learn.microsoft.com

Describe the bug
I have an Azure Web App where I am using the following code to get the Web App configuration
const { WebSiteManagementClient } = require("@azure/arm-appservice");
const { DefaultAzureCredential } = require("@azure/identity");
const util = require("util");

async function main() {
  const subscriptionId = "<subscription_id>";
  const client = new WebSiteManagementClient(new DefaultAzureCredential(), subscriptionId);

  let webAppConfiguration = await client.webApps.getConfiguration("<resource_group>", "<web_app_name>");
  console.log(util.inspect(webAppConfiguration, { depth: null }));
}
main();

In the webAppConfiguration, I see that my ftpsState field value is disabled.
Now I am trying to use the following code to update the Web App configuration
const { WebSiteManagementClient } = require("@azure/arm-appservice");
const { DefaultAzureCredential } = require("@azure/identity");
const util = require("util");

async function main() {
  const subscriptionId = "<subscription_id>";
  const client = new WebSiteManagementClient(new DefaultAzureCredential(), subscriptionId);

  await client.webApps.update("<resource_group>", "<web_app_name>", {
    siteConfig: { ftpsState: "Disabled" },
  });

  let webAppConfiguration = await client.webApps.getConfiguration("<resource_group>", "<web_app_name>");
  console.log(util.inspect(webAppConfiguration, { depth: null }));
}
main();

After updating the configuration and checking the output I still see that in the webAppConfiguration object ftpsState value is still set to disabled.
To Reproduce
Steps to reproduce the behavior:
1.
Expected behavior
I expected the webApps.update function to update the Web App configuration with the value Disabled for the ftpsState field. Instead, I see the value is still set to disabled.
Screenshots

Additional context
When I first tried to update the configuration of the Web App I called the update method with the following
{
    siteConfig: { ftpsState: "disabled" }
}

I later realized the allowed value was Disabled instead of disabled.

will check

@sdsubhajitdas , appservice has a api named updateConfiguration(),
could you use that? I think client.webApps.update() may not work for configuration.
as when I called webApps.get(), the ftpsState from the result is null, but I calledwebApps.getConfiguration(), the ftpsState  is disabled.
here is my code to test:
const result=await client.webApps.getConfiguration(resourceGroupName,"czwapp");
    console.log(result.ftpsState);
    const res=await client.webApps.update(resourceGroupName,"czwapp",
      {
        siteConfig:{ftpsState: "AllAllowed"}
      }
    );
    console.log(res.siteConfig?.ftpsState)

    const res1=await client.webApps.updateConfiguration(resourceGroupName,"czwapp",
      {
        ftpsState: "Disabled"
      }
    )
    console.log(res1.ftpsState)

and the result is :
disabled
null
Disabled

Thanks for the response @kazrael2119 .
I tried the updateConfiguration API and yes it works.
From your testing code, I can see that you are transitioning from AllAllowed -> Disabled, which also works for me.
But I am trying to transition from disabled -> Disabled state.

Thanks for the response @kazrael2119 . I tried the updateConfiguration API and yes it works. From your testing code, I can see that you are transitioning from AllAllowed -> Disabled, which also works for me. But I am trying to transition from disabled -> Disabled state.

you can ignore
const res=await client.webApps.update(resourceGroupName,"czwapp",
      {
        siteConfig:{ftpsState: "AllAllowed"}
      }
    );

this one as this is tell you that webapp.update() doesn't work.

@kazrael2119
Here is my code to test
  const client = new WebSiteManagementClient(new DefaultAzureCredential(), subscriptionId);

  let webAppConfiguration = await client.webApps.getConfiguration(resourceGroup, webAppName);
  console.log("Web App Configuration Before Update");
  console.log(webAppConfiguration.ftpsState);

  console.log("Updating configuration...");
  let result = await client.webApps.updateConfiguration(resourceGroup, webAppName, {
    ftpsState: "Disabled"
  });
  console.log(result.ftpsState);

  webAppConfiguration = await client.webApps.getConfiguration(resourceGroup, webAppName);
  console.log("Web App Configuration After Update");
  console.log(webAppConfiguration.ftpsState);

and the output for the following
Web App Configuration Before Update
disabled
Updating configuration...
disabled
Web App Configuration After Update
disabled

I tried to debug this case and I found that the request body is Disabled but the response is still diasbled. I think this should be a service issue.
Normally, on portal we can select three value for ftps states:

but when I updated the status as disabled, this value is null on portal：

I guess in The server side does not distinguish between uppercase and lowercase, but supports the use of lowercase if using sdks

Add Service attention for awareness

@sdsubhajitdas since this is a service backend issue, could you open a support ticket to get better support from them directly https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request, thank you.


nvcc fatal: Unsupported gpu architecture 'compute_30'

Bug Description
nvcc fatal   : Unsupported gpu architecture 'compute_30'
How can I pass compute_61 as nvcc flag which should be supported by my card GTX 1050
Reproduction Steps
[Steps to reproduce. Please include, if needed for your issue:

Any configurations or custom setup
master branch
Commands to run
cmake .. -DCMAKE_BUILD_TYPE=Release -DFL_BACKEND=CUDA -DFL_BUILD_DISTRIBUTED=ON -DFL_BUILD_CONTRIB=OFF -DFL_BUILD_TESTS=OFF -DFL_BUILD_EXAMPLES=OFF -DFL_LIBRARIES_USE_MKL=OFF
make -j4
make install

Error
[  1%] Building NVCC (Device) object CMakeFiles/fl-libraries-cuda.dir/lib/sequence/criterion/cuda/fl-libraries-cuda_generated_ViterbiPath.cu.o nvcc fatal   : Unsupported gpu architecture 'compute_30' CMake Error at fl-libraries-cuda_generated_ViterbiPath.cu.o.Release.cmake:220 (message):   Error generating   /home/fb/flashlight/build/CMakeFiles/fl-libraries-cuda.dir/lib/sequence/criterion/cuda/./fl-libraries-cuda_generated_ViterbiPath.cu.o
Platform and Hardware
Ubuntu 20.2
GeForce GTX 1050 (455.23.05)
CUDA: 11.1
NVCC: 11.1.74
Cmake: 3.16.3

It's an issue because of CUDA 11. Look here
I need to make the MR with changes.

@alealv would be happy if you prepare the PR with all your fixes/findings on this.

This should be fixed in the aforementioned commits. Feel free to reopen if you're still having problems with CUDA compute versions.


Deprecate redux-immutablejs in favour of redux-immutable

Deprecate for reasons outlined in https://github.com/gajus/redux-immutable/issues/12#issuecomment-176189454

Any reason why you don't want to export combineReducers as a drop-in replacement? I understand the desire for flexibility but it would be nice to have createCombineReducers({ debug: process.env.NODE_ENV !== 'production' }) as the default.

@gaearon Redux implementation of combineReducers uses process.env.NODE_ENV to enable/ disable debug mode. It is only my opinion, but third-party libraries should not rely on environment variables to control their behaviour, e.g. in our deployment process we are using production-{name of the server} NODE_ENV value to make different builds. This unintentionally included "development" build of Redux in the production bundle. To avoid this, library/function behaviour must be controlled only through the public API.
I did not want to change Redux combineReducers API (I could have had options as the second parameter of the function). Therefore, a sound compromise was to have a function that would build combineReducers with preset "debug" behaviour.
I would advise redux to either take a similar approach or update combineReducers ARI to avoid earlier described pitfall.

I can of course export combineReducers in addition to createCombineReducers with preset debug value (as you suggested), but that would be of little value to people since they would still need to import createCombineReducers to differentiate between development and production builds.

I would advise redux to either take a similar approach or update combineReducers API to avoid earlier described pitfall.

If you see this as a worthy discussion, I will open a GitHub issue.

@gaearon Redux implementation of combineReducers uses process.env.NODE_ENV to enable/ disable debug mode. It is only my opinion, but third-party libraries should not rely on environment variables to control their behaviour, e.g. in our deployment process we are using production-{name of the server} NODE_ENV value to make different builds.

I agree in principle but this is an established convention in the React ecosystem. Redux just tries to be a good citizen here. If you're not envifying React, you'll have quite slow builds, so all we do is follow the same convention as React, and if you want to skip that, you can just use pre-envified UMD builds. I think libraries complementary to Redux (at least those we officially recommend) should stick to the same conventions as Redux.

in our deployment process we are using production-{name of the server} NODE_ENV value to make different builds.

Since React and Redux and React-Redux and a ton of other libraries in React ecosystem already use NODE_ENV for that, maybe you could just use a different env variable name?

Published<EMAIL_ADDRESS>implementing the discussed changes.

Thanks for cooperation :+1:
I know that existing conventions often aren't the best but it's better to avoid fragmenting community over this.

Just working for the better tomorrow. : )


youtube-dl wrongly claims extended attributes are not supported when setxattr() returns ENOSPC

On an ext4 filesystem:
$ > x; setfattr -n user.test -v 123 x; getfattr -d x; rm x
# file: x
user.test="123"

$ youtube-dl -v --xattrs 3TR_YuDFIFI
…
[metadata] Writing metadata to file's xattrs
ERROR: This filesystem doesn't support extended attributes. (You may have to enable them in your /etc/fstab)
Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/youtube_dl/postprocessor/xattrpp.py", line 120, in run
    write_xattr(filename, xattrname, byte_value)
  File "/usr/lib/python3.4/site-packages/youtube_dl/postprocessor/xattrpp.py", line 54, in write_xattr
    return xattr.setxattr(path, key, value)
OSError: [Errno 28] No space left on device

And I wish youtube-dl treated this as a warning anyway, or provided a way to slim down the metadata stored. The only xattr I actually care for is user.xdg.referrer.url (the original URL); the rest (usually) already fits inside regular media tags.

Thanks for the report. Now a warning instead of an error is issued in this case.


Create a Cleanup Event [WIP]

Description:
A user (soon to be an organizer of the event) should be able to create a cleanup event in an area. They can choose a square? are on the map and choose what time and day the event should take place.
Schema:
{
??? collection of event-statuses?
}

progress on #5 PR

Closing: PR #9 #12


[FLINK-26723][runtime]fix the error message thrown by SourceCoordinatorContext

What is the purpose of the change
fix the error message thrown by SourceCoordinatorContext
Brief change log

fix the error message SourceCoordinatorContext
provide more message for test in SourceCoordinatorContextTest

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot  run azure

Gentle ping @becketqin, could you help me to review this pr in your spare time ?

@flinkbot run azure

LGTM. The CI failure should be irrelevant to this PR.

Merged to master: da79677c9afcd6703ee5cd513740981530916f2f
Cherry-picked to

release-1.15: e3992ab17a4515076c287b8d12003e1449718df1
release-1.14: 36136bc2bc33f0dc0add1303af949f681a7e42cd


added a new divide & conquer algorithm

Related Issue

issue number : #171

Proposed Changes
added a exponent calculation algorithm using divide & conquer
Additional Info

Checklist

[x] ✅ My code follows the code style of this project.
[ ] 📝 My change requires a change to the README.
[ ] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

integer,integer
-ve integer,integer

Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
///----------------------PR README --------------------///
You need to follow particular guidelines for your README , please follow
these guidelines click here
also you can see how your README should look like see here
for more please go through these here

This looks good to me, @n4i9kita  kindly have a look before moving it to admin


[Performance] v3.3 out of box performance comparison

对比Starrocks3.3，以及doris2.1版本，很多SQL的盲查速度是落后于doris的，能否提高一下速度呢

Is the performance of doris2.1 really that much better? Has anyone done an in-depth performance comparison test between doris2.1 and starrocks?

v3.3.0 shared shorage for StarRocks?


PayloadTooLargeError: request entity too large

Current Behavior
too many flows and deployment is no longer possible
Expected Behavior
I would like to be able to program a significantly larger number of flows
Steps To Reproduce
Create a large number of flows.
How can I increase the flow size monitoring?
Example flow
node-red: PayloadTooLargeError: request entity too large
node-red:     at readStream (/usr/local/addons/redmatic/lib/node_modules/body-parser/node_modules/raw-body/index.js:163:17)
node-red:     at getRawBody (/usr/local/addons/redmatic/lib/node_modules/body-parser/node_modules/raw-body/index.js:116:12)
node-red:     at read (/usr/local/addons/redmatic/lib/node_modules/body-parser/lib/read.js:79:3)
node-red:     at jsonParser (/usr/local/addons/redmatic/lib/node_modules/body-parser/lib/types/json.js:138:5)
node-red:     at Layer.handle [as handle_request] (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/layer.js:95:5)
node-red:     at trim_prefix (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:328:13)
node-red:     at /usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:286:9
node-red:     at Function.process_params (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:346:12)
node-red:     at next (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:280:10)
node-red:     at cors (/usr/local/addons/redmatic/lib/node_modules/cors/lib/index.js:188:7)
node-red:     at /usr/local/addons/redmatic/lib/node_modules/cors/lib/index.js:224:17
node-red:     at originCallback (/usr/local/addons/redmatic/lib/node_modules/cors/lib/index.js:214:15)
node-red:     at /usr/local/addons/redmatic/lib/node_modules/cors/lib/index.js:219:13
node-red:     at optionsCallback (/usr/local/addons/redmatic/lib/node_modules/cors/lib/index.js:199:9)
node-red:     at corsMiddleware (/usr/local/addons/redmatic/lib/node_modules/cors/lib/index.js:204:7)
node-red:     at Layer.handle [as handle_request] (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/layer.js:95:5)
node-red:     at trim_prefix (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:328:13)
node-red:     at /usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:286:9
node-red:     at Function.process_params (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:346:12)
node-red:     at next (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/index.js:280:10)
node-red:     at expressInit (/usr/local/addons/redmatic/lib/node_modules/express/lib/middleware/init.js:40:5)
node-red:     at Layer.handle [as handle_request] (/usr/local/addons/redmatic/lib/node_modules/express/lib/router/layer.js:95:5)

Environment

Node-RED version: V4.0.5
Node.js version: V20.11.1
npm version: V10.2.4
Platform/OS: Raspberrymatic
Browser: Google Chrome

The default payload max is 5mb, you can increase this in the settings.js using the apiMaxLength field

Thank you so much, that helped me a lot!
Merry Christmas


CertRenewal: Port Trust v1 request handler to Trust v2

Given the AS attributes introduced by https://github.com/Anapaya/scion/issues/1762, if the CS is in an Issuing AS, the handler should run the normal issuance logic. Otherwise, it should return an error to the client saying it is not an issuing AS.

Once the spec is in, we can implement server side support for it on top of capnp messages.

This is closed in favor of efforts of translating the current certificates to x509 certificates.


The install generator generates a coffeescript root file, but Sprockets 4 doesn't seem to support that anymore.

https://github.com/rails/sprockets/issues/273#issuecomment-206415863
Looks like we'll need to update the install generator to not generate a spec_helper.coffee, and instead generate a spec_helper.js.
#473

We can now close this with the advent of #478.


InfluxDB Enterprise 1.9.7 release notes

https://dl.influxdata.com/enterprise/nightlies/master/CHANGELOG.md
https://docs.influxdata.com/enterprise_influxdb/v1.9/about-the-project/release-notes-changelog/
cc @samhld

@kelseiv This is a dupe of https://github.com/influxdata/docs-v2/issues/3928, right?

Closes https://github.com/influxdata/docs-v2/issues/3928
Features

Expose passive nodes feature to influxd-ctl and the API. Notes for docs: https://github.com/influxdata/docs-v2/issues/3794
Throttle inter-node data replication, both incoming writes and hinted hand-off, when errors are encountered (for docs, this pertains to https://github.com/influxdata/plutonium/issues/3790)
Update Flux to 0.161.0

Add http/requests package!
Add isType()
Add display()
Function enhancements: increase(), sort(), derivative(), union(), timeshift(), vectorization to applicable functions (i.e. map())
Continue performance work (i.e., sort-> limit)
Add TCP connection pooling to mqtt.publish() when called in map()

Maintenance updates

Update Go to 1.17.9
Update Flux to 0.161.0

Bug fixes
Error messaging

Improve error messaging for max series per database exceeded error
Add info to error creating subscription

Miscellaneous

Fix race condition causing restore command to fail

@kelseiv @lwandzura for review

@davidby-influx can you review the above comment for any omissions, to go out for release notes?

We are also going get fixes for
https://github.com/influxdata/EAR/issues/3193 (gating fix for 1.9.7 GA)
https://github.com/influxdata/plutonium/pull/3805

Thanks, @davidby-influx  -- added!

@samhld wasn't "Drop shard should ignore shard not found errors" fixed in 1.9.6?  Is this an additional update?

@lwandzura that's very weird. It looks like that incorrectly went into 1.9.6. Any idea how that's even possible? Did 1.9.6 tell the future? That commit is not in the commit log for that version.

it is weird....but miscommunications do happen sometimes

@lwandzura of course! I'm actually just curious how 1.9.6 was able to tell the future :)

@samhld can you add any detail around this bullet point?  do you mean we are continuing to improve flux functions in general or how they work within Enterprise?
Continue performance work (i.e., sort-> limit)

@lwandzura

do you mean we are continuing to improve flux functions in general or how they work within Enterprise?

It's both. Flux gets upgrades in each of these versions and that often comes with features or optimizations. Flux function improvements are not only that but also improvements to Enterprise...because it's part of it.


Refactor database seeding and CustomWebApplicationFactory

Errors in the Tests were fixed.
Tests are executed and passed correctly

Thanks!


build breaks for camus-kafka-coders

When building camus-kafka-coders it breaks with a missing dependencies to:
io.confluent:kafka-avro-serializer:jar:1.0
and
io.confluent:kafka-schema-registry-client:1.0
Where can I find this code?
-M

There is also a dependency issue with:
org.apache.kafka:kafka_2.10:jar:<IP_ADDRESS>-cp
Where do we find this -cp version of Kafka?
-M

Thanks for catching this @pehrs. Fixed in ee1916140b. I noticed this issue and fixed it on our development branch. We just omitted the new packages.confluent.io repository when generating the final version, which you generally wouldn't notice is missing if you're building the whole stack since all the other packages would already be in your local repository.
Right now that patch is on the 1.x branch, so you'll want to check out that branch. However, it's all still tagged as 1.0 so you won't be getting snapshot builds.

@ewencp but where is the source code for these components and where is the fork for the (I assume patched) kafka (<IP_ADDRESS>-cp)?

@pehrs Ah, sorry, didn't realize you were looking for the source as well. The kafka-avro-serializer and kafka-schema-registry-client modules are both included in our schema-registry repository. (We keep these all together since the serializers are one of the few direct users of the kafka-schema-registry-client library and we can share a bit of code between the client and schema registry server).
The <IP_ADDRESS>-cp release doesn't contain anything proprietary, so we haven't even started maintaining a separate repository. We tag it with the extra -cp for two reasons. First, we don't want to conflict with the version numbers for the Apache releases that are pushed to Central, but still be able to use the same version numbers when our releases are closely aligned. Second, we will sometimes release slightly different versions. In this case, our <IP_ADDRESS>-cp is built from 5f3eb1cafaece, which has a few patches that were checked in that will make it into Apache's <IP_ADDRESS>. Let me look into providing a copy of the repository -- we might as well have clearly tagged releases so you can easily find out exactly what's in the release.

@ewencp Thanks for clearing this up :-)


can't make dense vector tiles

I'm trying to generate vector tiles that include all the polls in Vancouver, BC.  (Polls are small electoral districts -- precincts in US terms -- and are usually a few blocks in size.)  I can generate them in rural areas in Canada, but other urban areas fail as well.  My guess is that there is too much data being included in a single tile, but I'm not sure.  I've tried increasing shape simplification or turning it off entirely to no avail.  It seems to fail after the database query to find the shapes is complete, since it hangs but there are no running queries on my database.  If you want a dump of the problematic data and a tile address that fails, I'm happy to provide it.
Thanks!

You might try turning tiny "polls" into point geometries (but keeping the big ones as polygons)?

There are polls that are just one apartment building, but most are a few blocks.  The ones that are a single apartment building have a cut-out from another poll.  If that is indeed the problem, we could potentially drop polls that are below a certain square mileage and merge them into adjacent or surrounding polls; we'd then need to use different shapes at different zoom levels.  Can tile generation even handle that?  I would expect simplification supposed to handle the shapes of polls.  Why is it crashing on complex polygon data?

Do you eventually get an error with a stack trace? Or does data eventually come through? If it's just hanging, you might want to profile it a little bit to pinpoint where the slow part is.

Data never comes through, and the tile is never returned.  If it did, it would be cached on S3, so there would be no problem requesting the tile another time.
I tried upping our logs from info to debug, and I don't see anything useful.
Where/how do you recommend I put in profiling?

I'd try something simple first. If you can reproduce it locally, you can just step through the provider that generates the data to see what statement it hangs on. Or you could add in your own logging statements in the provider to see how far it gets.

I don't know where it actually fails in the code, but I know what sort of shapes cause it now.  It's caused by tiny shapes.
In Canada, their polling districts may be a few city blocks in urban areas.  But when they have a big apartment building, it's a polling district all to itself.  Its shape is cut out from the surrounding one, but it's land mass is tiny.  The biggest such polling district is 0.05 square miles, and the smallest is  0.00005 sq miles.  I don't know where it that range things start to break, but removing those tiny districts solves the problem and allows the vector tiles to be generated.  I don't need to do anything to change the districts these polls are cut out from.
I suspect there's a division by 0 problem.

Which tile format are you requesting? Sometimes problems that manifest in MVT or GeoJSON work in TopoJSON for instance.

This is only a problem for mvt tiles.
I also generate image and utf grid tiles from these shapes, and those have no problems with the tiny shapes.

Can you try for another vector format like TopoJSON or GeoJSON?

Both of those seem to work fine.  It's an MVT problem.  And I need MVT tiles.

Are you pre-simplifying geometry in PostGIS as part of the queries, depending on the zoom? Is there a link to a config file &/or data files?

I can email problematic data somewhere or post it somewhere public.  It's currently just in my db.
We aren't doing any pre-simplification.  We do ensure validity and change the projection when we load districts originally, but that's it.

Is it during the mvt encoding that it actually fails? Can you create a small test case from your data that reproduces the problem?

I'm 95% sure this data set will fail.  It's hard for me to run it with this limited set to confirm.  It's very likely probably due to the smallest polls.
problematic_for_vector_tiles.zip

Were you able to see it fail with this dataset?  Or where are we on this?

Can you provide a GeoJSON tile (tile coordinate and raw JSON output as an attached file) that is working so we can figure out why MVT is failing?
It could be the problem is in this old TileStache configuration, which we don't currently use in production and don't currently support. We now recommend using our tileserver to serve the tiles. Does using that config fix this problem?

Hi - taking over for Julie while she is on vacation.  We've pinned this down to a load problem instead of a hard failure.  Generating the MVTs for this dataset is MUCH more processor-intensive than generating GeoJSON.  Run one-at-a-time, we can get the MVTs to generate but it takes 30-60 seconds for each one (on an otherwise unused AWS t2.large).  So rendering an entire map pegs the CPU and locks up the whole server.
The same GeoJSON tiles generate just fine... hardly any CPU bump at all.  Unfortunately, switching to JSON isn't an option for us (MapboxGL does not support Tiled GeoJSON).
Any idea why MVTs take so much more CPU?

Thanks for the additional information.
Can you provide a GeoJSON tile (tile coordinate and raw JSON output as an attached file) that is working so we can figure out why MVT is failing?

350.zip

Cool, thanks. We'll have a look at it tomorrow morning (EST / London time). Do you have a publish deadline you're working against?

Thanks for asking.  While we'd love to get it fixed within a week, our hard deadline is 2-3 weeks.

I wrote a small program to transcode GeoJSON to MVT, and got an MVT tile which was 53,291 bytes long rather than 57,749 as expected. And took only 0.9s rather than the expected 30-60s. I wonder if we might be using different versions of that library?
@peckjon, it would be really helpful if you could try out the small program above - it should take the GeoJSON as input like this: time python test.py 350.json and let us know if that's also slow, please? It would also be helpful to know what version of the mapnik_vector_tile module is installed. Thanks!

There have been some performance optimizations made relatively recently, in particular of the encoding of properties. If you're not already using the latest mapbox-vector-tile version, I suggest trying the latest to release to see if it speeds it up.

Thanks, @rmarianski -- with the latest version it pegs the CPU but does not deadlock, which is sufficient for us... we can simply restart the requests for the uncached tiles after the CPU settles down.

Great to hear, would love to see your map when it's published.


[Feature]: There should be an option to resize image inside Table widget

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
We should be able to set the height and width of the image inside table widget
Why should this be worked on?
The ability to provide height and width to images inside the table will give the images more visibility.

@aswathkk this can be implemented once we figure out the dynamic height of row in the new table widget
cc @riodeuno

@aswathkk Can you provide an example where this would be useful?

@aswathkk @dilippitchika @somangshu Can you provide an example where this would be useful?

@momcilo-appsmith In this table, it's hard to see the image properly since it is small. The maximum height possible for an image inside the table is 28px.

@momcilo-appsmith this is a good issue to pick up for design, if you have used word-wrapped table which Balaji created with images you can see how this behaves today after updates.

Stats

Stat
Values

Reach
220

Effort (months)
0.75

The way I am thinking to go about this is to either:

Have a set of defined values for the width or
Have a custom width field

@momcilo-appsmith should this also involve a max-width baed on the table cell dimension?

@somangshu At first I thought that it shouldn't because of cell wrap, but then you won't be able to define width if you don't.
I think the answer to your questions is NO.

Yeah, i also thought the same that we give default sizes for the images like Small, medium, Large and in the JS option user can define the height of image in px if they wish to.
The challenges i see are

Each image can be of different dimension, so having a fixed set of values may cause some other problems like another column getting wrapped.
Defining the default sizes themselves

@dilippitchika I think letting them choose from one of the sizes we set is the way to go. Is there a way we can enable people to zoom in the picture?

We can i guess, but it has to happen in a popover like scenario. @momcilo-appsmith can you assign someone to research and create a design brief for this problem?

@dilippitchika

Design: https://www.figma.com/file/nTMtrnQJUsso2Ud6m8UPqW/Resize-Image-Inside-Table-Widget?node-id=459%3A4159

PRD
Story
When adding images in appsmith tables, i want to manage the size of the images so that i can show images better to my users
Design flow

When user selects an image col in the table widget, they will now see options for predefined image sizes.
One of these would be default, which inherits data from row height set. Meaning when default is selected the image will follow default row height
Other than that we have options for medium and large which are fixed cell sizes to show images. When any of these are selected, the row wraps to reach these sizes.
Images can be of multiple sizes, by fixing the height we are allowing for changes in width only to maintain the same aspect ratio

@dilippitchika
Updates:

What will happen when cell wrap is on?
https://www.figma.com/file/nTMtrnQJUsso2Ud6m8UPqW/Resize-Image-Inside-Table-Widget?node-id=475%3A7903
What will happen when Image Column width is reduced?
https://www.figma.com/file/nTMtrnQJUsso2Ud6m8UPqW/Resize-Image-Inside-Table-Widget?node-id=476%3A8753

All items are resolved. Moving this to PRD/Design done phase


Providers should have a name

Currently, the provider name is hard coded as "default" which is pretty confusing. We should allow a configuration to specify which provider to use

That's a good idea.
If a configuration isn't set, we find the provider with default name, or the only provider in the cluster, or set error message for configuration.


Error: The number of nested documents has exceeded the allowed limit of [10000]

Below is the error I get when trying to log a TokenClassificationRecord with a fairly large piece of text (>30000 characters) and some predictions. I have tried sending a PUT request to the elasticsearch docker container to update the index.mapping.nested_objects.limit, and It seems that Im able to successfully send the request. However, when trying to log the record I receive the same error that the limit is 10000, as opposed to the new limit that I sent in the put request.
ERROR
opensearchpy.helpers.errors.BulkIndexError: ('1 document(s) failed to index.', [{'index': {'_index': '.rubrix.dataset.coreyelowsky.test.records-v0', '_type': '_doc', '_id': '2091e6a3-2daa-4f5b-8677-1adbe2254fd6', 'status': 400, 'error': {'type': 'mapper_parsing_exception', 'reason': 'The number of nested documents has exceeded the allowed limit of [10000]. This limit can be set by changing the [index.mapping.nested_objects.limit] index level setting.'},

Hi @coreyelowsky and thanks for your feedback
Did you check if the index settings were updated?
GET .rubrix.dataset.coreyelowsky.test.records-v0/_settings

Did you launch the update as follows?:
PUT .rubrix.dataset.coreyelowsky.test.records-v0/_settings
{
  "index": {
    "mapping": {
      "nested_objects": {
        "limit": "30000"
      }
    }
  }
}

Which versions of elasticsearch and Rubrix are you using?
Thanks!

Closing this issue since cannot reproduce. Please, @coreyelowsky, feel free to reopen if you consider.

This problem is related to token-level metrics. We should let users warn about these metrics and allow them to enable/disable them.

@frascuchon Is this issue relevant for 2.0?


Incorrect VRF filter used when clicking the VRFs column in a Prefix table (also in the Prefix Bulk Edit table)

Environment

Nautobot version (Docker tag too if applicable): 2.3.11
Python version: 3.11
Database platform, version: PG13
Middleware(s): N/A

Steps to Reproduce

Create a new Prefix and assign 3 VRFs to it (for example)
Go to the Prefix table and add the VRF Column
Locate your new Prefix
Click the number '3' in the VRFs column to get redirected to the VRFs page

Expected Behavior
I expected to be redirected to the VRFs page correctly showing the 3 VRFs assigned to my Prefix

Observed Behavior
I get redirected to the VRFs page with an incorrect filter being used - prefixes= instead of prefix=

Thanks for submitting the issue! Seems like VRFFilterSet does not have a prefixes filter, instead it has a prefix filter.


Keyboard is not open on textfield (I am using this package with GoRouter)

this package sued with GoRouter then I am getting issue while type on textfield. Keyboard doesn't open .
this issue is occurred if  TextEditingController without static or global key without static as below given:
// this code give the error
final GlobalKey _formKey = GlobalKey();
final TextEditingController mobileController = TextEditingController();
// solved error after add static, but this is not the good solution
static final GlobalKey _formKey = GlobalKey();
static final TextEditingController mobileController = TextEditingController();

@anilflutter make sure you are not building routes inside ScreenUtilInit scope

But ScreenUtil is the parent widget above the MaterialApp. And GoRouter used with Materialapp as MaterialApp.GoRouter().
ScreenUtilInit(
designSize: const Size(430, 932),
builder: (BuildContext context, Widget? child) {
return MaterialApp.router(
debugShowCheckedModeBanner: false,
theme: AppTheme.appThemeData(context),
builder: EasyLoading.init(),
routeInformationProvider: Routes.onRouter.routeInformationProvider,
routeInformationParser: Routes.onRouter.routeInformationParser,
routerDelegate: Routes.onRouter.routerDelegate,
);
},
)

The issue is resolved after moving theme out of screen until scope
ScreenUtilInit(
designSize: const Size(430, 932),
builder: (BuildContext context, Widget? child) {
return child!;
},
child: const MaterialRoute(),
),

child

After applying your solution, I'm now getting this error
Another exception was thrown: LateInitializationError: Field '_minTextAdapt@3085084504' has not been
initialized.

Using this solution, I am not getting any error and not even warning
ScreenUtilInit(
designSize: const Size(430, 932),
builder: (BuildContext context, Widget? child) {
return child!;
},
child: const MaterialRoute(),
),

Can you share the code where are you getting error?


Support for Multi-root Workspaces

I'm working with multi root workspaces and I am not able to get the folder root path in my command.
I would like to use something like "${workspaceFolder}" like is mentioned on the variable reference of vscode.
Can it be added or is there another way this can be achieved?

I'm starting to look into this now.

5826336b485b6bb13fbb3e14d03e651f54dae348

1ccd7ec0bf4463caa7749a7c0c815714aff7b21a

f100db852a7de9cc7e366cf9447c3943e594e979

Released in 0.1.0


SegmentName

The <segmentName> element can currently occur within any <repetition> or <instruction>. This makes no sense. It should only be allowed at the top level, right under the first  element. In the folder bookExamples, the file segmentName.xml has valid and invalid test cases.

had it working but now the assertion doesn't work again.
it works when testing in the xml file with Xpath builder
but not when validating against actual xsd file


Not building on windows

Could it be that sdl2-image needs the same fix as sdl2-ttf ?
if os(windows)
    cpp-options: -D_SDL_main_h

I don't have access to a Windows machine at this time, so any comments on this are very welcome.

I can confirm this.
if os(windows)     cpp-options: -D_SDL_main_h
Has to be added to the .cabal file or it wouldn't install. Same issue with sdl2-gfx.


gh-1532 - fed store now does not add to graph library

Codecov Report

Merging #1533 into develop will increase coverage by 0.02%.
The diff coverage is 75%.

@@              Coverage Diff              @@
##             develop    #1533      +/-   ##
=============================================
+ Coverage      66.11%   66.13%   +0.02%
- Complexity      1796     1797       +1
=============================================
  Files            741      741
  Lines          24451    24448       -3
  Branches        3148     3148
=============================================
+ Hits           16166    16169       +3
+ Misses          7013     7010       -3
+ Partials        1272     1269       -3

Impacted Files
Coverage Δ
Complexity Δ

...q/gaffer/federatedstore/FederatedGraphStorage.java
81.77% <100%> (-0.38%)
0 <0> (ø)

...q/gaffer/federatedstore/operation/RemoveGraph.java
94.44% <50%> (-5.56%)
0 <0> (ø)

...ov/gchq/gaffer/federatedstore/FederatedAccess.java
88.33% <0%> (-1.67%)
0% <0%> (ø)

...onutil/iterable/LimitedInMemorySortedIterable.java
50% <0%> (+2.77%)
16% <0%> (+1%)
:arrow_up:

.../gov/gchq/gaffer/store/schema/SchemaOptimiser.java
81.72% <0%> (+6.45%)
0% <0%> (ø)
: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 db0f21c...8618a4c. Read the comment docs.


pattern-match and, and, or

Simple match test with expression in case:
match 1, 3, 3
| 1, 1, 2 or 3 => ok 0
| 1, 2 or 3, 3 => ok 1
| _            => ok 0

Compiles to:
// Generated by LiveScript 1.3.1
var ref$;
switch (ref$ = [1, 3, 3], false) {
case !(1 === ref$[0] && 1 === ref$[1] && 2 === ref$[2] || 3 === ref$[2]):
  ok(0);
  break;
case !(1 === ref$[0] && 2 === ref$[1] || 3 === ref$[1] && 3 === ref$[2]):
  ok(1);
  break;
default:
  ok(0);
}

The problem in words: Every case-expression is bundled in one long expression.
It should wrap braces around each column so the precedence for each case is preserved.
1 === ref$[1] && 2 === ref$[2] || 3 === ref$[2]
^---- 1 ----^ && ^------------ 2 -------------^ # yay
^------------ 1 -------------^ || ^---- 2 ----^ # nay

Correct output:
(1 === ref$[1]) && (2 === ref$[2] || 3 === ref$[2])

Updated OP as it was a little.. plain.
I fiddled with ast.Case.compileCase but without much luck. I don't fully understand the code to approach this problem :/

I don't think LS should add parenthesis by default, but if it is the most commonly expected use case, it makes sense to do it.

Well if we want to keep the meaning of , to end a expression they should be there.


193 bug unable confirm invoice

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Non-functional change (docs, style, minor refactor)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my code changes.
[ ] All new and existing tests passed.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 59.043%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/controllers/callbacks/zebedee-callback-controller.ts
0
1
0.0%

src/controllers/invoices/post-invoice-controller.ts
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
1167

Relevant Lines:
1951

💛  - Coveralls


Import Error, 'Symbol not Found'

Hello @aashrafh ! thank you for your repo.
I'm successfully done on install step3. "conda activate mozart"
but when I get through step4, It gives me an error 'Symbol not Found'
and also I wonder that do I need to run main.py file on Mozart-main/src/ directory? I'm not sure about this step.
my environment is macOS, BIg Sur.
this is the error I got.
Traceback (most recent call last):   File "main.py", line 2, in <module>     from pre_processing import *   File "/Users/parkhyunwoo/opt/anaconda3/envs/mozart/Mozart-main/src/pre_processing.py", line 4, in <module>     import cv2 ImportError: dlopen(/Users/parkhyunwoo/opt/anaconda3/envs/mozart/lib/python3.7/site-packages/cv2.cpython-37m-darwin.so, 2): Symbol not found: _mp_get_memory_functions   Referenced from: /Users/parkhyunwoo/opt/anaconda3/envs/mozart/lib/libgnutls.30.dylib   Expected in: /Users/parkhyunwoo/opt/anaconda3/envs/mozart/lib/libhogweed.4.dylib  in /Users/parkhyunwoo/opt/anaconda3/envs/mozart/lib/libgnutls.30.dylib

It seems that you have a problem with the OpenCV version. the version used in the code doesn't work for your machine so try to downgrade it.
You can find more details here


Tooltip component

Tooltips can provide a huge usability impact.
This component should receive at least two props.

position
background-color

Any other props which might come in handy to configure the Tooltip can be implemented as well if you have some in mind.
It should of course also accept content via a slot.

Hello! is it okay if can work on this?

Absolutely!


Set up a single sign-on for multiple Azure Active Directory domains?

Hi,
I have setup SSO for Opendistro Kibana using Azure AD- Keycloak-OpenID Connect using single domain and its working perfectly.
Could you please help on setting up SSO using multiple domains?

Using OpenID connect.
Using SAML.

Please check this doc to set up multiple authentication domains: https://opendistro.github.io/for-elasticsearch-docs/docs/security/configuration/saml/#running-multiple-authentication-domains
Here is the doc on how to set up openId domain: https://opendistro.github.io/for-elasticsearch-docs/docs/security/configuration/openid-connect/#configure-openid-connect-integration
Please feel free to reopen the issue if these info doesn't help you.

Hi @cliu123,
Can you please suggest how can i configure multiple domains using OpenID connect? Its working fine with single domain and here is the Kibana configuration. How can i add the same for multiple domains? Please suggest.
opendistro_security.auth.type: "openid"
opendistro_security.openid.connect_url: "https://<keycloak_url>/auth/realms/test/.well-known/openid-configuration"
opendistro_security.openid.client_id: "<keycloak_client_id>"
opendistro_security.openid.client_secret: "<keycloak_client_secret>"
opendistro_security.openid.base_redirect_url: "https://<kibana_ip>:5601/"

@cliu123,
Or Can you please suggest multiple authentication configurations using SAML?
We are using Opendistro ELK + Keycloak + Azure AD (multiple authentication).


Mc text search

@lukecampbell @DanielJMaher
Text search API needed to support the construction of the ui backbone searching.  This also implements the catalog rebuild when the services are deployed.

good to go?

No.  This is going to wait until we have time to dedicate to understanding it's potential impacts.  Without Jim, Luke, Andy, or myself able to dedicate time to this review, it will probably sit until Thursday.  Will this impede your work for the week?

Sounds good, nah it's cool.

@FBRTMaka Why is this closed now?

We're waiting till Thursday!

If you WANT to be distracted, I can add it back.  But I'd rather not have a PR open cause confusion for no reason.


Support for Lilygo T5-4.7 e-paper device

Adding support for Lilygo e-paper T5 device.
So far tried few examples, and this one mostly works:
https://www.reddit.com/r/homeassistant/comments/sdx5gg/yet_another_lilygo_t5_eink_esphome_dashboard/
Adapted to my setup, changed language to English, but still more work is needed.

Following files are used my my version of the project - based on folder location:
/esphome

common.hr
t5.yaml
Google_Sans_Bold.ttf
Google_Sans_Medium.ttf
materialdesignicons-webfont.ttf

/entities/binary_sensors
balcony_temp_falling.yaml
balcony_temp_rising.yaml
/entities/templates
distance_andrej.yaml
distance_mirta.yaml


Remove previously deprecated Reader.fetch method

Codecov Report

Merging #231 into master will decrease coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #231      +/-   ##
==========================================
- Coverage   86.19%   86.03%   -0.16%
==========================================
  Files          69       69
  Lines        3686     3680       -6
  Branches      560      504      -56
==========================================
- Hits         3177     3166      -11
- Misses        413      414       +1
- Partials       96      100       +4

Impacted Files
Coverage Δ

petastorm/reader.py
90.22% <ø> (+1.89%)
:arrow_up:

petastorm/pytorch.py
96.15% <0%> (-3.85%)
:arrow_down:

petastorm/workers_pool/tests/test_workers_pool.py
96.75% <0%> (-2.6%)
:arrow_down:

petastorm/tf_utils.py
79.13% <0%> (-1.74%)
:arrow_down:

petastorm/workers_pool/process_pool.py
93.56% <0%> (-0.59%)
: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 127f1cc...b423461. Read the comment docs.


revert hadoop 3 in docker

@lyogev if ci passes u can merge...its a big change but if the e2e tests should pass i think we are good


Fix keys error

I was seeing a local compiler error after updating some keys values, and had to add this typealias to get it to compile. I'm curious to see if this will build on CI at all.

Yup, failed. That means something's up with my local machine. Closing PR.


App crashes in release mode

Hi,
Thanks for the plugin. It works great in debugging apk.
However, when I tried to build a release apk (flutter build apk), the app is crashing on opening the camera.
I am building the example in your plugin package. I did not do any modifications on the code.
I got the following errors in Logcat:
2021-08-12 21:08:09.591 2620-2693/? E/Perf: Fail to get file list co.sotai.flutter_mediapipe_example
2021-08-12 21:08:09.591 2620-2693/? E/Perf: Fail to get file list co.sotai.flutter_mediapipe_example
2021-08-12 21:08:12.594 3074-3074/? A/DEBUG: pid: 2620, tid: 2974, name: ExternalTexture  >>> co.sotai.flutter_mediapipe_example <<<
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #01 pc<PHONE_NUMBER>bd557c  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/lib/arm64/libmediapipe_jni.so
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #02 pc<PHONE_NUMBER>bd49c0  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/lib/arm64/libmediapipe_jni.so (google::LogMessage::SendToLog()+920)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #03 pc<PHONE_NUMBER>bd4f68  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/lib/arm64/libmediapipe_jni.so (google::LogMessage::Flush()+220)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #04 pc<PHONE_NUMBER>bd8590  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/lib/arm64/libmediapipe_jni.so (google::LogMessageFatal::~LogMessageFatal()+16)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #05 pc<PHONE_NUMBER>425a18  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/lib/arm64/libmediapipe_jni.so
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #06 pc<PHONE_NUMBER>425b38  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/lib/arm64/libmediapipe_jni.so (Java_com_google_mediapipe_framework_PacketCreator_nativeCreateGpuBuffer+40)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #07 pc<PHONE_NUMBER>006cb8  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.odex (art_jni_trampoline+184)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #14 pc<PHONE_NUMBER>053740  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.vdex (com.google.mediapipe.framework.PacketCreator.a+40)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #17 pc<PHONE_NUMBER>052abc  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.vdex (c.a.b.a.m.a+188)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #20 pc<PHONE_NUMBER>05229c  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.vdex (c.a.b.a.l$a.o+188)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #23 pc<PHONE_NUMBER>052080  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.vdex (c.a.b.a.l$a.j)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #26 pc<PHONE_NUMBER>052068  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.vdex (c.a.b.a.l$a.k)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #29 pc<PHONE_NUMBER>0516fc  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.vdex (c.a.b.a.i.run+8)
2021-08-12 21:08:13.065 3074-3074/? A/DEBUG:       #41 pc<PHONE_NUMBER>054946  /data/app/co.sotai.flutter_mediapipe_example-E38YiQQIHIYt11cfZW8WPQ==/oat/arm64/base.vdex (c.a.b.b.c.run+106)
2021-08-12 21:08:13.858 1624-2106/? E/InputDispatcher: channel '7661bd9 Sys2030:co.sotai.flutter_mediapipe_example/co.sotai.flutter_mediapipe_example.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
2021-08-12 21:08:13.858 1624-2106/? E/InputDispatcher: channel 'a37fbc co.sotai.flutter_mediapipe_example/co.sotai.flutter_mediapipe_example.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
2021-08-12 21:08:13.900 894-894/? E/CompositionEngine: Error when queueing buffer for display [flutter-vd]: -32
2021-08-12 21:08:13.909 1624-3299/? E/InputDispatcher: Window handle Window{7661bd9 u0 Sys2030:co.sotai.flutter_mediapipe_example/co.sotai.flutter_mediapipe_example.MainActivity} has no registered input channel
2021-08-12 21:08:13.918 1624-4397/? E/InputDispatcher: Window handle Window{7661bd9 u0 Sys2030:co.sotai.flutter_mediapipe_example/co.sotai.flutter_mediapipe_example.MainActivity} has no registered input channel

Thank you for your using and report.
But nowadays, little bit busy. Please wait a couple weeks. After that, I will check it.

Hi @Emad-Eldeen
Thank you for your report. You are right.
It seems to not refer JNI lib, Now I struggling to refer it.
flutter_mediapipe/example/android/app/build.gradle
    externalNativeBuild {
        ndkBuild {
            path '../../../android/src/main/jniLibs/arm64-v8a/libopencv_java3.so', '../../../android/src/main/jniLibs/arm64-v8a/libmediapipe_jni.so'
        }
    }

But, in order to do that, release key from google is required, it seems.
* Where:
Build file '/Users/hoge/flutter_mediapipe/example/android/app/build.gradle' line: 27

* What went wrong:
A problem occurred evaluating project ':app'.
> No signature of method: build_9vdixiby72husarqd7bfv6pf9.android() is applicable for argument types: (build_9vdixiby72husarqd7bfv6pf9$_run_closure2) values: [build_9vdixiby72husarqd7bfv6pf9$_run_closure2@2dd56c8c]

It needs much more time to solve it.
Thank you for your patience.

If there is any other way to fix, please let me know.
Actually, it is my first time to make Smartphone application.

@Emad-Eldeen
I am keeping to investigate it.
I confirmed app-release.apk contains JNI libs with extracting file.
The difference of size between app-debub.apk and app-release.apk is kernel_blob.bin size basically.
So, I think the reason is the permission for release.
https://flutter.dev/docs/deployment/android
   signingConfigs {
       release {
           keyAlias keystoreProperties['keyAlias']
           keyPassword keystoreProperties['keyPassword']
           storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
           storePassword keystoreProperties['storePassword']
       }
   }

Currently, I don't want to release  this sample for Android Play.
If you tried other example of the app-release.apk, please let me know.
Thanks, tac.

Hello Tac,
Thanks for the hint. I will check that and in case I was able to solve it, I will create a pull request.
BR

I finally was able to fix this issue.
The issue is coming from R8 shrinking and minimizing in Gradle. It seems that it is detecting some mediapipe code as not needed and removing it for some reason.
The issue was fixed by setting the following config in build.grade file:

Thank you for your help.
I will check it.


Add otPlatRadioGetReceiveSensitivity() API

More backgrounds in #1709.
This PR:

Add a new otPlatRadioGetReceiveSensitivity() API to get sensitivity value;

Use the receive sensitivity value as the noise floor for link metric computation;

Remove some unused noise floor related functions.

@nibanks, I have updated it and addressed all of your comments, thanks.

Looks great. Thanks for taking care of this. Just added some small suggestions.


map_blocks errors with numpy 1.26.0

map_blocks raises an attribute error when used with numpy 1.26
Minimal Complete Verifiable Example:
import dask.array as da

x = da.arange(6, chunks=3)
x.map_blocks(lambda x: x * 2).compute()

Which results in:
AttributeError: module 'numpy' has no attribute 'object'.
`np.object` was a deprecated alias for the builtin `object`. To avoid this error in existing code, use `object` by itself. Doing this will not modify any behavior and is safe.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
    https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

np.object isn't used though: np.object_ is used twice in array.core:
https://github.com/dask/dask/blob/5d75a04132d5ea1535287a649310c8529dbb3a79/dask/array/core.py#L901
https://github.com/dask/dask/blob/5d75a04132d5ea1535287a649310c8529dbb3a79/dask/array/core.py#L979
So I'm a little confused about why it's erroring here.
For what it's worth, writing dtype=object instead seems to work fine for me locally.

Hi, thanks for your report.
Your reproducer works for me without raising
I am on NumPy 1.26
numpy                     1.26.0          py311hb8f3215_0    conda-forge

Which Dask version are you on? I am on main


Updated UI

That looks cool!! @divyaagrawal261
Can you share the link to the GitHub pages deployed for your branch

Sure, here is the link :
https://divyaagrawal261.github.io/Stopwatch/

Hello @divyaagrawal261, you have done a phenomenal Job,
But there is a problem with it. Your branch contains a lot of conflicts from the main branch.
A possible solution to this is, You can make a button in the original project which can redirect to your project files.
You can add your files separately instead of making changes to the original one.
All the best 👍


Simplify the default name of the TranslatedResourceOfX Types

Is your feature request related to a problem? Please describe.
The default name of the TranslatedResourceOfX Types is unpractical.
Describe the solution you'd like
Maybe something like this?
type XTranslation {
   key: X!
   label: String!
}

This should be done at the same time as, or after, enhancement #5


Add files via upload

@rkgp3 leicester.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


Update tab navigation to be 508 compliant

Definition of Ready

[ ] Does this meet the INVEST criteria?
[ ] Does this have a clearly defined user?
[ ] Does this have an estimate?
[ ] Does this have acceptance criteria?
[ ] Does this have sufficient context (wireframes, business rules, etc.)?
[ ] Is this traceable to a feature, epic, or PI?

User Story
As a user, I want to be able to navigate Monitoring Plan tabs in a way so that they are 508 compliant.
Acceptance Criteria
Given the user is in the system,
When the user is navigating Monitoring Plan tabs,
Then the tab navigation is compliant with 508 standards.
Context
The coding of the UI tabs will be important. They need to be "tab-able."
Be sure to model the tab coding against the aria specs, here are some resources
https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel
https://www.w3.org/TR/wai-aria-practices-1.1/examples/tabs/tabs-1/tabs.html
https://dequeuniversity.com/library/aria/tabpanel
http://accessibility.athena-ict.com/aria/examples/tabpanel2.shtml
Be sure to discuss tab order with dev and UX team—especially with multiple menus, tables, and accordions.
Tab order should be logical, up to down, left to right
Make sure the tab order is based on the order in the DOM, do not use tabindex because the order must also be logical in the DOM for screen readers
Make sure that scrollable areas can be scrolled using a keyboard.
If specific keystrokes are necessary to scroll, be sure to put visible directions on the page to communicate the keystrokes to the user
"Open" buttons or links should be labeled in the code with what they're actually opening. E.g. "Open Power Plant."
Yes, visibly it's ok to have the buttons say 'Open Tab' but programmatically it should be something like 'Open Tab for . This can be done with an aria label. See example 1 on https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute.
Make the tabs only openable from the actual "open" buttons, anything else would be inaccessible or confusing
This would simplify. If the whole row is clickable, then just make sure that the keyboard only tabs to the open tabs buttons
Form fields should only submit input when a user has told it to submit.
This would simplify, otherwise you would need a visible message saying that a change on the page will occur when interacting with the forms, see https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G13
Make sure that sections like the pagination area have hidden headings that identify them as such for screen readers.
The external "show/hide inactive" toggle method is preferred.
Correct, pagination in general will need care in keyboard accessibility and coding. See https://www.a11ymatters.com/pattern/pagination/ for an example. Right now one problem is that if a keyboard user activates a pagination page, 3 for example, visually the table is shifted, but when tabbing back, it goes to the last row of the table.
Other Notes
Testing
Test Case:
Tester:
Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Has the user story been accepted by the Product Owner?
[ ] Is the user story ready to be deployed to the test/staging environments?

Closing for now, the tabs work well with keyboard and pretty well with a screen reader. The only thing that is not implemented is the ARIA coding for tabpanels https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel. Not sure if the EPA 508 team will require that.


[SPARK-30790]The dataType of map() should be map<null,null>

What changes were proposed in this pull request?
spark.sql("select map()") returns {}.
After these changes it will return map<null,null>

Why are the changes needed?
After changes introduced due to #27521, it is important to maintain consistency while using map().

Does this PR introduce any user-facing change?
Yes. Now map() will give map<null,null> instead of {}.

How was this patch tested?
UT added. Migration guide updated as well

Can one of the admins verify this patch?

ok to test

Can one of the admins verify this patch?

Test build #118254 has started for PR 27542 at commit 395eee8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23013/
Test PASSed.

Test build #118254 has finished for PR 27542 at commit 395eee8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118254/
Test FAILed.

Just to check; we need independent legacy configs for arrays and maps?

Just to check; we need independent legacy configs for arrays and maps?

That is exactly my doubt as well. As per my opinion we should have a single config for both of them.

Test cases are failing because key of a map can't be of NullType. @cloud-fan

how about a single config spark.sql.legacy.createEmptyCollectionUsingStringType?

how about a single config spark.sql.legacy.createEmptyCollectionUsingStringType?

Seems fine to me. I will update code.

Test build #118291 has started for PR 27542 at commit 3319d3a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23049/
Test PASSed.

Test build #118296 has started for PR 27542 at commit 1a066e1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23054/
Test PASSed.

Test build #118291 has finished for PR 27542 at commit 3319d3a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118291/
Test PASSed.

Test build #118296 has finished for PR 27542 at commit 1a066e1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118296/
Test PASSed.

Test build #118315 has started for PR 27542 at commit e873527.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23073/
Test PASSed.

Test build #118315 has finished for PR 27542 at commit e873527.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118315/
Test FAILed.

retest this please

Test build #118322 has started for PR 27542 at commit e873527.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23080/
Test PASSed.

Test build #118322 has finished for PR 27542 at commit e873527.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118322/
Test PASSed.

thanks, merging to master/3.0!


Wrong answer -15

WHEN I answer a question incorrectly
THEN time is subtracted from the clock

+15 actually

nope -15


Updates!

Includes all the changes by @bountye and then my updates:
add more PaymentType enums
add $payment_methods to Account

fixes #13  and #16

@mathieukempe Do you have time to merge this and publish a new version of the NuGet package?

sorry for the delay, it's now merged and pushed to nuget

Thanks! I'll send pull requests for bug fixes if I broke anything >.<


chore(jest-config): util types

Summary
Adjusted typing's for _replaceRootDirTags and fix related issue in normalize.ts.
Note: did change functionality in _replaceRootDirInObject, (not used anywhere else and not exported) , i moved the null check within _replaceRootDirTags to simplify typings.

Test plan
No compile errors

Codecov Report

Merging #8437 into master will increase coverage by <.01%.
The diff coverage is 25%.

@@            Coverage Diff             @@
##           master    #8437      +/-   ##
==========================================
+ Coverage   62.33%   62.33%   +<.01%
==========================================
  Files         266      266
  Lines       10737    10738       +1
  Branches     2614     2614
==========================================
+ Hits         6693     6694       +1
+ Misses       3461     3460       -1
- Partials      583      584       +1

Impacted Files
Coverage Δ

packages/jest-config/src/utils.ts
75.86% <22.22%> (ø)
:arrow_up:

packages/jest-config/src/normalize.ts
77.92% <33.33%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

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


Should access, administrative, identification, structural be @nest properties?

See: https://json-ld.org/spec/latest/json-ld/#dfn-nested-properties

Looks like those are properly defined "node objects" (https://json-ld.org/spec/latest/json-ld/#dfn-node-objects) so probably not.


[qa] Fix commit message check fails #187

Changes
Fix commit message check is failing when there is a dot after issue
Checklist

[ ] I have read the contributing guidelines.
[ ] I have manually tested the proposed changes.
[ ] I have written new test cases to avoid regressions. (if necessary)
[ ] I have updated the documentation. (e.g. README.rst)
[ ] I have added [change!] to commit title to indicate a backward incompatible change. (if required)
[ ] I have checked the links added / modified in the documentation.

Closes #187.

Coverage increased (+0.003%) to 98.585% when pulling 718ffd2bcb7e0c8e29795074f341530ca671642d on issues/187-commit-check into e49737869597ece9500736e766d5f24ad1e60d47 on master.


Open terminal in specific directory

If I initialize Gotty with this parameters:
gotty --permit-arguments /myshellscript.sh
And the URL with which access is:
https://mygottyserver/?dir=/mydir
I can assume that in myshellscript.sh:
#!/bin/sh
cd "$1"
exec sh

Will it open a shell with the current directory = mydir which is the value passed in the dir argument of the URL?
And if I call several times the same URL changing the url parameter on each of the times will I have a new web console positioned in the directory informed via the URL parameter?

You need to use arg to pass parameter values. I think what you want is https://mygottyserver/?arg=/mydir. When you have two or more parameters, you can simply add more arg to your query string like https://mygottyserver/?arg=/mydir&arg=/some/where/else.

And if I call several times the same URL changing the url parameter on each of the times will I have a new web console positioned in the directory informed via the URL parameter?

Yes.
Note that, it could be a security volatility if you don't sanitize or check any parameter values. In your example, anyone who know the URL can try "directory traversal" to access hidden files.


Cant slice along batch for MixtureSameDistribution produced by Keras layer

I'm trying to make some dense layers that output the parameters of Gaussian mixture (a mixture density network). I want to run a batch of data through the network (for speed), get out a batch of distributions, and then slice to work with only some elements of the batch at a time. If I were doing this with just tfp, I call:
import tensorflow_probability as tfp
tfd = tfp.distributions

num_mixture_components = 12
batch_size = 4

probs = np.random.rand(batch_size, num_mixture_components)
loc = np.random.rand(batch_size, num_mixture_components)
scale = np.random.rand(batch_size, num_mixture_components)

gm = tfd.MixtureSameFamily(
      mixture_distribution=tfd.Categorical(probs=probs),
      components_distribution=tfd.Normal(loc=loc, scale=scale))

print(gm)
# slice along batch
print(gm[1])

This works as expected giving
tfp.distributions.MixtureSameFamily("MixtureSameFamily", batch_shape=[4], event_shape=[], dtype=float64)
tfp.distributions.MixtureSameFamily("MixtureSameFamily", batch_shape=[], event_shape=[], dtype=float64)

However when I try the same thing with a mixture density network in Keras I get an error
import tensorflow.keras.layers as tfkl
import tensorflow.keras as tfk

num_mixture_components = 12

l = tfkl.Input(shape=(100))

# Make a fully connected network that outputs parameters of Gaussian mixture
mu = tfkl.Dense(units=num_mixture_components, activation=None)(l)
sigma = tfkl.Dense(units=num_mixture_components, activation='softplus')(l)
alpha = tfkl.Dense(units=num_mixture_components, activation='softmax')(l)
stacked = tfkl.Concatenate()([mu, sigma, alpha])

mixture = tfp.layers.MixtureNormal(num_mixture_components,
                                        event_shape=[], name="test")(stacked)
model = tf.keras.Model(inputs=l, outputs=mixture)

out = model(np.random.rand(4, 100))

gm = out.tensor_distribution;

print(gm)
# slice along batch
print(gm[1])

Gives me this cryptic error:
tfp.distributions._MixtureSameFamily("MixtureSameFamily", batch_shape=[4], event_shape=[], dtype=float32)

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In [72], line 27
     25 print(gm)
     26 # slice along batch
---> 27 print(gm[1])

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/distributions/distribution.py:852, in Distribution.__getitem__(self, slices)
    825 def __getitem__(self, slices):
    826   """Slices the batch axes of this distribution, returning a new instance.
    827
    828   ```python
   (...)
    850     dist: A new `tfd.Distribution` instance with sliced parameters.
    851   """
--> 852   return slicing.batch_slice(self, {}, slices)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:220, in batch_slice(batch_object, params_overrides, slices, bijector_x_event_ndims)
    217 slice_overrides_seq = slice_overrides_seq + [(slices, params_overrides)]
    218 # Re-doing the full sequence of slice+copy override work here enables
    219 # gradients all the way back to the original batch_objectribution's arguments.
--> 220 batch_object = _apply_slice_sequence(
    221     orig_batch_object,
    222     slice_overrides_seq,
    223     bijector_x_event_ndims=bijector_x_event_ndims)
    224 setattr(batch_object,
    225         PROVENANCE_ATTR,
    226         batch_object._no_dependency((orig_batch_object, slice_overrides_seq)))  # pylint: disable=protected-access
    227 return batch_object

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:179, in _apply_slice_sequence(batch_object, slice_overrides_seq, bijector_x_event_ndims)
    177 """Applies a sequence of slice or copy-with-overrides operations to `batch_object`."""
    178 for slices, overrides in slice_overrides_seq:
--> 179   batch_object = _apply_single_step(
    180       batch_object,
    181       slices,
    182       overrides,
    183       bijector_x_event_ndims=bijector_x_event_ndims)
    184 return batch_object

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:168, in _apply_single_step(batch_object, slices, params_overrides, bijector_x_event_ndims)
    166   override_dict = {}
    167 else:
--> 168   override_dict = _slice_params_to_dict(
    169       batch_object, slices, bijector_x_event_ndims=bijector_x_event_ndims)
    170 override_dict.update(params_overrides)
    171 parameters = dict(batch_object.parameters, **override_dict)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:153, in _slice_params_to_dict(batch_object, slices, bijector_x_event_ndims)
    150 else:
    151   batch_shape = batch_object.experimental_batch_shape_tensor(
    152       x_event_ndims=bijector_x_event_ndims)
--> 153 return batch_shape_lib.map_fn_over_parameters_with_event_ndims(
    154     batch_object,
    155     functools.partial(_slice_single_param,
    156                       slices=slices,
    157                       batch_shape=batch_shape),
    158     bijector_x_event_ndims=bijector_x_event_ndims)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/batch_shape_lib.py:367, in map_fn_over_parameters_with_event_ndims(batch_object, fn, bijector_x_event_ndims, require_static, **parameter_kwargs)
    361     elif (properties.is_tensor
    362           and not tf.is_tensor(param)
    363           and not tf.nest.is_nested(param_event_ndims)):
    364       # As a last resort, try an explicit conversion.
    365       param = tensor_util.convert_nonref_to_tensor(param, name=param_name)
--> 367   results[param_name] = nest.map_structure_up_to(
    368       param, fn, param, param_event_ndims)
    369 return results

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow/python/util/nest.py:1435, in map_structure_up_to(shallow_tree, func, *inputs, **kwargs)
   1361 @tf_export("__internal__.nest.map_structure_up_to", v1=[])
   1362 def map_structure_up_to(shallow_tree, func, *inputs, **kwargs):
   1363   """Applies a function or op to a number of partially flattened inputs.
   1364
   1365   The `inputs` are flattened up to `shallow_tree` before being mapped.
   (...)
   1433     `shallow_tree`.
   1434   """
-> 1435   return map_structure_with_tuple_paths_up_to(
   1436       shallow_tree,
   1437       lambda _, *values: func(*values),  # Discards the path arg.
   1438       *inputs,
   1439       **kwargs)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow/python/util/nest.py:1535, in map_structure_with_tuple_paths_up_to(shallow_tree, func, *inputs, **kwargs)
   1526 flat_value_gen = (
   1527     flatten_up_to(  # pylint: disable=g-complex-comprehension
   1528         shallow_tree,
   1529         input_tree,
   1530         check_types,
   1531         expand_composites=expand_composites) for input_tree in inputs)
   1532 flat_path_gen = (
   1533     path
   1534     for path, _ in _yield_flat_up_to(shallow_tree, inputs[0], is_nested_fn))
-> 1535 results = [
   1536     func(*args, **kwargs) for args in zip(flat_path_gen, *flat_value_gen)
   1537 ]
   1538 return pack_sequence_as(structure=shallow_tree, flat_sequence=results,
   1539                         expand_composites=expand_composites)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow/python/util/nest.py:1536, in <listcomp>(.0)
   1526 flat_value_gen = (
   1527     flatten_up_to(  # pylint: disable=g-complex-comprehension
   1528         shallow_tree,
   1529         input_tree,
   1530         check_types,
   1531         expand_composites=expand_composites) for input_tree in inputs)
   1532 flat_path_gen = (
   1533     path
   1534     for path, _ in _yield_flat_up_to(shallow_tree, inputs[0], is_nested_fn))
   1535 results = [
-> 1536     func(*args, **kwargs) for args in zip(flat_path_gen, *flat_value_gen)
   1537 ]
   1538 return pack_sequence_as(structure=shallow_tree, flat_sequence=results,
   1539                         expand_composites=expand_composites)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow/python/util/nest.py:1437, in map_structure_up_to.<locals>.<lambda>(_, *values)
   1361 @tf_export("__internal__.nest.map_structure_up_to", v1=[])
   1362 def map_structure_up_to(shallow_tree, func, *inputs, **kwargs):
   1363   """Applies a function or op to a number of partially flattened inputs.
   1364
   1365   The `inputs` are flattened up to `shallow_tree` before being mapped.
   (...)
   1433     `shallow_tree`.
   1434   """
   1435   return map_structure_with_tuple_paths_up_to(
   1436       shallow_tree,
-> 1437       lambda _, *values: func(*values),  # Discards the path arg.
   1438       *inputs,
   1439       **kwargs)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:101, in _slice_single_param(param, param_event_ndims, slices, batch_shape)
     85 """Slices into the batch shape of a single parameter.
     86
     87 Args:
   (...)
     98     `slices`.
     99 """
    100 # Broadcast the parmameter to have full batch rank.
--> 101 param = batch_shape_lib.broadcast_parameter_with_batch_shape(
    102     param, param_event_ndims, ps.ones_like(batch_shape))
    103 param_batch_shape = batch_shape_lib.get_batch_shape_tensor_part(
    104     param, param_event_ndims)
    105 # At this point the param should have full batch rank, *unless* it's an
    106 # atomic object like `tfb.Identity()` incapable of having any batch rank.

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/batch_shape_lib.py:274, in broadcast_parameter_with_batch_shape(param, param_event_ndims, batch_shape)
    270 base_shape = ps.concat([batch_shape,
    271                         ps.ones([param_event_ndims], dtype=np.int32)],
    272                        axis=0)
    273 if hasattr(param, '_broadcast_parameters_with_batch_shape'):
--> 274   return param._broadcast_parameters_with_batch_shape(base_shape)  # pylint: disable=protected-access
    275 elif hasattr(param, 'matmul'):
    276   # TODO(davmre): support broadcasting LinearOperator parameters.
    277   return param

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/distributions/distribution.py:952, in Distribution._broadcast_parameters_with_batch_shape(self, batch_shape)
    926 def _broadcast_parameters_with_batch_shape(self, batch_shape):
    927   """Broadcasts each parameter's batch shape with the given `batch_shape`.
    928
    929   This is semantically equivalent to wrapping with the `BatchBroadcast`
   (...)
    950       the given `batch_shape`.
    951   """
--> 952   return self.copy(
    953       **batch_shape_lib.broadcast_parameters_with_batch_shape(
    954           self, batch_shape))

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/distributions/distribution.py:915, in Distribution.copy(self, **override_parameters_kwargs)
    897 """Creates a deep copy of the distribution.
    898
    899 Note: the copy distribution may continue to depend on the original
   (...)
    909     `dict(self.parameters, **override_parameters_kwargs)`.
    910 """
    911 try:
    912   # We want track provenance from origin variables, so we use batch_slice
    913   # if this distribution supports slicing. See the comment on
    914   # PROVENANCE_ATTR in batch_slicing.py
--> 915   return slicing.batch_slice(self, override_parameters_kwargs, Ellipsis)
    916 except NotImplementedError:
    917   pass

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:220, in batch_slice(batch_object, params_overrides, slices, bijector_x_event_ndims)
    217 slice_overrides_seq = slice_overrides_seq + [(slices, params_overrides)]
    218 # Re-doing the full sequence of slice+copy override work here enables
    219 # gradients all the way back to the original batch_objectribution's arguments.
--> 220 batch_object = _apply_slice_sequence(
    221     orig_batch_object,
    222     slice_overrides_seq,
    223     bijector_x_event_ndims=bijector_x_event_ndims)
    224 setattr(batch_object,
    225         PROVENANCE_ATTR,
    226         batch_object._no_dependency((orig_batch_object, slice_overrides_seq)))  # pylint: disable=protected-access
    227 return batch_object

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:179, in _apply_slice_sequence(batch_object, slice_overrides_seq, bijector_x_event_ndims)
    177 """Applies a sequence of slice or copy-with-overrides operations to `batch_object`."""
    178 for slices, overrides in slice_overrides_seq:
--> 179   batch_object = _apply_single_step(
    180       batch_object,
    181       slices,
    182       overrides,
    183       bijector_x_event_ndims=bijector_x_event_ndims)
    184 return batch_object

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/tensorflow_probability/python/internal/slicing.py:172, in _apply_single_step(batch_object, slices, params_overrides, bijector_x_event_ndims)
    170 override_dict.update(params_overrides)
    171 parameters = dict(batch_object.parameters, **override_dict)
--> 172 return type(batch_object)(**parameters)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/decorator.py:231, in decorate.<locals>.fun(*args, **kw)
    229 def fun(*args, **kw):
    230     if not kwsyntax:
--> 231         args, kw = fix(args, kw, sig)
    232     return caller(func, *(extras + args), **kw)

File ~/mambaforge/envs/phenotypes/lib/python3.10/site-packages/decorator.py:203, in fix(args, kwargs, sig)
    199 def fix(args, kwargs, sig):
    200     """
    201     Fix args and kwargs to be consistent with the signature
    202     """
--> 203     ba = sig.bind(*args, **kwargs)
    204     ba.apply_defaults()  # needed for test_dan_schult
    205     return ba.args, ba.kwargs

File ~/mambaforge/envs/phenotypes/lib/python3.10/inspect.py:3179, in Signature.bind(self, *args, **kwargs)
   3174 def bind(self, /, *args, **kwargs):
   3175     """Get a BoundArguments object, that maps the passed `args`
   3176     and `kwargs` to the function's signature.  Raises `TypeError`
   3177     if the passed arguments can not be bound.
   3178     """
-> 3179     return self._bind(args, kwargs)

File ~/mambaforge/envs/phenotypes/lib/python3.10/inspect.py:3168, in Signature._bind(self, args, kwargs, partial)
   3166         arguments[kwargs_param.name] = kwargs
   3167     else:
-> 3168         raise TypeError(
   3169             'got an unexpected keyword argument {arg!r}'.format(
   3170                 arg=next(iter(kwargs))))
   3172 return self._bound_arguments_cls(self, arguments)

TypeError: got an unexpected keyword argument 'reinterpreted_batch_ndims'

v2.11.0-rc2-17-gd5b57ca93e5 2.11.0
tensorflow-probability    0.19.0
Python 3.10.6
Ubuntu 18.04
Any ideas why this is happening and how to fix?

@henrypinkard,
The reinterpreted_batch_ndims parameter controls the number of batch dims which are absorbed as event dims; reinterpreted_batch_ndims <= len(batch_shape).
For example, the log_prob function entails a reduce_sum over the rightmost reinterpreted_batch_ndims after calling the base distribution's log_prob. Also the batch dimension(s) index independent distributions, the resultant multivariate will have independent components.
Also reinterpreted_batch_ndims is part of tensorflow probability(tfp), So i request you to check in this repo for more assistance. Thank you!

Thanks for the explanation. I also opened an issue on TFP (https://github.com/tensorflow/probability/issues/1679), though no response yet

@henrypinkard,
Could ypu please feel free to move this issue to closed status, since it is already being tracked there? Thank you!

Still no activity on the TFP issue or clarity no how this might be fixed


Can't do Native executable generation

This command: ./mvnw package -Dpackaging=native-image
Generates an error, it is very long so i put only a part of it

Now i can generate the Quarkus native exe


Unable to attach authorizers to routes

Description
I am using an JWT Authorizer on my APIGateways routes
Reviewing the example set out in complete-http I can either:

Build a map of authorizers within the APIGateway module resource and attach it to a route using the authorizer_key attribute
Build out an authorizer resource and attach it to a route using the authorizer_id attribute

Versions

Module version: 2.0.0:

Terraform version: v1.2.1 on darwin_amd64

Provider version(s):

provider registry.terraform.io/hashicorp/archive v2.2.0
provider registry.terraform.io/hashicorp/aws v4.18.0
provider registry.terraform.io/hashicorp/random v3.3.2
provider registry.terraform.io/hashicorp/template v2.2.0

Reproduction Code [Required]
module "apigateway-v2" {
  source  = "terraform-aws-modules/apigateway-v2/aws"
  version = "2.0.0"

  name          = "${var.environment}-${local.application_name}-http-api"
  description   = "API proxy to ${local.new_relic_app_name}"
  protocol_type = "HTTP"

  cors_configuration = {
    allow_headers = ["content-type", "x-amz-date", "authorization", "x-api-key", "x-amz-security-token", "x-amz-user-agent"]
    allow_methods = ["*"]
    allow_origins = ["*"]
  }

  create_api_domain_name = false

  # Authorizers
  authorizers = {
    "auth0" = {
      authorizer_type  = "JWT"
      identity_sources = "$request.header.Authorization"
      name             = "${var.environment}-auth0-jwt-authorizer"
      audience         = ["https://${local.domain}/api/v2/"]
      issuer           = "https://${local.domain}/"
    }
  }

  # Routes and integrations
  integrations = {
    "ANY /{proxy+}" = {
      connection_type    = "VPC_LINK"
      vpc_link           = "${local.application_name}-vpc"
      integration_uri    = local.alb_http_listener_arn
      integration_type   = "HTTP_PROXY"
      integration_method = "ANY"
      authorizer_key     = "auth0"
    }

    "OPTIONS /{proxy+}" = {
      connection_type    = "VPC_LINK"
      vpc_link           = "${local.application_name}-vpc"
      integration_uri    = local.alb_http_listener_arn
      integration_type   = "HTTP_PROXY"
      integration_method = "OPTIONS"
    }
  }

  vpc_links = {
    knowledge-graph-vpc = {
      name               = "${var.environment}-${local.application_name}-link"
      security_group_ids = flatten([local.alb_sg_ids])
      subnet_ids         = var.vpc_private_subnets
    }
  }

  tags = var.tags
}

Steps to reproduce the behavior:
Code is developed locally, formated and validated using terraform commands
Code is pushed to branch in GitHub
Code is deployed from GitHub using CICD pipelines run using Slack commands
Expected behavior
The created authorizer resource should be attached to the given route
Actual behavior
The authorizer is created as expected but never attached to the route
Workaround
Manually attach the authorizer to the route as required.
Screenshots

I have resolved this issue.
I need to explicity set the authorization_type on the route that uses the authorizer - adding authorization_type = "JWT" resolved this issue:
    "ANY /{proxy+}" = {
      connection_type    = "VPC_LINK"
      vpc_link           = "${local.application_name}-vpc"
      integration_uri    = local.alb_http_listener_arn
      integration_type   = "HTTP_PROXY"
      integration_method = "ANY"
      authorization_type = "JWT"
      authorizer_key     = "auth0"
    }


Wrong output on Windows

When running Ebox on Windows without arguments (list mode), the output is
Distribution "." must start with ".emacs.d-". Aborting.
This is probably due to C:\Users\<username>\AppData\Roaming\.emacs.d being a directory instead of a symlink.
=> What are the values of homeDirName, emacsLinkName, and emacsDir in Ebox?

Fixed with #7


[AVRO-3942] Mark MemoryOutputStream as final

AVRO-3942
What is the purpose of the change
Otherwise the class raises a compilation warning:
lang/c++/impl/Stream.cc:129:27: warning: class with destructor marked 'final' cannot be inherited from [-Wfinal-dtor-non-final-class]
  120 | class MemoryOutputStream : public OutputStream {
      |                          final
  121 | public:
  122 |     const size_t chunkSize_;
  123 |     std::vector<uint8_t *> data_;
  124 |     size_t available_;
  125 |     size_t byteCount_;
  126 |
  127 |     explicit MemoryOutputStream(size_t chunkSize) : chunkSize_(chunkSize),
  128 |                                                     available_(0), byteCount_(0) {}
  129 |     ~MemoryOutputStream() final {
      |                           ^
lang/c++/impl/Stream.cc:120:7: note: mark 'avro::MemoryOutputStream' as 'final' to silence this warning
  120 | class MemoryOutputStream : public OutputStream {
      |       ^

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Documentation

Does this pull request introduce a new feature? no

This PR is effectively the same as https://github.com/apache/avro/pull/2550 which got closed because the fork was deleted.

Thank you, @mkmkme !


Make deployment mode required

 https://github.com/Azure/azure-sdk-for-node/pull/1781

 https://github.com/Azure/azure-sdk-for-python/pull/641


chore: Spellcheck and correct entire code base

chore: Add typos configuration to manifest for project level spellchecking
This commit just sets the stage with tooling configuration for typos, conveniently tucked away in the workspace manifest where other lint configurations already are.

chore: Fix typos throughout code base (automatic)
This commit has fixes for all the typos that typos is confident can just be fixed automatically, minus the overrides added to the manifest for the false positives I found.

chore: Fix typos throughout code base (manual)
This commit has fixes for just the typos that typos was not confident on how to fix but these seem like reasonable resolutions to me.

Force pushed to revert some whitespace changes to the manifest my editor automatically weaseled in there. I'll propose normalizing TOML formatting separately.

It looks like PRs are configured to be squashed by default but rebase is an option. I suggest the split here is meaningful because in the event a later PR branched before this has a merge conflict or an API spelling problem comes up later, this split makes it easier to diagnose and re-correct (for the former scenario) or re-configure or upstream fixes (for the later scenario).

Sorry for the delayed response. I had a rest and didn't look into PRs in recent days. First, it is great to integrate more great tools into workflow, and typos should be great and well-known one, so I'll proceed with merge it. I shall need to learn how I can configure typos locally at the same time.

It looks like PRs are configured to be squashed by default but rebase is an option.

We can rebase, but squash isn't bad, because we also have git revert and git cherry pick to help edit sub commits a PR conveniently. A key advantage of rebasing in my eyes is that if we do rebase, everyone can view and each of the three commit messages at the top level of the commit history.

First, it is great to integrate more great tools into workflow, and typos should be great and well-known one, so I'll proceed with merge it. I shall need to learn how I can configure typos locally at the same time.

You shouldn't have to configure it at all, it will follow the project configs here. You don't even need it locally if you don't want. If you do, just run typos from the root of the project to see any potential errors it flags, and typos --write-changes if you want it to automatically fix them.
That's it.

We can rebase, but squash isn't bad, because we also have git revert and git cherry pick to help edit sub commits a PR conveniently.

This is not correct. If you squash, you do not have the ability to revert or cherry pick available any longer on the actual commits. Those tools only work at the commit level, and by definition if you squash the commits of a PR together you will no longer have them separately.

A key advantage of rebasing in my eyes is that if we do rebase, everyone can view and each of the three commit messages at the top level of the commit history.

Yes, and it will turn up the most related commit message in a future git blame, which might be useful in this case. I hope not, but renaming a bunch of symbols can have unexpected consequences if something happens to either use or be used publicly that I missed excluding. Having the automatic from the manually edited changes separately can be very useful in correcting things later if need be.

If you do, just run typos from the root of the project to see any potential errors it flags, and typos --write-changes if you want it to automatically fix them.

I remember my friend fixed some typos by typos using his local typos plugin, https://github.com/Myriad-Dreamin/tinymist/pull/177.

QuarticCat: My typos plugin keeps complaining so I fixed some.

This is what I would like to set up.

This is not correct. If you squash, you do not have the ability to revert or cherry pick available any longer on the actual commits.

To be clear, we can revert/cherry pick them as long as we have references stored in .git, and they'll not be garbage collected in local under some conditions. They might be even forever stored on GitHub's storage, but I'm not sure whether we can pull these references from GitHub explicitly. But you're correct, this is not safe.

I'm sure there are editor plugins and probably even LSP drivers for typos, but I don't happen to know exactly what is out there. Personally I just use the CLI tool and run it now and then.