Search - Not here page opens when returning from Hold page when accessing from header

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.1-0
Reproducible in staging?: y
Reproducible in production?: no, new feature
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Launch New Expensify app.
Go to any DM.
Submit an expense to the user.
Go to Search.
Tap on the expense submitted in Step 3.
Tap on the report header.
Tap Hold.
Tap Back button.

Expected Result:
App will return to previous page (report details page or transaction thread).
Actual Result:
App opens not here page.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/38435837/a39aedad-48b0-4d78-8a01-d23977763a0c

View all open jobs on GitHub

@rlinoz FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-collect - Release 1

My solution here will fix this issue too.

reviewing

I can, but I think the problem here is that we are showing the hold option in a DM.
https://github.com/Expensify/App/assets/5201282/78e52359-096e-4dd4-8048-dae410c9d581

We added this actions in this PR https://github.com/Expensify/App/pull/43251
cc: @cdOut @ikevin127

I think we should try to fix the underlying issue which is there is no backTo in the HoldReasonPage when coming from the Search page.
cc: @bernhardoj

Still looking for proposals, I think this is annoying UX issue but does not have to be blocker this late in the deployment cycle

I tried a few times with existing expense and with brand new expense but I could not reproduce this. I believe this probably is reproducible, but there has to be some extra circumstances to get this as this does not always happen.
my test
https://github.com/Expensify/App/assets/3929868/6bd96ace-17c1-46d4-ad73-5e90d567a2e2
There is one thing that I have noticed: in the reproductions that do have this bug, for @rlinoz and @m-natarajan the animation when going from Details -> Hold looks like a "back" animation, suggestion this is a POP action. Whereas on my video I cleaarly get the PUSH and I'm moving forward. This definitely feels related to the bug, but thats the extent of what I found.
Can someone give a 100% reliable way to reproduce this?

This was fixed in this other PR https://github.com/Expensify/App/pull/44359/files#diff-63967b77292f23428a8509ef11c77b0e68feb3a8ddddfa0fa560c38014915eb9R78-R80, not reproducible anymore.


Unable to add new PWA

I've tried to submit the quotery.com web app. It's not clear if it's being saved properly, but there are quite a few console errors as shown below:

The issue is that we are strict about the origin and static.quotery.com is not part of www.quotery.com
"Error: Error while validating the manifest: ERROR: start_url must be same-origin as document"
We would need to relax the validation


Quick Start Guide seems out of date

Trying to install on RHEL7...
From https://github.com/BeyondTrust/pbis-open/wiki/docs/PBIS_Open_Quick_Start.pdf
Step 1: Download PBIS Open
To download PBIS Open:
1. Browse to www.beyondtrust.com and click Downloads and Free Tools.

There appears to be no such link
I tried installing from the repo ( https://repo.pbis.beyondtrust.com/yum.html )
I got the package installed, but I see no GUI.

We are currently working on updating the Quick start guide for the transition to github.
The downloads can be found on the release page:
https://github.com/BeyondTrust/pbis-open/releases
As for a GUI there is only one for the domainjoin process which needs some updating. This can also been done via the command-line:
/opt/pbis/bin/domainjoin-cli

Thanks for the prompt reply.
So does this mean that the YUM repos that are linked from this wiki are not currently distributing the correct version?
If so, advise removing the links in the wiki to both the QuickStart guide and the repos, to avoid confusion.

Release page and repositories are both updated with the same version at release. Both are currently <IP_ADDRESS>
I'll leave this open as a reminder to upload the new quick start guide once it's completed.

Quick start guide updated
https://github.com/BeyondTrust/pbis-open/wiki/docs/PBIS_Open_Quick_Start.pdf

From the guide:
"After the wizard finishes installing PBIS Open, the user interface for joining a domain appears."

Did not appear for me.
Printed to the console after running the installer:
As root, run domainjoin-gui or domainjoin-cli to join a domain...
[...]
domainjoin-gui: command not found...

Rebooted, and still no domainjoin-gui command available.
domainjoin-cli is, however.

pbis and domainjoin-cli are available commands in the path but domainjoin-gui is not. I'll bring this up to get removed from the post install text to prevent confusion.
As for the the gui not launching. This would be caused by a missing library in the latest distributions
<EMAIL_ADDRESS>~]$ /opt/pbis/bin/domainjoin-gui
/opt/pbis/bin/domainjoin-gui: error while loading shared libraries: libpangox-1.0.so.0: cannot open shared object file: No such file or directory
We are aware of this and are planning to update them.
For now I recommend the domainjoin-cli as it's much quicker then the gui anyway:
domainjoin-cli join MYDOMAIN.COM MyJoinAccount

After trying to get this to work on RHEL (Tried 7.1, 7.3 beta and 7.3), I gave up after days of trying, but it seems that this is largely to do with RHEL's networking being fundamentally broken.
So I tried Ubuntu.
I ran the pbis-open-<IP_ADDRESS>.linux.x86.deb.sh on Ubuntu 16.10 and it broke apt
I can now no longer install anything on Ubuntu, as it always moans that pbis-open "subprocess installed post-installation script returned error exit status 1. Errors were encountered while processing: pbis-open:i386"
I tried searching around on the internet and all the suggestions I can find to fix it don't work.
apt-get clean etc, all do nothing to fix this.

Can you open a new issue for the platform of your choice and provide the install logs (/var/log/pbis-open-install.log)
More details and output will help us identify your issue. Thanks


Blackjack rules

[ ] How card values are counted (+ ace counts differently)
[ ] The winner is the one who is closer to blackjack (21 points)
[ ] Exceeding 21 points – loss
[ ] Button: Pass
[ ] Button: Double
[ ] Button: Hit
[ ] Button: Stand
[ ] Button: Cancel

Closed in 6a58d4b9aa526405f72791f51b68c40d40276bc3


Build fail with glog 0.7

Describe the bug
Build librime will fail with glog 0.7
To Reproduce
Steps to reproduce the bug:

clone the repo
build with the following command

cmake . -GNinja -Bbuild -DCMAKE_INSTALL_PREFIX=/usr -DBUILD_MERGED_PLUGINS=Off -DENABLE_EXTERNAL_PLUGINS=On
cmake --build build

Expected behavior
Build should success.
Log
 1376 |   LogMessage(const LogMessage&) = delete;
      |                                 ^
/usr/include/glog/logging.h:1377:3: error: ‘LogMessage’ does not name a type
 1377 |   LogMessage& operator=(const LogMessage&) = delete;
      |   ^~~~~~~~~~
/usr/include/glog/logging.h:1379:2: error: expected unqualified-id before ‘private’

Screenshots
If applicable, add screenshots to help explain your problem.
Flavor(please complete the following information):
Select your flavor:

[ ] ibus-rime
[ ] fcitx-rime
[*] fcitx5-rime
[ ] Squirrel
[ ] Trime
[ ] Weasel

Package:

OS: ArchLinux
Version: 20240222
URI: N/A

Additional context
Add any other context about the problem here.

Possible fix would be https://github.com/archlinuxcn/repo/pull/3656/files?diff=unified&w=0#diff-ab3bf317eb940e89ab7d2e235ec51e25c003f8ca472a788f882bc9d9633414d9


Closing tags

Since files are often shared or re-used (via include(), require(), and their _once variants), any whitespace after the closing PHP tag can cause buffering issues, improper formatting for responses (like JSON or XML), broken Ajax requests, or problems with the timing of sending headers. Closing PHP tags are also prohibited by many style guides, including PSR-2, Zend Framework, Symfony, and CodeIgniter. I saw on Code Climate that many of your PHP-only files had closing PHP tags, many with a line of whitespace after it, so I cleaned these up. I also added the Code Climate badge to the readme.

Can you please re-create this against the development branch? I have quiet a lot of changes in there that will go to master soon for the 1.0.2 release. Would be cool to have this in the same release.


Getting wrong date

Seems its duplicate for  https://github.com/felixge/node-dateformat/issues/70 & closing this one.


Improve update process

After merging #21, we are basically abandoning Darin's neat awk script for the old Debian repository which generated Dockerfiles based on available versions of libraries.  I'm sure this could be adapted (not by me, as I'm not an AWK person), or rewritten based on the PPA we are now using so that we can stay up-to-date with releases.

I think it should mostly just be a matter of updating the URL the script parses the packages from. I'll try to have a look.

Changing the the URL at this line from:
curl_url = "http://deb.haskell.org/stable/Packages"

to
curl_url = "http://ppa.launchpad.net/hvr/ghc/ubuntu/dists/utopic/main/binary-amd64/Packages"

is all that's needed to restore version info fetching. However, the rewriting won't work unless the ENV variables are put back in place in the Dockerfile since the script used these for search and replace.

If someone wants to change how the rewriting works to not use the ENV variables, the functions dfile_sed_cmd and dfile_tag_rewrite here would be the place to start.


[TwigComponent] Deprecations not setting defaults and anonymous template directory

With v2.13.0 you get a deprecation warning for not setting for not setting twig_component.defaults and twig_component.anonymous_template_directory.
I’m not familiar with the internals or future plans but at least for now it’s no problem to ignore those two settings, if you don’t have any anonymous components and explicitly name your components. So being forced to set them creates a bit of boilerplate.
With setting twig_component.anonymous_template_directory (and later being it components by default) there’s even another little problem. Until now I had a folder /templates/components where my named components live. Setting the anonymous template directory to components makes at least the console debug:twig-component command fail:

Unknown component "foobar.twig". And no matching anonymous component template was found.

I don’t know, if that’s just a minor problem of that command or if that can also be problematic in normal use, though. Anyway, I had to move my components to an ux subfolder and add a useless empty anonymous folder.
Anyway, declaring I have no anonymous components by not setting a directory would make sense for me and perhaps would even save a few cycles searching for them. Probably the same with default naming.
What do you think?
PS: I wonder if the configuration defaults should get a better, more self explanatory name like anonymous_template_directory, where you know what it does by just looking at it.

Those config values should be set via the flex recipe so it should not be too much troubles for most.
There is something with the command i’ll check that in a couple of hours.

@smnandre Something like namespace_directory_mapping.

The configuration file copied by Flex should be this one.
twig_component:
    anonymous_template_directory: 'components/'
    defaults:
        # Namespace & directory for components
        App\Twig\Components\: 'components/'

I find it pretty good but there is always room for improvement, so feel free to open an issue/PR to suggest changes :)

t least the console debug:twig-component command fail:

Unknown component "foobar.twig". And no matching anonymous component template was found.

What are the arguments given to the command ?
This message should only happen if you type something like
php bin/console debug:twig-component foobar.twig

But maybe there is something not working as expected there

@smnandre

I find it pretty good but there is always room for improvement, so feel free to open an issue/PR to suggest changes :)

That is why I mentioned it :-)

What are the arguments given to the command ?

Just plain console debug:twig-component

Could you update symfony/ux-twig-component and check if it still happen ? I think this could be something we fixed already.
If that does not help things (but i'm pretty confident it will), i'll probably need more details about the structure / name of your templates and classes.
But i really do think an update will fix this problem

@smnandre I now know where the problem is. Stay tuned…
Btw, would be good to merge #1314 in the meantime :-)

It would be :)


Fix BLE testcase setup and teardown

Fix BLE testcase setup and teardown
Description
Miscellaneous fixes for testcases encountered during testing with ESP-IDF FreeRTOS. Check return values, initialize BLE as needed, and use some older APIs during assertions.
Checklist:

[ X] I have tested my changes. No regression in existing tests.
[ X] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Rebase to master and merge.


Getting error unauthorized on every link

Describe the bug
Can't log in anymore because I get redirected to / and get the error unauthorized, but I am not signned in. That also happens if I visit /login. The api still works.
System information
Please provide information on:

v1.29.6 @ sqlite3 in Docker

So if you try to log in, you get an unauthorized error? Can you please send corresponding server logs?

So if you try to log in, you get an unauthorized error? Can you please send corresponding server logs?

Somehow my browser fcked something up, so it was the problem of my browser, not your awesome work!


Improve error architecture so developers can do better detection

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


Feature: Change color theme by specifying color in the data.json file

ISSUE #10
Context
This new feature allows users to choose their preferred color theme by specifying the colors in the data.json file, where all the information needed to generate the CV is provided.
Description
A new property called colorTheme has been added to the data.json file. The value of colorTheme is passed to the CSS variable  --color-theme during the setup of the App component, and this variable sets the color where needed.
Changes in the codebase
App.tsx:
import data from "./data.json";
...
function App() {
  useEffect(() => {
    // Assign the CSS variable (--color-theme) with the value in data.json
    document.documentElement.style.setProperty(
      "--color-theme",
      data.colorTheme,
    );
  }, []);

return (
...

Thanks for the contribution.
As discussed in the issue, we will need to implement other features before tackling this one.


Chrony wont start

Problem/Motivation
Chrony wont start when click clicking start in home assistant.
Expected behavior
Chrony should start as a addon to home assistant and provide time with ntp.
Actual behavior
Following messages appears:
Failed to to call /addons/a0d7b954_chrony/start - Can't start addon_a0d7b954_chrony: 500 Server Error for http+docker://localhost/v1.41/containers/474c35e999870cde3b02e796bf9b44950e9feecc825adfa88960fe394ae8bf32/start: Internal Server Error ("failed to open stdout fifo: error creating fifo /var/run/docker/containerd/474c35e999870cde3b02e796bf9b44950e9feecc825adfa88960fe394ae8bf32/init-stdout: no space left on device")
Steps to reproduce
Install, config and start (try)
Proposed changes
Rebuild the docker image and validated before releasing

"failed to open stdout fifo: error creating fifo /var/run/docker/containerd/474c35e999870cde3b02e796bf9b44950e9feecc825adfa88960fe394ae8bf32/init-stdout: no space left on device"
Appears to be an issue on your device, this isn't anything the addon can resolve.

Not a problem with my device - all other addons are working and it no problem adding or removing addons - just this one. Is this a issue with HA?


Scaled 3D Models causes light issues

Godot version:
3.2 mono
OS/device including version:
ubuntu 19.10
Issue description:
If you scale a model from for example: 1 to -1, the light does not reflect as spected:

Steps to reproduce:

create a spotlight
place 3d model
scale model's Z to -1
light will be shown as the gif

Minimal reproduction project:
mrp.zip
Workarounds
The workaround for the moment is creating animations for the model scaled inside the modeling software. (if you have 10 animations, create another 10 scaled -1?)
Related to #26710 but the issue is from Mar 6, 2019
Related to #20599 from far back in time Jul 30,2018

duplicate of #29317

Duplicate of #29317 indeed.


Macrobody facet support

I need to convert a model that uses macrobody facets for an RCC surface type. I've added this by parsing the macrobody facet identifier ([sense]{macrobody}.{facet_number}) and replacing the entry in the expression with the ID of the attribute-surface on the openmc.SurfaceComposite object before we send it off to openmc.Region.from_expression.
The sense of the surface replacing the macrobody facet in the expression is accounted for in a mapping of the facet ID to the attribute-surface based on the object. While it gets the job done I'm a little conflicted about it as most (all?) of this tool is independent of assumptions about the internals of objects in OpenMC. Still, I think any MCNP-specific conventions should be kept here. I'm open to other suggestions on how to approach this.

Not a bit! Thanks for polishing it up!


main: address feedback from #49

Addressing feedback from #49 that accidentally arrived after I merged.

LGTM thanks!


Weights not shared when static quantizng and converting LSTM

Hi again,
I was testing quantization and conversion of LSTM models and everything works perfectly for fp32 and dynamic quantization!
However, when doing static quantization (for example with post-training quantization) the model quantizes and converts successfully but the weights are not shared in the model, so the size of the TFLite file is much bigger than it should be. This doesn't happen when converting fp32 models or using dynamic quantization - weights are shared for each step of the LSTM and model size is small as expected. This is all using unroll_lstm=True.
Is there an option that I haven't set correctly or this is just a limitation of conversion at the moment, I couldn't find anything in the documentation?
Many thanks,
Richard

We will take a look.

Is there an option that I haven't set correctly or this is just a limitation of conversion at the moment, I couldn't find anything in the documentation?

Seems to be a bug.  As you can see here, the weight is always created rather than reused. https://github.com/alibaba/TinyNeuralNetwork/blob/main/tinynn/converter/operators/torch/quantized.py#229

@Burton2000 Actually, this problem is a bit more complicated than I had thought. These weights are generated separated after going through torch.jit.trace, so it seems the only way to group them together is to a add group_weight_pass in the Graph Optimizer.

@Burton2000 Added a new option group_buffers in TFLiteConverter to mitigate this issue. Please update to the latest version and have a try. https://github.com/alibaba/TinyNeuralNetwork/commit/43295f1521989a7cc05981fe0ca56b6a6271e218#diff-4fdac68b9e814bcddd1a62032f7dc0464582e3c4b740a4d2d80ebbe38d665789R58

@peterjc123 wow thanks for the quick reply and patch! I have tried it out and seems to be working, the quantized file size is now small again as expected and inference is still working as expected, thank you!
One thing out of curiosity, when inspecting the model in Netron the weight names for the quantized model are still different for each time step which isn't the case for fp32 model. Do you think this is something easy to change so names match if setting group_buffer_pass=True or is not worth the time?

@Burton2000 Well, to achieve that we will need another group_tensors pass (or we can just fuse the group_buffers pass into the new pass). It should be easy to implement but I don't quite get why we need the same names for weights here. Nevertheless, I can do this anyway.

@Burton2000 The new option named group_tensors is added and should work as what you expected. FYI, the old pass is removed.

@peterjc123 this is awesome it works perfectly, thank you!


No matching export for import "getSyntheticLinkProps"

Provide a general summary of the issue here
After updating the @nextui-org/react package to 2.4.6, the @react-aria/utils dependency was updated to 3.25.0. There was a problem importing into @react-aria/utils. This is why the project is not deployed to AWS Amplify and there is no way to continue developing the project!

🤔 Expected Behavior?
Everything should work as it did on the previous version @react-aria/utils 3.24.1
😯 Current Behavior
The project does not start and does not build
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce

yarn remove @nextui-org/react
yarn add @nextui-org/react
yarn dev

Version
3.25.0 @react-aria/utils
What browsers are you seeing the problem on?
Chrome, Other
If other, please specify.
No response
What operating system are you using?
MacOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

I think you possibly have multiple copies of our packages installed. Could you check that is the case? it usually manifests as a node_modules inside of a package already in your node_modules. There's also this script https://git.corp.adobe.com/gist/luyau/5033d7b6fb95deb94be24c623e0b1118 which may help you identify duplicates.
Another option is that you need to update some of the other packages, such as react-aria/menu or react-aria/gridlist

I have the same error

We are all using NextUI at least with NextJS the import trace seems a bit more helpful
<EMAIL_ADDRESS>Attempted import error: 'getSyntheticLinkProps' is not exported from '@react-aria/utils' (imported as '$2K6sg$getSyntheticLinkProps').

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./components/admin/rootLayout.tsx

I was still in 2.4.2 and got the same error without updating. Was my CI pipeline broken all the time and I didn't know it or this isn't my fault? :D

I was also using version 2.4.2 and did not update it, I noticed this error when I deployed an update to my app on aws amplify. Then I decided to update all versions of the packages to the latest and the error began to appear no matter what version I installed. I don't have duplicate packages, I'm sure of that!

Anyone else using turbo in this setup? Is this possibly related to turbo?

I got this same error message as well when deploying on Vercel 😰

@IvanHoliak

After updating the @nextui-org/react package to 2.4.6, the @react-aria/utils dependency was updated to 3.25.0.

this looks weird since we use the fixed version for<EMAIL_ADDRESS>as well as for other RA dependencies.

I am also facing this issue (not using next-ui), it seems that<EMAIL_ADDRESS>in general is broken.
The script proposed by @snowystinger reports no duplicates in package-lock.

Boiled it  down to this commit.
https://github.com/adobe/react-spectrum/commit/a4dee6e127265a93c7a88d9c559c7d7fea180560
Apparently getSyntheticLinkProps was renamed to useSyntheticLinkProps.
That on it's own shouldn't cause so much trouble as nextui refers to the 3.24.1 version which was released 2 months ago. Makes me wonder why 3.5.0 is used in nextui builds. More specifically in docker builds, as on my local machine with my yarn.lock unchanged, this problem does not occur but only in my Dockerfile.
In my specific use case, I was using turbo which produced a malformed yarn.lock which would be dirty on yarn install --immutable. I opted out of turbo and manually added all packages/ and apps/ package.jsons.
Either way if it's broken on your local machines it helps to do yarn why @react-aria/utils to see why it is using 3.5.0 perhaps. On my CI machine, turbo was to blame.

Something like that is a breaking change, especially when combined with the usage of ^ when referring to that dependency, it means that grabbing<EMAIL_ADDRESS>will install<EMAIL_ADDRESS>because the dependency refers to "@react-aria/utils": "^3.24.1",

"After updating to Next.js 3.25, I am encountering an issue when creating a build. Please suggest how to fix it."
Errors:-
Invalid next.config.js options detected:
⚠     Unrecognized key(s) in object: 'sentry'
⚠ See more info here: https://nextjs.org/docs/messages/invalid-next-config
▲ Next.js 14.2.5

Environments: .env.local, .env.production

Creating an optimized production build ...
Failed to compile.
<EMAIL_ADDRESS>Attempted import error: 'getSyntheticLinkProps' is not exported from '@react-aria/utils' (imported as '$2K6sg$getSyntheticLinkProps').
Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./app/error.tsx

Same error getting from this morning
Failed to compile
Next.js (14.2.5)
<EMAIL_ADDRESS>Attempted import error: 'getSyntheticLinkProps' is not exported from '@react-aria/utils' (imported as '$2K6sg$getSyntheticLinkProps').
Any solution for this.

Something like that is a breaking change, especially when combined with the usage of ^ when referring to that dependency, it means that freshly grabbing (or deduping) packages like<EMAIL_ADDRESS>will install<EMAIL_ADDRESS>because the dependency refers to "@react-aria/utils": "^3.24.1",, and then build will be broken.

Supplement a bit. In our NextUI table component, we are using the fixed version for RA table (v3.14.1)
"dependencies": {
  "@react-aria/table": "3.14.1",
   // some other dependencies ...
}

In<EMAIL_ADDRESS>it uses<EMAIL_ADDRESS>"node_modules/@react-aria/table": {
  "version": "3.14.1",
  "dependencies": {
    "@react-aria/focus": "^3.17.1",
    "@react-aria/grid": "^3.9.1",
     // some other dependencies ...
  },
}

Due to the caret (^), @react-aria/grid": "^3.9.1" will resolve to<EMAIL_ADDRESS>which was released yesterday.
"node_modules/@react-aria/grid": {
  "version": "3.10.0",
  "dependencies": {
    "@react-aria/utils": "^3.25.0",
     // some other dependencies ...
  },
}

and the breaking change was introduced in<EMAIL_ADDRESS>

That means all previous versions of React-aria are broken due to the poor version management of the React-aria monorepo ?

@wingkwong should we expect a fix from react-aria or NextUI?

As a temporary fix, you can specify the older version in a package.json
"resolutions": {    "@react-aria/utils": "3.24.1"  }

As a temporary fix, you can specify the older version in a package.json
"resolutions": { "@react-aria/utils": "3.24.1" }

This will only work if you also lock other @react-aria/* packages (and any transitive dependencies) to install versions that do not depend on the 3.25.0 version, as otherwise you'll get the inverse error.

same issue here

Any hope :D?

Hmm, interesting issue. I think we were under the impression that since this is an internal/private package, breaking changes were ok, but clearly that's not the case due to pinning. Sorry about that.
I guess we could potentially bring back the old version of the function and leave it there alongside the new one. In this case the function is quite small. We will check to see if there are any more like this as well.

same here

Solved here https://github.com/nextui-org/nextui/pull/3537

Solved here nextui-org/nextui#3537

That's not correct. We rollbacked it.

Solved here nextui-org/nextui#3537

That's not correct. That PR was experimental and somehow it got merged by mistake. We've rollbacked it. We'll wait for RA team's updates and at the same time we're trying to upgrade to RA latest and resolve the build issues.

I tried it earlier once I saw this PR. Forgot I have added resolutions as a temp solution. My bad.

still happening

hold your horses, I'm still working on releasing the fix to npm 😅

Waiting patiently.

As a temporary fix, you can specify the older version in a package.json
"resolutions": { "@react-aria/utils": "3.24.1" }

This will only work if you also lock other @react-aria/* packages (and any transitive dependencies) to install versions that do not depend on the 3.25.0 version, as otherwise you'll be at risk of getting the inverse error.

You can also specify versions below 3.25.0 in case some package depends on an older version:
"resolutions": { 	"@react-aria/utils": "<3.25.0"  }

As a temporary fix, you can specify the older version in a package.json
"resolutions": { "@react-aria/utils": "3.24.1" }

This worked on my end. Thanks for the heads up @yuliahey

This should be fixed in v1.3.1. Sorry for the bug and thanks for your patience.

@devongovett Thanks a lot!

Build Error Due to Import Error with @react-aria/utils - Solution Found
Description:
When building my project, I encountered errors related to imports from @react-aria/utils. Specifically, the build failed due to an import error for getSyntheticLinkProps.
Errors Encountered:
Failed to compile.
<EMAIL_ADDRESS>Attempted import error: 'getSyntheticLinkProps' is not exported from '@react-aria/utils' (imported as '$2K6sg$getSyntheticLinkProps').
Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>Solution:
I resolved the issue by ensuring the following package versions:
"@nextui-org/react": "2.2.10"
@nextui-org/react: 2.2.10
@react-aria/utils: 3.24.1
Steps Taken:
1:  use  nextUI version  "@nextui-org/react": "2.2.10",
2: yarn cache clean
3: yarn node_module delete
4: yarn.locak file delete
5: yarn install
Ran the build command (yarn build) successfully.
Additional Context:
This solution addresses the import error by using compatible versions of the involved packages. If you encounter similar issues, aligning your package versions as shown above might help resolve them.


Add rst module to init.example.el

PR #2020 adds support for a lang/rst module, but it wasn't added to the example init.el, which I believe is the one that's placed in ~/.doom.d/init.el during a new installation ?
I think this greatly improves discoverability :)

Good catch. Thanks for your help!


Working with default mapping (defautMessage => msgid) don't allow msgid duplicates in a same file

In my case, all my translations from babel-react-intl-plugin are merged into a default json file. When I want to use the default json2pot behavior, it won't merge messages sharing the same msgid / defaultMessage.
From my understanding it came from the fact that every file builds a map of msgid / message data. Before the real mapping to occur. I guess it would be better to generate an array of message data for each file, then merge them all through map/reduce, later allowing duplicated msgid in the same file.
To reproduce this, simply put two string sharing the same defaultMessage in a same file.

@Guibod got same result.

It now allows duplicated key in the same file.
Please try v2.0.0 (with some breaking changes of internal functions.)  and feel free to reopen this issue if there is any problems.
Thanks! 😄


Setup Android Tests CI Setup

Setup Android Tests CI Setup
:recycle: Current situation & Problem

Addresses #16
Closes #21

:gear: Release Notes

Setup Android Tests CI Setup

☑ Remaining Issues

[x] Report Code Coverage: I have build the rough setup for running the tests but the code coverage report currently doesn't work as expected for the Android tests. Codecov seems to merge reports for the same commit so we can just upload them all in different builds. Would be amazing if you can take a look at this @eldcn
[x] Contact Tests Fail: It seems like the contact Android tests fail locally and on the CI. Good as a test for the setup, would be great if we can fix them as part of this PR @Basler182

:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

Thank you @eldcn for the amazing work to finish this PR up and thanks for the feedback and suggestions. I improved the state based on your feedback and provided some reasoning about some for the GitHub action setup.
Will merge this PR for now but happy to continue parts of the discussion here or in separate GitHub issues if there is still something to follow up on this PR 🚀


When using default netview, dnsview should not be prepended by default.

When trying to test schiff ipam in our environment, with default netview, we see the following in the logs when the controller tries to allocate an IP:
"error": "WAPI request error: 404('404 Not Found')\nContents:\n{ \"Error\": \"AdmConDataNotFoundError: View default.default not found\", \n  \"code\": \"Client.Ibap.Data.NotFound\", \n  \"text\": \"View default.default not found\"\n}\n"}
This is my configuration:
kind: Secret metadata:     name: schiff-operator-config     namespace: engine-system type: Opaque stringData:     IPAM_INFOBLOX_WAPI_VERSION: 2.6.1
and my VSphereMachine has annotation
    ipam.schiff.telekom.de/InfobloxNetworkView: default
This is where "default." is statically prepended - https://github.com/telekom/das-schiff/blob/ipam/ipam/pkg/ipam/infoblox/operations.go#L109
I believe when the netview is "default", the dns view should also be just "default".

should be fixed by
https://hub.docker.com/layers/dasschiff/schiff-operator/v0.2.6/images/sha256-6f47e46f5e758246b5e7593f8b4fb5c94859f14e8157c311350f843b8ee632c2?context=explore
and  https://github.com/telekom/das-schiff/pull/7/commits/7e14c6608dd8582aff57f679a9ca5f2667bad71c


Crash when inserting equations in word

I don't know if this is the place where I should post it, so I am giving it a try.
I was making some notes on word and wanted to insert an equation. So I clicked on Insert -> Equation
Nothing bad until now.
But when I want to insert an structure from Equation Tools -> Design -> Structures, the document freezes and doesn't do anything for a few minutes.
So I started looking online for some information and the only link i found was this one.
It is quite old but it's the same exact problem aparently, this problem comes from the fonts as addresed by the user that addresed this problem.

Hi [MOD],
I noticed that when I disconnect my network, everything works fine.
further investigation with sysinternals' Process Monitor showed that Word loads printers, when I click on 'structures'. Why it is done is beyond me...
Anyhow, It turns out that it waited for 2 minutes every time, for my network printer to respond.
The moment I turned on my network printer, everything works fine.
I really think MS should provide some patch for this...
waiting for a printer to respond, when I don't even want to print anything, seems rather strange.
Big thanks for your support!

So I want to address this bug and I think github is the place to go, but I dont know where.
A comment will be grateful.
Greetings,
Fran Andreo

Thank you for reporting the issue. I will reach out to the engineers to triage this issue.


"Polling" section is confusing

I'm not sure why that section is there or what it's trying to tell me. Is it an explanation of how the blob trigger works? A suggestion of how to implement blob handling? Some clarity would be useful.
The "Warning" message below that is also confusing. In addition to what? And why should I care about storage logs (implementation detail) when I'm implementing a blob trigger?
Finally, if blob triggers are unreliable, how will creating a blob trigger that puts messages on a queue be any more reliable?
Please can this section be rewritten so it's actually comprehensible and useful.

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

ID: 5ecb1e79-f603-03fd-2ef9-c6cf08ffaacd
Version Independent ID: 35c99e36-f224-350b-a258-2e0cfb8ab154
Content: Azure Blob storage trigger for Azure Functions
Content Source: articles/azure-functions/functions-bindings-storage-blob-trigger.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@IanKemp Thanks for the feedback! The section is intended to explain the inner workings of the trigger since it's important to understand the general purpose storage account requirement and later understand the number of operations executing on your storage account.
The Event Grid trigger is the best alternative except the fact that its not straightforward like the blob trigger. This is infact changing with 5.x version of the binding which supports Event Grid as a source while still using the Blob Trigger.
Hope that helps. I am still assigning this issue to the content author for further review and to update the document accordingly if required.


Fix markdown format in ai panel

Before:

After:

can we write a test for this? there were originally matrix tests that test that markdown is rendered correctly, i'd like to see that sort of thing added here as well

This is a little strange. That test is still there and is passing actually. This is for rendering the response that's coming from the ai bot. I'm not sure how to replicate that in a test but I'll take a look.
Here's an example from staging:

is there a mock we can use? maybe @IanCal knows?

is there a mock we can use? maybe @IanCal knows?

Added a test for this 👍


[MM-16039] Fixed accessibility issues with the Account Settings modal

Summary
Fixes MM-16039 by adding ARIA tags to the required elements
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-16039

Thanks @devinbinnie for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla

/check-cla

As per @hmhealey's comments in Apps Team, I'm going to make a fix in mattermost/react-bootstrap to add an aria-label to the CloseButton component, which is a better fix than my workaround

Awaiting https://github.com/mattermost/react-bootstrap/pull/1

I've tested with JAWS and everything looks good!

Awesome! Nice work :)


Add environment configuration

@getsentry/javascript
Fixes GH-660

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

src/raven.js, line 445 [r1] (raw file):

        return this;
    },

I realize we have setRelease, setTransport and others, but I'm concerned about a future where we have setX for every possible config option potentially bloating the library.
Approving tho ...

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

src/raven.js, line 445 [r1] (raw file):
Previously, benvinegar (Ben Vinegar) wrote…
> I realize we have `setRelease`, `setTransport` and others, but I'm concerned about a future where we have `setX` for every possible config option potentially bloating the library.
>
> Approving tho ...

fyi commenting blocks the review unless you change the status or use something like 'btw' to prefix it

Comments from Reviewable

feel free to hijack and/or just merge this when you feel its good

Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Reviewed 1 of 3 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable


Make export_pgp_public nonblocking, memoized

This is an API change, but it doesn't need to take a callback and changing it will make some Keybase changes easier. Let's also make it cache its result in @armored_pgp_public.

Thought a little bit about this, I would advise against.  You'd have to change the code in way too many places, and we've already published the API as is.  Is there a way to get the same result without interfering with code that's already in the wild?

(In other words, I don't think the upside is worth all the bugs this change might introduce.)

I whipped this together, we can make this change backwards compatible with the existing API.

Fixed in 90c9ec99e4100643dd55a3aca6243bb4df011c2a.


Add pgp options/wrong standard

It would be very nice to have some more options in the process of generating the key, e.g. i would like to set the length of my key to 4096 bits. Maybe as a expert option not shown at first...
(sorry didn't notice that the issue was already there)
Also it would be nice to have the option to change the pgp standard to inline. I know its not »state of the art« but in fact a lot of people can not understand more than that. K9 and APG/openkeychain only show inline messages. Another problem seems to be, that you have a mistake in your encryption<EMAIL_ADDRESS>can not decrypt the message. If i copy the text of an email to another adress of me by hand into APG it errors with saying, that the integration of the encryption has an error. On my linux machine the decryption works fine...
Maybe the inline support could change the biggest problems...
wkr iorek

hi, letting the user choose to send either as pgp/inline or pgp/mime is extremely bad user experience, since this is a decision most users will not be able to make. also, in the pgp community, the overwhelming majority is leaning towards deprecating pgp/inline and letting it rest in peace. pgp/mime is a properly standardized format, whereas pgp/inline is a shim that's broken more often than not.


Update logging/metrics config using ConfigWatcher

Eventing has now a helper for configuring ConfigMapWatcher callbacks for logging/metrics/tracing configs, so we can get rid of all the redundant updateAdapter...Config methods.
The usage of a static ConfigMapWatcher is also not necessary anymore since the source.ConfigAccessor interface can be mocked.

so if we merge this, this feature won't work with an old knative release ?

It will, this only makes use of internal eventing libraries, the clients work across versions within a range of supported API versions.

ok


Added platform protocols to flutter/services

Added two simple communication protocols on top of PlatformMessages:
PlatformProtocols.invokeJSONFunction (returns Future<T>)
PlatformProtocols.createJSONBroadcastStream (returns Stream<T>)
They allow client code to communicate with platform end-points in a slightly higher-level way than do PlatformMessages, including specified JSON envelopes for error handling. The main driver for adding such facilities is that PlatformProtocols are intended to be the Dart counterpart of an Android and iOS plugin concept (upcoming) that expects this particular protocol, and that should make it easier to write the native side in a stream-lined way that lends itself to tool support, e.g. for consuming a published plugin by declaring a dependency on it.
For preliminary native code and sample Dart client code, see the mit-mit/flutter fork.
More pull-requests cherry-picking from that fork are in the works.

This seems fine, but I wonder if JSON really is the best transport for this stuff. Having to convert an int into a string then insert it into JSON then encode it as UTF-8, then transfer it over, then parse the bytes as UTF-8 then JSON then parsing the int, seems like a lot of effort when we could just pass the four bytes as-is.
JSON also limits us to what we can send over. For example, how would you send an image? Are we going to use this mechanism for a stream of data from the camera?

Would it make more sense to put this on PlatformMessages rather than creating yet another static?

Another option which might be more usable would be to refactor the PlatformMessages stuff so that there is a PlatformChannel object that represents a channel, and then on that you can send and receive messages, set up a stream, etc.

Plan:

refactor PlatformProtocols into PlatformMessages;
introduce PlatformChannel concept
unify PlatformMessages.invokeMethod and PlatformProtocols.invokeJSONFunction
suppress JSON into an implementation detail, then enable more general and performant types of payload encoding

WIP. I'll upload a pull request once I have docs and tests in place.
/// A named channel for efficiently communicating with the host platform using
/// structured messages. The message types supported are non-cyclic structures
/// of the following kinds:
///
/// * `null`
/// * [bool]
/// * [int], will be communicated using 32-bit two's complement binary form
/// * [double], will be communicated using IEEE 754 double-precision binary
///   floating-point format (binary64)
/// * [String]
/// * [ByteData]
/// * [List] of payload values
/// * [Map] from strings to payload values
///
/// Values of these types will be referred to as 'payload values' below.
/// In function signatures, the type of a payload value is `dynamic`.
class PlatformChannel {
  final String channel;

  PlatformChannel(this.channel);

  Future<dynamic> send(dynamic payload) async {
    return _decode(await PlatformMessages.sendBinary(channel, _encode(payload)));
  }

  void setMessageHandler(Future<dynamic> handler(dynamic payload)) {
    PlatformMessages.setBinaryMessageHandler(channel, (ByteData bytes) async {
      return _encode(await handler(_decode(bytes)));
    });
  }

  void setMockMessageHandler(Future<dynamic> handler(dynamic payload)) {
    if (handler == null) {
      PlatformMessages.setMockBinaryMessageHandler(channel, null);
    } else {
      PlatformMessages.setMockBinaryMessageHandler(channel, (ByteData bytes) async {
        return _encode(await handler(_decode(bytes)));
      });
    }
  }

  Future<T> invokeFunction<T>({
    String name,
    Map<String, dynamic> arguments,
    T interpreter(dynamic payload),
  }) async {
    return _interpretPayload(
      send(_encode(<String, dynamic>{
        'name': name,
        'args': arguments,
      })),
      interpreter);
  }

  Stream<T> receiveStream<T>({
    Map<String, dynamic> arguments,
    T interpreter(dynamic payload),
  }) {
    assert(arguments == null || arguments['eventChannel'] is String);
    final String eventChannel = arguments == null ? channel : arguments['eventChannel'];
    StreamController<T> controller;
    controller = new StreamController<T>.broadcast(
      onListen: () async {
        PlatformMessages.setBinaryMessageHandler(
          eventChannel,
          (ByteData reply) async {
            try {
              controller.add(_interpretPayload<T>(_decode(reply), interpreter));
            } catch (e) {
              controller.addError(e);
            }
          }
        );
        try {
          await invokeFunction<Null>(
            name: 'listen',
            arguments: arguments,
          );
        } catch (e) {
          PlatformMessages.setBinaryMessageHandler(eventChannel, null);
          controller.addError(e);
        }
      }, onCancel: () async {
        PlatformMessages.setBinaryMessageHandler(eventChannel, null);
        try {
          await invokeFunction<Null>(
            name: 'cancel',
            arguments: arguments,
          );
        } catch (exception, stack) {
          FlutterError.reportError(new FlutterErrorDetails(
            exception: exception,
            stack: stack,
            library: 'services library',
            context: 'while de-activating platform stream on channel $channel',
          ));
        }
      }
    );
    return controller.stream;
  }

  T _interpretPayload<T>(dynamic payload, T interpreter(dynamic payload)) {
    if (payload is Map) {
      final dynamic status = payload['status'];
      final dynamic message = payload['message'];
      final dynamic data = payload['data'];
      if (status == 'ok')
        return interpreter?.call(data);
      else if (status is String && message is String)
        throw new PlatformException(status: status, message: message, details: data);
      else
        throw new FormatException('Invalid envelope: $payload');
    } else {
      throw new FormatException('Expected envelope Map, got $payload');
    }
  }

  // TODO(mravn): consider replacing this homegrown codec by something existing (protobuf?).
  // TODO(mravn): consider making the codec pluggable.
  ByteData _encode(dynamic payload) { ... }
  dynamic _decode(ByteData bytes) { ... }
}

/// Thrown to indicate that a platform interaction resulted in an error.
class PlatformException implements Exception {
  PlatformException({
    @required this.status,
    @required this.message,
    this.details,
  }) {
    assert(status != null);
    assert(message != null);
  }

  /// A non-`null` status string, such as 'error' or 'not found'.
  final String status;

  /// A non-`null` human-readable error message.
  final String message;

  /// A payload value providing custom details about the error, maybe `null`.
  final dynamic details;

  @override
  String toString() => 'PlatformException($status, $message, $details)';
}

WIP. Created a PlatformChannel concept, a named communication channel with pluggable message codec.
I'd very much appreciate comments on the new design, before I take it much further.
TODOs:

platform-side message codec implementation
dart-side tests
replace calls to deprecated PlatformMessages methods with use of PlatformChannel.
reconsider the current standard codec implementation, maybe use protobufs or some other established standard.

Update: Mikkel is out this week; he will return to this next week.

I'm going to close this PR to get it off the review queue since it's not ready for checkin yet, but please don't hesitate to submit a new PR (or reopen this one) when you're ready.


Code for residual plot

import seaborn as sns
sns.set_theme(style="whitegrid")
X_test.index.name = "Index"
X_test.index
predict_test = ridge_pipeline.predict(X_test)
residual = y_test.copy()
residual.name = "Residuals"
sns.residplot(x=X_test.index, y=residual - predict_test,  color="g")

please change ridge_pipeline to the model you are using with any name, the color can be changed as well

code for saving the figure: can change path in savefig("")
import seaborn as sns
sns.set_theme(style="whitegrid")
X_test.index.name = "Test Data Observations"
predict_test = ridge_pipeline.predict(X_test)
residual = y_test.copy()
residual.name = "Residuals(hours)"
residual_plot = sns.residplot(x=X_test.index, y=residual - predict_test,  color="g")
residual_fig = residual_plot.get_figure()
residual_fig.savefig("residual_fig")

Very nice plot


setup.py does not specify required python version

Which is at least 3.7, since this uses dataclasses.

You are right, I only updated travis configuration, thank you.


Chat messages being lost

We need to implement a way to better check if chat messages were actually accepted server-side and if not resend them. It might be useful to seperate sending and pulling messages for that.

@w20k @Algareb @Ardenian any opinions on that?

Could we use sockets in chat, instead of polling ? :) Though, in this case we will drop some older browser version from our support list.

sockets are supported by all browsers we generally support, I just don't have a backend for that yet, would need to write that first.

if we move to websockets, we could support the webchat that mutik's script provides on kong atm - after all it's the same technologie then. I guess that might be useful to add those rooms as chat-rooms in our chat as well(optional)

Any opinions on moving to sockets?


Errors executing my project after bundle

I have a custom bundle.js file. You can see in that plunk: http://plnkr.co/edit/1HbxsRMjpW9FcF1UtaSQ?p=preview
I execute gulp bundle and the process ends correctly. Then I get a deploy folder. When I load index.html I get errors:
Error: Access to restricted URI denied Error loading<EMAIL_ADDRESS>the same for aurelia-dialog and font-awesome.
My bundle file, is different to the skeleton-navigator, but I think that is correct and don't undestand why I get that errors.

@sergidt Could you please create a github repo with this issue so that I can inspect it better.

I'm getting the same error. After bundling I get:
Unhandled promise rejection Error: XHR error (404 Not Found) loading
<EMAIL_ADDRESS>
In my bundle config, I do have aurelia-validation listed.

@ahmedshuhel Can you please advise on this? I would assume that the specific cultures would need to be listed inthe bundle config or otherwise deployed to the server in the jspm_paclages folder at the above location for dynamic localization.

@32graham stupid question: do you have a<EMAIL_ADDRESS>?

@doktordirk No. Not after bundling (which is correct).
Before bundling yes.
Of course I can fix it by manually copying the files to the right place but then they are not bundled.

@32graham
Try adding aurelia-validation/**/*.js in bundle config. If that does not work try aurelia-validation/resources/*.js

@ahmedshuhel both aurelia-validation/**/*.js and aurelia-validation/resources/*.js worked independently. Thanks :+1:

@ahmedshuhel this is nice, so if I add aurelia-dialog/**/*.html then the views will be bundled as well? Bucause currently I have JS files bundled, but not html files

Yes, that should work. If it doesn't let us know.

yes, it worked, thanks! Now I have about 5 less request :joy:

Thank you all. Closing this one.


StackPrefetch stops when selecting different element (regression)

This feature was remove during a merge in the version 3.
The parameter 'preserveExistingPool' in stackPrefetch.js no longer exists after the commits on Nov 11, 2018.

@frolic06 if you can provide more info, I'm sure we can whip up a quick PR? Any links or code snippets? Would you like to draft a PR to expedite things?

I fixed the bug with this code. I am sorry but i am not used to make a PR.
stackPrefetch.js.txt

I made a PR, I hope it will help you.

Thanks, @frolic06! I'll take a peak today.
Linked PR: https://github.com/cornerstonejs/cornerstoneTools/pull/1074

Hello,
I think this issue #900 refers to the same bug.
The fix is still relevant.

Merged 🎉


TypeError on using SpotDL to downlaod playlists

Environment

System OS: Windows Subsystem for Linux 2
Windows Subsystem for Linux 2
Python Version: Python 3.8.5
Install Source: pip3 install spotdl
Version OR Commit hash: 3.3.1

Expected Behaviour

Iterate over the playlist finding the songs
Actual Behaviour

Gets far down the list then throws a TyperError; 'NoneType' object is not subscriptable
Steps to Reproduce
1.spotdl https://open.spotify.com/playlist/6uMtvyRWTsOSLjRa5JXeRV?si=lSJgpT_mSrm2nz-I0614BA

Traceback

  File "/home/x/.local/bin/spotdl", line 8, in <module>
    sys.exit(console_entry_point())
  File "/home/x/.local/lib/python3.8/site-packages/spotdl/__main__.py", line 110, in console_entry_point
    songObjList = get_playlist_tracks(request)
  File "/home/x/.local/lib/python3.8/site-packages/spotdl/search/utils.py", line 83, in get_playlist_tracks
    'https://open.spotify.com/track/' + songEntry['track']['id'])
TypeError: 'NoneType' object is not subscriptable
Exception ignored in: <function tqdm.__del__ at 0x7f7b4c1de550>
Traceback (most recent call last):
  File "/home/x/.local/lib/python3.8/site-packages/tqdm/std.py", line 1134, in __del__
  File "/home/x/.local/lib/python3.8/site-packages/tqdm/std.py", line 1281, in close
  File "/home/x/.local/lib/python3.8/site-packages/tqdm/std.py", line 1467, in display
  File "/home/x/.local/lib/python3.8/site-packages/tqdm/std.py", line 1137, in __repr__
  File "/home/x/.local/lib/python3.8/site-packages/spotdl/download/progressHandlers.py", line 23, in format_dict
  File "/home/x/.local/lib/python3.8/site-packages/tqdm/std.py", line 1424, in format_dict
TypeError: cannot unpack non-iterable NoneType object

Any other information:

It looks like the track object of songObject of Taylor Swift - Love Story, but I don't know how that's possible.
I'm also unable to find the song in the playlist on Spotify.
{'added_at': '2020-01-22T08:43:17Z', 'added_by': {'external_urls': {'spotify': 'https://open.spotify.com/user/pm5gmrz0rm7b3eayz8aa51840'}, 'href': 'https://api.spotify.com/v1/users/pm5gmrz0rm7b3eayz8aa51840', 'id': 'pm5gmrz0rm7b3eayz8aa51840', 'type': 'user', 'uri': 'spotify:user:pm5gmrz0rm7b3eayz8aa51840'}, 'is_local': False, 'primary_color': None, 'track': None, 'video_thumbnail': None}

It looks like the track object of songObject of Taylor Swift - Love Story, but I don't know how that's possible.
I'm also unable to find the song in the playlist on Spotify.
{'added_at': '2020-01-22T08:43:17Z', 'added_by': {'external_urls': {'spotify': 'https://open.spotify.com/user/pm5gmrz0rm7b3eayz8aa51840'}, 'href': 'https://api.spotify.com/v1/users/pm5gmrz0rm7b3eayz8aa51840', 'id': 'pm5gmrz0rm7b3eayz8aa51840', 'type': 'user', 'uri': 'spotify:user:pm5gmrz0rm7b3eayz8aa51840'}, 'is_local': False, 'primary_color': None, 'track': None, 'video_thumbnail': None}

I'm running into this interesting error:
Searching for: Taylor Swift - Love Story
Traceback (most recent call last):
  File "c:\program files\python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\program files\python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\jayde_000\AppData\Roaming\Python\Python39\Scripts\spotdl.exe\__main__.py", line 7, in <module>
  File "C:\Users\jayde_000\AppData\Roaming\Python\Python39\site-packages\spotdl\__main__.py", line 110, in console_entry_point
    songObjList = get_playlist_tracks(request)
  File "C:\Users\jayde_000\AppData\Roaming\Python\Python39\site-packages\spotdl\search\utils.py", line 83, in get_playlist_tracks
    'https://open.spotify.com/track/' + songEntry['track']['id'])
TypeError: 'NoneType' object is not subscriptable
  0%|          |ETA: ?, ~min/song```

I'm running into this interesting error:
Searching for: Taylor Swift - Love Story
Traceback (most recent call last):
  File "c:\program files\python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\program files\python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\jayde_000\AppData\Roaming\Python\Python39\Scripts\spotdl.exe\__main__.py", line 7, in <module>
  File "C:\Users\jayde_000\AppData\Roaming\Python\Python39\site-packages\spotdl\__main__.py", line 110, in console_entry_point
    songObjList = get_playlist_tracks(request)
  File "C:\Users\jayde_000\AppData\Roaming\Python\Python39\site-packages\spotdl\search\utils.py", line 83, in get_playlist_tracks
    'https://open.spotify.com/track/' + songEntry['track']['id'])
TypeError: 'NoneType' object is not subscriptable
  0%|          |ETA: ?, ~min/song```

I found the song it's the 357 entry in the list.
I don't see anything particular with the song, but the Spotify Python API is unable to retrieve any information about the song.

I found the song it's the 357 entry in the list.
I don't see anything particular with the song, but the Spotify Python API is unable to retrieve any information about the song.

Thats very weird that it would happening. I haven't looked at the code base yet but would surrounding it in a try catch statement help

Thats very weird that it would happening. I haven't looked at the code base yet but would surrounding it in a try catch statement help

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

That's a different thing. This has something to do with the spotify api rather than ytmapi.

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

That's a different thing. This has something to do with the spotify api rather than ytmapi.

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

That's a different thing. This has something to do with the spotify api rather than ytmapi.

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

That's a different thing. This has something to do with the spotify api rather than ytmapi.

Could you try adding this block before line 82 in utils.py
if songEntry is None:
    continue

Could you try adding this block before line 82 in utils.py
if songEntry is None:
    continue

I think we should compare songEntry with None before subscripting it.
Try adding this before line 82 in utisl.py
if songEntry is None:
    continue

I think we should compare songEntry with None before subscripting it.
Try adding this before line 82 in utisl.py
if songEntry is None:
    continue

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

Yes, The error raised is the same one. Because when we don't filter out songs, some of the results don't have keys like 'videoId' in them.
But here, the cause is the spotify API and not ytmapi.

This is the same thing that happens when we stop filtering the ytm results of I'm not wrong.
cc:@s1as3r

Yes, The error raised is the same one. Because when we don't filter out songs, some of the results don't have keys like 'videoId' in them.
But here, the cause is the spotify API and not ytmapi.

@kyleharte could you check if all the songs in that playlist are available in your country?

@kyleharte could you check if all the songs in that playlist are available in your country?

It's my playlist, so it definitely would be.

It's my playlist, so it definitely would be.

I think we should compare songEntry with None before subscripting it.
Try adding this before line 82 in utils.py
if songEntry is None:
    continue

Could you try this?

I think we should compare songEntry with None before subscripting it.
Try adding this before line 82 in utils.py
if songEntry is None:
    continue

Could you try this?

Ah my bad. It's not the song Love Story that's the problem. But the song after that.
It looks like there is a song in between Love Story and Say Na Na Na, which also is not shown on the Spotify Website.
I found a similar issue on spotify/spotipy (See: https://github.com/plamere/spotipy/issues/626)
@kyleharte you can skip any missing tracks by inserting this if statement on line 82 of utils.py, until it's fixed.
if songEntry['track'] is None:
    continue

Ah my bad. It's not the song Love Story that's the problem. But the song after that.
It looks like there is a song in between Love Story and Say Na Na Na, which also is not shown on the Spotify Website.
I found a similar issue on spotify/spotipy (See: https://github.com/plamere/spotipy/issues/626)
@kyleharte you can skip any missing tracks by inserting this if statement on line 82 of utils.py, until it's fixed.
if songEntry['track'] is None:
    continue

Hey @bee395, could you open a PR to hotfix with that change please

Hey @bee395, could you open a PR to hotfix with that change please

Hey @bee395, could you open a PR to hotfix with that change please

I created a pull request.

Hey @bee395, could you open a PR to hotfix with that change please

I created a pull request.

I also get this error when downloading any song.
Running on repl.it, is that the problem?

@JavaScythe This specific issue is resolved on v3.2.2.
However, repl.it does not support FFmpeg, so you cannot use spotDL there.

Fixed in v3.3.2


Alpine 3.16 Update

Is there a particular reason why alpine docker files use php:8.1.8-cli-alpine3.15 image?
I could propose a PR with 3.16 version.

Thanks for the suggestion. I added two commits today to update latest images to use Alpine 3.16, and included you as a co-author of the commits, as you can see from commit messages.
Please note that the change applies to latest images and future images (Swoole 5.0.1+ images), but not existing images.


Connect to AWS and On-prem services from AKS deployed karavan

I have deployed the karavan in azure aks cluster, I want to connect to AWS and on-prem services from that. Can it be done ? If yes then how can I do that.

There is no any limitations in Karavan and Camel to connect from AKS to On-Prem or AWS using Kamelets or Components.
Any particular system/services you connect and have issue with?


via cqlsh not possible to escape special characters such as ' when used as FILTER for UPDATE

This is a copy of scylladb/scylla#6165
Summary of the problem is that in certain situations a pg style string that
contains single quotation mark is miss parsed in cqlsh and causes it to wait for more
input, the example in the issue was:
UPDATE pi.upui SET createddate='1974-10-17 00:00:00.00+0000' WHERE upuishort=$$uyuyueyy'euyruwey$$;
For more details refer to  scylladb/scylla#6165

@slivne @avikivity Could you, please, give me "labelling" permissions for this repo?


Merge pull request #46 from davewalker5/main

Merge Main Back Into Sonar Fixes Branch

Codecov Report

Merging #47 (e773d19) into main (91126c7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #47   +/-   ##
=======================================
  Coverage   97.83%   97.83%
=======================================
  Files          57       57
  Lines        2767     2767
  Branches      400      400
=======================================
  Hits         2707     2707
  Misses         41       41
  Partials       19       19

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 91126c7...e773d19. Read the comment docs.


fix index of table

Hi,
as it is now, the output table index from 1. However, nushell index from 0, so doing stuff like net | get 1 actually gives the row with index 2.
Regards,

Ahh, I didn't even realize this! Apparently setting the index field of a record will modify it's table index. I'll push an update that will add an if_index instead of using the apparently special index


Add Apache Iceberg IO connector

Apache Iceberg is an open table format layer on top of different filesystems.
Beam could support it in the form of an IO connector ideally integrating with Beam's own system for SQL support.
Inspiration can be taken from the ongoing effort to support Iceberg on Flink:
https://github.com/apache/iceberg/issues/788
https://docs.google.com/document/d/1idTjQCubhOCea8LkKJ_5aMTV4V_Wf1n0aYhabGsLQZc/edit
Imported from Jira BEAM-10160. Original Jira may contain additional context.
Reported by: iemejia.

any updates?

any updates?

any updates ?

@gabrywu , @yupbank , @yeshvantbhavnasi -- nobody is assigned [ therefore potentially not being worked on ], so not clear how quickly this will progress.  That said, it is also open, and therefore something that anyone could work on and contribute.  Contributions welcome!  :-)

hi folks - I am taking a look at this...

Hey folks, is there any plans regarding this?

@pabloem ping from Spotify

Affirm interested in this  👀  cc @lydian

CC: @mosche

There was some work on Sink for iceberg by @Fokko
https://github.com/apache/iceberg/pull/1972
@Fokko do you have any info about this, has someone tried to build on your work to get Beam + Iceberg working together?

That was some early work, and probably I would just start from scratch. I would take inspiration from the Kafka-connect repository: https://github.com/tabular-io/iceberg-kafka-connect

we use iceberg low-level API adding data files directly

Wanted to check in on this, is beam prioritizing this?

No chance guys unless google have plans.

@RPasecky -- it is less 'beam' prioritizing, and a question of whether any individuals are prioritizing.  I'd love for this to exist, but can't devote the time.  Hopefully someone will.  Contributions welcomed!  :-)

Added in #30797 and released in version 2.56.0

Awesome! This is a great milestone! Thanks for working on this 🎉


merge from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 -x 'tests/**/*' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(package): add main from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/*-test.mjs' as in template
chore(package): set $.ava.extensions='mjs' as in template
chore(package): remove unknown value for main ({{main}})

Pull Request Test Coverage Report for Build 2318

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.509%

Totals

Change from base Build 2315:
0.0%

Covered Lines:
361

Relevant Lines:
375

💛  - Coveralls


Config file for server

Is there a way to edit the percentage chance of getting banglum chunk and what is the correct way to mine banglum ores, ive tried normal diamond pickaxe out of 64 blocks 5 exploded and 0 banglum and a pickaxe with fortune 3 all exploded.

The chance of getting a Banglum Chunk is determined by its loot table. You can tweak this to your liking using a datapack.
Generally the best way to get chunks involves:

Not using Fortune. While it does five you more Banglum, it negatively affects your chances of getting chunks (since the ores can explode)
Using a Mythril Drill with the Banglum Defuser upgrade
Bringing Nether Banglum ores to the overworld. Nether Banglum has a much higher chance to give you a chunk. The explosion chance is directly affected by the dimension the ore is in. However, you can (usually) safely mine it using Silk Touch, which will further help in not exploding the ores


GraphQL Support

I'm thinking about adding GraphQL support. I'd like to hear some of your thoughts on it, feel free to criticize.  The idea is to keep both the REST and GraphQL modes.
Our current REST model is also flexible in a way that it already supports a good subset of a GraphQL server.
We would need to export a /graphql endpoint that routes to a Java GraphQL Schema. The schema could be created directly from the same way we declare models today with the help of some Java GraphQL library like: https://github.com/graphql-java/graphql-java

I think it's a very good ideal. GraphQL and Relay are a very nice way to fetch data from the server using a component driven front-end.
Also it increases the readability of queries on the front-end, since JSON.

Started development on graphql branch. Right now it creates a schema with a field at the root level for every endpoint; this field returns a list of that endpoint, and receives optional arguments for filtering, just like the /people route would.
There is much more to do though, like: complex queries, security using shields, actions, transformer & hooks, et cetera.
I'm slowly working towards it :)

+1


warn if generation prompt does not start with a control code

@julien-c great idea, totally get your commit, but how is the control code/token identified right now in the master branch? I don't get how control_codes.txt is being referenced from generate.py right now? Or am I missing something? I'm pretty sure I setup everything right on my V100, but the master branch just doesn't work (runs, but copies the last word over and over, so likely it doesn't see my control code) while the lower_memory branch works just fine. Totally lost to be honest...

Did you try all the different models? Maybe it's an issue with a specific one?

A control code is just a token. So if you start with Joke A man comes into a bar "Joke" is just a token like the other ones. Not sure I can help on debugging your specific issue though. Good luck!

@julien-c thanks a lot, will try running your code, maybe it’ll work. Just strange why my setup doesn’t;to see control code on the master branch.

@julien-c I’ve got an idea about what might be wrong. I think I might be patching the wrong keras.py file. Can you share the path of this file you are patching (as your setup is GCP with V100, just like mine). Im also using Anaconda Python 3.7 virtual environment setup.

Thanks for the PR @julien-c !
@dimitri320 , you should patch wherever tensorflow_estimator is. You can find this by
>>> import tensorflow_estimator
>>> tensorflow_estimator.__file__


Areas of Effect v1.0

A script that lets GMs let their players create graphical areas of effect for their spells and powers!

Where did the graphics for this script come from? Are they self owned, licensed, or creative commons?

I created the graphics. They are free for public use.

Thanks for the quick response.


Problem With adding support to iframe

Hi I use this code to add support to youtube iframe for the player
<script>
        jQuery(function ($) {
            $('video, audio, iframe').mediaelementplayer({
                stretching: 'responsive'
            });
        });

    </script>

The problem is that it start adding the player to every element that has iframe tag so can you provide any other code which only add support to YouTube dailymition   facebook and other suppoerted only instead of every element that has iframe

For example it start adding support to google ads and jetpack comment system facebook page box

Just use a specific class for your iframes (i.e., class="media-player") or an attribute (i.e., data-player="true"):
jQuery(function ($) {
     $('video, audio, iframe[data-player], iframe.media-player').mediaelementplayer({
          stretching: 'responsive'
     });
});

@rafa8626 Thank you very much for reply
Hi It works but I can't edit more than 2k post and add a class just as you Shown above
I have post from dailymotion Facebook YouTube in normal iframe like this one

Is there any other way i can Exclude Google ads Facebook like box and jetpack comments without Editing every single post?

You may have to use selectors that target the src of iframes; something like this:
jQuery(function ($) {
     $('video, audio, iframe[src*=youtube.com], iframe[src*=daylimotion]').mediaelementplayer({
          stretching: 'responsive'
     });
});

@rafa8626 not working showing console error

Use quotes after *=; that should do it

@rafa8626  Still same issue

This worked for me:
jQuery(function ($) {
     $('video, audio, iframe[src*="youtube.com"], iframe[src*="daylimotion"]').mediaelementplayer({
          stretching: 'responsive'
     });

Can You check this url https://newsa2.com/smallfoot-teaser-trailer-1-2018-movieclips-trailers/
Not working for me whats creating the problem ?

You have a Uncaught SyntaxError: Unexpected end of input so one of your inputs in the markup is not closed properly. I can't assist you more since this is not MEJS related anymore.

This Is script im using I just copied as you wrote Sorry i know its frustating
Here is The code
<script>
      jQuery(function ($) {
     $('video, audio, iframe[src*="youtube.com"], iframe[src*="daylimotion"]').mediaelementplayer({
          stretching: 'responsive'
     });

    </script>

@rafa8626  Solve  Thank You Very Much Sorry Im Just started to learn jquery so I hard for me understand few things
 jQuery(function ($) {
     $('video, audio, iframe[src*="youtube.com"], iframe[src*="daylimotion"]').mediaelementplayer({
          stretching: 'responsive'
     });
     });


Problems tab of Appsmith console/debugger

Description
We can use this PR to discuss code design and flow of the actionable errors for the upcoming console.
I opened it here because github review comments are easy-ish to work with. If you want me to do this on Miro/Notion, feel free to leave a comment.
cc: @hetunandu

@ofpiyush initial thoughts and to make sure I'm getting the scenarios:
Error scenarios:

JS errors, ex.

Undefined variable (key of undefined)
Syntax errors

Validation errors
Cyclic dependency
Auth (future use cases)
Error response on action execution

Contexts associated with them:

Widget (multiple incase of cyclic dependency)

Property

API
Query

Actions that can be taken by the user:

Navigate to/focus context

Info:

JS stack
Formatted message
Resulting action (do we have UserAction for this purpose?)

So based on this:

For the info part we can use arrays and key-value pairs, we can finalise on a simple format like

{ message: “”, params: {}, e: Error object }

Handling JS errors stack: I suppose in the future we could also allow users to link to the file from where the error was thrown
For navigating to the widget we could have an action type constant and some params (type: API/QUERY/WIDGET, otherData: {}) that a util could use and handle the logic

@ofpiyush initial thoughts and to make sure I'm getting the scenarios:
Error scenarios:

JS errors, ex.

Undefined variable (key of undefined)
Syntax errors

Validation errors
Cyclic dependency
Auth (future use cases)
Error response on action execution

Contexts associated with them:

Widget (multiple incase of cyclic dependency)

Property

API
Query

Actions that can be taken by the user:

Navigate to/focus context

Info:

JS stack
Formatted message
Resulting action (do we have UserAction for this purpose?)

So based on this:

For the info part we can use arrays and key-value pairs, we can finalise on a simple format like

{ message: “”, params: {}, e: Error object }

Handling JS errors stack: I suppose in the future we could also allow users to link to the file from where the error was thrown
For navigating to the widget we could have an action type constant and some params (type: API/QUERY/WIDGET, otherData: {}) that a util could use and handle the logic

@rishabhsaxena Thank you for that! It's more or less correct. I'd started from a simple-ish format considering the debugger as the primary user.
But the more I worked on it, the more I agree with @Nikhil-Nandagopal's framing here.

Our goal is to build a database of problems with clean system readable metadata that any part of the system should be able to take and use either it's to display the error, write a rule on top of or give the user an action to take.

@Nikhil-Nandagopal w.r.t. previous, the plan was to plug into redux-saga as a middleware and leverage their effect tracking to build proper relationships between discreet events.
i.e. Appsmith engineers wouldn't need to manage the relationship between events. They just write something like recordLog(message) and all tracking just works magically behind the scenes.
I prototyped it and there's some weirdness in how redux-saga tracks effects, that makes it difficult/impossible to achieve this.
The trade off now is between user experience vs speed of implementation.
We can either:

Pass the metadata of a user initiated event around ourselves, spend some time enabling plumbing.
Log independent events as they come and the user will need to figure out the relationships manually.

What each path looks like in practice:
Log Independent events

Import the logger/ error global function and use it to record events/errors.
Developer user will see a chronological list of events and errors exactly like logs.

Plumbing for passing metadata
I'll try to find ways to make that easier, but in it's current form this is what plumbing will look like:

A new metadata object needs to be created on any user action with the first event.
This object can be attached to meta key of redux actions at dispatch.
We can auto-initialise an empty logger / clone existing logger on every dispatch.
Every function will need to create / pass this metadata around to gain the ability to add timeline events/errors.
Developer user will see the exact trace of events leading up to any error.

If we go down the plumbing route, it can be leveraged to enable better telemetry and structured traceable logging within the app for appsmith engineers as well.

@rishabhsaxena Thank you for that! It's more or less correct. I'd started from a simple-ish format considering the debugger as the primary user.
But the more I worked on it, the more I agree with @Nikhil-Nandagopal's framing here.

Our goal is to build a database of problems with clean system readable metadata that any part of the system should be able to take and use either it's to display the error, write a rule on top of or give the user an action to take.

@Nikhil-Nandagopal w.r.t. previous, the plan was to plug into redux-saga as a middleware and leverage their effect tracking to build proper relationships between discreet events.
i.e. Appsmith engineers wouldn't need to manage the relationship between events. They just write something like recordLog(message) and all tracking just works magically behind the scenes.
I prototyped it and there's some weirdness in how redux-saga tracks effects, that makes it difficult/impossible to achieve this.
The trade off now is between user experience vs speed of implementation.
We can either:

Pass the metadata of a user initiated event around ourselves, spend some time enabling plumbing.
Log independent events as they come and the user will need to figure out the relationships manually.

What each path looks like in practice:
Log Independent events

Import the logger/ error global function and use it to record events/errors.
Developer user will see a chronological list of events and errors exactly like logs.

Plumbing for passing metadata
I'll try to find ways to make that easier, but in it's current form this is what plumbing will look like:

A new metadata object needs to be created on any user action with the first event.
This object can be attached to meta key of redux actions at dispatch.
We can auto-initialise an empty logger / clone existing logger on every dispatch.
Every function will need to create / pass this metadata around to gain the ability to add timeline events/errors.
Developer user will see the exact trace of events leading up to any error.

If we go down the plumbing route, it can be leveraged to enable better telemetry and structured traceable logging within the app for appsmith engineers as well.

Check out #2611 for POC of how a full trace solution could look like.

Check out #2611 for POC of how a full trace solution could look like.

Need the ability to add html links for documentation.
Should we start looking at shared error codes between server and client? (Also see #2626)

Need the ability to add html links for documentation.
Should we start looking at shared error codes between server and client? (Also see #2626)

@ofpiyush the independent logging route might not make sense. If we look at our debugger #1236
there is a tab that needs to display a list of static errors. So even if you log table1.tableData is in error state 10 times, this tab will just show that table1.tableData is in error state, this is the error line, it's a data type error or a syntax error.
There is also a tab that has the stream of events. This tab may or may not choose to show that the table data went into an error state. This should be controllable otherwise a user's log stream becomes populated with tons of event data which is unreadable unless you really know the system well (our console log is this today). So we should be able to say
error.type === "WIDGET_PROPERTY" && !error.isSyntaxError && error.isDataTypeError to quote a random example and change this as we learn more. We may also want to display button which links to the table from this error or we may not.

@ofpiyush the independent logging route might not make sense. If we look at our debugger #1236
there is a tab that needs to display a list of static errors. So even if you log table1.tableData is in error state 10 times, this tab will just show that table1.tableData is in error state, this is the error line, it's a data type error or a syntax error.
There is also a tab that has the stream of events. This tab may or may not choose to show that the table data went into an error state. This should be controllable otherwise a user's log stream becomes populated with tons of event data which is unreadable unless you really know the system well (our console log is this today). So we should be able to say
error.type === "WIDGET_PROPERTY" && !error.isSyntaxError && error.isDataTypeError to quote a random example and change this as we learn more. We may also want to display button which links to the table from this error or we may not.

I'm slightly wary of classifying static vs dynamic errors.
Mostly because of the example:
[Dropdown1] options does not evaluate to type array < label: string, value, string>

Given one can write conditionals in Dropdown1.options, it can be either static or dynamic in some cases.
For example the same dropdown can depend on multiple things and have conditionals that break because of different reasons:

Table1 is undefined. (should be static?)
Api1.data.map((r)=>({label: r.text, value: r.id})) might have timed out. (should be dynamic?)

What was the intent of drawing the distinction?

I'm slightly wary of classifying static vs dynamic errors.
Mostly because of the example:
[Dropdown1] options does not evaluate to type array < label: string, value, string>

Given one can write conditionals in Dropdown1.options, it can be either static or dynamic in some cases.
For example the same dropdown can depend on multiple things and have conditionals that break because of different reasons:

Table1 is undefined. (should be static?)
Api1.data.map((r)=>({label: r.text, value: r.id})) might have timed out. (should be dynamic?)

What was the intent of drawing the distinction?

We don't need error ids, property path from source can be used to track and resolve errors.
Every property will need to broadcast that it's not broken anymore.

We don't need error ids, property path from source can be used to track and resolve errors.
Every property will need to broadcast that it's not broken anymore.

@Nikhil-Nandagopal has decided to go with Log Independent events route for now. If we need to, we'll build trace-ish route later.

@Nikhil-Nandagopal has decided to go with Log Independent events route for now. If we need to, we'll build trace-ish route later.