Allow errors to throw

Searched around a bit for this so if anything hopefully this is helpful as documentation.
Wondering why mobx catches and shows a warning on errors:
[mobx] An uncaught exception occurred while calculating your computed value, autorun or transformer. Or inside the render() method of an observer based React component. These functions should never throw exceptions as MobX will not always be able to recover from them. Please fix the error reported after this message or enable 'Pause on (caught) exceptions' in your debugger to find the root cause.

We use a few libraries in our stack, three of which trigger "fake" exceptions on startup. Beyond that, the warnings here remove all stack trace.
So the process for debugging becomes extremely tedious. It goes from clicking a stack trace, to reading a big warning to find the small "In: " area, and then going to sources, hitting pause, hitting catch (also, on a Macbook, sources is very slow, so this process takes a while), then pushing through 3-4 exceptions to find the right one.
To me, this is one of the biggest problems with mobx. Others we are patching around and will try and release tools for, but just curious what's the rationale behind this one and can it be avoided?
I noticed there used to be a globalError function, what happened to that? Don't see any mention in changelog.

Hi @natew, in principle this should not make a difference in debugging, this message is not a catch but a finally, basically:
try {
  hasError = true;
  render()
  hasError = false;
} finally {
  if (hasError) printWarning()
}

Note that in chrome at least you can blackbox scripts which can be a huge help to filter out unrelevant exceptions. But hitting "break on exception" should bring you at a proper that should be fixed. MobX at least will not track functions that throw exceptions so behavior might become unexpected.
That being said it confuses more people, so maybe I will remove the log message anyway

I think using console.warn instad of console.error might help. Because people can simply not notice actual thrown error under console.error message.

@andykog changed it two weeks ago to warnings indeed, so that should be case already in the latest versions.

@natew, are you using fresh mobx-react version? Is it possible that you didn't notice actual error? Can you show minimal example if the error is really being swallowed in some cases?

Please don't remove that message. I run into some edge cases when exception from render is swallowed, and this warning is the only thing that's left. So far, I've not been able to reproduce it in a JSFiddle, but I suspect it can be because of combination with other libraries async stuff

TypeScript version seems to throw as well: https://jsfiddle.net/Sl1v3r/ko1s4xbx/
To fix this problem we need to reproduce it somehow, your help would be appreciated.

You are right, it's not typescript. I'm now trying crazy stuff to reproduce it to no avail. For me, right now it breaks when I do the failing render from a promise catch inside axios call (quite an edge case). Can you maybe see it here?
https://sm-web-widget-pr-1.herokuapp.com/?query=Test company&mode=Login
just fill something and click on login.

The POST https://sm-api-eu-west-staging.herokuapp.com/register 400 (Bad Request) exception is NOT it. The actual happens inside job-form.tsx, line 52
Apply to {job.title}

@tomaash, well, if you are doing render stuff in Promise#catch, this behaviour is quite expected. You can rethrow catched error, if you want it to appear in console:
Promise.resolve()
   .then(somethingThatCousesRender)
   .catch(e => {
      throw e; // <-- rethrow the error
   })

I don't actually render from the promise catch. I just change some observable values inside the catch handler. The error is thrown from render function, and disappears.

For example this works for me:
    axios.post('fooo', { a: 1 }).then((ok) => {
      console.log('stuff')
    }).catch(() => {
      this.problem = null
    })

  render() {
    const {trans} = this.props

    return (

{this.problem.foo}

even in this case, the error IS rethrown. So the case I'm having elsewhere is some super-edge case. I'll post here when I'll be able to do some minimal reproduction.

Changing observable value may cause synchronous re-rendering, so the error is catched.
Here is a simplified example: https://jsfiddle.net/Sl1v3r/32n59gfu/
So I don't think there is a way to solve this.
What I'm thinking about is providing stack trace in mobx warning. Will it solve your problem?

Yes please! That would totally solve the problem.
On Fri, Jul 29, 2016 at 12:52 PM, Andy Kogut<EMAIL_ADDRESS>wrote:

Changing observable value may cause synchronous re-rendering, so the error
is catched.
Here is a simplified example: https://jsfiddle.net/Sl1v3r/32n59gfu/
So I don't think there is a way to solve this.
What I'm thinking about is providing stack trace in mobx warning. Will it
solve your problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/83#issuecomment-236151770,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABLoGuuSO2-e_opIuG1b3Udcdnj6EXIks5qadtegaJpZM4JLFLQ
.

I realized, that stack trace (via console.trace() or new Error().stack) alone can help only partionally, because you won't see error message. So I made PR, that includes original error (with stack trace) in the warning: https://github.com/mobxjs/mobx/pull/447

there is one potential issue with the error catch. if i remember correctly
(should test that to be sure) the rethrow will produce a fresh stacktrace
on the error. this means that clicking the error in the log or break on
uncaught exception will lead to the mobx throw statement instead of the
root cause i think? that might make it harder instead of easier to find the
original cause? sadly JS has no caused by... like java ...
Op za 30 jul. 2016 16:25 schreef Andy Kogut<EMAIL_ADDRESS>
I realized, that stack trace (via console.trace() or new Error().stack)
alone can help only partionally, because you won't see error message. So I
made PR, that includes original error (with stack trace) in the warning:
mobxjs/mobx#447 https://github.com/mobxjs/mobx/pull/447
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/83#issuecomment-236368020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvGhIpCpwY5LP3q0UxJSv46e7qPP9qGks5qa17wgaJpZM4JLFLQ
.

Nope:
function foo() {
  function bar() {
    throw new Error('FooBarError');
  }
  bar();
}

(function aaaaaaaaa() {
  try {
    foo();
  } catch (e) {
    (function bbbbbbbb() {
      throw e;
    }());
  }
}());

Uncaught Error: FooBarError
    at bar (<anonymous>:3:11)
    at foo (<anonymous>:5:3)
    at aaaaaaaaa (<anonymous>:10:5)
    at <anonymous>:16:2

ah cool and without error constructor? might it differ per engine? probably
not I guess.  and where does the debugger break?
Op za 30 jul. 2016 17:13 schreef Andy Kogut<EMAIL_ADDRESS>
Nope:
function foo() {
function bar() {
throw new Error('FooBarError');
}
bar();
}
(function aaaaaaaaa() {
try {
foo();
} catch (e) {
(function bbbbbbbb() {
throw e;
}());
}
}());
Uncaught Error: FooBarError
at bar (:3:11)
at foo (:5:3)
at aaaaaaaaa (:10:5)
at :16:2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/83#issuecomment-236370436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvGhAbEl_LxE-eGX8_XgRv7NrWntL7nks5qa2oYgaJpZM4JLFLQ
.

Tested in Crome, Safari, Firefox. But I'm sure without testing, that debugger will break at second throw as executing of foo() is inside try {} block. (unless you check «Pause on caught exceptions») :-(

Closed my PR. @tomaash, I don't see any worthwhile option but that you log errors inside your own Promise#catch (I guess, you're using Promises, right?)

Btw if there are any ideas on how the message it self can be improved to avoid these kinds of issues, let me know! I'm thinking maybe on adding an link with additional explanation, similar to how React usually does this

It would be helpful to inform the user of the synchronous errors in render, that can be unintuitively caught by your own catch block. The message is already quite long, so maybe a link to some stack overflow page or something like that would be sufficient. How about something like this?

[mobx] An uncaught exception occurred while calculating your computed value, autorun or transformer. Or inside the render() method of an observer based React component. These functions should never throw exceptions as MobX will not always be able to recover from them. Please fix the error reported after this message or enable 'Pause on (caught) exceptions' in your debugger to find the root cause. If you cannot see the error below, it was most probably caught by your own code. This can happen e.g. when synchronous update to an observable (which causes a render error) is triggered from a promise handler with a successive catch block.

Will explain further details in https://github.com/mobxjs/mobx/issues/462, and link to that error from the error message.

👍


MM-30878 Change format of dates that are not this year

Summary
Changes incident create date format if year is different than the current year.
Ticket Link
https://github.com/mattermost/mattermost-server/issues/16399

Hello @berkeka,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Great! But I think we need to do the same for endedAt below.

@crspeller Do we still want show "--" for incidents that were created before 2020-01-01?

@berkeka I think that's a backwards compatibility thing. So we should keep that.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

/update-branch

Ready to test!

/update-branch


is operator for QDM entity type

Support for the "is" operator for QDM entities was raised in cql-execution issue 269 but it will require implementation in cqm-models

this is fixed in https://github.com/projecttacoma/cqm-models/pull/207.

https://github.com/projecttacoma/cqm-models/pull/207 is merged. closing this.


itertracks() doesn't work properly in 0.1.1

itertracks() doesn't work properly in 0.1.1. problems:

Hyperparameters onset/offset doesn't work properly, for example in the output there are segments shorter than "onset".
Looks like segments in time skew to front.
Segments overlap.

Audio to test:
audio.mka_dump.zip
UPDATE:
I thought that onset/offset corresponds to "min_duration_on"/"min_duration_off".
onset/offset shouldn't be touched for pyannote/segmentation-3
"min_duration_on"/"min_duration_off" could be set in some very first version of pyannote-onnx , can you add them back?

You could try sherpa-onnx with pyannote-audio.

You could try sherpa-onnx with pyannote-audio.

I tried it but it doesn't have "min_duration_on"/"min_duration_off" implemented too, btw, it works very well, almost same output as original pyannote segmentation.
Another thing it's slow, ~same speed as pyannote's torch version, when your repo is ~4 times faster.

OK, I will try to add "min_duration_on"/"min_duration_off".
This repo is faster because I use a large step: https://github.com/pengzhendong/pyannote-onnx/blob/bcd0a7f0ce9807436a886a0d6b8b3f3284ecd724/pyannote_onnx/pyannote_onnx.py#L108

step = self.duration // 2

Tested step = self.duration // 10 it got slower only ~10%


Managing CPM support in CSV

Adding support to manage (Add / Update) the Managing CPM when using CSV
Omitting the Managing CPM will take the defaults when creating or will not change it when updating

Relevant for #68


[Bug]: Close button appears on different row div

What happened?
After creating a banner with option "banner can be closed by user" selected, the close button appears on different row div

How to reproduce the bug

Go to banner manager
Create a banner
Select option "banner can be closed by user"
See the banner with close button in different row div

Package Version
0.0.9
PHP Version
8.2
Laravel Version
11.23.5
Which operating systems does with happen with?
Windows
Notes
No response

Hi thanks for reaching out.
Did you runnpm run dev?

In the examples above I didn't run that command but I tried to run it now and I still have the same bug

Could you please go to the banner manager page and send a screenshot of that page?

Sorry for the delay, a lot of work..
Here you go

No problem, thanks.
Do you use a custom theme? And have you followed all the steps of section 2 of the installation part?
https://github.com/kenepa/banner?tab=readme-ov-file#installation

I just redid all the steps and solved it, thank you for your support!


Set just flags through environment variables

Configure clap to set some configuration options via JUST_<name> environment variables.
Resolves https://github.com/casey/just/issues/1979 and https://github.com/casey/just/issues/1934

Looks good to me! Can you add a section in the readme which documents the fact that some options can be set via environment variables? I think we probably shouldn't list the specific options which can be set, since users can look in the --help message to see what exactly is supported.

LGTM!


Specs intermediate nodes

This PR refactors the specs introducing the intermediate property. This property allows other components such as conditions and references to avoid abusing the specs.Call implementation.

Codecov Report

Merging #104 into master will decrease coverage by 0.05%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master     #104      +/-   ##
==========================================
- Coverage   83.29%   83.24%   -0.06%
==========================================
  Files          65       65
  Lines        4281     4279       -2
==========================================
- Hits         3566     3562       -4
- Misses        448      449       +1
- Partials      267      268       +1

Impacted Files
Coverage Δ

pkg/flow/node.go
83.46% <ø> (ø)

pkg/lookup/lookup.go
87.75% <0.00%> (-1.22%)
:arrow_down:

pkg/specs/flows.go
93.82% <ø> (ø)

pkg/references/forwarding/references.go
67.94% <75.00%> (ø)

pkg/dependencies/dependencies.go
86.20% <100.00%> (ø)

pkg/providers/hcl/specs.go
76.26% <100.00%> (-0.21%)
:arrow_down:


cluster configuration not found error

Hello,
i have a trouble when i create the kubeconfig for developers on my Macbook.
I have tried to create with 0.31 version, and 0.29.

kubectl-kc create
WARNING: This feature is only supported in kubernates v1.24 and later.
user name: developer
😸 Select:kubernetes-admin@kubernetes
🚀  Namespace: dev is selected.
CSR: developer create success
CSR: developer has been approved
😸 Select:admin
RoleBinding : developer-admin create success
Error: cluster configuration not found
Usage:
kubecm create [flags]

Examples:
Create new KubeConfig(experiment)
kubecm create
Create new KubeConfig(experiment) with flags
kubecm create --user test --namespace default --cluster-role view --context-name kind-kind
Flags:
--cluster-role string   cluster role for user
--context-name string   context name for kubeconfig
-h, --help                  help for create
-n, --namespace string      namespace for user
--print-clean-up        print clean up command
--user string           user name for kubeconfig
Global Flags:
--config string   path of kubeconfig (default "$HOME/.kube/config")
-m, --mac-notify      enable to display Mac notification banner
-s, --silence-table   enable/disable output of context table on successful config update
-u, --ui-size int     number of list items to show in menu at once (default 4)
cluster configuration not found
Despite, i have kubeconfig that is working properly:

kubectl config view
apiVersion: v1
clusters:

cluster:
certificate-authority-data: DATA+OMITTED
server: https://REDACTED:6443
name: kubernetes
contexts:
context:
cluster: kubernetes
namespace: dev
user: kubernetes-admin
name: kubernetes-admin@kubernetes
current-context: kubernetes-admin@kubernetes
kind: Config
preferences: {}
users:
name: kubernetes-admin
user:
client-certificate-data: REDACTED
client-key-data: REDACTED

kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:51:05Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.8", GitCommit:"66fee42707cd7f5a89f1987f7cb81b02dd19161c", GitTreeState:"clean", BuildDate:"2023-11-15T16:50:09Z", GoVersion:"go1.20.11", Compiler:"gc", Platform:"linux/amd64"}

You appear to be using the kubectl plugin version of kubecm. Could you try using it as a binary? You can install kubecm using brew install kubecm.

update: I haven't reproduced the problem so far. If you have new inputs, please leave them in the issue. Thank you very much!

Here is my cluster list

I want to create a role named logn. The error prompt shows: cluster configuration not found

This is my cluster configuration, and the cluster appears to exist

These are the commands I executed, and I have already performed corresponding deletion statements multiple times
kubecm create --print-clean-up  --user logn --namespace sre --cluster-role view --context-name apps-k8s

@logn-xu Thanks for the feedback, I'll try to reproduce it and fix it.


Feat: Add valinet.ExplorerPatcher.Prerelease

[x] Have you verified that a previous version of the package is already there in the Windows Package Manager Community Repository?
[x] Have you validated the JSON with the JSON Schema?
[x] Have you verified that the values entered in the JSON are correct?
[x] The commit message follows the conventional commits guidelines.

⧗   input: Feat: Add valinet.ExplorerPatcher.Prerelease
✖   subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]
✖   type must be lower-case [type-case]
✖   type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]


Undefine base_type macro to avoid conflict with boost type

This is quick PR that removes base_type macro from plugin files. It helps to prevent boost error message during compilation that started to appear in recent build.

Begin/end header files added. @dictoon could you check if I understood correctly?


fix: isHostname reports malformed IPv6 addresses as valid

Previous version of the function was reporting addresses like ]::1[ or even ]:]:]1] as valid.

@lidel - this is a follow-up from https://github.com/ipfs-shipyard/ipfs-companion/pull/945 - mind having a look? Thanks!

Like this?


Remove inlined css from external css files

I use critical to inline the critical css. How can I instruct to remove from the external css files the inlined css? in addition to the unused css in the css files?

Sorry, that's out of scope for this project. This project removes unused css. It does not remove used-but-already-listed-in-a-different-file css.
You may be interested in looking at postcss to do what you want: manipulating a css file. It's what uncss uses internally.


Complete initial PDS App Bar widget for simple web deployment

@c-suh has already put a lot of work into a simple PDS App Bar that functions similarly to the Feedback Widget with minimal overhead to deploy at each of the nodes.
Here are some tasks I see remaining with the current widget deployed at pds.nasa.gov (these will need individual tickets defined once these tasks are solidified):

Migrate app bar widget to public github
Document how a node can deploy this widget
Work with DNs to deploy widget as appropriate

Rationale
Note: This has been bumped up in priority per conversations with Project Office.

Things to consider in the PDS app bar above what is already deployed

Log in button (primary) for user authentication
Settings icon (cog) for user settings (preferences, theme toggle)
Cart for products?

Initial thoughts:

move question mark to the left of 'Find a Node'
insert two icons in upper right for Login and Cart
have icon for Settings included in the dropdown for Login

per meeting today:
updates needed:

[ ] move app bar to Github public repo (https://github.com/NASA-PDS/pds-wds-web)
[ ] move question mark to the left of 'Find a Node'
[ ] update the icon with grayscale version (to be provided by @edwardbarraza )
[ ] remove bolding from P, D, S in spelling
[ ] removing NASA from "NASA Planetary Data System"
[ ] update colors to match current WDS color schemes (to be provided by @edwardbarraza )
[ ] update height, dimensions, and spacing to match current WDS (to be provided by @edwardbarraza )
[ ] update typography to match current WDS (to be provided by @edwardbarraza )
[ ] check app bar break points for mobile (to be provided by @edwardbarraza )
[ ] Document how a node can deploy this widget

punt to next delivery:

light / dark / settings / login
see-through app bar

Here is the icon in png format. It should be sized at 48 x 25 in the app bar.

Figma design file has been shared with @c-suh and @eddiesarevalo  - the page of interest is labeled App Bar 1.0

 'Info' icon from the design system

@edwardbarraza I'll send you a link to the changes; let me know if I've missed anything.

@c-suh is waiting for feedback from @edwardbarraza

The i icon currently has the following text in tooltip:
`Welcome to NASA's PDS
NASA's Planetary Data System (PDS) maintains and archives data from planetary missions dated from the beginning of space exploration through the concerted effort of nine teams geographically distributed around the U.S.
This bar indicates that you are within the PDS enterprise which includes 6 science discipline nodes and 2 support nodes which are overseen by the Project Management Office at NASA's Goddard Space Flight Center (GSFC). Each node is led by an expert in the subject discipline, supported by an advisory group of other practitioners of that discipline, and subject to selection and approval under a regular NASA Research Announcement.
Find a Node - Use these links to navigate to any of the 8 publicly accessible PDS Nodes.`
We have moved the tooltip next to the Find a Node dropdown and have created an association with that feature, so I say we ax the first bit of the tooltip text and just keep this:
`Find a Node - Use these links to navigate to any of the 8 publicly accessible PDS Nodes.
This bar indicates that you are within the PDS enterprise which includes 6 science discipline nodes and 2 support nodes which are overseen by the Project Management Office at NASA's Goddard Space Flight Center (GSFC). Each node is led by an expert in the subject discipline, supported by an advisory group of other practitioners of that discipline, and subject to selection and approval under a regular NASA Research Announcement.`
Tooltips should be short and informative - what we have is overly verbose. WDY think @jordanpadams?

@edwardbarraza looks good!

Other change requested but not on Figma:

[x]  have information show on hover, not select.
[ ]  hover should be persistent (on info body and icon)
[x]  info body shall show on top of the dropdown

@edwardbarraza and @jordanpadams please verify the gamma version before I push the changes.

Looks good! ✅

Updates specified in the comment above have been made operational. Changes will be pushed to a TBD repository.

@jordanpadams should we create a new repository for the app bar Catherine worked on ?

@tloubrieu-jpl apologies for not updating the comment. The updates have been pushed to an existing repository and packaged as release PDS WDS Web v0.0.1

Hi! This is awesome. Two minor things to note too:

The info icon is better as an svg:

<svg style="width:17px;height:17px;/* display: none; */" viewBox="0 0 24 24">
    <path fill="white" d="M13,9H11V7H13M13,17H11V11H13M12,2A10,10 0 0,0 2,12A10,10 0 0,0 12,22A10,10 0 0,0 22,12A10,10 0 0,0 12,2Z"></path>
</svg>

The pds-app-bar-dropdown ul uses the default user agent margin style and so sits below the app bar 16px by default.

Also, if sites were to implement informational banners, should those sit above or below the app bar?

I am happy to provide an SVG here, only Github doesn't support that type of file. Ideas?
Regarding informational banners, we haven't discussed what the informational banner would look like, but we should distinguish between PDS-wide banner style/placement and Node-Specific style/placement. TBD.

@edwardbarraza upload here as a ZIP. @c-suh can you make the quick update when you have a chance?

info_icon.zip

The svg above can be inline.

It's also good practice to include the attribute rel="noopener" on all the anchor links with target="_blank" as it stops the target page from referencing the previous page.

Oh, one other little thing worth looking into too (that the Earth daacs miss) is that, because the app bar renders after the page loads, the whole rest of the page jumps down suddenly (constantly refresh to see this more clearly).
A quick way to solve this is to require nodes that wish to load this way to also add something like:

to the top of their page to then populate it later.

Hi @tariqksoliman. Thank you for your suggestions! We have started to address them, and you will be able to track the status of these at the pds-wds-web repo.
Further suggestions or comments - the detailed the better - would be greatly appreciated there. Thank you for helping us (streamline the process to) improve this app bar!

Initial development has been released


Tray icon color channels are being incorrectly rendered

Describe the bug
The tray module is incorrectly rendering the color channels of the pixmaps provided by applications with tray icons.
To Reproduce
Steps to reproduce the behavior:

Update the config to include the tray module (very large icons make it easier to see)type: tray
icon_size: 128
prefer_theme_icons: false

Observe the tray icon in detail, and notice that it does not appear the same as the original icon viewed in an image viewer.

Expected behavior
The tray icon should be rendered the same way an image viewer would.
System information:

Distro: Arch Linux
Compositor: Hyprland
Ironbar version: f4e1e81

Configuration
start: []
center: []
end:
  - type: tray
    icon_size: 128
    prefer_theme_icons: true

Additional context
The GTK documentation here shows that the internal representation of their pixel data is RGBA, instead of the ARGB data that's being handled by modules/tray/icon.rs::get_image_from_pixmap
Screenshots
Rendered Icon:

Original Icon (Before it was scaled to 22x22 and back):

Can't believe nobody has spotted this before lol


Mention --tb=short?

Looks like adding --tb=short might make much nicer annotations, especially for long functions, could be worth mentioning in the README.

Is there a way to get the short traceback only inside the plugin, perchance?

Nevermind, I have an idea, will propose it tomorrow if it works.


[Bug]: Incorrect array initialisation with simultaneously changing global variables

Description
$title
Steps to Reproduce
import ballerina/io;

int a = 0;

public function main() {
    foo();
}

function foo() {
    int[] arr = [1, a, 3, bar(), a];
    io:println(arr);
}

function bar() returns int {
    a = a + 1;
    return a;
}

gives
[1,1,3,1,1]

But should give
[1,0,3,1,1]

Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

BIROptimizer removes the temp variables created for global variables.


💪♻ Refactor FE AuthService to use generated client

@matt-goldman - are you still going to work on this?

Re-assigning to @christoment


rakedb.lazy runs "up" changes in reverse order after "down" migration

I have rakedb.lazy multi-change migration, such as:
export default [
  change(async (db, up) => {
    console.log("change 1", up)
  }),
  change(async (db, up) => {
    console.log("change 2", up)
  }),
]

If I execute run(["up"]) then run(["down"]) then run(["up"]) again, the second up runs changes in reverse order:
change 1 true
change 2 true
change 2 false
change 1 false
change 2 true
change 1 true

It's probably reversing them in-place on down somewhere instead of making a copy with the reverse order.

rake-db 2.10.65

Thank you for catching it, indeed there was a mutable reverse that caused this, fixed in the latest update.


Throw unfound column

Add support for ColumnNotFoundError when using find*/update*/delete* () functions.

Only thing of interest is the src/metadata/EntityMeta.ts, everything is just transpiling to build all the files out.

Look here:
https://github.com/puzzlefin/typeorm/pull/26/files#diff-4bf9dddd6111e1c8ccad4ae59480520463c9cdd978df47e4b00e671579dcf79d


Support discovering PSR-17 factories from guzzlehttp/psr7 package

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
it depends on the outcome of the discussion

Deprecations?
no

Related tickets
fixes #164

License
MIT

What's in this PR?
In the next version of guzzlehttp/psr7 there will be support for PSR-17 (actually the feature has not been released yet), so I simply added support for discovering the factories.
Checklist

[x] Updated CHANGELOG.md to describe BC breaks / deprecations | new feature | bugfix

To Do
For the moment I added the new factories in the middle of the list instead of at the end. What this means is that suddenly the priorities of discovery will change and the guzzle/psr7 package will be preferred over the php-http/guzzle6-adapter, which may be considered a BC. Just let me know if I have to move the classes to the end of the list instead

@Nyholm @dbu is there anything left to do or can this be merged?


Alias 0 as ret value

This PR is to fix the problem that an op of alias_0 is used a return value, and offload_copy is false.
In this case, the output parameter is provided by a user. If the output shape is different from the alias ins shape, then there is an error since the buffer provided by user cannot be used as the alias ins output.
The fix is: if an op of alias 0 is used as a return value, and the op element_space is different from the element_space of its alias ins, we need to add a contiguous after the the op, so the alias output is allocated by the program, and user only needs to provide the output param to be used as the output to the contiguous.
This PR also refines the instruction index when printing a program. Current implementation is count only the instructions (param and literals are ignored), I changed it to count everything, so we can use the index of the instruction to get a better idea the instruction location in the program printed out.

This PR is to resolving the issue of dangling reference in issue #1090, but the solution is not what we like. Khalique is working on another PR to solve this problem. So close this PR.


Flag "D" (deleted) when i am doing a commit is not appearing on web vscode

The flag "D", that shows what was deleted, is not appearing in web vscode when i am using source control to manage commits. Why it is happenning?

@joyceerhl not seeing this, must not be released

Fix needs tomorrow's pre-release to be verified

Fix needs tomorrow's pre-release to be verified

Why was it closed, @joyceerhl? It's happening to me too.
*I deleted README.md (D) and modified LICENSE-CODE (M).

About
Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:35:55.911Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>

@joyceerhl not seeing this, must not be released

@meganrogge
The missing D in the git short status is the issue.

It's working! Thanks!
Q: Where was the fix committed? I don't see a reference here. Was it done in a private repo?

Yes


Add Charm Icons

Firstly, thanks for your work on this and leptos-icons!
I am excited to use leptos-icons in my projects, but also want to use my icon set charm-icons (MIT Licensed) with the library.
Hopefully I have done everything right, please let me know and I can make any necessary changes.

Yes thank you!
I will review the changes and merge some time tomorrow when I have access to my computer.


I wanted to use this great looking framework

But it is not true that works on android 4.2+ browsers. Unfortunatelly most users do not install Chrome and use the default browser and even your very own http://foundation.zurb.com/apps/app-templates/email/#!/ is full of bugs on android 4.2 and 4.4
There is already a disturbing bug right when you start it. The top bar elements are not aligned vertically.
Then when you click on compose, no popup with compose appears.
When you try to read an email off canvas email read panel is neither off canvas nor full screen. Just tries to scroll with the background with fail. And the list goes on. It is really unfortunate, because my site would have used all these broken features.
On Android 5.0 it works great and fast, however it will take some time until the users from my poor country finally upgrade their shitty phones.

+1, quite some stuff going funky on android browsers


Release to Pypi

Thanks so much for the updates to the main branch that relax the requirements to more modern levels.  We would love to use pypi and artifactory to consume the latest stable release with updated requirements.  Anything I can do to help prepare that release?  Thanks again for this amazing library!

Done. Thanks for asking.

Much appreciated.  We are so enjoying using the library and appreciate the flexible inputs, test coverage, and all the other work that went into making this library so usable.  I hope we can contribute back to it as we gain experience!

I just know y'all are going to find some horrible test cases in the wild. I can't wait for them to added to the test suite.


[Feature Request]:  Floating Animation to the Rate us Image

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Floating Animation to the Rate us Image
Use Case
Floating Animation to the Rate us Image
Benefits
Floating Animation to the Rate us Image
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSOC'24 contributor
[X] I have starred the repository

@Damini2004 Plz elaborate on the feature..

@Damini2004 Plz elaborate on the feature..

Here the image will levitate in upward and downward manner continuously.

@apu52 please assign this issue to me


Fetch automaticality offical results and update database

https://github.com/yak-toto/yak-server/pull/342


Plugin roomPanel

I use OpenFire for CandyChat on my website and i have one conference service in openfire and 3 rooms, but only the first created room is used and visible, so i want to use the roomPanel plugin but I don't understand how to use it. I used te script and the css file but how and where do i call the init method where do I have to put code and how should it look like? I quess that in the JS file i need to specify the rooms names and jids but how to initiate the plugin?

You call init after initializing Candy. The docs are very clear at https://github.com/candy-chat/candy-plugins/tree/master/roomPanel.


How do we know when these endpoints are public?

Hi,
I'm using github actions to publish my extension to google's chrome webstore.  I would like to do the same with Edge, but the API is not available yet.  How will we know when the proposed API endpoints in this document are available to the public?
Thanks!
Mark

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

ID: 4f22ef0a-202d-482d-be95-1a772c2addc9
Version Independent ID: 1a2f5a98-fbb2-ce6b-698c-09b3d878f168
Content: Using the Microsoft Edge Add-ons API - Microsoft Edge Development
Content Source: microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
Product: microsoft-edge
Technology: extensions
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for reaching out. I don't know whether this has been planned yet, since the API is still under development. But I expect that the documentation page you refer to will be updated, and that a blog post will be added to the MS Edge Dev blog, at least.
@ashishnirvana1 might be able to share some information related to timeframe here.

See https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/whats-new/roadmap


Impossible to switch-off translations

I have enabled Translations in form settings:

However, I am now not able to switch them off. When I remove the language, hit the Update button and refresh the page, the translations re-appaear. I can update the Translations setting, but can't disable it completely.

Oops, wrong repository, sorry. Reporting in https://github.com/heyform/heyform.


Please provide CDN

Due to complications i cant install the package on my project. Instead I need to use CDN. Can you provide a CDN?

Have you tried UNPKG? You could use https://unpkg.com/siwe in your project as a CDN to pull the package down. We don't plan on deploying this NPM package to a different CDN at this time


Presets - add babelDefault extension

Issue: https://github.com/storybooks/storybook/pull/4107#discussion_r216251083
What I did
Added an option to extend "babelDefault" method in presets

IMO, we should move babelDefault to babel.

That was my initial thought. But I can see why it may break... maybe when we will remove the support of babel 6 we will be able to remove babelDefault as well 🤷♂

IMO, we should remove babelDefault to babel, and move babel to webpack =)

can you please share an example ?

export function webpack(config) {
  return {
    ...config,
    // find babel-loader here and add docgen plugin
  };
}

But maybe it's not worth it

Yeah, I don't like it much. It is less API friendly and more error-prone. I have another idea about what to do with babelDefault. Will PR asap


Warning icon does nothing

what does it mean? How can I act on this?

This means the page is insecure because it doesn't use HTTPS. This is a really confusing icon, and I actually just changed it yesterday to a "broken padlock" icon in f9042872c179464e87cf9bdf976da79c57c6822f. This change will be included in 1.2.0, which will be released in about two weeks.


Adds Issue templates for bug report and feature request

Modified by me. @PSGitHubUser1

Please approve

Really, if yes then accept this pull request.. pls


Acceptance tests

Description
This adds acceptance tests to the SDK which can be called from a connector to make sure it fulfills expectations.
Besides acceptance tests this also introduces the struct Connector which ties together the functions we had to manually gather before (constructors for creating specifications, source and destination). It's a minor improvement that makes the code nicer and safer since the connector can be defined globally once and used in the entry point as the argument to Serve as well as the argument to the acceptance test driver config.
For example, we can run the acceptance tests for the Kafka connector by creating acceptance_test.go with the following test (the code needs to be slightly adjusted to pass, the tests already found a couple of issues):
package kafka

import (
	"testing"

	sdk "github.com/conduitio/conduit-connector-sdk"
	"github.com/google/uuid"
)

func TestAcceptance(t *testing.T) {
	cfg := testConfigMap()

	sdk.AcceptanceTest(t, sdk.ConfigurableAcceptanceTestDriver{
		Config: sdk.ConfigurableAcceptanceTestDriverConfig{
			Connector: sdk.Connector{ // Note that this variable should rather be created globally in `connector.go`
				NewSpecification: Specification,
				NewSource:        NewSource,
				NewDestination:   NewDestination,
			},
			SourceConfig:      cfg,
			DestinationConfig: cfg,

			BeforeTest: func(t *testing.T) {
				// use new topic for each test
				cfg[Topic] = "test-topic-" + uuid.NewString()
			},
		},
	})
}

Some linters are disabled on file acceptance_testing.go since it's essentially a test file.
There are some tests still missing, I'll keep working on them but they shouldn't affect existing tests so that shouldn't block the review. Here's a list of tests I identified (please let me know if I forgot any important test so we add it to the list!):

[ ] source

[X] configure

[X] required parameters
[X] teardown after configure

[ ] open

[ ] resume at position

[X] read

[X] successful snapshot
[X] successful CDC read
[X] timeout / cancelled context
[X] goroutine leak
[X] unique position

[ ] ack
[X] stop (closed context in read tests)
[X] teardown (implicitly in configure/read tests)

[ ] destination

[X] configure

[X] required parameters
[X] teardown after configure

[X] write

[X] successful write
[X] goroutine leak

[ ] async write

[X] successful write
[X] goroutine leak
[X] ack after flush
[ ] ack after X seconds
[ ] ack after X records
[ ] ack error

[X] stop (closed context in write tests)
[X] teardown (implicitly in configure/write tests)

Looking good so far! 🔌 ✅ Re: Missing tests cases - Should we add a test case for idempotent Teardown's? is that a standard we want to enforce at some level?

Re idempotent Teardown it's obviously nice, but not a requirement IMO, we are only ever going to call it once. What we do test on the other hand is that Teardown can be called after Configure without a call to any other function in between.


[Android] Add test APKs for shared mode

Add XWalkSharedShell and XWalkSharedTest for shared mode test, the
package name, test cases, assets of these APKs are just like
XWalkCoreShell and XWalkCoreTest except that they must work with
XWalkRuntimeLib.

Please remember to file JIRA tickets for those APKs to start being shipped with each build, as well as added to the bot test list.

@rakuco These new APKs don't need to be shipped nor to be included into the bot because they are the exactly same with XWalkCoreShell and XWalkCoreTest. They are only for compatibility test of shared mode. Before every beta release, QA will run XWalkSharedTest on different versions of XWalkRuntimeLib manually.

@rakuco Could you give a LGTM so that I can merge this.

@rakuco

lgtm
I still think you need to file a ticket to get this into the bot/release build workflow, otherwise we won't even know if it's minimally running, and if it's not part of the zip files QA will need to build the APKs on their own.

Thanks for the reply. I'll file a ticket to ship this.


Usage docs page example does not work correctly

Describe the bug
The example demo from the Usage docs page does not work. Multiple errors are produced.
To Reproduce
Steps to reproduce the behavior:

Create a new test environment, with python 3.10, pip, copier, pytest, and pytest-copie.
Go to the Usage docs page
Create this repository structure:

my_template/
├── {{repo_name}}/
│   └── README.rst.jinja
├── tests/
│   └── test_template.py
└── copier.yaml

Add this content to the file copier.yaml

repo_name:
   type: str
   default: foobar
short_description:
   type: str
   default: Test Project

Add this content to the file README.rst.jinja:

{{ repo_name }}
===============

{{ short_description }}

Add this content to the file ``:

def test_template(copie):
    result = copie.copy()

    assert v.exit_code == 0
    assert result.exception is None
    assert result.project_dir.name == "foobar"
    assert result.project_dir.is_dir()

Confirm that regular old copier works on this example repo: cd ..; copier copy my_template my_output. Observe that it works, and has created a "foobar" directory containing a README.rst file containing a "foobar" heading and the example short description.
Try running pytest (with pytest-copie on the my_template repository: cd my_template; pytest --keep-copied-projects --pdb
See the pytest errors

Additional context
There were a number of errors. I've found and made fixes for some easy ones, but am still not quite sure about some others.

Easy fix number one: https://github.com/12rambau/pytest-copie/pull/46
Easy fix number two: https://github.com/12rambau/pytest-copie/pull/47
Remaining problem:

...this sounds like it has an easy fix, i.e. adding _subdirectory: {{repo_name}} to copier.yaml
BUT that causes other problems. I tried:

_subdirectory: {{repo_name}}
_subdirectory: "{{repo_name}}"
_subdirectory: \{\{repo_name\}\}
_subdirectory: my_template
_subdirectory: foobar (I know this one is the silliest, but I was getting fed up)

A workaround that helped was to restructure the repository, so we had my_template/template/{{repo_name}}/README.rst.jinja, and in copier.yaml I wrote _subdirectory: template. That worked, and got me to the next error.

Possibly related problem - pytest-copie's result.project_dir.name is returning copie0001 instead of the expected foobar. This is possibly related to the subdirectory problem above, because if you look in the temporary pytest-copie folder that is generated, the foobar directory (and everything else we expect) does exist... it's just inside the copie0001 temp folder. So if we can convince pytest-copie to look one level down for the project_dir, that might fix this.

Questions:

Should we use the workaround I suggested here, or do you know how to make the yaml work so we can use _subdirectory: {{repo_name}} directly?

A workaround that helped was to restructure the repository, so we had my_template/template/{{repo_name}}/README.rst.jinja, and in copier.yaml I wrote _subdirectory: template.

How should I convince pytest-copie to look in the right place for the project_dir folder?

I found this line, so I think if I mess around with the extra_answers dictionary values, I might be able to do it
https://github.com/12rambau/pytest-copie/blob/bd114eb5202933165f68e0ad98eb8d6ae6e06386/pytest_copie/plugin.py#L62


fix(JSON RPC): Prevening processing of duplicate entries

:tada: This PR is included in version 1.4.18 :tada:
Your semantic-release bot :package::rocket:


Update contribute.md (Fix links to subscribe for users and contributors)

Description
This change is to update the contribute.md page to use the right references/links for the subscribing to the different mailing lists.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Hello Soji, welcome to MXNet and thanks a lot for your first contribution!

@sad- Can you please retrigger CI? (with empty commit)
Changes looks good, thanks for your contributions.

@marcoabreu why doesnt CI show any status?

It seems like this particular PR is bugged and does not execute the ping to our ci server. I'd recommend reopening the PR

@marcoabreu i see you tried closing and reopening and that still did not trigger the ci. Any idea why that did not work? Did you mean closing out this one entirely and opening a different one?

Exactly

https://github.com/apache/incubator-mxnet/pull/12183


Fix(UI)#8737: Converted edit description modals into antd modals

Describe your changes :

I worked on converting edit description modals to antd modals
Closes #8737

Type of change :

[x] Bug fix
[x] Improvement

Frontend Preview (Screenshots) :

https://user-images.githubusercontent.com/51777795/208237647-74f0a2d8-c1b8-41c6-a347-88ad40dcb0f5.mov

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Frontend: @open-metadata/ui

@chirag-madlani, I have pushed the changes as per the comments. Can you please review it?


feat: optional files option

related #96

Codecov Report

Merging #113 (0fd55ad) into next (37c47a7) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             next     #113      +/-   ##
==========================================
- Coverage   57.14%   57.10%   -0.04%
==========================================
  Files          59       59
  Lines        1449     1450       +1
  Branches      291      292       +1
==========================================
  Hits          828      828
- Misses        621      622       +1

Impacted Files
Coverage Δ

packages/bundlemon/src/main/utils/configUtils.ts
28.57% <0.00%> (-0.42%)
: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 37c47a7...0fd55ad. Read the comment docs.


Add days-old flag to ruff clean

Summary
Change the cleaning to only include files that are of a certain age.
Based on https://github.com/astral-sh/ruff/pull/5122.
Test Plan
Manually tested.

What's the use case for this flag? It seems that building the cache is pretty cheap. A user can, therefore, just clean the whole cache and rebuild it. I think what would be more useful (but probably still too rare to be useful) is to allow cleaning by package. However, that starts exposing implementation details.

This assumes that we switch to a global cache (https://github.com/astral-sh/ruff/pull/5122), which changes ruff clean to remove all caches (for all packages). For users working with multiple packages they might not want to clean the entire cache, only the unused cache file. This is to combat the general problem of the "every growing cache".

(I completely missed this comment)

I continue to be undecided whether we should move to a global cache. It seems to introduce more complexity. Anyway:
* I think we should change the documentation of `clean` to make it clear that, by default, removes **all** caches, globally. This should probably go into [Use global cache directory #5122](https://github.com/astral-sh/ruff/pull/5122)

:+1:

* Would it make sense to instead add a flag (similar to `cargo -p`) to specify which packages to clean?

to combat the general problem of the "every growing cache".

My understanding was that your PR adding the last seen already removes old files. Does this PR address the case where a cache keeps growing after changing the settings?

Yes, for caches that are actually used. When/if we switch to a global cache dir removing a Python project will no longer remove Ruff's cache for it (as it's stored outside of the project's directory that is removed). This also true, to a lesser extend, for "packages" within the same repo, e.g. one-off files, examples and often tests. Using the current solver these are stored separately from the "main" source code. For example the FastAPI repo has 79 "packages" and thus 79 different cache files, moving the source file (e.g. an example or test) will cause the cache to be now longer used, but it won't be removed as we simple don't even look at the old cache files again.
A regular cargo clean will take of the above, but it will also wipe out still used caches. A days-old flag like this adding keep the useful caches, while removing only the unused cache files.

Since https://github.com/astral-sh/ruff/pull/5122 wasn't merged this still has some benefit, but less so. If "packages", including tests, docs, scripts, etc., move within a repo this can remove the old cache where the current clean command simply removes everything (this assumes a single cache dir is used for the entire repo).

Since #5122 wasn't merged this still has some benefit, but less so. If "packages", including tests, docs, scripts, etc., move within a repo this can remove the old cache where the current clean command simply removes everything (this assumes a single cache dir is used for the entire repo).

I'll close this for now based on the decision of #5122. The new flag is less needed now that we keep the local cache and cleaning the whole cache of a single project and rebuilding it should only take a few seconds. Not having the flag keeps Ruff's complexity and API smaller.


Fix poms dependencies on indy-promote-common:dataset

Not know why the 1.3 does not produce xxx-dataset.jar anymore. It seems this can fix the build but some ftests failed. We need to make it produce dataset.jar or consume dataset.tar.gz.

@jdcasey I am sorry if this confused. This is a bad commit. Some ftests failed due to failing to read default promotion rules. Those are packaged in the dataset.jar file, rather than tar.gz. I don't know why this did not fail prev prs (maybe because the jar was still on sonatype snapshot and removed recently). Anyway, we need to fix it. I will submit another PR making the indy-promote-common still produce the dataset jar file.

@ruhan1 Let's roll it back then, if necessary. @bxf12315 just submitted a PR to restore the dataset.jar file to the assembly descriptor, and I've merged that.


npx nuxi upgrade keeps geting nuxt 2

So i've got a project that got running on nuxt 3.2.3, and wanted to reinstall my node and package-lock by deleting them. when the instalation complete, it broking up says that 'defineNuxtConfig' is not defined. tried to check my nuxt version using npx nuxi info, it tells that nuxt version that being used is 2.15.8. try to use the npx nuxi upgrade -f it still says nuxt version of 2.15.8.
here's the info from my npx nuxi info
*nuxi version : 3.2.3

Operating System: Darwin
Node Version:     v18.16.0
Nuxt Version:     2.15.8
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      modules, css, runtimeConfig
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Here's my package.json
{
  "overrides": {
    "vue": "latest"
  },
  "private": true,
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "devDependencies": {
    "@nuxt/content": "^2.5.2",
    "@nuxtjs/fontaine": "^0.2.4",
    "@nuxtjs/tailwindcss": "^6.4.1",
    "@pinia-plugin-persistedstate/nuxt": "^1.1.1",
    "@sidebase/nuxt-auth": "^0.4.4",
    "@tailwindcss/typography": "^0.5.9",
    "@vueuse/nuxt": "^10.0.2",
    "nuxt": "^3.4.3",
    "tailwindcss": "^3.3.0"
  },
  "dependencies": {
    "@heroicons/vue": "^2.0.16",
    "@nuxt/test-utils-edge": "^3.5.0-28049707.16bf2284",
    "@nuxtjs/html-validator": "^1.2.4",
    "@nuxtjs/strapi": "^1.9.0",
    "@pinia/nuxt": "^0.4.7",
    "@popperjs/core": "^2.11.7",
    "@vueuse/core": "^10.0.2",
    "daisyui": "^2.51.3",
    "flowbite": "^1.6.4",
    "flowbite-datepicker": "^1.2.2",
    "hooper": "^0.3.4",
    "marked": "^4.3.0",
    "pinia": "^2.0.33",
    "v-calendar": "^3.0.3",
    "vue3-carousel": "^0.2.16"
  }
}

i tried to install a new project, and it still says 'defineNuxtConfig' is not defined, and got nuxt 2.15.8.

I would guess you have nuxt 2 installed globally or in a parent node_modules folder. Would you check?

I see, it solved the problems. thankyou sir

/cc @danielroe We had this neighbor resolution issue in past too (mlly search path). Adding comment to remember debugging it together later.


[InputDecoration] 'dart:ui/text.dart': Failed assertion: line 1372

Steps to Reproduce
Complete working bug sample: https://github.com/nbkolchin/flutter-bugs/tree/master/bug_textfield_1372
Minimal sample code:
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(title: Text('TextField Bug line 1372 demo')),
        body: Center(
            child: Column(
                children: <Widget>[
                  OutlineButton(
                      child: Text(_searchMode ? "Hide textfield" : "Show textfield"),
                      onPressed: () {
                        setState(() {  _searchMode = !_searchMode;  });
                      },
                  ),
                  Visibility(
                      visible: _searchMode,
                      child: TextField(
                          controller: widget.filterController,
                          autofocus: true,
                          decoration: new InputDecoration(
                              prefixIcon: new Icon(Icons.search),
                              hintText: 'Search...',
                          ),
                      ),
                  ),
                ],
            ),
        ),
    );
  }

Press Show TextField.
Press Hide TextField.
Press Show TextField.
Exception will appear.

It looks like selection become null at some point...
Target Platform: Android
Target OS version/browser: Android 9
Devices: Simulator, various Phones.
Logs
I/flutter ( 9216): ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter ( 9216): The following assertion was thrown during paint():
I/flutter ( 9216): 'dart:ui/text.dart': Failed assertion: line 1372: '<optimized out>': is not true.
I/flutter ( 9216):
I/flutter ( 9216): Either the assertion indicates an error in the framework itself, or we should provide substantially
I/flutter ( 9216): more information in this error message to help you determine and fix the underlying cause.
I/flutter ( 9216): In either case, please report this assertion by filing a bug on GitHub:
I/flutter ( 9216):   https://github.com/flutter/flutter/issues/new?template=BUG.md
I/flutter ( 9216):
I/flutter ( 9216): The relevant error-causing widget was:
I/flutter ( 9216):   TextField
I/flutter ( 9216):   file:///Users/snob/work/experiments/dart/bug-reports/bug_textfield_1372/lib/main.dart:60:30
I/flutter ( 9216):
I/flutter ( 9216): When the exception was thrown, this was the stack:
I/flutter ( 9216): #2      new TextPosition (dart:ui/text.dart:1372:15)
I/flutter ( 9216): #3      RenderEditable._updateSelectionExtentsVisibility (package:flutter/src/rendering/editable.dart:367:7)
I/flutter ( 9216): #4      RenderEditable._paintContents (package:flutter/src/rendering/editable.dart:1956:7)
I/flutter ( 9216): #5      RenderEditable.paint (package:flutter/src/rendering/editable.dart:2012:7)
I/flutter ( 9216): #6      RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #7      PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #8      RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #9      RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #10     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #11     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #12     PaintingContext.pushLayer (package:flutter/src/rendering/object.dart:384:12)
I/flutter ( 9216): #13     RenderLeaderLayer.paint (package:flutter/src/rendering/proxy_box.dart:4796:13)
I/flutter ( 9216): #14     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #15     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #16     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #17     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #18     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #19     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #20     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #21     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #22     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #23     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #24     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #25     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #26     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #27     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #28     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #29     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #30     PaintingContext._repaintCompositedChild (package:flutter/src/rendering/object.dart:135:11)
I/flutter ( 9216): #31     PaintingContext.repaintCompositedChild (package:flutter/src/rendering/object.dart:95:5)
I/flutter ( 9216): #32     PaintingContext._compositeChild (package:flutter/src/rendering/object.dart:201:7)
I/flutter ( 9216): #33     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:182:7)
I/flutter ( 9216): #34     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #35     RenderCustomPaint.paint (package:flutter/src/rendering/custom_paint.dart:575:11)
I/flutter ( 9216): #36     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #37     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #38     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #39     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #40     PaintingContext._repaintCompositedChild (package:flutter/src/rendering/object.dart:135:11)
I/flutter ( 9216): #41     PaintingContext.repaintCompositedChild (package:flutter/src/rendering/object.dart:95:5)
I/flutter ( 9216): #42     PaintingContext._compositeChild (package:flutter/src/rendering/object.dart:201:7)
I/flutter ( 9216): #43     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:182:7)
I/flutter ( 9216): #44     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #45     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #46     PaintingContext._repaintCompositedChild (package:flutter/src/rendering/object.dart:135:11)
I/flutter ( 9216): #47     PaintingContext.repaintCompositedChild (package:flutter/src/rendering/object.dart:95:5)
I/flutter ( 9216): #48     PaintingContext._compositeChild (package:flutter/src/rendering/object.dart:201:7)
I/flutter ( 9216): #49     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:182:7)
I/flutter ( 9216): #50     _RenderDecoration.paint.doPaint (package:flutter/src/material/input_decorator.dart:1404:17)
I/flutter ( 9216): #51     _RenderDecoration.paint (package:flutter/src/material/input_decorator.dart:1439:12)
I/flutter ( 9216): #52     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #53     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #54     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #55     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #56     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #57     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #58     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #59     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #60     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #61     RenderMouseRegion.paint (package:flutter/src/rendering/proxy_box.dart:2787:13)
I/flutter ( 9216): #62     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #63     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #64     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #65     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #66     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #67     RenderBoxContainerDefaultsMixin.defaultPaint (package:flutter/src/rendering/box.dart:2508:15)
I/flutter ( 9216): #68     RenderFlex.paint (package:flutter/src/rendering/flex.dart:948:7)
I/flutter ( 9216): #69     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #70     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #71     RenderShiftedBox.paint (package:flutter/src/rendering/shifted_box.dart:70:15)
I/flutter ( 9216): #72     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #73     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #74     RenderBoxContainerDefaultsMixin.defaultPaint (package:flutter/src/rendering/box.dart:2508:15)
I/flutter ( 9216): #75     RenderCustomMultiChildLayoutBox.paint (package:flutter/src/rendering/custom_layout.dart:396:5)
I/flutter ( 9216): #76     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #77     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #78     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #79     _RenderInkFeatures.paint (package:flutter/src/material/material.dart:530:11)
I/flutter ( 9216): #80     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #81     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #82     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #83     PaintingContext.pushLayer (package:flutter/src/rendering/object.dart:384:12)
I/flutter ( 9216): #84     RenderPhysicalModel.paint (package:flutter/src/rendering/proxy_box.dart:1755:15)
I/flutter ( 9216): #85     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #86     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #87     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #88     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #89     PaintingContext.paintChild (package:flutter/src/rendering/object.dart:184:13)
I/flutter ( 9216): #90     RenderProxyBoxMixin.paint (package:flutter/src/rendering/proxy_box.dart:123:15)
I/flutter ( 9216): #91     RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
I/flutter ( 9216): #92     PaintingContext._repaintCompositedChild (package:flutter/src/rendering/object.dart:135:11)
I/flutter ( 9216): #93     PaintingContext.repaintCompositedChild (package:flutter/src/rendering/object.dart:95:5)
I/flutter ( 9216): #94     PipelineOwner.flushPaint (package:flutter/src/rendering/object.dart:937:29)
I/flutter ( 9216): #95     RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:346:19)
I/flutter ( 9216): #96     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:774:13)
I/flutter ( 9216): #97     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:283:5)
I/flutter ( 9216): #98     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1102:15)
I/flutter ( 9216): #99     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1041:9)
I/flutter ( 9216): #100    SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:957:5)
I/flutter ( 9216): #104    _invoke (dart:ui/hooks.dart:259:10)
I/flutter ( 9216): #105    _drawFrame (dart:ui/hooks.dart:217:3)
I/flutter ( 9216): (elided 5 frames from class _AssertionError and package dart:async)
I/flutter ( 9216):
I/flutter ( 9216): The following RenderObject was being processed when the exception was fired: RenderEditable#c26df relayoutBoundary=up18:
I/flutter ( 9216):   creator: _Editable-[GlobalKey#ec266] ← Semantics ← CompositedTransformTarget ←
I/flutter ( 9216):     IgnorePointer-[GlobalKey#1f9d4] ← Semantics ← _PointerListener ← Listener ←
I/flutter ( 9216):     RawGestureDetector-[LabeledGlobalKey<RawGestureDetectorState>#ffd05] ← _PointerListener ← Listener
I/flutter ( 9216):     ← _ScrollableScope ← RepaintBoundary ← ⋯
I/flutter ( 9216):   parentData: <none> (can use size)
I/flutter ( 9216):   constraints: BoxConstraints(w=312.0, 0.0<=h<=Infinity)
I/flutter ( 9216):   size: Size(312.0, 19.0)
I/flutter ( 9216):   cursorColor: Color(0x004285f4)
I/flutter ( 9216):   showCursor: ValueNotifier<bool>#4a016(true)
I/flutter ( 9216):   maxLines: 1
I/flutter ( 9216):   minLines: null
I/flutter ( 9216):   selectionColor: Color(0xff90caf9)
I/flutter ( 9216):   textScaleFactor: 1.0
I/flutter ( 9216):   locale: en_US
I/flutter ( 9216):   selection: TextSelection(baseOffset: 0, extentOffset: 0, affinity: null, isDirectional: false)
I/flutter ( 9216):   offset: ScrollPositionWithSingleContext#9a9e9(offset: 0.0, range: 0.0..0.0, viewport: 312.0,
I/flutter ( 9216):     ScrollableState, ClampingScrollPhysics, IdleScrollActivity#fc6a8, ScrollDirection.idle)
I/flutter ( 9216): This RenderObject had the following child:
I/flutter ( 9216):     text: TextSpan
I/flutter ( 9216): ════════════════════════════════════════════════════════════════════════════════════════════════════

bash-3.2$ flutter analyze
Analyzing bug_textfield_1372...
No issues found! (ran in 2.9s)

bash-3.2$ flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.14.6 18G1012, locale en-RU)
    • Flutter version 1.12.13+hotfix.5 at /Users/snob/tools/flutter
    • Framework revision 27321ebbad (5 days ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/snob/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3, Build version 11C29
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 41.1.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.40.2)
    • VS Code at /Users/snob/Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.2.0

[✓] Connected device (1 available)
    • POT LX1 • WQD7N19227000688 • android-arm64 • Android 9 (API 28)

• No issues found!

i have the same issue to
import 'package:flutter/material.dart';

class RoundedField extends StatelessWidget {
  final String label;
  final bool isPassword;
  final bool autoValidate;
  final TextEditingController controller;
  final Function validator;
  final TextInputType inputType;

  RoundedField({
    @required this.label,
    this.isPassword = false,
    @required this.controller,
    @required this.autoValidate,
    this.validator,
    this.inputType,
  });

  @override
  Widget build(BuildContext context) {
    return Padding(
      padding: const EdgeInsets.all(12.0),
      child: TextFormField(
        keyboardType: inputType,
        validator: validator,
        controller: controller,
        autovalidate: autoValidate,
        style: TextStyle(
          color: Colors.white,
          fontSize: 18.0,
        ),
        decoration: InputDecoration(
          labelText: label,
          border: OutlineInputBorder(
            borderRadius: BorderRadius.circular(16.0),
          ),
        ),
        obscureText: isPassword,
      ),
    );
  }
}

The following assertion was thrown during paint():
'dart:ui/text.dart': Failed assertion: line 1372: '<optimized out>': is not true.

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=BUG.md

The relevant error-causing widget was:
  TextFormField file:///D:/AProjects/coffee_mate/lib/features/register/presentation/widgets/rounded_field.dart:24:14
When the exception was thrown, this was the stack:
#2      new TextPosition (dart:ui/text.dart:1372:15)
#3      RenderEditable._updateSelectionExtentsVisibility (package:flutter/src/rendering/editable.dart:367:7)
#4      RenderEditable._paintContents (package:flutter/src/rendering/editable.dart:1956:7)
#5      RenderEditable.paint (package:flutter/src/rendering/editable.dart:2012:7)
#6      RenderObject._paintWithContext (package:flutter/src/rendering/object.dart:2219:7)
...
The following RenderObject was being processed when the exception was fired: RenderEditable#2c7f8 relayoutBoundary=up21
...  parentData: <none> (can use size)
...  constraints: BoxConstraints(w=363.4, 0.0<=h<=Infinity)
...  size: Size(363.4, 21.0)
...  cursorColor: Color(0x004285f4)
...  showCursor: ValueNotifier<bool>#a1976(true)
...  maxLines: 1
...  minLines: null
...  selectionColor: Color(0xff64ffda)
...  textScaleFactor: 1.0
...  locale: en_US
...  selection: TextSelection(baseOffset: 10, extentOffset: 10, affinity: null, isDirectional: false)
...  offset: ScrollPositionWithSingleContext#c7dc6(offset: 0.0, range: 0.0..0.0, viewport: 363.4, ScrollableState, ClampingScrollPhysics, IdleScrollActivity#20ecb, ScrollDirection.idle)
  text: TextSpan
    debugLabel: ((englishLike subhead 2014).merge(whiteMountainView subhead)).merge(unknown)
    inherit: false
    color: Color(0xffffffff)
    family: Roboto
    size: 18.0
    weight: 400
    baseline: alphabetic
    decoration: TextDecoration.none
    "••••••••••"
RenderObject: RenderEditable#2c7f8 relayoutBoundary=up21
  parentData: <none> (can use size)
  constraints: BoxConstraints(w=363.4, 0.0<=h<=Infinity)
  size: Size(363.4, 21.0)
  cursorColor: Color(0x004285f4)
  showCursor: ValueNotifier<bool>#a1976(true)
  maxLines: 1
  minLines: null
  selectionColor: Color(0xff64ffda)
  textScaleFactor: 1.0
  locale: en_US
  selection: TextSelection(baseOffset: 10, extentOffset: 10, affinity: null, isDirectional: false)
  offset: ScrollPositionWithSingleContext#c7dc6(offset: 0.0, range: 0.0..0.0, viewport: 363.4, ScrollableState, ClampingScrollPhysics, IdleScrollActivity#20ecb, ScrollDirection.idle)
  text: TextSpan
    debugLabel: ((englishLike subhead 2014).merge(whiteMountainView subhead)).merge(unknown)
    inherit: false
    color: Color(0xffffffff)
    family: Roboto
    size: 18.0
    weight: 400
    baseline: alphabetic
    decoration: TextDecoration.none
    "••••••••••"
════════════════════════════════════════════════════════════════════════════════════════════════════

Hi @nbkolchin
I'm running you code in dartpad, but I'm not experiencing the issue you are describing,
I also see that you commented out the selection  related code.
I'm not sure if what you are describing is an issue with Flutter itself
or if you are asking for assistance within your code.
If you believe it's an issue with flutter,
please provide the steps to reproduce the problem.
If you need help with your app,
please be aware that this platform is not met for assistance on personal code.
Please see https://flutter.dev/community for resources for asking questions like this,
you may also get some help if you post it on Stack Overflow.
Thank you

This bug doesn't appear on Flutter-Web (i.e. dartpad). You should test under Android environment.

Commented out "selection" code was used to get around problem in real-world application. It doesn't help in stripped bug sample, though.

According to stack trace the exception is raised because selection.affinity become null at some point. This is definitely flutter problem, cause application don't change selection or affinity in any way.

Hi again @nbkolchin
on android it does output the error,
but it's not related to the textfield itself
(that doen't use dart:ui ), but rather to the InputDecoration.
Regardless, thank you for the contribution

Same error during debug sessions on iOS (13.3) simulator after Flutter upgrade to 1.12.13+hotfix.5
════════ Exception caught by rendering library ═════════════════════════════════
'dart:ui/text.dart': Failed assertion: line 1372: '<optimized out>': is not true.
The relevant error-causing widget was
    TextField
lib/pages/login_page.dart:308
The following RenderObject was being processed when the exception was fired: RenderEditable#7e848 relayoutBoundary=up32
RenderObject: RenderEditable#7e848 relayoutBoundary=up32
    parentData: <none> (can use size)
    constraints: BoxConstraints(w=276.0, 0.0<=h<=Infinity)
    size: Size(276.0, 19.0)
    cursorColor: Color(0x002196f3)
    showCursor: ValueNotifier<bool>#a3ec0(true)
    maxLines: 1
    minLines: null
    selectionColor: Color(0xff90caf9)
    textScaleFactor: 1.0
    locale: en
    selection: TextSelection(baseOffset: 8, extentOffset: 8, affinity: null, isDirectional: false)
    offset: ScrollPositionWithSingleContext#49d60(offset: 0.0, range: 0.0..0.0, viewport: 276.0, ScrollableState, BouncingScrollPhysics, IdleScrollActivity#a9b82, ScrollDirection.idle)
    text: TextSpan
        debugLabel: (englishLike subhead 2014).merge((blackCupertino subhead).apply)
        inherit: false
        color: Color(0xdd000000)
        family: Roboto
        size: 16.0
        weight: 400
        baseline: alphabetic
        decoration: TextDecoration.none
        "••••••••"

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C57, locale en-IT)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Android Studio (version 3.4)
[✓] VS Code (version 1.41.0)
[✓] Connected device (1 available)

• No issues found!

Row(
                          crossAxisAlignment: CrossAxisAlignment.center,
                          mainAxisAlignment: MainAxisAlignment.start,
                          children: <Widget>[
                            Expanded(
                              child: TextField(
                                controller: _passwordController,
                                obscureText: true,
                                textAlign: TextAlign.left,
                                decoration: const InputDecoration(
                                  border: InputBorder.none,
                                  hintText: '*********',
                                  hintStyle: TextStyle(color: Colors.grey),
                                ),
                              ),
                            ),
                          ],
                        ),

Can anyone reproduce this on master?  I just tried all of the following and couldn't get an exception:

@nbkolchin's code on the iOS simulator and the Android emulator.
@muhammad1339's code on the Android emulator.
@enricobenedos's code on the Android emulator.

Hopefully this is fixed already and on its way to stable.

No exception on master under IOS and Android.

Great, hopefully the fix will be in the next stable release then.  If anyone needs it sooner, you could try switching to the dev or master channels.
I'm going to close this, but if anyone sees it again on master feel free to reopen.

I can confirm that using master and testing it on Android the problem does not appear.


Add "sec" units to numbers

Right now, we just show numbers (e.g. 0.1234, 0.5432) without units. We need to put in the units so that people know what they represent.

Also, we can make the instructions a little more clear (e.g. hold the button for 5 seconds).


Remove pooling display refresh code.

add missing collection monitor
add display refresh to missed entities list

I added a little bit of conflicts in your PR :-)
Check my comment on the manual refresh on the 2 datasources (Car and Charging Profile)


[Task]: Provide OAuth2 field details to documentation team

SubTasks
The docs team needs information on what all fields are there in datasource form config for configuring oauth2 datasource in appsmith.
The team also wants to know the error thrown when refresh token expires

@jnikhila I have added all the requested details here. Please check and let me know if anything else is required.


Saving Notebook Editor file with a new name doesn't change the doc name

Create a new notebook editor
Add and run a cell in it
Press "Save notebook" button and give it a new name / location

Expected:
Title of file tab should reflect the new name
Actual:
File tab is still Untitled-1

Validated


Fixed missing element issue in parsed ast

The markdown parser is not perfect and it returns bogus entry and it will break the code here. We can just skip processing when expected key is missing.

Thanks for the PR! Would you be able to add something to the smoketest to demonstrate a case that causes this failure?
One piece of this code should now have been addressed (on master, not yet released) in https://github.com/jamalex/notion-py/pull/158


Fix and extend (AAC/M4A/ALAC) decoding

You might have noticed that decoding stopped working somehow by running the examples.
The MediaElement does not support the new formats yet. Enabling these features is blocked by a pending PR for creek: https://github.com/MeadowlarkDAW/creek/pull/22

Thanks! I guess I never tried to to use any multi-track input, so I'm happy you have caught it.
Hope to see the upstream work at creek merged any time soon. I have added myself as a subscriber to the PR

Thanks! I guess I never tried to to use any multi-track input, so I'm happy you have caught it. Hope to see the upstream work at creek merged any time soon. I have added myself as a subscriber to the PR

I am not very confident that this will ever happen. The maintainer seems to have abandoned the project and/or is not interested in contributions.

I will open an issue asking if they are open for us to co-maintain the lib.
If we don't hear anything we can just publish a fork - it is liberally licensed.


Iverilog Version

 Hi Dinesh, I have a problem when verifying the user_usb, the iverilog I'm using gives me a warning like this, could you tell me which iverilog you are using?

mine is 11.

These are warning, simulation still will work.

Could you please take a look at it here? I see no waveform generated.

I don't see Error details, Mostly if will be at starting of the log

Yes, you are correct. Seems that problem came from AES module, I will take a look at that. Thank you.

Looks like there are lint issues due to the latest iverilog, I have pushed
fixes back to repo .. You can pull the changes and sub-git repos.
On Sun, Jul 14, 2024 at 11:35 AM Painting(Looking for jobs or Phd
positions) @.***> wrote:

image.png (view on web)
https://github.com/user-attachments/assets/7aab057e-14fd-45c0-ab96-a329cac6a9b9
Yes, you are correct. Seems that problem came from AES module, I will take
a look at that. Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/dineshannayya/riscduino/issues/31#issuecomment-2227207702,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7HAVRJG2JWO3HB75GGD5LZMIILZAVCNFSM6AAAAABK2VRDDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGIYDONZQGI
.
You are receiving this because you commented.Message ID:
@.***>

Thank you.

In the security_core provided in the submodule, the version might not be the latest(has no idle signal).  After git pull the latest and manually upgrade the security_core, dv now works. Thank you.


Feature Request: Analyze in Xcode only runs against uppermost subset of targets

Let me know if this is an inaccurate read of what is happening. From what I can see, when running Analyze against a target in Xcode (BwB, Bazel 7.3.1, rules_xcodeproj 2.7, rules_apple 3.8, rules_swift 2.1.1), the analyzer is only run against the source-list of the topmost library target in a top-level target. For example, the library of an ios_application, ios_unit_test, or ios_build_test. Sources in dependencies of that library target are not analyzed, and the analyzer doesn't appear to have much of an effect regardless.
Before I go through the process of sanitizing logs for y'all, does this sound familiar? Has the analyzer ever received attention in the ruleset? I would totally believe it if it had not yet.

It hasn't received any attention. I expect the issue is that target dependencies aren't represented in Xcode (as a performance optimization to prevent the compiler stubs from being run constantly). you could try to adjust _collect_dependencies to not filter out any dependencies to see if that fixes it for you.


Add nedb adapter for database

Add NeDB as a backend option via the adapter:
https://github.com/adityamukho/sails-nedb

:+1:

Now available in<EMAIL_ADDRESS>


[google_maps_flutter] Android integration test crashing in CI: glCreateShader failed

I'm seeing flaky failures with the maps integration tests recently; example runs:

https://firebase.corp.google.com/project/flutter-cirrus/testlab/histories/bh.ccd6322d1559daa/matrices/7573375672107147278/executions/bs.4e441d9bcae26d4/issues
https://firebase.corp.google.com/project/flutter-cirrus/testlab/histories/bh.ccd6322d1559daa/matrices/8994558717084734910/executions/bs.b5c61781c34f7b94

The report is:
Test run failed to complete. Instrumentation run failed due to Process crashed.
 Fatal exception
Fatal AndroidRuntime Exception detected.
     FATAL EXCEPTION: GL-Map
Process: io.flutter.plugins.googlemapsexample, PID: 23876
ers: glCreateShader failed with return value 0and GL error code 0
GL info log:
<no info log>
Shader vert source:
<unused source>
	at eor.b(:com.google.android.gms.policy_maps_core_dynamite@224312102@224312102065.485900589.485900589:3)
	at eor.a(:com.google.android.gms.policy_maps_core_dynamite@224312102@224312102065.485900589.485900589:1)
	at epn.<init>(:com.google.android.gms.policy_maps_core_dynamite@224312102@224312102065.485900589.485900589:2)
	at epo.<init>(:com.google.android.gms.policy_maps_core_dynamite@224312102@224312102065.485900589.485900589:1)
	at efd.e(:com.google.android.gms.policy_maps_core_dynamite@224312102@224312102065.485900589.485900589:17)
	at eom.run(:com.google.android.gms.policy_maps_core_dynamite@224312102@224312102065.485900589.485900589:35)

It's possible this is a regression on the maps side rather than a plugin issue? Filing for tracking and further investigation.

This just happened again, on both the initial run and the re-run, so this is still a relatively common flake.

I've seen this again, while attempting to roll flutter-stable-packages:

https://ci.chromium.org/ui/p/flutter/builders/try/Linux_android android_device_tests_shard_2 master/6337/overview
https://ci.chromium.org/ui/p/flutter/builders/try/Linux_android android_device_tests_shard_2 master/6338/overview

Both crashes mention the same test:
┌─────────┬────────────────────────┬─────────────────────┐
│ OUTCOME │    TEST_AXIS_VALUE     │     TEST_DETAILS    │
├─────────┼────────────────────────┼─────────────────────┤
│ Failed  │ panther-33-en-portrait │ Application crashed │
└─────────┴────────────────────────┴─────────────────────┘
Test failure for example/integration_test/latest_renderer_test.dart after 2 attempts

With the same "trace" as in OP.


Add PyF>=0.11 constraint to cabal

PyF < 0.11 is broken on ghc >= 9.2

You saw the link to the 1PyF issue, right? https://github.com/guibou/PyF/issues/111
I didn't try to minimize it, but that might be a good next step.

I was unable to replicate the bug, so I hoped that adding the 0.11 constraint Would Just Work :(
What did you test it on? Which ghc/PyF versions? cabal repl or ghci?
I'm testing on ghc8107 and PyF <IP_ADDRESS> with cabal repl and it works fine... yet the nix build fails.

I could replicate it with cabal build in the nix-shell, I think? I'll check.

Yep, can reproduce.

cabal build plutus-tx-plugin

@zliu41 I've been informed you were the proponent of PyF.
PyF does have a more powerful and slimmer API, but again this is blocking the ghc9.2 upgrade.
Are you happy replacing it with string-interpolate?

Hello, PyF author here.
I'm sorry to learn about your problem and I would like to find a solution suitable for your needs.

I can fix PyF <= 0.10 for ghc 9.2 (and 9.4), it should be easy.
I can also, as proposed in https://github.com/guibou/PyF/issues/115, avoid the unsafeRunTcm trick, or at least set a flag to disable it. Actually, I'm using this "trick" in two contexts, one for error reporting with correct location, and one to detect if a variable is in scope, which was the problem observed in https://github.com/guibou/PyF/issues/111.

Do you have a reproduction of the issue which may help me try and see what solution would be the best?

Hey @guibou thank you for reaching out.
Fixing PyF 0.10 for ghc >=9.2 would be great!
We can reproduce the error only when using PyF 0.11 as a build dependency using the patched GHC coming from haskell-nix on linux (macSO works fine it seems).
To reproduce you could enter the nix-shell (any revision behind the current master, which now uses string-interpolate) after setting PyF to ==<IP_ADDRESS> in the cabal files,  and running e.g. cabal build plutus-tx-plugin.
But that is not at all a minimal reproducible example...

Would you mind testing https://github.com/guibou/PyF/pull/117 which move the "dangerous" function under the cabal flag -unsafe_error_reporting.
You may want to use PyF with this flag set to True when developing locally (i.e. no cross compilation, better error reporting) and set the flag to False in your CI.

But that is not at all a minimal reproducible example...

That's minimal enough, I'll try that, thank you ;)

https://hackage.haskell.org/package/PyF-<IP_ADDRESS>/changelog fixs the build in your codebase.

@bezirg this is getting reverted


BookStack Community Forum?

Not exactly a feature request, but more a general request: Could you set up a forum/message board, where BookStack users can ask questions, help each other and discuss?
(For instance I'm just asking myself if there is a way to link a BookStack page in a text link on another BookStack page using the page ID, so the link doesn't break if the page title gets changed. Can't figure out how to accomplish that, not documented. Saw this one, but that’s for reusing the content, not the link to the content.
Edit: Just figured out that an internal page link somehow is always memorized under its URL in the moment when linked, regardless of a later page title change and thus URL change).

Hi @Wookbert,
I'd rather not have an additional source of discussion via a forum since it gets hard to keep on top of these things.
The best alternative for open discussion would be the discord chat, Details here.
As you found, BookStack will attempt to resolve old URLs if a page has been renamed. There is some cases where this can fail so it's not 100%. It is possible to get a id-based link to a page via the popover that shows when you select some text:

This specifically references the selected section but you can just remove the hash, and all content afterwards, from the link to only reference the page.

I'll go ahead and close this since the core question has been answered and there has been no further discussion.

@ssddanbrown
So there's no plans or at least the possibility for an actual forum?
Pretty much every other open source project has a Discourse forum and maybe additionally a Discord or IRC or anything similar. Relying only on something like Discord sounds like a really bad idea not only because the platform itself is really bad but also because this type of community exchange and communication is far less result-oriented than an actual forum where you can actually find what someone has written a couple of months ago instead of getting lost in the history of inifinite chat... So it would pretty much save time in the long run to have an actual forum rather than having a chatting platform that, as already mentioned, is atrocious in the first place, because you don't have to repeat the same stuff over and over again. With a forum, you can easily find old conversations about a topic and save the time of both community members seeking help and members providing help. (That is just one of the biggest factors, there are many other reasons I can't go into detail about.)

@theAkito
I assume that time/human resources is the biggest problem here. Setting up a forum is one thing, moderating it another. We need people here who are willing to come forward and spent time and energy on this. Unfortunately I'm already loaded with work.

Yeah, @Wookbert is spot on here.
We already have the GitHub issues, the discord chat and a semi-official subreddit.
Discord acts as the informal, temporary discussion solution. The GitHub issue list is the more permanent, formal discussion solution. It'll be too much work at this time to monitor and maintain yet another community option.
GitHub are exploring the concept of discussions, I may look to enable that when available but the differences between that and issues would need to be clear, which I think will be tricky.


[Bug]: Assist action does not work

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Current Behavior
When you set the tap action as "Assist" it doesn't work and it also throws an error in the editor UI.

Expected Behavior
Assist tap action should open assist popup.
Steps To Reproduce

Set any entity (sun.sun)
Change tap action to "Assist"
Editor breaks and tap action doesn't work

https://github.com/piitaya/lovelace-mushroom/pull/1173
Context
YAML state
type: custom:mushroom-chips-card
chips:
  - type: entity
    entity: sun.sun
    tap_action:
      action: assist
    icon: mdi:message-text
    icon_color: blue
    name: Assist
    content_info: name

Environment
- Browser: Arc Browser (chromium)
- HA Version: 2023.7
- Mushroom: 3.0.0

Anything else?
No response

Hello. Did you try this https://github.com/piitaya/lovelace-mushroom#i-dont-see-the-last-changes?

Clearing the cache a few times worked!


Handle control C

We should restore the cursor when the user presses Ctrl+C, and probably add handler methods to KonsoleBlock and KonsoleApp that get triggered as well so users can clean up if it happens.

Possibly we should create a KonsoleExitException(val message: String, val errorCode = -1) which we catch in the KonsoleApp, fire all handlers, clear all data (ConcurrentScopedData stopAll?), and then exit with an error code?

When done, we should use this in Kobweb#CreateFlow to throw this exception instead of return@konsoleApp

The exception idea is bad and I should feel bad :) Often we'll want to abort from run handlers, but at that point we'll be in a different thread.
We probably need something like KonsoleApp#abort which somehow causes the app to exit at that point after cleaning up resources.

Closing this issue as we now dispose the konsole app data on Ctrl C, it's probably as good as it's going to get.
Note that #52 is still open for dealing with restoring console state, which we should still definitely do.