a little mistake in the code

https://github.com/tgsmith61591/smrt/blob/0863b0b94897ad8d8d9184b792cdb275627e1ac4/smrt/balance/smrt.py#L207
I think this should be
X_sub = X_copy[y_transform == transformed_label, :]

Thanks for taking the time to file an issue. I think you're right. Feel free to file a PR, if you like. We haven't been working on this project in a while, but I have another project that built on this balancing codebase, should you be interested in using it: https://github.com/tgsmith61591/skoot

Thanks for your reply. In fact, I have met a problem about the imbalabced dataset recently. My dataset is so imbalanced that the variance of the Gaussian distribution is too low and the distribution is almost the same as Dirac delta function. we compare the image nums to the lables as following.

the x-axis represents the num of images in one id and the y-axis represents the corresponding labels' num. So I would like to ask you a double of questions:
Do you think it is a good way to use SMOTE to balance this kind of dataset?
And can you recommend me some efffiencient strategies to handle such problem?
Thanks very much!

The original SMOTE paper got its biggest performance boost by combining down-sampling with their method. I think it would absolutely be worth trying such a method. Things like:

Downsample
Perform SMOTE
Consider stratified batching (if you're using a minibatch family of algorithms)
Explore class-weighted loss functions

The skoot package I shared can help you downsample and perform SMOTE, but the other strategies will depend on your framework and family of algorithms.

Thanks for your help.
In fact I have tried other 3 methods except SMOTE, but still can not improve the performance.  Since my dataset is 2D image of human bodies in different poses and SMOTE augment the dataset by linear interpolation,  I was wondering this method may generate misleading images and did not consider it in the first place.  But now maybe it is the only one I can count on......


incomplete comment in proto_format.sh

Title: Incomplete comment found in script proto_format.sh
Description: incomplete comments in proto_format.sh script it says "# Generate //versioning:active_protos."
However it produces both active and frozen_protos as well.
url: https://github.com/envoyproxy/envoy/blob/master/tools/proto_format/proto_format.sh#L27

Describe the issue.

[optional Relevant Links:]

Any extra documentation required to understand the issue.

though it is very trivial bug to report but i thought it should be corrected for clarity of code.

@dio. please reopen it and assign to me. as per your latest comment i will push pr.

/no stalebot


Add a customisable FVT for subject area omas

Add a customisable FVT for subject area omas - to allow any serverName and any userId to be used to run the Subject Area OMAS FVT

See https://github.com/odpi/egeria/issues/2524
Suggest we ensure we can easily and regularly run the FVT
Depends upon:

Switch containers to run the full metadata distribution (#2375)
FVT execution (#426)

This issue needs to:

Ensure this FVT is appropriately packaged within the distribution files
Provide instructions to run these tests against the 'standard' environment (this could be a docker/kubectl 'exec' command to launch the test - whilst making the tests as configurable as needed
Subsequently automate the execution of these specific tests

persue in #426


Update README.md with the description of Windows build setup

Added a brief description on how to build the app on Windows

Wow, I didn't realize there is extra setup for libretro on Window
Thank you so much for the PR!!! It will be a great help for Window user.


themes: add new felipec theme

Autogenerated with vim-felipec.

Please show results of running check-theme utility.

Hello, here are the results.
I noticed the tool checks for template-tag and formula, but one is barely used, and the other doesn't seem to be ever used.
Templates/HTML/XML, etc.
- Theme does not fully support.
- scope template-tag is not highlighted
  (css: .hljs-template-tag)

Markup (Markdown, etc)
- Theme does not fully support.
- scope formula is not highlighted
  (css: .hljs-formula)

nice to haves (optional, but many grammars use)
- Theme does not fully support.
- scope meta keyword is not highlighted
  (css: .hljs-meta .hljs-keyword)
- scope meta string is not highlighted
  (css: .hljs-meta .hljs-string)

high fidelity highlighting (this is optional)
- Theme does not fully support.
- scope title.class is not highlighted
  (css: .hljs-title.class_)
- scope title.class.inherited is not highlighted
  (css: .hljs-title.class_.inherited__)
- scope title.function is not highlighted
  (css: .hljs-title.function_)
- scope char.escape is not highlighted
  (css: .hljs-char.escape_)
- scope variable.language is not highlighted
  (css: .hljs-variable.language_)

Accessibility Report
┌───────┬────────────────────────────────────────┬──────────┬──────────┐
│ ratio │ selector                               │ fg       │ bg       │
│ 12.27 │ .hljs                                  │ #dddde1  │ #1e1e22  │
│ 6.64  │ .hljs::selection,.hljs ::selection     │ #1e1e22  │ #bf8fef  │
│ 4.75  │ .hljs-comment,.hljs-code,.hljs-quote   │ #888896  │ #1e1e22  │
│ 7.12  │ .hljs-number,.hljs-literal,.hljs-dele… │ #ef8f8f  │ #1e1e22  │
│ 9.9   │ .hljs-punctuation,.hljs-meta,.hljs-op… │ #efbf8f  │ #1e1e22  │
│ 13.78 │ .hljs-type                             │ #efef8f  │ #1e1e22  │
│ 12.63 │ .hljs-tag,.hljs-title,.hljs-selector-… │ #bfef8f  │ #1e1e22  │
│ 11.8  │ .hljs-string,.hljs-regexp,.hljs-addit… │ #8fef8f  │ #1e1e22  │
│ 12.08 │ .hljs-class,.hljs-property             │ #8fefbf  │ #1e1e22  │
│ 12.47 │ .hljs-name,.hljs-selector-tag          │ #8fefef  │ #1e1e22  │
│ 8.6   │ .hljs-keyword,.hljs-built_in           │ #8fbfef  │ #1e1e22  │
│ 5.81  │ .hljs-section,.hljs-bullet             │ #8f8fef  │ #1e1e22  │
│ 6.64  │ .hljs-selector-pseudo                  │ #bf8fef  │ #1e1e22  │
│ 7.79  │ .hljs-variable,.hljs-params,.hljs-att… │ #ef8fef  │ #1e1e22  │
│ 7.4   │ .hljs-symbol,.hljs-link                │ #ef8fbf  │ #1e1e22  │
└───────┴────────────────────────────────────────┴──────────┴──────────┘

Also, my theme was using background-color which is more proper than background, but the checkTheme crashed with that.

I'm not sure it's more "proper". More exact, perhaps. We'd be open to a PR making the tool smarter. It shouldn't have crashed in any case.

@joshgoebel Well, it is more precise: background is a shorthand property for a bunch of other properties, which include background-color, the actual property we care about.
I've sent a pull request to check for that too: #3449.

Do I need to add template-tag and formula? Or what is missing for consideration?

Do I need to add template-tag and formula? Or what is missing for consideration?

I need to find time to pull it up and at least have a  quick glance at it... holidays.  You haven't been forgotten.  Just busy.

All right. Here's a screenshot if it helps: screenshot.

Approved, please add CHANGELOG entry?

@joshgoebel Done. I followed the steps of intellij-light and updated tools/developer.html too.
BTW. I think my generator might be useful to other theme creators, for example:
palette:
  red: '#ef8f8f'

blocks:
  - - number literal deletion
    - color: red

Gets converted to:
.hljs-number,
.hljs-literal,
.hljs-deletion {
  color: #ef8f8f;
}

The full YAML code I used to generate my theme is this: felipec.yml. I use HSL instead of hex triplets, but they get automatically converted.

Thanks.


simple attempt to speed up cold starts

use the cached for UPAKs on LoadUserPlusKeys on prod and staging. We get invalidations so it should be safe!

r? @mmaxim

I'm still slightly in favor of modifying the test, but looks good!

I don't know how to modify the test without slowing it down a bunch or introducing flakes.

No problem!


npm prepack fails for plugins outside of runtime folder and specifying the module in nuxt.config.ts fails with error in md

Environment
Operating System: Mac OS Ventura
Node Version: v20.10.0
Nuxt Version: 3.10.0
Package Manager<EMAIL_ADDRESS>Reproduction
https://stackblitz.com/edit/github-bfnrsx-dxkhza?file=src%2Fplugins%2Flogger.client.ts,src%2Fplugins%2Flogger.server.ts,src%2Fmodule.ts,package.json,src%2FlogLevels.ts,playground%2Fnuxt.config.ts
Describe the bug
When I run the following commands:
npm run dev:prepare i.e. nuxt-module build
npm run prepack
It only works if there is the plugin.ts in the runtime folder. When I add a plugins folder and load those files with addPlugin, I get the failure when run the prepack script
I get the following error
ERROR Exiting with code(1). You can change this behavior by setting failOnWarn:false.
Additional context
The project fails build if I omit the 'prepack' command and publish the module using 'release' command. Here is the configuration I use in the my Nuxt apps.  I also get a failure when I call useNuxtApp() on the server side.  I read that I can use the event.context in some way to get the logger, but the logging the context has mostly empty objects
 // https://nuxt.com/docs/api/configuration/nuxt-config
 export default defineNuxtConfig({
                nitro: {
                                serveStatic: true,
                },
                css<EMAIL_ADDRESS>                modules: ['@vueuse/nuxt', '@cp/logger'],
                runtimeConfig: {
                                public: {
                                  firstModule: {
                                                loggerOptions: {
                                                  appName: '@cp/logger',
                                                  useIsoTime: false,
                                                  outPutOnSingleLine: true,
                                                  clientOptions: {
                                                                level: 'info',
                                                  },
                                                  serverOptions: {
                                                                level: 'info',
                                                                useFormattersAndSerializers: true,
                                                  },
                                        },
                                  },
                                },
                  }
      })

```If I build the project without  'prepack'  and publish the app using release script, I get the error when I use the logger in any nuxt app as follows:

ERROR  Cannot find module '/workspace/source/node_modules/jiti/lib/index.js'
Require stack:
-<EMAIL_ADDRESS>

### Logs

_No response_

It turns out to be a defu issue, causing the build to fail


added tag for fluentd on instance type entity

added tag for fluentd on instance type entity

Tested in controlled environment and works fine. Next step is to write the unit test for the new method added.

Assuming extending taupage/stups support, such info should be retrievable from the User data of the instance. Similar to this line here where we retrieve application_id, stack_version etc...

👍

👍


TableViewHeaderFooterView should not override any font or color provided as part of the AttributedString

Platforms Impacted

[ x] iOS
[ ] macOS

Description of changes
There is an issue with usage of this control when an NSAttributedString is provided for the label. The existing code updates the font and foreground color of the label in a number of places, but this will override any font or foreground color attributes which the consumer may have set in the attributed string.
We can extract the UIFont and UIColor and store these if they have been provided as part of the attributed string, and wherever we update the font or color, we can apply the provided values where they exist, otherwise fall back to the default values we were previously using.
Verification
Verified locally when integrated into an app that the default font and color are used where not provided, and if they are provided as part of the attributed string then those values will be used instead.

Visual Verification

Before
After

Screenshot or description before this change
Screenshot or description with this change

Pull request checklist
This PR has considered:

[x] Light and Dark appearances
[x] iOS supported versions (all major versions greater than or equal current target deployment version)
[x] VoiceOver and Keyboard Accessibility
[x] Internationalization and Right to Left layouts
[x] Different resolutions (1x, 2x, 3x)
[x] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

Curious if this couldn't be dealt with externally by overriding the font and title color tokens.

Not sure on that, though it is an interesting question. I would assume that if I override font/color tokens that could apply to other elements of this/other FluentUI components, whereas it should only apply to the attributed string. In addition to that I am not sure that the caller should assume knowledge of the internals of this component (i.e. what font/color tokens are used and where, which could change).
Even considering that, I do think that it would still be correct behaviour to not override the consumer provided string attributes, and that this change would make sense regardless of what the consumer does with the tokens...

Curious if this couldn't be dealt with externally by overriding the font and title color tokens.

Not sure on that, though it is an interesting question. I would assume that if I override font/color tokens that could apply to other elements of this/other FluentUI components, whereas it should only apply to the attributed string. In addition to that I am not sure that the caller should assume knowledge of the internals of this component (i.e. what font/color tokens are used and where, which could change).
Even considering that, I do think that it would still be correct behaviour to not override the consumer provided string attributes, and that this change would make sense regardless of what the consumer does with the tokens...

Overriding the tokens on a control instance doesn’t propagate to other fluent controls. Also fluent control tokens are publicly exposed and architected to allow partners to customize them as they see fit, so I don’t think there are any particular assumptions about what’s going on internally that need to be considered.
But yeah I do agree this change makes sense regardless, especially considering TableViewCell seems to have similar custom behavior for attributed titles.