Provider with futurebuilder not working properly for me in statefulwidget

Hello,
provider.txt
Currently I am working in an app.
I have added provider in that app. but, i don't know how to use futurebuilder in stateful management without continuously firing future attribute.
Also, I want to add circular progress indicator while initialising, no data found message when fetch data is null. otherwise i will display data.
But, I am not able to found proper way to do it. Can you please do that thing in one of my future builder demo ?
Can anybody please suggest me a best way using provider in statefulwidget using futurebuilder and consumer attached for the file attached code.

Close the issue and use stackoverflow for questions like that.
Looking at your question I think you don't really need a Statefull widget for wrapping FutureBuilder.
In short my suggestion for you case is StatelessWidget like this:
class FutureBuilderApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text("FutureBuilder App"),
      ),
      body: FutureBuilder<List<User>>(
        future: _getUserData(),
        builder: (context, snapshot) {
          // You must check the error first
          if (snapshot.hasError) return ErrorWidget(snapshot.error);
          if (!snapshot.hasData) return const LoadingWidget();

          // the data widget
          // some thing code here...
        },
      ),
    );
  }
}

Note that if your future returns null for some reasons it will be loading always. You should make sure that you future never returns null. For example, if there is empty user list then it should return List: [], not the null.


Headless Performance Drop with Group blendMode="multiply"

Description
I've noticed that rendering Group with blendMode="multiply" in headless mode causes subsequent renders to take longer. This bug only occurs when using variables inside of Group. Using constant values yields consistent render performance. This only becomes noticeable for large canvas sizes at the scale of a few dozen renders, and eventually heals itself after a few hundred renders (I'm very confused by this part). From preliminary testing, it seems it steadily picks up from iteration 0, up until ~iteration 200 when the rendering time speeds up again. The range of rendering time spikes to ~100ms and drops back down to ~2ms.
Here's some of the cleaned up and truncated output to give a better picture of the performance curve.
Iteration 0 took 9ms
Iteration 20 took 12ms
Iteration 40 took 41ms
Iteration 60 took 83ms
Iteration 80 took 111ms
Iteration 100 took 131ms
Iteration 120 took 131ms
Iteration 140 took 126ms
Iteration 160 took 118ms
Iteration 180 took 109ms
Iteration 200 took 98ms
Iteration 220 took 88ms
Iteration 240 took 79ms
Iteration 260 took 69ms
Iteration 280 took 60ms
Iteration 300 took 50ms
Iteration 320 took 43ms
Iteration 340 took 34ms
Iteration 360 took 28ms
Iteration 380 took 21ms

Version
1.0.4
Steps to reproduce
I'm using an M3 Pro and running the script using bun 1.0.29, though testing with node yields the same results.
Snack, code example, screenshot, or link to a repository
import {
	Circle,
	drawOffscreen,
	Group,
	makeOffscreenSurface,
} from "@shopify/react-native-skia/lib/commonjs/headless";
import { LoadSkiaWeb } from "@shopify/react-native-skia/lib/commonjs/web/LoadSkiaWeb";

const render = ({ frame }: { frame: number }) => {
	const r = 10 * frame;

	return (
		<Group blendMode="multiply">
			<Circle cx={r} cy={r} r={r} color="cyan" />
			<Circle cx={r} cy={r} r={r} color="cyan" />
			<Circle cx={r} cy={r} r={r} color="cyan" />
		</Group>
	);
};

const memoryLeakTest = async () => {
	await LoadSkiaWeb();
	const surface = makeOffscreenSurface(1920, 1080);
	for (let i = 0; i < 1000; i++) {
		const t = performance.now();
		const image = drawOffscreen(surface, render({ frame: i }));

		image.dispose();
		console.log(`Iteration ${i} took ${performance.now() - t}ms`);
	}
	surface.dispose();
};
await memoryLeakTest();

Silly question: is this using the GPU or not? Because these numbers look quite ok if they run on CPU no? blending operation seems quite slow even on GPU (used to do things like inner shadows for instance).

After testing it looks like the memory leaks was just slowing down the operation and blending especially on the CPU is slow enough to see such a big difference.


Upgrade numpy from 1.26.4 to 2.0.1

Thank you very much for your work. It is very useful.
I have tried to update numpy to version 2.0.1. When doing so, pyfqmr gives the following error.
`
Python 3.11.9 (main, Aug  2 2024, 14:42:39) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import pyfqmr
Traceback (most recent call last):
  File "", line 1, in
  File "/usr/local/lib/python3.11/site-packages/pyfqmr/init.py", line 1, in
    from .Simplify import *
  File "pyfqmr/Simplify.pyx", line 1, in init pyfqmr.Simplify
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
`

Are there any plans to release a new version of pyfqmr that will make it work?

Thanks you for opening the issue and your interest in the package. We will be trying to keep everything as much up to date as possible - mostly thanks to @bwoodsend and his fast inputs. I'll close this issue for now, as pull #24 seems to be an appropriate provisional solution.

... and that's it released.


Build fails under NetBeans on Win

Hi @tessus,
with your update I'm now getting the following error when doing "Clean and Build" in Netbeans on WIn:
Executing: gradle clean build
Arguments: [-c, D:\Thomas\Development\NetBeansProjects\ownNoteEditor\ownNoteEditor\settings.gradle]

:clean
:copyBackgroundImage SKIPPED
:bundleJRE SKIPPED
:copyIcon
:copyStub
Note: D:\Thomas\Development\NetBeansProjects\ownNoteEditor\ownNoteEditor\src\tf\ownnote\ui\helper\OwnNoteEditorParameters.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: D:\Thomas\Development\NetBeansProjects\ownNoteEditor\ownNoteEditor\src\tf\ownnote\ui\main\OwnNoteEditor.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:compileJava
:processResources
:classes
:jar
:copyToResourcesJava
:generatePkgInfo
:generatePlist
:createApp
:createDmg FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':createDmg'.
> A problem occurred starting process 'command 'hdiutil''

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 0.79 secs

Build failure (see the Notifications window for stacktrace): gradle clean build

Which is true, since I don't want a Build for Mac...

I don't understand why NetBeans even tries to run the task createDmg. Or any of these tasks, because then NetBeans would go through all tasks that are returned by ./gradlew tasks which also doesn't make any sense.
Maybe there is a setting in NetBeans that allows you to specify what tasks are run for a Clean and Build.
The changes I made did not change any default behavior. I only added additional functionality.
I have no idea why this would be happening.

Let me read up on gradle. Maybe you have a setting in one of the files that specifies to run all tasks.

I've narrowed the problem down. It seems that certain tasks are added to the action gradlew build.
I opened the following ticket crotwell/gradle-macappbundle#39.

@ThomasDaheim the new pull request should fix your problem.


[globalopt] Eliminate unused field.

Some time ago I believe due to compile time I believe, we started to use
ColdBlockInfo in a per function way. So for each function, we instantiate a new
ColdBlockInfo and never use this one. So there is no reason for it to exist...

@swift-ci smoke test and merge

@swift-ci smoke test linux platform

The linux failure is not from this commit (we are failing on a Sema test)

@swift-ci smoke test linux platform


[tv2] Add support for mtvuutiset.fi

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Extracts videos from articles / web pages in mtvuutiset.fi. The videos share the backend with mtv.fi / katsomo.fi / tv2.no.

Closing in favour of #27744.

Closing in favour of #27744.


Delete is currently in progress. - Watchlist removal sometimes gets stuck

Describe the bug
Sometimes the REST API/CLI/Portal - Remove watchlist will fail to remove and be stuck for an indefinite period of time
To Reproduce
Steps to reproduce the behavior:

Remove a large watchlist
It will sometimes get stuck on 'Delete is currently in progress.'
Wait for an undefined amount of time
Watchlist is removed

Expected behavior
Watchlist removal process does not get stuck or stops/retries if it fails to do so after some predefined time.
Screenshots

Additional context
Do note that said watchlist was tried to be removed with both AZ CLI/Rest API/Portal. In each of those cases it tells me 'Removed watchlist 'name' successfully!'
But it never actually goes away from the environment and causes the deployment process to fail.
This is what MSFT recommends as there is no 'replace' watchlist function. To update a watchlist (e.g. remove entries) you need to remove it and then push it.
https://learn.microsoft.com/en-us/azure/sentinel/watchlists-manage#:~:text=If you've deleted an item from your watchlist file and upload it%2C bulk update won't delete the item in the existing watchlist. Delete the watchlist item individually. Or%2C when you have a lot of deletions%2C delete and recreate the watchlist.
Again, this has been occuring for over a year now but it's never been resolved/addressed. It's an intermittent issue that causes some pain for us. The 'undefined' amount of time can be even up to a week! - if it were 30 minutes it wouldn't be that bad. But it can block us from updating a critical watchlist.

Hi @Kaloszer , Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 01Mar24. Thanks!

Hi @Kaloszer, Have you open any support case for this issue? As you mentioned this issue occur if operation perform only for large Watchlist, not for any specific one.
Thanks!

@v-sudkharat - what is this repository for if not for raising issues :)?
It's been happening for years:
https://learn.microsoft.com/en-us/answers/questions/506415/cannot-delete-watchlist-upload-is-currently-in-pro

More than two weeks with this problem in the production environment. Please, can someone help us? . We opened a case weeks ago, but they don't solve ANYTHING.

https://techcommunity.microsoft.com/t5/microsoft-sentinel/sentinel-watchlist-stuck-in-queued-state-for-days/m-p/3747521

I spoke with Microsoft support who cleared the queued watchlists in a few different workspaces. They confirmed that there was no option for me to do this from the Azure Portal and if it happens again to just contact them to fix.
Bit of an odd one.

It seems to be a known issue according to that last entry - and having to rely on MSFT to clear some queue is not really a solution.

@Kaloszer, We appreciate you have highlighted this issue with us over this repo, It would be great if you let us know if you have already open support case for this issue, so we can check on it and take follow up on that to get unblocked you from this issue.
Thanks!

I don't have the issue currently but that does not mean that the issue does not exist and should be addressed.

Hi @Kaloszer, we will check this issue with our concerned team, and will update you. Thanks!

@v-sudkharat - what is this repository for if not for raising issues :)?
It's been happening for years: https://learn.microsoft.com/en-us/answers/questions/506415/cannot-delete-watchlist-upload-is-currently-in-pro

More than two weeks with this problem in the production environment. Please, can someone help us? . We opened a case weeks ago, but they don't solve ANYTHING.

https://techcommunity.microsoft.com/t5/microsoft-sentinel/sentinel-watchlist-stuck-in-queued-state-for-days/m-p/3747521

I spoke with Microsoft support who cleared the queued watchlists in a few different workspaces. They confirmed that there was no option for me to do this from the Azure Portal and if it happens again to just contact them to fix.
Bit of an odd one.

It seems to be a known issue according to that last entry - and having to rely on MSFT to clear some queue is not really a solution.

Hi @Kaloszer ,Will do detailed analysis on this issue and will update you

Hi @Kaloszer ,After analysis ,identified the scenarios of the issue ,working on replicating the issue at my environment,will update you

Hi @Kaloszer ,Still need some more time for replicating the issue,,will update you

Hi @Kaloszer ,It seems the issue is with large size and working on having the similar watchlist,will update once replicated from my end and will try to delete in another approach

Hi @Kaloszer ,Still need some time as unable to find the large size watchlist for replicating  the issue, with larger size data,will update you

@v-muuppugund Easiest way to replicate this issue would be in my opinion to have a loop of a large watchlist that will do the following logic:
deploy > remove > deploy > remove -> and so on for a few hours. Eventually you will hit the aforementioned issue where the deployment will fail.
If luck would have it you'd also experience the behaviour I mentioned earlier - that even if you attempt to remove it from the portal/az cli - even though it's saying it's 'removed' -> when you look at the pipeline (that would be still running as it should retry on failure) it would still be giving you the 'failed to remove' error.

@v-muuppugund Easiest way to replicate this issue would be in my opinion to have a loop of a large watchlist that will do the following logic:
deploy > remove > deploy > remove -> and so on for a few hours. Eventually you will hit the aforementioned issue where the deployment will fail.
If luck would have it you'd also experience the behaviour I mentioned earlier - that even if you attempt to remove it from the portal/az cli - even though it's saying it's 'removed' -> when you look at the pipeline (that would be still running as it should retry on failure) it would still be giving you the 'failed to remove' error.

Apologies for the delayed response,Sure @Kaloszer ,Will check and let you know

@v-muuppugund Easiest way to replicate this issue would be in my opinion to have a loop of a large watchlist that will do the following logic:
deploy > remove > deploy > remove -> and so on for a few hours. Eventually you will hit the aforementioned issue where the deployment will fail.
If luck would have it you'd also experience the behaviour I mentioned earlier - that even if you attempt to remove it from the portal/az cli - even though it's saying it's 'removed' -> when you look at the pipeline (that would be still running as it should retry on failure) it would still be giving you the 'failed to remove' error.

Apologies for the delayed response,Sure @Kaloszer ,Will check and let you know

Hi @Kaloszer ,unable to replicate the issue,We will discuss the issue in today's call

Hi @Kaloszer ,As discussed on Monday i.e. 8Apr2024 , reached our backend team over an email, will update over an email once have an update, we are closing your issue (https://github.com/Azure/Azure-Sentinel/issues/10107) as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation!

@v-muuppugund Before closing the issue, provide a tracking Id to reference.

@Kaloszer As we are unable to raise ICM independently, so reached CSS team and they suggested support case from azure subscription, so they can assist you.

Hey @v-muuppugund, what would be the correct way to report this so we can actually get a resolution to long standing issues and bugs?
It seems that this is a never-ending circle, raise issue here then here, get no actual solution and it gets bounced around for months until we actually reach the product team.
In a previous UEBA issue it was addressed by the product team eventually after raising said support case:
https://github.com/Azure/Azure-Sentinel/issues/8883
For this set of issues:
https://github.com/Azure/Azure-Sentinel/issues/10044
https://github.com/Azure/Azure-Sentinel/issues/10106
https://github.com/Azure/Azure-Sentinel/issues/10107 (we need the root cause or assurances this wont happen again)
I could of course raise another set of support cases but it seems as if for this one I'm also getting a run around and it will take some time to get the issue to the product team.
As we're an MSSP most of the time we can't raise support cases within a customers tenant (as either they don't have a support plan paid for, or we don't have access and will never get it.
Just for sanity sake, what should and should not be reported in this particular repository, would product issues go here, or should they go straight through internal Azure support system? Just to skip the run-around.

Hey @v-muuppugund, what would be the correct way to report this so we can actually get a resolution to long standing issues and bugs?
It seems that this is a never-ending circle, raise issue here then here, get no actual solution and it gets bounced around for months until we actually reach the product team.
In a previous UEBA issue it was addressed by the product team eventually after raising said support case: #8883
For this set of issues: #10044 #10106 #10107 (we need the root cause or assurances this wont happen again)
I could of course raise another set of support cases but it seems as if for this one I'm also getting a run around and it will take some time to get the issue to the product team.
As we're an MSSP most of the time we can't raise support cases within a customers tenant (as either they don't have a support plan paid for, or we don't have access and will never get it.
Just for sanity sake, what should and should not be reported in this particular repository, would product issues go here, or should they go straight through internal Azure support system? Just to skip the run-around.

HI @Kaloszer ,  I understood your point, as I don't have access to backend system, so reached our team internally on this ,as per their suggestion asked to raise azure support case for this issue,

shared response in comment -https://github.com/Azure/Azure-Sentinel/issues/10107#issuecomment-2074880736

@Kaloszer Encountering this bug and found this issue.
I have a logic app that creates a watchlist based on the output of various graph API requests/Azure rest api requests (approximately 10-20k rows). Every night when the logic app triggers, its set to delete the former day's watchlist and recreate. I've added a 6 minute delay in between the deletion and creation phases, but it continually breaks with the error "Cannot upload watchlist 'Resources'. Delete is currently in progress"
I need the delete/recreate step, because otherwise the watchlist will hit the million row capacity after a few weeks of the logic app doing a nightly update on the state of resources.

Recommended using the 2024-04-01-preview or later API versions to avoid this issue when calling the API.
This API version will return a 202 (Accepted) status code for the "Delete a Watchlist" action, along with an "Azure-AsyncOperation" header, which can be used to poll for the status of the delete operation. The upload operation also returns a similar status header.
For logic apps, our internal teams are working on updating the actions to use the new API version. In the meantime, we are in the process of releasing V2 actions specifically for delete operations, with deployment expected in the next few weeks.
Once deployed, you should use this V2 action for delete operations and use the Azure-AsyncOperation header to poll for the status of the delete and only start the upload operation once the delete status is 100%.
If you cannot wait for the deployment and need a fix sooner, we recommend using the 2024-04-01-preview REST API with the HTTP logic app connector (instead of Sentinel) and using the headers to poll statuses.
Please note that adding a delay of hours might not always work because we don't know how much delay the operation would require technically due to the environmental complexity in each customer's environment. As an immediate solution, the best approach is to follow the workaround by using the HTTP connector to mock an API call.
Another workaround : Use of the new alias names for the watchlist. ( temporary)
++++++++++++++
Recommended  solution 1:
To set up the workflow for deleting a watchlist in Sentinel and using the Azure-AsyncOperation header to poll for the status of the delete operation.

Use the 2024-04-01-preview API Version: Ensure you are using the 2024-04-01-preview or later API versions to avoid issues with deleting and immediately uploading watchlists with the same alias. You can find more information about the API version lifecycle  here:  | Microsoft Learn](https://learn.microsoft.com/en-us/azure/ai-services/openai/api-version-deprecation
)Delete a Watchlist: When calling the API to delete a watchlist, the API will return a 202 (Accepted) status code along with an Azure-AsyncOperation header. This header contains a URL that you can use to poll for the status of the delete operation. You can refer to the  Watchlists - Delete - REST API (Azure Sentinel) | Microsoft Learn for  details.
Poll for Status: Use the Azure-AsyncOperation header URL to poll for the status of the delete operation. Continue polling until the delete status is 100%. Detailed information on how to track the status of asynchronous operations can be found at  Status of asynchronous operations - Azure Resource Manager | Microsoft Learn
Upload Watchlist: Once the delete operation is complete, you can proceed with uploading the new watchlist. You can refer to the [Watchlists - Create Or Update - REST API (Azure Sentinel)]](https://learn.microsoft.com/en-us/rest/api/securityinsights/watchlists/create-or-update?view=rest-securityinsights-2024-09-01) for more details.

Here is a sample workflow using the HTTP logic app connector (Please feel free to edit as per your business needs)

Create a Logic App: Start by creating a new logic app in Azure.
2. Add HTTP Action for Delete Operation:
Add an HTTP action to call the delete watchlist API.
Set the method to DELETE.
Set the URI to the delete watchlist API endpoint.
Capture the Azure-AsyncOperation header from the response.
3. . Add HTTP Action to Poll for Status:
Add another HTTP action to poll the status of the delete operation.
Set the method to GET.
Set the URI to the value of the Azure-AsyncOperation header.
Use a loop to continue polling until the status indicates that the delete operation is complete
** 4 Add HTTP Action for Upload Operation:**
Once the delete operation is complete, add an HTTP action to call the upload watchlist API.
Set the method to POST.
Set the URI to the upload watchlist API endpoint.

For more detailed information and examples, you can refer to the Status of asynchronous operations - Azure Resource Manager[3].


brush, pointer

Related #4. Like the new brush mark, except whatever is near the pointer is considered selected. It defaults to searching in a radius around the pointer in x and y, but you can configure it to search only along a single dimension, too.
https://user-images.githubusercontent.com/230541/151642007-86ba0519-7292-49fd-a375-1b31f2ffc29f.mov
TODO

[x] Draw little whiskers connecting the pointer to the selected points Fun, but no.
[x] An n option for selecting the n closest items to the pointer
[x] Have the default r vary depending on whether n is finite
[x] Should the pointer mark display anything when there’s a selection? Yes.
[x] Should you be able to control what the pointer mark displays, or is it just 4px-radius circles? No.
[x] Validate the mode option
[x] Optimize the display so that only the visible circles are instantiated
[x] A mode where things are only selected while the pointer is down?
[x] … or maybe that just happens automatically (ephemeral hover; persistent drag)
[x] … and where shift-dragging will add to the current selection?
[x] … and maybe option-dragging removes from the current selection? Maybe in the future.
[x] Do something nice for band scales?
[ ] Support data transforms (e.g., bin and group)
[ ] Support x1, x2, y1, and y2 (e.g., for selecting bins or rects)
[ ] Support mode = “rect” for rect selection, mode = “point” for point selection

From the screen capture my feeling is that this is a different system than the one implemented for brush. With brush, the interaction mark shows the selected region, and is not responsible for highlighting the selected data points. Here the interaction mark shows the individual selected dots.
We should aim for a consistent approach (brush, lasso, pointer) and just show the selection region as an overlay of the corresponding shape.
The task of highlighting the selected marks is the same in all cases, and would be handled by the dot mark instead, maybe with the suggested selected: { stroke: "red" } option?
Rather than mode, could we use pointer, pointerX and pointerY? Conversely, would we prefer to remove brushX brushY and have only one brush with a mode option? (I think I like the mode approach better, if it works consistently.)

We should aim for a consistent approach (brush, lasso, pointer) and just show the selection region as an overlay of the corresponding shape.

Consistency is generally a good thing, but it’s worth thinking this through.
I find it helpful to think of two forms of selection: the geometric selection and the logical selection.
The geometric selection describes the area—some region of the plane—that is selected. For a brush that is an axis-aligned rectangular region defined by x1, x2, y1, and y2. For a lasso it is some complex polygon or set of polygons. For a pointer it might be a circle around the mouse, or an infinitely tall or wide region for one-dimensional pointing. Or, it might be a buffered region of a given radius around the path traveled by the pointer (in the case of the more persistent “spray paint” pointing that I’d like to implement). In some cases, say if we select the n points that are closest to the pointer, there might not be a simple definition of the geometric selection!
The logical selection describes which data are selected. In Plot this is represented exclusively by a subset of the mark’s index (node[Plot.selection]). This is the value that the plot exposes to the rest of the notebook, so you can e.g. show a table or a coordinated visualization. The logical selection, in a sense, is what matters to the user. It’s what the user seeks to control through interaction. The geometric selection is the means to that end: how to indicate that selection (conveniently). So, showing the logical selection, perhaps in addition to the geometric selection, is usually a good thing because it provides more direct feedback as to the effect of the user’s input.
In the case of a brush, the geometric selection is persistent: after brushing a rectangular region, you can drag that rectangular region around. We could, possibly, do this behavior with the lasso as well, where you draw an arbitrary polygon, and then you can pick up and move that polygon around to change your selection. But I don’t think we want or need that. Instead, my expectation with a lasso is that the geometric selection (the polygon) is ephemeral: it dissolves as soon as I lift the pointer, and I’m left only with a logical selection as a set of selected points. Similarly when I’m using the pointer, if we want to support a persistent selection where I can click and drag to select some points near the mouse, and then shift-click and drag to select some other points, I’d rather just see the logical selection. I don’t think I want a visual representation of a buffered region around the path of the pointer while it was down.
The challenge with showing the logical selection is that, unlike the geometric selection, we may not know an appropriate visual representation. If interaction marks only understand that you’re selecting infinitesimal points in x and y, then we could draw circles around those points, say, but that might not be a great representation say when you’re selecting circles of varying radii, or bars, images, rects, etc. But, maybe that’s fine? Maybe it just needs to convey a hint that you’ve selected something, even if it’s not perfect. The goal of Plot is just to get you something “good enough”, quickly.
As we’ve discussed, I like the idea of an internal selection channel maintained by Plot and some mechanism for marks to express style overrides when selected. Maybe it’s even possible for Plot to have defaults so that all marks have a default selected state. But there remain a variety of technical and design challenges to get this to work, and we’ve already merged the brush mark and I would like to add pointer, lasso, and perhaps others. Perhaps when we add selection styles in the future, we change the interaction marks so that they don’t have a visual representation of the logical selection? Or at least a way to turn it off.

Rather than mode, could we use pointer, pointerX and pointerY? Conversely, would we prefer to remove brushX brushY and have only one brush with a mode option? (I think I like the mode approach better, if it works consistently.)

It’s useful to control separately (1) whether the points to be selected are defined in x or y or both and (2) whether the selection region around the pointer is defined in x  or y or both. As I showed in the video, the points are defined in x and y, but I only want to select in x. I think this will be a common pattern when there is an independent and dependent variable (e.g., time and temperature, respectively). Also, the separate constructors (pointer, pointerX, and pointerY) don’t just set the mode, they also providing convenient defaults for x and y: maybeTuple if both x and y are specified, and otherwise identity if only one of x and y is specified. I think we want to maintain this pattern for consistency with other marks in Plot. I think the defaults are setup correctly that you won’t have to think about it most of the time, I hope.
If we want the brush to show the logical selection, we’ll need to take the mode option implemented here and implement that for brush, too.

Here’s my other idea for a visual representation of the logical selection. The first video shows mode xy and the second mode x.
https://user-images.githubusercontent.com/230541/151676770-28a3b5de-60a3-4b66-b072-c241f5725aa1.mov
https://user-images.githubusercontent.com/230541/151676771-e8837560-25aa-493d-aea6-72100fcd4cb0.mov
It looks kinda neat, but I don’t think it will work as well when we make the pointer selection persistent using click-and-drag (and letting you point to multiple areas with shift-click-and-drag, or deselect with option-click-and-drag). And also this style wouldn’t work with the brush, where the position of the pointer isn’t relevant. And, perhaps most importantly, while looking cool it does put most of the emphasis on the pointer location which is already visible with the pointer anyway. But leaving it here for the record. 🙂

Rather than mode, could we use pointer, pointerX and pointerY?

Maybe a different interpretation of your comment is that pointer means mode = xy, pointerX means mode = x, and pointerY means mode = y. So, you’d never need to specify the mode option (or perhaps, you’d only specify the mode option with pointer, but we’d expect you to use pointerX or pointerY instead). However, unlike Plot’s other similar constructors such as dotX and dotY, you’d be allowed to specify a y channel for pointerX, or an x channel for pointerY. Maybe that’s confusing? I think maybe that‘s confusing but it’s not a strong preference so let me know what you prefer.

I'm confused by your remark since dotY does accept both x and y (it's just defaulting y to identity, and x to undefined) ;-)
Anyway, yes, I'd be inclined to use pointer as 2d (mode=xy), pointerY as mode=y and pointerX as mode=x, and in that case there is no need to expose "mode" as an option.
In terms of visual feedback, I don't like the circle much since it moves in sporadic jumps, whereas the link version is a bit less jarring as it's never static (it's still very jumpy though); but this can probably be smoothed out with a (quick) transition, a less aggressive shape and color, I don't know. link + circle would work too, the link easing the visual movement, but stopping before it actually occludes the target.
I think i'd use it most often to select the (n = 1) closest element to the pointer rather than a whole range, but it's more gut feeling than any experience with this type of selection mechanism. My hunch is that with a large n the flock of lines will tend to occlude a majority of the selected dots, and the ones that are not occluded will be those farthest from the pointer, which seems a bit opposite to the goal.

I'm confused by your remark since dotY does accept both x and y

Oh, whoops. I got confused because it wasn’t always that way; prior to 5b81573b374129f7d1811d0644ba6e2625841472 dotX forced y to be null, and dotY forced x to be null.
So, does this mean brushX should allow y, and brushY should allow x? 🤔
https://github.com/observablehq/plot/blob/551f53a1b1a63cd9c099e125f4c8929ce13f52f6/src/marks/brush.js#L81-L87

I think the difference between brushX(… {y}) and brush(… {y}) would be if the brush highlights the logical selection; in the first case brushX(… {y}) the brush is horizontal, but the highlighted values are dots positioned in x and y. In the second case it is a 2-d brush.

Okay, I think I got it in the latest commit. Now brushX and brushY allow you to specify y and x, respectively. And pointerX and pointerY similarly only provide defaults for mode and x and y, respectively, while allowing you to specify y and x respectively.

I’ve implemented persistent selection (click and drag, and shift-click and drag). Let me know what you think, @Fil!

Some open tasks:

[ ] Allow the radius of pointer circles to be specified as r (a constant? a channel?).
[ ] Rename the current r option to distance, or something else, maybe maxR?
[ ] Allow fill on pointer. (It’s currently overridden by fill="none".)
[ ] Allow the fill and stroke be specified as channels, not just constants?
[ ] Making clearing the persistent pointer selection less twitchy. (Any pointermove will interfere.)
[ ] Allow dx and dy on pointer.
[ ] For one-dimensional pointers, draw blue rules rather than dots?
[ ] Support data transforms (e.g., bin and group).

The last task also applies to the brush—it’ll require some core changes, not just changes to pointer. The problem is that mark.data isn’t the same as the data returned by the transform. We have to decide whether we’re selecting from the original (untransformed) data or, perhaps more likely, selecting from the transformed data (e.g., selecting bins).

This branch currently breaks brushX and brushY on a 2-d scatterplot.
can be fixed by 020a1ea5bec4776698193a57eac44b6faa4d132d

This branch currently breaks brushX and brushY on a 2-d scatterplot.

Based on our earlier discussion, it is behaving as expected. (Or, it’s not clear what you mean by “breaks”.) In your example you are specifying x and y, so brushX behaves the same as brush. The only difference between brush, brushX, and brushY is the defaults for x and y.
If you want one-dimensional brushing:
Plot.brushX(data, {x: "culmen_depth_mm"})

Or:
Plot.brush(data, {x: "culmen_depth_mm"})

If you want two-dimensional brushing:
Plot.brush(data, {x: "culmen_depth_mm", y: "culmen_length_mm"})

The case I found "broken" is when you want the data to be a 2-d scatterplot, and the brush to be on X only. This (in my mind) is what you want when you say brushX(data, {x, y}). It's also what's currently implemented in main.
Since we're not highlighting the logical selection, it's true that we can use brush(data, {x}) instead. Maybe I just need to adapt my mental model… but for now I don't see what is the purpose of brushX and brushY anymore, if the mode is driven by the x and y options. 🤔

but for now I don't see what is the purpose of brushX and brushY anymore, if the mode is driven by the x and y options

It’s the same as dotX and dotY. The only purpose is to specify different defaults.
https://github.com/observablehq/plot/blob/94d69a54eea6a085657e66c04b8412da51bacff8/src/marks/dot.js#L95-L101
The brush doesn’t support a mode option currently. We could add one for symmetry with the other marks, but it’s a little redundant because brush doesn’t need the x and y channels in the other modes. Meaning if we did, you’d be passing in (and computing) the y channel with mode = x, but you wouldn’t be using it for anything.

I've reverted my commit and updated my mental model!

I’ve made a few small improvements (to handle band scales, to improve the display of one-dimensional pointing using rules instead of circles, and to change the default n to 1). The big outstanding tasks are:

[ ] Support data transforms (e.g., bin and group)
[ ] Support x1, x2, y1, and y2 (e.g., for selecting bins or rects)

I’m currently thinking that when you use brush or pointer with a transform, that you’re still selecting the source (input) data, i.e., the data prior to aggregation; you won’t be selecting e.g. bins.

This branch now reverts #748, restoring the brush #71 and fixes #5.

Hey guys – any update on this? I saw this demo on observable not sure if it ever got released) but would be keen to see this feature in a recent version on NPM 🚀


exec -> execFile

The child_process.exec command is insecure and it is usually suggested that child_process.execFile be used instead.  Thoughts on switching it?
@contra @sindresorhus

exec sends the command to the shell, execFile sends it directly to the process. The former is more insecure indeed, but has a lot more possibilities. You can only do simple stuff with execFile: git clone, while with exec you can do git status | grep foo && git clone; echo done.
I think both has a merit, but execFile should be preferred whenever possible. Might make sense to have this task support both, but with a big warning about preferring execFile whenever possible and the dangers of exec.

In general, don't use gulp-exec, use child_process.exec or child_process.spawn directly.

That's what we suggest but people are still going to use this plugin, so it's not really valid to dismiss the issue for that reason.

https://ant.apache.org/manual/Tasks/exec.html


feat: bounded discrete time

Description

put a lower bound on block time (previous block time)
put upper bound on the block time (less than peer current time)

Linked issue

Closes #{issue_number}

Benefits
now have a bounded concept of time that is synchronized across peers.
the time is discrete with increment intervals being the time between 2 blocks
Checklist

[ ] I've read CONTRIBUTING.md
[ ] I've used the standard signed-off commit format (or will squash just before merging)
[ ] All applicable CI checks pass (or I promised to make them pass later)
[ ] (optional) I've written unit tests for the code changes
[ ] I replied to all comments after code review, marking all implemented changes with thumbs up

Can you provide more context for this change.

Sequence of blocks is now guaranteed to have monotonically increasing time. The leader can't just completely fabricate the voted block's creation time because the creation time has to be within some limits (after previous block creation time, but before current validator/observer/proxy node time). If the leader tells a lie within the imposed limits, given enough rotations we should again arrive to the correct value of the time. On average, I'd say that time should remain quite close to the current time (a little bit behind, never in the future).

Also i can't see synchronization part of this PR, am i missing something?

I removed that word. I meant that it's synchronized in the sense that everybody can agree when the block was created (within an interval). Peers can use blocks creation time to reason about current time. Whatever is the last creation time is the current time across all peers and it increases discretely in intervals.
Example

A block was created at 11:25AM and committed
11:25AM becomes the current time (the network is certain that the actual time is no less than that)
Block was committed at 11:35
11:35AM becomes the current time (the network is certain that the actual time is no less than that)

time is discrete in the blockchain because 11:30 is not a valid time, only 11:25, 11:35, etc are valid timestamps
Implementing time based logic in a smart contract
A smart contract can be given latest block creation time as the current time (a sort of synchronization point) and have logic based on that (understanding the limitations). In the previous example, if the smart contract was written so that it performs a certain action if time is past 11:30AM, it will do it at 11:35AM. But the time of the execution is guaranteed to never be less than 11:30AM

To avoid block rejection can't leader select block time to be as close to the previous block time as possible?
I think it would be considered valid because it's in the range (previous_block_time, min(voting_peer_current_time_1, voting_peer_current_time_n)].

To avoid block rejection can't leader select block time to be as close to the previous block time as possible? I think it would be considered valid because it's in the range (previous_block_time, min(voting_peer_current_time_1, voting_peer_current_time_n)].

yes, but then the next leader will correct it, or the one after that. The error doesn't compound or get propagated indefinitely. Network time can drift from the actual current time but not too far.


Picasso not load images from YouTube Thumbnails On Android Pie Devices And Above

I'm Manually Upload Some Images For My Admin Control Panel It will Shows. But Youtube Thumbnails Not Loading Properly On Pie Devices. In Lower Version Of Devices Its Shows Fine?
What's a Problem ?????

There's no information here to diagnose a problem and it's not clear why you think it's specific to this downloader.


access_token Authorisation issue (provide an example for access_token usage?)

I've been trying to add a new room via a request to my server
fetch('http://localhost:3001/newRoom', {
                    method: 'POST',
                    headers: {
                        'Content-Type': 'application/json',
                        'Authorization': 'Bearer '+btoa(this.state.accessToken)
                    },
                    body: JSON.stringify({
                            creatorId: (this.state.origin_username).toString(),
                            name: `${this.state.origin_username}&${this.state.dest_username}`,
                            userIds: [currentUser.id,this.state.dest_username]
                    })
                })
                .then((response) => {
                    console.log(response.json());
                })
                .catch(error => console.error('error', error))

However I receive this error
error: 'services/chatkit_authorizer/authorization/invalid_token_subject',   error_description: 'Missing token subject',   error_uri: 'https://docs.pusher.com/errors/services/chatkit_authorizer/authorization/invalid_token_subject'
I'm unsure if I'm making a silly error or whether there is an issue with SDK. Some more documentation on the topic would probably resolve this either way :)

Looks like your Auth Pusher server is not returning the correct data to your ChatKit client.
Using express 4.x you can this in your Node.Js server:
   const auth = chatkit.authenticate({
      userId: user_id, // your app user id
      authPayload: req.body,
    });
    return res.json(auth.body);

See also this example:
https://github.com/pusher/chatkit-server-node/blob/master/examples/auth_server.js

A missing subject means that there's no sub claim in the token that is being generated. We use the sub (subject) claim to store the user's ID, so it sounds like you're not providing a user ID when you generate your token(s).

It was to do with the


Replace btcd with bitcoincore in docker/docker-compose

Continue to use btcd in itest docker-compose because it's needed for simnet testing.

https://github.com/yzernik/squeaknode/pull/481


For Discussion : Iframe Service

I got a very basic iframe implementation working and I wanted to get some feedback before I get too far down the rabbit hole. At this point I just duplicated the Popup service and made the minimum changes required to get an iframe approach to work in a test app. Issues that could use discussion are:

There's a lot of code that I didn't touch, which I'm thinking should probably be extracted into a mix-in that both services can use.

I'd love to hear some thoughts about how the iframe service should be used instead of the popup service. For testing this implementation I just registered the iframe service AS the popup service in lib/torii/bootstrap/torri.js. Maybe we just add documentation about how someone would override this in an application specific initializer? Another route would be to register it as the iframe service and then create a new batch of providers that know to look for the iframe service instead of the popup service, but that seems like a bunch of unnecessary code. To my mind a provider shouldn't care whether the OAuth flow is happening via popup or iframe. That seems more like an application configuration option.

Managing the iframe needs work. At this point when you open the iframe service I'm just unceremoniously appending an iframe element to the end of the body, with an id of torii-iframe. Then when you close the service I'm just removing it. This seems.... inelegant. Anybody have any thoughts about how we should approach this? Maybe you pass an element or element id to open so that we know where to put the iframe? Maybe we require you (or give you the option) to transition to some route where you setup the iframe yourself? Also, with the popup service the user could close the window to 'opt out' of signing in. Do we need to offer something similar for the iframe?

I just realized that we'll also need a way to make the RedirectHandler not call windowObject.close(). For some reason it's not happening to me, but a user reported that after the iframe returned from the provider that their tab was automatically closed. After looking at it I can totally see why, but I'm not sure why it's not happening in any of my browsers.

I went ahead and did some refactoring to eliminate all the duplicate code. I think this makes it much easier to actually see what's going on. I pulled most of the code from lib/torii/services/popup.js into lib/torii/mixins/services-mixin.js. Now popup.js contains only the code that's directly related to opening and closing the popup window itself. Likewise iframe.js only deals with the iframe and not any of the other setup. The services-mixin.js contains the main open method, which still does all of the setup for remote URL options, setting the request ID and what not. Then instead of opening a popup/iframe directly it calls openImpl which is defined in each service. Each service implements close to handle tearing down the popup or iframe.

The config or developer experience using this is still hazy. Appending the iframe to the body is hardly ideal. Perhaps open could be passed the parent DOM node of the iframe as an argument and the iframe service would append to that. Need to ponder some more.

Yeah, adding the iframe to the body is not great. I think passing in the parent node makes sense. And maybe we fall back to body if you don't pass anything.

So, thinking through the iframe use case some more, if we have it so that you have to pass in a DOM node, I'm imagining that the flow will go something like this:

User click 'Sign in' firing some signIn action
The signIn action opens an in-window modal of some sort
The signIn action calls open with something like this.get("session").open("clickfunnels-oauth2","#modal-inner-content");
We append the iframe to #modal-inner-content

I'm further imagining that the modal will have some sort of UI element to allow a user to decide not to sign in (some way to close the modal). In that case we'd either need to poll the iframe to see if it has disappeared, much like we do with the popup, or we'd need to instruct people to manually trigger didClose in the method that's responsible for tearing down the modal.
Thoughts on the best approach?

With the latest changes in this branch and the code below I've been able to put together a reasonable user experience for the iframe flow. When a user clicks 'Sign in' a modal opens with a login form. If the user signs in successfully the modal goes away and they're logged in. If the user clicks outside the modal form, the modal goes away and the torii promise rejects.
With this implementation, when the modal is closed it's up to the application developer to remove the #torii-iframe element from the DOM so that the pollRemote method will see that it's gone. This works, but it doesn't feel quite right.
I'm sure it can use some more polish under the hood. I'd love to hear feedback.
// app/routes/application.js
import Ember from 'ember';

export default Ember.Route.extend({

  beforeModel : function(){
    return this.get("session").fetch().catch(function() { console.log('in the fetch callback catch!'); });
  },

  actions: {
    signIn: function() {
      Ember.$('body').addClass('signingIn');
      Ember.$('#signin-modal-back').one('click',function(){
        Ember.$('#signin-modal-content').html('');
        Ember.$('body').removeClass('signingIn');
      });
      this.get("session")
        .open("clickfunnels-oauth2",{ iframeParent : '#signin-modal-content'})
        .then(function(){
          Ember.$('body').removeClass('signingIn');
        });
    },

    logout: function() {
      this.get("session").close();
    }
  }

});

{{#if session.isAuthenticated}}
  Logout
  {{ log session.isAuthenticated }}

  {{outlet}}
{{else}}
  <button {{action "signIn"}}>Sign in</button>
{{/if}}

And then in config/environment.js the torii object looks like this:
    torii: {
      sessionServiceName: 'session',
      remoteServiceName: 'iframe',
      providers : {
        'acme-oauth' : {
          apiKey : 'xxx'
        }
      }
    }

And just for good measure, the CSS for the modal:
iframe{
  width:100%;
  height:500px;
  border:1px solid blue;
}

#signin-modal-back{
  display:none;
}

body.signingIn #signin-modal-back{
  display:block;
  position:absolute;
  left:0;
  top:0;
  width:100%;
  height:100%;
  background:black;
  z-index:1000;
}

body.signingIn #signin-modal-frame{
  position:absolute;
  top:100px;
  left:50%;
  margin-left:-250px;
  width:500px;
  height:500px;
  padding:10px;
  background:#dedede;
}

I've been playing with this some more and have an alternate iframe implementation working with a liquid fire modal.
Along with the changes mentioned above to config/environment.js I have:
In router.js
this.modal('signin-modal', { withParams: 'signIn' });

In controllers/application.js
queryParams: ['signIn'],
signIn: null

In routes/appication.js
  beforeModel : function(){
    return this.get("session").fetch().catch(function() { console.log('in the fetch callback catch!'); });
  },

  actions: {
    signIn: function() {
      var _this = this;
      this.controller.set('signIn','');
      Ember.run.next(this,function(){
        this.get("session")
          .open("clickfunnels-oauth2",{ iframeParent : '#signin-modal-content'})
          .then(function(){
            console.log('we are signed in....');
            _this.controller.set('signIn',null);
          },function(error){
            console.log('sad panda', error);
          });
       });
    },

    logout: function() {
      this.get("session").close();
    }
  }

And in templates/components/signin-modal.hbs

@jagthedrummer I will have time to give this some attention this week. I just want to make sure the API design is something we can live with for a while.

Great! Thanks for the update. So far this has been working well for us.

I just ran into a situation where we're going to want to be able to opt in to the iframe service on a per provider basis. For our own "internal login" we want to use the iframe, but we also need to provide for Stripe Connect. Stripe has X-Frame-Options set to SAMEORIGIN, so an iframe won't work for them. I'll be looking at what it will take to set this at the provider level instead of for the whole app.

Hey guys, just wondering if there's anything I can do to advance this. The master branch has changed quite a bit since I submitted this PR and I'm currently in the process of getting this branch up to date with all the latest stuff. I'd sure love to avoid having to do that more that once if possible.

OK, I have a branch of this that's up to date with the current master branch. Should I force push over this branch/PR or push a new branch and open a new PR?
We ended up handling Stripe in a different way, so I didn't do anything for making it possible to configure popup vs iframe on a provider by provider basis. I suspect that it would be needed in some cases, and I'd be happy to help figure out how to make that happen. In the interest of not needing every single provider to check the config to know which 'popup' to request I'm thinking that during initialization we'd need to override the 'popup' object in any providers that are configured to use the iframe remote. If that's a reasonable approach, it seems like lib/torii/instance-initializers/walk-providers would be the place to do it. Does that sound right?

@jagthedrummer how about a fresh PR and we can close/archive this one. I will absolutely make time to think about the API around this.
Providers should be able to change this, agreed. I think the config should be something providers read to pick a service (popup or iframe) when one is not provided. I'm unsure, but it sounds like there also must be a config for the default DOM node to connect the iframe to?
Actually, IMO we should just publish a component that the consumer must put in their application.hbs or wherever they want the iframe to appear.

Friday at the latest for more design thoughts. If you can make time Friday morning to chat perhaps we can sync on it.

Sounds good. Closing this PR and will open a new one shortly.

Also, some time on Friday morning should work for me.


Save 3D, 2D+c or 2D+t test and sample images correctly

Hi!
I'm converting the ZCDL4M 3D U-Net notebook with the bioimageio.core code and I see that 3D images are not properly stored. This also happened to StarDist as far as I remember when the images were 2D + channels. Could it be possible to correct it?
Thank you!

Hi @esgomezm,
I think that this is a discrepancy with how tifs with more than 2 dimensions are written here and read in deepImagej/Fiji.
And this is definitely something we want to fix. Currently, the code for writing the tif samples is here.
So we would need to adapt this code so that it's compatible with deepIJ. But I don't really know how to test this easily, as I can read it back correctly in python, e.g. for the stardist example model:
import imageio
out = imageio.volread("sample_output_0.tif")
print(out.shape)
Out[3]: (512, 512, 33)

Hi @constantinpape
I answered you by email as well. But we can discuss it here. The code I normally use with tiff files is the following one:
tifffile.imsave(file_name),
                    np.expand_dims(video, axis=[1, 2, -1]), # addapt the dimensions to tifffile ordering TZCYXS
                    resolution=(1 / pixel_size, 1 / pixel_size),
                    imagej=True,
                    metadata={'spacing': 1, 'unit': 'um'})

Storing the tiff like that shouldn't give you problems when recovering it from python. Could you test it?
Also, can use the very last version of the bioimageio.core in the notebook?

Thanks for the code snippet @esgomezm. I am working on using it now, see #212.

Also, can use the very last version of the bioimageio.core in the notebook?

Sorry, I don't quite understand what you mean, could you please clarify?

@esgomezm I think I have fixed the issues now and I have made a new release already that includes the changes: v0.4.10. If you switch to it in the zero cost notebooks the problems should be fixed.

Hi!
I'm using v0.4.11 and the tiff export gives the following error with 3D data. Looking at the tifffile library, seems that the type needs to be specified in tifffile.write but I'm not 100% sure. Any idea?
[/usr/local/lib/python3.7/dist-packages/bioimageio/core/build_spec/build_model.py](https://localhost:8080/#) in write_im(path, im, axes, pixel_size)
    441         if np.dtype(im.dtype) == np.dtype("float64"):
    442             im = im.astype("float32")
--> 443         tifffile.imsave(path, im, imagej=True, resolution=resolution)
    444
    445     sample_in_paths = []

[/usr/local/lib/python3.7/dist-packages/tifffile/tifffile.py](https://localhost:8080/#) in imwrite(file, data, shape, dtype, **kwargs)
    964
    965     with TiffWriter(file, **tifargs) as tif:
--> 966         result = tif.write(data, shape, dtype, **kwargs)
    967     return result
    968

[/usr/local/lib/python3.7/dist-packages/tifffile/tifffile.py](https://localhost:8080/#) in write(self, data, shape, dtype, photometric, planarconfig, extrasamples, volumetric, tile, contiguous, truncate, align, rowsperstrip, bitspersample, compression, predictor, subsampling, jpegtables, colormap, description, datetime, resolution, subfiletype, software, subifds, metadata, extratags, returnoffset, ijmetadata, compress)
   1768             if datadtypechar not in 'BHhf':
   1769                 raise ValueError(
-> 1770                     'the ImageJ format does not support data type '
   1771                     f'{datadtypechar!r}'
   1772                 )

ValueError: the ImageJ format does not support data type '?'

You can check the notebook here: https://github.com/esgomezm/ZeroCostDL4Mic/blob/master/Colab_notebooks/BioImage.io notebooks/U-Net_3D_ZeroCostDL4Mic_BioImageModelZoo_export.ipynb

ValueError: the ImageJ format does not support data type '?'

The "?" seems to come from https://github.com/blink1073/tifffile/blob/af9d70058b01f501b29cfe924a6463414c388480/tifffile/tifffile.py#L891
which means boolean data: https://numpy.org/doc/stable/reference/arrays.dtypes.html
seems unrelated to bioimageio.core: The input data should not have dtype boolean to be saved as "ImageJ Tiff"?? How do you deal with boolean arrays in ImageJ?

Thanks for looking into this @FynnBe. Indeed it looks like an issue with the data type.
@esgomezm please check that the numpy array passed to https://github.com/bioimage-io/core-bioimage-io-python/blob/main/bioimageio/core/build_spec/build_model.py#L588-L589 has a "normal" datatype (i.e. not bool or some string datatype).

Hi @carlosuc3m,
I am a bit puzzled by this, since I tried the tif export functionality locally and it worked fine for me (i.e. the tifs can be loaded correctly in Fiji). So I am not sure how to fix this and also don't really have time to look into it right now.
Maybe you could have a look at it? The function for saving the tifs is this one: https://github.com/bioimage-io/core-bioimage-io-python/blob/main/bioimageio/core/build_spec/build_model.py#L421-L450. If you manage to fix it I am happy to help out with updating the tifs in the models where they are wrong.

Okk, will do and will get back to this issue.

I just create a pull request ( https://github.com/bioimage-io/core-bioimage-io-python/pull/275 ) that should solve the issue. It was pretty straight forward to solve. The 2D image generation was also wrong but it had not created any problem because the c and b dimensions where the ones mixed and in the models all the images had only one channel and one batch.
I am also linking the documentation in the tifffile project that justifies the change: https://github.com/cgohlke/tifffile/blob/master/tifffile/tifffile.py#L1348-L1357

I just create a pull request ( #275 ) that should solve the issue. It was pretty straight forward to solve. The 2D image generation was also wrong but it had not created any problem because the c and b dimensions where the ones mixed and in the models all the images had only one channel and one batch.

Unfortunately it seems to not be that straight forward, since your changes now break the tests because some of the images cannot be written any more. Could you please have another look?

Thanks for fixing this @carlosuc3m. I made a new release (0.5.5) including your changes.


Add: RDC TV [BR]

Channel Name
RDC TV
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
BR
Subdivision (optional)
BR-RS
City (optional)
Porto Alegre
Broadcast Area
s/BR-RS
Languages
por
Categories (optional)
General
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://rdctv.com.br/
Logo
https://rdctv.com.br/wp-content/uploads/2018/05/logo-rdctv.png
Notes
https://596639ebdd89b.streamlock.net/datavideo01/datavideo01/chunklist.m3u8

Thank you for the stream: it will be included in the next release.


DataContractAttribute does not cause JSon object serialization for IEnumerable

According to Serialization Attributes documentation:

The DataContractAttribute can be used as substitute for JsonObjectAttribute.

This should cause the decorated class to be serialized as Json object.
Unfortunately when IEnumerable< T > is implemented, the class is still serialized as Json array, when DataContract is present. Using JsonObjectAttribute does properly cause it to be serialized as Json object.

Thanks for reporting this. Fixed https://github.com/JamesNK/Newtonsoft.Json/commit/e9e2d006a50d6b54f14c28dff856ff2b105ddb9e

Hi
I'm going to revert this in 11.0.2 and improve the documentation. People who have placed DataContractAttribute on collection types are having there apps broken, and while consistency is nice, I feel like this is such a minor thing that it is not worth breaking existing users.

Clarified docs https://github.com/JamesNK/Newtonsoft.Json/commit/a444322988b6e40bf2a3ad6089da2566ffcea5a4


Very Unstable downloads that results in bad files

Steps to reproduce
For the first mentioned issue at actual behavior:

Start the download of one or more episodes
Pause the downloader

For the second:

Add two or more episodes to the queue
Remove from the queue an episode that isn't being downloaded

For the third one:

Limit your internet connection or contract a bad isp
Start a download. In a speed of 30kb/s downloads crashes randomly

For the fourth:

Start some downloads
Power off the screen of your cellphone or use another app. Downloads crashes at any moment while this happens.

Expected behavior
Downloads should go fine every moment.
Actual behavior
The following conditions results in unstable downloads that crashes at any moment:

Pausing a Download
Removing from the queue an episode that isn't being downloaded in the present
Slow internet (from 30kb/s to 500kb/s)
Putting the app in the background

This behavior may sometimes result in episodes that aren't fully downloaded and marked as complete, and converted from a .tmp file to a .mkv or .mp4 video file. Or in a few cases where the downloader creates duplicated video files, and one of them is not fully downloaded while the other one is fully downloaded, manual renaming is needed if this happens.
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 14
Device
Redmi Note 12 4G
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extension's repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Same here. Moto g 2020. Needs better error handling on files, causes my sd card errors only fixable with fsck


Implement volume control with switches

BCP volume control is gone. Implement it properly using switches.

Implemented in service mode


Installed this and now I can no longer use Wagtail admin

Seems like the devs at Wagtail are not using fastdev!

While I'll check with them to fix the undefined tag, I'm sure that's not the only exception.
It would be great if we could exclude specific apps (or directly all external code), with a configuration or something.
TLDR: I think that fastdev should not run outside of the project's boundaries.
Longer explanation: while I totally agree on the fact that undefined variables must explode as they always do everywhere else, I feel that the Django templating language is meant to be more permissive. For me, that simply means that we could find ourselves adding apps to our projects which are written by people not sharing our same views on undefined variables, and are not willing to "fix" what is not a problem to them.

Yea, maybe a simple whitelist that is regexes on template names will do. I'm open to a PR for this.

I have a similar issue with https://github.com/unfoldadmin/django-unfold in my case is Invalid blocks specified:.
Also if I put django_fastdev as last app I am getting that error for a block of that template of that package that I don't duplicated in my project.

After investigating a bit in my case is that the blocks doesn't exist as it is a package that has a logic to not print them if found them in various HTML files so the logic right now doens't work.
For fastdev is invalid but in reality is not declared or unused.


What is "Listener state: Not listening" in general

Hi,
I copy my own rdpwrap.ini by similar code:
net stop UmRdpService
net stop termservice
copy /b rdpwrap.ini "c:\Program Files\RDP Wrapper"
net start termservice
net start UmRdpService
It is ok, but sometimes result is "Listener state: Not listening". After restart PC everything is OK. Can I restrat some service or something similar to managed it without restart whole PC?
Thanks for help.

Try restarting remote desktop services

@SealedCrib
net stop termservice
net start termservice
does EXACTLY that, so if you cannot help then move on politely

It can be error of owner of file or file can be used by another process. Look at log

Closed as not actual


Wrong cursor position and terminal width (Linux, ZSH)

VSCode Version: 1.38.0
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.19.71-1-lts
ZSH: 5.7.1

Steps to Reproduce:

Install ZSH with Powerline

powerline-daemon -q
. /usr/lib/python3.7/site-packages/powerline/bindings/zsh/powerline.zsh

Open terminal

Does this issue occur when all extensions are disabled?: Yes

Please try repro in the upstream xterm.js project and report there if it happens.


Enhance DuckDB Data Connector documentation

[x] Connector description
[x] Configuration section
[x] Secrets section / Authentication section
[x] Examples section
[x] Parameters table
[x] File format support (if applicable)
[x] Add semicolons to SQL statements

Replaced by #587


Forward slashes unexpectedly emiting line breaks

So I was trying to typeset a URL just now:
\begin{center}
Via Christus Yayınları\break
\url{https://www.viachristus.com}\break
<EMAIL_ADDRESS>\end{center}

But much to my surprise it came out like this:

The goose chase took me to the URL package line 21 from a2325d8.
local breakpat = options.breakpat or "/"

Can I ask when one would want to break URL's on forward slashes?

These should be \goodbreaks - decent places to break the line - but for some reason they are being interpreted as mandatory breaks.

Here's a minimal test:
\begin[papersize=a4]{document}
Good\penalty[penalty=-500]break

\set[parameter=document.rskip,value=0 plus 10000pt]
Good\penalty[penalty=-500]break
\end{document}

And TeX does the same thing. That's annoying.

Color me surprised.‹/sarcasm›

Think I've got it. TeX's URL package uses positive, not negative, penalties. Testing now.


Add an ImageryLayer

ImageryLayer

Add the ImageryLayer
Add the layer to LayerTypes.razor created in #63. Alternatively, if these are too different, create a new samples page.

Good layer to use for sample : https://moraveclabsllc.maps.arcgis.com/home/item.html?id=a1ba14d09df14f42ad6ca3c4bcebf3b4

The dotnet renderers associated with this layer are in GeoBlazor.Pro.
Reference: https://github.com/dymaptic/GeoBlazor.Pro/issues/59
The sample and javascript methods are in this repo.


Feature/all values multiple filter

Closes: #25
Closes: #97

Codecov Report

Merging #98 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #98   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          228       237    +9
=========================================
+ Hits           228       237    +9

Impacted Files
Coverage Δ

django_property_filter/filters.py
100.00% <100.00%> (ø)

django_property_filter/filtersets.py
100.00% <100.00%> (ø)

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 7191cbe...6e08f18. Read the comment docs.


Fixes #94. Fix label wrapping issue in underlined textfield.

Add white-space no wrap for labels in underlined variant. Clean up states in Less.

Approved - nice clean-up, too


Add support for per-profile tab colors

Summary of the Pull Request

This PR adds support for per-profile tab colors, in accordance with #7134. This adds a single tabColor property, that when set, specifies the background color for profile's tab. This color can be overridden by the color picker, and clearing the color with the color picker will revert to this default color set for the tab.
References

Seriously go read #7134
Theming is covered in #3327 & #5772

PR Checklist

[x] Closes #1337
[x] I work here
[ ] Tests added/passed
[ ] Requires documentation to be updated

Detailed Description of the Pull Request / Additional comments

Seriously go read #7134

Validation Steps Performed
Played with setting this color, both on launch and via hot-reload

@DHowett and I discussed this and he's more okay with it now that we've considered the fact that the color needs to be associated with each individual control, not just per-tab. It's more like and extension of titlebar state:

titlebar text
titlebar color
titlebar icon

etc.

@zadjii-msft could you please clarify how we can actually add this to our json settings per-profile now?
I simply tried adding tabColor to a profile, but that didn't do anything. The documentation isn't very clear in how to configure this either, and the UI doesn't have an option either.
Other issues I found all refer to this issue regarding per-profile tab colors, but haven't been able to find the answer.


[beta] Add strings for Call Composite People button

What
Add people button labels specific to call composite.
Why
People button in Call composite was using CallWithChat strings.
How Tested
Locally on MacOS chrome browser with Calling sample.
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

The new strings are failing on the localization hermetic tests on beta flavor.
@prprabhu-ms, is there something specific I need to do when adding new strings that have yet to be localized in beta flavor?


Milestone 1a

https://github.com/opendata-mvcr/sgov/issues/106

updated layout to support attachments
updated SSP exporting to support attachments
removed old diagrams
cleaning incorrect rdfs:subClassOf ""^^xsd:integer

Closing in favour of another PR to avoid CircleCI failure badges.


Feature Request - Ability to disable inbound peering

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
Is your feature request related to an issue?

Describe the solution you'd like
I would like the inbound peering to be optional. I'm using the CAF Enterprise Scale module to setup the whole ES framework. (https://github.com/Azure/terraform-azurerm-lz-vending/blob/813c30f136e7b21979f0c15a1c1913c7e82f1acb/docs/wiki/Example-4-Integration-with-ALZ-module.md#locals)
I'm using the spoke_virtual_network_resource_ids property there to let the ES module make the initial peer towards the spoke. It will also setup the Private DNS zones. I would like to use the lz-vending module to make the second peer towards the hub. That currently doesn't work as I'm getting an ERROR CODE: AnotherPeeringAlreadyReferencesRemoteVnet error on:
│   on .terraform/modules/corp_lz/modules/virtualnetwork/main.tf line 104, in resource "azapi_resource" "peering_hub_inbound":
│  104: resource "azapi_resource" "peering_hub_inbound" {

This approach is also a best practice from a least privilege perspective, as I can now let one service principal handle the ES deployment and the other the landing zone deployments.
Thanks!

Additional context
CC: @krowlandson

Seems a fair ask @DevSecNinja ... Will discuss with @matt-FFFFFF to see what we can do to help 👍🏻

Hi @DevSecNinja
I'm happy to investigate this change.
Please can you share how you are establishing this in config? The reason we create both hub peerings with the LZ vending module is that the subscription ID (and therefore resource ID of vnet) is not known until after the sub alias resource has been created. Therefore it made sense to us to leave the peering configuration to the lz-vending module. Can you provide a sample of how you have this wired up? Have you used the outputs of the lz-vending module to populate the list of spoke_virtual_network_resource_ids? If so how have you ensured the vnets are peered to the correct hub?
Furthermore, in terms of privileges. I have seen a custom role used that is only able to manage peerings for the hub network. We document the required permissions here: https://learn.microsoft.com/azure/virtual-network/virtual-network-manage-peering?tabs=peering-portal#permissions

Thanks @matt-FFFFFF! Sure, I've added the VNET IDs statically to spoke_virtual_network_resource_ids in the CAF module with a comment to 'prettify' that. (It's a small test environment) I have my subscription IDs and names in a separate JSON file, so I should be able to use that as input. But it's not as nice.
Can the vending module also provision the Private DNS resources that are provisioned when using spoke_virtual_network_resource_ids in the CAF module? If yes, that would convince me to move the peering over to the vending module.
Thanks!

Hey @DevSecNinja - we are considering this: see #132

Hey @DevSecNinja - we are considering this: see #132

Thanks for creating that! But doesn't that introduce the same 'challenges' as what we have now with this inbound/outbound peering situation? As in, we need to keep track of something (either created VNETs or private DNS zones) that comes from the other module? In this case, the Private DNS zones that are created in the ES CAF module and VNET linked to the spoke VNET from the vending module.
Not sure which approach I like more. What do you think?

Good point!
The CAF ES module provides outputs for all created resources, including the hub network resource ID in order to create the peering in the first place 😄
In terms of order of operations, we see that the platform would be created first. Therefore the vnet and pDNS zone resource IDs are already known.
In terms of the subs that are created by LZ vending, out assumption is that these subscriptions should be created afterwards.
If the modules exist in the same state, or if the LZ vending module can access the state of the ES CAF module, then the resource IDs for the hub resources can be mapped into the lz vending module.
We document how to do this here:


Compared with the indicators

Hi, I would like to ask why your paper is not related to the Enhancing Pseudo Label Quality for Semi-Supervised Domain-Generalized in 2022 Compared with the indicators of Medical Image Segmentation, is it because the backbone is different?

Hi, yes, the paper you mentioned used a pre-trained ResNet as the backbone.
See in the related work:
Following \cite{liu2021semi}, Yao et al.\ \cite{yao2022enhancing} adopted a pre-trained ResNet \cite{he2016deep} as a backbone feature extractor and augmented the source data by mixing MRI images in the Fourier domain and employed pseudo-labelling to leverage the unlabelled data.
Different backbones affect the DG performance.


Flutter packages general.shard test error

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Install Flutter version 3.16.0-2.0.pre.22
Clone the Flutter packages repository: git clone https://github.com/flutter/packages
Navigate to the packages/flutter_tools directory: cd packages/flutter_tools
Run the command flutter pub get
Run the command: flutter test test/general.shard >> general.shard_logs.txt
Expected results
Running all tests should succeed.
Actual results
The test fails
Logs:
Exception:
  package:flutter_tools/src/base/common.dart 10:3       throwToolExit
  package:flutter_tools/src/dart/package_map.dart 50:5  loadPackageConfigWithLogging
  ===== asynchronous gap ===========================
  dart:async                                            _CustomZone.registerBinaryCallback
  package:flutter_tools/src/base/context.dart 150:19    AppContext.run.<fn>
  dart:async                                            runZoned
  package:flutter_tools/src/base/context.dart 149:12    AppContext.run
  test/src/context.dart 127:30                          testUsingContext.<fn>.<fn>.<fn>.<fn>
  dart:async                                            runZonedGuarded
  test/src/context.dart 125:18                          testUsingContext.<fn>.<fn>.<fn>
  package:flutter_tools/src/base/context.dart 150:29    AppContext.run.<fn>
  dart:async                                            runZoned
  package:flutter_tools/src/base/context.dart 149:12    AppContext.run
  test/src/context.dart 101:22                          testUsingContext.<fn>.<fn>
  package:flutter_tools/src/context_runner.dart 83:18   runInContext.runnerWrapper
  ===== asynchronous gap ===========================
  dart:async                                            _CustomZone.registerUnaryCallback
  package:flutter_tools/src/context_runner.dart 82:20   runInContext.runnerWrapper
  package:flutter_tools/src/base/context.dart 150:29    AppContext.run.<fn>
  dart:async                                            runZoned
  package:flutter_tools/src/base/context.dart 149:12    AppContext.run
  package:flutter_tools/src/context_runner.dart 86:18   runInContext
  test/src/context.dart 100:11                          testUsingContext.<fn>
  test/src/common.dart 177:18                           test.<fn>
``

### Code sample

<details><summary>Code sample</summary>

```dart
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
general.shard_logs.txt
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.16.0-2.0.pre.22, on macOS 13.5.2 22G91 darwin-arm64, locale en-UY)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2023.2.2)
[✓] VS Code (version 1.82.3)

Clone the Flutter packages repository: git clone https://github.com/flutter/packages

Navigate to the packages/flutter_tools directory: cd packages/flutter_tools

package flutter_tools is part of the Flutter SDK (https://github.com/flutter/flutter/tree/master/packages/flutter_tools) not the flutter/packages repo: https://github.com/flutter/packages/tree/main/packages/flutter_tools

I'm guessing that this was open mistakenly, so I'm going to close this. If I am mistaken however, feel free to re-open, with some more context. Thanks!


IC/TS option "trust_file_extensions"

The default is 0, old behavior. If you set to nonzero, you are
promising the ImageCache that it will always be able to identify a
texture file's format based on the filename extension (e.g. ".exr"
always means it's an openexr file, ".tif" or "tx" for TIFF files, and
you will NEVER call a file ".tx" if it's really openexr, or if you do,
you are ok with it being unable to open it). When you enable it with
that promise, it can eliminate a few redundant file opens and header
reads, by not needing to verify file format types at certain stages of
processing.
I'm not sure I would recommend enabling this in general. But if you
are operating in a closed environment where you are sure that file
extensions will match their types (such as a studio with rigid naming
conventions, where all possible textures have been converted with
maketx), this can eliminate some unnecessary network traffic and file
server workload.

LGTM!


439 implement new summary card component

Trello
The changes here:

remove the existing component
remove the existing stylesheet
remove the reference to the existing stylesheet from application.scss
add the component from the Publishing Components gem
add the Summary card styles from the Publishing Components gem

Additionally

The page summary section at the top and the links below have been separated into <section> elements. This is a semantic improvement though here it also serves to avoid the double border that is rendering under the top section in the current implementation, caused by the way the component is designed to display when there are multiple instances of it in a section.
The way the colours used to represent different states (Draft, Published etc.) are defined has been updated to use the app/assets/stylesheets/tags.scss file, which was previously created to map specific colours onto states. This ensures there is a "single source of truth" for the correspondence between state and colour.

Before
After

LGTM.


navigator.navigate is handled by parent navigator instead of child navigator after BackHandler.exitApp()

I have a nested navigator structure:
const Tab1Navigator = StackNavigator({
  Tab1: { screen: routes.Tab1 },
  OtherScreen: { screen: routes.OtherScreen }
});

const Tab2Navigator = StackNavigator({
  Tab2: { screen: routes.Tab2 }
});

const AuthenticatedNavigator = TabNavigator({
  Tab1: { screen: Tab1Navigator },
  Tab2: { screen: Tab2Navigator }
});

const UnauthenticatedNavigator = StackNavigator({
  Login: { screen: routes.Login },
  Register: { screen: routes.Register }
});

const AppNavigator = StackNavigator({
  Unauthenticated: { screen: UnauthenticatedNavigator },
  Authenticated: { screen: AuthenticatedNavigator }
});

If I call this.props.navigation.navigate('Tab1') normally it would dispatch Navigation/NAVIGATE action with routeName: Tab1, but if I exit the app with BackHandler.exitApp(), then when I call this.props.navigation.navigate('Tab1') it dispatches Navigation/NAVIGATE action with routeName: Authenticated instead of the expected routeName: Tab1 and it results in a duplicated Authenticated route in the root stack navigator.
I have tried changing the keys for the tabs, so that they don't match the actual screen keys, but it doesn't solve this issue.
Environment

software
version

react-navigation
^1.0.0-beta.11

react-native
0.46.4

node
v6.5.0

npm or yarn
3.10.7

A running demo would be very helpful in debugging this issue - thanks!

Pinging OP @nicemanis since this issue has not been active for a while, and it's related to an old version of the lib.
Please let me know if you want this to remain open; if I get no answer in the next 7 days I will close it.

Hi there @nicemanis ,
In an effort to cleanup this project and prioritize a bit, since this issue had no follow up since my last comment I'm going to close it.
If you are still having the issue with the latest version (especially if it's a bug report) please check the current open issues, and if you can't find a duplicate, open a new one that uses the new Issue Template to provide some more details to help us solve it.


A question for Mike Pick

.affiliates .ala doesn't have the laurel svg referenced as a background-image the same way as the other affiliate logos so is currently displaying an empty box.
Not sure if this was an intentional decision so you could re-use the same block and just hide the logo of the current site but thought it was worth mentioning anyway.
ala

It's been so long that I honestly don't know why this is the case or who made this so. We should just figure out whether we want to have the logo there or not...

We don’t want a visible logo there.

(Thanks!)


Create and save sample data on new file

Fixes #66

How do I test for this?

Good question, there's currently no tests for MainApp. (Any such test must be an end-to-end test and requires the GUI to be visible I think.)
We will see.


Win32 Exception

I did everything like indicated in MS site, I'm on 0.10.3, Unity 5.3.0 and your latest package. I'm also using Unity's debugger package, I get the exception when I open a file or the C# project.

Anything on that**?**

I have same problem here. Using Unity and VS Code on Ubuntu 15.04
This is stack trace:
Win32Exception: ApplicationName='code', CommandLine='"/mnt/b4bfaaa5-3fb3-44fe-b055-ea09420a39ba/Projects/unity-test/Roll-a-Ball" -r', CurrentDirectory=''
System.Diagnostics.Process.Start_noshell (System.Diagnostics.ProcessStartInfo startInfo, System.Diagnostics.Process process)
System.Diagnostics.Process.Start_common (System.Diagnostics.ProcessStartInfo startInfo, System.Diagnostics.Process process)
System.Diagnostics.Process.Start ()
(wrapper remoting-invoke-with-check) System.Diagnostics.Process:Start ()
dotBunny.Unity.VSCode.CallVSCode (System.String args) (at Assets/Plugins/Editor/VSCode.cs:309)
dotBunny.Unity.VSCode.MenuOpenProject () (at Assets/Plugins/Editor/VSCode.cs:504)

Ok I from stack trace I found that I missing command code in my system.
I figured it out with this command
,,,
sudo ln -s /path/to/VSCode/Code /usr/local/bin/code
,,,

Hey @tommy-gun can you please elaborate on that? I'm having the exact problem. But I'm on Windows. Is what you did adding path to the VSCode to the system path(Environment variable)?

Hi @chandujr it is similar but not same for one important reason. My OS does not recognized command 'code' so, I make a symbolic link (with correct name) to it real location.
Until this part it is same as add to PATH variable. But executable in VSCode dir is Code.exe (i supose, because in my case it is not .exe of course). So you must somehow set alias for this executable to desired command name 'code' with small letters.

Thank you @tommy-gun I'll try that out.

Hey, any improvement on this? I am als orunning the WIN version and got hte same erro as the original poster

I'm getting this issue, and I'm not sure where I can give it the full path to be sure?
Unity shows the option for external editor as:
External Script Editor: code.cmd
External Script Editor Args: -r -g "$(File):$(Line)"
It doesn't appear as "VS Code".

Hey, guys. I came across with the same problem and I managed to figure it out.
Luckily, our friends from dotBunny put a text field with a path to code.cmd inside Edit/Preferences/VSCode.
By default, it is set as an inexistent folder inside AppData/Local.
What I did was to set that path (line 52 in VSCode.cs) to:
var newPath = Path.GetPathRoot(System.Environment.SystemDirectory) + Path.DirectorySeparatorChar + "PROGRA~2" + Path.DirectorySeparatorChar + "MIFA7F~1" + Path.DirectorySeparatorChar + "bin" + Path.DirectorySeparatorChar + "code.cmd";
It is worth noticing that "PROGRA~2" is a denotation for Program Files (x86) and "MIFA7F~1" a denotation for Microsoft VS Code. You can get those names by going to C: in your cmd console and putting "dir /x".
Good luck, buddies.

var newPath = Path.GetPathRoot(System.Environment.SystemDirectory) + Path.DirectorySeparatorChar + "PROGRA~2" + Path.DirectorySeparatorChar + "MIFA7F~1" + Path.DirectorySeparatorChar + "bin" + Path.DirectorySeparatorChar + "code.cmd";

It is worth noticing that "PROGRA~2" is a denotation for Program Files (x86) and "MIFA7F~1" a denotation for Microsoft VS Code. You can get those names by going to C: in your cmd console and putting "dir /x".<
@Prisoner19 Thank you for your help! Your solution worked perfectly after I looked at the "dir /x" names of the directories.
For me (Fresh install of windows 10) "MIFA7F~1" is actually "MICROS~1".
It may be different for each computer!

Well, now that Code it's installed in Program Files (x86), I think VSCode should do this by default.

It should now :)

Have you manually set the path in the options by chance? That seems to be the override for people when its not in a standard place?

How do you set the path in options?  I don't see anything in the Unity Preferences.

Ok so I guess the Force Update was not working as well.  I just copied and pasted the latest of of github's raw into the VSCode.cs and it works.  Thanks for writing this, because I hate using MonoDevelop!

Np :)


MACE has crash on some devices

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
MacOS to compilation
NDK version(e.g., 15c):
r17b
GCC version(if compiling for host, e.g., 5.4.0):
4.9.0
MACE version (Use the command: git describe --long --tags):
v0.9.0-63-g70a41900
Python version(2.7):
Bazel version (e.g., 0.13.0):
0.15.2-homebrew

Model deploy file (*.yml)
......

Describe the problem
A clear and concise description of what the bug is
crash on some devices.
To Reproduce
Steps to reproduce the problem:
with the examples of android directory on MIUI 10 above.
Error information / logs
Please include the full log and/or traceback here.

Synchonize our threads can work it out.


Date picker and time picker not working properly (https://material-ui-next.com/demos/pickers/)

Date picker and time picker not working properly.  On desktop the calendar pop up won't show at all, work only in mobile. on Firefox, not show anything.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

https://material-ui-next.com/demos/pickers/

Context

Your Environment

Tech
Version

Material-UI
1.0 beta.18

React

browser

etc

Right, it's a limitation of the native input pickers. We gonna need a better story. For this. We encourage third party libraries for now.

Duplicate of #9081


ERROR 1500

Everytime i run the bot it attempts to purchase a item but just gives "[LOG:] Bought 5ad7217186f7746744498875 [ Key_cash_machine_OLI ] at 45000 / 60000
Waited 0.44726455211639404 Seconds before purchase
[ERROR:] 1500"

This error equals when the shitty developed BSG server, can't respond in time due to heavy traffic. I've updated the source patching this error, delete and re-download.


[FE]support custom webfont

User story
Users currently only have a choice of fonts from Re:Earth, and would like to use their own webfont with Infobox, Label, etc. We would like to use unique webfonts for Infobox, Label, etc. This will give us a wider range of design option
Requirements

Can input webfont URL or JS code
The fonts which are added by users can be chosen from the fonts pull-down list
Web font works on published page as well

[ ] write document

[ ] Front-end
[ ] Back-end

https://github.com/typekit/webfontloader is recommended 👍  (@rot 1024)

👆 supports google, typekit, monotype, fontdeck

Since we don't have a plan to develop this soon, I'll close this.


CI 3.X Router error on _set_default_controller

The _set_default_controller method requires the default controller to be a maximum two segment rout (i.e. the controller cannot be in a subdir of the 'controllers' path). Resusing the _set_request inside _set_default_controller corrects the problem

This is by design and explained in the manual.


Update mobile-broadband-device-firmware-update.md

Update guidance to use driver store location instead of well-known location

Thanks @zlockard!


How to use Slik in a .NET 6 Web Api project?

I'm trying to create a REST API project using Slik.Cache, code example:
            WebApplicationBuilder builder = WebApplication.CreateBuilder();
            builder.Host.UseSlik(new SlikOptions
            {
                Host = new IPEndPoint(IPAddress.Loopback, 3092),
                Members = new[] { "localhost:3092", "localhost:3093", "localhost:3094" }
            });

            builder.Services.AddControllers();
            // Learn more about configuring Swagger/OpenAPI at https://aka.ms/aspnetcore/swashbuckle
            builder.Services.AddEndpointsApiExplorer();
            builder.Services.AddSwaggerGen();

            var app = builder.Build();

            // Configure the HTTP request pipeline.
            if (app.Environment.IsDevelopment())
            {
                app.UseSwagger();
                app.UseSwaggerUI();
            }

            app.UseAuthorization();
            app.MapControllers();

            app.Run();

But I get exception `System.NotSupportedException: 'ConfigureWebHost() is not supported by WebApplicationBuilder.Host. Use the WebApplication returned by WebApplicationBuilder.Build() instead.'.
Do I need to modify something to make it work?

@harrison314 To support WebApplication properly, I need to rewrite the initialization (UseSlik extension method). As a workaround you can continue to use Generic Host in .NET 6. Please consult this article.


Translate nav into ja

Part of #220
Navigation bar translation.

Original

nav

Diff

https://github.com/microsoft/TypeScript-Website/commit/88539cfbebf444d4ee16360791db5cddd1bb2844

I'm going to intentionally close and re-open this PR, to see if https://github.com/orta/code-owner-self-merge works

Looks like it only affects new PRs 👍🏻


runtime synchronization error

I recorded an ouster os1-64 bag with external IMU, and everything works fine for Lego_LOAM, but when I turn to LIO-SAM, nothing showed in rviz, thus I checked the code and found the synchronization error below.
The first figure is from myself recored bag, which indicates the time is the internal ouster time, while the second is from your dataset, where both timestamp is ros time.

There is about 50 years time difference between your IMU and Ouster data. Have you tried to sync your Ouster lidar time with the current time?

I recorded an ouster os1-64 bag with external IMU, and everything works fine for Lego_LOAM, but when I turn to LIO-SAM, nothing showed in rviz, thus I checked the code and found the synchronization error below.
The first figure is from myself recored bag, which indicates the time is the internal ouster time, while the second is from your dataset, where both timestamp is ros time.

I have the same problem and handled.But I could not download the ouster dataset because the wall.Are you from China too?

I recorded an ouster os1-64 bag with external IMU, and everything works fine for Lego_LOAM, but when I turn to LIO-SAM, nothing showed in rviz, thus I checked the code and found the synchronization error below.
The first figure is from myself recored bag, which indicates the time is the internal ouster time, while the second is from your dataset, where both timestamp is ros time.

I have the same problem and handled.But I could not download the ouster dataset because the wall.Are you from China too?

留个邮箱我发给你老铁

There is about 50 years time difference between your IMU and Ouster data. Have you tried to sync your Ouster lidar time with the current time?

We

I recorded an ouster os1-64 bag with external IMU, and everything works fine for Lego_LOAM, but when I turn to LIO-SAM, nothing showed in rviz, thus I checked the code and found the synchronization error below.
The first figure is from myself recored bag, which indicates the time is the internal ouster time, while the second is from your dataset, where both timestamp is ros time.

I have the same problem and handled.But I could not download the ouster dataset because the wall.Are you from China too?

哦对，你怎么弄啊，是录bag的时候搞，还是用sim time？

I recorded an ouster os1-64 bag with external IMU, and everything works fine for Lego_LOAM, but when I turn to LIO-SAM, nothing showed in rviz, thus I checked the code and found the synchronization error below.
The first figure is from myself recored bag, which indicates the time is the internal ouster time, while the second is from your dataset, where both timestamp is ros time.

I have the same problem and handled.But I could not download the ouster dataset because the wall.Are you from China too?

哦对，你这个问题是怎么解决的哈~也是全弄sim time还是录bag时候搞？

I recorded an ouster os1-64 bag with external IMU, and everything works fine for Lego_LOAM, but when I turn to LIO-SAM, nothing showed in rviz, thus I checked the code and found the synchronization error below.
The first figure is from myself recored bag, which indicates the time is the internal ouster time, while the second is from your dataset, where both timestamp is ros time.

I have the same problem and handled.But I could not download the ouster dataset because the wall.Are you from China too?

留个邮箱我发给你老铁

<EMAIL_ADDRESS>邮箱留个微信吧 交流一下