Will be the project updated in the future ...

Hello,
will be the project updated in the future and listed in the official IOBroker Adapter Repro (i don't install adapters from external sources) or is the project died before started?

Hello @GameWatchProjects ,
I didn't update the project since it didn't seem like there was anyone interested in the adapter.
If I find some time I will at leat make it compatible with the lastest version

A new version 0.1.0 has just been uploaded to npm


prediction of fruit disease

accept my request

accept my request

Hey @janvikohli  .. Just Generate the same PR in https://github.com/py3-coder/Model-EDA-Analysis-CART this repo.
will accept after verification


Word transposition

This change is

@bors-servo: r+

:pushpin: Commit 9ecbcef has been approved by jdm

:hourglass: Testing commit 9ecbcefca7e48aaec25ae279ab4a7acb60b9e19c with merge 9dbacd715271eba6f211db1a590360143e61e6f2...

:sunny: Test successful - status-travis
Approved by: jdm
Pushing 9dbacd715271eba6f211db1a590360143e61e6f2 to master...


broken C++ Code Analysis link

Through a websearch, I found http://microsoft.github.io/CodeAnalysis/ which still exists but has an incorrect link to:
http://microsoft.github.io/CppCodeAnalysis

@japj  Where is the code in which change is required ?? I would like to fix this .

Looks like the link on the webpage is fine. this can be closed

Um, the link is still broken. It's the third "View on GitHub" button at https://microsoft.github.io/CodeAnalysis

@jeffwilcox the third link on that page goes to 404

@jeffwilcox the third link on that page goes to 404


Segmentation fault when running image driver with LAKES = TRUE (cells with and without lakes)

Hello, I am trying to run VIC with the image driver for the submeridional lowlands (45000 km2, Argentina) with cells of ~5 km *5 km. The region has numerous lakes and wetlands, whose representation implies that there are cells with and without lake/wetland.
I got the following error when trying to run the model on a certain year:
Invalid MIT-MAGIC-COOKIE-1 keyVIC Driver  : Image
VIC Version : 5.0.1 February 1, 2017
VIC Git Tag :
Compiled    : by root on edna-MS-7A15 (LINUX) Oct 11 2022 21:36:34
Compiler    : gcc
version    : 9.4.0
Variable Infiltration Capacity (VIC) macroscale hydrologic
model version 5.0.1, Copyright (C) 2016 Computational
Hydrology Group, Dept. of Civil and Environmental Engineering,
University of Washington.  VIC comes with ABSOLUTELY NO
WARRANTY. This is free software, you may redistribute it
under certain conditions; see LICENSE.txt for details.
Report Bugs and Issues to : https://github.com/UW-Hydro/VIC/issues
VIC Users Email Listserve<EMAIL_ADDRESS>[INFO] ../shared_all/src/vic_log.c:139: Logging to stderr
[DEBUG] ../shared_image/src/get_global_domain.c:98: 5881 active grid cells found in run_cell in the parameter file.
[edna-MS-7A15:385101] *** Process received signal ***
[edna-MS-7A15:385101] Signal: Segmentation fault (11)
[edna-MS-7A15:385101] Signal code: Address not mapped (1)
[edna-MS-7A15:385101] Failing at address: 0x7ffcf0fe6000
[edna-MS-7A15:385101] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x143c0)[0x7f89cd7983c0]
[edna-MS-7A15:385101] [ 1] ./vic_image.exe(+0x1ff9d)[0x5646cfdb1f9d]
[edna-MS-7A15:385101] [ 2] ./vic_image.exe(+0x47dd1)[0x5646cfdd9dd1]
[edna-MS-7A15:385101] [ 3] ./vic_image.exe(+0x1b952)[0x5646cfdad952]
[edna-MS-7A15:385101] [ 4] ./vic_image.exe(+0xb2aef)[0x5646cfe44aef]
[edna-MS-7A15:385101] [ 5] ./vic_image.exe(+0x4d8ab)[0x5646cfddf8ab]
[edna-MS-7A15:385101] [ 6] ./vic_image.exe(+0x4dbca)[0x5646cfddfbca]
[edna-MS-7A15:385101] [ 7] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7f89cd5b60b3]
[edna-MS-7A15:385101] [ 8] ./vic_image.exe(+0x3e2e)[0x5646cfd95e2e]
[edna-MS-7A15:385101] *** End of error message ***
Violación de segmento
This error occurs only when LAKES = TRUE, otherwise the model runs successfully for all times.
To find out if the problem was in having cells with and without wetland, I tried to run the model with a domain of 4 cells with lake/wetland and the model ran but until the penultimate time:
[ERROR] ../shared_image/src/get_nc_field.c:48: errno: NetCDF: Index exceeds dimension bound: Error getting values for CHANNEL_IN in /home/edna/Escritorio/datos_BBSS/forcing_file_2003.nc
It's very weird because I have a single netcdf forcing and the variables (PREC, AIR_TEMP..., CHANNEL_IN) share the same time dimension (the model runs successfully when LAKES=FALSE).

Try using gcc version 8.* That seemed to have fixed the issue for me. I suspect newer versions of gcc have stricter memory safety features that throw seg faults with the lake model.


Compatibility with Kotlin 1.8.10+

My project is using Kotlin 1.8.10 but it seems that mockposable using 1.7.20 prevents us from being able to upgrade. Would it be possible to get a new release with the versions updated?

@jpetitto can you try with the snapshot version 0.3-SNAPSHOT?
Requires you to add the snapshot maven repo
maven {
    url 'https://oss.sonatype.org/content/repositories/snapshots/'
}

Doesn't look like I'm able to locate the version (I'm using the mockk version btw).
> Could not resolve all files for configuration ':presentation:kotlinCompilerPluginClasspathDebug'.
   > Could not find com.jeppeman.mockposable:mockposable-compiler:0.3-SNAPSHOT.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/maven-metadata.xml
       - https://dl.google.com/dl/android/maven2/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/mockposable-compiler-0.3-SNAPSHOT.pom
       - https://jcenter.bintray.com/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/maven-metadata.xml
       - https://jcenter.bintray.com/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/mockposable-compiler-0.3-SNAPSHOT.pom
       - https://repo.maven.apache.org/maven2/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/maven-metadata.xml
       - https://repo.maven.apache.org/maven2/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/mockposable-compiler-0.3-SNAPSHOT.pom
       - https://artifacts.dox.support/repository/maven_hosted/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/maven-metadata.xml
       - https://artifacts.dox.support/repository/maven_hosted/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/mockposable-compiler-0.3-SNAPSHOT.pom
       - https://jitpack.io/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/maven-metadata.xml
       - https://jitpack.io/com/jeppeman/mockposable/mockposable-compiler/0.3-SNAPSHOT/mockposable-compiler-0.3-SNAPSHOT.pom

Looks good on our end. Thanks for the quick turnaround!

Great! 0.3 is available on mavenCentral now


Make wool/carpet items drop silently

Fix for MC-252258
The code is kinda ugly, but I wasn't sure how to write it better, and it works.

Ok I need to revisit this


Customizable shortcut for Shortcut Guide doesn't make sense

Microsoft PowerToys version
0.41
Running as admin

[ ] Yes

Area(s) with issue?
Shortcut Guide
Steps to reproduce
I believe from this update Shortcut Guide lost its ability to appear on holding the Win button and it's using a customizable shortcut ( Win+Shift+\ by default) now. This behaviour feels wrong because the guide shows the second button of all possible  Win button shortcuts.
✔ Expected Behavior
Shortcut Guide should appear on hold the Win button or must be completely redesigned
❌ Actual Behavior
Shortcut Guide appears on pressing the customizable shortcut
Other Software
No response

My problem with this update, that UX became confusing. When you pressed the button and saw what you can press next that was a simple and elegant solution. Now you need to remember the shortcut which only shows the second button of all possible win button shortcuts and you should keep this in mind. I hope the shortcut guide v2 will fix it but until that unlinking from the win button gives unnecessary complexity.

@HenryOfCarim You can pull it up and still press and hold winkey and shortcut guide will not dismiss so the behavior still slightly exists, you can keep the UX up.
I would suggest looking at what is being proposed for v2 as it is radically different concept.

I am trying to follow this and not sure what I am not understanding. What happened to press and hold windows key? was it removed in the update? (It still mentions it in the manual here https://docs.microsoft.com/en-us/windows/powertoys/shortcut-guide It worked fine for me before and now it doesnt. I liked it better than a customized key. Please bring it back.

I believe from this update Shortcut Guide lost its ability to appear on holding the Win button and it's using a customizable shortcut ( Win+Shift+\ by default) now. This behaviour feels wrong because the guide shows the second button of all possible Win button shortcuts.

What does this mean?

Looking through the v2 plan the change makes a bit of sense. But the chosen hotkey combination is very tragic for winkey shortcuts. The press and hold behaviour integrated perfectly with the intention the user had when pressing the key by showing the possible shortcut while holding the correct modifier key.

Pressing the Win button and waiting to be told what to press next was 90% of my usage of PowerToys. This is because, like a lot of people, I can never remember the shortcuts. Now it is activated by a shortcut I WILL NEVER REMEMBER!
Not sure negative improvements for the sake of code elegance is a good thing. I will revert to an earlier version if possible.

Pressing the Win button and waiting to be told what to press next was 90% of my usage of PowerToys. This is because, like a lot of people, I can never remember the shortcuts. Now it is activated by a shortcut I WILL NEVER REMEMBER!
Not sure negative improvements for the sake of code elegance is a good thing. I will revert to an earlier version if possible.

AGREE! Now we need a shortcut to remember the shortcuts! If you find out how to revert to old version, please let us know here!

Yes please atleast give us an option to set the shortcut to only Win. I tried but couldn't set it

Great feedback here, i just created a new issue that groups this and a different variant of the same feedback in #11963.  This is where we'll track the feedback moving foward
To be crisp, i directly hear and understand the feedback.  This is interesting as well as we've shared thoughts for v2 shortcut guide for a long time now and this is really the first big push against that concept.  We will have to rethink it.

Pressing the Win button and waiting to be told what to press next was 90% of my usage of PowerToys. This is because, like a lot of people, I can never remember the shortcuts. Now it is activated by a shortcut I WILL NEVER REMEMBER!
Not sure negative improvements for the sake of code elegance is a good thing. I will revert to an earlier version if possible.

Agree, but now that I know it's the equivalent of Win-? (at least on my American keyboard) I at least have a small chance of remembering.


We need to add the max # of merge policies allowed in Profile to the guardrails page

Issue in ./help/profile/guardrails.md
The product description says 3 - https://helpx.adobe.com/legal/product-descriptions/real-time-customer-data-platform.html#:~:text=Profile Merge Policies.  Customer may use up to 3 concurrent Profile Merge Policies%2C including any system Profile Merge Policies.
But the merge policy page says 5 -
https://experienceleague.adobe.com/docs/experience-platform/profile/merge-policies/overview.html?lang=en#:~:text=Please note that there is a maximum of five merge policies allowed per organization.

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-161243.


Read ITC array values in output reports

Pull Request Template
Description
-Change report templates to read ITC federal and state as arrays rather than numbers.
Fixes #1226
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)

Checklist:
If you have added a new compute module in a SSC pull request related to this one, be sure to check the Process Requirements.

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

Updated mini-grid example to latest version as otherwise Version upgrade window is blocking user interface and can't close it without exiting the wizard first. Thoughts @sjanzou @cpaulgilman ?

Updated mini-grid example to latest version as otherwise Version upgrade window is blocking user interface and can't close it without exiting the wizard first.

I agree with updating the mini-grid-example.sam file to the current version so the upgrade script does not run -- we should add that to the pre-release checklist. I think that is the only .sam file in the distribution.

Updated mini-grid example to latest version as otherwise Version upgrade window is blocking user interface and can't close it without exiting the wizard first. Thoughts @sjanzou @cpaulgilman ?

Thanks for updating the mingrid sam file - that should be one more thins off of the pre-release checklist!

When ITC is an array of more than one value, I don't think it makes sense to report the average over the analysis period in the PDF report. (The PBI applies to annual production every year, so reporting the average over the analysis period is somewhat meaningful, but the ITC applies to the installation cost only in the years where the percentage is not zero.) For ITC it might make more sense to report the sum of the array values instead of their average, and put "total" in parentheses instead of "average".
@sjanzou, what do you think?

@cpaulgilman, yes, I agree, the sum is the most meaningful single metric for the ITC array.


Add darklua.json generation

I think using darklua to bundle requires into a single file would be nice

breh i didn't even check if darklua settings were right


xlsx2csv 0.7.7

Type: Missing
Summary:
xlsx2csv 0.7.7
Details:
Inconsistent license info - LICENSE.txt is GPL-3.0, file header is GPL-2.0-or-later, and COPYING file is LGPL-2.0.
Resolution:
Curating as GPL-2.0-or-later.
Affected definitions:

xlsx2csv 0.7.7

Note - the repo has an open issue asking about the licensing inconsistency.  I curated based on the license information in the xlsx2csv.py file - GPL-2.0-or-later.  The "or-later" covers or includes the GPL-3.0 LICENSE.txt.

@ariel11 How confusing... Since it has a COPYING file, should we wait and see what they determine the correct license should be? I thought COPYING applied over LICENSE in a distribution. Please correct me if I am wrong.

@capfei - Yes, let's wait for confirmation from the author on Issue 147.  (I see COPYING and LICENSE as equivalent file names for a project's main/primary license file.)

@ariel11 I submitted a PR to change license info to GPL 2.0. We'll see if the author accepts.
https://github.com/dilshod/xlsx2csv/issues/147
https://github.com/dilshod/xlsx2csv/pull/210

@ariel11 The author accepted my PR. Merging this.


CHEBI:157683 is not a pentapeptide

The entity althiomycin (CHEBI:157683) is currently classified as a pentapeptide (CHEBI:48545). I'm not quite sure why exactly this classification has been made, since the definition does not make a reference to pentapeptides.
However, there are definitely less than 5 amino acid residues in this molecule. There are 2 amide bonds which sets the upper limit to three amino acids. In addition, I would argue that the structure on the left-hand side does not contain an amino group since both nitrogen atoms are double-bonded. So my conclusion is that althiomycin is a dipeptide.
I would suggest to either change the axiom or remove it entirely (for most other peptide antibiotics, no classification based on the number of amino acids has been made).

The pentapeptide relationship has now been removed. I assume that the relationship was added because a few articles classify it as a heavily modified pentapeptide (E.g. https://chemistry-europe.onlinelibrary.wiley.com/doi/epdf/10.1002/cbic.201100154).


Quick start example using l for a variable name

Hey guys,
Please don't use l as a variable name in any of your examples, let alone the first example under "Quick start".
I assume l is short for love?  Also the font that you have used 1 and l look almost identical.
Thanks, Jared.

The naming could be better. I'm going to close this issue for now, but please do open a pull request.


Block edge 4.5.14

4.5.14 needs to be disabled:
2 clusters currently failing (20%),  2 gone (20%),and  6 successful (60%), out of 10 who attempted the update over 7d
Currently failing classification:
* Monitoring issues: 1
* Untriaged: 1

4.5.14 can be enabled again:
1 clusters currently failing (10%),  2 gone (20%),and  7 successful (70%), out of 10 who attempted the update over 7d
Currently failing classification:
* Monitoring issues: 1


[ios] 1.20.1, "No such module" error when referring from extension module

This issue occurs when I upgrade flutter version to 1.20.1. I have "No such module" error when the imported module (AnyCodable-FlightSchool) is used in extension module.
Steps to Reproduce

Add AnyCodable-FlightSchool to the Podfile

Podfile

# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))

  # Plugin Pods
  pod 'AnyCodable-FlightSchool', '~> 0.2.3'
end

 target 'OneSignalNotificationServiceExtension' do
   use_frameworks!

 end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
    end
  end
end

Create a swift file for importing the module

Notification.swift

import Foundation
import AnyCodable

public struct TNotificationPayload: Codable {
    public var additionalData: [String: AnyCodable]
}

Create a NotificationServiceExtension
Up till here, building has no issue. However, if the Notification.swift is set to be used in ServiceExtension (Show File Inspector > Target Membership > Check NotificationServiceExtension), the No such module 'AnyCodable' will occurs after clicking build.

Logs
flutter build ios
flutter doctor -v

[✓] Flutter (Channel stable, 1.20.1, on Mac OS X 10.15.5 19F101, locale en-GB)
    • Flutter version 1.20.1 at /Users/kahwaimok/Development/flutter
    • Framework revision 2ae34518b8 (6 days ago), 2020-08-05 19:53:19 -0700
    • Engine revision c8e3b94853
    • Dart version 2.9.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/kahwaimok/Library/Android/sdk
    • Platform android-29, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.13.2

[✓] Connected device (1 available)
    • SM N960F (mobile) • <IP_ADDRESS>:5555 • android-arm64 • Android 10 (API 29)

• No issues found!

Hi @...
I see there's an open issue addressing the case you described. https://github.com/flutter/flutter/issues/63018
Please read this  comment https://github.com/flutter/flutter/issues/63018#issuecomment-670601961 & https://github.com/flutter/flutter/issues/63018#issuecomment-670759935
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you

I am already using the latest Podfile.

Hi @TabooSun
I can reproduce this issue  based on the steps,
logs.txt

flutter doctor -v
[✓] Flutter (Channel stable, 1.20.1, on Mac OS X 10.15.6 19G73, locale en-GB)
    • Flutter version 1.20.1 at /Users/tahatesser/Code/flutter_stable
    • Framework revision 2ae34518b8 (6 days ago), 2020-08-05 19:53:19 -0700
    • Engine revision c8e3b94853
    • Dart version 2.9.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.1
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.13.2

[✓] Connected device (3 available)
    • SM M305F (mobile)      • 32003c30dc19668f                     • android-arm64 • Android 10 (API 29)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E            • ios           • iOS 13.6
    • iPhone 11 (mobile)     • A63D6F51-59F3-4A75-961F-3769709F3A92 • ios           • com.apple.CoreSimulator.SimRuntime.iOS-13-6
      (simulator)

• No issues found!

Ok, added this to PodFile
target 'NAME_OF_EXTENSION_TARGET' do
  use_frameworks!
  use_modular_headers!

  pod 'Alamofire','~> 4.9.1'
end

Built successfully after that

Are you able to install it? I can build it but can't install.

Ok, added this to PodFile
target 'NAME_OF_EXTENSION_TARGET' do
  use_frameworks!
  use_modular_headers!

  pod 'Alamofire','~> 4.9.1'
end

Built successfully after that

@amantoux Are you able to install it? I can build it but can't install.

Yes managed to install it

Details

Unable to install "Runner"
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402653028
--
The bundle’s Info.plist does not contain a CFBundleVersion key or its value is not a string.
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402653028
User Info: {
    DVTRadarComponentKey = 261622;
    MobileDeviceErrorCode = "(0xE800009C)";
    "com.apple.dtdevicekit.stacktrace" = (
	0   DTDeviceKitBase                     0x0000000122dbb81a DTDKCreateNSErrorFromAMDErrorCode + 233
	1   DTDeviceKitBase                     0x0000000122dfcf70 __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155
	2   DVTFoundation                       0x0000000109c65f35 DVTInvokeWithStrongOwnership + 73
	3   DTDeviceKitBase                     0x0000000122dfcca8 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1654
	4   IDEiOSSupportCore                   0x0000000122c73e91 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.352 + 4165
	5   DVTFoundation                       0x0000000109d995d4 __DVT_CALLING_CLIENT_BLOCK__ + 7
	6   DVTFoundation                       0x0000000109d9b216 __DVTDispatchAsync_block_invoke + 1194
	7   libdispatch.dylib                   0x00007fff7356e6c4 _dispatch_call_block_and_release + 12
	8   libdispatch.dylib                   0x00007fff7356f658 _dispatch_client_callout + 8
	9   libdispatch.dylib                   0x00007fff73574c44 _dispatch_lane_serial_drain + 597
	10  libdispatch.dylib                   0x00007fff735755d6 _dispatch_lane_invoke + 363
	11  libdispatch.dylib                   0x00007fff7357ec09 _dispatch_workloop_worker_thread + 596
	12  libsystem_pthread.dylib             0x00007fff737c9a3d _pthread_wqthread + 290
	13  libsystem_pthread.dylib             0x00007fff737c8b77 start_wqthread + 15
);
}
--

System Information

macOS Version 10.15.6 (Build 19G2021)
Xcode 11.6 (16141)

Following @amantoux workaround, I got this error.

Details

Unable to install "Runner"
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402653028
--
The bundle’s Info.plist does not contain a CFBundleVersion key or its value is not a string.
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402653028
User Info: {
    DVTRadarComponentKey = 261622;
    MobileDeviceErrorCode = "(0xE800009C)";
    "com.apple.dtdevicekit.stacktrace" = (
	0   DTDeviceKitBase                     0x0000000122dbb81a DTDKCreateNSErrorFromAMDErrorCode + 233
	1   DTDeviceKitBase                     0x0000000122dfcf70 __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155
	2   DVTFoundation                       0x0000000109c65f35 DVTInvokeWithStrongOwnership + 73
	3   DTDeviceKitBase                     0x0000000122dfcca8 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1654
	4   IDEiOSSupportCore                   0x0000000122c73e91 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.352 + 4165
	5   DVTFoundation                       0x0000000109d995d4 __DVT_CALLING_CLIENT_BLOCK__ + 7
	6   DVTFoundation                       0x0000000109d9b216 __DVTDispatchAsync_block_invoke + 1194
	7   libdispatch.dylib                   0x00007fff7356e6c4 _dispatch_call_block_and_release + 12
	8   libdispatch.dylib                   0x00007fff7356f658 _dispatch_client_callout + 8
	9   libdispatch.dylib                   0x00007fff73574c44 _dispatch_lane_serial_drain + 597
	10  libdispatch.dylib                   0x00007fff735755d6 _dispatch_lane_invoke + 363
	11  libdispatch.dylib                   0x00007fff7357ec09 _dispatch_workloop_worker_thread + 596
	12  libsystem_pthread.dylib             0x00007fff737c9a3d _pthread_wqthread + 290
	13  libsystem_pthread.dylib             0x00007fff737c8b77 start_wqthread + 15
);
}
--

System Information

macOS Version 10.15.6 (Build 19G2021)
Xcode 11.6 (16141)

Following @amantoux workaround, I got this error.
I notice that the FLUTTER_BUILD_NAME and FLUTTER_BUILD_NUMBER is not copied to the extension module.

Workaround found for this issue by changing the Info.plist of extension module:

Change the value of CFBundleShortVersionString from $(FLUTTER_BUILD_NAME) to $(MARKETING_VERSION)
Change the value of CFBundleVersion from $(FLUTTER_BUILD_NUMBER) to $(CURRENT_PROJECT_VERSION)

The bundle's Info.plist does not contain a CFBundleVersion key or its value is not a string.

@TabooSun Did you find a fix? Also running into this with Flutter 1.20.4.

We got to fix the The bundle's Info.plist does not contain a CFBundleVersion key or its value is not a string. error, but setting the build configuration for the NotificationService in Xcode as well, e.g.

I think before it was inherited from the parent, but this changed in https://github.com/flutter/flutter/pull/54691.

Any progress on this issue? Or a reliable workaround?

@TabooSun
I followed the details you mentioned in original description and ran a sample app using latest stable version (3.19.5) through Xcode with which I was able to compile and run the app without any issues.
I added the said pod, notification.swift and NSE but I am not sure how to set below you mentioned:

4. However, if the Notification.swift is set to be used in ServiceExtension (Show File Inspector > Target Membership > Check NotificationServiceExtension),

Can you try this issue again at your end with latest stable to confirm if the issue you had reported persist or not ?
If so, please provide us updated steps to properly address the issue.

Unfortunately, I don't have access to that repo now, it's hard for me to reproduce it.

I am going ahead and closing this due to lack of updated reproducible code sample pertaining to latest stable. If anybody in this thread still facing same issue using latest version, please open a new issue with relevant details so that we can properly address it.


Swagger for Facebook Connector Has Errors

Describe the bug
Unable to create a power automate app with power platform Customer facebook connection.
To Reproduce

Go to power automate.
Go to Data--> Custom connections tab.
Click on new custom connectors icon.
Click on Import an OpenAPI file.
Select apiDefinition.swagger.json file within "..\Custom Connection\PowerPlatformConnectors-master\custom-connectors\Facebook".
Put client id and client secret.
Click on create connector.

Expected behavior
Specified swagger has the following errors: 'Definition is not valid.  Error: 'Error : paths/~1{pageId}~1feed/get/parameters/0/x-ms-dynamic-values/parameters/Accept : The parameter could not be found in operation 'GetMyPages' in the swagger document.    ##   Error : paths/~1{pageId}~1feed/post/parameters/0/x-ms-dynamic-values/parameters/Accept : The parameter could not be found in operation 'GetMyPages' in the swagger document. '

Any resolution for this to use in power automate ?

Hi @abhishekpalit09
I would encourage you to fix the connector and submit a fix for the community.

any help on this would be appreciated,
I made changes to the swagger json file
`basePath: /
consumes: []
host: graph.facebook.com
info: {description: A sample Facebook connector for using with the CLI., title: Facebook,
version: '1.0'}
parameters: {}
paths:
/trigger/me/feed:
get:
description: Triggers a new flow when there is a new post on your timeline.
It is possible for this trigger to not activate for all posts since detection
of a post must pass several privacy checks including a person's privacy settings
on Facebook.
summary: When there is a new post on my timeline
operationId: TriggerNewPost
x-ms-visibility: important
x-ms-trigger: batch
x-ms-trigger-hint: To see it work now, add a post to your Facebook timeline.
consumes: []
produces: [application/json, text/json]
parameters: []
responses:
'200':
description: OK
schema: {$ref: '#/definitions/TriggerFeedResponse'}
'400': {description: Bad Request}
'500': {description: Internal Server Error}
default: {description: Operation Failed.}
/me/feed:
get:
description: Get the feed from your timeline.
summary: Get my feed
operationId: MyFeeds
consumes: []
produces: [application/json, text/json]
parameters:
- {name: fields, in: query, description: 'Specify the fields you want returned.
Example (id,name,picture).', required: false, x-ms-visibility: advanced,
default: 'id, created_time, from, message, to, type', type: string, x-ms-summary: Fields}
- {name: limit, in: query, description: Maximum number of posts to be retrieved.,
required: false, type: integer, format: int32, x-ms-summary: Max posts, x-ms-visibility: advanced}
- name: with
in: query
description: Restrict the list of posts to only those with location attached.
required: false
type: string
enum: [location]
x-ms-summary: With or without location
x-ms-visibility: advanced
responses:
'200':
description: OK
schema: {$ref: '#/definitions/GetFeedResponse'}
'400': {description: Bad Request}
'500': {description: Internal Server Error}
default: {description: Operation Failed.}
x-ms-visibility: important
/{pageId}/feed:
get:
description: Get posts from the feed of a specified page.
summary: Get page feed
operationId: PageFeeds
consumes: []
produces: [application/json, text/json]
parameters:
- {name: pageId, in: path, description: Unique ID of the page from which posts
have to be retrieved., required: true, type: string, x-ms-summary: Page
ID}
- {name: limit, in: query, description: Maximum number of posts to be retrieved.,
required: false, type: integer, format: int32, x-ms-summary: Max posts, x-ms-visibility: advanced}
- {name: include_hidden, in: query, description: Whether or not to include any
posts that were hidden by the Page., required: false, type: boolean, x-ms-summary: Include
hidden posts, x-ms-visibility: advanced}
- {name: fields, in: query, description: 'Specify the fields you want returned.
Example (id,name,picture).', required: false, x-ms-visibility: advanced,
default: 'id, created_time, from, message, to, type', type: string, x-ms-summary: Fields}
responses:
'200':
description: OK
schema: {$ref: '#/definitions/GetFeedResponse'}
'400': {description: Bad Request}
'500': {description: Internal Server Error}
default: {description: Operation Failed.}
x-ms-visibility: important
post:
description: Post message to a page that you own.
summary: Post to page
operationId: PostToPage
consumes: [application/json, text/json]
produces: [application/json, text/json]
parameters:
- {name: pageId, in: path, description: Unique ID of the page to post to., required: true,
type: string, x-ms-summary: Page ID}
- name: post
in: body
required: true
description: New message to be posted.
x-ms-summary: Post Details
schema: {$ref: '#/definitions/PagePostFeedRequest'}
responses:
'200':
description: OK
schema: {$ref: '#/definitions/PostFeedResponse'}
'400': {description: Bad Request}
'500': {description: Internal Server Error}
default: {description: Operation Failed.}
x-ms-visibility: important
/users/{userId}/feed:
get:
description: Get posts from a user's timeline.
summary: Get user timeline
operationId: UserTimeline
consumes: []
produces: [application/json, text/json]
parameters:
- {name: userId, in: path, description: Unique ID of the user whose timeline
have to be retrieved., required: true, type: string, x-ms-summary: User
ID}
- {name: limit, in: query, description: Maximum number of posts to be retrieved.,
required: false, type: integer, format: int32, x-ms-summary: Max posts, x-ms-visibility: advanced}
- name: with
in: query
description: Restrict the list of posts to only those with location attached.
required: false
type: string
enum: [location]
x-ms-summary: With or without location
x-ms-visibility: advanced
- {name: fields, in: query, description: 'Specify the fields you want returned.
 The profile could be a user,
page, app, or group.
x-ms-summary: Feed Item
type: object
properties:
id: {description: Unique ID of the post., type: string, title: Post ID}
admin_creator:
description: Unique ID of admin who created the post. Applies to pages only.
type: array
items: {$ref: '#/definitions/AdminItem'}
x-ms-visibility: advanced
title: Admin Creators
caption: {description: The caption of a link in the post (appears beneath the
name)., type: string, title: Link caption, x-ms-visibility: advanced}
created_time: {description: 'The time the post was initially published. For
a post about a life event, this will be the date and time of the life event.',
type: string, title: Created Date-Time, x-ms-visibility: advanced}
description: {description: A description of a link in the post (appears beneath
the caption)., type: string, title: Link Description, x-ms-visibility: advanced}
feed_targeting: {$ref: '#/definitions/FeedTargetItem'}
from: {$ref: '#/definitions/UserItem'}
icon: {description: A link to an icon representing the type of this post., type: string,
title: Icon link, x-ms-visibility: advanced}
is_hidden: {description: If this post is marked as hidden (applies to Pages
only)., type: boolean, title: 'Is hidden?', x-ms-visibility: advanced}
is_published: {description: 'Indicates whether a scheduled post was published
(applies to scheduled Page Post only, for users post and instanlty published
posts this value is always true).', type: boolean, title: 'Is published?',
x-ms-visibility: advanced}
link: {description: The link attached to this post., type: string, format: uri,
title: Link url, x-ms-visibility: advanced}
message: {description: The status message in the post., type: string, title: Status
message}
name: {description: The name of the link., type: string, title: Name}
object_id: {description: The ID of any uploaded photo or video attached to the
post., type: string, title: Media ID, x-ms-visibility: advanced}
picture: {description: The picture scraped from any link included with the post.,
type: string, format: uri, title: Image url, x-ms-visibility: advanced}
place: {$ref: '#/definitions/PlaceItem'}
privacy: {$ref: '#/definitions/PrivacyItem'}
properties:
description: A list of properties for any attached video, for example, the
length of the video.
type: array
items: {$ref: '#/definitions/PropertyItem'}
title: Post Properties
x-ms-visibility: advanced
source: {description: A URL to any Flash movie or video file attached to the
post., type: string, format: uri, title: Video source, x-ms-visibility: advanced}
status_type:
description: Description of the type of a status update.
type: string
enum: [mobile_status_update, created_note, added_photos, added_video, shared_story,
created_group, created_event, wall_post, app_created_story, published_story,
tagged_in_photo, approved_friend]
title: Status update type
x-ms-visibility: advanced
story: {description: 'Text from stories not intentionally generated by users,
such as those generated when two people become friends, or when someone
else posts on the person''s wall.', type: string, title: Story text, x-ms-visibility: advanced}
targeting: {$ref: '#/definitions/TargetItem'}
to:
description: Profiles mentioned or targeted in this post.
title: To
type: array
items: {$ref: '#/definitions/ProfileCollection'}
x-ms-visibility: advanced
type:
description: A string indicating the object type of this post.
type: string
title: Post type
enum: [link, status, photo, video, offer]
x-ms-visibility: advanced
updated_time: {type: string, description: 'The time of the last change to this
post, or the comments on it.', title: Last updated time, x-ms-visibility: advanced}
with_tags: {$ref: '#/definitions/ProfileCollection'}
media:
type: array
items: {description: Url of the media attached to this post. 'Attachments'
field should be specified in a request., type: string, format: uri, title: Attached
media Url, x-ms-visibility: advanced}
AdminItem:
type: object
properties:
id: {description: Unique ID of the admin user., title: User ID, type: integer,
format: int32, x-ms-visibility: advanced}
name: {description: Name of the admin., type: string, title: Admin full name,
x-ms-visibility: advanced}
ProfileCollection:
type: object
properties:
data:
type: array
items: {$ref: '#/definitions/UserItem'}
UserItem:
type: object
x-ms-summary: User
description: Details of a specific Facebook user.
properties:
id: {title: User ID, type: string, description: Unique ID of the user., x-ms-visibility: advanced}
first_name: {title: First name, type: string, description: User first name.,
x-ms-visibility: advanced}
last_name: {title: Last name, type: string, description: User last name., x-ms-visibility: advanced}
name: {title: Full name, type: string, description: User full name., x-ms-visibility: advanced}
gender: {title: Gender, type: string, description: Gender of the user., x-ms-visibility: advanced}
about: {title: User bio, type: string, description: Body of the user's bio page.,
x-ms-visibility: advanced}
PropertyItem:
type: object
properties:
name: {description: The property name., title: Property name, type: string,
x-ms-visibility: advanced}
text: {description: The value of the property., type: string, title: Property
value, x-ms-visibility: advanced}
href: {description: Any link associated with the property., type: string, format: uri,
title: Property link, x-ms-visibility: advanced}
PlaceItem:
type: object
properties:
id: {description: Unique ID of the place, type: string, title: Place ID, x-ms-visibility: advanced}
name: {description: Name of the place, type: string, title: Place name, x-ms-visibility: advanced}
overall_rating: {description: 'Overall rating of place, on a 5-star scale. 0
means not enough data to get a combined rating.', type: number, title: Place
rating, format: float, x-ms-visibility: advanced}
location: {$ref: '#/definitions/LocationItem'}
LocationItem:
type: object
properties:
city: {description: City of the location., type: string, title: City name, x-ms-visibility: advanced}
country: {description: Country of the location., type: string, title: Country
name, x-ms-visibility: advanced}
latitude: {description: Latitude of the location., type: number, title: Latitude,
format: float, x-ms-visibility: advanced}
located_in: {description: The parent location if this location is located within
another location., type: string, title: Located in, x-ms-visibility: advanced}
longitude: {description: Longitude of the location., type: number, title: Longitude,
format: float, x-ms-visibility: advanced}
name: {description: Name of the location., type: string, title: Location name,
x-ms-visibility: advanced}
region: {description: Name of the location region., type: string, title: Region
name, x-ms-visibility: advanced}
state: {description: State which the location is in., type: string, title: State
name, x-ms-visibility: advanced}
street: {description: Street which the location is on., type: string, title: Street
name, x-ms-visibility: advanced}
zip: {description: Location Zip Code., type: string, title: Zipcode, x-ms-visibility: advanced}
PrivacyItem:
required: [value]
type: object
properties:
description: {description: 'Text that describes the privacy settings, as they
would appear in Facebook.', title: Privacy settings description, type: string,
x-ms-visibility: advanced}
value:
description: The value of the privacy setting.
title: Privacy value
type: string
enum: [EVERYONE, ALL_FRIENDS, FRIENDS_OF_FRIENDS, SELF, CUSTOM]
x-ms-visibility: advanced
allow: {description: 'When value is CUSTOM, this is a comma-separated list of
user IDs and friend list IDs that can see the post.', type: string, title: Allowed
users, x-ms-visibility: advanced}
deny: {description: 'When value is CUSTOM, this is a comma-separated list of
user IDs and friend list IDs that cannot see the post.', type: string, title: Denied
users, x-ms-visibility: advanced}
friends:
description: When value is CUSTOM, this indicates which group of friends can
see the post.
type: string
title: Denied friends
enum: [ALL_FRIENDS, FRIENDS_OF_FRIENDS, SOME_FRIENDS]
x-ms-visibility: advanced
FeedTargetItem:
description: Object that controls news feed targeting for this post. Anyone in
these groups will be more likely to see this post, others will be less likely.
Applies to Pages only.
title: News Feed Target
type: object
properties:
geo_locations:
description: This object allows you to specify a number of different geographic
locations.
title: Targetted locations
type: object
properties:
countries:
description: Values of targeting countries.
title: Targetted countries
type: array
x-ms-visibility: advanced
items: {type: string, title: Country code}
regions:
description: Values for targeted regions.
title: Targetted regions keys
type: array
x-ms-visibility: advanced
items: {$ref: '#/definitions/GeoLocationItem'}
cities:
description: Values for targeted cities.
title: Targeted cities keys
type: array
x-ms-visibility: advanced
items: {$ref: '#/definitions/GeoLocationItem'}
zips:
description: Values for targeted locations with specified zip code keys.
title: Targeted zip code keys
type: array
x-ms-visibility: advanced
items: {$ref: '#/definitions/GeoLocationItem'}
x-ms-visibility: advanced
age_min: {description: Must be 13 or higher., title: Minimum age, type: integer,
format: int32, x-ms-visibility: advanced}
age_max: {description: Maximum Age., title: Maximum age, type: integer, format: int32,
x-ms-visibility: advanced}
genders:
description: Target specific genders. 1 targets all male viewers and 2 females.
Default is to target both.
title: Targetted genders
type: array
x-ms-visibility: advanced
items: {type: integer, title: Gender code. Use 1 for male and 2 for female.,
format: int32}
relationship_statuses:
description: Array of integers for targeting based on relationship status.
title: Targetted relationship statuses
type: array
x-ms-visibility: advanced
items: {type: integer, title: 'Relationship status. Use 1 for single, 2 for
''in a relationship'', 3 for married, and 4 for engaged.', format: int32}
interested_in:
description: Indicates targeting based on the 'interested in' field of the
user profile.
title: Targetted interests
type: array
x-ms-visibility: advanced
items: {type: integer, title: 'Interest code. Use 1 to indicate male, 2 indicates
female.', format: int32}
college_years:
description: Array of integers for graduation year from college.
title: Targetted college graduation year
type: array
x-ms-visibility: advanced
items: {type: integer, title: Graduation year, format: int32}
education_statuses:
description: Array of integers for targeting based on education level.
title: Targetted education statuses
type: array
x-ms-visibility: advanced
items: {type: integer, title: 'Education status code. Use 1 for high school,
2 for undergraduate, and 3 for alum (or localized equivalents).', format: int32}
locales:
description: Targeted locales.
title: Targetted locales
type: array
x-ms-visibility: advanced
items: {type: integer, title: Locale code, format: int32}
GeoLocationItem:
type: object
properties:
key: {description: Target location item's key., title: Location key, type: string,
x-ms-visibility: advanced}
UserPostFeedRequest:
required: [message]
type: object
properties:
message: {description: 'The main body of the post, otherwise called the status
message.', type: string, title: Status message}
link: {description: The URL of a link to attach to the post., type: string,
format: uri, title: Post link, x-ms-visibility: advanced}
picture: {description: Determines the preview image associated with the link.,
type: string, format: uri, title: Link image, x-ms-visibility: advanced}
name: {description: Overwrites the title of the link preview., type: string,
title: Link name, x-ms-visibility: advanced}
caption: {description: Overwrites the caption under the title in the link preview.,
type: string, title: Link caption, x-ms-visibility: advanced}
description: {description: Overwrites the description in the link preview.,
type: string, title: Link description, x-ms-visibility: advanced}
place: {description: Page ID of a location associated with this post., type: string,
title: Post location, x-ms-visibility: advanced}
tags: {description: Comma-separated list of user IDs of people tagged in this
post., type: string, title: Tagged users, x-ms-visibility: advanced}
privacy: {$ref: '#/definitions/PrivacyItem'}
object_attachment: {description: Facebook ID for an existing picture in the
person's photo albums to use as the thumbnail image., type: string, title: Thumbnail
picture ID, x-ms-visibility: advanced}
PostFeedResponse:
type: object
x-ms-summary: Posted Item
description: Details of the item posted to the feed.
properties:
id: {type: string, title: Post ID}
PagePostFeedRequest:
required: [message]
type: object
properties:
message: {description: 'The main body of the post, otherwise called the status
message.', type: string, title: Status message}
link: {description: The URL of a link to attach to the post., type: string,
format: uri, title: Post link, x-ms-visibility: advanced}
picture: {description: Determines the preview image associated with the link.,
type: string, format: uri, title: Link image, x-ms-visibility: advanced}
name: {description: Overwrites the title of the link preview., type: string,
title: Link name, x-ms-visibility: advanced}
caption: {description: Overwrites the caption under the title in the link preview.,
type: string, title: Link caption, x-ms-visibility: advanced}
description: {description: Overwrites the description in the link preview.,
type: string, title: Link description, x-ms-visibility: advanced}
actions:
description: The action links attached to the post.
type: array
items: {$ref: '#/definitions/ActionItem'}
title: Action links
x-ms-visibility: advanced
place: {description: Page ID of a location associated with this post, type: string,
title: Post location, x-ms-visibility: advanced}
tags: {description: Comma-separated list of user IDs of people tagged in this
post., type: string, title: Tag users, x-ms-visibility: advanced}
object_attachment: {description: Facebook ID for an existing picture in the
person's photo albums to use as the thumbnail image., type: string, title: Thumbnail
picture ID, x-ms-visibility: advanced}
targeting: {$ref: '#/definitions/TargetItem'}
feed_targeting: {$ref: '#/definitions/FeedTargetItem'}
published: {description: Whether a story is shown about this newly published
object., type: boolean, title: Publish post., x-ms-visibility: advanced}
scheduled_publish_time: {description: 'Time when this post should go live, this
can be any date between ten minutes and six months from the time of the
API call.', type: string, format: date-time, title: Schedule publish time,
x-ms-visibility: advanced}
backdated_time: {description: Specifies a time in the past to back-date this
post to., type: string, format: date-time, title: Back date time., x-ms-visibility: advanced}
backdated_time_granularity:
description: Controls the display of how a backdated post appears.
type: string
title: Backdated time display format.
enum: [year, month, day, hour, minute]
x-ms-visibility: advanced
child_attachments:
description: 'Use to specify multiple links in the post. '
type: array
items: {$ref: '#/definitions/ChildAttachmentsItem'}
title: Attachments
x-ms-visibility: advanced
multi_share_end_card: {description: 'If set to false, does not display the end
card of a carousel link post when child_attachments is used.', type: boolean,
title: Multi-share end card, x-ms-visibility: advanced}
ActionItem:
type: object
properties:
name: {description: The name or label of the action link., title: Action link
name, type: string, x-ms-visibility: advanced}
link: {description: The URL of the action link itself., type: string, title: Action
link, x-ms-visibility: advanced}
TargetItem:
type: object
properties:
geo_locations:
description: This object allows you to specify a number of different geographic
locations.
title: Targetted locations
type: object
properties:
countries:
description: Values of targeting countries.
title: Targetted countries
type: array
x-ms-visibility: advanced
items: {type: string, title: Country code}
regions:
description: Values for targeted regions.
title: Targetted regions keys
type: array
x-ms-visibility: advanced
items: {$ref: '#/definitions/GeoLocationItem'}
cities:
description: Values for targeted cities.
title: Targeted cities keys
type: array
x-ms-visibility: advanced
items: {$ref: '#/definitions/GeoLocationItem'}
x-ms-visibility: advanced
locales:
description: Targeted locales.
title: Targetted locales
type: array
items: {type: integer, title: Locale code, format: int32}
x-ms-visibility: advanced
ChildAttachmentsItem:
type: object
properties:
link: {description: The URL of a link to attach to the post., title: Attachment
link, type: string, x-ms-visibility: advanced}
picture: {description: 'Determines the preview image associated with the link
(1:1 aspect ratio and a minimum of 458 x 458 px for best display).', title: Link
picture, type: string, format: uri, x-ms-visibility: advanced}
image_hash: {description: 'Hash of a preview image associated with the link
from your ad image library (1:1 aspect ratio and a minimum of 458 x 458
px for best display).', title: Image hash, type: string, x-ms-visibility: advanced}
name: {description: The title of the link preview., title: Link name, type: string,
x-ms-visibility: advanced}
description: {description: 'Used to show either a price, discount or website
domain.', title: Link description, type: string, x-ms-visibility: advanced}
TriggerFeedResponse:
x-ms-summary: Timeline Feed
description: List of newly created posts.
type: object
properties:
data:
type: array
items: {$ref: '#/definitions/TriggerItem'}
x-ms-summary: Response Data
TriggerItem:
x-ms-summary: Feed Item
description: An individual entry in a profile's feed. The profile could be a user,
page, app, or group.
type: object
properties:
id: {description: The post ID., type: string, title: Post ID}
created_time: {description: 'The time the post was initially published. For
a post about a life event, this will be the date and time of the life event.',
type: string, title: Created Time, x-ms-visibility: advanced, format: date-time}
from: {$ref: '#/definitions/UserItem'}
message: {description: The status message in the post., type: string, title: Status
message}
type:
description: A string indicating the object type of this post.
type: string
title: Post Type
enum: [link, status, photo, video, offer]
x-ms-visibility: advanced
picture: {description: The picture scraped from any link included with the post.,
type: string, format: uri, title: Image url, x-ms-visibility: advanced}
link: {description: The link attached to this post., type: string, format: uri,
title: Link url, x-ms-visibility: advanced}
name: {description: The name of the link., type: string, title: Name}
description: {description: A description of a link in the post (appears beneath
the caption)., type: string, title: Link description, x-ms-visibility: advanced}
media:
type: array
items: {description: Url of the media attached to this post., type: string,
format: uri, title: Attached media Url, x-ms-visibility: advanced}
produces: []
responses: {}
schemes: [https]
security:

oauth2_auth: [user_posts]
securityDefinitions:
oauth2_auth:
type: oauth2
flow: accessCode
authorizationUrl: https://graph.facebook.com/oauth/authorize
tokenUrl: https://login.windows.net/common/oauth2/authorize
scopes: {user_posts: user_posts}
swagger: '2.0'
tags: []
`

but then I don't have the Get page Access token action, and it fails as the following:

@williamwatfeh Can you please send me the swaggerfile as an attachment.?

Out of interest, I am seeing the exact same issue here.  :(

@williamwatfeh @abhishekpalit09

The initial issue issue can be resolved by removing the "Accept" Parameter
Then use Paconn cli to deploy your connector Instead of importing the SwaggerFile. Because the current Facebook Connector uses Policies to append the pagetoken to the request. Please try and let me know if you still have any issues.

CC : @mamurshe

We released the Facebook connector as starting point. All of the validator tools are also available for testing this. Please feel free to fix and release for the opensource community if you need this connector.


Add UI mockup

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (890b1d4) compared to base (c1acb36).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #33   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

lgtm


[DSpace 7 Upgrade] Reimplement RDF map collections and communities metadata

Original PR: https://github.com/TAMULib/DSpace/pull/155

At some point, the DSpace RDF app will have to be configured and a triple store (fuseki) set up.
https://github.com/TAMULib/DSpace/pull/103/files
https://wiki.lyrasis.org/display/DSDOC7x/Linked+(Open)+Data


Support packages with extension modules

The tool currently only supports noarch pacakges, the noarch thing is hardcoded in the template. It would be nice if it also supported packages with extension modules - those are archful and usually need at least gcc to build.

Taking a look at Packaging Guidelines and some arched spec files this is needed in template.spec:

if package is not arched, print the line BuildArch: noarch (that'd be the default)
otherwise (set by a flag) the line wouldn't be printed to the spec file

Also, it could be possible to define ExcludeArch: and ExclusiveArch: in the config.
It's already possible to define custom BuildRequires: in addition to the generated ones.
Will it be enough to make it working?

I suppose the conf2spec tool needs a way to say we don't want noarch (I would not bother with ExcludeArch: and ExclusiveArch:) and a way to say we need gcc (the option already exists).
For automated rebuilds to work, the pyp2conf tool would need to detect this and add the proper config options.


Update find command

Find contacts by name, company, job title, addresses, phone, emails or tags.
Field must be specified using the prefix otherwise find will not search anything.
Currently a user can search only through one field at a time.

Codecov Report

Merging #62 (d3d28ef) into master (a00b9ad) will decrease coverage by 6.60%.
The diff coverage is 55.00%.

@@             Coverage Diff              @@
##             master      #62      +/-   ##
============================================
- Coverage     72.15%   65.55%   -6.61%
- Complexity      399      515     +116
============================================
  Files            70       85      +15
  Lines          1232     1745     +513
  Branches        125      203      +78
============================================
+ Hits            889     1144     +255
- Misses          311      544     +233
- Partials         32       57      +25

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

.../main/java/seedu/address/commons/core/Version.java
82.50% <ø> (ø)

...n/java/seedu/address/commons/core/index/Index.java
90.90% <0.00%> (-9.10%)
:arrow_down:

...in/java/seedu/address/commons/util/StringUtil.java
51.42% <0.00%> (-43.31%)
:arrow_down:

...ss/logic/commands/exceptions/CommandException.java
100.00% <ø> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
100.00% <ø> (ø)

...a/seedu/address/logic/parser/ArgumentMultimap.java
60.00% <0.00%> (-40.00%)
:arrow_down:

.../seedu/address/logic/parser/ArgumentTokenizer.java
97.36% <ø> (ø)

...c/main/java/seedu/address/logic/parser/Prefix.java
91.66% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
97.91% <0.00%> (-2.09%)
:arrow_down:

... and 48 more

Continue to review full report at Codecov.

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


Update number of lint rules

Summary
While reading the Japanese documentation today, I noticed that the numbers of lint rules in each README are outdated.
I have updated them accordingly.

Thank you!


Allow "like" search query

Currently using this list of items:

V1001
P1001
1001
Basic
and entering 100 in the search field, only 1001 will be returned.
When entering `asic, Basic wil not be returned.

I have looked #28 but could not find the proper "token" for what I am looking for.
I wonder if there is a configuration setting allowing the like searchers.
I've tried wrapping the query value between * à la Lurnr.js but I think those are escaped by ItemsJS.
Thanks.

The idea seems useful. Is the like feature '*' supported by lunr.js ?

There is a notion of wildcards if this can help: https://lunrjs.com/guides/searching.html

Thanks. We'll need to upgrade Lunr.js from 1.0 to the newest 2.x soon. Fortunately API seems almost the same https://lunrjs.com/guides/upgrading.html so upgrading should not be a problem.
Additional features will be available by default then i.e. wildcard, boosting or searching by field
One change which I see will be:

The behaviour of the search has changed slightly, multi-term searches are now combined with OR, where they used to be combined with AND.
Practically this change means that a given search will return more documents in 2.x than it did previously, with the most relevant results returned first.

Not sure yet if this change will be good or not

@regisphilibert you can use Lunr 2.x (or plenty of others) by custom integration. Example is here https://github.com/itemsapi/itemsjs/blob/master/docs/lunr2-integration.md. Thanks to that you have full control over search features (wildcards, etc)


Enabled Sentinel analytic rules "Description" field to be imported with importAzureSentinelRules.ps1

Is your feature request related to a problem? Please describe.
When I used the importAzureSentinelRules.ps1 script to import the analytic rules to Sentinel, it did not import the "Description" field value although it was correctly exported and present in the Scheduled.json file.
When looking at the script, I can see that there is this line:
if ($Description) { $NewRuleObject.Description = $Description }
But it still did not import the description values.
Describe the solution you'd like
I would like to the importAzureSentinelRules.ps1 script to import the analytic "Description" value.
@tianderturpijn or anyone from the Sentinel team, could you please try to replicate this and see if you are having the same issue?
Thanks, Ludek

Closing this feature request as this is most likely a bug. I will open a new bug issue for this.


Can't Relative Abundance take ‘estimate-unknown’ into account?

Thank you for developing such a wonderful tool!
When comparing the relative abundance of species obtained using sylph, I would like to take into account unknown sequences.
However, the current -u option is only valid for sequence abundance and cannot be applied to relative abundance.
If there is a way to take the -u option into account for relative abundance, please let me know.
Or is it not appropriate to apply the -u option to relative abundance?

@HirokiK0 this is a mathematical issue. Taxonomic abundance depends in the size of the genomes. If the "unknown" genomes have small or large length, this would shift the percentage of unknown sequences.
So we don't scale taxonomic abundance by unknown content. You are free to multiply it by the percentage of unknown content, just like with sequence abundance... although this is not mathematically valid, but it's usually OK.


[QUESTION] how to change healthesp position ingame

Hello,
I'm asking if it's possible to change the healthesp position both in the X axis and the Y axis.
I was able to change the X axis in game by typing this
renderPositionedText(209, (std::to_wstring(entity->health()) + L" HP").c_str(), { bbox.x1 + config.hpposx , drawPositionY });
in Misc.cpp, you can find it by searching "config.health.enabled"
I tried doing the same by writing drawPositionY + config.hpposy but it gave me errors.
More info:
float hpposx{ 0.0f };
float hpposy{ 0.0f };
in Config.h under "float maxDistance"
and
ImGui::SliderFloat("hp esp pos x", &config.esp.players[selected].hpposx, -100.0f, 100.0f, "%.2f Hp pos X");
ImGui::SliderFloat("hp esp pos y", &config.esp.players[selected].hpposy, -100.0, 100.0f, "%.2f Hp pos Y");
in GUI.cpp, you can find it by searching "void GUI::renderEspWindow"
if anyone finds the solution, thanks a lot!

Inside renderPlayerBox in ESP.cpp:
replace this:
renderPositionedText(config.font, (std::to_wstring(entity->health()) + L" HP").c_str(), { bbox.x1 + 5, drawPositionY });
with this:
const auto [width, height] { interfaces->surface->getTextSize(config.font, (std::to_wstring(entity->health()) + L" HP").c_str()) };
float drawPositionYy = bbox.y1 - 5 + height;
renderPositionedText(config.font, (std::to_wstring(entity->health()) + L" HP").c_str(), { (bbox.x0 + bbox.x1 - width) / 2, drawPositionYy });
health value is now below the character

thanks


Github CI should use vanilla Lua instead of LuaInternals

We should sort this out after we figure out how to make the CI run in the first place.

@hugomg should we go with Lua from the package manager of ubuntu-latest?

I think we can keep compiling from source.
For Lua that's simple enough, and it gives us more control over the exact version.


nixos: use structured attrs for assertions/warnings

Description of changes

This PR reworks the assertions module to take a freeform tree-like structure for assertions and warnings. This has one major advantage over the existing list structure, which is the ability for a downstream user to forcefully disable an assertion or warning they believe to be erroneous without needing to resort to any tricky hacks. It might also open up for ideas where we could add more metadata or properties to the assertions/warnings, like different types of warnings or whether the message should be lazily evaluated. It will also let you extract the tree structure of non-firing warnings/assertions for whatever kinds of research purposes you might need it for. I don't suspect that an entire manual appendix of warnings/assertions is particularly useful, but maybe the data is useful for some?
Example
Here is an example of the old and new way to write assertions and warnings:
# Old
{
  warnings = lib.mkIf config.services.foo.bar [
    "Some example warning"
  ];

  assertions = [{
    assertion = config.services.foo.baz;
    message = ''
      You forgot to enable baz.
    '';
  }];
}

# New
{
  warnings.services.foo.beCarefulWithBar = {
    # ⬐ New option for storing the boolean that triggers the warning
    condition = config.services.foo.bar;
    message = "Some example warning";
  ];

  assertions.services.foo.makeSureToEnableBaz = {
    assertion = config.services.foo.baz;
    message = ''
      You forgot to enable baz.
    '';
  };
}

If the user believes either of these to be an error in nixpkgs, they should of course make an issue first, but in the meanwhile they can do this:
{
  warnings.services.foo.beCarefulWithBar.enable = false;
  assertions.services.foo.makeSureToEnableBaz.enable = false;
}

Backwards compatibility
The module takes any existing assertions/warnings that are declared as lists, and coerces them to the new format under {assertions,warnings}.legacy.<sha256-sum of message string>. While this makes them a bit harder to disable, it ensures a smooth transition. While assertions and warnings are marked with internal = true, I believe a lot of people are using them for out-of-tree modules. I have explicitly opted out of adding a note to the release docs, but I have changed the nixos manual.
Other things worth mentioning, and maybe discussing

This PR depends on https://github.com/NixOS/nixpkgs/pull/342330

I've modified some of the core modules and library functions to use the new scheme, in addition to a few modules with a large set of assertions/warnings as a proof of concept.

There is obviously no established scheme for the naming or namespacing of assertions and warnings. I've tried naming them roughly to reflect what they are warning about and what they are trying to assert, but I'm very open for changes and/or standardisation of some kind of scheme.

Should we consider making these options non-internal, considering widespread use outside nixpkgs?

Due to typechecking of the assertion/warning submodule, the message strings will now become non-lazy. In one way, that's a good thing because we get to typecheck the messages. On another hand, there are some message strings that depend on their boolean error condition to make any sense (e.g if the assertion asserts that a setting should not be set, the message might refer to the content of that setting without any regard for what happens if the setting is not there). The warning mkIfs handle this properly, but the assertions might not. I'm not sure whether we should try to hunt these down, or make typechecking opt-in, or how to go about this? Building all the nixos tests is a good start I suppose.

Some assertions and warnings have been slightly modified to fit better with the new system. Some assertions and warnings that earlier were aggregated have been split up to be separate assertions.

I'm not sure about the evaluation speed impact of all the coercion stuff I've added. It doesn't seem much slower on my PC, but I haven't made any measurements.

There might be a case where identical assertions that were earlier part of the assertion list can have differing boolean values while still getting the same hash. I believe this could trigger an eval error where the same option is set to differing values? I'm not sure if we should handle those cases as they come and move towards the new format, or try to handle it with something like lib.types.boolByOr

Testing
I've only done basic testing, opening a nix repl and evaluated attributes as follows:
# Using traceValSeqN for some reason has the sideeffect of pretty printing,
# in contrast to some of the other trace functions
nix-repl> lib.traceValSeqN 40 legacyPackages.x86_64-linux.nixosTests._3proxy.config.nodes.peer0.assertions

... # Too much here, it's the entire expanded tree of all assertions

{
  boot = { ... };
  console = { ... };
  documentation = { ... };
  environment = { ... };
  fileSystems = { ... };
  fonts = { ... };
  hardware = { ... };
  i18n = { ... };
  krb5 = { ... };
  legacy = { ... };
  nesting = { ... };
  networking = { ... };
  nix = { ... };
  programs = { ... };
  security = { ... };
  services = { ... };
  sound = { ... };
  stubby = { ... };
  systemd = { ... };
  users = { ... };
  virtualisation = { ... };
  xdg = { ... };
  zramSwap = { ... };
}

nix-repl> lib.traceValSeqN 40 legacyPackages.x86_64-linux.nixosTests._3proxy.config.nodes.peer0.warning

... # Expanded tree here as well

{
  boot = { ... };
  docker-containers = { ... };
  documentation = { ... };
  environment = { ... };
  fonts = { ... };
  hardware = { ... };
  i18n = { ... };
  jobs = { ... };
  legacy = { ... };
  networking = { ... };
  nix = { ... };
  programs = { ... };
  qt5 = { ... };
  security = { ... };
  services = { ... };
  snapraid = { ... };
  system = { ... };
  systemd = { ... };
  unifi-poller = { ... };
  users = { ... };
  virtualisation = { ... };
}

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Can't review right now, but I already have some (incomplete) thoughts:

If you haven't already, please read / be aware of https://github.com/NixOS/nixpkgs/pull/97023
It was reverted because triggering the checks at the right time is tricky. I don't think this PR changes that, which is good, but it may have other design aspects that could be interesting.
Disabling whole trees of checks mkIf- or enable-style (or similar) will be good for laziness / performance and module DX
We may consider not to translate existing checks into the new structure, but just trigger two independent check systems
I've said checks to generalize assertions and warnings just now, but maybe we want to reserve that term for derivations that check things (for example, checks as in flakes, or system.checks in NixOS)

ofborg seems to fail due to an assertion message that is now being evaluated eagerly. It is building nixos-vm, which causes the failure.
$ nix-instantiate --arg nixpkgs ./. ./pkgs/top-level/release.nix -A unstable

...

… while evaluating definitions from `/home/h7x4/nixpkgs/nixos/modules/misc/nixpkgs.nix':

… while evaluating the option `nixpkgs.localSystem':

… while evaluating the option `nixpkgs.system':

nixosExpectedSystem (due to config.nixpkgs.localSystem.config) here causes the failure.
# nixos/modules/misc/nixpkgs.nix:354
let
  nixosExpectedSystem =
    if config.nixpkgs.crossSystem != null
    then config.nixpkgs.crossSystem.system or (lib.systems.parse.doubleFromSystem (lib.systems.parse.mkSystemFromString config.nixpkgs.crossSystem.config))
    else config.nixpkgs.localSystem.system or (lib.systems.parse.doubleFromSystem (lib.systems.parse.mkSystemFromString config.nixpkgs.localSystem.config));
  nixosOption =
    if config.nixpkgs.crossSystem != null
    then "nixpkgs.crossSystem"
    else "nixpkgs.localSystem";
  pkgsSystem = finalPkgs.stdenv.targetPlatform.system;
in {
  assertion = constructedByMe -> !hasPlatform -> nixosExpectedSystem == pkgsSystem;
  message = "The NixOS nixpkgs.pkgs option was set to a Nixpkgs invocation that compiles to target system ${pkgsSystem} but NixOS was configured for system ${nixosExpectedSystem} via NixOS option ${nixosOption}. The NixOS system settings must match the Nixpkgs target system.";
}

Eventually leading to triggering the throw in nixpkgs.system
# nixos/modules/misc/nixpkgs.nix:283
system = lib.mkOption {
  type = lib.types.str;
  example = "i686-linux";
  default =
    if opt.hostPlatform.isDefined
    then
      throw ''
        Neither ${opt.system} nor any other option in nixpkgs.* is meant
        to be read by modules and configurations.
        Use pkgs.stdenv.hostPlatform instead.
      ''
    else
      throw ''
        Neither ${opt.hostPlatform} nor the legacy option ${opt.system} has been set.
        You can set ${opt.hostPlatform} in hardware-configuration.nix by re-running
        a recent version of nixos-generate-config.
        The option ${opt.system} is still fully supported for NixOS 22.05 interoperability,
        but will be deprecated in the future, so we recommend to set ${opt.hostPlatform}.
      '';
  defaultText = lib.literalMD ''
    Traditionally `builtins.currentSystem`, but unset when invoking NixOS through `lib.nixosSystem`.
  '';
  ...
};

Sorry to ping you about this @roberth, but I could really use some help to decide how to go about this. I currently see 3 possible solutions:

Rewrite the assertion message or somehow should rewrite nixosExpectedSystem to not refer to nixpkgs.system (not sure where to start, or whether this even inherently makes sense)
Add a lazy bool option to assertion/warning to allow for disabling type checking/eval of message
Disable this part of the eval test or somehow modify it to set nixpkgs.system so it doesn't throw (however, I'm not sure what implications this has, but it doesn't seem very desirable).

I've verified that the command (and then probably also ofborg) evaluates completely if I remove ${nixosExpectedSystem} from the message.

I see that you're trying to do a good job with thorough checking, which as a fan of good DX and static checking, I can very much relate to. However, the module system is very different from most other languages or configuration systems, by virtue of its fairly unique architecture, doing runtime checks in a lazy language. This has profound implications for the implementation trade-offs.
The module system is very sensitive when it comes to the specifics of its behavior, especially regarding strictness (laziness). It is very important for it to be as lazy as possible, so that it avoids running into errors that shouldn't be triggered, or infinite recursions.
We also need to care for users who write their own modules with assertions and warnings. By forcing them to migrate their code immediately, you put them in a position where they have to choose whether to support NixOS stable or unstable. This isn't great for end users, but particularly problematic for maintainers who need their module to work on both releases. For this reason, we can't accept an immediate breaking change in the assertions/warnings type. However, this can be resolved by translating list-based definitions to attributes like "anon-${i}".
For this you need something like coercedTo but using imap instead of map in the merge function.

Rewrite the assertion message or somehow should rewrite nixosExpectedSystem to not refer to nixpkgs.system (not sure where to start, or whether this even inherently makes sense)

As said, we must not regress in laziness, so this should be solved in the module system; not the code that uses the module system.

Add a lazy bool option to assertion/warning to allow for disabling type checking/eval of message

Lazy and unchecked are fast. The module system will check the message because it's a submodule anyway; just later than you envisaged. This will make it run a bit faster, and a bit more reliably.
Ideally infrequently used values, like the message, are checked in a static way, such as with a test. Anything that's important is worth testing.

Disable this part of the eval test or somehow modify it to set nixpkgs.system so it doesn't throw (however, I'm not sure what implications this has, but it doesn't seem very desirable).

That module already needs to balance complicated compatibility and error reporting at the cost of basically no simplicity and very little room to spare in terms of making literally anything more strict. I would be happy to review or discuss changes that improve the end user experience of that module, which I believe is still possible, but I feel like this may be the wrong reason.
I don't know if you've studied it in detail; if not, it's probably best to that module untouched and solve the problem in the module system itself.
I hope my earlier suggestion helps to make it work again.

Okay, so I've had another go at it. Turns out that the message was evaluated in 3 places:

While being typechecked by the module system

This was expected, mitigated by adding the lazy option, which disables typechecking and preserves lazyness. This is not needed for warnings, because all legacy warnings already are behind a mkIf or similar. I've added a note recommending people not to enable it unless absolutely necessary, so we can typecheck as much as possible, as well as a warning stating that you should make sure to verify the message yourself if you do end up enabling it. I would count the nixpkgs.config assertion as a location where it's necessary.
All legacy options are lazy by default to ensure we don't break any out-of-tree modules.

During coercion while being hashed before being added to assertions.legacy

This is the most problematic part. We can't hash the message without evaling the message. Currently, I've switched to using the lib.imap0 (i: ... "anon-${toString i}") strategy, but the indices will shift everytime someone adds/removes an anonymous assertion and so you cannot disable an assertion in a stable manner. I'm tempted to make assertions.legacy into a list and handle it separately, but that might just add more convoluted coercion handling with little added value. We could also run through all legacy assertions, check if the user has disabled them and warn them that this is unstable?
I am also not sure how much I should strive to make this common with warnings. For warnings, there shouldn't be any problem with using the hashString approach, and it would make for a stable interface to let users disable legacy warnings. Is this property more important than similarity to legacy assertions?

While running the collect' before displaying warnings in nixos/modules/system/activation/top-level.nix

The collect' would further recurse into the attrset if the condition didn't trigger, and accidentally evaluate the message. I've made a custom version of collect' that has a stop condition when it finds something that looks like an assertion but is marked as lazy. The use for this function seems fairly niche, so I haven't added it to lib.attrsets, but I'd be happy to do so if someone asks. warnings still uses lib.collect'


[FEATURE] DeepSeek V2 Chat Support

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
https://github.com/AutoGPTQ/AutoGPTQ/issues/664

@LRL-ModelCloud  has been assigned to this task.  Model has been downloaded and work should be completed soon.

@LRL-ModelCloud has been assigned to this task. Model has been downloaded and work should be completed soon.

Can you provide a quantified model for DeepSeek V2 Chat? I encountered an OOM error during the quantization process

What gpu model did you use for deepseek v2 quant? I want to check if the oom is code related or just because deepseek v2 is a little special and requires more vram.

@Xu-Chen What gpu model did you use for deepseek v2 quant? I want to check if the oom is code related or just because deepseek v2 is a little special and requires more vram.

File "/home/root/.local/lib/python3.10/site-packages/gptqmodel/models/base.py", line 258, in quantize
    move_to(module, cur_layer_device)
  File "/home/root/.local/lib/python3.10/site-packages/gptqmodel/utils/model.py", line 66, in move_to
    obj = obj.to(device)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1173, in to
    return self._apply(convert)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 804, in _apply
    param_applied = fn(param)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1166, in convert
    raise NotImplementedError(
NotImplementedError: Cannot copy out of meta tensor; no data! Please use torch.nn.Module.to_empty() instead of torch.nn.Module.to() when moving module from meta to a different device.

quant  code
  quantize_config = QuantizeConfig(
        true_sequential=False,
        bits=4,
        group_size=group_size,
        desc_act=desc_act
    )
    max_memory = {i: "75GB" for i in range(8)}
    model = GPTQModel.from_pretrained(
        args.model_id,
        quantize_config,
        trust_remote_code=True,
        device_map="sequential",
        attn_implementation="eager",
        torch_dtype=torch.bfloat16,
        max_memory=max_memory)
    model.quantize(examples)

Is it not possible to use the GPU to load the model?

vram

delete max_memory=max_memory can run.
Is there a way to use the GPU to load the model and then perform parallel quantization to improve the quantization speed?

Remove all options and use just the base. GPTQModel will select the best dtype and accelerate will auto handle model weight splits.
  model = GPTQModel.from_pretrained(
        args.model_id,
        quantize_config,
  )


Ensure MTU is set correctly when WireGuard interface already exists

In ce46eb1e2cde ("Fix incorrect MTU configurations"), we changed WireGuard interface's MTU in IPv4 case. However, if a cluster already enables WireGuard, the WireGuard interface's MTU would remain unchanged while new Pod would use a higher MTU, causing problems.

/skip-all


Warning: The "to" argument must be of type string.

Setup:

Windows 10
Node v10.15.3
npm 6.4.1
yarn 1.16.0
grunt 1.0.4

Gruntfile.js
module.exports = function(grunt) {
   require('load-grunt-tasks')(grunt);

   grunt.initConfig({

    babel: {
         dist: {
            files: {
               'js/app.js': 'js/app-compiled.js'
            }
         }
      },
   });

   grunt.registerTask("build", ["babel",]);
}

When i enter "grunt build" i receive respond:
Warning: The "to" argument must be of type string. Received type undefined Use --force to continue.
and only this. What is a "to" argument and why it isn't be of type string? After all this is taken from the example and does not work.

facing the same issue
"babel-core": "^6.26.3",
"babel-preset-env": "^1.7.0",
"grunt": "^1.0.3",
"grunt-babel": "^7.0.0"

@RiddickAbaddon I'm not sure if you realized it already, but i realized it shortly after i posted here. The source file was not created. In my case, I was using concat first and the output from concat didnt create a file. therefore, babel didn't find any file to work with. not sure if this is the same issue you have, but once i had the file in place, everything went fine.

The previous comment solved it for me, wasn't too obvious the format was supposed to be 'destination-name.js : source-name.js'

In summary: this error is talking about the source file. If the error states that received type is undefined then it couldn't find the source file you specified. As with the other commenters, it's usually a matter of double-checking that your path string is correct. In my case, I was skipping over a subdirectory—added it an fixed the problem.

Yes, this is it. I confused the name of the source file with the resulting one. Thank you all


Build fails on Windows

copy /y E:/Dev/Bacon2D/src/PhysicsEntity.qml E:/Dev/Bacon2D/src/BoxBody.qml E:/Dev/Bacon2D/src/ChainBody.qml E:/Dev/Bacon2D/src/CircleBody.qml E:/Dev/Bacon2D/src/EdgeBody.qml E:/Dev/Bacon2D/src/ImageBoxBody.qml E:/Dev/Bacon2D/src/PolygonBody.qml E:/Dev/Bacon2D/src/Boundaries.qml E:/Dev/Bacon2D/src/RectangleBoxBody.qml E:/Dev/Bacon2D/src/qmldir E:/Dev/Bacon2D-Debug/src/imports/Bacon2D/
The syntax of the command is incorrect.

I think that the problem is here:
qmlplugin.commands = $$QMAKE_COPY $$QMLFILES $$OUT_PWD/imports/Bacon2D/
qmlplugin.path = $$target.path

Windows requires backslashes for its paths, but its copy command also doesn't seem to be able to take multiple files.
I'm not very good with qmake, but the INSTALLS variable as documented here seems to already take care of producing a valid copy command on all supported platforms, so the .commands stuff shouldn't be necessary:
qmlplugin.path = $$target.path
qmlplugin.files = $$QMLFILES

You might also be able to use the for loop approach shown here somehow, in combination with shell_path.

I'm also willing to test out potential fixes, or submit them with some guidance. This issues is preventing me from a patch I'm working on for the examples.

@mitchcurtis I have a branch that may fix this, but I suspect there might be more similar issues.  Please test https://github.com/kenvandine/Bacon2D/tree/windows_qmake

Thanks for the bug report, should be fixed now.  I've built this on Windows 8.1 with Qt 5.4 and successfully ran some examples.  If you create a game, please share it and your experiences on our G+ community https://plus.google.com/u/0/communities/104485147844809689114

Yep, that fixes it. Thanks. :)


install-cni-plugin.sh erroneous

You reference a shell script for Linux, "install-cni-plugin.sh", but the file is not a shell script.
It is an HTML document.
I tried several different links already, and I downloaded it several different times.
The links do not point to a downloadable Linux shell script.
Any help would be greatly appreciated.
Joe F.

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

ID: d73b15b3-be21-46bb-f5a4-04ef9d03cb08
Version Independent ID: bcbdfb51-8092-735d-83da-77c0ae1adb0a
Content: Deploy Azure virtual network container networking
Content Source: articles/virtual-network/deploy-container-networking.md
Service: virtual-network
GitHub Login: @aanandr
Microsoft Alias: aanandr

@jxfish2 - you have to copy the script content that you see on that page into a text file, save it and rename it per the guidance provided in the documentation link above. It will then be ready to run. Did you try these steps?

@jxfish2 Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue

@TravisCragg-MSFT jxfish is right, this is not the way to doc things for linux folks - the URL should refer to the RAW version (specifically https://raw.githubusercontent.com/Azure/azure-container-networking/master/scripts/install-cni-plugin.sh) then folks would execute their prefered way to get that (usually wget and less frequently curl) to get the file xhmod with +x and run it


updated code to use version <IP_ADDRESS>

Updated the code to use version <IP_ADDRESS>

Wow, that's great, thanks for your contribution @franva! Will give it a try in a minute but looks good at a first glance

@Erol444 I just updated that and it works without issues on my end

wow so efficient guys~! I just walked out to pick up my stuff and back to home saw this all done haha.
Great team work~!

hi @Erol444 and @VanDavv
Just a question, since version <IP_ADDRESS> already included wheels for opencv-python and opencv-contrib-python,
should we remove these 2 packages from the requirements.txt?

Hello @franva , I don't think the library itself has these dependencies, just the depthai_demo. Could you elaborate, please?
Thanks, Erik


LandingPage: End of text lines showing strange characters

Probably when the database merge happened. Please check if this is represented in the CMS. If so, remove extra characters. If in code, remove and review why/how this happened so we know in the future (making sure it doesn't happen when pushing builds, etc.)

This is a database issue. I will look into it.

just flagging this is still a thing. It isn't appearing in CMS nor could I find it in code.

this is a priority before monday just fyi


⚠ SceneTime has degraded performance

In ad956bc, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1065 ms

Resolved: SceneTime performance has improved in 1fcf6c1 after 7 minutes.


[FLINK-9486] Introduce TimerState in keyed state backend

What is the purpose of the change
This PR integrates InternalTimerQueue with keyed state backends (Heap and RocksDB), so that we can use the RocksDB-based version in the job for the first time.
We introduce the interface KeyGroupPartitionedPriorityQueue as an easy adapter to existing snapshotting code. This can probably be removed once the queues are fully integrated with the backend's snapshotting, in a followup PR.
The PR also addresses an issue with the TreeOrderedCache that requires a "proper" Comparator (implemented in TieBreakingPriorityComparator) and we introduce PriorityComparator to give more emphasize to this difference. TieBreakingPriorityComparator is likely to also go away once we come up with an improved caching that is not simply based on a tree that requires an aligned comparator/equals contract.
We introduce PriorityQueueSetFactory to the keyed state backends, and this is were the queues are build. The current implementation of RocksDB uses an additional RocksDB instance until we are fully integrated with backend snapshotting, because we are otherwise running into trouble with incremental snapshots.
A configuration parameter is introduced to chose the implementation of queues for RocksDB, the default is still using the heap variant for now.
Finally, we introduce an additional method for bulk polling in the InternalTimerQueue interface that opens up future optimizations.
Verifying this change
This change is already covered by existing tests, such as AbstractEventTimeWindowCheckpointingITCase, but you would currently need to activate it via
RockDBBackendOptions.PRIORITY_QUEUE_STATE_TYPE.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (yes, if activated)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

CC @tillrohrmann

@tillrohrmann Thanks for the fast review. Merging.


Milestone: Compile a complete function

Let's start by working to compile this function into machine code. The steps are:

Handle local variable declarations -- for now, we'll assume the locals will be allocated in a contiguous memory region, so the task here is: using the information from the local declarations at the top of function_body::translate, to write a function that maps from local indices to offsets in that region, and to compute the needed size of that region.
Keep track of the stack pointer -- Move the backend's Registers struct into a backend Context, add a field recording the current depth of the stack pointer, and make push_i32 and pop_i32 subtract from and add to this field so that we always know where the stack pointer is (relative to where it started).
Implement get_local/set_local -- In function_body.rs, use the mapping we created above to get the offset within the locals area, then pass that to backend.rs to do the load or store. In the backend, this will look like mov offset(%rsp), Rq(op) where offset is the offset within the locals area plus the current stack depth.
Implement function entry -- For now, we can use this simple sequence:

	push   %rbp               # save incoming frame pointer
	mov    %rbp, %rsp         # copy stack pointer to frame pointer
        sub    %rsp, framesize    # allocate the stack frame (the stack grows down)

where framesize is the size of the locals area.

Store the incoming function arguments into their slots in the locals area. If you're on Linux/Mac/etc., the first 4 arguments are in rdi, rsi, rdx, rcx. If you're on Windows, they're in rcx, rdx, r8, r9. Eventually we'll want to make the calling convention configurable, but it's ok to hardcode stuff to get started with.

Implement returns - at the function exit, pop the last remaining i32, copy it into RAX, add the size of the locals area back to the stack pointer, then do a ret.

Then, at the end of function_body::translate, instead of just disassembling the output, return the compiled code, make examples/test.rs transmute the address to a function pointer and... call it!
Write a test case to test that "add" works :-).

Once that milestone is achieved, the work can branch out a little bit. One set of tasks is implementing more integer arithmetic operations. Another is to add floating-point register support and after that, floating-point arithmetic operations. And independently of those, the next big milestone will be to compile a fibonacci function. Once we achieve this first milestone, I'll write up a new design issue for that :-).
For anyone interested in getting involved, welcome! and please post in the issue here so that we can coordinate work.

I will start working on that, slowly though!
Can we limit the scope to just linux/mac (systemv calling conv) for now?

Sounds good! And yeah, we can just support one calling convention for now. As long as we keep platform-specific things reasonably localized, we can easily add more platforms later.

Why do we need to track SP and load/store locals relative to id? Isn't it would be easier to address relative to RBP?

Yes, either way would work for now. I have a mild preference for using RSP here because that will oblige us to always keep track of RSP as we add more code, which will make it easier to do things like frame pointer elimination or dynamically-aligned stack frames in the future. But I'm ok keeping it simpler for now too.
Yeah, that's fine for now. It might be a good idea to start a list of these kinds of things somewhere, as they would be good discrete projects for someone looking to get involved to pick up.


fix: fixes initial page load issue (closes #758)

Wrapped the client side code with DOMContentLoaded event.  Fixed and tested!

Thank you!

You can run "Static Site CI" manually, it automatically runs every day.