Training on custom dataset with only single class.

Hello, I am testing your scripts by changing the defaults.yaml.  My problem is with gt_det.
gt det is initialized as:
gt_det = np.zeros((self.max_detections, num_classes), dtype=np.float32)
Which has shape of (150, 1) because I only have single class. But if you look further down, gt_det is broadcasted to 6 different values, and I was not sure how to change below line exactly.
 gt_det[k] = ([ct[0] - w / 2, ct[1] - h / 2,                               ct[0] + w / 2, ct[1] + h / 2, 1, cls_id])
Are there anything else I need to consider when I am dealing with 1 class instead of 6 classes?

Hi, the line consists of an error which I never found since I had only 6 classes that fit, by accident, exactly the shape of the gt_det. gt_det consists of the gt boxes and this correspond to 6 values (x1, y1,x2,y2,score,class_id). I've pushed a fix for this.

thank you, your latest commit fixes all those issues. cheers.

sorry, one more question. This may be a related issue to your previous commit i think, as similar issue happens during validation.
If you look at evaluation/coco.py starting line 283,
 for gt_bb, gt_lb, gt_ar, gt_crw in zip(
                    gt_bbox, gt_label, gt_area, gt_crowded):
                gt_counter += 1
                gt_args.append(
                    (gt_bb,
                     gt_lb,
                     None,
                     image_id,
                     gt_counter,
                     gt_ar,
                     gt_crw,
                     image_shape,
                     self.use_rotated_boxes))

                self.existent_labels[gt_lb] = True

self.existent_labels causes the trouble, as it breaks validation saying it's not hashable. I am assuming this is wanting some kind of single int or string key, not a numpy array of shape (1,6). What needs to go in here exactly?
If I print out, I get [282 392 287 400   1   0], and I am assuming here that 0 at the end here is the class ID.

I've observed something similar in the past, the evaluation produces errors if your batch leftover a single item. Therefore, can you check that the following statement len(dataset) mod batch_size != 1 is true for your setup? I know about the bug but I've not the time to fix it and the workaround works well for me :).

I think you are right, because the validation loop crashes on the final batch (17th batch). Up to 16th, the validation proceeds perfectly. I checked the train loop (let me know if this not where i need to look) like the following.
  train_loader, val_loader, test_loader = load_datasets(
        cfg, down_ratio=backend.down_ratio, rotated_boxes=backend.rotated_boxes)
    tensorboard_logger = TensorboardLogger(cfg, val_loader.dataset.classes)

    # check the loader length here
    loaders = {}
    loaders['train'] = train_loader
    loaders['val'] = val_loader
    loaders['test'] = test_loader

    for k, loader in loaders.items():
        print('{} loader, batch size {}, results: {}'.format(k, cfg.batch_size, len(loader)% cfg.batch_size))

And as you suspected, you get:
train loader, batch size 16, results: 13
val loader, batch size 16, results: 1
test loader, batch size 16, results: 1

Any idea how you may actually workaround this? simply checking the batch size wouldn't actually fix the problem, so I am assuming there is something I can do to prevent this from happening.


[Grid] Unexpected spacing behavior

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
In the Material UI documentation on the Grid component examples, it works fine inside the main container when using spacing

Expected Behavior 🤔
What is expected is that if I copy and paste the same example code to be able to test it will behave in the same way, but this does not work Link to codesandbox
It ends up generating a horizontal scroll.
Some solutions are given, but I don't see these being used in the example.

We are using a Container component as parent

Steps to Reproduce 🕹

Steps:

Copy NestedGrid code example
Paste to codesandbox
Run app

Context 🔦
We were building a Layout for a page and we were in doubt regarding the spacing of the Grid component since we began to have several problems with horizontal scrolling.
Our implementation is
container: {
  paddingTop: 8,
  paddingBottom: 8,
}

<Container className={classes.container}>
  <Grid container spacing={2}>
    <Grid item xs>
      ...
    </Grid>
  </Grid>
</Container>

Your Environment 🌎
Material UI v4.11.2
React v17.0.1

`npx @material-ui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @material-ui/envinfo` goes here.

I think it works as expected codeSandBox
Because spacing is calculated for each item in the respected container.

I think it works as expected codeSandBox
Because spacing is calculated for each item in the respected container.

I think it works as expected codeSandBox
Because spacing is calculated for each item in the respected container.

Or your example also works as expected.

But if you enter the link of the sanbox that leaves, you will see that it does not work as expected in the example.

I think it works as expected codeSandBox
Because spacing is calculated for each item in the respected container.

Or your example also works as expected.

But if you enter the link of the sanbox that leaves, you will see that it does not work as expected in the example.

@povilass But if you enter the link of the sanbox that leaves, you will see that it does not work as expected in the example.

@povilass But if you enter the link of the sanbox that leaves, you will see that it does not work as expected in the example.

@vicasas Do you have more details on how it's wrong?

@vicasas Do you have more details on how it's wrong?

@oliviertassinari Actually, I don't know if it is an error, but I don't understand why if I copy an example from Grid it doesn't work as in the documentation as it generates horizontal scrolling as shown in the codesanbox link.
Given this, I wonder if I am using Grid with correct spacing or not, since in my design it breaks generating horizontal scroll, so I should use any of the solutions indicated in the same documentation,

@oliviertassinari Actually, I don't know if it is an error, but I don't understand why if I copy an example from Grid it doesn't work as in the documentation as it generates horizontal scrolling as shown in the codesanbox link.
Given this, I wonder if I am using Grid with correct spacing or not, since in my design it breaks generating horizontal scroll, so I should use any of the solutions indicated in the same documentation,

I can't reproduce the horizontal scrollbar you are referring to. What browser are you using? Which codesandbox?

I can't reproduce the horizontal scrollbar you are referring to. What browser are you using? Which codesandbox?

Ok example showed problem bus still you need applied half spacing size to parent https://codesandbox.io/s/new-cache-lrynu like the documentation says.

Ok example showed problem bus still you need applied half spacing size to parent https://codesandbox.io/s/new-cache-lrynu like the documentation says.

As docs documentation example fix should be added to root div sandbox.
Before

After

As docs documentation example fix should be added to root div sandbox.
Before

After

I can't reproduce the horizontal scrollbar you are referring to. What browser are you using? Which codesandbox?

@oliviertassinari  I am using Chrome in its version 87.0.4280.88 (Official Build) (64 bits), Material UI v4.11.2 and React v17.0.1.
To reproduce the "error" what I did was copy and paste the sample code of Basic Grid in a codesanbox, which automatically generates the horizontal scroll.
Example https://codesandbox.io/s/frosty-https-j4fzo?file=/src/App.js

@povilass I think the same in the documentation examples should come spacing compensation for the example to work as expected. Or maybe add a more explicit example using Container as parent.

I can't reproduce the horizontal scrollbar you are referring to. What browser are you using? Which codesandbox?

@oliviertassinari  I am using Chrome in its version 87.0.4280.88 (Official Build) (64 bits), Material UI v4.11.2 and React v17.0.1.
To reproduce the "error" what I did was copy and paste the sample code of Basic Grid in a codesanbox, which automatically generates the horizontal scroll.
Example https://codesandbox.io/s/frosty-https-j4fzo?file=/src/App.js

@povilass I think the same in the documentation examples should come spacing compensation for the example to work as expected. Or maybe add a more explicit example using Container as parent.

@vicasas Ok great, thanks. This is exactly why we have documented the limitation of the approach as well as workarounds. At this point, it's probably still too early to use flex-gap as not supported by iOS/Safari. But maybe #9513 will be our salvation.
Actually, this diff seems to fix the scrolling issue, could you confirm?
diff --git a/packages/material-ui/src/Grid/Grid.js b/packages/material-ui/src/Grid/Grid.js
index fa64775cfc..259596b6e3 100644
--- a/packages/material-ui/src/Grid/Grid.js
+++ b/packages/material-ui/src/Grid/Grid.js
@@ -65,9 +65,9 @@ function generateGrid(globalStyles, theme, breakpoint) {
   }
 }

-function getOffset(val, div = 1) {
+function getOffset(val) {
   const parse = parseFloat(val);
-  return `${parse / div}${String(val).replace(String(parse), '') || 'px'}`;
+  return `${parse / 2}${String(val).replace(String(parse), '') || 'px'}`;
 }

 function generateGutter(theme, breakpoint) {
@@ -81,10 +81,12 @@ function generateGutter(theme, breakpoint) {
     }

     styles[`spacing-${breakpoint}-${spacing}`] = {
-      margin: `-${getOffset(themeSpacing, 2)}`,
+      marginTop: `-${getOffset(themeSpacing)}`,
+      marginLeft: `-${getOffset(themeSpacing)}`,
       width: `calc(100% + ${getOffset(themeSpacing)})`,
       '& > $item': {
-        padding: getOffset(themeSpacing, 2),
+        paddingTop: getOffset(themeSpacing),
+        paddingLeft: getOffset(themeSpacing),
       },
     };
   });

I can't catch regressions.

@vicasas Ok great, thanks. This is exactly why we have documented the limitation of the approach as well as workarounds. At this point, it's probably still too early to use flex-gap as not supported by iOS/Safari. But maybe #9513 will be our salvation.
Actually, this diff seems to fix the scrolling issue, could you confirm?
diff --git a/packages/material-ui/src/Grid/Grid.js b/packages/material-ui/src/Grid/Grid.js
index fa64775cfc..259596b6e3 100644
--- a/packages/material-ui/src/Grid/Grid.js
+++ b/packages/material-ui/src/Grid/Grid.js
@@ -65,9 +65,9 @@ function generateGrid(globalStyles, theme, breakpoint) {
   }
 }

-function getOffset(val, div = 1) {
+function getOffset(val) {
   const parse = parseFloat(val);
-  return `${parse / div}${String(val).replace(String(parse), '') || 'px'}`;
+  return `${parse / 2}${String(val).replace(String(parse), '') || 'px'}`;
 }

 function generateGutter(theme, breakpoint) {
@@ -81,10 +81,12 @@ function generateGutter(theme, breakpoint) {
     }

     styles[`spacing-${breakpoint}-${spacing}`] = {
-      margin: `-${getOffset(themeSpacing, 2)}`,
+      marginTop: `-${getOffset(themeSpacing)}`,
+      marginLeft: `-${getOffset(themeSpacing)}`,
       width: `calc(100% + ${getOffset(themeSpacing)})`,
       '& > $item': {
-        padding: getOffset(themeSpacing, 2),
+        paddingTop: getOffset(themeSpacing),
+        paddingLeft: getOffset(themeSpacing),
       },
     };
   });

I can't catch regressions.

@oliviertassinari Try that change, but the horizontal scroll still appears anyway. I was comparing how Bootstrap for Grid works, but didn't see more.
In the same way, I think it is fine, but the Grid examples of Material UI should be added compensation in the root as indicated in it.
For example Basic grid
root:  {
  padding: 8
}

  <Grid container spacing={3}>
        ...
  </Grid>

ór add this example
container: {
  paddingTop: 8,
  paddingBottom: 8,
}

<Container className={classes.container}>
  <Grid container spacing={2}>
    <Grid item xs>
      ...
    </Grid>
  </Grid>
</Container>

@oliviertassinari Try that change, but the horizontal scroll still appears anyway. I was comparing how Bootstrap for Grid works, but didn't see more.
In the same way, I think it is fine, but the Grid examples of Material UI should be added compensation in the root as indicated in it.
For example Basic grid
root:  {
  padding: 8
}

  <Grid container spacing={3}>
        ...
  </Grid>

ór add this example
container: {
  paddingTop: 8,
  paddingBottom: 8,
}

<Container className={classes.container}>
  <Grid container spacing={2}>
    <Grid item xs>
      ...
    </Grid>
  </Grid>
</Container>

But it works I applied changes to Grid component and called it Grid2 sandbox.
Example 1 with scroll

New grid example 1 no scroll

Important When you change property leave just one of them and press codesandbox refresh button.
I reproduced issues in Windows 10 Chrome Version 87.0.4280.88 (Official Build) (64-bit) and Microsoft Edge Version 87.0.664.66 (Official build) (64-bit).
Maybe it's working if you are using MAC+Chrome. MAC+Chrome not equal to WINDOWS+Chrome.

But it works I applied changes to Grid component and called it Grid2 sandbox.
Example 1 with scroll

New grid example 1 no scroll

Important When you change property leave just one of them and press codesandbox refresh button.
I reproduced issues in Windows 10 Chrome Version 87.0.4280.88 (Official Build) (64-bit) and Microsoft Edge Version 87.0.664.66 (Official build) (64-bit).
Maybe it's working if you are using MAC+Chrome. MAC+Chrome not equal to WINDOWS+Chrome.

@povilass Thanks for the codesandbox. I have tested in macOS Chome and Windows Chrome latest version, no scrollbar.

@povilass Thanks for the codesandbox. I have tested in macOS Chome and Windows Chrome latest version, no scrollbar.

@oliviertassinari Ok this is preview.

@oliviertassinari Ok this is preview.

@povilass Ok, so we can reproduce the problem as well as reproduce the solution is working. It sounds like we can move forward with a pull request.

@povilass Ok, so we can reproduce the problem as well as reproduce the solution is working. It sounds like we can move forward with a pull request.

@oliviertassinari @povilass  I think I got lost with the last example. Would the solution be to add root padding in the examples?

@oliviertassinari @povilass  I think I got lost with the last example. Would the solution be to add root padding in the examples?

@oliviertassinari I doubt, is it correct to change the spacing of the 4 axes and leave it to the left and up? In grid layouts, the columns (element) always have their padding on their 4 axes.
Personally, I would settle for adding in the Grid examples that overflow padding at the root.

@oliviertassinari I doubt, is it correct to change the spacing of the 4 axes and leave it to the left and up? In grid layouts, the columns (element) always have their padding on their 4 axes.
Personally, I would settle for adding in the Grid examples that overflow padding at the root.

Hey guys, I fixed that like 2 weeks ago. But I didn't get time to do the PR, may I send the PR and just tag this issue without giving a description?

Hey guys, I fixed that like 2 weeks ago. But I didn't get time to do the PR, may I send the PR and just tag this issue without giving a description?

@greguintow Can we see the solution? in a codesandbox

@greguintow Can we see the solution? in a codesandbox

@vicasas Okay, I'll prepare one

@vicasas Okay, I'll prepare one

@vicasas Here you go Demo. My solution works through a fullWidth prop

@vicasas Here you go Demo. My solution works through a fullWidth prop

@greguintow Why do we need to add an extra prop? What's wrong with the existing proposed solution?

@greguintow Why do we need to add an extra prop? What's wrong with the existing proposed solution?

@oliviertassinari I've tried to reproduce the same example I used on mine in the proposed solution and didn't work as it should.

@oliviertassinari I've tried to reproduce the same example I used on mine in the proposed solution and didn't work as it should.

@greguintow Do you have a reproduction?

@greguintow Do you have a reproduction?

@greguintow Do you have a reproduction?

I changed on the code sandbox if you want I can add to my demo to compare it. Answering your question about why I decided to go with a prop, it's because I didn't want to cause any breaking change.

@greguintow Do you have a reproduction?

I changed on the code sandbox if you want I can add to my demo to compare it. Answering your question about why I decided to go with a prop, it's because I didn't want to cause any breaking change.

What breaking change are you referring to? Unless https://github.com/mui-org/material-ui/issues/24272#issuecomment-754693543 has a flaw we aren't aware of, we should continue forward with this approach. Adding a new prop isn't OK.

What breaking change are you referring to? Unless https://github.com/mui-org/material-ui/issues/24272#issuecomment-754693543 has a flaw we aren't aware of, we should continue forward with this approach. Adding a new prop isn't OK.

@vicasas Aquí tienes Demo . Mi solución funciona a través de un accesorio de ancho completo

@greguintow  I keep seeing the same scroll problem

@vicasas Aquí tienes Demo . Mi solución funciona a través de un accesorio de ancho completo

@greguintow  I keep seeing the same scroll problem

@vicasas Wow, I really haven't noticed that, I was wondering why there was a blank space on my app haha, okay let me try to fix that.

@vicasas Wow, I really haven't noticed that, I was wondering why there was a blank space on my app haha, okay let me try to fix that.

@vicasas Could you try https://codesandbox.io/s/keen-feather-rdgty?

@vicasas Could you try https://codesandbox.io/s/keen-feather-rdgty?

@greguintow Do you have a reproduction?

This is I using my example in the proposed solution Demo

@greguintow Do you have a reproduction?

This is I using my example in the proposed solution Demo

@vicasas ¿Podrías probar https://codesandbox.io/s/keen-feather-rdgty ?

@oliviertassinari  That approach works, image attached.

But I wonder if item should only have left and top padding instead of having them on its 4 axes. The question comes to the fact that other Grids always have padding in the 4 axes🤔

@vicasas ¿Podrías probar https://codesandbox.io/s/keen-feather-rdgty ?

@oliviertassinari  That approach works, image attached.

But I wonder if item should only have left and top padding instead of having them on its 4 axes. The question comes to the fact that other Grids always have padding in the 4 axes🤔

But I wonder if item should only have left and top padding instead of having them on its 4 axes.

I don't think that it matter

But I wonder if item should only have left and top padding instead of having them on its 4 axes.

I don't think that it matter

This is I using my example in the proposed solution Demo

@greguintow It looks like this issue is already existing and different from the scrollbar.

This is I using my example in the proposed solution Demo

@greguintow It looks like this issue is already existing and different from the scrollbar.

@oliviertassinari Got it. So there is a serious bug with the proposed solution regarding the spacing.
Demo

@oliviertassinari Got it. So there is a serious bug with the proposed solution regarding the spacing.
Demo

@oliviertassinari Got it. So there is a serious bug with the proposed solution regarding the spacing.
Demo

Ignore what you guys saw before on the old section, it was using the latest instead of the next version.
You can see normally now:
Demo

@oliviertassinari Got it. So there is a serious bug with the proposed solution regarding the spacing.
Demo

Ignore what you guys saw before on the old section, it was using the latest instead of the next version.
You can see normally now:
Demo

@oliviertassinari I just realized that my solution actually fixes the scrollbar problem haha, if used without the fullWidth prop it will work

@oliviertassinari I just realized that my solution actually fixes the scrollbar problem haha, if used without the fullWidth prop it will work

@oliviertassinari Alright, after I lot of headaches, I could figure out the solution and not just fixing the scrollbar problem, but also the spacing problem.
Please check it out: Demo

@oliviertassinari Alright, after I lot of headaches, I could figure out the solution and not just fixing the scrollbar problem, but also the spacing problem.
Please check it out: Demo

@oliviertassinari Let me know if you want to me remove the fullWidth prop and make native support.

@oliviertassinari Let me know if you want to me remove the fullWidth prop and make native support.

@oliviertassinari On PR #24332 there is the same solution without the fullWidth prop that was able to reduce 4x times the ungzipped size of the Grid component.

@oliviertassinari On PR #24332 there is the same solution without the fullWidth prop that was able to reduce 4x times the ungzipped size of the Grid component.

Duplicate of #7466


[Wrangler] Undocumented configuration options

Existing documentation URL(s)

https://developers.cloudflare.com/workers/wrangler/configuration/

What changes are you suggesting?
Based on environment.ts and config.ts, there are several undocumented configuration options:

find_additional_modules
base_dir
version_metadata
pages_build_output_dir

Additional information
No response

This issue is pretty stale. Closing as won't do for now.


sc object not defined

sc object is not define in this page. Can you fix it or add below statement
import spark.implicits._
spark.sparkContext.parallelize(newContact).toDF
[Enter feedback here]

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

ID: c95be163-e576-6e54-5811-424221d56d39
Version Independent ID: f4217104-b75a-03bc-025b-7dff1a60b5e0
Content: Use Spark to read and write HBase data - Azure HDInsight
Content Source: articles/hdinsight/hdinsight-using-spark-query-hbase.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

We have assigned the issue to the content author . They will evaluate & update the document as appropriate

@abhaydiwan  Thanks for reaching out. Did you encounter a specific error when executing the steps of the tutorial? If so please provide it so that we can try to reproduce it. Also, please note that the import command import spark.sqlContext.implicits._ is used in the Define a catalog and query section.

@abhaydiwan We'll assume that you were able to resolve your issue and proceed to close this issue. If you need any further assistance, please feel free to reply to this thread again. Thank you.

#please-close


python310Packages.azure-mgmt-datafactory: 2.8.1 -> 2.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.azure-mgmt-datafactory is: "This is the Microsoft Azure Data Factory Management Client Library"
meta.homepage for python310Packages.azure-mgmt-datafactory is: "https://github.com/Azure/azure-sdk-for-python"
meta.changelog for python310Packages.azure-mgmt-datafactory is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.9.0 with grep in /nix/store/s6xc1d7awgsp7y8hpc2hmyks6dcqr10q-python3.10-azure-mgmt-datafactory-2.9.0
found 2.9.0 in filename of file in /nix/store/s6xc1d7awgsp7y8hpc2hmyks6dcqr10q-python3.10-azure-mgmt-datafactory-2.9.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.azure-mgmt-datafactory
python39Packages.azure-mgmt-datafactory

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s6xc1d7awgsp7y8hpc2hmyks6dcqr10q-python3.10-azure-mgmt-datafactory-2.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.azure-mgmt-datafactory https://github.com/r-ryantm/nixpkgs/archive/2b25fe058cf6ef4776ea81168ed7ce1e0f8f2318.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s6xc1d7awgsp7y8hpc2hmyks6dcqr10q-python3.10-azure-mgmt-datafactory-2.9.0
ls -la /nix/store/s6xc1d7awgsp7y8hpc2hmyks6dcqr10q-python3.10-azure-mgmt-datafactory-2.9.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.azure-mgmt-datafactory
python39Packages.azure-mgmt-datafactory

Maintainer pings
cc @mwilsoncoding for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.azure-mgmt-datafactory is: "This is the Microsoft Azure Data Factory Management Client Library"
meta.homepage for python310Packages.azure-mgmt-datafactory is: "https://github.com/Azure/azure-sdk-for-python"
meta.changelog for python310Packages.azure-mgmt-datafactory is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.10.0 with grep in /nix/store/242y3ip22xk6wnzpm8hjj3p6lkyi82zv-python3.10-azure-mgmt-datafactory-2.10.0
found 2.10.0 in filename of file in /nix/store/242y3ip22xk6wnzpm8hjj3p6lkyi82zv-python3.10-azure-mgmt-datafactory-2.10.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.azure-mgmt-datafactory
python39Packages.azure-mgmt-datafactory

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/242y3ip22xk6wnzpm8hjj3p6lkyi82zv-python3.10-azure-mgmt-datafactory-2.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.azure-mgmt-datafactory https://github.com/r-ryantm/nixpkgs/archive/bad89588755c9640f530deef5db1bb0b42f55015.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/242y3ip22xk6wnzpm8hjj3p6lkyi82zv-python3.10-azure-mgmt-datafactory-2.10.0
ls -la /nix/store/242y3ip22xk6wnzpm8hjj3p6lkyi82zv-python3.10-azure-mgmt-datafactory-2.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.azure-mgmt-datafactory
python39Packages.azure-mgmt-datafactory

Maintainer pings
cc @mwilsoncoding for testing.


[BUG]: macos arm64 self-hosted agent cannot update automatically

What happened?
Update from web cannot be processed (Settings→Agent Pools→[myPool]→macMiniM1→update Agent).
Update other platforms like Win, Linux, LinuxARM works fine, but not macos arm64.
Versions
macOS: 13.4
Installed DevOps Agent: 3.220.0
New DevOps Agent: 3.220.2
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
macOS 13
Version controll system
No response
Relevant log output
23-05-19 04:59:16Z INFO Agent] Refresh message received, kick-off selfupdate background process.
[2023-05-19 04:59:16Z ERR  VisualStudioServices] GET request to https://dev.azure.com/storeit/_apis/distributedtask/packages/agent/osx-arm64/3.220.2 failed. HTTP Status: NotFound, AFD Ref: Ref A: 6110B64F57854E38BF42792E381188A8 Ref B: PRG01EDGE0517 Ref C: 2023-05-19T04:59:17Z
[2023-05-19 04:59:17Z INFO Agent] Ignore agent update exception. Microsoft.TeamFoundation.DistributedTask.WebApi.PackageNotFoundException: A package with type agent, platform osx-arm64, version 3.220.2 was not found.
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponseAsync(HttpResponseMessage response, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpRequestMessage message, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync[T](HttpMethod method, IEnumerable`1 additionalHeaders, Guid locationId, Object routeValues, ApiResourceVersion version, HttpContent content, IEnumerable`1 queryParameters, Object userState, CancellationToken cancellationToken)
   at Microsoft.VisualStudio.Services.Agent.Listener.SelfUpdater.UpdateNeeded(String targetVersion, CancellationToken token) in /Users/runner/work/1/s/src/Agent.Listener/SelfUpdater.cs:line 138
   at Microsoft.VisualStudio.Services.Agent.Listener.SelfUpdater.SelfUpdate(AgentRefreshMessage updateMessage, IJobDispatcher jobDispatcher, Boolean restartInteractiveAgent, CancellationToken token) in /Users/runner/work/1/s/src/Agent.Listener/SelfUpdater.cs:line 70
   at Microsoft.VisualStudio.Services.Agent.Listener.Agent.RunAsync(AgentSettings settings, Boolean runOnce) in /Users/runner/work/1/s/src/Agent.Listener/Agent.cs:line 346
[2023-05-19 04:59:17Z INFO Agent] Auto update task finished at backend, there is no available agent update needs to apply, continue message queue looping.

Hi @ferben, thanks for reporting! We are working on more prioritized issues at the moment but will get back to this one soon.

I think it's resolved by development. Now it works.


WIP: Feature/manager ready callback

Fixes 2 issues:

Allows developer to know when sdlmanager is ready to send requests
doesnt start submanagers until active proxy connection

CLA

[X] I have signed the CLA

Codecov Report

Merging #819 into feature/issue_782_Android_Managers will decrease coverage by 0.8%.
The diff coverage is 10.52%.

@@                           Coverage Diff                            @@
##             feature/issue_782_Android_Managers     #819      +/-   ##
========================================================================
- Coverage                                 44.27%   43.47%   -0.81%
+ Complexity                                 3205     2966     -239
========================================================================
  Files                                       373      372       -1
  Lines                                     18011    17554     -457
  Branches                                   1755     1763       +8
========================================================================
- Hits                                       7975     7631     -344
+ Misses                                     9705     9554     -151
- Partials                                    331      369      +38

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/smartdevicelink/api/BaseSubManager.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...main/java/com/smartdevicelink/api/ProxyBridge.java
5.74% <0%> (+2.17%)
3 <0> (+2)
:arrow_up:

.../main/java/com/smartdevicelink/api/SdlManager.java
36.66% <19.04%> (-1.03%)
15 <0> (+2)

...a/com/smartdevicelink/proxy/rpc/OnVehicleData.java
94.94% <0%> (-0.71%)
57% <0%> (-59%)

...celink/proxy/rpc/SubscribeVehicleDataResponse.java
96.73% <0%> (-0.02%)
57% <0%> (-29%)

...link/proxy/rpc/UnsubscribeVehicleDataResponse.java
96.73% <0%> (-0.02%)
57% <0%> (-29%)

...artdevicelink/proxy/rpc/enums/VehicleDataType.java
100% <0%> (ø)
2% <0%> (-1%)
:arrow_down:

...ink/proxy/rpc/enums/ElectronicParkBrakeStatus.java

.../com/smartdevicelink/proxy/rpc/GetVehicleData.java
98.88% <0%> (+0.19%)
59% <0%> (-31%)
:arrow_down:

...martdevicelink/proxy/rpc/SubscribeVehicleData.java
98.85% <0%> (+0.2%)
57% <0%> (-30%)
:arrow_down:

... and 14 more

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 6413709...b4fd386. Read the comment docs.


Detected blocking call to open with

Detected blocking call to open with args ('/config/custom_components/eero/api/images/logo_icon_white_background.png', 'rb') inside the event loop by custom integration 'eero' at custom_components/eero/api/init.py, line 69: self.default_qr_code = open(EERO_LOGO_ICON, "rb").read() if show_eero_logo else None (offender: /config/custom_components/eero/api/init.py, line 69: self.default_qr_code = open(EERO_LOGO_ICON, "rb").read() if show_eero_logo else None), please create a bug report at https://github.com/schmittx/home-assistant-eero/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#open
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component
result = await _async_setup_component(hass, domain, config)
File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in async_setup_component
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in
create_eager_task(
File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task
return Task(coro, loop=loop, name=name, eager_start=True)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 752, in async_setup_locked
await self.async_setup(hass, integration=integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/eero/init.py", line 180, in async_setup_entry
api = EeroAPI(
File "/config/custom_components/eero/api/init.py", line 69, in init
self.default_qr_code = open(EERO_LOGO_ICON, "rb").read() if show_eero_logo else None

I was not able to reproduce this, are you still experiencing a problem?

I see you were unable to reproduce the issue previously. Let me know if you need further information.

This should be fixed in 1.6.2; please update and confirm.

Wow that was speedy - thank you.
Sorry to ask, but is it just a question of overwriting the files in the custom_components folder?
Thanks

Sorry to ask, but is it just a question of overwriting the files in the custom_components folder?

Yep, exactly.

Thank you - all looking good so far :-)


Cancel and send buttons on feedback form do not work

I tried to use the feedback form, but neither the cancel nor the send button did anything. The rest of the UI (selection Issue, Idea, Other, textfields) were functional. I could go back with the phone's back button.
Phone: OnePlus Nord
Android: 12

Hey @johannesschweig, just tested it and I can confirm the behavior you're describing. Will be fixed in the next version as of https://github.com/mrzmyr/pixy-mood-tracker-app/commit/c52f06ed4f23b19c381b933f93d4cf8a57ac3efc.


Replace NLog with LibLog or Microsoft.Extensions.Logging

I was wondering if you would consider using a logging abstraction to allow better integration with applications
https://github.com/damianh/LibLog/wiki/Using
https://www.nuget.org/packages/Microsoft.Extensions.Logging

Hi andymac4182,
Thank you for your interest in this library, and thank you for submitting a PR request too.
Could you please elaborate as to why choosing LibLog over NLog would allow you to achieve better application integration? Some of my initial arguments against switching would be:

(In my honest opinion) it's relatively ugly to include an extra (big) code file in the project directly (which then needs to be maintained and updated in a non standard way).
Using reflection and "assumptions" about the consuming logging framework (the way LibLog works) is (once again, in my honest opinion) kind of ugly too. A lot of "magic" at play.
You still require a "regular" logging framework so the total dependency for this particular library / command line application still increases with 1 by using LibLog.
Some applications already depend on NLog being used in this library. There really needs to be a compelling case / significant advantage in order to offset the risk of breaking external code (although I realize it should "just work".

There was a couple of reasons for looking at LibLog over NLog.

NLog doesn't support any version of netstandard at the moment in a released package just their prerelease packages
Not all applications use NLog. LibLog allows people to use the logging framework they would like to use instead of being tied to your choice.
It doesn't remove the ability to use NLog just increases the amount of people that can get good logs integrated into their logging platform.
LibLog appears to be simpler to implement than Microsoft.Extensions.Logging and that would cause a much larger overhead I believe.
The alternative would be to build an internal logging implementation with extension packages to each logging implementation similar to how MassTransit does it but that would be a large overhead to maintain.

Thank you for providing more detail. I agree with your point that a library should not force a dependency on a logging framework (e.g. NLog) onto code consuming it.
Therefore, I have removed the NLog dependency and instead exposed a small IArduinoUploaderLogger interface which one can implement if one wants to subscribe to the log messages emitted by the library (fully optional).
I believe this allows for the best of both worlds, without introducing a dependency on LibLog.

Thanks @christophediericx I will have a look once you publish the new nuget package.

I just used your updated package. I noticed you fixed up the logger but didn't pull in the netstandard changes.

That's correct. I'm definitely not opposed to targeting NETStandard soon, but at the moment no testing at all has been done to see if everything still works properly when e.g. consuming the library from a .NET Core application. There might be some hickups in SerialPortStream (since serial port communication code is typically far from "portable"). I'll try and see if I can test it out in one of the coming weekends, though.

@christophediericx SerialPortStream targets Netstandard 1.5. Would you like me to add a example app that targets netcore2 as well?

Sure, that would be helpful. Curious to see what quirks (if any) will show up. I'll be out a couple of days (for a national park camping trip) but I should be able to provide feedback on Sunday or at the latest Monday evening. Thanks.

Closing this issue off since the logging is resolved 👍


A type inference pattern

The problem
The current implementation of foldMap has some type inference issues
import * as option from 'fp-ts/lib/Option'
import * as array from 'fp-ts/lib/Array'
import { monoidSum } from 'fp-ts/lib/Monoid'
import { foldMap } from 'fp-ts/lib/Foldable'

const monoid = option.getStaticMonoid(monoidSum)
const as = [1]
// x1 :: Option<{}> // <= {} instead of number
const x1 = foldMap(array, monoid, a => option.some(a), as)

Here TypeScript infers {} instead of number!
The solution
If I curry foldMap, the result is way better
export function foldMap$<F extends HKTS, M>(foldable: StaticFoldable<F>, monoid: StaticMonoid<M>): <A>(f: (a: A) => M, fa: HKT<A>[F]) => M {
  return <A>(f: (a: A) => M, fa: HKT<A>[F]) => foldable.reduce((acc, x: A) => monoid.concat(f(x), acc), monoid.empty(), fa)
}

// x2 :: Option<number>
const x2 = foldMap$(array, monoid)(a => option.some(a), as)

The pattern
After some trials and errors, a clean pattern seems to emerge: whenever in PureScript there is a type constraint, in fp-ts we need a curried function accepting the static dictionaries as first arguments
PureScript
foldMap :: forall f a m. Foldable f, Monoid m => (a -> m) -> f a -> m

TypeScript
function foldMap<F extends HKTS, M>(foldable: StaticFoldable<F>, monoid: StaticMonoid<M>): <A>(f: (a: A) => M, fa: HKT<A>[F]) => M

This is good news: in general porting PureScript libraries to fp-ts is pretty straightforward (with the possible exception of highly polymorphic signatures)

Alas there are many functions in fp-ts which I wrote when I was still learning TypeScript in February/March and before I was aware of this pattern, for example

Functor/lift
Foldable/toArray
Apply/liftA2
Apply/liftA3
Apply/liftA4
etc..

I'd like to change the current implementation but it's obviously a breaking change. I see 2 options

(1) brutal braking changes releasing v0.3
(2) migration path from 0.2 to 0.3 via deprecations

An example of (2) would be to define a curried foldMap$ as above and just deprecate foldMap. New code should use foldMap$ instead of foldMap so it will almost ready for the upgrade to v0.3 (should be a simple replace). Not sure if it worth it though
A Con of (2) is a more confusing code base, a Pro is that it leaves some time to figure out if there will be other breaking changes affecting other parts of fp-ts.
@OliverJAsh @sledorze @danielepolencic @leemhenson sorry to tag you all but being "real world" users I'd love to hear from you what you think

I'm fine with (1). It's still early days and I don't mind the breaking changes.
Also, I'll take the opportunity to ask a question.
If we decide for:

(1) brutal braking changes releasing v0.3

Is there anything like https://github.com/facebook/jscodeshift for Typescript?

Breaking changes is ok with me.

... leaves some time to figure out if there will be other breaking changes affecting other parts of fp-ts.

Maybe leave 0.3 in pre for a while until this is bottomed out though?

Is there anything like https://github.com/facebook/jscodeshift for Typescript?

That would be a great, AFAIK there's no such a tool. Perhaps it will be available after the work on prettier and typescript-eslint-parser is settled down

PR here https://github.com/gcanti/fp-ts/pull/93

Maybe leave 0.3 in pre for a while until this is bottomed out though?

I will publish a version in the next channel (npm install fp-ts@next) so we can check that everything is ok before actually releasing

@gcanti breaking changes fine with me too!

Relevant https://github.com/gcanti/fp-ts/pull/93#issuecomment-303172449

Hi all, I put up a branch (dev) with the lib folder committed in, please give it a spin on your codebase / lib and let me know if there are unexpected issues
npm i gcanti/fp-ts#dev

Pre-released v0.3 as fp-ts@next

FYI here's the change log so far
# 0.3.0

- **New Feature**
  - add `StateT` monad transformer, closes #104 (@gcanti)
  - add `Store` comonad, closes #100 (@rilut)
  - add `Last` monoid, closes #99 (@gcanti)
  - add `Id` monad (@gcanti)
  - Array: add extend instance (@gcanti)
  - NonEmptyArray: add comonad instance (@gcanti)
  - `examples` folder
  - `exercises` folder
- **Polish**
  - Tuple: remove StaticFunctor checking (@rilut)
- **Breaking Change** (@gcanti)
  - required typescript version: **2.3.3**
  - drop `Static` prefix in type classes
  - Change contramap signature, closes #32
  - Validation: remove deprecated functions
  - Foldable/toArray
  - Dictionary/fromFoldable
  - Dictionary/toUnfoldable
  - Profunctor/lmap
  - Profunctor/rmap
  - Unfoldable/replicate
  - compositions: renaming and signature changes
    - `getFunctorComposition` -> `getCompositionFunctor`
    - `getApplicativeComposition` -> `getCompositionApplicative`
    - `getFoldableComposition` -> `getCompositionFoldable`
    - `getTraversableComposition` -> `getCompositionTraversable`
  - `OptionT`, `EitherT`, `ReaderT` refactoring
  - drop `IxMonadT`, move `IxIO` to the `examples` folder
  - drop `Trans` module
  - `Free` refactoring
  - drop `rxjs` dependency
  - drop `lib-jsnext` folder
  - make `None` constructor private
  - remove `Pointed` and `Copointed` type classes


Performance and Capacity Planning documentation for WSO2 APIM v3.1.0

Description:
I can see there is a Performance and Capacity Planning documentation for the previous version (APIM v2.6.0) : link . But, I could not find Performance and Capacity Planning documentation for WSO2 API v3.1.0. Can you please share the documentation link for the same? We would need this for planning/evaluating the product for our use cases.
Content Positioning in Documentation:
Currently, it is available for APIM 2.6.0 here: https://docs.wso2.com/display/AM260/WSO2+API-M+Performance+and+Capacity+Planning
Suggested Labels:
Priority/highest/urgent

This is fixed.
https://apim.docs.wso2.com/en/3.1.0/install-and-setup/setup/deployment-best-practices/performance-test-results/


UART bug

In a mail by @eeboo he brought up the following repository: https://github.com/eeboo/stm32h743zi-test/
In there you will find two examples, one tagged ok, the other tagged ko. The ko example is producing garbage on his logic analyzer.
As one can see in his example code the only difference is:
// Acquire the GPIOD peripheral. This also enables the clock for
    // GPIOD in the RCC register.
    let gpiod = dp.GPIOD.split(ccdr.peripheral.GPIOD);

    let tx = gpiod.pd8.into_alternate_af7();
    let rx = gpiod.pd9.into_alternate_af7();

    // Configure the serial peripheral.
    let serial = dp
        .USART3
        .usart(
            (tx, rx),
            serial::config::Config::default(),
            ccdr.peripheral.USART3,
            &ccdr.clocks,
        )
        .unwrap();

in the Ok example, vs
    let gpiob = dp.GPIOB.split(ccdr.peripheral.GPIOB);

    let tx = gpiob.pb9.into_alternate_af8();
    let rx = gpiob.pb8.into_alternate_af8();

    // Configure the serial peripheral.
    let mut serial = dp
        .UART4
        .usart(
            (tx, rx),
            serial::config::Config::default(),
            ccdr.peripheral.UART4,
            &ccdr.clocks,
        )
        .unwrap();

in the not working example. (and only now am I realizing that in my response I actually misread, its not pd8 being used for both but pb8 for the not working one)
We should definitely investigate on this.

I can reproduce that Ok works
However Ko works perfectly fine for me as well, at least when modifying it so it echo's back to itself and then prints what it receives via RTT.
So this is an issue specific to @eeboo 's setup since I have a stm32h743zi chip on my end as well.
Would someone have an idea what we could do to figure out what's wrong with his setup?

Thanks for reporting this, it's good to have it in the issue tracker too.
Just a note that I also tried the UART4 peripheral in the past and it worked for me. But I was using pins PA11 and PA12.
Could you try using those pins instead? Are they accessible on the Nucleo board? It could actually be an electrical issue (broken trace or pad perhaps)

Hello thanks for your comments.
To avoid electrical issue I just run a new test generated with cubemx with UART 4 and PB9 as TX
It's working perfectly fine.

https://github.com/eeboo/st-nucleo-h743ZI-cubemx-serial-test

Hello my setup caused the issue.
when the logic analyzer is not plugged to the same computer as the nucleo board the interpreted data is corrupted.
when it is plugged on the same computer data is ok.
thank you very much for your feedback and sorry for wasting your time
I think you should close this issue

Ok, great that you've found the problem. Please make new issues if you find other problems with the HAL 😃
I did test the serial_usart4_ko example on a stm32h743vi rev Y, it worked for me also.


Check ztunnel namespace

Please provide a description of this PR:
This is a quick fix for part of https://github.com/istio/istio/issues/46032 - we may add more customization
or rules later.
It prevents use of ztunnel in other namespace - but also avoid the problem of a (malicious or accidental) pod
having the app=ztunnel label taking over ztunnel.

@costinm: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
c54274b637f0d0cce403c58fa7b0dc9d5b0cefe9
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

On 'SystemNamespace' - I'm not entirely sure how it is used and what is the intent, it doesn't seem to have any usage.
I assumed it's intended to map to the namespace where Istiod is installed.
In Istiod we usually use indicate where Istiod runs - it is ok to have Istiod running in tenant namespaces or use arbitrary names (not tested or supported - but used in various places).
The check here is to restrict where ztunnel can be deployed - even if you run Istiod in 10 namespaces, we don't want ztunnel in each of them.
I don't see a huge readability benefit to have "ISTIO_SYSTEM" and KUBE_SYSTEM constants and use them instead of the well-known values - the line above uses "app" and "ztunnel". But I don't mind having them as constants - what I do want
to avoid is having them as flags or options ( and the associated lack of testing if anything else is used, lack of use cases for using other values, security or breakage risks if someone is messing with it, etc)


Vagrant: Update instructions

Add some notes about the explicit nature of the Vagrant and Virtualbox
setup we support.
Related: #98
Signed-off-by: Kyle Mestery<EMAIL_ADDRESS>

LGTM!


Request: make binary artifacts to be statically linked

Context: https://github.com/lima-vm/alpine-lima/issues/77#issuecomment-1188572513

#57 produces statically linked binary.


Calling removeLayer() on L.D3SvgOverlay layer breaks map

Hello!
Many thanks for a great tool to easily add D3 overlays to leaflet maps. I've run across a problem when attempting to remove layers added with L.D3SvgOverlay to a map. I've recreated the swiss cities example here to demonstrate the problem:
http://embed.plnkr.co/f8YQg4LTVBsmMvdKaams/preview
I've added:
map.on('zoomend', function(e) {
  if (map.getZoom() < 8) {
    map.removeLayer(citiesOverlay);
  }
});

so that when one zooms out one level from the starting zoom, the citiesOverlay layer is removed but the map breaks. One can no longer pan or zoom the map any further.
Is there some other way to safely remove a map layer added with L.D3SvgOverlay, or is this a known issue with removeLayer() and L.D3SvgOverlay?
Thanks!
JD

One more thing to report with this problem. On another map I have where I have two layers, one just a run of the mill L.circleMarker and the other a L.D3SvgOverlay layer, I can remove the L.D3SvgOverlay layer and add the L.circleMarker layer with a time slider I've built, but zooming and panning break after the L.D3SvgOverlay layer is removed. It also breaks silently -- I don't see any error messages in the console to help debug.

Hi, JD
Have you noticed the issue #1 I have over here? I reproduced the Swiss cities case with my own bridge code - that deals with any SVG library, not just D3. Its approach is different in the way that it doesn't change the underlying SVG DOM when scaling happens. Maybe your code will work with it?
Disclaimer: at this point, it's only available as a fork of Leaflet. It could be made into a plugin, like the D3 plugin is.

Hi Asko!
Thank you! I'll try out your leaflet fork and see if that does the trick.
JD

Hi again Asko!
I looked at your fork of Leaflet and I didn't see a leaflet JS library that I can use directly. Do I need to build the library (I've not done that before) or is there one hidden in that repository I can use?
Thank you!!!
JD

@jdgodchaux
If you send me a msg at<EMAIL_ADDRESS>we can continue this discussion elsewhere (or open an issue in my fork pages).
Yes, you need to compile the fork. I haven't taken the time to make it a plugin (since that would mean also maintaining it, publicizing it and all). But there's no reason the code couldn't easily be made a plugin. I just haven't. For my own needs a forked Leaflet is enough.
I was also waiting to see if I get more people interested in using the code, first.

@jdgodchaux thanks for reporting the issue. Looks like unbinding of event listeners doesn't work as expected. Just commenting this part of the code fixes the issue: http://embed.plnkr.co/isWbcSOm41pVmmG7PX9x/preview
@akauppi please, see my response in #1

Thank you Kirill! That worked for me!
On Fri, Jun 5, 2015 at 5:32 AM, Kirill Zhuravlev<EMAIL_ADDRESS>wrote:

@jdgodchaux https://github.com/jdgodchaux thanks for reporting the
issue. Looks like unbinding of event listeners doesn't work as expected.
Just commenting this part of the code fixes the issue:
http://embed.plnkr.co/isWbcSOm41pVmmG7PX9x/preview
@akauppi https://github.com/akauppi please, see my response in #1
https://github.com/teralytics/Leaflet.D3SvgOverlay/issues/1
—
Reply to this email directly or view it on GitHub
https://github.com/teralytics/Leaflet.D3SvgOverlay/issues/5#issuecomment-109217141
.


rails_admin throw ActionController::InvalidAuthenticityToken in rails-api

rails_admin throw ActionController::InvalidAuthenticityToken when I want to create model

rails version 5.1.2 with --api mode
rails_admin version 1.2.0
change config.api_only from true to false in application.rb fix the problem idk why, anyone care to explain?

I think its related with this https://github.com/sferik/rails_admin/issues/2830
adding these stack into rails middleware also fix this
# application.rb
config.session_store :cookie_store
config.middleware.use ActionDispatch::Cookies
config.middleware.use ActionDispatch::Session::CookieStore, config.session_options

https://github.com/sferik/rails_admin/issues/2830#issuecomment-323622174

Thanks @buncismamen it worked for me!!

Thank you, this fixed it. But I don't get why this worked, can you explain? @buncismamen

@visheshruparelia because rails-api remove some middleware stacks that rails admin needs.
so you just need to re-added it.

Fixed by #3006.

i have the problem: back 422
ActionController::InvalidAuthenticityToken
i have add the code in application.rb
config.session_store :cookie_store
config.middleware.use ActionDispatch::Cookies
config.middleware.use ActionDispatch::Session::CookieStore, config.session_options
config.middleware.use Rack::MethodOverride
config.api_only = false


Add code formatter to javascript code

It seems like we don't have a defined linter/formatter for the js code and there's a ton of variation in indentation/semicolon, etc.
@CannonLock  Let's talk and setup a linter and formatter for the js code to improve coding style consistency.

Good call, thanks for calling that out. I can handle this.


avoided unnecessary git call from git_prompt_status

The primary use of git_prompt_status is in prompts, which demands that the function should be as fast as possible. Taking an early exit from this function on non-git directories saves around 60ms on my machine for every prompt that is rendered.

I'm working on a related PR to add a timeout to the git status calls, so slow repos don't cause the zsh prompt to hang in the status check functions (like in the case of a large repo directory tree, or repos on a network filesystem). It's #3725 (branch https://github.com/apjanke/oh-my-zsh/tree/git-status-timebox). I could merge in your short-circuit change so they can be tested and merged at the same time.
It looks like a lot of the time in git_prompt_status is spent on repeated shell-outs to grep. Parsing the status results using built-in zsh features could make it faster even in the case where you can't short-circuit. I took a stab at this (https://github.com/apjanke/oh-my-zsh/commit/f26f5014883deca0e56c94365994dab87e29d011) and the basic parser I came up with got it from around 45 ms down to 20 ms on the small repos I tested it on.

The difference between grep shell-outs and zsh builtins or the short-circuit is particularly pronounced on Cygwin on Windows, where starting a new process is more expensive. Saves nearly half a second. Though it's still a bit too slow for my taste at 110 ms when in a repo.
Here's a non-repo dir. This reflects your early-exit optimization, which saves half a second per prompt on Windows.
[@ in ~/local/opp]
$ time (_git_prompt_status_grep)

( _git_prompt_status_grep; )  0.10s user 0.36s system 85% cpu 0.546 total
[@ in ~/local/opp]
$ time (_git_prompt_status_zsh_parse)
( _git_prompt_status_zsh_parse; )  0.00s user 0.03s system 96% cpu 0.031 total

And here's a repo dir. About 400 ms speedup.
[@ in ~/local/opp/omz/oh-my-zsh on ⇄ git-status-timebox ±]
$ time (_git_prompt_status_grep)
M
( _git_prompt_status_grep; )  0.04s user 0.36s system 81% cpu 0.499 total
[@ in ~/local/opp/omz/oh-my-zsh on ⇄ git-status-timebox ±]
$ time (_git_prompt_status_zsh_parse)
M
( _git_prompt_status_zsh_parse; )  0.03s user 0.06s system 84% cpu 0.109 total

(This is on a repo on a local SSD, after multiple calls to each variant to warm up the cache, on a 2-core Windows 7 VM in VMware Fusion on a MacBook Pro.)


Enable osx-arm64 builds

When the PR for osx-arm64 was first merged, it wasn't cross compiling to osx-arm64, and was building a native version for osx-64. When cross-compiling was enabled, it failed with make: argument list too long. osx-arm64 build was disabled due to this error.

Any plan to fix this issue?


"PRAJILA", "Curăturile",  "Gătejești" are localities in "BĂILE GOVORA" city, "VALCEA" county

Description
When an user search a location, this appear in the drop-down menu
according to the law
Precondition
The website ( https://peviitor-ro.github.io/ui.orase/ ) is up an running.
Empty the search bar after every step

Steps 1
Write "PRAJILA"
Expected result
In the drop down menu you find "Localitatea PRAJILA, VALCEA (BĂILE GOVORA)"
Test Data
PRAJILA

Steps 2
Write "Curăturile"
Expected result
In the drop down menu you find "Localitatea Curăturile, VALCEA (BĂILE GOVORA)"
Test Data
Curăturile

Steps 3
Write "Gătejești"
Expected result
In the drop down menu you find "Localitatea Gătejești, VALCEA (BĂILE GOVORA)"
Test Data
Gătejești


Confusing text in security considerations

Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)
2:3.110.11
Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.
I am not sure what the following text means:
"The Resource Notification Broker might maintain a whitelist of acceptable senders for the rest-create/rest-update methods. "
Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.
Please rephrase and/or clarify.
Priority:

Low: Typo or other minor classification that an editor can manage. Requires no group discussion.

the concept is that the Resource Notification Broker can have policies for which only Subscribers being part of a specific list can perform subscriptions or unsubscriptions.
we can rephrase it to clarify @scontento


Add env var to configure whether reconciler deletes should be enabled.

Right now it's hardcoded.  This will mean adding an env key in vdi-common and wiring it into the reconciler config.

Why does this need to be configured, as opposed to being permanently set in the code?
and which way is it set now:  enabled or not?

This would primarily be useful in local development to avoid making code changes that might accidentally be committed.
Right now the option is hidden away and undocumented and only known to those familiar with the code.
In a perfect future where we have the ability to configure services, we would be able to make an env change ourselves to disable/enable this on dev/qa without needing to make junk commits solely for the purpose of working around our current devops limitations.


Use new path to loader.js

In regards to #150, this should fix the path issue.  However, there seems to be subsequent ember-data related issues.  @rwjblue I bower installed (without saving) ember-data and that addressed those issues only to be left with some assert.async related issues.  I figured I'd PR this change and see what happens.  Granted, the tests still won't pass.

Thanks!  This is a great start!


heap-buffer-overflow in vim at skip_string (src/cindent.c:94)

Hello,
We are currently working on fuzz testing feature, and we found a heap-buffer-overflow on vim.
The stack traces are as follow:
==25536==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x621000012900 at pc 0x562b81ffecf3 bp 0x7fff8f674610 sp 0x7fff8f674600
READ of size 1 at 0x621000012900 thread T0
    #0 0x562b81ffecf2 in skip_string .../vim-git/src/cindent.c:94
    #1 0x562b82003e96 in find_last_paren .../vim-git/src/cindent.c:1131
    #2 0x562b8201367e in get_c_indent .../vim-git/src/cindent.c:3713
    #3 0x562b821f94cf in op_reindent .../vim-git/src/indent.c:1060
    #4 0x562b822febd6 in do_pending_operator .../vim-git/src/ops.c:3998
    #5 0x562b822b5adf in normal_cmd .../vim-git/src/normal.c:1125
    #6 0x562b82144188 in exec_normal .../vim-git/src/ex_docmd.c:8574
    #7 0x562b82143f64 in exec_normal_cmd .../vim-git/src/ex_docmd.c:8537
    #8 0x562b82143805 in ex_normal .../vim-git/src/ex_docmd.c:8455
    #9 0x562b82121e30 in do_one_cmd .../vim-git/src/ex_docmd.c:2614

Here is the full stack trace : full_stacktrace_poc_6.zip
Step to reproduce
We configured vim using CFLAGS="-g -O0 -fsanitize=address" CXXFLAGS="-g -O0 -fsanitize=address" LDFLAGS="-g -O0 -fsanitize=address" ./configure --prefix=$(pwd)/ and build it using make -j10, and run it with:
./vim -u NONE -X -Z -e -s -S <attached file> -c ':qa!'

Attachment: input_vim_poc_6.zip
Environment

OS: Ubuntu 18.04.5 LTS
GCC version: gcc 7.5.0
vim version: latest commit (f67d3fb7) of master branch in github (link)

Thank you.

I can reproduce it with the latest vim-8.2.3480 and minimized it to an obscure 2-line script:
$ cat bug.vim
exe "norm v>O'\\\<C-m>-"
exe "norm \<C-q>="

$ valgrind ./vim --clean -e -s -S bug.vim -c'q!'
==11501== Memcheck, a memory error detector
==11501== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==11501== Using Valgrind-3.17.0.GIT and LibVEX; rerun with -h for copyright info
==11501== Command: ./vim --clean -e -s -S bug.vim -cq!
==11501==
==11501== Invalid read of size 1
==11501==    at 0x423FCA: skip_string (cindent.c:94)
==11501==    by 0x429CF4: find_last_paren (cindent.c:1131)
==11501==    by 0x427D72: get_c_indent (cindent.c:3713)
==11501==    by 0x4F6AA4: op_reindent (indent.c:1060)
==11501==    by 0x55AE8E: do_pending_operator (ops.c:3998)
==11501==    by 0x5448FB: normal_cmd (normal.c:1125)
==11501==    by 0x4A4E3A: exec_normal (ex_docmd.c:8574)
==11501==    by 0x4A4CE3: exec_normal_cmd (ex_docmd.c:8537)
==11501==    by 0x4A4C09: ex_normal (ex_docmd.c:8455)
==11501==    by 0x49C664: do_one_cmd (ex_docmd.c:2614)
==11501==    by 0x49978F: do_cmdline (ex_docmd.c:1000)
==11501==    by 0x46C110: ex_execute (eval.c:6250)
==11501==  Address 0xa4395a0 is 0 bytes after a block of size 4,096 alloc'd
==11501==    at 0x4C32FB5: malloc (vg_replace_malloc.c:380)
==11501==    by 0x406636: lalloc (alloc.c:244)
==11501==    by 0x4065D9: alloc (alloc.c:151)
==11501==    by 0x71162D: mf_alloc_bhdr (memfile.c:884)
==11501==    by 0x71129A: mf_new (memfile.c:376)
==11501==    by 0x51EEA0: ml_new_data (memline.c:4068)
==11501==    by 0x51E990: ml_open (memline.c:394)
==11501==    by 0x40F82F: open_buffer (buffer.c:190)
==11501==    by 0x70E286: create_windows (main.c:2851)
==11501==    by 0x70DAD3: vim_main2 (main.c:704)
==11501==    by 0x70B727: main (main.c:425)
==11501==
==11501==
==11501== HEAP SUMMARY:
==11501==     in use at exit: 2,061,571 bytes in 17,219 blocks
==11501==   total heap usage: 31,280 allocs, 14,061 frees, 17,157,897 bytes allocated
==11501==
==11501== LEAK SUMMARY:
==11501==    definitely lost: 0 bytes in 0 blocks
==11501==    indirectly lost: 0 bytes in 0 blocks
==11501==      possibly lost: 3,759 bytes in 67 blocks
==11501==    still reachable: 2,057,812 bytes in 17,152 blocks
==11501==         suppressed: 0 bytes in 0 blocks
==11501== Rerun with --leak-check=full to see details of leaked memory
==11501==
==11501== For lists of detected and suppressed errors, rerun with: -s
==11501== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)


Window resizing issues

Because of this crash on macos: https://github.com/BabylonJS/BabylonNative/issues/151
now bgfx::frame is called when resizing, replacing a call to bgfx::touch
Crash is fixed and no strange behavior appearing on win32/Android.
On UWP a flickering was experienced before, now the refresh happens 0.5s after resizing, without flickering.
On iOS, there is a Metal exception when a bgfx::touch(0) is not performed once a frame.

Blocked on the rendering rework (#345)

I need to check if there are still issues.

Resize and resume tested OK on Android, win32, uwp, ios and mac. Closing.


Troubleshooting label widget

Moved from https://github.com/cmv/cmv-app/issues/642#issuecomment-264847921
@roemhildtg We're giving it a try in a copy of our editor. Looks good for a long time, but ultimately doesn't label. We keep getting an error , maybe one of those still existing bugs you mention. Maybe analyzing the error in the app helps to see what's happening: https://www.hgis-indias.net/cmv-app-master/label/
Anyway, please keep me updated, this seems to be really useful for us, probably not for all layers, but for the "aggregated data" ones, where I can imagine people would want to use different values as labels and there's no need to label more than one of them.

I tried adding labels to the lagos layer (https://www.hgis-indias.net:6443/arcgis/rest/services/HGIS/hgis_fisico/MapServer/1)
The error I get is esri.layers.FeatureLayer: unable to find a field of type 'esriFieldTypeGeometry' in the layer 'fields' information. If you are using a map service layer, features will not have geometry [url: https://www.hgis-indias.net:6443/arcgis/rest/services/HGIS/hgis_fisico/MapServer/1]
This means you don't have your "Shape" field turned on when you published the service. This is highly recommended to have turned on, and it is necessary for Feature layers which the label layer uses.

FYI, I published the service again with all fields turned on!

@Wernazuma I've made some major enhancements to the label widget.
After going back through your original issue, it appears we both had a very similar issue...people want different types of labels and rather than providing a set of 15-20 layaers just for labels, why not let the user create them on the fly?
The new functionality allows exactly this, and you can also set up predefined labels as the developer to enable users to quickly add frequently used/complex label expressions.
https://github.com/roemhildtg/cmv-widgets/tree/master/widgets/LabelLayer

FYI, your app is using an old version of the api (3.14). you may want to try updating to 3.19 and see if anything changes.

Thank you for your update! We'll try that and make a new effort to get it working. This could make our app so much lighter instead of having dozens of "label only" layers. I'm at a conference next week, but I will report back how we fare!

An update: We checked the new version 3.2 but we figured that there is a lot we'd have to work over so we wait for CMV version 2.0 so we don't do redundant work.