[eslint-config] Environment key "jest/globals" is unknown

Description
I use @react-native-community/eslint-config with TypeScript. After update "@typescript-eslint/eslint-plugin", "@typescript-eslint/parser", and "@typescript-eslint/typescript-estree" from "5.24.0" to "5.25.0" I have error
Oops! Something went wrong! :(

ESLint: 8.16.0

Error: .eslintrc.js » @react-native-community/eslint-config#overrides[2]:
        Environment key "jest/globals" is unknown

    at /Users/bardiamist/Documents/my-proj/my-proj-mobile/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2058:23
    at Array.forEach (<anonymous>)
    at ConfigValidator.validateEnvironment (/Users/bardiamist/Documents/my-proj/my-proj-mobile/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2052:34)
    at ConfigValidator.validateConfigArray (/Users/bardiamist/Documents/my-proj/my-proj-mobile/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2202:18)
    at CascadingConfigArrayFactory._finalizeConfigArray (/Users/bardiamist/Documents/my-proj/my-proj-mobile/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3947:23)
    at CascadingConfigArrayFactory.getConfigArrayForFile (/Users/bardiamist/Documents/my-proj/my-proj-mobile/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3753:21)
    at FileEnumerator._iterateFilesRecursive (/Users/bardiamist/Documents/my-proj/my-proj-mobile/node_modules/eslint/lib/cli-engine/file-enumerator.js:446:49)
    at _iterateFilesRecursive.next (<anonymous>)
    at FileEnumerator.iterateFiles (/Users/bardiamist/Documents/my-proj/my-proj-mobile/node_modules/eslint/lib/cli-engine/file-enumerator.js:297:49)
    at iterateFiles.next (<anonymous>)
error Command failed with exit code 2.

Version
3.0.2
Output of npx react-native info
System:
    OS: macOS 12.4
    CPU: (10) arm64 Apple M1 Max
    Memory: 8.97 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.2.0 - /opt/homebrew/bin/node
    Yarn: 1.22.15 - /opt/homebrew/bin/yarn
    npm: 8.9.0 - /opt/homebrew/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8512546
    Xcode: 13.4/13F17a - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.15 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.68.2 => 0.68.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce
Use @react-native-community
Run yarn eslint .
Snack, code example, screenshot, or link to a repository
module.exports = {
  parser: "@typescript-eslint/parser",
  extends: [
    'plugin:@typescript-eslint/recommended',
    '@react-native-community',
    'airbnb',
  ],
  ...
};

https://github.com/typescript-eslint/typescript-eslint/issues/5132

Looks fixed in typescript-eslint 5.27.1

I had the same error and what worked was yarn-deduplicate, see also this comment: https://github.com/facebook/react-native/issues/32181#issuecomment-966998048
I think it's related.

Updating jest in package.json fixed this for me

Problem appears often afetr some depencencies update
I fixing by next steps:

Set in package.json version of @react-native-community/eslint-config to 2.0.0 (3.1.0 don't work)
yarn
Set version back to 3.2.0
yarn

Here is what helped me
npm i eslint-plugin-jest -D
More details here

In my case I was missing the file: jest.config.js in the root of my project. I added it with the following contents:
module.exports = {
    preset: 'react-native',
    moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json', 'node'],
};

For me this command fix it...
yarn upgrade @typescript-eslint/eslint-plugin @typescript-eslint/parser

For me this error showed up at upgrading from RN 0.73.9 to 0.74.5,
I fixed it with updating in package.json the following 2 modules vrom v5 to v7:
-    "@typescript-eslint/eslint-plugin": "^5.40.1",
-    "@typescript-eslint/parser": "^5.40.1",
+    "@typescript-eslint/eslint-plugin": "^7.18.0",
+    "@typescript-eslint/parser": "^7.18.0",


Missing required module 'CommonCrypto'

On Xcode 9, when installing the library through Carthage I get the following error when building my project:
"Missing required module 'CommonCrypto'".
However, on my development computer, this error does not appear.
The only difference I noticed is that on my own computer I have the "Checkouts/JSONWebToken" folder that contains the modulemap for CommonCrypto.
In my CI computer, I don't have the "Checkouts" folder so the modulemaps are not present.
Is there any possible fix for this?

Fixed.
I removed the "import JWT" from the file where I'm using it and now it builds and works properly.
However, I didn't understand why this is happening.

I'm having a similar issue where my CI fails with an error: missing required module 'CommonCrypto' but my development computer works fine.
Removing the "import JWT" line didn't work for me, it's just giving me errors of use of undeclared types.

Turns out that I wasn't using the library in the project and forgot to clean it.
But it's an odd error to have, I couldn't understand why it was happening on my CI and not locally...

@IvoPintodaSilva Thanks for the update.
With that being said, this issue is not really fixed and closed then...
@kylef Can we get this sorted out?

As per the Carthage nested dependencies documentation, you will need to add the CommonCrypto framework to your project.

If the embedded framework in your project has dependencies to other frameworks you must link them to application target (even if application target does not have dependency to that frameworks and never uses them).

I'm sorry if I'm asking a dumb question, but how exactly should I add the CommonCrypto framework to my swift project in this case?


SVG file not tagged as "image"

SVG files do not include an "image" tag, but they are images (as indicated in the following references):

https://fileinfo.com/extension/svg
https://en.wikipedia.org/wiki/Scalable_Vector_Graphics

Can the entry in extensions.py be updated from:
'svg': {'text', 'svg'},

to:
'svg': {'text', 'image', 'svg'},

?

sure, sounds good -- would you please send a patch?

sure thing.


Upgrading to 0.12.2 breaks MultiJson

Since 0.12.2 Que is attempting to call a non-exitent parse method on MultiJson module if it's present.

Fixed in 0.12.3, thanks!


Larger input image, Bigger model size

I'm facing mlmodel size issue on iOS when implementing style transfer model. tfcoreml convertor makes mlmodel bigger when setting large input image size. Does size of mlmodel depend on size of input image? I think mlmodel size should be constant despite of input image size because mlmodel only contains weights trained.

Please provide details to replicate the issue.

@aseemw Sorry for late.
I made decoder like below
Input: feature from encoder as shape as 1x120x160x512 (N x H x W x C)
Net:
deconv = Input
rows = Input.W
cols = Input.H
for i in range(3):
deconv = tf.image.resize_images(deconv, rows ,cols,
method=tf.image.ResizeMethod.NEAREST_NEIGHBOR)
deconv = tf.pad(deconv, [[0, 0], [padding_size, padding_size ],
[padding_size, padding_size ], [0, 0]], mode='REFLECT')
W_conv, b_conv = self.deconv_layer[i]
deconv = conv2d(deconv, W_conv, stride=self.dec_conv_stride[i], padding='VALID')
deconv = tf.nn.bias_add(deconv, b_conv)
rows = rows * 2
cols = cols * 2
Input shape of decoder can be changed by input shape of encoder. Large input image makes big feature. (ex. If input image of encoder is 360x480, then feature shape is 45x60x512. And if input image size is 720x960, then feature shape is 90x120x512).
First I freeze above network (model_frozen.pb) then convert model_frozen.pb to model_frozen_coreml.mlmodel. As I reported before size of converted .mlmodel is dependent on size of input feature although model_frozen.pb file always has same size.
I just wonder why this happened and please let me know how to solve this problem.
Thank you~

Here is the frozen .pb
arbitrary_enc_decoder_frozen.pb.zip

Here is the frozen .pb
frozen.pb.zip
Thank you~

I figured out why this is happening. Its basically due of the limitation of the "minimum" and "maximum" layers in Core ML. They do not support broadcasting.
The TF graph has two operations in the end: min(x,255) and max(x,0). Currently these are implemented using CoreML's load constant layer and min/max layers. Due to the load constant layer and broadcasting its shape during conversion, the size of the model increases.
Long term solution is not to change the converter but to modify the CoreML layer.
Short term: maybe a hack in the converter can get rid of this issue, for this particular model. max(x,0) is same as relu. min(x,255) is trickier but can be approximated using sigmoid hard layer.
If these ops are in the end, you can also convert the graph before them and implement them as post processing after obtaining the output from CoreML.

@aseemw I really appreciate your detail review. Your guide helped solving problem. Thank you :).

@aseemw can you please teach me how to convert such pb models using tf-coreml?I dont know how to set the input shape in the param input_name_shape_dict.this is my pb file:https://drive.google.com/file/d/1bGM82rdAQlZUj7F8W2wm_JJBmBxNBiah/view?usp=sharing
thank you!

These are the two inputs (from this script)
0: op name = import/Placeholder, op type = ( Placeholder ), inputs = , outputs = import/Placeholder:0
@input shapes:
@output shapes:
name = import/Placeholder:0 : (?, ?, 3)
1: op name = import/Placeholder_1, op type = ( Placeholder ), inputs = , outputs = import/Placeholder_1:0
@input shapes:
@output shapes:
name = import/Placeholder_1:0 : (?, ?, 3)

So the input dict should be something like: {"Placeholder:0":[H1,W1,3], "Placeholder_1:0": [H2,W2,3]}
where H1,H2,W1,W2 are the values that you have tested works on the original TF model.
However, looking at the ops in this graph, there are quite a few that are not supported at this time:

Hi, I was having a similar issue when my model size increased from 30MB (.pb file) to 90MB (.mlmodel) after the conversion.
Thanks to @aseemw for pointing out the root cause of this. For a short term solution, I replaced the Minimum layer implementation in the converter as follows:-
def minimum(op, context):
  input_name = make_tensor(op.inputs[0], context)
  output_name = compat.as_str_any(op.outputs[0].name)
  neg_output_name = output_name + '_neg'
  # negate it
  context.builder.add_activation(
      neg_output_name, 'LINEAR', input_name, neg_output_name, [-1.0, 0])
  # apply threshold
  clip_output_name = output_name + '_clip'
  context.builder.add_unary(
      clip_output_name, neg_output_name, clip_output_name, 'threshold',
      alpha=-6.0)
  # negate it back
  context.builder.add_activation(
      output_name, 'LINEAR', clip_output_name, output_name, [-1.0, 0])
  context.translated[output_name] = True

For me the constant was 6 for all the layers, so it became fairly easy. It might be tricky if all your layers have a different constant to compare against. Doing this implementation helps me get rid of the broadcasting of constant to huge matrices which was increasing the model size. Verified that converted model is same size and produces same results.


setup peerDependencies

kill src/setup/setup.sh's src/examples/EXAMPLE/package.json copy

peerDependencies might not be the solution here, as peerDepenedencies are not auto-installed in npm3.
The extra dependencies come from

angular2's parse5 adapter - it requires css and parse5, but doesn't list them as dependencies

angular2 should include these

angular2's parse5 adapter (again) - it requires url, but React Native doesn't patch url

React Native should include a patch for url or support patching

Not sure why other dependencies are being flattened. I think many of these can just be removed.

either move alexeagle/typescript#error_is_class dependecy to src/examples/EXAMPLE/package.json, to peerDependencies, or remove it altogether.


TabbedPage sample crashes

I get an unhandled exception in the ControlGallery app when using the TabbedPage sample.
Build info

Built from source, using the cloned repo (commit "a897e3ce77f66181c97e7f5c80cabe749f3030de").
I have changed nothing in the build config, and git diff shows nothing changed.
Building in Debug configuration
Building and running on the same Windows machine.

Reproduce

Click on the TabbedPage sample
Switch from the "Red" tab to the "Green" tab (Or any other tab, it seems)

Exception
Type: System.ArgumentException
Message: "The parameter is incorrect."
Stacktrace:
at WinRT.ExceptionHelpers.g__Throw|20_0(Int32 hr)
at ABI.Microsoft.UI.Xaml.IFrameworkElementOverridesMethods.MeasureOverride(IObjectReference _obj, Size availableSize)
at Microsoft.UI.Xaml.FrameworkElement.MeasureOverride(Size availableSize)
at ABI.Microsoft.UI.Xaml.IFrameworkElementOverrides.Do_Abi_MeasureOverride_0(IntPtr thisPtr, Size availableSize, Size* result)
Tried

Restarted Visual Studio 2022
Restarted System
Disabled AV
Attempted running VS in Admin and non-Admin modes

System Info

Windows 10 Pro  10.0.19045, 64-bit
Processor: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz, 3600 Mhz, 4 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM)	16.0 GB

Visual Studio Info
Microsoft Visual Studio Professional 2022
Version 17.7.4
VisualStudio.17.Release/17.7.4+34031.279
Microsoft .NET Framework
Version 4.8.09037
Installed Version: Professional
Visual C++ 2022   00476-80000-00000-AA789
Microsoft Visual C++ 2022
ADL Tools Service Provider   1.0
This package contains services used by Data Lake tools
ASA Service Provider   1.0
ASP.NET and Web Tools   17.7.273.65229
ASP.NET and Web Tools
Azure App Service Tools v3.0.0   17.7.273.65229
Azure App Service Tools v3.0.0
Azure Data Lake Tools for Visual Studio   2.6.5000.0
Microsoft Azure Data Lake Tools for Visual Studio
Azure Functions and Web Jobs Tools   17.7.273.65229
Azure Functions and Web Jobs Tools
Azure Stream Analytics Tools for Visual Studio   2.6.5000.0
Microsoft Azure Stream Analytics Tools for Visual Studio
C# Tools   4.7.0-3.23416.8+43b0b05cc4f492fd5de00f6f6717409091df8daa
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Extensibility Message Bus   1.4.34 (main@d5ab18b)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.
FireGiant HeatWave   <IP_ADDRESS>
Visual Studio tooling for WiX projects.  For more information about HeatWave, visit http://www.firegiant.com.
Microsoft Azure Hive Query Language Service   2.6.5000.0
Language service for Hive query
Microsoft Azure Stream Analytics Language Service   2.6.5000.0
Language service for Azure Stream Analytics
Microsoft Azure Tools for Visual Studio   2.9
Support for Azure Cloud Services projects
Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Mono Debugging for Visual Studio   17.7.27 (547ea6f)
Support for debugging Mono processes with Visual Studio.
NuGet Package Manager   6.7.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
Office Developer Tools for Visual Studio   17.6.34022.00
Microsoft Office Developer Tools for Visual Studio
Razor (ASP.NET Core)   <IP_ADDRESS>3001+0ab18affdf2a37647768d0e25f5f021bee6257a1
Provides languages services for ASP.NET Core Razor.
SQL Server Data Tools   <IP_ADDRESS>
Microsoft SQL Server Data Tools
ToolWindowHostedEditor   1.0
Hosting json editor into a tool window
TypeScript Tools   17.0.20829.2001
TypeScript Tools for Microsoft Visual Studio
Visual Basic Tools   4.7.0-3.23416.8+43b0b05cc4f492fd5de00f6f6717409091df8daa
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools   17.7.0-beta.23314.10+e612cf93b989503c89e3a5830090062b7ab5e143
Microsoft Visual F# Tools
Visual Studio IntelliCode   2.2
AI-assisted development for Visual Studio.
VisualStudio.DeviceLog   1.0
Information about my package
VisualStudio.Mac   1.0
Mac Extension for Visual Studio
VSPackage Extension   1.0
VSPackage Visual Studio Extension Detailed Info
WiX Toolset Visual Studio Extension   <IP_ADDRESS>
WiX Toolset Visual Studio Extension version <IP_ADDRESS>
Copyright (c) .NET Foundation and contributors. All rights reserved.
Workflow Manager Tools 1.0   1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.
Xamarin   <IP_ADDRESS> (d17-7@133ddef)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin Designer   <IP_ADDRESS> (remotes/origin/d17-7@796d191def)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.
Xamarin Templates   17.7.21 (150ec9f)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.
Xamarin.Android SDK   <IP_ADDRESS> (d17-5/a8a26c7)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: d9a6e87
Java.Interop: xamarin/java.interop/d17-5@149d70fe
SQLite: xamarin/sqlite/3.40.1@68c69d8
Xamarin.Android Tools: xamarin/xamarin-android-tools/d17-5@ca1552d
Xamarin.iOS and Xamarin.Mac SDK   <IP_ADDRESS> (8c3876d5e)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

Can't reproduce, at least not when updating to .NET 8 which should be here very soon, so going to assume this is fixed on the .NET MAUI side, thanks!


nixos/grub: use the correct ZFS version

Description of changes
When config.boot.zfs.enableUnstable is set to true, grub was built with the zfs package even though the rest of the system uses the zfsUnstable package.
The effect of this can only be seen when zfs and zfsUnstable actually differ (which is not currently the case), for example when overriding one of them locally.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1301

Do we have any ZFS+GRUB test?

I don't think so.

@Luflosi I would advise to write a GRUB+ZFS if you have some time, it would be very helpful to get this merged.

GRUB reads ZFS pools with its own read-only filesystem driver, see 1 and 2.  Any ZFS filesystem must be created with option compatibility=grub2 to be used with GRUB, see 3.  Therefore building GRUB against zfsUnstable would not affect GRUB support for ZFS in any way.

I'm adding a test in #223412.

@RaitoBezarius the test has been added. Could you please take a look?

Thanks!


The npm-publish started failing

Hi @Scotley,
the publishing jobs started to fail with the following error..
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/vuex-orm-decorators - Not found
npm ERR! 404
npm ERR! 404<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Probably you need to re authenticate the package on npm and re run the following job please to make sure is working again.

Note: The workflow file is 100% correct, is not there the problem
I have already published 4 releases with this workflow

Please take care of it @Scotley :)

Hi @TiBianMod,
Should be working again now.  NPM decided to jump all my access tokens yesterday, which sucked as I have a tonne of private repositories used in CI pipelines which needed updating.  It should work now as I have setup a new token for this repository.
As I no longer use this repository, don't have time to maintain (and you are doing a stellar job) I am happy to hand ownership of this repository to you.

Hi @TiBianMod,
Should be working again now.  NPM decided to jump all my access tokens yesterday, which sucked as I have a tonne of private repositories used in CI pipelines which needed updating.  It should work now as I have setup a new token for this repository.
As I no longer use this repository, don't have time to maintain (and you are doing a stellar job) I am happy to hand ownership of this repository to you.

Thank you very much @Scotley for the ownership and the quick reply.

All jobs working again, nice.

I hope you doing well :)

Thank you very much @Scotley for the ownership and the quick reply.

All jobs working again, nice.

I hope you doing well :)

Now about the ownership, if you want you can transferred to me (thank you a lot for the trust), personally I will continue maintaining this repo how much I can.

Now about the ownership, if you want you can transferred to me (thank you a lot for the trust), personally I will continue maintaining this repo how much I can.

Happy to transfer it, I can see you are transforming the code in a positive way.  Do you have a nodejs account that I can transfer the package across to?

Happy to transfer it, I can see you are transforming the code in a positive way.  Do you have a nodejs account that I can transfer the package across to?

I have this account on npm
https://www.npmjs.com/~tibian
and email<EMAIL_ADDRESS>Thank you very much @Scotley :)

I have this account on npm
https://www.npmjs.com/~tibian
and email<EMAIL_ADDRESS>Thank you very much @Scotley :)

The big transformation is happening in the next branch with almost 100% unit test :)

The big transformation is happening in the next branch with almost 100% unit test :)

Can i change the references about you Name ?

Can i change the references about you Name ?

Cool, I have added you as a maintainer and removed myself on npmjs.  No need to reference to me at all, feel free to update anything as you see fit!
Note that you will probably need to change the secret in this Github repository to be able to continue publishing.  Looking forward to seeing where you take the project - I was never able to afford the time to take it to where I wanted to.
Fully unit tested will be awesome, nicely done.  In the future if you need a hand with anything on it feel free to reach out, always happy to help if I'm able :)

Cool, I have added you as a maintainer and removed myself on npmjs.  No need to reference to me at all, feel free to update anything as you see fit!
Note that you will probably need to change the secret in this Github repository to be able to continue publishing.  Looking forward to seeing where you take the project - I was never able to afford the time to take it to where I wanted to.
Fully unit tested will be awesome, nicely done.  In the future if you need a hand with anything on it feel free to reach out, always happy to help if I'm able :)

Thank you very much again @Scotley, I will do my best.
I hope you doing well and if I need something I will contact you, (you can do the same and contact me if you need something)

Thank you very much again @Scotley, I will do my best.
I hope you doing well and if I need something I will contact you, (you can do the same and contact me if you need something)


Force minimum dates to affect the current month

This ensures that when a start date is selected but there are fewer days than the minimum days left in the month, we set the initial date to be at the minimum date.
Screenshots:
Before -
After -

Can you include a screenshot of before and after so that we can better understand the problem?

Also, I'm trying to get this change pushed out ASAP: https://github.com/airbnb/react-dates/pull/70 Do you think that would be able to address your problem without adding knowledge of startDate and min nights to the DayPicker component?

I'll absolutely add a screenshot.
startDate as far as I can derive must be required. Because I have to know how far out from the start date I would need to scroll the initial month so-as to not see the right month as empty. This way the user does not have to guess how far they must scroll to find an acceptable day.

Yeah, I think I understand the concern. Plus the initialVisibleMonth PR is mostly targeted at setting the month when the DayPicker is first opened.
I think my biggest concern about this PR right now is that there's no slick animation for this kind of transition so it would just flash to that month. I def see the need for this but am unsure if this is the best way to implement it.
It's starting to seem like maybe the DayPicker month should be controlled in general. :/ Hmm.

Can we expose the function that does the animation and have initial month
be controlled by props?
On Fri, Sep 30, 2016 at 9:48 AM Maja Wichrowska<EMAIL_ADDRESS>wrote:

Yeah, I think I understand the concern. Plus the initialVisibleMonth PR
is mostly targeted at setting the month when the DayPicker is first
opened.
I think my biggest concern about this PR right now is that there's no
slick animation for this kind of transition so it would just flash to that
month. I def see the need for this but am unsure if this is the best way to
implement it.
It's starting to seem like maybe the DayPicker month should be controlled
in general. :/ Hmm.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-dates/pull/103#issuecomment-250794556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-n88_itvn2oxWsGgU3tq7O7zXTZ1bcks5qvT1EgaJpZM4KKtnN
.

Also, I can make this functionality optional until the animation can be
exposed, if that works. I agree that the UX isn't ideal.
On Fri, Sep 30, 2016 at 10:17 AM Ben Bayard<EMAIL_ADDRESS>wrote:

Can we expose the function that does the animation and have initial month
be controlled by props?
On Fri, Sep 30, 2016 at 9:48 AM Maja Wichrowska<EMAIL_ADDRESS>wrote:

Yeah, I think I understand the concern. Plus the initialVisibleMonth PR
is mostly targeted at setting the month when the DayPicker is first
opened.
I think my biggest concern about this PR right now is that there's no
slick animation for this kind of transition so it would just flash to that
month. I def see the need for this but am unsure if this is the best way to
implement it.
It's starting to seem like maybe the DayPicker month should be controlled
in general. :/ Hmm.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-dates/pull/103#issuecomment-250794556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-n88_itvn2oxWsGgU3tq7O7zXTZ1bcks5qvT1EgaJpZM4KKtnN
.

Can we expose the function that does the animation and have initial month
be controlled by props? Also, I can make this functionality optional until the animation can be
exposed, if that works. I agree that the UX isn't ideal.
The biggest issue currently is that the UX for minimumNights of 1 "month" makes it look like the dates are selectable and that there is nothing to select. The animation currently does not have an API users can access and since this is controlled by a prop it further complicates the situation.
Perhaps the best way to handle it might be to say something like:
onDatesChange(start, end) {
  const {minimumNights, onDayClick} = this.props;
  if (minimumNightsExceedsCurrentlyVisibleMonths) {
    this.refs.calendarMonthGrid.transitionToDay(start + minimumNights);
  }
  onDayClick && onDayClick(start, end);
}

This requires a few things I do not like. Is there another way to hook in to the animation? Perhaps through firstVisibleMonthIndex?

@majapw I found a way to do this using the existing animation API. If you like how this works and the general logic, I'll add some tests and make changes per your recommendations.

Unfortunately this PR's fork was deleted, so the PR can never be landed.
@benbayard if you're still interested in landing this fix, a new PR would be appreciated.


Tensorflow + metaflow = Can't pickle datasets/models

I'm trying to put some word embeddings exercise into metaflow to avoid running training or downloading/transforming the datasets every time I run the scripts
Specifically:
2020-02-16 13:04:40.669 [1581858157185440/get_dataset_batches/2 (pid 21)] tensorflow.python.framework.errors_impl.InternalError: Tensorflow type 21 not convertible to numpy dtype
Metaflow's checkpointing is the perfect answer for this instead of me manually coding all the saving/loading logic
However I can't seem to checkpoint a lot of common tensorflow steps with metaflow, I'm aware you use tensorflow internally, I assume together with metaflow, do you have any solution for this kind of problems?
I've produced a repository where the whole issue is documented and reproducible in a dockerised manner, you can check it out here

@sandman21dan we rely on the model serialization methods provided by each library, e.g. model.save() in Keras. You can then store bytes produced by the native method as a Metaflow artifact. It is easy to package this functionality, which is just a few lines of code, as a utility library

Is this something like tempfile.SpooledTemporaryFile or is there a Metaflow method/util to go from file into the self scope of a step?

Something like this
# serialize model
self.model = model.to_json()
self.weights = model.get_weights()

# deserialize model
model = model_from_json(self.model)
model.set_weights(self.weights)

You could also do the following.
Save model during training locally and serialize as Metaflow artifact:
model.save('model.h5')
with open(script_path('model.h5'), 'rb') as fh:
    self.buffered_model = BytesIO(fh.read())

Load model from a Metaflow artifact, save to local h5 model file and load for TF e.g.:
self.training_run = Flow('TrainKeras').latest_run
loaded_model = self.training_run.data.buffered_model
with open('loaded_model.h5', 'wb') as f:
    shutil.copyfileobj(loaded_model, f)
model = tf.keras.models.load_model('loaded_model.h5')

@sandman21dan : do the answers provided solve your problem. If so, please let me know so I can close the issue.

They seem to do, haven't had the time to try them individually, and nothing specific about the tf.data.Dataset type which also can't be Pickled

@sandman21dan Please reopen this issue if you have more to add.


Updating 50-org to conform to the Updated Data schemas

Updating the 50-a Scraper to use the new schemas outlined in the NPDI API Documentation.
Additionally:

Adds a testing mode (scrapes only 10 random items rather than the entire site)
Adds user agent data to identify the scrapper as coming from the National Police Data Coalition.

Much of this will be covered by the CSV files that 50-a provides. But, I'm adding this PR for 2 reasons:

As a reference for using the Pydantic models to create the JSONL data
Just for myself to have a better understanding of Scrapy
Some data doesn't get included in the CSV files. For example, CSV only includes an officer's current unit assignment while the page has their previous unit assignments as well.


samples: build error in sample.llext.shell: implicit declaration of strnlen

Describe the bug
Starting with 9dcbfa8bf23fb73a0d4ab14f93e1f14fb07022c8, the following build failure occurs
/home/jonas/Workspace/zephyr_sandbox_2/zephyr/subsys/llext/shell.c: In function 'cmd_llext_load_hex':
/home/jonas/Workspace/zephyr_sandbox_2/zephyr/subsys/llext/shell.c:124:26: error: implicit declaration of function 'strnlen'; did you mean 'strlen'? [-Werror=implicit-function-declaration]
  124 |         size_t hex_len = strnlen(argv[2], CONFIG_LLEXT_SHELL_MAX_SIZE*2+1);
      |                          ^~~~~~~
      |                          strlen

To Reproduce
Steps to reproduce the behavior:
west twister --build-only --inline-logs  --platform teensy41 -s samples/subsys/llext/shell_loader/sample.llext.shell -v

Expected behavior
No build error
Impact
Caused CI failure for OOT board repo, which builds samples against custom board nightly: https://github.com/ottojo/otterpill_zephyr/actions/runs/7674769452/job/20919951824
Environment:

OS: Linux 6.6.12-1-MANJARO
Toolchain: zephyr sdk 0.16.1
Bisected first bad commit: 9dcbfa8bf23fb73a0d4ab14f93e1f14fb07022c8

I see there is discussion around some posix stuff already, but i'm not sure if this is the same problem, as this seems to occur with default configuration?

Thank you for the report, will take a look

It seems the outdated SDK seems to be the culprit here... Locally i had SDK 16.1 installed, updating to the latest 16.4 solved the issue locally, so it seems like the problem was indeed fixed between SDK releases 16.1 and 16.2.
Thanks for the suggestion, and sorry for the false alarm :smile:


Fix #57

A freshly created promise can now be injected into its wait function for simpler creation / resolution:
use GuzzleHttp\Promise\Promise;
use GuzzleHttp\Promise\PromiseInterface;

$promise = new Promise(function (PromiseInterface $promise) {
    $promise->resolve('The promise has been resolved');
});

@mtdowling Hi, can you have a look at this PR and #63 ?
Thanks,
Ben

Personally, I don't think this should be merged, as this is potentially a breaking change* and I don't think it brings any value.
*Consider the following example:
new Promise(function (\Foo $bar = null) {
    // wait logic
});

Although this example is quite contrived, I really don't think this PR justifies the risk of breaking things.

@joshdifabio Currently, true is injected into $wfn, already breaking your constructor.
cf https://github.com/guzzle/promises/blob/master/src/Promise.php#L246
This value is purely arbitrary and has absolutely no semantics.

@joshdifabio Currently, true is injected into $wfn, already breaking your constructor.

I wasn't aware of that, but this only makes it more likely that your PR will break existing code.

This will indeed, for developers who expect true to be passed as the only argument into the wait function, for no reason.
Actually it won't break existing code (the library runs exactly as before and all the previous unit tests pass successfully), it could only break some use cases which relies on that argument, which, I repeat, is currently unique, and without any semantics.
I personnaly don't see any real world use case or a true reason to code this:
$wfn = function($value) {
    if (true !== $value) {
        throw new \InvalidArgumentException("Why guzzlehttp/promises does not send 'true' anymore?");
    }
}

But it's indeed a BC break (that's sometimes necessary) and as I said, it would need a bump in the version number.

... which, I repeat, is currently unique, and without any semantics.

Not entirely, because elsewhere with this library that parameter is bool $unwrap.

But it's indeed a BC break (that's sometimes necessary) and as I said, it would need a bump in the version number.

Do you think this change is worthy of a BC break?

Hi @joshdifabio,
AFAIK $unwrap is transfered through different wait() methods (implementing GuzzleHttp\Promise\PromiseInterface::wait()), but not within user closures (which are called within these wait()). Otherwise, it should be documented.
Even if this was the case (or tell me where I can find such code?), I haven't modified any unit test, I only added one, and all tests run successfully.
I have described the need in issue #57 where the original way to create a stack of promises causes issues from a DX point of view (need to explicitely define each $promise variable with a different name - impossible to handle within a loop).
I understand your fear of breaking things for a use case you may not evaluate the importance (maybe you never faced that kind of issue and you might think, from your point of view, that this enhancement is useless), and I know this library is widely used, which automatically increases the risk, but here's why I think it's worth it:

It is an enhancement of the library, allowing more use cases, and provides a better DX
It solves an actual problem
There is no evidence of a regression within the internal code
I have ran the latest guzzlehttp/guzzle unit tests with this change, and they also passed successfully.

Maybe, if you provide some more information about the $unwrap mechanism, we could check if this behaviour is fully tested (have we missed testing something?) and if no regression would occur?
Thank you for your time,
Ben

Not entirely, because elsewhere within this library wait functions define a parameter bool $unwrap.

This was my concern as well. Granted it's been a while since I've dived very deep in the code here, but I couldn't find how the unwrap method accepting true or not would affect the wait function. The semantics of the wait function were never defined in the docs. I honestly don't remember why I passed true to the wait function when invoking it, and I don't see anywhere else where invoking it would pass false. I don't see where it's done in this library, but I guess it's possible you could pass in the wait function of another promise into the wait function of a promise. That would be weird though considering waiting on dependent promises is currently handled through an explicitly managed list of promises.

When you wait on a promise, it waits if the promise is still pending: https://github.com/guzzle/promises/blob/master/src/Promise.php#L62
If there's a waitFn on the promise, then it invokes it (otherwise it invokes the waitList chain for chained promises): https://github.com/guzzle/promises/blob/master/src/Promise.php#L222
invokeWaitFn is called and it called the wait function of the promise. The interesting thing here is that regardless of the $unwrap argument that was passed to the original wait method of the promise that started this process, the waitFn is always invoked with true as an argument: https://github.com/guzzle/promises/blob/master/src/Promise.php#L246

Another thing to consider is that an instance of a promise will evaluate to true when using ==. The only users this would break, from what I can tell, are users expecting literal true with ===. The only use case I can see where this might happen is someone passing the wait function of a promise into another promise (something like [$promise, 'wait']). Considering that the wait method of promise uses a truthy check rather than a literal true check, it shouldn't be affected. This is the case for FulfilledPromise and RejectedPromise as well.
So that limits the blast radius of this change to people who implement PromiseInterface and are passing a reference to that implementation's wait method to another promise's wait function and are using a literal true check on $unwrap when deciding whether or not to unwrap; or people who wrote a wait function that expects a literal true to be passed to their methods.

The only users this would break, from what I can tell, are users expecting literal true with ===.

Or if they have used a bool typehint on their wait function, in which case there would be a TypeError.

So... ?

Hi there,
Is there any chance to see this merged in the near future?
Thank you,
Ben

Would love to see this merged. Would clean up promises quite a bit for me.

Hi @aequasi,
You can create your own promise factory with a simple function, that's what I finally did:
use GuzzleHttp\Promise\Promise;
use GuzzleHttp\Promise\PromiseInterface;
use GuzzleHttp\Promise\RejectedPromise;

/**
 * @param callable $callable
 * @return PromiseInterface
 * @throws \InvalidArgumentException
 */
function async(callable $callable): PromiseInterface
{
    try {
        $promise = new Promise(function () use ($callable, &$promise) {
            $promise->resolve($callable());
        });
        return $promise;
    } catch (\Throwable $e) {
        return new RejectedPromise($e);
    }
}

Usage:
$promise = async(function() {
    return 'foo';
});

echo $promise->wait(); // foo

Closing as I think a helper function as explained in https://github.com/guzzle/promises/pull/62#issuecomment-394063606 is the better solution for the reason given in https://github.com/guzzle/promises/issues/57#issuecomment-584958457
Feel free to create a PR to add such function to the library. That would seem fine to me.


[Error] LanguageTranslator.processText Error 3

Environment: iPhone X Simulator
text that I want to translate:
Google LLCl is an American multinational technology company that specializes in Internet-related services and products, which include
online advertising technologies, search engine, cloud computing, software, and hardware. It is considered one of the Big Four technology
companies, alongside Amazon, Apple and Facebook (6|171
Google was founded in 1998 by Larry Page and Sergey Brin while they were Ph.D. students at Stanford University in California. Together
they own about 14 percent of its shares and control 56 percent of the stockholder voting power through supervoting stock. They
incorporated Google as a privately held company on September 4, 1998. An initial public offering (IPO) took place on August 19, 2004,
and Google moved to its headquarters in Mountain View, California, nicknamed the Googleplex. In August 2015, Google announced plans
to reorganize its various interests as a conglomerate called Alphabet Inc. Google is Alphabet's leading subsidiary and will continue to be.
Error:
Unhandled Exception: PlatformException(Error 3, com.firebase.ml, Asked to download an unsupported language.)

[VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: PlatformException(Error 3, com.firebase.ml, Asked to download an unsupported language.)
#0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:564:7)
#1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:302:33)

#2      LanguageTranslator.processText (package:firebase_mlkit_language/src/language_translator.dart:31:10)

#3      FirebaseVisionHelper.translate (package:tech_talk_ml_kit/firebase_vision_helper.dart:54:41)

#4      LanguageTranslatorPageState.readText (package:tech_talk_ml_kit/language_translator_page.dart:47:58)

#5      _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:511:14)
#6      _InkResponseState.build. (package:flutter/src/material/ink_well.dart:566:30)

[VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: PlatformException(Error 3, com.firebase.ml, Asked to download an unsupported language.)
#0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:564:7)
#1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:302:33)

#2      LanguageTranslator.processText (package:firebase_mlkit_language/src/language_translator.dart:31:10)

#3      FirebaseVisionHelper.translate (package:tech_talk_ml_kit/firebase_vision_helper.dart:48:41)

#4      LanguageTranslatorPageState.readText (package:tech_talk_ml_kit/language_translator_page.dart:45:58)

#5      _InkResponseState._handleTap (package:flutter/src/material/ink_well.dart:511:14)
#6      _InkResponseState.build. (package:flutter/src/material/ink_well.dart:566:30)
#7      GestureRecognizer.invokeCallback (package:flutter/src/ge<…>

Code:
List<LanguageLabel> languages =
        await FirebaseLanguage.instance.languageIdentifier().processText(text);
    String fromLanguage = languages.first.toString();

    await FirebaseLanguage.instance.modelManager()
        .downloadModel(fromLanguage);
    await FirebaseLanguage.instance.modelManager()
        .downloadModel(SupportedLanguages.Spanish);

    final languageTranslator =  FirebaseLanguage.instance
        .languageTranslator(fromLanguage, SupportedLanguages.Spanish);
        return await languageTranslator.processText(text);

pubspec.yaml
version: 1.0.4

environment:
  sdk: ">=2.2.2 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  image_picker: ^0.6.0+2
  firebase_core:  ^0.4.0+1
  firebase_ml_vision: ^0.8.0+2
  firebase_mlkit_language: ^1.0.1

@juanagu you need to set your fromLanguage, since you're translating from English, set that to SupportedLanguages.English

Thanks! @rishab2113 I had an error on my code. I Replaced:
String fromLanguage = languages.first.toString();
To
String fromLanguage = languages.first.languageCode.toString();


--version is handled by the launcher

steps
$ which sbt
/Users/eugene/bin/sbt
$ sbt --version
sbt launcher version 0.13.6
$ which scalaxb
/Users/eugene/bin/scalaxb
$ scalaxb --version
sbt launcher version 0.13.6

problem
Launcher responding it own version
sbt launcher version 0.13.6

is not helpful.
expectation
Older launcher used to delegate --version to the underlying application.
I would like sbt --version to return the sbt version, and scalaxb --version to return the scalaxb version. This becomes more relevant as the sbt launcher stabilizes and is used by both sbt and conscript.
note
conscript calls foo --version when you install foo to force download of the necessary JARs.
As such, all conscripted applications are encouraged to implement --version.

Attached a PR on this. /review @jsuereth

There's a bunch of stackoverflow answers we'll have to update after this, but makes sense to me.


only run on PR merge

[title here]

Description 🗒

Examples 📸

Related Issues 🔗

 Expand for Help

Have questions about the review or deployment process? View our contributing docs
Need additional help and want to chat in real time? Join our community Discord

By submitting this pull request, you agree to our code of conduct

.deploy


Remove input pins from "Turn off all digital pins for safety at the end"

Does anyone have a problem with me excluding input pins from this line:
https://github.com/dattalab-6-cam/multicamera_acquisition/blob/main/microcontroller_firmware/trigger_io/trigger_io.ino#L407C1-L412C14
// Turn off all digital pins for safety at the end
for (int i = 0; i < NUM_DIGITAL_PINS; i++)
{
    pinMode(i, OUTPUT);
    digitalWrite(i, LOW);
}

The issue being that when you have a second device monitoring the same input, it only works if the cameras are rolling.
For me a Fed3 is simultaneously being listened to by the teensy, a raspberry pi, and a nidaq board, and this line is messing with that.

Makes sense to me. If it's an input pin we shouldn't force it to have one voltage or the other.


Add new formula: yage

YaGE, a.k.a. Yet another Graphics Engine, is a C/C++ Graphics Library based on cairo/GTK+ 3 for C/C++ learners.

Sorry for the late response.
We’re deprecating this repository and won’t accept new formulae. Please ask upstream for a stable release and/or consider maintaining the formula in a tap. Thanks!


[BUG] DnsResolverManagementClient.forwarding_rules.list iterator exception when pages are left

Package Name: azure-mgmt-privatedns
Package Version: 1.1.0
Operating System: MAC and linux
Python Version: 3.11

Describe the bug
Exception if rulesets count is greater 100 with ForwardingRulesOperations.list within iterator.
(not sure if the exception is also thrown if count is < 100. 100 is default top)
Example code:
from azure.mgmt.dnsresolver import DnsResolverManagementClient
from azure.identity import DefaultAzureCredential

client = DnsResolverManagementClient(credential=DefaultAzureCredential(), subscription_id=subscription_id)

res = client.forwarding_rules.list(
        resource_group_name=<resource_group_name>,
        dns_forwarding_ruleset_name=<ruleset_name>,
        # top = 10,
    )

for i in res:
  print(i.as_dict())

when reaching 100 (or last item within page with top parameter) there is an exception
ValueError('The value provided for the url part \'https://management.azure.com/subscriptions/****/resourceGroups/****/providers/Microsoft.Network/dnsForwardingRulesets/****/forwardingRules?$skipToken=[{"token":"****","range":{"min":"05C1DFFFFFFFFC","max":"FF"}}]&api-version=2022-07-01\' was incorrect, and resulted in an invalid url')

To Reproduce
Use the code sample above. Not sure if this happens if you have less then 100 rules (not tested)
Expected behavior
No exception
Additional context
Possibly somehow related to #29940 (but the mentioned workaround is not working in our case).
stack trace
KeyError: '"token"'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/site/wwwroot/svc_azure.py", line 130, in list_dns_ruleset_with_rules
    for i in az_res:
  File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/core/paging.py", line 123, in __next__
    return next(self._page_iterator)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/core/paging.py", line 75, in __next__
    self._response = self._get_next(self.continuation_token)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/mgmt/dnsresolver/operations/_forwarding_rules_operations.py", line 821, in get_next
    request = prepare_request(next_link)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/mgmt/dnsresolver/operations/_forwarding_rules_operations.py", line 809, in prepare_request
    request.url = self._client.format_url(request.url)  # type: ignore
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/core/pipeline/transport/_base.py", line 658, in format_url
    url = _format_url_section(url_template, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/core/pipeline/transport/_base.py", line 108, in _format_url_section
    raise ValueError(****

Thanks for the feedback, we’ll investigate asap.

@ChenxiJiang333 Please help on this issue.

got it

Hi @AndreasAugustin, I guess you're using the package azure-mgmt-dnsresolver with version 1.0.0, could you try update it to azure-mgmt-dnsresolver==1.1.0b1?

Hi @AndreasAugustin, I guess you're using the package azure-mgmt-dnsresolver with version 1.0.0, could you try update it to azure-mgmt-dnsresolver==1.1.0b1?

Hi @ChenxiJiang333 . Yes azure-mgmt-dnsresolver with version 1.0.0 (sorry had the wrong package name and version within the description -> changed).
Run some of my tests with version 1.1.0b1 -> the exception did not occur again and the list of results is also > 100.
Seems the version is fixing the bug (at least within my tests).
Thanks

@ChenxiJiang333 is there is not a new release available yet. Just a beta. For me this issue is not closed yet. When will the new release be available?

azure-mgmt-dnsresolver

The python SDK is generated by swagger definition and azure-mgmt-dnsresolver==1.1.0b1 has been released with latest api version. Since it's an old server, I'm not sure whether service team would launch a new api version and ask for the release of a new SDK version. I suggest you open an issue at https://github.com/Azure/azure-rest-api-specs/issues to get support from the service team.

Hi @AndreasAugustin , the python SDK is generated by swagger definition and azure-mgmt-dnsresolver==1.1.0b1 has been released with latest api version. Since it's an old server, I'm not sure whether service team would launch a new api version and ask for the release of a new SDK version. I suggest you open an issue at https://github.com/Azure/azure-rest-api-specs/issues to get support from the service team.

Hi @ChenxiJiang333 and thanks for the clarification. Created an issue as requested: https://github.com/Azure/azure-rest-api-specs/issues/30409


Plans for ARM release?

Hi
Is there any plans to release an M1 compatible version? The app is working fine using Rosetta 2 but wonder how long Rosetta 2 will be around.

+1

+1

Hi @sandrich @BenThrottle85 , there's no plans at the moment but if M1 platform improves and the usage increases, we could look at doing something. Our team is focused on delivering value on the blockchain and we prioritise what the majority of the user base sees; as the direction we want to go.

Hi @sandrich @BenThrottle85 , there's no plans at the moment but if M1 platform improves and the usage increases, we could look at doing something. Our team is focused on delivering value on the blockchain and we prioritise what the majority of the user base sees; as the direction we want to go.

Referencing for context: https://github.com/DeFiCh/app/issues/1030#issuecomment-905561464


MAJOR SECURITY VUNURIBILITES FOUND

Please do not download any versions of VirtualPass until these issues are fixed the site is currently vuenriable to cross scripting attacks among other cookie and page= related issues

regqrid exploit fixed

Fixed the file exiests bug in the admin portal

Fixed


org.wso2.carbon.mediation.transport.handlers.PassThroughNHttpGetProcessor cannot be found by synapse-nhttp-transport_2.1.7.wso2v143

Description
Hello!
I got next error when try to run EI version 6.6.0 :
[org.wso2.carbon.mediation.transport.handlers.PassThroughNHttpGetProcessor не может быть найден с помощью синапса-nhttp-transport_2.1.7.wso2v143](https://stackoverflow.com/questions/78062216/wso2-error-org-wso2-carbon-mediation-transport-handlers-passthroughnhttpgetproce)
As i can understand it happaned becuase there is some error in one of the config files, but i do not know in which one.
Can you to give me directions for looking for ?
Log.txt
This is config from my asix2.xml file :

I am shure that problem is in this part of logs - i do not know where i can fix this? The path to the synapse.xml has to be the same as for the Synapse home in the beginning of the row , e.g. : C:\PROGRA~1\WSO2\ENTERP~1\6683E8~1.0\.\.\repository/deployment/server/synapse-configs\default

Affected Component
Analytics
Version
6.6.0
Environment Details (with versions)
OS - Windows 10 10.0, amd64
Java version - 1.8.0_271
Java VM - Java HotSpot(TM) 64-Bit Server VM 25.271-b09,Oracle Corporation
Related Issues
No response
Suggested Labels
wso2-ei

Hi, everybody
After 3 days i resolved this problem - this is the link to answer
stackoverflow


MQ sink does not map headers from Kafka source

I have been told that an user have trouble with sourcing from Kafka and sinking to IBM MQ then headers are not mapped, and they want Kafka Key to be mapped as JMSCorrelationID as well.
I think they may have seen this example
https://github.com/apache/camel-kamelets/blob/main/kamelets/jms-ibm-mq-sink.kamelet.yaml
They are using Camel K and KameletBinding to setup the source and sink (no step in-between)

There is a generic MQ example here. Maybe it can be used to test and see
https://github.com/apache/camel-k-examples/tree/main/generic-examples/ibm-mq

I'll have a look

Using deserializeHeaders and setting it to true will work. This needs to be done also a kafka source not secured Kamelet


[Question]: SimpleDirectoryReader Problem Does not generate vector data

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Hello,
I have tried the sample code for using the SimpleDirectoryReader, however, i notice it doesn't work and throws ValueError message, i have tried on both Mac and Windows, and same issue has occured. I notice this with 0.10.20 version. Earlier version doesn't throw this kind of exception because i can see before that before the upgrade i did, i still see the vector data being generated.
Here's the sample code:
import os
from llama_index.core import VectorStoreIndex, SimpleDirectoryReader

documents = SimpleDirectoryReader("data").load_data()
index = VectorStoreIndex.from_documents(documents)
query_engine = index.as_query_engine()
response = query_engine.query("What did the author do growing up?")
print(response)

i tried debugging it by checking if i have correct permission and it seems that's not the issue because i can list the files in the data folder with the command below:
print("Current Working Directory:", os.getcwd())

# Attempt to list files in the "data" directory
try:
    print("Files in 'data' directory:", os.listdir("data"))
except FileNotFoundError:
    print("The 'data' directory was not found.")
except PermissionError:
    print("Permission denied when accessing the 'data' directory.")

The error message was:
Traceback (most recent call last):
  File "/Users/user/.pythonvenv/llamaindex-test/starter.py", line 7, in <module>
    documents = SimpleDirectoryReader("data").load_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/.pythonvenv/llamaindex-test/lib/python3.12/site-packages/llama_index/core/readers/file/base.py", line 215, in __init__
    self.input_files = self._add_files(self.input_dir)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/.pythonvenv/llamaindex-test/lib/python3.12/site-packages/llama_index/core/readers/file/base.py", line 297, in _add_files
    raise ValueError(f"No files found in {input_dir}.")
ValueError: No files found in data.

Can anyone help me figure out what could be the problem?

@rgaesspi do you have a folder named "data" ? Is that the correct path to the folder?

This error is only raised if no files are found at that path

i can confirm that i do have it. and permission are correct. which really confuses me what's going on.

import os
print(os.listdir("./data"))

from llama_index.core import SimpleDirectoryReader
documents = SimpleDirectoryReader("./data").load_data()
print(len(documents))

Does that code work?

import os
print(os.listdir("./data"))

from llama_index.core import SimpleDirectoryReader
documents = SimpleDirectoryReader("./data").load_data()
print(len(documents))

Does that code work?

No it didn't work. but it can print the data listed.
['.DS_Store', 'paul_graham_essay.txt', 'old_vector', 'raw']
Traceback (most recent call last):
  File "/Users/randolfarevalo/.pythonvenv/esspiai-api/test.py", line 5, in <module>
    documents = SimpleDirectoryReader("./data").load_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/.pythonvenv/esspiai-api/lib/python3.12/site-packages/llama_index/core/readers/file/base.py", line 215, in __init__
    self.input_files = self._add_files(self.input_dir)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/.pythonvenv/esspiai-api/lib/python3.12/site-packages/llama_index/core/readers/file/base.py", line 297, in _add_files
    raise ValueError(f"No files found in {input_dir}.")
ValueError: No files found in data.

this is tricky. hmm.

@rgaesspi , how comfortable are you with IDEs? Can I ask you to go create a breakpoint at this line:

set up a Run Configuration for your script, and then click this button:

This invokes a debugger. It will pause the program at the line with that little red dot. You can then step through the code and see all the variables available at each line. You can at which point the reader decided to ignore the .txt file you provided.
Let us know how it goes.

hey @tslmy thank you for the clue, i debug the code related to that and it seems to be skipping my files because of this code block

skip_because_hidden becomes TRUE. i set my parameters to this
documents = SimpleDirectoryReader("data", exclude_hidden=False).load_data()
and the error disappears. aggghhh. i least i figured out what's wrong.


add Dependency::directory to the PR payload

What are you trying to accomplish?
Dependabot needs to know the directory that each dependency was found in. After the introduction of multi-dependency updates, a single update could produce two PRs containing the same dependency but in different directories.
Currently the service refuses to create a PR with the same dependency. To fix this we first need this PR to send the directory in the dependency, and then the next step is to use that in the service to decide if a PR already exists with this dependency.
Anything you want to highlight for special attention from reviewers?
Nope, pretty straight forward really.

How will you know you've accomplished your goal?
In new PRs we should start seeing job definitions have the directory in the existing PR data.

Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

The smoke test failures are expected since this adds new data to the create_pull_request call. I am working on a PR for those.

I confirmed the directory data is now being sent and stored.
Since there are so many failures, I am opting to merge this with broken smoke tests and then fix the smokes next. It's likely I will miss something in the smoke tests and I can avoid having to put up multiple smoke test fix PRs.


Handle errors in chunk uploads

Description (required)
Fixes #3868

Tested this on prodDebug, Nexus 5X emulator API 28. Works well for me, however it might be noted that I have not encountered the original issue before. Will merge to master so that @nicolas-raoul can get it on alpha and see if it solves the issue for him. :)


fix some errors

Fix issue  #38

add comment for "multisport" day (line 976...)
fix code for "multisport" day (line 987...)
add time to filename (line 1017...)
fix error in one re.sub (line 1010)

Thanks for your contribution, dan1967! :)

little error.... delete file Huawei-TCX-Converter_muj.py - only test/work file...

Okay, I've removed it.


2.0 doesn't work on OnePlus 11 but 1.3 works.

Sorry... Deleting the template. But my report is so simple. As the title says, 2.0 doesn't work on OnePlus 11 running OOS 13, but older version 1.3 works fine.
Device is a CPH2451 On stock OOS 13.

This is nothing new. If you had a look at the other issue tickets (closed ones, too), you would have recognised.

I don't see anything about OnePlus 11 (CPH2541), I see a lot of Xiaomi devices and one about a OnePlus 6T, so I looked 👀


Allow main-h1-bg, logo-margin-top configuration

This PR adds a new item to _variables.scss to allow configuration of main-h1-bg, for example:
// ...
$main-bg: #F3F7F9 !default;
$main-h1-bg: #c97a7e !default; // this is some kind of red
$aside-notice-bg: #8fbcd4 !default;
// ...

now you get:

and for logo margins, if you change it slightly:
$logo-margin-top: 16px !default; // margin above logo
$logo-margin-bot: 0px !default; // margin below logo

you now have a much nicer spacing on the navbar:

Hi Robert! This is a cool addition, and while I'm sure many users would like to change this color, it's also the kind of change they can make directly without using variables? I'd rather not avoid adding too many variables for every possible styling change, since the end result of that is a variable for every CSS rule that we have. If you think this is a particular pain point, perhaps it could be documented in the wiki?


Adjust imports to match the now-recommended "import ops" style (section 1)

As part of canonical/operator#921, we're updating the docs to use the now-recommended "import ops" style, that is, instead of:
from ops.charm import CharmBase
from ops.main import main
class MyC(CharmBase):
    ...
if __name__ == "__main__":
    main(MyC)

We prefer people do:
import ops
class MyC(ops.CharmBase):
    ...
if __name__ == "__main__":
    ops.main(MyC)

The docs have been updated (as part of #921), so ideally the linked repo would be as well. I'll create a PR for each section of the tutorial - this is for #1 ("Create minimal charm").
This includes a drive-by version bump to isort, because the current one's dependencies break pre-commit.  See PyCQA/isort:#2079 for details.

Consolidating.


Pass a single lock token to the service instead of an array

Fixes #20483
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

My local tests failed with the service rejecting the non array version. It seems to be related only for when you receive a message, example
https://github.com/Azure/azure-sdk-for-net/blob/5ccae4bbba4507d5151501423a75977937276807/sdk/servicebus/Azure.Messaging.ServiceBus/src/Amqp/AmqpReceiver.cs#L1268-L1272


patchelf: Fails on static executables: cannot find section .interp

From @sjackman on March 29, 2016 22:53
https://travis-ci.org/Linuxbrew/linuxbrew/builds/119350327#L2890
/home/travis/build/Linuxbrew/linuxbrew/Cellar/patchelf/0.9/bin/patchelf --set-rpath @@HOMEBREW_PREFIX@@/lib --set-interpreter /lib64/ld-linux-x86-64.so.2 /home/travis/build/Linuxbrew/linuxbrew/Cellar/afl-fuzz/2.09b/share/afl/testcases/others/elf/small_exec.elf
cannot find section .interp
Error: undefined method `write' for nil:NilClass

Copied from original issue: Linuxbrew/linuxbrew#1005

That's the error message that patchelf gives when it attempts to relocate a static executable. This bug definitely needs to be fixed. It could be fixed in patchelf to make this a warning rather than an error. That's probably the simpler fix. The alternative is that Linuxbrew could check whether the ELF is dynamic or static, and skip patchelf for static executables. The problem here is that I haven't found an easy way to distinguish dynamic from dynamic. The easiest way would be to call out to file.

There was a similar problem with Alpine binaries IIRC. Has this been fixed somehow?

No, it has not been fixed. The possible solutions are:

Fix patchelf to make the above error a warning rather than an error
Use file to skip static executables
Use ruby-elf gem to skip static executables

I'm inclined for solution 1. Your thoughts?

I was avoiding file because it's an external dependency that may not be available. ruby-elf would have to vendored in.

Counting on file means we either a) depend on it being available or b) drag in a dependency on homebrew/dupes/file-formula. 3 is probably better than 2, if only for language consistency.
@sjackman, are you still experiencing this issue? If so, then it sounds like we might be best off skipping static executables.

Yep, this issue is current, and we need to skip static executables. How though? 1 or 3?

Sorry, I wasn't clear. By that, I meant we probably shouldn't be modifying patchelf. Rather, we should ensure that any static executable doesn't get that far, which would imply option 2 or 3.
I'm more inclined to use patchelf to handle dynamic executables and treat passing static executables to it as undefined behaviour.
Strictly my opinion, I emphasize. Maybe we should defer to the NixOS developers on what they do about static executables?

I didn't click on the link. My fault. I haven't experienced patchelf segfaulting recently as in https://github.com/NixOS/patchelf/issues/78. This issue may be fixed. I think we get the above error message now. I just thought of a really simple fix. If patchelf fails, check the error message. If it's exactly cannot find section .interp, we disregard the error. Sound good?
I've asked the NixOS developers in https://github.com/NixOS/patchelf/issues/78 if they would consider adding an option to make the above error a warning rather than an error.

@DoomHammer Piotr, do you have a fix for patchelf failing on static executables?

Aye, https://github.com/Linuxbrew/homebrew-core/pull/352

I believe #352 fixes the error cannot find section, which affects Go executables, but I don't believe it fixes cannot find section .interp, which affects static executables. Can you confirm?

You are right, this was a different issue. ruby-elf might be the way to go, but consider that file is already being used and causing silent failures when unavailable (Debian Sid casus). Fixing this upstream should be the priority, I think?

Now that file is an upstream dependency of Homebrew (it wasn't before) to determine whether a file is a text file or a binary file, should we also use file to determine if an ELF executable is dynamic or static? I don't really see a downside. file is effectively already a dependency of Linuxbrew now.

Agreed, resources such as file shouldn't go to waste ;)

Great. Agreed. That should fix the cannot find section .interp and cannot find section .dynamic issues. Would you like to take a stab at using file to skip static ELF files?

Compiling on a CentOS 5 machine, I ran
brew install --build-bottle --with-static --cc=gcc-4.4 patchelf
brew bottle --rb patchelf

It would be nice to find a recipe that we can run on Ubuntu 14 that builds a working bottle for CentOS 5.

I'll take it.

Found a recipe for building on Ubuntu 14:

install glibc
remove patchelf
install patchelf --with-static
bottle patchelf

PR #75 uses file to test whether an executable is static and skips relocating the executable with patchelf if so.


Possible to extent the .attribute access?

Is it possible to extend the the dot notation to support other types of variables in addition to POJO and Map.
In my use case the variables are vert.x JsonObject and JsonArray, which use getValue(..) instead of get(..).
As far as I can tell the supported variable types are hardcoded in GetAttributeExpression and can not be extended

Looking at the docs for those objects, they have a getter to expose the underlying map/list so you should be able to do something like jsonObject.map['property'] or jsonArray.list[index] to retrieve your property.
An alternative would be to write a pebble filter which takes the property name and calls the getValue method on the input object

I did an pull request to make it extendable .. https://github.com/PebbleTemplates/pebble/pull/280

I have merged the pull request #281 in branch v3. I think that we will release it only on v3 since I will use this PR to remove the DynamicAttributeProvider which was causing some performance issues


Global Placement Help Issue

In replace.tcl please add \ at the end of first line. Is it also possible to add more descriptive help inside the openroad executable?

86002325 cleanup replace cmd arg doc
adds the \ so help works correctly, added the other args and moved the (lame) doc from doc/replace/README to the top level README.md

86002325 cleanup replace cmd arg doc
adds the \ so help works correctly, added the other args and moved the (lame) doc from doc/replace/README to the top level README.md


Removed the unnecessary NeonMacDemo scheme

This solves #17.

Perfect, thanks for doing this!

No problem :)

@amitai-hoze  good job!

Still getting the following:
*** xcodebuild output can be found in /var/folders/98/36hndq_926z_75201r95qvkw0000gn/T/carthage-xcodebuild.YbAJIp.log
A shell task failed with exit code 66:
xcodebuild: error: Scheme NeonMacDemo is not currently configured for the build action.

Carthage file looks like this: github "mamaral/Neon" "master"


committed to emsl_project_identifiers

@brynnz22 can you please add a description?

#927

@turbomam I added a description. Also, regarding your other todos, @lamccue mentioned that currently, the identifier is always a 5 digit integer.  We can't guarantee that it will not change...we have no control over that. But to her knowledge, there is no plan make any changes and we can expect 5 digit integers for the foreseeable future.

Thanks @brynnz22. I am going to merge this, but I hope we can elaborate on the description to make it more informative


Hoe settings - Replant Crops | No durability usage

Timings link
No need for timings
Expected behavior
I expected to make my hoe lose durability when harvesting fully grown crop.
Observed/Actual behavior
My hoe didn't lose any durability when I harvested fully grown crop.
Steps/models to reproduce

Enable: world-settings.default.tools.hoe.replant-crops: true
Plant a crop of your choice.
Wait (or use bone meal) to make it fully grown.
Use hoe and left click the fully grown crop. It will replant automatically and drop items on the ground.
Voilá no damage to hoe.

Purpur version
[03:00:18 INFO]: This server is running Purpur version git-Purpur-1474 (MC: 1.18.1) (Implementing API version 1.18.1-R0.1-SNAPSHOT) (Git: 1c9c6b9 on HEAD)
[03:00:18 INFO]: You are running the latest version
[03:00:18 INFO]: Previous version: git-Purpur-1453 (MC: 1.18.1)
Agreements

[X] I am running the latest version of Purpur available from https://purpurmc.org/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] My version of Minecraft is supported by Purpur.

Other
I'm honestly not sure if this is working as intended. Maybe it was meant to work that way. What about making it an option in config to actually damage the hoe when harvesting crops that way?

Crops have a strength of 0, so they do not damage durability. This is a vanilla thing (try it on single player if you don't believe me).
I originally had the same thought about it, and was honestly surprised to find out about this.

Crops have a strength of 0, so they do not damage durability. This is a vanilla thing (try it on single player if you don't believe me).
I originally had the same thought about it, and was honestly surprised to find out about this.

Can you add the durability as a config thing? Plugins such as sickle effect durability as a added thing. Any way of treating it with a configurable dmg value?


⚠ Payment API has degraded performance

In 4d8c5b5, Payment API ($PAYMENT_API_URL) experienced degraded performance:

HTTP code: 504
Response time: 29609 ms

Resolved: Payment API performance has improved in e411075.


updated Style.css to look more interactive

updated button-group style to look  more interactive on page

Hi @yashjain1974
Thanks for contributing.
As your PR is accepted for the Hacktoberfest so can you please fill this form to become eligible for LoginRadius cool swags. :)
Thanks & Regards
Indrasen

Hi @yashjain1974,
Thanks for bringing this to our notice and we appreciate your valuable feedback on this.
As of now, we are not considering this design enhancement request into SDK as we have a specific design template for all SDK demos.
Please let me know if you see any other areas of improvement.
Regards
Indrasen


Support System Struct Serialiaztion (CGRext, CGPoint, etc)

My workaround:
For example: CGAffineTransform
extension JSONEncoder {
    func encode(value: CGAffineTransform, key: String) {
        object[key] = NSValue(CGAffineTransform: value)
    }
}

extension JSONDecoder {
    func decode(key: String) throws -> CGAffineTransform {
        guard let value = get(key) else {
            throw JSONDecodableError.MissingTypeError(key: key)
        }
        guard let compatible = value as? NSValue else {
            throw JSONDecodableError.IncompatibleTypeError(key: key, elementType: value.dynamicType, expectedType: NSValue.self)
        }
        guard let type = String.fromCString(compatible.objCType) where type.containsString("CGAffineTransform") else {
            throw JSONDecodableError.IncompatibleTypeError(key: key, elementType: value.dynamicType, expectedType: CGAffineTransform.self)
        }
        return compatible.CGAffineTransformValue()
    }
}

But the object is internal and get() is private, So I have to change the source code.Would you consider add these pattern in the source code? I can make a pull request. But I think maybe there is a more elegant solution.

Any reason why using a JSONTransformer isn't an option?

public func decode<EncodedType, DecodedType>(key: String, transformer: JSONTransformer<EncodedType, DecodedType>) throws -> DecodedType {
        guard let value = get(key) else {
            throw JSONDecodableError.MissingTypeError(key: key)
        }
        guard let actual = value as? EncodedType else {
            throw JSONDecodableError.IncompatibleTypeError(key: key, elementType: value.dynamicType, expectedType: EncodedType.self)
        }
        guard let result = transformer.decoding(actual) else {
            throw JSONDecodableError.TransformerFailedError(key: key)
        }
        return result
    }

this line:
        guard let actual = value as? EncodedType

The problem is CGAffineTransform needs to be boxed in NSValue.

I'm not sure I'm understanding this correctly. Is your stored property of type CGAffineTransform and the JSON a string?
let transformer = JSONTransformer<String, CGAffineTransform>(
  decoding: {CGAffineTransformFromString($0)},
  encoding: {NSStringFromCGAffineTransform($0)})

extension JSONDecoder {
  public func decode(key: String) throws -> CGAffineTransform {
    return try decode(key, transformer: transformer)
  }
}

The struct contains a property whose type is CGAffineTransform.  So it need to be encoded as a NSValue and decoded as CGAffineTransform. It's not from the JSON, but I want to encode and decode it. Thank you.

I reckon you can create a similar JSONTransformer<NSValue, CGAffineTransform>

But the original type is CGAffineTransform, may be I can make it as a computed property and define a new property as NSValue. But it will make a lot of bloated code and hard to maintain. Thanks.

I think your implementation here seems to apply mostly to your specific transform case and may not be particularly useful in your overall suggestion in the title : "Support System Struct Serialiaztion."
Regarding that point, although adding serialization support is an interesting idea it bloats the overall goal of the framework, which is to encode/decode JSON.  So for the time being I am closing this issue.

Ok, thanks.


Update platformData.ts

Added multi tenant SaaS in EU
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66146d9df11271210df363e4--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66146e6ccc32ff1b81e20cb5--harness-developer.netlify.app


[SNAP-2034] separate callback for update/delete post-actions

Changes proposed in this pull request

CacheListener is occasionally causing trouble due to entry locks in BucketRegions
when trying to put into the same region so removed its addition in GemFireContainer
instead using a separate callback in StoreCallbacks that in turn invokes RowEncoder
for post-put operations outside (like done for rollover createAndInsertColumnBatch)

Patch testing
precheckin with store
ReleaseNotes changes
NA
Other PRs
https://github.com/SnappyDataInc/snappydata/pull/858

Looks good.


Scala 2.12 version?

Would be great to have

I would like to wait and see what scala-xml does of the Scala.js support pull request. If it's rejected (or takes much longer) I might cross publish another Scala.js build under my group id, but I would rather use the official one :)

Fixed in latest release.


fix tooltips margins

Summary:
As described in #21146 and #22300, and shown here, left and top tooltips exhibit inconsistencies in regards to margins.
before
Top and left tooltips sometimes ignore margins
After
All tooltips now use padding instead of margin
Technical
As shown here, top and left tooltips switches between absolute and fixed positions. No doubt this is what causes the inconsistencies, but I admit the logic behind this switch, and the reason it differs from bottom or right tooltips remains an enigma to me. It happens here, but since it's deep inside tether's logic, I tried looking for a workaround in bootstrap's code. Since the margins seems to be what causes the issue, i've successfully replaced them with paddings, while preserving the spacing by adding it to the arrow position.
Example of fix available here -
http://jsbin.com/ricinujala/edit?html,css,js,output

/CC @mdo

updated jsbin - http://jsbin.com/noyitof/edit?html,css,js,output

I close this PR because #22444 fixed that and will be merge on sunday.
Thank you @IdanCo


Confirm Delete unreadable

The text in the red Confirm Delete boxes is unreadable. Or at least I can't read it.

Is there any way to make the font bigger or somethng that stands out more? Not sure if it's a theme issue or an Obsidian Issue. It is sort of  readable in the default light theme.

It's a theme issue. I can take a look tonight and come up with something that has more contrast for readability. I can read it but it strains my eyes to do so.


panic on latest nightly

While running on the libgit2-sys crate, I'm getting a panic:

thread 'main' panicked at 'attempted to leave type extern "C" fn(u32, *const i8, *const libgit2_sys::git_diff_file, *const libgit2_sys::git_diff_file, *const libgit2_sys::git_diff_file, *mut core::ffi::c_void) -> i32 uninitialized, which is invalid', /rustc/c20d7eecbc0928b57da8fe30b2ef8528e2bdd5be/src/libcore/mem/mod.rs:536:5

This is caused by https://github.com/rust-lang/rust/pull/66059.  I'm guessing ctest will need to be rewritten to use MaybeUninit?
rustc 1.43.0-nightly (c20d7eecb 2020-03-11)

Switching from fn types to Option<fn> types would circumvent the panic for now. That type can at least legally be zero-initialized, unlike fn.
But leaving Option<fn> uninitialized still UB, and eventually the panic will catch up with that and be precise enough to test this (the planned timeframe for that extra precision is 6-12 weeks).
@ehuss do you have a full backtrace?

Alex made everything Option<fn> which seems to fix the immediate problem (https://github.com/rust-lang/git2-rs/commit/d70b64599a080ea91f6052cb234a4a485f5dcdff).
@RalfJung It looks like a lot of what ctest uses uninitialized for is computing struct layout. Do you happen if there is a "modern" way to do that?  The only thing I'm aware of is eddyb's offset_of macro (internals), but I don't know if there is a newer/better way.  Also, it looks like it needs the size and padding of the fields as well, which isn't immediately obvious to me how to compute.
The original code looked like:
#[allow(non_snake_case, unused_mut, unused_variables, deprecated)]
#[inline(never)]
fn roundtrip_padding_git_checkout_notify_cb() -> Vec<u8> {
  // stores (offset, size) for each field
  let mut v = Vec::<(usize, usize)>::new();
  let foo: git_checkout_notify_cb = unsafe { std::mem::uninitialized() };
  let foo = &foo as *const _ as *const git_checkout_notify_cb;

  // This vector contains `1` if the byte is padding
  // and `0` if the byte is not padding.
  let mut pad = Vec::<u8>::new();
  // Initialize all bytes as:
  //  - padding if we have fields, this means that only
  //  the fields will be checked
  //  - no-padding if we have a type alias: if this
  //  causes problems the type alias should be skipped
  pad.resize(mem::size_of::<git_checkout_notify_cb>(), 0);
  for (off, size) in &v {
      for i in 0..*size {
          pad[off + i] = 0;
      }
  }
  pad
}

Backtrace

thread 'main' panicked at 'attempted to leave type `extern "C" fn(u32, *const i8, *const libgit2_sys::git_diff_file, *const libgit2_sys::git_diff_file, *const libgit2_sys::git_diff_file, *mut core::ffi::c_void) -> i32` uninitialized, which is invalid', /rustc/c20d7eecbc0928b57da8fe30b2ef8528e2bdd5be/src/libcore/mem/mod.rs:536:5
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.44/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.44/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: ::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1063
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1426
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:204
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:224
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:470
  11: rust_begin_unwind
             at src/libstd/panicking.rs:378
  12: core::panicking::panic_fmt
             at src/libcore/panicking.rs:111
  13: core::panicking::panic
             at src/libcore/panicking.rs:54
  14: core::mem::uninitialized
             at /rustc/c20d7eecbc0928b57da8fe30b2ef8528e2bdd5be/src/libcore/mem/mod.rs:536
  15: systest::roundtrip_padding_git_checkout_notify_cb
             at /Users/eric/Proj/rust/git2-rs/target/debug/build/systest-d5ec5154a009511d/out/all.rs:5460
  16: systest::roundtrip_git_checkout_notify_cb
             at /Users/eric/Proj/rust/git2-rs/target/debug/build/systest-d5ec5154a009511d/out/all.rs:5494
  17: systest::run_group0
             at /Users/eric/Proj/rust/git2-rs/target/debug/build/systest-d5ec5154a009511d/out/all.rs:45828
  18: systest::run_all
             at /Users/eric/Proj/rust/git2-rs/target/debug/build/systest-d5ec5154a009511d/out/all.rs:47097
  19: systest::main
             at /Users/eric/Proj/rust/git2-rs/target/debug/build/systest-d5ec5154a009511d/out/all.rs:10
  20: std::rt::lang_start::{{closure}}
             at /rustc/c20d7eecbc0928b57da8fe30b2ef8528e2bdd5be/src/libstd/rt.rs:67
  21: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:52
  22: std::panicking::try::do_call
             at src/libstd/panicking.rs:303
  23: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:86
  24: std::panicking::try
             at src/libstd/panicking.rs:281
  25: std::panic::catch_unwind
             at src/libstd/panic.rs:394
  26: std::rt::lang_start_internal
             at src/libstd/rt.rs:51
  27: std::rt::lang_start
             at /rustc/c20d7eecbc0928b57da8fe30b2ef8528e2bdd5be/src/libstd/rt.rs:67
  28: ::pretty

@ehuss memoffset can compute offset and size of fields (and thus infer padding based on the gaps between them). Does that help?
Note that there is currently no sound way to do that, but memoffset uses the "least unsound" way. Also we will make sure to update it once a sound way exists. That's why it is better to depend on memoffset than copy its current implementation.


logo: Add new logo image from dave-tucker

This adds the new logo image to our Hugo setup. It also adds an email
address.
Signed-off-by: Kyle Mestery<EMAIL_ADDRESS>

Ah, this is much better, thanks for the help @dave-tucker !


Provide root state as second parameter to mapState

Having to constantly check if state.root exists is annoying and reduces our ability to refactor the root node out in the future.  Providing the rootState to the mapState function simplifies both.
I have also included TypeScript definitions for subspace in this PR.

Looks good to me


go: invoke bash directly on make.bash

Description of changes
This change invokes bash interpreter directly on make.bash script. This allows using overrideAttrs with dontPatch set to true as a workaround for issue #125198.
pkgs.go.overrideAttrs (prev: { dontPatch = true; })

The package also now keeps the regexp/syntax/make_perl_groups.pl script since it is not used by the current test suite and it is confusing when some files present in upstream src tree are missing.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This change invokes bash interpreter directly on make.bash script.

Rather than doing this it might be easier if we move patchShebangs to buildPhase?
diff --git a/pkgs/development/compilers/go/1.18.nix b/pkgs/development/compilers/go/1.18.nix
index 7b208da5988..5390d4f2b5b 100644
--- a/pkgs/development/compilers/go/1.18.nix
+++ b/pkgs/development/compilers/go/1.18.nix
@@ -63,10 +63,6 @@ stdenv.mkDerivation rec {

   depsTargetTarget = lib.optional stdenv.targetPlatform.isWindows threadsCross;

-  postPatch = ''
-    patchShebangs .
-  '';
-
   patches = [
     (substituteAll {
       src = ./iana-etc-1.17.patch;
@@ -117,6 +113,7 @@ stdenv.mkDerivation rec {

   buildPhase = ''
     runHook preBuild
+    patchShebangs .
     export GOCACHE=$TMPDIR/go-cache
     # this is compiled into the binary
     export GOROOT_FINAL=$out/share/go

Please open a new PR on staging.

Oops, sorry, forgot to rebase!


Adding Latex Support

Is there a way to support latex commands in the preview? What I have seen is that the latex blocks need to be protected before the markdown can be parsed.

Please adding Latex support, Thanks. XD


Please add version to manifest.json

Hello,
According to the latest breaking changes in HA 2021.3 you need to specify the version in the manifest.json for custom components.
https://www.home-assistant.io/blog/2021/03/03/release-20213/#breaking-changes
Could you please add it?
Thanks,
Gábor

Home Assistant will enforce this in the future:
2021-04-10 02:02:27 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'ecowitt'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'ecowitt'

Logger: homeassistant.setup
Source: setup.py:172
First occurred: 7:18:31 AM (1 occurrences)
Last logged: 7:18:31 AM
Setup failed for ecowitt: Integration not found.
I loaded 2021.6.0 this morning March 6 2021 and Ecowitt fails to load for this reason.
No Update in HACS yet.

Yes. I can confirm that the integration does not work anymore with 2021.6.0.

Yepp, it's not working anymore. :(

To anybody who is unable to run this custom component with HA 2021.6.
As a temporary fix, you can add this to the manifest.json manually in your own setup:
"version": "0.5",
The manifest.json should be located in this place:
/config/custom_components/ecowitt/manifest.json
And should look like this after the manual modification:
{
"domain": "ecowitt",
"name": "Ecowitt Weather Station",
"config_flow": true,
"documentation": "https://www.home-assistant.io/integrations/ecowitt",
"requirements": [
"pyecowitt==0.11"
],
"ssdp": [],
"zeroconf": [],
"homekit": {
"dependencies": [],
"version": "0.5",
"codeowners": [
"@garbled1"
]
}
The easiest to do this, is install File Editor from the Add-On store, and navigate to the file and change it manually.
This is just a temporary fix, until the PR will be merged. The same change will be available through HACS then.

Just a reference regarding the version number requirement:
https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions

To anybody who is unable to run this custom component with HA 2021.6.
As a temporary fix, you can add this to the manifest.json manually in your own setup:

Works! Thx a lot!

As a temporary fix, you can add this to the manifest.json manually in your own setup:
"version": "0.5",
The manifest.json should be located in this place:
/config/custom_components/ecowitt/manifest.json

Many thanks!

Changed  "version": "0.5", reboot, add integration, and up and running

thank you, made the modification, an can now ADD the integration after adding it to HACS

thank you, made the modification, an can now ADD the integration after adding it to HACS
but, when adding I now get
Error
Config flow could not be loaded

With HA 2021.8.X there is another breaking change regarding VOLT has to be changed to something else. Look at the other issues and PRs.

thank you, made the modification, an can now ADD the integration after adding it to HACS
but, when adding I now get
Error
Config flow could not be loaded

It happens to me exactly the same.


New Chapter Collections

Following PR #67 .

I created a New Chapter 05_Collections.
I added new content:

List
Set
Map

I moved into 05_Collections folder, collections-related part of stdlib chapter (everything except let and with).

Updated chapters result:
$ tree examples/05_Collections/ examples/06_stdlib/
examples/05_Collections/
├── 00_description.md
├── 01_List.md
├── 02_Set.md
├── 03_Map.md
├── 04_filter.md
├── 04_map.md
├── 05_existential.md
├── 06_find.md
├── 07_firstlast.md
├── 08_count.md
├── 10_associateBy.md
├── 11_partition.md
├── 12_flatMap.md
├── 13_max.md
├── 14_sorted.md
├── 15_Map_getValue.md
├── 16_zip.md
└── 17_getOrElse.md
examples/06_stdlib/
├── 00_description.md
├── 01_letFunction.md
└── 02_withFunction.md

Furthermore, I took the liberty of renaming chapters after 05_Collections, just incrementing values:

$ ls -1 examples/
01_introduction
02_control_flow
03_special_classes
04_functional
05_Collections
06_stdlib
07_Delegation
08_productivity_boosters
09_Kotlin_JS

I updated descriptions, following "Wording, style and formatting" rules.

Please let me know if this PR meets your requirements.
Thank you
Alberto
Note:
I created a brand new PR because I prefer to send "clean" request (in the previous one I didn't like what happened locally with .idea/* and .gitattributes stuff). Now I'm working locally with my own .gitignore and everything is working by default.

Hi again!
Thanks, I'll be able to test it on Monday.

Everything looks fine now. @AlexanderPrendota I think we can merge.

Alberto, thanks again for your contribution!
Regards, Pavel

It's a pleasure to collaborate in projects like this. See you next time! :)