PESDK.openCamera is undefined

package.json
{
  "name": "AppName",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "@react-native-community/cameraroll": "^1.4.1",
    "@react-native-community/google-signin": "^4.0.0",
    "@react-native-community/masked-view": "^0.1.6",
    "@react-native-firebase/app": "^6.4.0",
    "@react-native-firebase/auth": "^6.4.0",
    "@react-native-firebase/firestore": "^6.4.0",
    "lodash": "^4.17.15",
    "moment": "^2.24.0",
    "prop-types": "^15.7.2",
    "ramda": "^0.27.0",
    "react": "16.9.0",
    "react-native": "0.61.5",
    "react-native-actionsheet": "^2.4.2",
    "react-native-camera": "^3.23.1",
    "react-native-fbsdk": "^1.1.2",
    "react-native-gesture-handler": "^1.5.6",
    "react-native-image-crop-picker": "^0.28.0",
    "react-native-keyboard-aware-scroll-view": "^0.9.1",
    "react-native-modal": "^11.5.3",
    "react-native-modalbox": "^2.0.0",
    "react-native-photoeditorsdk": "^2.4.1",
    "react-native-reanimated": "^1.7.0",
    "react-native-root-toast": "^3.2.0",
    "react-native-safe-area-context": "^0.6.4",
    "react-native-safe-area-view": "^1.0.0",
    "react-native-screens": "^2.0.0-beta.1",
    "react-native-size-matters": "^0.3.0",
    "react-native-snap-carousel": "^3.8.4",
    "react-native-vector-icons": "^6.6.0",
    "react-navigation": "4.0.10",
    "react-navigation-redux-helpers": "^4.0.1",
    "react-navigation-stack": "^2.1.0",
    "react-redux": "6.0.1",
    "redux": "^4.0.4",
    "redux-persist": "5.10.0",
    "redux-saga": "^1.1.3",
    "redux-saga-routines": "^3.2.2",
    "reduxsauce": "^1.1.2"
  },
  "devDependencies": {
    "@babel/core": "^7.6.2",
    "@babel/runtime": "^7.6.2",
    "@react-native-community/eslint-config": "^0.0.5",
    "babel-jest": "^24.9.0",
    "eslint": "^6.5.1",
    "jest": "^24.9.0",
    "jetifier": "^1.6.5",
    "metro-react-native-babel-preset": "^0.56.0",
    "react-test-renderer": "16.9.0",
    "reactotron-react-native": "2.2.0",
    "reactotron-redux": "2.1.3",
    "reactotron-redux-saga": "3.0.0",
    "seamless-immutable": "^7.1.4"
  },
  "jest": {
    "preset": "react-native"
  }
}

I have reviewed the code of the PESEK module.
PESEK module file
import { Component } from 'react';
import { Configuration } from './configuration';

declare class PESDK {
  /**
   * Modally present a photo editor.
   * @note EXIF meta data is only preserved in the edited image if and only if the source
   * image is loaded from a local `file://` resource.
   *
   * @param {string | {uri: string} | number} image The source of the image to be edited.
   * Can be either an URI (local, remote, data resource, or any other registered scheme for the
   * React Native image loader), an object with a member `uri`, or an asset reference which can
   * be optained by, e.g., `require('./image.png')` as `number`. If this parameter is `null`,
   * the `serialization` parameter must not be `null` and it must contain an embedded source image.
   * @param {Configuration} configuration The configuration used to initialize the editor.
   * @param {object} serialization The serialization used to initialize the editor. This
   * restores a previous state of the editor by re-applying all modifications to the loaded
   * image.
   *
   * @return {Promise<{image: string, hasChanges: boolean, serialization: object}>} Returns the
   * edited `image`, an indicator (`hasChanges`) whether the input image was modified at all, and
   * all modifications (`serialization`) applied to the input image if `export.serialization.enabled`
   * of the `configuration` was set. If the editor is dismissed without exporting the edited image
   * `null` is returned instead.
   */
  static openEditor(
    image: string | {uri: string} | number,
    configuration: Configuration,
    serialization: object
  ): Promise<{image: string, hasChanges: boolean, serialization: object}>

  /**
   * Unlock PhotoEditor SDK with a license.
   *
   * @param {string | object} license The license used to unlock the SDK. Can be either an URI
   * pointing to a local `file://` resource that contains the license, the license as a string,
   * or the license as an object which can be optained by, e.g., `require('./pesdk_license')`
   * where the required license files must be named `./pesdk_license.ios.json` for the iOS license
   * and `./pesdk_license.android.json` for the Android license file in order to get automatically
   * resolved by the packager.
   */
  static unlockWithLicense(
    license: string | object
  ): void

  /**
   * Creates a configuration object populated with default values for all options.
   * @return {Configuration} The default configuration.
   */
  static createDefaultConfiguration(
  ): Configuration
}

/**
 * Props for the `PhotoEditorModal` component.
 */
interface PhotoEditorModalProps {
  /**
   * This prop determines whether your modal is visible.
   */
  visible: boolean;

  /**
   * This prop determines the source of the image to be edited.
   * Can be either an URI (local, remote, data resource, or any other registered scheme for the
   * React Native image loader), an object with a member `uri`, or an asset reference which can
   * be optained by, e.g., `require('./image.png')` as `number`.
   *
   * If this prop is `null`, the `serialization` prop must not be `null` and it must contain an
   * embedded source image.
   *
   * @note EXIF meta data is only preserved in the edited image if and only if the source
   * image is loaded from a local `file://` resource.
   */
  image?: string | {uri: string} | number;

  /**
   * This prop determines the configuration used to initialize the editor.
   */
  configuration?: Configuration;

  /**
   * This prop determines the serialization used to initialize the editor. This
   * restores a previous state of the editor by re-applying all modifications to the loaded
   * image.
   */
  serialization?: object;

  /**
   * This prop determines the callback function that will be called when the user exported an image.
   *
   * The object passed to this callback includes the edited `image`, an indicator (`hasChanges`) whether
   * the input image was modified at all, and all modifications (`serialization`) applied to the input image
   * if `export.serialization.enabled` of the `configuration` prop was set.
   */
  onExport: ({image: string, hasChanges: boolean, serialization: object}) => void;

  /**
   * This prop determines the callback function that will be called when the user dissmisses the editor without
   * exporting an image.
   */
  onCancel?: () => void;

  /**
   * This prop determines the callback function that will be called when an error occurs.
   */
  onError?: (error: Error) => void;
}

/**
 * State for the `PhotoEditorModal` component.
 */
interface PhotoEditorModalState {
  /**
   * This state determines whether the modal is visible.
   */
  visible: boolean;
}

/**
 * A component that wraps the `PESDK.openEditor` function to modally present a photo editor.
 */
declare class PhotoEditorModal extends Component<PhotoEditorModalProps, PhotoEditorModalState> {}

export { PESDK, PhotoEditorModal };
export * from './configuration';

Issue
According to the documentation which is on this link
https://github.com/interwebsug/photo-editor-sdk-react-native
PESDK.openCamera  method exists
But you can see inside the module this method does not exist.

Hello, bạn đã fix được lỗi này chưa

I use react-native-photoeditorsdk in project RN.
I can use funtion openEditor but can't use funtion openCamera.
Error TypeError: _$$_REQUIRE(dependencyMap[5], "react-native-photoeditorsdk").PESDK.openCamera is not a function. (In '$$_REQUIRE(dependencyMap[5], "react-native-photoeditorsdk").PESDK.openCamera(configuration)', '$$_REQUIRE(_dependencyMap[5], "react-native-photoeditorsdk").PESDK.openCamera' is undefined)
How to fix it? Pls


SSDT data comparison reports wrong results

If I try to compare to 2 databases using SSDT, I get incorrect results. The same 2 databases when compared with Red Gate's 'SQL Data Compare' tool shows correct results. Please see attached snapshots, diff1.png and diff2.png.

diff1.png shows SSDT comparison and it incorrectly reports that there are 108 updated rows in Archive_samples table. That is wrong as these are new rows.
diff2.png shows Red Gate's 'SQL Data Compare' tool and it correctly reports 108 rows in Archive_samples table as new additions.

It seems like a bug in SSDT data comparison tool.
SSDT data comparison:

Red Gate 'SQL Data Compare':

@umbersar -- Ramneek, thank you for your research and feedback.  Please add this here:

SQL Server feedback

I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Release version 1.0

Release tasks

[x] finish all jiras for v1.0 milestone
[x] update the readme to include new configuration
[ ] make the travis build pass

Released. Travis, node.. or mocha was broken in the process.


[Event Change Request] TAB39 Purchase Line - procedure SelectMultipleItems- Event OnBeforeSelectMultipleItems

Describe the request
We would like add IsHandled added to the following events.
Original:
TAB39 Purchase Line - procedure SelectMultipleItems- Event OnBeforeSelectMultipleItems

    procedure SelectMultipleItems()
    var
        ItemListPage: Page "Item List";
        SelectionFilter: Text;
    begin
        OnBeforeSelectMultipleItems(Rec);

        if IsCreditDocType() then
            SelectionFilter := ItemListPage.SelectActiveItems()

    [IntegrationEvent(false, false)]
    local procedure OnBeforeSelectMultipleItems(var PurchaseLine: Record "Purchase Line")
    begin
    end;

Change:
    procedure SelectMultipleItems()
    var
        ItemListPage: Page "Item List";
        SelectionFilter: Text;
        IsHandled : Boolean;
    begin
        IsHandled := FALSE;
        OnBeforeSelectMultipleItems(Rec,IsHandled);
        IF IsHandled THEN
          EXIT;

        if IsCreditDocType() then
            SelectionFilter := ItemListPage.SelectActiveItems()

    [IntegrationEvent(false, false)]
    local procedure OnBeforeSelectMultipleItems(var PurchaseLine: Record "Purchase Line"; var IsHandled : Boolean)
    begin
    end;

Additional context
Set a custom filter on ItemPage
Internal work item: AB#539825

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 21509.


Also link to https://github.com/huggingface/transformers/tree/master/…

…examples/pplm

 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.

 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.

 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.


add confessionals support

Comfessional support is currently only slightly visible on home page, not scored. Fix that.

Done in https://github.com/mawilson/survivor_draft/pull/146


The compiled executables are HUGE.

44MB seems a bit big for a command-line-based chat client.
Remove all dependencies which can be reasonably removed.
AESON may be the main problem.

Some light reading indicates that GHC.Generics is likely the cause of the problem.

GHC's -dynamic option reduces the size of the executable to an acceptable ~400KB.


I want shell completion for the AaC package

As a user of AaC, I want shell tab-completion for AaC commands, so that I don't have to repetitively type out commands or copy-paste them in my shell.
AC:

[ ] The user is able to type aac valid in a shell, hit tab, then see it completed to aac validate
[ ] There is autocompletion for file paths (This may require changes to the current argparse configuration)

Notes:

The main library contender I found for this is argcomplete

Limited non-bash support: You’re using bash as your shell (limited support for zsh, fish, and tcsh is available)

Another option that supports bash and zsh: https://dvc.org/blog/shtab-completion-release

Tracking this task in a newer story #409


[Idea] Chess pieces detection

Idea is to use DepthAI to recognize chess pieces on the chessboard, like in the gif below

Dataset and useful links can be found here - https://public.roboflow.com/object-detection/chess-full

@VanDavv maybe not relevant anymore, since Roboflow has created this tutorial already:
https://blog.roboflow.com/deploy-luxonis-oak/

Yes, seems so, thanks for pointing out!


I am using androidGradlePlugin, which is 7.2.2. Why is it reporting red here

adb I 05-03 00:38:16 20121 20121 main.cpp:63] Android Debug Bridge version 1.0.41
adb I 05-03 00:38:16 20121 20121 main.cpp:63] Version 31.0.3p1-android-tools
adb I 05-03 00:38:16 20121 20121 main.cpp:63] Installed as /data/app/~~tiYGxTuACHbgl5qXpByaiA==/com.github.standardadb-J_hYJoMYKFLLNn1F67BNjw==/lib/arm64/libfs64.so
adb I 05-03 00:38:16 20121 20121 main.cpp:63]
adb F 05-03 00:38:17 20121 20121 main.cpp:155] could not install smartsocket listener: Address already in use

failed to start daemon
error: cannot connect to daemon

Copyright 2020 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

org.gradle.daemon=false
org.gradle.parallel=false
org.gradle.jvmargs=-Xmx5120m
org.gradle.workers.max=2
kotlin.incremental=false
kotlin.compiler.execution.strategy=in-process
sh: [22]: org.gradle.daemon=false: inaccessible or not found
sh: [23]: org.gradle.parallel=false: inaccessible or not found
sh: [24]: org.gradle.jvmargs=-Xmx5120m: inaccessible or not found
sh: [25]: org.gradle.workers.max=2: inaccessible or not found
sh: [27]: kotlin.incremental=false: inaccessible or not found
sh: [28]: kotlin.compiler.execution.strategy=in-process: inaccessible or not found

adb I 05-03 00:38:16 20121 20121 main.cpp:63] Android Debug Bridge version 1.0.41
adb I 05-03 00:38:16 20121 20121 main.cpp:63] Version 31.0.3p1-android-tools
adb I 05-03 00:38:16 20121 20121 main.cpp:63] Installed as /data/app/~~tiYGxTuACHbgl5qXpByaiA==/com.github.standardadb-J_hYJoMYKFLLNn1F67BNjw==/lib/arm64/libfs64.so
adb I 05-03 00:38:16 20121 20121 main.cpp:63]
adb F 05-03 00:38:17 20121 20121 main.cpp:155] could not install smartsocket listener: Address already in use

failed to start daemon
error: cannot connect to daemon

Copyright 2020 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

org.gradle.daemon=false
org.gradle.parallel=false
org.gradle.jvmargs=-Xmx5120m
org.gradle.workers.max=2
kotlin.incremental=false
kotlin.compiler.execution.strategy=in-process
sh: [22]: org.gradle.daemon=false: inaccessible or not found
sh: [23]: org.gradle.parallel=false: inaccessible or not found
sh: [24]: org.gradle.jvmargs=-Xmx5120m: inaccessible or not found
sh: [25]: org.gradle.workers.max=2: inaccessible or not found
sh: [27]: kotlin.incremental=false: inaccessible or not found
sh: [28]: kotlin.compiler.execution.strategy=in-process: inaccessible or not found

Idk bro is just seems that i will wont have an account pretty soon

It looks like you are encountering an issue with the Android Gradle Plugin (AGP) version 7.2.2, which is causing your Gradle project to report errors. Let’s go through a step-by-step approach to understand and resolve this issue.
Understanding the Issue
AGP version compatibility issues can arise from:

Mismatch between Gradle and AGP versions.
Incompatibility between AGP and the Kotlin plugin version.
Issues in project configuration (build.gradle files).

Step-by-Step Solution
1. Verify Gradle Version
Ensure that your Gradle wrapper is updated to a version compatible with AGP 7.2.2. According to the official compatibility matrix, AGP v7.2.2 requires Gradle v7.4+.

Check the version in gradle/wrapper/gradle-wrapper.properties:

# gradle-wrapper.properties
distributionUrl=https\://services.gradle.org/distributions/gradle-7.4-bin.zip

If it’s not 7.4 or higher, update it to match the requirement.

2. Verify Android Gradle Plugin Version in Project-level build.gradle
Ensure the AGP version is consistent in your project-level build.gradle file:
// build.gradle (Project-level)
buildscript {
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:7.2.2' // Ensure this is the correct version
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.21" // Ensure you've the correct Kotlin plugin version
    }
}

3. Verify Kotlin Plugin Version Compatibility
Ensure the Kotlin version is compatible with AGP 7.2.2. Check the Kotlin and Android Gradle plugin compatibility table.
Update the Kotlin plugin if needed:
// Project-level build.gradle
buildscript {
    dependencies {
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.21" // Adjust to the compatible version
    }
}

4. Module-level build.gradle
Verify the compatibility in your module-level build.gradle:
plugins {
    id 'com.android.application'
    id 'kotlin-android'
}

android {
    compileSdkVersion 31

    defaultConfig {
        applicationId "com.example.myapp"
        minSdkVersion 21
        targetSdkVersion 31
        versionCode 1
        versionName "1.0"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }

    kotlinOptions {
        jvmTarget = '1.8' // Ensure this is compatible with Kotlin and AGP versions
    }
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib:1.6.21" // Ensure compatibility
    // Your other dependencies
}

5. Sync and Rebuild Your Project

Sync Gradle: Click the "Sync Now" button in the prompt that appears after modifying build.gradle files or use Tools > Sync Project with Gradle Files in Android Studio.
Rebuild Your Project: Build > Rebuild Project.

6. Check Error Message Details
If the problem persists and Gradle sync still reports errors, carefully review the error message. It may provide specific clues about the incompatibility or misconfiguration. Common AGP issues often link back to obsolete dependencies or settings.
Example Error and Solution:
Example Error:
The minCompileSdk (31) specified in a
dependency’s AAR metadata is greater than
this module’s compileSdkVersion (30).

Solution:
Update compileSdkVersion in your module-level build.gradle to match or exceed the dependency’s minCompileSdk.
android {
    compileSdkVersion 31 // Make sure this matches or exceeds the required version
    // other configurations
}

Conclusion
By ensuring compatibility between Gradle, AGP, and the Kotlin plugin, and making necessary updates to your build.gradle files, you should resolve the red reporting issue with AGP 7.2.2. Always refer to the latest compatibility tables and official documentation for the most accurate information. If issues persist, the exact error message context is very helpful for further diagnosis.


Tell cluster autoscaler to leave the hub pod alone

Prevents the autoscaler from evicting the hub pod, and resolves an outage caused by the autoscaler bouncing around a lot.
Ref: https://github.com/2i2c-org/infrastructure/issues/3461

I'm going to merge this now to prevent further possible outages.


Atomic bomb materials are not correct for 0.17, needs rocket control, less blue circuits

lol, and by "less blue circuits" I mean "none"

Thanks for the bug report!


Deleting user/roles/groups/tenant from list view throws undefined method `split' for 1:Fixnum [ops/x_button]

Build:
master.20160311012927_71e362e

Steps:
1. Navigate to Configure->Configuration.->access control
2. Try deleting the user from list view.

Note:Also try deleting group,role and tenant from list view

Actual Results:
split' for 1:Fixnum [ops/x_button] is thrown on UI

production.log:
[----] I, [2016-03-11T09:04:45.973788 #2994:d5f9120]  INFO -- :   Parameters: {"miq_grid_checks"=>"1", "pressed"=>"rbac_user_delete"}
[----] F, [2016-03-11T09:04:46.026285 #2994:d5f9120] FATAL -- : Error caught: [NoMethodError] undefined method `split' for 1:Fixnum
/var/www/miq/vmdb/app/controllers/ops_controller/ops_rbac.rb:268:in `block in rbac_user_delete'
/var/www/miq/vmdb/app/controllers/ops_controller/ops_rbac.rb:268:in `collect'
/var/www/miq/vmdb/app/controllers/ops_controller/ops_rbac.rb:268:in `rbac_user_delete'
/var/www/miq/vmdb/app/controllers/ops_controller.rb:100:in `x_button'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/abstract_controller/base.rb:183:in `process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal/rendering.rb:30:in `process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:126:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:126:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:506:in `block (2 levels) in compile'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:455:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:455:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:101:in `__run_callbacks__'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:750:in `_run_process_action_callbacks'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:90:in `run_callbacks'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/abstract_controller/callbacks.rb:19:in `process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal/rescue.rb:27:in `process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/notifications.rb:164:in `block in instrument'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/notifications.rb:164:in `instrument'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activerecord/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/abstract_controller/base.rb:128:in `process'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionview/lib/action_view/rendering.rb:30:in `process'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal.rb:190:in `dispatch'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_controller/metal.rb:262:in `dispatch'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/routing/route_set.rb:32:in `serve'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/journey/router.rb:39:in `block in serve'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/journey/router.rb:26:in `each'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/journey/router.rb:26:in `serve'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/routing/route_set.rb:739:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/secure_headers-3.0.3/lib/secure_headers/middleware.rb:10:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/etag.rb:25:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/conditional_get.rb:38:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/head.rb:12:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/session/abstract/id.rb:220:in `context'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/session/abstract/id.rb:214:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/cookies.rb:613:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:97:in `__run_callbacks__'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/callbacks.rb:90:in `run_callbacks'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/callbacks.rb:36:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/railties/lib/rails/rack/logger.rb:36:in `call_app'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/railties/lib/rails/rack/logger.rb:26:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/request_store-1.3.0/lib/request_store/middleware.rb:9:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/request_id.rb:24:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/method_override.rb:22:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/runtime.rb:22:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/activesupport/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/actionpack/lib/action_dispatch/middleware/executor.rb:12:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/rack-2.0.0.alpha/lib/rack/sendfile.rb:111:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/bundler/gems/rails-2506c7979306/railties/lib/rails/engine.rb:522:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/puma-2.16.0/lib/puma/server.rb:557:in `handle_request'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/puma-2.16.0/lib/puma/server.rb:404:in `process_client'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/puma-2.16.0/lib/puma/server.rb:270:in `block in run'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/puma-2.16.0/lib/puma/thread_pool.rb:106:in `call'
/opt/rubies/ruby-2.2.4/lib/ruby/gems/2.2.0/gems/puma-2.16.0/lib/puma/thread_pool.rb:106:in `block in spawn_thread'

For reference Screenshot is attached.

@AparnaKarve double check that this is upstream only.  Thx, Dan


Suggestion for Config file

Hi dev, i had for you a suggest. Please made command for reload config mading full reload/restart on big servers can made long lag or crash a server. I like your's plugin but please add it i will be happy for that option.

Thanks for your suggestion, I will implement the reload command as soon as I am able to ^^

I was able to implement this sooner than expected. You can download a version with the reload command here.
Please note that this is not a stable release though.


document HTML mangling

Hugo mangles output HTML, adding stuff like <meta name="generator" content="Hugo 0.55.6" /> and LiveReload by default. While LiveReload is quite well documented, the meta tag isn't. there are probably other forms of mangling that it does that are hard or impossible to disable. those should be documented as well.

I wouldn't say that the meta generator tag is 'mangling' and it is clearly documented in the Getting Started guide too: https://gohugo.io/getting-started/configuration/

disableHugoGeneratorInject (false)
Hugo will, by default, inject a generator meta tag in the HTML head on the home page only. You can turn it off, but we would really appreciate if you don’t, as this is a good way to watch Hugo’s popularity on the rise.

LiveReload is only used on Live Preview as it's needed for live reloading. It isn't included in the final generated output.

I will close this. It is documented.


WorkspaceEdit doesn't support creating new files

Not sure if this is a bug or just a missing feature!
I'm using WorkspaceEdit in my Code Actions provider but noticed that when a code action requires a new file (eg. creating a file from an import statement) it crashes because it can't find the file to modify (for both insert and replace).
I can't see anything on the API for allowing creation of new files, nor an easy way to detect if a file exists. I could obviously us node's fs class for this, but it seems a little weird to start doing that separate from the nice WorkspaceEdit class.
Is it valid to have WorkspaceEdit support creation of new files were required or is creating the files "manually" the expected way? I had a quick look at some other extensions (like TypeScript) but it seems like they don't handle it either (presumably none of their code actions need to create new files yet?).

Closing as dupe of #10659


Adjust version catalog documentation

Gradle 7.2 adds support for declaring plugin version in the version catalog. The implementation now lists plugin as a reserved keyword, but the documentation doesn't mention it.
The PR targets the release branch, although an RC version has already been published. This is a documentation-only PR so should be fine to merge it without publishing a new RC.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Thanks for the review!

OK, I've already triggered a build for you.


Plugin does not support<EMAIL_ADDRESS>or higher versions

Describe the bug The plugin worked until version 5.0.12 of vite. Starting from version 5.1.0 it is not allowing to start the app in development mode anymore.
To Reproduce Try running the Vite dev mode with the plugin and<EMAIL_ADDRESS>Expected behavior The plugin continues to function as before.
Additional context Almost immediately after starting the dev mode the following kind of error appears in the terminal:
error when starting dev server:
Error: Could not analyze entry file "...<private>..."
    at file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.3.3_vite@5.1.0/node_modules/vite-plugin-entry-shaking/dist/index.mjs:336:11
    at async Object.analyzeEntry (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.3.3_vite@5.1.0/node_modules/vite-plugin-entry-shaking/dist/index.mjs:335:3)
    at async file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.3.3_vite@5.1.0/node_modules/vite-plugin-entry-shaking/dist/index.mjs:344:7
    at async Promise.all (index 0)
    at async Object.analyzeEntries (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.3.3_vite@5.1.0/node_modules/vite-plugin-entry-shaking/dist/index.mjs:341:3)
    at async configResolved (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.3.3_vite@5.1.0/node_modules/vite-plugin-entry-shaking/dist/index.mjs:370:17)
    at async Promise.all (index 2)
    at async resolveConfig (file:///<private>/node_modules/.pnpm/vite@5.1.0_@types+node@20.11.17_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-nGG-_oRu.js:67848:5)
    at async _createServer (file:///<private>/node_modules/.pnpm/vite@5.1.0_@types+node@20.11.17_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-nGG-_oRu.js:64223:20)
    at async CAC.<anonymous> (file:///<private>/node_modules/.pnpm/vite@5.1.0_@types+node@20.11.17_sass@1.70.0/node_modules/vite/dist/node/cli.js:762:24)

Hey! Thank's again for your feedback, there's been some work done late 2023 (and last month) to address most of the issues that were opened (including yours!). Unfortunately, I could not find much time to get it 100% ready, Apologies for the delay, I'll need to get back to it soon. In the mean time, could you by any chance test your codebase against the next branch? I've tried to run it on the simple example and did not notice any error (but as the name states, it's a rather trivial example and I may be missing something).
(If you were to test it by locally by cloning & building the next branch, please don't mind the "debugger app" that may spawn along with Vite's dev server as it is still WIP)

Will do and come back to you with the results. Thanks for the great news :+1:

Can you release a "next" version using npm publish --tag next?

Can you release a "next" version using npm publish --tag next?

I also restored the example dedicated to your issue :)

Used versions:
    "vite": "5.1.3",
    "vite-plugin-entry-shaking": "0.0.0-next-20240219224802",

Sadly, starting locally still results in an error:
Error: EISDIR: illegal operation on a directory, read
    at readFileSync (node:fs:453:20)
    at file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:210:14
    at async Context.measure (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:674:17)
    at async Object.doAnalyzeEntry (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:208:20)
    at async Object.analyzeEntry (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:195:10)
    at async file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:183:7
    at async Promise.all (index 0)
    at async file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:181:5
    at async Context.measure (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:674:17)
    at async Object.analyzeEntries (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:179:31) {
  errno: -21,
  code: 'EISDIR',
  syscall: 'read'
}
error when starting dev server:
Error: Could not analyze entry file "/<private>/ui/components/"
    at file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:199:11
    at async Object.analyzeEntry (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:195:10)
    at async file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:183:7
    at async Promise.all (index 0)
    at async file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:181:5
    at async Context.measure (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:674:17)
    at async Object.analyzeEntries (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:179:31)
    at async Context.init (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:663:20)
    at async configResolved (file:///<private>/node_modules/.pnpm/vite-plugin-entry-shaking@0.0.0-next-20240219224802_vite@5.1.3_vue@3.4.19/node_modules/vite-plugin-entry-shaking/dist/index.mjs:726:7)
    at async Promise.all (index 2)
 ELIFECYCLE  Command failed with exit code 1.

Yes, there is a /ui/components/index.ts.
.tsconfig
{
  "extends": "../../.tsconfig.base.json",
  "compilerOptions": {
    "baseUrl": "."
  },
  "include": [
    "**/*.ts",
    "**/*.vue"
  ],
  "exclude": [
    "node_modules"
  ]
}

And .tsconfig.base.json
{
  "compilerOptions": {
    "target": "es2020",
    "module": "esnext",
    "strict": true,
    "jsx": "preserve",
    "importHelpers": true,
    "moduleResolution": "node",
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "sourceMap": true,
    "resolveJsonModule": true,
    "noEmit": true,
    "lib": [
      "esnext",
      "dom",
      "dom.iterable",
      "scripthost"
    ],
    "paths": {
      "@/*": [
        "./src/*"
      ]
    }
  }
}

Node Version: v20.11.0

I'm definitely having a hard time reproducing it, even by using your whole merged tsconfig and using the same node version. I've tried leaving trailing slashes at the end of entry paths, using aliases, mixed module extensions, etc. Tried on Linux and Windows environments.
Maybe there's something with your getAllLibs function? Is there any chance I could get a preview of its implementation? Anyway, I need to make a slight change to the fix I made for your #28 issue so I'll need to release another next tag for you to test it. If you have an idea of some kind of log that could help find the cause of your issue, please let me know!

Ok, I just wanted to debug the root cause, but installed a later version of Vite now:
    "vite": "5.1.4",
    "vite-plugin-entry-shaking": "0.0.0-next-20240219224802",

It works without any issues. It also feels way faster than the older versions 🤔
So, if you also think, we should not waste time investigating why it didn't work with the previous Vite version, I would be happy to just expect your next release :)

Do you already know roughly when the new release will be available?

Next version's core has been ready for quite some time now but I initially really wanted to get the upcoming debugger on point before I release anything. But tbh, I won't ever be satisfied enough with it so II'll probably take two weeks to do some fine-tuning and eventually release it even if debugger's not 100% complete. I'd say most probably ~March 30th.

@fdc-viktor-luft I've just released v0.4.0, I'm closing the issue but feel free to re-open if needed :-)


Changing an analysis node doesn't save a (parent) analysis definition

Setup the following scenario:

create a layer A with two nodes, i.e. A2 --> A1 --> A0
create a layer B which uses layer A as input, i.e. B1 --> A(2)

This means there will exist two analysis definitions (pointing to the three heads, i.e. A2, B1). Now change node A1…
Expected result:

The two analysis definitions should be updated (PUT requests), each with their own analysis_definition updated.

Actual result:

Definitions are not updated

done in 6118aa2


Update messages_de_DE.properties

Updated translations for German language.
Description
I updated the translations for German language.
Closes no issue.
Checklist

[x] I have read the Contribution Guidelines
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas - I guess this does not apply for translations
[x] My changes generate no new warnings
[ ] I have read the section Add New Translation Tags (for new translation tags only) - not checked since it is no new translation tag

Did you run the translation through Google Translate? There are strings that shouldn't be translated one-to-one in German.

There are still a few improvements, but I'll leave those up to you ;-)

@Ludy87 thank you for your comments.

Did you run the translation through Google Translate? There are strings that shouldn't be translated one-to-one in German.

No, I just did the translations by myself. Your additions sound good to me, whereas mine partly sound very "steinern".

There are still a few improvements, but I'll leave those up to you ;-)

I did some more translations and edits now. I hope they suit you better. I did everything here in good faith and based on the best knowledge available to me.

Hello @Frooodle and/or @Ludy87,
this was one of my very first ever contributions to any repository. I never worked with translations before and don´t know how in GitHub the actions work to build the language completeness indicator seen here: https://hub.docker.com/r/stirlingtools/stirling-pdf
Can you tell me, is there an easy way to find out which strings in the translation are missing to achieve the 100% translation?
Help appreciated! :)


Add Cloudformation support for BYOIP IP updates and cross-account attachments

Issue #, if available:
Description of changes:

Update Java SDK version
Add capability for defining Cloudformation workflows that include BYOIP IP Updates
Add capability for defining Cloudformation workflows that include Cross Account Attachment Resources
Add contract tests for BYOIP IP Updates
Add contract tests for Cross Account Attachment resources

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Adding BYOIP swap and Cross account attachment


Handle multiple filters in search results page

Related to #144
Right now, multiple ontology IDs (and multiple types) are not handled by the search API. See image below.

In that example, I tried to pass a comma-separated list of ontology IDs to ontologyId with EFO and DUO as elements of the list.


Lang - get maintemplate using the reusable make files

JustWe are getting lots of errors with missing translations.

The above should be impossible to screw up. But it did 😔
Also we need to stop including the JSON. It's not needed I think as the ARB is all that needed for the release. The app is up to 9 mb !
I also think we need to save sertings using shared preferences or hive. The app is so big that android is reloading the app when it goes out of foreground and back into foreground and sonlooses whatever language you selected . This is why I wanted setting to be protobuf based because then the a new version with changed setting won't blow up when it reads the stored settings JSON.
Either the developer missed a text field leaving it as English or the modules translation is not being updates
Let's start to use the boilerplate makefile system that is now setup
Also let's change CI to force translation all the way down.
The root makefile is in the root of maintemplate.
The lsng.mk in boilerplate will need some adjustment I expect
The i18.km is sys-core can be deleted ?

I was looking into the intl stuff, but i am afraid i can't do anything as long as the go script is not working correctly. It fails with mod-main:
Stacktrace:
~/projects/getcouragenow/packages/mod-main/client on master*
$ make lang-gen-flu
fatal: No names found, cannot describe anything.
panic: runtime error: index out of range [35] with length 35

goroutine 1 [running]:
github.com/getcouragenow/bootstrap/tool/i18n/services.getTranslatedMaps(0x163dd06, 0x2, 0xc000294700, 0x6, 0x8, 0xc00018b200, 0x1, 0xc0001c9e00, 0x6, 0x6)
	/Users/alec/workspace/go/pkg/mod/github.com/getcouragenow/bootstrap/tool/i18n@v0.0.0-20200430105819-54dc86e15368/services/translation.go:66 +0x5c9
github.com/getcouragenow/bootstrap/tool/i18n/services.GenerateMultiLanguageFilesFromTemplate(0x7ffeefbff4bf, 0x52, 0x7ffeefbff473, 0x40, 0x7ffeefbff51b, 0x4, 0x163e479, 0x4, 0x163dd06, 0x2, ...)
	/Users/alec/workspace/go/pkg/mod/github.com/getcouragenow/bootstrap/tool/i18n@v0.0.0-20200430105819-54dc86e15368/services/write.go:298 +0x1b3
github.com/getcouragenow/bootstrap/tool/i18n/cmd.glob..func1(0x1b02d20, 0xc000114510, 0x0, 0x9, 0x0, 0x0)
	/Users/alec/workspace/go/pkg/mod/github.com/getcouragenow/bootstrap/tool/i18n@v0.0.0-20200430105819-54dc86e15368/cmd/flutter.go:28 +0x1bd
github.com/spf13/cobra.(*Command).execute(0x1b02d20, 0xc000114480, 0x9, 0x9, 0x1b02d20, 0xc000114480)
	/Users/alec/workspace/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842 +0x453
github.com/spf13/cobra.(*Command).ExecuteC(0x1b03260, 0x1042dca, 0x1abfe40, 0xc000000180)
	/Users/alec/workspace/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950 +0x349
github.com/spf13/cobra.(*Command).Execute(...)
	/Users/alec/workspace/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887
github.com/getcouragenow/bootstrap/tool/i18n/cmd.Execute()
	/Users/alec/workspace/go/pkg/mod/github.com/getcouragenow/bootstrap/tool/i18n@v0.0.0-20200430105819-54dc86e15368/cmd/root.go:29 +0x31
main.main()
	/Users/alec/workspace/go/pkg/mod/github.com/getcouragenow/bootstrap/tool/i18n@v0.0.0-20200430105819-54dc86e15368/main.go:6 +0x20
make: *** [lang-gen-flu] Error 2

I think you mentioned several separated issues here:

I also think we need to save sertings using shared preferences or hive. The app is so big that android is reloading the app when it goes out of foreground and back into foreground and sonlooses whatever language you selected . This is why I wanted setting to be protobuf based because then the a new version with changed setting won't blow up when it reads the stored settings JSON.

IMHO-> should be a new issue

Let's start to use the boilerplate makefile system that is now setup
Also let's change CI to force translation all the way down.
The root makefile is in the root of maintemplate.
The lsng.mk in boilerplate will need some adjustment I expect
The i18.km is sys-core can be deleted ?

-> i can say if the go tool is fixed

Either the developer missed a text field leaving it as English or the modules translation is not being updates

-> translations are there but, same as above, waiting for the go tool fix.

Also we need to stop including the JSON. It's not needed I think as the ARB is all that needed for the release.

-> think the same, but need to verify when things are running

The app is up to 9 mb !

-> new issue, we can shrink some images e.g.

@winwisely99  Please fix the go code :)

First fix it here: https://github.com/getcouragenow/bootstrap/issues/70

both screenshots above should be fixed now with https://github.com/getcouragenow/packages/pull/556


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/buildbot-www-feedstock#11.


Close GC window properly

This fixes the issue that sometimes GC window doesn't close properly.

This is a very old pull request but I'm going to commit it manually. Thank you.


Timeline: Update Events

Tasks

[ ] Receive events form sse and update timeline events

Use case
Timeline Events
Related Pull request
No response

Thx for creating the issue! The timeline should actually collect events from all layers, e.g., also drawing layer.


Add post-file walk linting and empty package linting

This checks for empty packages and also adds a facility to allow for post-walk lints that can walk the tree or do whatever.

Hmm, some packages are failing. Should I check subpackages as well?

So I've discovered in my travels that gdk-pixbuf had an empty metapackage that wasn't necessary, and exa had an empty docs package. So these weren't spurious failures at all. The linter did what it was supposed to do.
This linter is likely to show a lot of empty packages. I don't know if I should make this an optional lint for the moment, or rip the band-aid off now.


[Docs] A guide for Animation

So many questions come up about animation and AnimationExperimental, which inevitably lead to mentions of the new animation api and suggestions to avoid AnimationExperimental in favour of react-tween-state or rebound. This should be summarized in the docs to bring more clarity to the current state of animations for newcomers.

:100:

:+1:

@brentvatne  This should be close though. We have an animation guide up now.

Solved with documentation http://facebook.github.io/react-native/docs/animations.html#content unless you believe the current animation documentation isn't enough
@brentvatne already solved

Excellent :)


Update openapi.yaml to openai/openai-openapi commit 33d5c27 (latest as of Jun 9th)

Changes
Copy and paste openai-openapi yaml file and replace existing ones. The major motivation is OpenAI added a new parameter, tool_choice into the RunObject type(see this line vs current repo run object, because my project uses the Assistants API  a lot I noticed that missing tool_choice causes my project to work as expected.
Test
I ran the bb test in my local repo. Returns:
~/c/openai-clojure ❯❯❯ bb test                                                              (base)  main ⬆ ✱

Running task for: test
true

misc
I noticed that OpenAI has a lot of updates while the version handily stays at 2.0.0: https://github.com/openai/openai-openapi/blame/master/openapi.yaml#L5, any thoughts on using git submodule to maintain API specs compatibility ? (Assuming in this repo there's no manual update).

Thanks!
There's normally a few manual changes needed documented here: https://github.com/wkok/openai-clojure/blob/main/resources/openapi-README.md
I'll merge this PR and make those changes after.
Regarding the tests, bb test is deceiving in that it does not actually run the tests due to this reflection PR that was merged a while back. I think I'm going to revert the reflection warning change as running tests are more important.

oh I sure didn't realize that regarding bb test.
I read the README document, but I wasn't sure if it's still relevant, you
know especially with openapi specs got updated so frequently.
Werner Kok @.***> 于2024年6月10日周一 15:06写道：

Thanks!
There's normally a few manual changes needed documented here:
https://github.com/wkok/openai-clojure/blob/main/resources/openapi-README.md
I'll merge this PR and make those changes after.
Regarding the tests, bb test is deceiving in that it does not actually
run the tests due to this reflection PR
https://github.com/wkok/openai-clojure/pull/48/files that was merged a
while back. I think I'm going to revert the reflection warning change as
running tests are more important.
—
Reply to this email directly, view it on GitHub
https://github.com/wkok/openai-clojure/pull/64#issuecomment-2159100058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIIWBJK5XF35JNRUML42I7LZGX2K3AVCNFSM6AAAAABJBMJTLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGEYDAMBVHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Mark footer Slack CTA emoji as decorative with aria-hidden="true"

This will improve the accessibility of the Slack CTA.

Assigning to @shyusu4 as part of her Outreachy project.

Fixed in #49.


Makefile: move dashboard-server-frontend job

Signed-off-by: you06<EMAIL_ADDRESS>What problem does this PR solve?
Makefile image workload should only build docker images and this PR move dashboard-server-frontend out of image workload.
What is changed and how does it work?
Update Makefile.
Check List
Tests

Manual test (add detailed scripts or steps below)

Code changes

Has CI related scripts change

Side effects

Will build frontend when running make build

Codecov Report

Merging #134 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #134      +/-   ##
==========================================
+ Coverage   29.92%   30.03%   +0.11%
==========================================
  Files          24       24
  Lines         802      799       -3
==========================================
  Hits          240      240
+ Misses        531      528       -3
  Partials       31       31

Impacted Files
Coverage Δ

pkg/utils/coalescer.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 172d746...0735e7d. Read the comment docs.


Rel: can't make  relative to <relative --out path>

Seems unmaintained so I guess I'm on my own but may as well post anyway:
go-msi make
        --src=./distribution/windows/templates
        --path=./distribution/windows/wix.json
        --msi=./dist/windows/Appname.msi
        --out=./dist/windows/temp
        --version={{.VERSION}}
        --license=LICENSE

Rel: can't make D:\Work\appname\dist\windows\Appname.msi relative to ./dist/windows/temp

Looks broken, no paths work in the config even if they are absolute.

I have the same issue

I have the same issue


Athena: metadata caching

Is your idea related to a problem? Please describe.
We rely on Athena caching quite a bit - we currently run our own caching mechanism, but moving to the aws wrangler would be desirable. What's stopping us a bit is the way caching is implemented. If I want to extend the cache to the last, say, 300 queries, _read.py will query list_query_executions and batch_get_query_execution six times each, both of which are fairly slow.
Describe the solution you'd like
Since the logic is written in composable functions, we can't quite rely on some private caching in a class, so a global would have to do, which is not a super pretty pattern, but it would probably do. Caching batch_get_query_execution is rather simple, we could create a _cache = defaultdict(dict) and save all SUCCEEDED query metadata in _cache[workgroup][queryId].
Then when listing past queries, we could check the cache and only do batch_get_query_execution for those not in our cache. Ideally we'd want to skip the listing as well, but that would only be doable if we allowed for stale results - e.g. imagine you first check the cache and if a query is there, return it directly. But what if the query ran after you last filled the cache and it returned different results than the one before (e.g. count(*) and a new partition was added). We'd get quite flaky results.
So at least some listing stays. Say you request 150 past queries. You list once and find 3 new queries and 47 cached ones. If your cache contains at least 103 another entries, you don't need to do any more listing or batch getting - that's a nice speedup. It's even compatible with something more complex than a defaultdict - we'd probably prefer some sorted data structure that would start deleting old queries.
There are a few edge cases here and there, but overall, I think this could be done without a huge amount of complexity and could benefit interactive workloads, where you keep calling read_sql_query repeatedly and build your cache as you go along.

So that's my initial brain dump when it comes to client side caching of metadata. Let me know if you have thoughts on this topic

Hi @kokes ! It's a great idea for sure.
The whole Wrangler architecture was designed to keep things as simple as possible without handling states, so this implementation using only "raw functions" was conscious.
I really like you idea because it is not invasive at all. And I think the only point where some refactoring would be required is on this for statement. We just need to replace the current logic by something smarter like what you've proposed.
Like you said, a class holding this state would be more elegant, but a global variable solves the problem too. So I don't see any serious reason to not do it. To be honesty, we already have a global variable implemented in this code base.
For sure it is something that we will be happy to implement in the future. But please, feel free to also send your PR if you want.

@maxispeicher your propose seems perfect to me.
@kokes if you want, I recommend you to give it a try directly from the development branch:
pip install git+https://github.com/maxispeicher/aws-data-wrangler.git@athena-metadata-caching

@maxispeicher your propose seems perfect to me.
@kokes if you want, I recommend you to give it a try directly from the development branch:
pip install git+https://github.com/maxispeicher/aws-data-wrangler.git@athena-metadata-caching

Released on version 2.3.0 🚀

Released on version 2.3.0 🚀


Unable to connect with a Nextcloud instance in WebDAV :(

The problem
Hi
Following the documentation I have created my rclone.conf file:
[NC]
type = webdav
vendor = Nextcloud
pass = passwd created in nextcloud and passed through obscure command of rclone
url = https://mynextcloudurl/remote.php/dav/files/special-user/backup_HA
user = special-user

but it always fail to connect at NC. Here are logs:
[2024-08-22] [12:00:13] [ERROR]: failed to run rclone command: exit status 1
[2024-08-22] [13:00:00] [INFO]: running "Sync Backup daily"; /backup -> NC:/
[2024-08-22] [13:00:00] [INFO]: renamed 0 backups
2024/08/22 13:00:13 ERROR : webdav root '': error reading destination root directory: couldn't list files: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2024/08/22 13:00:13 ERROR : Attempt 1/3 failed with 1 errors and: couldn't list files: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2024/08/22 13:00:39 ERROR : webdav root '': error reading destination root directory: couldn't list files: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2024/08/22 13:00:39 ERROR : Attempt 2/3 failed with 1 errors and: couldn't list files: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2024/08/22 13:01:00 INFO  :
Transferred:   	          0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       1m0.0s

2024/08/22 13:01:05 ERROR : webdav root '': error reading destination root directory: couldn't list files: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2024/08/22 13:01:05 ERROR : Attempt 3/3 failed with 1 errors and: couldn't list files: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2024/08/22 13:01:05 INFO  :
Transferred:   	          0 B / 0 B, -, 0 B/s, ETA -
Errors:                 1 (retrying may help)
Elapsed time:       1m5.3s

2024/08/22 13:01:05 Failed to copy: couldn't list files: No public access to this resource., Username or password was incorrect, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
[2024-08-22] [13:01:05] [ERROR]: failed to run rclone command: exit status 1

I have tried also using the NC password without the rclone obscure command but it's the same !
Vincèn
What version of Rclone Backup has the issue?
3.3.1
What version of Home Assistant are you running?
2024.3.3
What type of installation are you running?
Home Assistant OS
If you're running HA OS/Supervised, what version of the Supervisor are you running?
2024.08.0
Example YAML snippet
No response
Anything in the logs that might be useful for us?
See above

Additional information
Problem on multiple HA instances and different NC servers too !

This works for me.
Looks like your credentials are invalid.
Did you created the config file via the addon frontend?
My rclone.conf file:
[<Name>]
type = webdav
pass = <hashed password>
url = https://example/remote.php/dav/files/path/to/folder
user = <nextcloud user>
vendor = Nextcloud


s/kafkacat/kcat

Many THX for this contribution @rmoff! I fixed the positioning of the now shorter text which is why I superseded this PR by #26


Allow regexes in 'allowed_users'

Allow to specify regexes in allowed_users list. This makes it possible to enable chatgpt for all users of a specific homeserver. Superseeds https://github.com/williamkray/maubot-chatgpt/pull/12

I would really enjoy a merge of this PR :) !

this feature is now available with commit 1ec2a42


first draft

Ops! I found it is better to use MessageAttributes instead of using topic and data into the message body.
Changing that NOW.

Yeap. Now you can review it. :)

Teste falhou

Falhou nada, seu mentiroso. Olha aí, passou de boas.


Explore MethodHandles usage

Do not merge this :) It's just to be able to post jmh results and do some experiments with MH stuff.
@gsmet I've tried a couple things that we talked about yesterday... Here are some first results based on such kind of changes:

these are for the case visible in this PR (when there's a validation of just one bean)

as is:

# Run complete. Total time: 00:00:40

Benchmark                                Mode  Cnt     Score     Error   Units
FooValidation.testSimpleBeanValidation  thrpt   20  1417.867 ± 140.205  ops/ms

just creating MH stuff in constructor:

# Run complete. Total time: 00:00:40

Benchmark                                Mode  Cnt     Score     Error   Units
FooValidation.testSimpleBeanValidation  thrpt   20  1421.445 ± 196.217  ops/ms

having a private static final MH:

# Run complete. Total time: 00:00:40

Benchmark                                Mode  Cnt     Score    Error   Units
FooValidation.testSimpleBeanValidation  thrpt   20  1569.186 ± 56.427  ops/ms

Next I've tried to validate a collection of beans (as usual - 100 beans in a list) instead of one and the results I've got are (on a different machine):
as is:

# Run complete. Total time: 00:00:40

Benchmark                                Mode  Cnt  Score   Error   Units
FooValidation.testSimpleBeanValidation  thrpt   20  4.217 ± 0.210  ops/ms

simple MH field init in constructor:

# Run complete. Total time: 00:00:40

Benchmark                                Mode  Cnt  Score   Error   Units
FooValidation.testSimpleBeanValidation  thrpt   20  4.496 ± 0.391  ops/ms

private static final MH

# Run complete. Total time: 00:00:39

Benchmark                                Mode  Cnt  Score   Error   Units
FooValidation.testSimpleBeanValidation  thrpt   20  4.696 ± 0.169  ops/ms

I'm a bit surprised to see that big of a jump in case of one bean when a constant field used and such small when just a MH is used as a regular field.
I think that a validation of a collection gives a better picture. I'll play with it a bit more and post the results here.
Note: to see how I've "changed" the location impls just check a corresponding commit.

FWIW, the general opinion is that MethodHandles can only get better and be polished in the future. So that would be a good move anyway, if it's at least not slower than what we had.
So I would be +1 on pursuing this.

@marko-bekhta, @gsmet, have you read Geoffrey's recent post on this: https://www.optaplanner.org/blog/2018/01/09/JavaReflectionButMuchFaster.html? It seems the best we can do would be to use code generation for accessing public members and fall back to method handles otherwise.

@gunnarmorling yes, we already discussed this post and John's result with Marko. We wanted to see what differences will it make in HV to understand better if this approach would be worth it or not.
Clearly, I'm against moving to bytecode generation in a micro. Not sure I would move to MethodHandle either tbh - especially since the gain is very minor.
I would say let's revisit it once we prepare a 6.1. Things might have evolved in the right way then (maybe by reducing the cost of not having the MH static final).

@marko-bekhta so on this one, I think it would be worth it to take a first baby step and migrate to MethodHandles even if they are not static final.

+1 to introduce the handles first. If we do this right, then replacing it with generated classes shouldn't be a problem (if we could generate a class that we need :)).
We would need to add an option for users to pass MethodHandles.Lookup to us, right ?

We would need to add an option for users to pass MethodHandles.Lookup to us, right ?

Probably. What bugs me a little is that in the OSGi case, you will be forced to pass a lookup in addition to the current external class loader. I don't see a way to avoid that and this is unfortunate as it will break existing applications. Unless you see a workaround?
So for now, I would favor working on things that can bring something to the user as the JSON stuff.

This was superseded by https://github.com/hibernate/hibernate-validator/pull/975 .


[Feature]: Restructure input validation

Describe the feature that you would like.*
Restructure how variables are validated throughout the codebase:

Avoid explicit validation, instead passing variables to their point of use and letting an error be raised if the value is inappropriate at the point of use.
If one of our functions does need to validate a variable in order to guard against security risks from bad input, use explicit if statements in preference to hidden validation functions, e.g. if a < 5: raise ValueError("Suitable error message") instead of validate_in_range.
Remove the module validation.py.

Why is this feature valuable to you?*

Make the code easier to read.
Reduce processing overhead for users who supply valid input.
Guard against abuse of private functions.

Describe alternatives you've considered
No response
Additional context
The codebase currently includes various validation functions in validate.py. The core development team has agreed that these should be replaced using the approach described in this ticket.
Code of Conduct*

[x] I agree to follow this project's Code of Conduct

Ticket needs to be broken down by module.

Closing as covered by other, more granular tickets.

@pc532627 Here is our strategy:

Do cast when required, e.g. jnp.atleast_2d.
Try to minimise the number of times the same thing is validated. This is easier said than done because we have many nested calls of public functions. In which case, we may just have to validate at point of use, rather than the __init__ to classes.
Keep isinstance (vanilla Python, not ours in validation.py) where necessary to provide useful error messages. If we're about to check for a particular attribute, it's probably not necessary to check the class is of the correct type.
In KernelHerding, there's a double loop with max_size as the step parameter.

If positive, we're ok.
If zero, get unhelpful error.
If negative, fails silently with weird output as loop does not execute.
Define a function so that we can update max_size in a local scope.
max_size = max(max_size, 0)
try: indices = range(from, to, max_size); except whatever error when step=0: raise ValueError("useful message")
Only need to apply to one range as the other will yield the same error.
Key is a very tight try-except statement designed to only pick up exactly what we want to validate. Do not use an if statement in LBYL style if you can help it.


Disambiguate Windows run-times when using clang to compile.

This is with reference to https://github.com/rust-lang/cc-rs/issues/819#issuecomment-1640309753. In the comment I'm suggesting to take it as far as rejecting the use of gcc in the msvc compilation, while this PR only issues a warning.

Yeah, my impression is it's pretty much always wrong to use gcc for a -msvc target. @ChrisDenton any objections to merging this?

Yes the current gnu toolchains, unlike llvm, do not aim to be compatible with msvc.

I'm okay with it too.

With cross-reference to #811, a case can be made that it would be appropriate to issue "unsupported" warning even for clang++ [not to be confused with clang-cl] being used with msvc target.


Add option --minimal-dependencies

Is your feature request related to a problem? Please describe.
When I install qtbase with a target triplet != host triplet, it also installs qtbase with all default features for the host system (in manifest and classic mode), but the host dependency states that only qtbase[core] is needed. So I build one hour host dependencies that I will never need.
Proposed solution
For host dependencies respect "default-features": false, for non host dependencies add an option --minimal-dependencies so that "default-features": false is even respected for the target triplet.
Describe alternatives you've considered
None
Additional context
For cross compiling it even breaks my build because some of the dependencies does not build on the host system.
You can workaround this issue by adding a dependency to every port that is installed for the host target and set  "default-features": false, but this is very tedious.
Previous Discussion
https://github.com/microsoft/vcpkg/issues/11602#issuecomment-686788148

@ras0219-msft what do you think about this?


ToFrozenDictionary(bool) does not exist

Type of issue
Typo
Description
From https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-8/runtime#performance-focused-types
private static readonly FrozenDictionary<string, bool> s_configurationData =
    LoadConfigurationData().ToFrozenDictionary(optimizeForReads: true);

As per FrozenDictionary.ToFrozenDictionary Method there are 3 overloads of ToFrozenDictionary:

ToFrozenDictionary<TKey,TValue>(IEnumerable<KeyValuePair<TKey,TValue>>, IEqualityComparer<TKey>)
ToFrozenDictionary<TSource,TKey,TElement>(IEnumerable<TSource>, Func<TSource,TKey>, Func<TSource,TElement>, IEqualityComparer<TKey>)
ToFrozenDictionary<TSource,TKey>(IEnumerable<TSource>, Func<TSource,TKey>, IEqualityComparer<TKey>)

None of them has bool parameter named optimizeForReads.
Page URL
https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-8/runtime
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/whats-new/dotnet-8/runtime.md
Document Version Independent Id
15cdd77f-e040-364f-035a-cecb0fac7cb6
Article author
@gewarren
Metadata

ID: cf0836eb-9b39-9da3-0bf8-cf9cd982727d
Service: dotnet-fundamentals

Related Issues

Thanks @bravequickcleverfibreyarn. Looks like this method was removed in https://github.com/dotnet/runtime/pull/87988.


Linked in Login does not fire any callback on IOS

I am using<EMAIL_ADDRESS>On Android device, it is working fine, but IOS does not do anything, not fire success or fail callback for both formats.
var scopes = ['r_basicprofile', 'r_emailaddress', 'rw_company_admin', 'w_share'];
1st :  cordova.plugins.LinkedIn.login(scopes, true, onSuccess, onError)

on Android, its working, Do nothing for IOS

2nd:  cordova.plugins.LinkedIn.login(scopes, true, onSuccess, onError)

On Android,
Error: Uncaught (in promise) TypeError: Cannot read property 'then' of undefined

On IOS,

Error in Success callbackId: LinkedIn77629818 : TypeError: undefined is not an object (evaluating 'cordova.plugins.LinkedIn.login(scopes, true).then')
Hardly finding the solution for IOS.
Someone Please help me to solve this problem.

For me the problem was having another plugin (cordova-plugin-ms-azure-mobile-apps ) which had an AppDelegate (AppDelegate+MobileServicesPlugin.m) with openURL function, and that was overriding the linkedin openURL, so basically when flow returns from LinkedIn app to your app, that would be intercepted by the other AppDelegate which doesnt handle our url schema (liAPPID). Removing that fixed the issue for me. Check for other AppDelegates on your plugins


[Bundle] include default files

Description
Create the bundles with default files for OpenSearch and OpenSearch
Dashboards.
These files include:

opensearch-tar-install.sh
config/opensearch_dashboards.yml

However, we do not want to include opensearch-tar-install.sh into
the OpenSearch Dashboards bundle because the script will just fail
to run.
Signed-off-by: Kawika Avilla<EMAIL_ADDRESS>Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/610
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #758 (d85e76f) into main (326d59f) will increase coverage by 0.07%.
The diff coverage is 91.30%.

@@            Coverage Diff             @@
##             main     #758      +/-   ##
==========================================
+ Coverage   91.21%   91.28%   +0.07%
==========================================
  Files          75       75
  Lines        1992     2009      +17
==========================================
+ Hits         1817     1834      +17
  Misses        175      175

Impacted Files
Coverage Δ

src/assemble_workflow/bundle.py
94.66% <75.00%> (-2.35%)
:arrow_down:

src/assemble_workflow/bundle_opensearch.py
100.00% <100.00%> (ø)

.../assemble_workflow/bundle_opensearch_dashboards.py
100.00% <100.00%> (ø)

src/run_assemble.py
97.05% <100.00%> (+4.75%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43b7675...d85e76f. Read the comment docs.


Webhook plugin  cache _m5 hook support.

Proposed Changes
Webhook cache should support _m5 webhooks.
Types of Changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes issue #2199 )
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (correction or otherwise)
[ ] Cosmetics (whitespace, styles...)
[ ] DevOps (Build scripts, pipelines...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

[ ] I have read the CODE_OF_CONDUCT.md document
[ ] All tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if needed)
[ ] Any dependent changes have been merged and published in related repositories
[ ] I have updated changelog (At the bottom of the release version)
[ ] I have squashed all my commits into one before merging

Further Comments
If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.

Looks like a perfect fix! Thank you :)
:tada: :1st_place_medal:


:sparkles: Compile Regex for tag comparisons

FYI because the automation seems broken:
Overall success rate: 82.16% (1838/2237)


in IE is error

SparkMD5.prototype.appendBinary = function (contents) {
    this._buff += contents;
    this._length += contents.length;

    var length = this._buff.length,
        i;

in IE is error
contents maybe null

appendBinary is a function that you call (part of the public API), and it expects a string. You can’t call it with null.


Add oneway arrows to remaining highway classes

Adds oneway arrows to non-motorway highway classes, with half the layers.

I honestly didn't even realize this was missing.

It appears that this change also unifies the link and regular versions of each road class, is that also a deliberate consolidation?

#513 would be helpful in assessing changes in layer count.

It appears that this change also unifies the link and regular versions of each road class, is that also a deliberate consolidation?

Yes - were they separate layers intentionally?

Yes - were they separate layers intentionally?

Only in the sense that I (a) didn't really know what I was doing and (b) didn't realize layer count had a performance implication.

The changes appear to be working from visual inspection.
The arrows on motorway_link are hard to see and we may want to open a separate issue to track it, as reducing layer count is a clear improvement by itself.

Adding oneway arrows seems to cause a significant slowdown at very high zoom, so it's hidden at ≥z20.

Adding oneway arrows seems to cause a significant slowdown at very high zoom

This sounds dodgy.

Something is extremely slow at high zooms already.

How about white arrows for motorways and trunks?

On second thought, white is even less legible against the red on trunk_link. Changing trunk oneway arrows back to black.

There is an artifact in cases of a link road:

Location (localhost link)
Is this resolvable with a change in ordering or unavoidable?  Is there a way to prevent the arrows from being drawn too close to the ends of a road?

We would have to sandwich oneway arrows in between two road fill layers, which would hinder our ability to refactor roads to use more expressions and fewer layers. I don't think there's an easy solution to this.

Is there a way to prevent the arrows from being drawn too close to the ends of a road?

It is possible to use invisible spacer symbols to collide out any arrows that would be drawn at the endpoints, similar to how we’re pushing waterway labels away from bridges. In this case, the symbol’s symbol-placement property would be set to point so that it gets placed at one of the endpoints instead of repeated along the line. We’d need to pay attention to the spacing settings so that shields and road names don’t become less dense because of collisions suddenly occurring at junctions – or junctions on nearby roadways. Also, openmaptiles/planetiler-openmaptiles#10 proposes to fix wrong-way one-way arrows by disabling line merging of one-way lines; with that stopgap fix in place, the spacers would frequently prevent any one-way arrows or shields from showing up at all on one-way streets.
/ref mapbox/mapbox-gl-js#4003

One-way arrows only come in at z15 for freeways. At this zoom level, we’re already starting to show surface streets in the “cased” style. I think this gives us some flexibility to deemphasize color distinctions based on road classification. It’s also at a high enough zoom level that there’s a less ambiguity as to which ramp goes in which direction, so maybe the ramp arrows aren’t essential.
/ref #486

Oneway arrows removed from link roads:

Hmm... Without arrows on link roads, figuring out whether a ramp is an on or off requires the eye tracing it up to the lanes it diverges from. I imagine that there are a few cases of stacked interchanges where that becomes really difficult to tease out visually. (for example, the GW bridge)

These looks pretty good for all but the lowest highway classes.
For the tiniest roads (alleys and so forth), I'm not sure if I'm seeing arrows or if there's a speck on my laptop screen that needs to be cleaned.  Not sure if there's a good solution to this.  Perhaps a hard minimum size to the arrow and let it overflow a bit?
Location:

Wondering if we might

This better?

This looks good!
I note that bridges are not included (example), however, bridges appear to be not supported presently. Is that intended to be part of this PR or left as future work?

I note that bridges are not included (example), however, bridges appear to be not supported presently. Is that intended to be part of this PR or left as future work?

That's a mistake. They're in the list of layers, so I don't know why they aren't showing up.

Figured it out. The culprit was the invisible spacer label that prevents waterway labels from colliding with bridges. This spacer is now disabled if the bridge is tagged oneway=yes.

The arrows seem to serve the spacers' purpose except at really high zooms.

The arrows seem to serve the spacers' purpose except at really high zooms.

Before removing the spacer, oneway arrows would only show up at very high zooms. Something weird is going on and it's cooking my CPU.

Ah, it might be that some combination of spacers + oneway arrows + lettering causes this.
I still also hypothesize that it's overzooming the z14 tile to z22 and then stuffing it full of symbols, i.e. if higher zoom tiles existed that were simply slices of the full ones then it would attempt to do less work.
Might also be that the waterway lettering is attempting to overlap itself severely, could see if the slowdown is localized depending on the presence of waterways or oneways.
https://osmus.slack.com/archives/C01V02K52UX/p1658777024337899


Fix type forwarding for init/record workaround

This PR fixes the magic around the IsExternalInit field that allowed OmniSharp to opt-in to the use of init and record semantics before they were available normally. This prior workaround, however, now can easily cause problems after updating to .NET 6.0, where the field is available. The primary problem manifests with a net6.0 app consumes the OmniSharp library (targeting netstandard2.0) and attempts to use any of the record structs (with init fields), such as PowerShell Editor Services' test suite when creating CompletionRecord structs. The type resolution would fail on initialization of the struct because the set method was not pointing to the right place, similar to what happened to System.Text.Json (which also opted in early with that workaround) in https://github.com/dotnet/runtime/issues/61737.
.NET may eventually find a solution (see https://github.com/dotnet/sdk/issues/23319) that is more elegant than this, but for now the correct thing to do, as confirmed with @ericstj, is as seen in this PR: forward the type when targeting .NET 5.0 or greater, and otherwise define it internally (it should never be defined publicly). Then in consuming libraries, if they similarly used the same IsExternalInit code, the same correction should be applied (as was done to PowerShell Editor Services in https://github.com/PowerShell/PowerShellEditorServices/pull/1953).
I also updated the test apps and sample program just to target net6.0 instead of netcoreapp3.1 for simplicity (note the prior targets had redundant frameworks, probably from a prior find/replace). This will not affect consumers.
Finally, I fixed the macOS CI build by updating the build tool that was failing to install, and then re-enabled CI.

It is working locally on macOS:
═══════════════════════════════════════════════════════════
Target                                 Status      Duration
───────────────────────────────────────────────────────────
Clean                                  Succeeded     < 1sec
DotnetToolRestore                      Succeeded     < 1sec
Restore                                Succeeded       0:04
Build                                  Succeeded       2:53
Test                                   Succeeded       1:45
GenerateCodeCoverageReportCobertura    Succeeded       0:09
GenerateCodeCoverageBadges             Succeeded       0:03
GenerateCodeCoverageSummary            Succeeded       0:03
GenerateCodeCoverageReport             Succeeded       0:10
Pack                                   Succeeded       0:05
───────────────────────────────────────────────────────────
Total                                                  5:17
═══════════════════════════════════════════════════════════

Build succeeded on 11/8/2022 1:58:02 PM. ＼（＾ᴗ＾）／
@andys-mac-mini .../csharp-language-server-protocol andschwa/fix-records ≡

This was confusing as all get out. @david-driscoll take a look at https://github.com/dotnet/sdk/issues/23319. I've tested PowerShell Editor Services whole test suite against this locally with this PR: https://github.com/PowerShell/PowerShellEditorServices/pull/1953.

.NET may eventually find a solution (see https://github.com/dotnet/sdk/issues/23319) that is more elegant than this

That issue is just about flagging this compatibility problem at build time for libraries that have it.  Right now the problem is still a library issue.  Libraries defined IsExternalInit locally and that "leaks" to their callers in public API.  If they want to remain compatible with that public API they need to keep defining the type locally, or forward the local definition to the framework version.  The only "more elegant fix" would be a hack to have the runitme's type loader ignore the assembly difference here and effectively "inject" a type forward.  I don't expect the runtime will ever do that, and likely not retroactively on net5.0 - net7.0, so this fix is the right one regardless.

I agree with @ericstj assessment. This is one of the dangers of using new C# features on old runtimes.


add chart description in html and readme

Changes

add chart tip in html template
update readme with chart description

/lgtm
Thanks @zyjiaobj for the nice chart and @gyohuangxin @maximilien for the review! Merging it.


feat: improve startup time by caching version

For me this reduces loading of this plugin from 7ms -> 1ms.

Hi,
cool idea. Can you please check tests before ill merge it upstream?
Kind regards
Alexander


implement a GETSTATICURL function

right now there's no way to add references from javascript code to the asset graph. expose a function call that wag can look for and parse out asset references.
AssetGraph exposes one called GETSTATICURL. Might be good to re-use that name for compatibility.

no longer relevant; parsing javascript for dynamic asset references is not easy/possible. support for javascript parsing has been removed.