Why CMAKE_BUILD_TYPE is always Debug?

Brief Issue Summary
CMake: Configure always uses -DCMAKE_BUILD_TYPE:STRING=Debug even if I delete CMAKE_BUILD_TYPE or set CMAKE_BUILD_TYPE=Release in setting of CMake Tools extension, and I've already set environment variable: export CMAKE_BUILD_TYPE=Release
CMake Tools Diagnostics
{
  "os": "darwin",
  "vscodeVersion": "1.90.0",
  "cmtVersion": "1.18.41",
  "configurations": [
    {
      "folder": "/Users/zz/work/cppsober/kcv",
      "cmakeVersion": "3.29.5",
      "configured": true,
      "generator": "Ninja",
      "usesPresets": false,
      "compilers": {
        "C": "/Library/Developer/CommandLineTools/usr/bin/cc",
        "CXX": "/Library/Developer/CommandLineTools/usr/bin/c++"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [],
    "responses": [],
    "partialMatches": [],
    "targetCount": 7,
    "executablesCount": 1,
    "librariesCount": 3,
    "targets": [
      {
        "name": "birch-autotimer-update",
        "type": "UTILITY"
      },
      {
        "name": "imgui",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "konacv",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "test",
        "type": "EXECUTABLE"
      },
      {
        "name": "glfw",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "update_mappings",
        "type": "UTILITY"
      }
    ]
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "never",
      "configureOnOpen": false
    }
  ]
}

Debug Log
No response
Additional Information
No response

I would like to add that I can't find the correct way to simply add more build types. The CMakeFiles I use have for instance ServRel or ToolRel as build types, which I can't access at all.

Thanks for reporting this issue. Today we try to repro using a simple CMake Project, but we didn't repro it. We find that if we set the "CMAKE_BUILD_TYPE": "Release" in related configuration, and the -DCMAKE_BUILD_TYPE=Release displays on CMake output when configure the project. For further investigation, could you please share us a demo project with clear repro steps? Wea re looking forward to hearing from you. Thanks.
ENV:
VS code version: 1.90.0
CMake Extension version: 1.18.42
Please see the verified results as below.

@Evelyn-001 Hi, thanks for the reply. This gif looks okay, and maybe I need a little time to learn to use CMakePresets.json. Actually I begin to use CMake since about CMake 3.12 or before that.
My previous trial was on a Apple M1 machine, which is not available now.
I'm currently using a Windows 11, x86-64 machine, and I can reproduce it.
I guess Ninja as generator is the key to reproduce.
Here is the detail:

C/C++ compiler: Visual Studio 2022 (17.10.1)
CMake:  3.29.5 (manually installed, instead of the VS2022 installed one)
Build Tool: Ninja 1.12.1 (manually installed, instead of the VS2022 installed one)

VSCode: Version: 1.90.0
VSCode CMake Tools plugin version: v1.18.42
VSCode User setting.json
{
    "cmake.generator": "Ninja",
    "cmake.pinnedCommands": [
        "workbench.action.tasks.configureTaskRunner",
        "workbench.action.tasks.runTask"
    ],
}

CMakeLists.txt
cmake_minimum_required(VERSION 3.29)
project(x)
message(STATUS "[x] CMAKE_BUILD_TYPE: ${CMAKE_BUILD_TYPE}")
add_executable(x x.c)

x.c:
int main() {}

CMake Configure output by CMake: Configure in VSCode command palette:

Do I set CMAKE_BUILD_TYPE environment variable? No

Thanks for your reply. According to your comment, we try to repro it using above demo files, please see the verified results as below. Is it your issue? Thanks.
ENV:
VS code version: 1.90.0
CMake Extension version: 1.18.42

Thanks for your reply. According to your comment, we try to repro it using above demo files, please see the verified results as below. Is it your issue? Thanks. ENV: VS code version: 1.90.0 CMake Extension version: 1.18.42

Thanks for the reply. The verified result you provided in the gif is nearly what I thing the issue is. And to be precise, I think there are two sub-issues:

When the C/C++ compiler is cl.exe, if specified Ninja as generator in settings.json, the bug appears
When the C/C++ compiler is Clang, including Clang.exe from Visual Studio (for Windows), and AppleClang (for macOS), the bug appears

This issue reproduces with below Conditions:

When the C/C++ compiler is cl.exe, if specified Ninja as generator in settings.json, the bug appears
When the C/C++ compiler is Clang, the bug appears

ENV：
VSCode version: 1.90.1
CMake version: 3.28.3-msvc11
Ninja version: 1.11.0
VSCode CMake Tools extension version: v1.18.42

@gcampbell-msft, if user do not explicitly specify a value for CMAKE_BUILD_TYPE when executing CMake, or do not explicitly set it before building, will CMake choose a default CMAKE_BUILD_TYPE of Debug? Coud you please help look at this issue? Thanks in advance.

@Evelyn-001 Yes, if there is no CMAKE_BUILD_TYPE specified, then the default is Debug.

@zchrissirhcz @Evelyn-001 Let me take some time to investigate, I actually believe I may have been wrong about our default, let me look more closely into it and get you the full understanding and context. Thanks!

@zchrissirhcz Okay I've investigated closer and we do in fact default to "Debug". What are you expecting the default to be?

@zchrissirhcz Follow up to help us understand your scenario better, is there a reason that you don't want to explicitly set the build type?

I think CMAKE_BUILD_TYPE should be set by user, and a default value provided by "VSCode CMake Tools" is not required. Consider this case: a cross-platform C/C++ project, in its CMakeLists.txt, automatically detect and set value for CMAKE_BUILD_TYPE:
cmake_minimum_required(VERSION 3.5)
projet(x)
if(NOT CMAKE_BUILD_TYPE)
  set(CMAKE_BUILD_TYPE "Release" CACHE STRING "Choose the type of build." FORCE)
endif()
message(STATUS "[x] CMAKE_BUILD_TYPE: ${CMAKE_BUILD_TYPE}")

When invoked in command like:
cmake -S . -B build

it will print [x] CMAKE_BUILD_TYPE: Release
But when invoked in VSCode CMake Tools' "cmake configure", it prints [x] CMAKE_BUILD_TYPE: Debug.
I see this usage in:

the ncnn project: https://github.com/Tencent/ncnn/blob/master/CMakeLists.txt#L26-L28

the 3rd search result in google with keywords "default value for cmake_build_type": https://www.kitware.com/cmake-and-the-default-build-type/

@gcampbell-msft @Evelyn-001

@zchrissirhcz Thanks for all of this information, we will definitely assess this on the backlog and investigate. Again, thanks!

Verify this issue has been fixed. Thanks.
ENV:
VS code: 1.91.1
CMake Tools Extension: v1.19.19 (pre-release)

Brief Issue Summary
CMake: Configure always uses -DCMAKE_BUILD_TYPE:STRING=Debug even if I delete CMAKE_BUILD_TYPE or set CMAKE_BUILD_TYPE=Release in setting of CMake Tools extension, and I've already set environment variable: export CMAKE_BUILD_TYPE=Release
CMake Tools Diagnostics
{
  "os": "darwin",
  "vscodeVersion": "1.90.0",
  "cmtVersion": "1.18.41",
  "configurations": [
    {
      "folder": "/Users/zz/work/cppsober/kcv",
      "cmakeVersion": "3.29.5",
      "configured": true,
      "generator": "Ninja",
      "usesPresets": false,
      "compilers": {
        "C": "/Library/Developer/CommandLineTools/usr/bin/cc",
        "CXX": "/Library/Developer/CommandLineTools/usr/bin/c++"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [],
    "responses": [],
    "partialMatches": [],
    "targetCount": 7,
    "executablesCount": 1,
    "librariesCount": 3,
    "targets": [
      {
        "name": "birch-autotimer-update",
        "type": "UTILITY"
      },
      {
        "name": "imgui",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "konacv",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "test",
        "type": "EXECUTABLE"
      },
      {
        "name": "glfw",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "update_mappings",
        "type": "UTILITY"
      }
    ]
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "never",
      "configureOnOpen": false
    }
  ]
}

Debug Log
No response
Additional Information
No response

12bc6cdb375f9688ba2eff535c36b26dbbaff710

@smp73, thanks for your reply. Do you want to use -DCMAKE_BUILD_TYPE:STRING=Release ? you need to add Adding "configuration": "release" in CMakePresets.json file. Please refer to this comment in that issue. Thanks.


Add fuzzer for parsing / reading

Fuzzing is a technique for sending arbitrary input into functions to see what happens. Typically this is done to weed out crashes/panics from software, or to detect bugs. In some cases all possible inputs are ran into the program (i.e. if a function accepts 16-bit integers it's trivial to try them all).
We should support fuzzing and ship a docker image that can be ran which will help automate fuzzing. There are examples we can use from moov-io/ach:

Fuzzing setup from moov-io/ach
Self-Contained Dockerfile for Fuzzing

https://github.com/moov-io/metro2/pull/23


Use PAT for publishing docs

The publish-docs workflow has been updated to use a personal access token for publishing docs instead of using the GITHUB_TOKEN. This allows for more control over doc publishing permissions.
Relates to https://github.com/MetaMask/metamask-module-template/issues/184

This depends upon #95

This requires some changes to the repository settings, but I will wait until just prior to merge before making those changes to avoid disrupting other PRs.
Typically I would test action changes in a fork, but in this case it's challenging because we're relying upon a feature not available without a paid plan (the ability to let metamaskbot bypass the review requirement), so I can't test it.

The required settings changes (as documented here) have been made


New-AppSourceSubmission failed, but didn't return error

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
Hello,
Could you add parameter that throws error after App Source Submission fails (substate value "Failed")? I would like to get fail status when it happens, but I only have "failed" info when I find it in logs and pipeline end with "success" status.
I may be wrong but it's only another if between 305-307 lines in New-AppSourceSubmission.ps1 (I am aware that someone would like to have it just as it is now, so I suggest parameter)
Scripts used to create container and cause the issue
write-host "Uploading an app"
New-AppSourceSubmission -authContext $authcontext -productId $productID -appFile $appfile -Verbose -force -autoPromote

Full output of scripts
2024-06-24T14:10:13.8417888Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a\_temp\7f994381-603d-4e37-b957-72cf765f19cf.ps1'"
2024-06-24T14:10:30.4627442Z Name of product: D:\a\r1\a\SourceObjects\<IP_ADDRESS>\Applications\***APP***.app
2024-06-24T14:10:30.8390169Z BcContainerHelper version 6.0.18
2024-06-24T14:10:33.6262909Z BC.HelperFunctions emits usage statistics telemetry to Microsoft
2024-06-24T14:10:33.7584466Z Running on Windows, PowerShell 5.1.20348.2400
2024-06-24T14:10:36.3443561Z Attempting authentication to https://api.partner.microsoft.com/.default using clientCredentials...
2024-06-24T14:10:36.4964303Z Authenticated as app ***
2024-06-24T14:10:41.4239941Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/setup
2024-06-24T14:10:41.7058234Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(module=Availability)
2024-06-24T14:10:43.3779604Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/productavailabilities/getByInstanceID(instanceID=2152924500014935998)
2024-06-24T14:10:44.1043525Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/featureavailabilities/getByInstanceID(instanceID=2152924500014935998)
2024-06-24T14:10:44.8309929Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(module=Property)
2024-06-24T14:10:45.3035597Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/properties/getByInstanceID(instanceID=9f2ea6d0-862d-8d5a-ecda-b4d1740b2f49)
2024-06-24T14:10:45.6065772Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(module=Listing)
2024-06-24T14:10:45.9637897Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/listings/getByInstanceID(instanceID=4ec8a8ab-2bc2-4f8c-c209-9cef0f1713d4)
2024-06-24T14:10:46.3008783Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/listings/22bfcc42-0ab2-e32a-8d63-609dded6a79e/assets
2024-06-24T14:10:46.8211923Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/listings/22bfcc42-0ab2-e32a-8d63-609dded6a79e/images
2024-06-24T14:10:47.2958833Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/listings/22bfcc42-0ab2-e32a-8d63-609dded6a79e/videos
2024-06-24T14:10:47.6221681Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(module=Package)
2024-06-24T14:10:48.1491309Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packageconfigurations/getByInstanceID(instanceID=27499ed2-9d21-4111-b3d8-03b4f1c5c25b)
2024-06-24T14:10:48.5947494Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packages/b97a38af-50fb-4e09-86fa-56b0e1bf9009
2024-06-24T14:10:49.6328344Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc
2024-06-24T14:10:49.9320858Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(module=Package)
2024-06-24T14:10:50.4873159Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packageconfigurations/getByInstanceID(instanceID=27499ed2-9d21-4111-b3d8-03b4f1c5c25b)
2024-06-24T14:10:50.9174088Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packages/b97a38af-50fb-4e09-86fa-56b0e1bf9009
2024-06-24T14:10:51.7528021Z
2024-06-24T14:10:51.7528755Z
2024-06-24T14:10:51.7532291Z resourceType                                    : Dynamics365BusinessCentralPackageConfiguration
2024-06-24T14:10:51.7532687Z packageType                                     : AddOn
2024-06-24T14:10:51.7533844Z packageReferences                               : {@{type=Dynamics365BusinessCentralAddOnExtensionPackage;
2024-06-24T14:10:51.7534932Z                                                   value=b97a38af-50fb-4e09-86fa-56b0e1bf9009}}
2024-06-24T14:10:51.7535556Z @odata.etag                                     : "0900e9f0-0000-0800-0000-6675bd140000"
2024-06-24T14:10:51.7535963Z id                                              : 27499ed2-9d21-4111-b3d8-03b4f1c5c25b
2024-06-24T14:10:51.7537030Z Dynamics365BusinessCentralAddOnExtensionPackage : @{resourceType=; fileName=***APP***.app;
2024-06-24T14:10:51.7539060Z                                                   state=Processed; @odata.etag="2e00280b-0000-0800-0000-6675bd0d0000";
2024-06-24T14:10:51.7539497Z                                                   id=APPID}
2024-06-24T14:10:51.7539664Z
2024-06-24T14:10:51.7547490Z Uploading an app
2024-06-24T14:10:51.8641587Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc
2024-06-24T14:10:51.8647605Z VERBOSE: GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc with 0-byte
2024-06-24T14:10:51.8648716Z  payload
2024-06-24T14:10:52.1531509Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:10:52.1566080Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/setup
2024-06-24T14:10:52.1574923Z VERBOSE: GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/setup with
2024-06-24T14:10:52.1575588Z 0-byte payload
2024-06-24T14:10:52.4736902Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:10:52.4892612Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions
2024-06-24T14:10:52.4900488Z VERBOSE: GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions
2024-06-24T14:10:52.4900982Z  with 0-byte payload
2024-06-24T14:10:53.3979928Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:10:53.4027396Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/1152921505697914941
2024-06-24T14:10:53.4037318Z VERBOSE: GET
2024-06-24T14:10:53.4038066Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:10:53.4038581Z 7914941 with 0-byte payload
2024-06-24T14:10:53.8511494Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:10:53.8583800Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(module=Package)
2024-06-24T14:10:53.8589344Z VERBOSE: GET
2024-06-24T14:10:53.8590222Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(mod
2024-06-24T14:10:53.8594218Z ule=Package) with 0-byte payload
2024-06-24T14:10:54.3651893Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:10:54.4253516Z VERBOSE: POST https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery?api-version=3.0-preview.1 with
2024-06-24T14:10:54.4254384Z -1-byte payload
2024-06-24T14:10:54.5737740Z VERBOSE: received 421933-byte response of content type application/json; charset=utf-8; api-version=3.0-preview.1
2024-06-24T14:10:55.1037494Z Downloading AL Language Extension (Prerelease) to C:\ProgramData\BcContainerHelper\alLanguageExtension\14.0.1055126.zip
2024-06-24T14:10:57.1203716Z using 7zip
2024-06-24T14:11:09.0725569Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packageConfigurations/getByInstanceID(instanceID=27499ed2-9d21-4111-b3d8-03b4f1c5c25b)
2024-06-24T14:11:09.0737128Z VERBOSE: GET
2024-06-24T14:11:09.0737856Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packageConfigurations/ge
2024-06-24T14:11:09.0738545Z tByInstanceID(instanceID=27499ed2-9d21-4111-b3d8-03b4f1c5c25b) with 0-byte payload
2024-06-24T14:11:09.5344228Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:09.5620947Z POST https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packages
2024-06-24T14:11:09.5634900Z {
2024-06-24T14:11:09.5635215Z     "fileName":  "***APP***.app",
2024-06-24T14:11:09.5636488Z     "resourceType":  "Dynamics365BusinessCentralAddOnExtensionPackage"
2024-06-24T14:11:09.5637220Z }
2024-06-24T14:11:09.5648197Z VERBOSE: POST https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packages
2024-06-24T14:11:09.5648724Z with -1-byte payload
2024-06-24T14:11:10.4180005Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:17.0460101Z VERBOSE: Transfer Summary
2024-06-24T14:11:17.0462032Z
2024-06-24T14:11:17.0462680Z --------------------------------
2024-06-24T14:11:17.0462784Z
2024-06-24T14:11:17.0462977Z Total:  1.
2024-06-24T14:11:17.0463100Z
2024-06-24T14:11:17.0463294Z Successful: 1.
2024-06-24T14:11:17.0463414Z
2024-06-24T14:11:17.0463781Z Failed: 0.
2024-06-24T14:11:17.1003651Z PUT https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packages/184f3253-badd-4bd6-a140-eb820ccf45c9
2024-06-24T14:11:17.1005156Z {
2024-06-24T14:11:17.1007458Z     "id":  "184f3253-badd-4bd6-a140-eb820ccf45c9",
2024-06-24T14:11:17.1007964Z     "fileName":  "***APP***.app",
2024-06-24T14:11:17.1009002Z     "fileSasUri":  "https://ingestionpackagesprod1.blob.core.windows.net/file/3028914190253625407?sv=2018-03-28\u0026sr=b\u0026sig=jynrOxfEy9a7Njc3llhZ%2Bj%2FDiuZwVL40lkw%2FTNOkrKE%3D\u0026se=2024-06-25T14%3A26%3A10Z\u0026sp=rwl",
2024-06-24T14:11:17.1009718Z     "resourceType":  "Dynamics365BusinessCentralAddOnExtensionPackage",
2024-06-24T14:11:17.1010148Z     "state":  "Uploaded",
2024-06-24T14:11:17.1011288Z<EMAIL_ADDRESS> "\"4a00b961-0000-0800-0000-66797e7e0000\""
2024-06-24T14:11:17.1011770Z }
2024-06-24T14:11:17.1015668Z VERBOSE: PUT
2024-06-24T14:11:17.1016319Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packages/184f3253-badd-4
2024-06-24T14:11:17.1016837Z bd6-a140-eb820ccf45c9 with -1-byte payload
2024-06-24T14:11:19.0347916Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:19.0446623Z PUT https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packageConfigurations/27499ed2-9d21-4111-b3d8-03b4f1c5c25b
2024-06-24T14:11:19.0448097Z {
2024-06-24T14:11:19.0449548Z     "resourceType":  "Dynamics365BusinessCentralPackageConfiguration",
2024-06-24T14:11:19.0450280Z<EMAIL_ADDRESS> "\"0900e9f0-0000-0800-0000-6675bd140000\"",
2024-06-24T14:11:19.0450761Z     "packageType":  "AddOn",
2024-06-24T14:11:19.0451287Z     "id":  "27499ed2-9d21-4111-b3d8-03b4f1c5c25b",
2024-06-24T14:11:19.0451696Z     "packageReferences":  [
2024-06-24T14:11:19.0452180Z                               {
2024-06-24T14:11:19.0452711Z                                   "value":  "184f3253-badd-4bd6-a140-eb820ccf45c9",
2024-06-24T14:11:19.0453062Z                                   "type":  "Dynamics365BusinessCentralAddOnExtensionPackage"
2024-06-24T14:11:19.0453698Z                               }
2024-06-24T14:11:19.0453924Z                           ]
2024-06-24T14:11:19.0454469Z }
2024-06-24T14:11:19.0456361Z VERBOSE: PUT
2024-06-24T14:11:19.0457191Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/packageConfigurations/27
2024-06-24T14:11:19.0457867Z 499ed2-9d21-4111-b3d8-03b4f1c5c25b with -1-byte payload
2024-06-24T14:11:19.9230402Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:19.9295140Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(module=Property)
2024-06-24T14:11:19.9302329Z VERBOSE: GET
2024-06-24T14:11:19.9303234Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/branches/getByModule(mod
2024-06-24T14:11:19.9303977Z ule=Property) with 0-byte payload
2024-06-24T14:11:20.2657498Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:20.2700107Z GET https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/properties/getByInstanceID(instanceID=9f2ea6d0-862d-8d5a-ecda-b4d1740b2f49)
2024-06-24T14:11:20.2709332Z VERBOSE: GET
2024-06-24T14:11:20.2709859Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/properties/getByInstance
2024-06-24T14:11:20.2711381Z ID(instanceID=9f2ea6d0-862d-8d5a-ecda-b4d1740b2f49) with 0-byte payload
2024-06-24T14:11:20.5854777Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:20.6075358Z PUT https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/properties/9f2ea6d0-862d-8d5a-ecda-b4d1740b2f49
2024-06-24T14:11:20.6083113Z {
2024-06-24T14:11:20.6083846Z     "resourceType":  "AzureProperty",
2024-06-24T14:11:20.6084486Z     "hideKeys":  [
2024-06-24T14:11:20.6084871Z
2024-06-24T14:11:20.6085392Z                  ],
2024-06-24T14:11:20.6085878Z     "categories":  [
2024-06-24T14:11:20.6086260Z
2024-06-24T14:11:20.6086718Z                    ],
2024-06-24T14:11:20.6087233Z     "leveledCategories":  {
2024-06-24T14:11:20.6087783Z                               "HumanResources":  [
2024-06-24T14:11:20.6088624Z                                                      "hr-operations"
2024-06-24T14:11:20.6089123Z                                                  ]
2024-06-24T14:11:20.6089689Z                           },
2024-06-24T14:11:20.6090241Z     "extendedProperties":  [
2024-06-24T14:11:20.6090587Z
2024-06-24T14:11:20.6091052Z                            ],
2024-06-24T14:11:20.6091760Z<EMAIL_ADDRESS> "\"4000bb96-0000-0800-0000-6675bd130000\"",
2024-06-24T14:11:20.6092313Z     "useEnterpriseContract":  false,
2024-06-24T14:11:20.6092840Z     "globalAmendmentTerms":  "",
2024-06-24T14:11:20.6093530Z     "id":  "9f2ea6d0-862d-8d5a-ecda-b4d1740b2f49",
2024-06-24T14:11:20.6094077Z     "leveledIndustries":  {
2024-06-24T14:11:20.6094403Z
2024-06-24T14:11:20.6094937Z                           },
2024-06-24T14:11:20.6095421Z     "termsOfUse":  "",
2024-06-24T14:11:20.6096090Z     "applicableProducts":  [
2024-06-24T14:11:20.6096458Z
2024-06-24T14:11:20.6097020Z                            ],
2024-06-24T14:11:20.6097514Z     "industries":  [
2024-06-24T14:11:20.6097932Z
2024-06-24T14:11:20.6098396Z                    ],
2024-06-24T14:11:20.6098879Z     "productTags":  [
2024-06-24T14:11:20.6099254Z
2024-06-24T14:11:20.6099764Z                     ],
2024-06-24T14:11:20.6100370Z     "marketingOnlyChange":  false,
2024-06-24T14:11:20.6100897Z     "additionalCategories":  [
2024-06-24T14:11:20.6101282Z
2024-06-24T14:11:20.6101749Z                              ],
2024-06-24T14:11:20.6102230Z     "appVersion":  "<IP_ADDRESS>",
2024-06-24T14:11:20.6102810Z     "submissionVersion":  "",
2024-06-24T14:11:20.6103362Z     "customAmendments":  [
2024-06-24T14:11:20.6103696Z
2024-06-24T14:11:20.6104182Z                          ]
2024-06-24T14:11:20.6104709Z }
2024-06-24T14:11:20.6105229Z VERBOSE: PUT
2024-06-24T14:11:20.6106064Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/properties/9f2ea6d0-862d
2024-06-24T14:11:20.6108345Z -8d5a-ecda-b4d1740b2f49 with -1-byte payload
2024-06-24T14:11:21.3272614Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:21.3342031Z POST https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions
2024-06-24T14:11:21.3342705Z {
2024-06-24T14:11:21.3343239Z     "resources":  [
2024-06-24T14:11:21.3344664Z                       {
2024-06-24T14:11:21.3345262Z                           "type":  "Package",
2024-06-24T14:11:21.3346021Z                           "value":  "27499ed2-9d21-4111-b3d8-03b4f1c5c25b"
2024-06-24T14:11:21.3347176Z                       },
2024-06-24T14:11:21.3347667Z                       {
2024-06-24T14:11:21.3348427Z                           "type":  "Property",
2024-06-24T14:11:21.3349393Z                           "value":  "9f2ea6d0-862d-8d5a-ecda-b4d1740b2f49"
2024-06-24T14:11:21.3349717Z                       }
2024-06-24T14:11:21.3350214Z                   ],
2024-06-24T14:11:21.3350455Z     "targets":  [
2024-06-24T14:11:21.3353610Z                     {
2024-06-24T14:11:21.3354592Z                         "type":  "Scope",
2024-06-24T14:11:21.3355025Z                         "value":  "preview"
2024-06-24T14:11:21.3355279Z                     }
2024-06-24T14:11:21.3355578Z                 ],
2024-06-24T14:11:21.3355853Z     "resourceType":  "SubmissionCreationRequest"
2024-06-24T14:11:21.3356117Z }
2024-06-24T14:11:21.3356341Z VERBOSE: POST
2024-06-24T14:11:21.3357009Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions with -1-byte
2024-06-24T14:11:21.3357449Z  payload
2024-06-24T14:11:23.0937505Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:53.0944278Z VERBOSE: GET
2024-06-24T14:11:53.0945356Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:11:53.0945962Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:11:53.5870664Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:11:53.6115272Z Automated validation.VERBOSE: GET
2024-06-24T14:11:53.6116003Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:11:53.6116457Z 7921375 with 0-byte payload
2024-06-24T14:11:54.0490247Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:12:24.0567481Z VERBOSE: GET
2024-06-24T14:12:24.0568464Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:12:24.0568939Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:12:25.3446266Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:12:25.3495242Z .VERBOSE: GET
2024-06-24T14:12:25.3496121Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:12:25.3496626Z 7921375 with 0-byte payload
2024-06-24T14:12:25.7701703Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:12:55.7633339Z VERBOSE: GET
2024-06-24T14:12:55.7634366Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:12:55.7634856Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:12:56.2087187Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:12:56.2135476Z .VERBOSE: GET
2024-06-24T14:12:56.2136322Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:12:56.2138389Z 7921375 with 0-byte payload
2024-06-24T14:12:56.6541757Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:13:26.6608605Z VERBOSE: GET
2024-06-24T14:13:26.6609659Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:13:26.6610147Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:13:27.1714184Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:13:27.1768550Z .VERBOSE: GET
2024-06-24T14:13:27.1769484Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:13:27.1770184Z 7921375 with 0-byte payload
2024-06-24T14:13:27.6264967Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:13:57.6398395Z VERBOSE: GET
2024-06-24T14:13:57.6399220Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:13:57.6399714Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:13:58.0729604Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:13:58.0780388Z .VERBOSE: GET
2024-06-24T14:13:58.0781239Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:13:58.0781705Z 7921375 with 0-byte payload
2024-06-24T14:13:58.5198588Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:14:28.5272619Z VERBOSE: GET
2024-06-24T14:14:28.5273679Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:14:28.5274317Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:14:28.9753557Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:14:28.9802755Z .VERBOSE: GET
2024-06-24T14:14:28.9803589Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:14:28.9805870Z 7921375 with 0-byte payload
2024-06-24T14:14:29.4930302Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:14:59.5075699Z VERBOSE: GET
2024-06-24T14:14:59.5076893Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:14:59.5077462Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:14:59.9622273Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:14:59.9671545Z .VERBOSE: GET
2024-06-24T14:14:59.9672598Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:14:59.9676387Z 7921375 with 0-byte payload
2024-06-24T14:15:01.1927807Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:15:31.2043046Z VERBOSE: GET
2024-06-24T14:15:31.2044331Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:15:31.2044827Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:15:31.6983955Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:15:31.7036361Z .VERBOSE: GET
2024-06-24T14:15:31.7037287Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:15:31.7037853Z 7921375 with 0-byte payload
2024-06-24T14:15:32.2724753Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:16:02.2782285Z VERBOSE: GET
2024-06-24T14:16:02.2783372Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:16:02.2783926Z 7921375/workflowdetails with 0-byte payload
2024-06-24T14:16:02.7596710Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:16:02.7621671Z  Failure
2024-06-24T14:16:02.7650255Z VERBOSE: GET
2024-06-24T14:16:02.7651074Z https://api.partner.microsoft.com/v1.0/ingestion/products/67358f61-fa6c-46e7-a03f-7a8294bfa4dc/submissions/115292150569
2024-06-24T14:16:02.7651557Z 7921375 with 0-byte payload
2024-06-24T14:16:03.2281010Z VERBOSE: received -1-byte response of content type application/json; charset=utf-8
2024-06-24T14:16:03.2297751Z New AppSource submission failed
2024-06-24T14:16:03.2310035Z resourceType       : Submission
2024-06-24T14:16:03.2310876Z state              : InProgress
2024-06-24T14:16:03.2311474Z substate           : Failed
2024-06-24T14:16:03.2312189Z targets            : {@{type=Scope; value=Preview}}
2024-06-24T14:16:03.2316157Z resources          : {@{type=Availability; value=cf2f3781-0af6-f5cc-0365-51a9bdb1e6b7}, @{type=Listing;
2024-06-24T14:16:03.2316813Z                      value=fdb2d2ba-a4ed-e90d-14f8-3f08c026f100}, @{type=Package;
2024-06-24T14:16:03.2317339Z                      value=27499ed2-9d21-4111-b3d8-03b4f1c5c25b}, @{type=Property;
2024-06-24T14:16:03.2317823Z                      value=9f2ea6d0-862d-8d5a-ecda-b4d1740b2f49}...}
2024-06-24T14:16:03.2318351Z publishedTimeInUtc : 1601-01-01T00:00:00Z
2024-06-24T14:16:03.2318723Z pendingUpdateInfo  : @{updateType=Create; status=Completed}
2024-06-24T14:16:03.2319050Z releaseNumber      : 38
2024-06-24T14:16:03.2319340Z friendlyName       : Submission 38
2024-06-24T14:16:03.2319679Z areResourcesReady  : True
2024-06-24T14:16:03.2320261Z id                 :<PHONE_NUMBER>697921375
2024-06-24T14:16:03.2320420Z
2024-06-24T14:16:04.0103836Z
2024-06-24T14:16:04.0107781Z
2024-06-24T14:16:04.1380444Z ##[section]Finishing: Publish app to appsource

Screenshots

Additional context

does it happen all the time? - Usually, apps are published without errors, but when there are some, it should fail
did it use to work? - No

Thank you in advance :)

New-AppSourceSubmission doesn't throw an error - it returns the submission object where you can see the status.
It does throw if it cannot create the appsource submission - it does not throw if there are validation errors.
In most cases, the app submission is done async and I cannot return the error anyway.


ECKFTag methods are misnamed?

Some comments on methods in ECKFTag:
buildPrivateKeyFromPoint/unsafeBuildPrivateKeyFromPoint delegate to java.security.spec.ECPrivateKeySpec, and the parameter passed is "the private value S". This is a secret value, not a point, so the method are misnamed.
unsafeBuildPublicKeyFromPoints delegates to java.security.spec.ECPublicKeySpec, and the parameters passed in are the affine x-coordinate and affine y-coordinate of the public point of the curve. Since we are passing in the coordinates of a single point, not multiple points, this method is also misnamed.
One more thing to note: there is a lack of symmetry between buildPublicKey and unsafeBuildPublicKeyFromPoints, since in most other cases, unsafe is appended to another method name without any other changes.

Also, to be honest, tsec 0.1 should really revamp these to just return Option.
Majority of these unsafeBlah is just laziness on my part when I wrote them months ago. There's no real observable side effect from doing this, despite forcing a try/catch


Leaderboard: setup project

In this pull request, I have setup a project using Webpack. Basic HTML markup is added as per the wireframe and instructions.
Please review my PR.

Hi @umair-rao, Kindly use the updated version  of the microverse readme template for your readme, this is a requirement to get a review


feat: introduce telemetry

This PR fixes #24.
Based on #31 and should be merged after it.
Changes

Introduced Telemetry, see below for events list with properties.
Added enableTelemetry config option (trueby default).
Was inspired by Desktop, so we have install and session events based on similar logic as Desktop has.
Used machineId provided by VSC env.
Each event also sends native VSC sessionId. This can be used to group all events from single session (new session is when VSC instance is started/restarted).
There is VSC native TelemetryLogger, but I realized a bit too late. Still I think what we have now is quite stable and good enough for now.

https://github.com/kubeshop/vscode-monokle/blob/02dc37e543b1f9e73c0062dca9d602869f677448/src/utils/telemetry.ts#L69-L97
Fixes

None.

Checklist

[x] tested locally
[x] added new dependencies
[x] updated the docs
[ ] added a test

I rechecked if we can send telemetry events differently, so properties are split in MixPanel instead of being shown as single property, but it seems this is how @segment/analytics-node works and there is no easy way to change it.


Using addDefaultXCTestPrivateActions does not work in Xcode 10.2

I tried to run the example project in Xcode 10.2 but it seems like monkey.addDefaultXCTestPrivateActions() is not working with this Xcode Version, while using monkey.addDefaultUIAutomationActions() works fine.
"Not working" means, you can not see any paws and nothing happens while running the UITest.
Maybe you have an idea why it's not working?

Hey @fbernutz and thank you for your report. We got a similar issue reported for the beta release (see #73) and it looks like it's not just a "beta thing". I'll try to find a solution / workaround for this problem and will get back to you as soon as I have something.

@fbernutz I did some research and as it has been mentioned in #73 the XCEventGenerator class seems to have be removed from the XCTest.framework. Unfortunately I couldn't find anything similar that could be used as a replacement. This means that as for now, I don't have a solution to this issue 😢. As you have mentioned, the monkey.addDefaultUIAutomationActions works fine, but only on a Simulator.
I've already marked this issue with "help wanted". Sorry for not having more positive update 😞

Hello, when can it be solved?

Maybe add this to the project description so people don't spend time trying to get this running?

This issue still persists on public Xcode 10.2. Any further help here?

Hey, I'm afraid there is no solution since this function was relying on an API that has been removed by Apple. You could try using monkey.addDefaultUIAutomationActions but that one will only work on a Simulator.

Found a workaround per this post
Simply replacing your XCTest.framework on xcode 10.2 with an older version (i tried xcode 10.1) will work.
Look for the framework at the following path:

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework

xcode 10.2 also not work  use .addDefaultXCTestPrivateActions .


Tex math output problem in version 1.7.1 (Windows)

Tex math formulas do not output correctly as of version 1.7.1.
For instance, this example on the AsciidocFX home page
[math,file="tex-formula.png"]
--
\begin{align}
\dot{x} & = \sigma(y-x) \\
\dot{y} & = \rho x - y - xz \\
\dot{z} & = -\beta z + xyp
\end{align}
--

renders to this:

My environment is Windows 10 64-bit.

I also met.

i also encountered the problem!
For some reason the math keyword is not accepted anymore.
I assume commit cd8c64c4cca0e6f09fe9911334b4b575af4ea2f3 changed the behaviour.
Simply change keyword math -> latexmath or mathml and it will work again;
[latexmath,file="tex-formula.png"]
--
\begin{align}
\dot{x} & = \sigma(y-x) \\
\dot{y} & = \rho x - y - xz \\
\dot{z} & = -\beta z + xyp
\end{align}
--

Hi, could you please reinstall https://github.com/asciidocfx/AsciidocFX/releases/tag/v1.7.4 and check?

Hey, I can confirm that with the newest version, the math identifier works as expected and returns the same result as with latexmath.

Thanks for testing 👍 I'm closing the issue.


ValueError : StoragePasswords cannot have wildcards in namespace.

Hi,
I know it's more likely a feature and not a bug. But I was wondering why is StoragePasswords is protected from access with wildcard apps or namespace, when the same action using rest is not protected ?
The first snippet will generate an error because app & owner are set to be wildcards
s = client.connect(username="<user>", password="<redacted>",host="<ip>",port="<port>",app="-",owner="-")

try:
    for pw in s.storage_passwords:
        print(pw.username)
except ValueError as ve:
    print(ve)

The following snippet will not generate an error with the wildcards :
req = requests.get(f"https://<host>:<port>/servicesNS/-/-/storage/passwords/", verify=False, headers={'Authorization': s.token},data={'output_mode':"json"})
req.raise_for_status()
for pw in req.json().get("entry"):
    print(pw.get("content").get("username"))

In our workflow with Splunk, we might not know where is stored the password so we need to be able to use wildcard on the app level of the namespace.
Is there any solution with splunklib or should we stick with our basic requests ?

Hi @Jalkar , thanks from bringing this to our knowledge. We are analysing on this and will be sharing an update soon.

@Jalkar we would request you to use the latest SDK release with the changes and let us know if it resolves the issue.


Add Building Blocks for Web Apps

Reopened from https://github.com/sindresorhus/awesome/pull/1789 (PR to master)

https://github.com/componently-com/awesome-building-blocks-for-web-apps
Standalone features to be integrated into web applications. It should be included because it's awesome not having to code the same functionality over and over again.
By submitting this pull request I confirm I've read and complied with the requirements 🖖

Reopened from https://github.com/sindresorhus/awesome/pull/1789
Lint: https://github.com/componently-com/awesome-building-blocks-for-web/runs/740112407#step:4:1
Reviewed PRs:

https://github.com/sindresorhus/awesome/pull/1787#pullrequestreview-424728426
https://github.com/sindresorhus/awesome/pull/1788#pullrequestreview-424722941

unicorn

I feel like the list is too much of an ad for Componently right now. It's fine to link to Componently of course, but I think it should be made clear what it is. For example, I don't think the repo link should be to Componently as it's not the website for the list itself.

The descriptions for items needs more work. It's not good enough that it's just copy-pasted from a project's repo. Many projects have bad descriptions/taglines. I saw both typos and titlecased descriptions just from a quick look.

Some examples of not useful descriptions:

Grow your business with honest marketing.
Ship faster and prove value with less risk.

And remove words like easy/simple/beautiful. They are overused words.

Thanks for the feedback. Removed the link from the repo description, will review item descriptions.

@sindresorhus  The descriptions are now also updated to be more helpful. Anything else you would change? :)

componently.com is a marketplace where developers can search, compare and integrate web application building blocks.

This still feels like an ad. Try to make it more relevant. Something like this:

By the way, if you like web building blocks, you'll love componently.com, which [(how it solves the problem of building blocks) blah blah...].

Curated list of standalone features to be integrated into web applications.

I'd like to see a more verbose description that describes why building blocks (components) are awesome and what problem they solve.

Tweet: https://twitter.com/awesome__re/status/1274245557297397760

This still feels like an ad. Try to make it more relevant. Something like this:

By the way, if you like web building blocks, you'll love componently.com, which [(how it solves the problem of building blocks) blah blah...].

I'd like to see a more verbose description that describes why building blocks (components) are awesome and what problem they solve.

Both very good points! I've edited the list around it :)


Menu Bar

Action center icon disappears
The action center icon is gone, and is no longer displayed.
The option is enabled in Cairo DTE settings.
System information:

Windows version: Windows 10 Pro
Cairo version: 0.3.7015.0 - Pre-release
32-bit or 64-bit: 64-bit
In Cairo Settings > Advanced, is Cairo set as shell?: Yes

Which build of Windows 10 are you using?

~Which build of Windows 10 are you using?~ Sorry, just noticed that you have Cairo set as shell. This feature is not supported with Cairo set as shell due to Action Center being a feature of explorer.exe.

That's fine the action center disappears when cairo is set as shell and the user logs out, but stays when I have it set to start on startup. So that makes sense.

Should this be closed?

Yeah, I think it was reopened inadvertently.


Apache Guacamole - differences

Hello,
Why should I use your application instead of Apache Guacamole?
Best regards,
Kamil

I'm sorry, I don't known.


Is it possible to handle offer/answer at 200OK and ACK for reINVITEs?

Hello Dave! I hope you are doing well.
I have a situation that I need to implement with Drachtio. After starting a standard dialog using createUAC(), I need later to send a reINVITE without SDP, then 200OK and ACK will finally carry the offer/answer.
I know that reINVITE would be processed this way and the SDP in the 200OK would be obtained from the res object:
        callerDialog.modify(callerSDP, (err, res) => {...}
For my scenario I can send an empty string in the place of callerSDP above and can handle the new calling SDP (i.e. the offer) in the res object, but how can I send later the new caller SDP (i.e. the answer) in the ACK?
I know that for the initial INVITE we can use the noAck: true in the options for createUAC() and later use the obj.ack(localSDP), but this is a different scenario, right?
Can you please advise on this? Thank you so much!

Hello Dave, I was able to test successfully a change that satisfies my needs. I think this would be a good contributions to other people, what do you think? I modified the modify() at dialog.js:
`
/**

modify the dialog session by changing attributes of the media connection

@param  {string} sdp - 'hold', 'unhold', or a session description protocol

@param  {function} [callback] - callback invoked with signature (err) when operation has completed

@param  {Object} opts - object where noAck param can be used to allow caller to provide ACK with SDP

@return {Promise|Dialog} if no callback is supplied, otherwise the function returns a reference to the Dialog
*/
modify(sdp, callback, opts) {
const noAck = opts && opts.noAck;
const __x = (callback) => {
switch (sdp) {
case 'hold':
this.local.sdp = this.local.sdp.replace(/a=sendrecv/, 'a=inactive') ;
this.onHold = true ;
break ;
case 'unhold':
if (this.onHold) {
this.local.sdp = this.local.sdp.replace(/a=inactive/, 'a=sendrecv') ;
}
else {
console.error('Dialog#modify: attempt to 'unhold' session which is not on hold');
return process.nextTick(() => {
callback(new Error('attempt to unhold session that is not on hold'));
}) ;
}
break ;
default:
this.local.sdp = sdp ;
break ;
}
debug(Dialog#modify: sending reINVITE for dialog id: ${this.id}, sdp: ${this.local.sdp}) ;
this.agent.request({
method: 'INVITE',
stackDialogId: this.id,
body: this.local.sdp,
_socket: this.socket,
headers: {
'Contact': this.local.contact
}
}, (err, req) => {
if (err) return callback(err);
req.on('response', (res, ack) => {
debug(Dialog#modifySession: received response to reINVITE with status ${res.status}) ;
if (res.status >= 200) {
if (!noAck) {
ack() ;
}
if (200 === res.status) {
this.remote.sdp = res.body ;
function ackForCaller(localSdp) {
ack({body: localSdp});
}
return callback(null, res.body, noAck ? ackForCaller : null);
}
callback(new SipError(res.status, res.reason)) ;
}
}) ;
}) ;
};

if (callback) {
  __x(callback) ;
  return this ;
}

return new Promise((resolve, reject) => {
  __x((err, sdp) => {
    if (err) return reject(err);
    resolve(sdp);
  });
});

}
`
I spent some time trying to submit the code to Gerrit for requesting a pull, but somehow I always get 403 when trying to submit my code in a new branch. Do you need maybe to give me authorization?
Thanks!!

I'd love to see it as a pull request in order to evaluate it.  I'm not sure why you are unable to submit a PR - I've had others do it successfully.  Have you forked the master branch to your own account, made the change their, and tried to submit a PR?

I will do it, thanks!

just checking in...would still love to see a PR from you on this if you are still interested..

I am working on a fix for this (finally!).  I've made an attempt in drachtio-srf@ 4.4.49-beta.2
This has an enhancement to the dlg.modify() function
You can use it in the same way as before for a "normal" reinvite which has a body:
const sdp = await dlg.modify(newSdpToOffer);

But if you want to do a reINVITE where you do not include a body, and you do not want the default behavior of having an ACK (with SDP including c=<IP_ADDRESS>) automatically generated for you, then you can do this:
const {sdp, ack} = await dlg.modify({noAck:true});

This will send a reinvite with no SDP, returning you the SDP received in the 200 ok, along with an 'ack()' function that you must call sometime later, passing the SDP you want included in the ACK.


Templating engine needed

As I think about this project more, I think a templating engine will greatly ease the development of the client. I've used ejs before, but it requires node. However if we want to stick with a strictly browser-based client, something like mustache.js could do the trick. Any preference here?

I dig browser based over a second server. Mustache sounds like a good choice.

@nicklathe - still needed?

Nope. Not needed anymore.


Create a Laser

Graphical:
- get a model, texture, make a prefab out of the laser
Implementation:
- Laser should take a speed, direction, position on construct
- use this to immediately accelerate on spawn and move towards direction
- if it touches the Player, run Player.damageTaken(damage)

The current implementation of NormalProjectile accomplishes this entire requirement pretty effectively as of commit e8c18d897752605d524bd3a61cd2f819c9773ea9:
https://github.com/Anedumgottil/VR-Mazmorra/blob/e8c18d897752605d524bd3a61cd2f819c9773ea9/Technodungeon/Assets/Scripts/NormalProjectile.cs
See the way the Pistol fires it's bullet in the aforementioned commit state to see how this could be implemented to make a laser. Since the gun already has a bullet, we can just use it for the Turrets and enemies as well, maybe with some minor tweaks to color, size, model, or damage value, so I'll be closing this ticket.


Colorscheme incorrectly displayed on Windows 11 terminal

Steps to reproduce
Hello everyone, I am using Windows 11 23H2 and I want to configure my vim on terminal.
I first opened cmd (not PowerShell !).
When I :set termguicolors or :set t_Co=256 , then :colo default.The colorsheme shows unexpectedly incorrect. The background is black which I looks very uncomfortable, like this:

I tried :set bg=light,but the background not changed, still black.
I was thinking my colorscheme file may be somewhere incorrect. For the reason that my cmd line is not black normally but changes black just as I enter vim,I think this may be vim's reason(maybe).
I searched everywhere for that but got nothing useful.
Suddenly, I found that, when I open a powershell in the same window the cmd in with different tabs, the same commands resulted in the correct colors! Just the same as gui!! Like this:

In the same window I opened the third tab, this time cmd again. When I typed vim and enter, what i saw made me surprised that this time the color was correct! Like this:

I tried to repeat the same phenomenon.I first pushed these commands in vimrc like these
set termguicolors
colorscheme default
set background=light

Then I opened in the same order:
1.Win+R to cmd, enter vim ->black
2.In the same window open a new PowerShell tab enter vim -> light
3.The same window then open a new cmd enter vim -> light
Why? Windows' bug or Vim's?
Expected behaviour
I expect the Correct color in the first go in cmd, as the third picture.
Version of Vim
9.1.882
Environment
OS Windows 11 23H2
Terminal: Windows cmd and PowerShell
vimrc
set termguicolors
colorscheme default
set background=light

Logs and stack traces
No response

Honestly, I can't tell a difference between screenshot 2 and 3. Also, please verify using  vim --clean there is at least vim-airline into play, let verify using a minimum vim config first.

Honestly, I can't tell a difference between screenshot 2 and 3. Also, please verify using vim --clean there is at least vim-airline into play, let verify using a minimum vim config first.

Look at the top of every screenshots.
2 is PowerShell and 3 is cmd, which I described in my narrative words (I am not native Eng speaker so there might be some errors in grammar. I'm Sorry for that)
Also I'm sorry for not providing the vim --clean test screenshot.
I verified, and got the same result.
Win+R to cmd
The First Tab cmd---
vim --clean
:set termguicolors
---Black---
then open The Second Tab PowerShell---
(the same steps)
---Light---
then The Third Tab cmd---
（the same steps)
---Light---

A way to confirm that it's not a Vim issue would be to repeat the experiment with another program (e.g., another command-line editor) that uses the terminal's background.

A way to confirm that it's not a Vim issue would be to repeat the experiment with another program (e.g., another command-line editor) that uses the terminal's background.
You got the same phenomenon? So, can you give some information about what probably caused that?
I'm fresh in programming, and this is my first issue. I don't know whether it was the issue of my terminal or vim, so my assumption may be wrong. I'm sorry for that.

A way to confirm that it's not a Vim issue would be to repeat the experiment with another program (e.g., another command-line editor) that uses the terminal's background.

You got the same phenomenon? So, can you give some information about what probably caused that?
I'm fresh in programming, and this is my first issue. I don't know whether it was the issue of my terminal or vim, so my assumption may be wrong. I'm sorry for that.

I wonder why there is the expectation that vim.exe should have white(or light) background. With default windows terminal settings it should be dark:
vim --clean:

Default gui and default terminal colorscheme -- 2 completely different beasts.

I wonder why there is the expectation that vim.exe should have white(or light) background. With default windows terminal settings it should be dark:
vim --clean:

Default gui and default terminal colorscheme -- 2 completely different beasts.

The default terminal and vim is black for sure, but
I was used to :set cursorline, but when i turn that on, I found it difficult to read the word covered. (to test, I opened help document using the terminal's default colorscheme and vim --clean, and one can easily see the low color contrast made it hard to read)

So I am trying to make the color grey and transparent just as the gVim.
I entered these in my vimrc:
set termguicolors
colorscheme default
set background=light

I got customed to the bright style. I set the terminal color theme following the system(light), and the terminal colorscheme a light one

(Sorry for not using English, but u may be able to understand that.)
After these sets, vim terminal should have been to gVim white style (on Windows 11 with 256 Colors), but it did not completely. The first tab black, but surprisingly the second White! ?!

Okay, so terminal background is set to be light. And probably "transparent" normal highlight group doesn't play well with cmd.exe, I don't know.
However as a workaround you can define Normal to be the same color as your terminal:
set termguicolors
set background=light
hi Normal guibg=#FFFFFF guifg=#000000


dgl issue

Dear all,
I created the given environment on a windows computer and experience a dgl error.
(equibind) PS C:\Users\reps\EquiBind> python inference.py --config=configs_clean/inference_file_for_reproduce.yml
Using backend: pytorch
[2022-02-13 09:04:14.926225] [ Using Seed :  1  ]
Traceback (most recent call last):
File "inference.py", line 459, in
inference(args)
File "inference.py", line 121, in inference
seed_all(args.seed)
File "C:\Users\reps\EquiBind\commons\utils.py", line 62, in seed_all
dgl.random.seed(seed)
File "C:\Users.conda\envs\equibind\lib\site-packages\dgl\random.py", line 18, in seed
_CAPI_SetSeed(val)
File "C:\Users.conda\envs\equibind\lib\site-packages\dgl_ffi_ctypes\function.py", line 190, in call
ctypes.byref(ret_val), ctypes.byref(ret_tcode)))
File "C:\Users.conda\envs\equibind\lib\site-packages\dgl_ffi\base.py", line 64, in check_call
raise DGLError(py_str(_LIB.DGLGetLastError()))
dgl._ffi.base.DGLError: [09:04:14] C:\Users\Administrator\dgl-0.5\src\random\random.cc:34: Check failed: e == CURAND_STATUS_SUCCESS: CURAND Error: CURAND_STATUS_INITIALIZATION_FAILED at C:\Users\Administrator\dgl-0.5\src\random\random.cc:34

Hi,
Could it be that you do not have a CUDA GPU?
the env.yml installs

cudatoolkit=10.2
dgl-cuda10.2

I will clarify that in the readme.

Hi, Could it be that you do not have a CUDA GPU?
the env.yml installs

cudatoolkit=10.2
dgl-cuda10.2

I will clarify that in the readme.

I did it on a windows machine to test.
Ok CUDA it is. Thanks


Access missing and cannot re-auth

I've been using GESI in my google sheets script for several weeks now. Today, after several tries over several hours, my usual functions would not pull data from ESI. Checking the Stackdriver logs in Google, I see each of the failed calls from the past couple hours giving the same error:
Error: Access not granted or expired.     at Service_.getAccessToken(Service:454:11)
Assuming something might have gone wrong with my character authorization, I just tried to re-auth using the GESI -> Authorize Character menu option. After authenticating with CCP, I was given this error by script.google.com:
Exception: Data storage error (line 263, file "gesi")

Probably not something you can fix; since reporting, I came across this, which is likely the source of the problem:
https://issuetracker.google.com/issues/162647522

Yea most likely a Google issue.  I'd just try again later.


Maintenance

NIT: Could you add an explanation why we had to change the go version in go.mod to the second commit?

I don't think we had to change it. Just noticed we were still running on 1.18 and I think k8s 1.27 is based on go 1.20

argh.... 😠  I accidentically clicked "close with comment" and now we gotta watch the tests run again and probably a bunch of /retest.

/test e2e-gcp-ovn
/test e2e-aws-ovn

/lgtm

https://issues.redhat.com/browse/SDN-3902

/jira-refresh

/label jira/valid-bug

/retest

/retest

/retest

/retest

/retest-required


only process context event of original application context

What is the purpose of the change
The DubboDeployApplicationListener currently processes all applicationContext event from current ApplicationContext and all its child applicationContext. It will cause duplicate deployment and ApplicationDeployListener will receive multi duplicate vents. The most bad is that, when the application uses hot load of  child spring context, and destroys the child spring context at runtime,  the dubbo infrastructure will be destroyed once receives the child spring context's ContextClosedEvent.
Brief changelog
dubbo-config/dubbo-config-spring/src/main/java/org/apache/dubbo/config/spring/context/DubboConfigApplicationListener.java
dubbo-config/dubbo-config-spring/src/main/java/org/apache/dubbo/config/spring/context/DubboDeployApplicationListener.java
Verifying this change
see the case code in https://github.com/jessin20161124/dubbo_demo.

java -Dspring.profiles.active=provider -Dserver.port=9999 -jar target/dubbo_demo-0.0.1-SNAPSHOT.jar
curl http://localhost:9999/practice/testGetSubApp
curl http://localhost:9999/practice/testDestroySubApp
watch the application log, the dubbo application runs normally.

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

LGTM

Codecov Report

Merging #9637 (a2dabb5) into 3.0 (65bd70b) will decrease coverage by 0.04%.
The diff coverage is 62.50%.

@@             Coverage Diff              @@
##                3.0    #9637      +/-   ##
============================================
- Coverage     65.53%   65.49%   -0.05%
+ Complexity      296      294       -2
============================================
  Files          1188     1191       +3
  Lines         51785    52070     +285
  Branches       7829     7909      +80
============================================
+ Hits          33939    34103     +164
- Misses        14173    14263      +90
- Partials       3673     3704      +31

Impacted Files
Coverage Δ

...spring/context/DubboConfigApplicationListener.java
73.33% <33.33%> (-5.24%)
:arrow_down:

...spring/context/DubboDeployApplicationListener.java
75.00% <80.00%> (-1.60%)
:arrow_down:

...va/org/apache/dubbo/rpc/protocol/tri/Metadata.java
75.00% <0.00%> (-25.00%)
:arrow_down:

.../main/java/org/apache/dubbo/rpc/FutureContext.java
70.58% <0.00%> (-21.08%)
:arrow_down:

.../dubbo/rpc/protocol/tri/command/QueuedCommand.java
68.75% <0.00%> (-15.87%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
:arrow_down:

...ache/dubbo/rpc/proxy/InvokerInvocationHandler.java
69.81% <0.00%> (-15.10%)
:arrow_down:

...he/dubbo/common/bytecode/DubboLoaderClassPath.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...mmon/threadpool/support/AbortPolicyWithReport.java
73.68% <0.00%> (-10.53%)
:arrow_down:

...n/java/org/apache/dubbo/config/AbstractConfig.java
71.83% <0.00%> (-9.05%)
:arrow_down:

... and 82 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 65bd70b...a2dabb5. Read the comment docs.


Adding Branch as a depedency on another Cocoapod, static library error

Hi,
when trying to add Branch framework as a dependency on another pod, the pod install commands complains: target has transitive dependencies that include static binaries
Are there any plans to convert the Branch framework to a dynamic library?

Hey,
it's not a warning. It's an error, preventing from building an internal framework.
We have an internal framework/pod that we use (link) as a base for our apps, that is linked against Branch.
When adding Branch as a dependency in the .podspec file of our internal framework, Cocoapods spits out an error that Branch's framework is build as a static library and not dynamically.
The error:
target has transitive dependencies that include static binaries (path/to/branch)

I am looking in to this -- It's something I'd like to do in the near future, but since this library is used by so many people I want to get a feeling for the impact before simply changing it.

bump — I'm having the same issue.
framework not found Branch for architecture x86_64

You can add Branch directly to your project as a dynamic library by adding the BranchSDK.xcodeproj file to your project.
Here's a step-by-step guide:
https://github.com/BranchMetrics/ios-branch-deep-linking#adding-the-raw-files-branch-sdk-to-your-project


Expression overloads for HasCheckConstraint and HasComputedColumn

This requires translation of the lambda, so it's not just about adding API.

This could also be done in additional APIs:

Default values
Index filters
View definitions (#465)

It could serve as an alternative to parsing the SQL. It could enable us to be smarter when ordering migration operations. (see #12726 & #14030)


[new locale] Support for zh-mo

As both zh-mo and zh-tw use traditional chinese, I used the zh-tw file and credited its authors.
Should resolve #4949

The zh-mo is the same as zh-tw. This is good for me. Maybe it could be merged.

Close in favor of #5356


Set username from HTTP headers?

fetch("/api", {
  headers: {
    'X-Fixture-Name': 'me'
  }
})

This would let us save the file dynamically, rather than relying on recorder.user to be set.
I would need to see if this changes things significantly, since every fixture would need to be loaded and headers would not be a differentiator.

Instead, it may be better to use filename or fixturePath or hash to do this.
It needs to be bi-directional:

When recording, we need to know where to record file file, for ease of use.
When replaying, nock needs to know the difference between asdf.default.json and asdf.someuser.js, and they need to have different headers or something for nock to differentiate (since we need to load all mocks).

Solved in #11


QSPI (1_4_4) Flash not working for board stm32f723e_disco

Describe the bug
The st,stm32-qspi-nor driver seems to have some issue with the board stm32f723e_disco if we use it with four (1_4_4) data lines. In this mode, the driver does either not write or read successfully from the flash.
Reproduce
This can be tested by running the flash_shell sample:
$ west build -p -b stm32f723e_disco samples/drivers/flash_shell
$ west flash

&quadspi {
	pinctrl-names = "default";
	pinctrl-0 = <&quadspi_clk_pb2 &quadspi_bk1_ncs_pb6
                &quadspi_bk1_io0_pc9 &quadspi_bk1_io1_pc10
                &quadspi_bk1_io2_pe2 &quadspi_bk1_io3_pd13>;
    flash-id = <1>;
    status = "okay";

	mx25r512: qspi-nor-flash@0 {
		compatible = "st,stm32-qspi-nor";
        reg = <0>;
        qspi-max-frequency = <80000000>;
        size = <DT_SIZE_M(512)>;
        reset-gpios = <&gpiod 13 GPIO_ACTIVE_LOW>;
        reset-gpios-duration = <10>;
        spi-bus-width = <4>;
        writeoc = "PP_1_4_4";
        status = "okay";

	};
};

/ {
	chosen {
		zephyr,flash-controller = &mx25r512;
	};
};

Shell commands based on sample page:
[00:00:00.010,000] <inf> flash_stm32_qspi: qspi-nor-flash@0: SFDP v 1.6 AP ff with 3 PH
[00:00:00.010,000] <inf> flash_stm32_qspi: qspi-nor-flash@0: SFDP v 1.6 AP ff with 3 PH
[00:00:00.010,000] <inf> flash_stm32_qspi: PH0: ff00 rev 1.6: 16 DW @ 30
[00:00:00.010,000] <inf> flash_stm32_qspi: qspi-nor-flash@0: 64 MiBy flash
[00:00:00.010,000] <inf> flash_stm32_qspi: Flash - address mode: 4B
[00:00:00.010,000] <inf> flash_stm32_qspi: Quad read mode 4 instr [0x6b] supported
[00:00:00.010,000] <inf> flash_stm32_qspi: Quad read mode 7 instr [0xeb] supported
[00:00:00.010,000] <inf> flash_stm32_qspi: Quad read mode 7 instr [0xeb] will be used
[00:00:00.010,000] <inf> flash_stm32_qspi: QE requirement mode: 2
[00:00:00.010,000] <inf> flash_stm32_qspi: Quad mode enabled
[00:00:00.010,000] <inf> flash_stm32_qspi: PH1: ffc2 rev 1.0: 4 DW @ 110
*** Booting Zephyr OS build 15999a4b0fac ***
Found flash controller qspi-nor-flash@0.
Flash I/O commands can be run.
uart:~$ flash_sample page_count
Flash device contains 16384 pages.
uart:~$ flash_sample page_erase 16383
Erasing page 16383 (start offset 0x3fff000, size 0x1000)
uart:~$ flash_sample page_write 16383 8 17 19 28 39
Reading back written bytes:
11 13 14 27 |
uart:~$ flash_sample page_write 16383 4 77 9 1 2
Reading back written bytes:
45 01 01 02 |
uart:~$ flash_sample page_read 16383 4 12
45 01 01 02 | 77 77 77 77 | 77 77 77 77 |
uart:~$ flash_sample page_read 16383 0 16
11 13 14 27 | 45 01 01 02 | 77 77 77 77 | 77 77 77 77
uart:~$

As we can see, the read value do not match with those we actually write.
Expected behavior
Same as shown on the sample page:
uart:~$ flash_sample page_count
Flash device contains 16384 pages.
uart:~$ flash_sample page_erase 16383
Erasing page 16383 (start offset 0x3fff000, size 0x1000)
uart:~$ flash_sample page_write 16383 8 17 19 28 39
Reading back written bytes:
11 13 1c 27
uart:~$ flash_sample page_write 16383 4 77 9 1 2
Reading back written bytes:
4d 09 01 02
uart:~$ flash_sample page_read 16383 4 12
4d 09 01 02 | 11 13 1c 27 | ff ff ff ff
uart:~$ flash_sample page_read 16383 0 16
ff ff ff ff | 4d 09 01 02 | 11 13 1c 27 | ff ff ff ff
uart:~$

Impact
Interacting with the NOR-Flash does not work properly. This also implies that file systems on top of the NOR-Flash do not work properly.
Environment (please complete the following information):

OS: Linux Arch
Toolchain SDK
Version: 15999a4b0fac

Testing quadspi with a stm32l496 disco kit instead (no stm32f723e_disco available)
I set the DTS as follows:
&quadspi {
	pinctrl-0 = <&quadspi_bk1_io0_pb1 &quadspi_bk1_io1_pb0
			&quadspi_bk1_io2_pa7 &quadspi_bk1_io3_pa6
			&quadspi_bk1_ncs_pb11 &quadspi_clk_pa3>;
	pinctrl-names = "default";
	flash-id = <1>;
	status = "okay";

	mx25r6435: qspi-nor-flash@0 {
		compatible = "st,stm32-qspi-nor";
		reg = <0>;
		qspi-max-frequency = <8000000>;
		size = <DT_SIZE_M(64)>; /* 8 MBytes */
		status = "okay";
		label = "QSPI-NOR";
		spi-bus-width = <4>;
		writeoc = "PP_1_4_4";
		jedec-id = [c2 28 17];
		sfdp-bfp = [
			e5 20 f1 ff  ff ff ff 03  44 eb 08 6b  08 3b 04 bb
			ee ff ff ff  ff ff 00 ff  ff ff 00 ff  0c 20 0f 52
			10 d8 00 ff  23 72 f5 00  82 ed 04 cc  44 83 68 44
			30 b0 30 b0  f7 c4 d5 5c  00 be 29 ff  f0 d0 ff ff
		];

	};
};

I run the sample  : west build -p auto -b stm32l496g_disco samples/drivers/flash_shell/
uart:~$ flash_sample set_device QSPI-NOR
Leaving behind device QSPI-NOR
uart:~$ flash_sample page_erase 2036
Erasing page 2036 (start offset 0x7f4000, size 0x1000)
uart:~$ flash_sample page_read 2036 0x10
ff ff ff ff | ff ff ff ff | ff ff ff ff | ff ff ff ff
uart:~$ flash_sample page_write 2036 1 2 3 4 5 6 7 8 9 0xa 0xb 0xc 0xd 0xe 0xf
Reading back written bytes:
02 03 04 05 | 06 07 08 09 | 0a 0b 0c 0d | 0e 0f

or
uart:~$ flash_sample write_pattern 0x000fe000 100
Reading back written bytes:
00 01 02 03 | 04 05 06 07 | 08 09 0a 0b | 0c 0d 0e 0f
10 11 12 13 | 14 15 16 17 | 18 19 1a 1b | 1c 1d 1e 1f
20 21 22 23 | 24 25 26 27 | 28 29 2a 2b | 2c 2d 2e 2f
30 31 32 33 | 34 35 36 37 | 38 39 3a 3b | 3c 3d 3e 3f
40 41 42 43 | 44 45 46 47 | 48 49 4a 4b | 4c 4d 4e 4f
50 51 52 53 | 54 55 56 57 | 58 59 5a 5b | 5c 5d 5e 5f
60 61 62 63 |

Hi @FRASTM,
thank you very much for your instant support  and please apologize my late reply.
You are right, the NOR-Flash works perfectly fine with our devicetree file. If I have not misunderstood the driver, there is no need to specify the jedec-id and sfdp-bfp because it pulls the values at runtime during the flash_stm32_qspi_init function is running. Is this correct?
However, it seems like the reset configuration in the device tree breaks the functionality. So after removing the two lines below, the sample works perfect for me.
reset-gpios = <&gpiod 13 GPIO_ACTIVE_LOW>;
reset-gpios-duration = <10>;
```

So here are the final device tree construct for the QSPI-Flash device from the stm32f723e_disco.
```
// QSPI Flash Controller
&quadspi {
	pinctrl-names = "default";
	pinctrl-0 = <&quadspi_clk_pb2 &quadspi_bk1_ncs_pb6
                &quadspi_bk1_io0_pc9 &quadspi_bk1_io1_pc10
                &quadspi_bk1_io2_pe2 &quadspi_bk1_io3_pd13>;
    flash-id = <1>;
    status = "okay";

	mx25r512: qspi-nor-flash@0 {
		compatible = "st,stm32-qspi-nor";
		reg = <0>;
		qspi-max-frequency = <8000000>;
		size = <DT_SIZE_M(512)>; /* 64 MBytes */
		status = "okay";
		spi-bus-width = <4>;
		writeoc = "PP_1_4_4";
	};
};

// Use the QSPI driver as flash
/ {
    chosen {
		zephyr,flash-controller = &mx25r512;
	};
};
```

Should I open a PR to add the QSPI and flash definition to the board device tree?

Ok, I will create a PR for the device tree, however I am currently blocked and I will need some time.

Ok, I will create a PR for the device tree, however I am currently blocked and I will need some time.

I can proceed, if you accept. It's just updating the DTS of the board.

Ok, I will create a PR for the device tree, however I am currently blocked and I will need some time.

I can proceed, if you accept. It's just updating the DTS of the board.

Sure, please go ahead


Feature request: generate from non-generic type (so with Type parameter)

I would like to generate from a Type parameter,
e.g.
Type type = ...
object generateObject = new AutoFaker(type).Generate();

Current work around:
Type type = ...
Type autoFakerType = typeof(AutoFaker<>).MakeGenericType(type);
dynamic autoFaker = Activator.CreateInstance(autoFakerType) ?? throw new Exception($"Failed creating type {autoFakerType.FullName} gefaald");
object generateObject = autoFaker.Generate();

Is a PR accepted for this? (needs some refactoring to replace internal calls from generic to non-generic)
This is maybe the same question: https://github.com/nickdodd79/AutoBogus/issues/98

Ah! Duplicate of https://github.com/nickdodd79/AutoBogus/issues/75


Django 1.10 support. 'AppCommand' has no attribute 'option_list'

when I run  this command this gives error.
AttributeError: type object 'AppCommand' has no attribute 'option_list'
:(
that's why http://<IP_ADDRESS>:8000/ gives me page not found

This is due to your django version. You are using 1.10, correct? They deprecated option_list. I will work on this if I get a chance, but I'm really busy with school at the moment.
A similar thing is being done, to drop earlier django support on my other repo, if you'd like to give a stab at it yourself. https://github.com/Brobin/django-seed/pull/38/files

Thanks for replay.
I have solve that .... And its works,
Just  add fields in api/serializers.py file... Thanks a lot, one of the
best website I never seen ..
On Nov 28, 2016 8:26 PM, "Tobin Brown"<EMAIL_ADDRESS>wrote:

This is due to your django version. You are using 1.10, correct? They
deprecated option_list. I will work on this if I get a chance, but I'm
really busy with school at the moment.
A similar thing is being done, to drop earlier django support on my other
repo, if you'd like to give a stab at it yourself.
https://github.com/Brobin/django-seed/pull/38/files
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Brobin/drf-generators/issues/28#issuecomment-263291551,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATXC7nm1--5qUKqzW4mSFPb1Z8porls3ks5rCuuDgaJpZM4K7jjp
.

doh, im not getting any clue out of it.. how to solve it?

Install the latest version (0.3.0) and this should be resolved. There were 2 open PRs to fix this, but noone was responding, so I did it myself.


test: Add more unit tests [DEV-2506]

Task linked: DEV-2506 Create unit tests for DID URL dereferencing


Distributivity of wsums

Many of the transformations for I(L)P solvers require the translation of constraints to weighted sums.
For this, it would be very handy to have distributivity of integer multiplication be implemented for wsum.
I.e, the following:
import cpmpy as cp

x = cp.intvar(0,10, shape=3)
expr = cp.sum(x * [1,2,3])
print(expr)
>> sum([1, 2, 3] * [IV0, IV1, IV2])
10 * expr
>> sum([10, 20, 30] * [IV0, IV1, IV2])

I think this should be part of a more general improvement of the wsum concept in CPMpy.
We should be more aggressive in converting to wsums using some kind of normalization or by doing it at construction time and probably also add an explicit wsum constructor so you can do cp.wsum([1,2,3], x) instead.

in normalized_numexpr we convert some things to wsums but not all things (for example not normal sums) maybe everything should become a wsum there?


feat: add control grouping functionality

🏆 Enhancements
This adds support for control grouping introduced in https://github.com/apache/incubator-superset/pull/9740 .

Thanks for the review @kristw ; my apologies for the brief description, I meant to expand on the initial description but got sidetracked. Will add more context to describe why this change is necessary and pointers for some design decisions. Also, as this is my first real stab at TS, I fully expect there to be inconsistencies, so if something looks weird, it's probably because I've done it wrong.

I think the term "control group" is kind of confusing. It took me quite a while to understand what problem this PR tries to solve.
If I'm getting it right, this is about consolidating control fields required for constructing DB queries (metrics, groupby, and columns). They may have as arbitrary field names, but the backend needs to know which are metrics fields, which are groupby, etc.
It's not grouped control as in UI components, but more like grouped query API parameters or consolidated query fields. The term control group is also too commonly used in Data Science in the context of hypothesis testing, i.e., A/B tests.
Can we maybe rename the variables/functions as such:
controlGroups -> queryFields
buildGroupedControls -> extractQueryFields
defaultedControlGroups -> aliases or queryFieldAliases

Thanks all for the comments! ❤ Will implement changes and update description + comment where necessary.


Pass diffstyle.css tests in Chromium

Let's turn these tests green, let's remember to check Puppeteer's code

This is not a test


Add ML notebook to demo dea_classificationtools

Seems like it would be a good idea to write a notebook as part of the refresh to demonstrate the functions in the dea_classificationtools module, otherwise users may not be aware that the ML functionality exists.

Yep, definitely agree: it'd be great if we had an demo notebook for each function we add to Scripts so people have a starting point to using the functions.
Feel free to make a Frequently_used_code notebook for each different ML functionality you add - I think several smaller/discrete notebooks will be easier to use than fewer long/complex notebooks.


Share connection between threads?

I'm trying to share connection between threads for executing callbacks of different queries.
Although, scoped thread is used to prevent 'static lifetime requirement for spawning.
However, scoped thread is not able to be spawned, which capture the reference of the connection.
Because, neither Connection nor Cursor is not Send marked.
The problem is Can connection handle multi queries concurrently?
The following code works as expected.
let env = Envirnoment::new().unwrap();
let conn = env.connect_with_connection_string(&conn_str).unwrap();

let r1 = conn.execute(&query1).unwrap();
let r2 = conn.execute(&query2).unwrap();

consume(r1);
consume(r2);

My expected concurrent code as below, so that consuming results from different queries with the same connection can be executed concurrently.
crossbeam_tuils::thread::scope(|scope|{
    let env = Envirnoment::new().unwrap();
    let conn = env.connect_with_connection_string(&conn_str).unwrap();

    {
        let conn = &conn;
        scope.spawn(move |_| {
            let r = conn.execute(&query1).unwrap();
           consume(r);
        });
    }

    {
        let conn = &conn;
        scope.spawn(move |_| {
            let r = conn.execute(&query2).unwrap();
           consume(r);
        });
    }
};

@hu6360567 Closing this issue for now. Feel free to open a new one, if you feel the library should support this better.


[Feature] Want to add Newtons Cradle Loader

Description
I want to add  Newtons Cradle Loader into the Loader Section. I am attaching the loader screenshot. Please assign me this issue under JWOC 2024.
Screenshots

Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[X] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Proceed @bera474


Test integer to string conversions with all DBMS

Such test has been added for SQLite only in #190.
It should be moved to generic tests to cover all databases we test on CI services.
It also should be checked if the column size and value truncation which occur with SQLite is a common issue, see https://github.com/lexicalunit/nanodbc/pull/176#issuecomment-229479993, then probably we want to improve the implementation of conversions.

This issue was moved to nanodbc/nanodbc#21


nil, is being prefixed to functions

nil seems to be automatically being added as a parameter to functions where it shouldn't be added.

I've read about this perhaps being the self/this reference, if so, how do I get rid of it? Since these functions break due to this fact.

did you read this page yet?

did you read this page yet?

That does not seem to apply to functions outside of your own project :)

I have been able to get around this by modifying TSTL's code and adding my own checks, although I do not really believe that is a great solution, so I would still highly appreciate suggestions.

Yeah, but that does not seem to apply to functions outside of your own project

are you talking about upstream lua? are you typing your own definitions?

Yeah, but that does not seem to apply to functions outside of your own project

are you talking about upstream lua? are you typing your own definitions?

I'm making add-ons for a game which supports Lua and JS.
Whereas I need the files to be in Lua, but would really love to still be able to use TS.
So the functions I'm using are related to that game and defined in these npm packages:
https://www.npmjs.com/package/@citizenfx/client
https://www.npmjs.com/package/@citizenfx/server
Hence why the functions aren't defined in my local project files and most likely why it doesn't work.

if the game supports JS then why are you using TSTL at all? can't you just use typescript and use the normal TS compiler to transpile to JS?

Whereas I need the files to be in Lua, but would really love to still be able to use TS.
From my previous message ^^

The game requires Lua for quite a lot of functionalities, especially for publishing your projects, hence why I would need to use Lua :) I already use Ts -> JS where it is possible.

can you post a playground that illustrates the problem?

https://github.com/Z3rio/fivem-tstolua/tree/08f0d4ea04bd2beee8c4944e9c62c25efeced630

main directory -> npm run build
(Ignore ui directory)

Seems to be happening due to the fact that @citizenfx/client's type def's don't include this: void
Example type def

This is funny expected behavior. In JS, every function call will pass the this object as a hidden extra argument by default. This means that in the normal case, there is never any need to specify this behavior when making declarations for JS (which this seem to be).
By contrast, in Lua there is no hidden variables being passed around. This means tstl will need more information to decide wether to call your function as an object method (with a this object, or with : instead of .) or not. This information we get from the declarations.
If nothing is specifically specified, we assume your code works like the JS implicitly specify: All function calls get a hidden this object. The declarations you are using here are simply lacking the information tstl requires to make a correct translation.


Roll engine to e44cd55fc452ba5524147280c451fb3ace350ec4

Seems like this PR grew flutter_gallery_ios__transition_perf average_frame_rasterizer_time_millis by ~20%. Is it expected?

This caused a bunch of regressions actually.

Specifically it looks like it regressed the rasterizer on iOS.


Re-enabling Button for user to click again.

Thanks for sharing. I am facing one problem while using this. If task fails i have set the value to -1(Error) but after 1000ms i have to reset the button for user to re-try and click. I tried setting value to 0 "Normal" but it is not animating if i click it 2nd time can anyone help. below is the code i am using.
public void onFailure(final ProcessButton button) {
button.setEnabled(false);
button.setProgress(-1);
button.setText("Cancellation Failed!! Try Again");
final Handler Failurehandler=new Handler();
Failurehandler.postDelayed(new Runnable() {
@Override
public void run() {
mProgressFailure += 10;
if (mProgressFailure < 100) {
Failurehandler.postDelayed(this, generateDelay());
} else {
button.setEnabled(true);
button.setProgress(0);
button.setText("click to cancel");
}
}
},generateDelay());
Toast.makeText(this.getContext(), "Task Failed", Toast.LENGTH_LONG).show();
}

#issue resolved. adding mprogress=0 worked for me.
public void start(final ProcessButton button) {
final Handler handler = new Handler();
handler.postDelayed(new Runnable() {
@Override
public void run() {
mProgress += 10;
button.setProgress(mProgress);
if (mProgress < 100) {
handler.postDelayed(this, generateDelay());
} else {
                onFailure(button);
                mProgress=0;
            }
        }
    }, generateDelay());
}


Issue 717 use nvm in docker build

Which issue does this PR close?
Closes #717.
Rationale for this change
The current build for the main branch is broken, as reported in the issue #717. This change aims to make it working again.
What changes are included in this PR?

Changes to the builder Dockerfile to use the NVM to install the appropriate node version.
Sets node version to v16.9.1

Are there any user-facing changes?
No, but it may be useful to update the documentation to showcase that it's now possible to build from the main branch.

Built docker images:

@andygrove Hi, I saw you recently triggered the docker build on the other PR. It won’t work until this issue is addressed first (pinning down a compatible node version).
If it helps to review/test I could instead address both issues on a single PR instead.

Hi, @paolorechia! I also submitted a patch (#731) for this, but installing nodejs from source, using node version 18. Take a look and see which you prefer... I can close mine

which you prefer

I'd advocate for whichever is easier for the developer to:

see in the CI script
reproduce in their local environment

IMO nvm would be closer to that as they might have to deal with multiple versions of node, and it's a one line command.

Hi, @jnaous
I don't have a strong preference here, I just wanted to fix the build so I could move forward with docker build workflow: https://github.com/apache/arrow-ballista/issues/162
One advantage I see with your PR is that you use Node 18 as opposed to Node 16 from my PR, as I ran into issues with the OpenSSL library.
It seems that you solved this issue with Node 18 it by adding --openssl-legacy-provider into the react build command, so it should also be easy to reuse your solution with my NVM PR.
Either way, both approaches work for me.

It's stale for a while.


Update .openpublishing.publish.config.json

Docs Build status updates of commit b1144db:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Send a message

Add the ability to send a message across a channel by posting to /channels/channel-id/messages. Adds the message to the correct rabbitmq queue for the specified channel-id.

The large coverage decrease is mainly because I don't know if there is a sane way of testing the Amqp factory and client.

Probably ready for a proper review

Made a few more comments, looks good :)

Okay, I think I've addressed all of the comments @justinvdm

:+1:!


Update Mistral client class to support new Mistral v1.0.1 package

Mistral AI released an updated python client package, v1.0.1, which had breaking changes to code using versions before then. This updated Mistral client class has been updated to support the new version.
No new functionality has been added, but prices have been updated.
Why are these changes needed?
Existing code will not work with the latest Mistral AI (mistralai) package.
Related issue number
None, yet :).
Checks

[X] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[X] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[X] I've made sure all auto checks have passed.

Codecov Report
Attention: Patch coverage is 6.66667% with 28 lines in your changes missing coverage. Please review.

Project coverage is 36.28%. Comparing base (3fc708d) to head (ca334a9).

Files
Patch %
Lines

autogen/oai/mistral.py
6.66%
28 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3356      +/-   ##
==========================================
+ Coverage   33.33%   36.28%   +2.94%
==========================================
  Files          95       95
  Lines       10661    10669       +8
  Branches     2278     2453     +175
==========================================
+ Hits         3554     3871     +317
+ Misses       6791     6440     -351
- Partials      316      358      +42

Flag
Coverage Δ

unittests
36.24% <6.66%> (+2.92%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

LGTM.


Could not resolve: org.springframework.cloud:spring-cloud-starter-consul

Hi,
I am using gradle to build. Gradle reports not able to resolve consul related dependency. Tried both consul-all and consul-dependency. Both reported similar errors.
Could not resolve: org.springframework.cloud:spring-cloud-starter-consul-all
Could not resolve: org.springframework.cloud:spring-cloud-starter-consul-discovery:

build.gradle snapsot :-
dependencies {
    compile("org.springframework.boot:spring-boot-starter-web")
    compile("org.springframework.cloud:spring-cloud-starter-consul-all")
    //compile("org.springframework.cloud:spring-cloud-starter-consul-discovery")
    // tag::actuator[]
    //compile("org.springframework.boot:spring-boot-starter-actuator")
    // end::actuator[]
    // tag::tests[]
    testCompile("org.springframework.boot:spring-boot-starter-test")
    // end::tests[]
}

Thanks.

They are maven central. You have said what BOM version you are using either. Please show your whole build file.

4.0.0
com.micro
SpringMicroService
0.0.1-SNAPSHOT
SpringMicroService
Spring boot

org.springframework.cloud
spring-cloud-starter-parent
Brixton_.RELEASE

org.springframework.boot
spring-boot-starter

    <dependency>
        <!-- Setup Spring MVC & REST, use Embedded Tomcat -->
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
    </dependency>

    <dependency>
        <!-- Spring Cloud starter -->
        <groupId>org.springframework.cloud</groupId>
        <artifactId>spring-cloud-starter</artifactId>
    </dependency>

    <dependency>
        <!-- Eureka for service registration -->
        <groupId>org.springframework.cloud</groupId>
        <artifactId>spring-cloud-starter-eureka-server</artifactId>
    </dependency>
</dependencies>

<properties>
	<java.version>1.8</java.version>
</properties>

This is pom.xml. It shows error
Error: Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.springframework.cloud:spring-cloud-starter-parent:pom:Brixton_.RELEASE in central (https://repo.maven.apache.org/maven2)
Kindly help to sort this. Went through couple of blogs but with no help.

No underscore in name. Brixton is no longer supported.

Hi
How i am supposed to configure spring cloud in pom.xml. Could you please refer or suggest.

You can see how to setup the POM here http://projects.spring.io/spring-cloud/.  Pick the version of Spring Cloud you want to use and copy the XML.

Hi Ryan
The issue is resolved now. Below is what i did

Deleted .m2(local repo) folder
run the command mvn package
after that update maven of the project

Worked for me , seems some of the jars are broken. Nothing was wrong with
pom.xml
Regards
Alok Mazumdar
On Sat, Dec 16, 2017 at 6:27 PM, Ryan Baxter<EMAIL_ADDRESS>wrote:

You can see how to setup the POM here http://projects.spring.io/
spring-cloud/. Pick the version of Spring Cloud you want to use and copy
the XML.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/spring-cloud/spring-cloud-release/issues/72#issuecomment-352181928,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ2KYl-8evPiEcPEjCmzz8WiJH_ngY_wks5tA74mgaJpZM4Ma6jL
.

Hai all .
could you pleases help out this error  in pom.xml , iam using spring boot with eureka when iam adding the below dependency it is saying --:Project build error: 'dependencies.dependency.version' for org.springframework.cloud:spring-cloud-starter-eureka:jar is missing.

org.springframework.cloud
spring-cloud-starter-eureka

My Boot version is below one

org.springframework.boot
spring-boot-starter-parent
2.1.0.RELEASE

Thank you,
Srinivas.

In the future, please don't comment on old closed issues. Has nothing to do with the boot version.
https://github.com/spring-projects/spring-cloud/wiki/Spring-Cloud-Edgware-Release-Notes#renamed-starters


use a batch of image as input

Hi guys, is there any example that can convert multiple image to one tensor with dimension [batch_size, channel, witdth, height]? I am hoping this may be more efficient towards to real inference scenarios.

I believe this may be possible with the OpenVINO backend in Wasmtime, but it could bear some investigation. The wasi-nn bindings repository has Rust and Assembly script examples of running an inference with a single image and you could adapt those to batch several images into one request. I think, but have not checked, that the first dimension in those examples can be used to indicate that the tensor contains multiple images (but now that I'm looking at the docs, I'm wondering if OpenVINO also needs some configuration). If you are interested in discussing further, I am usually online on Zulip if you want to chat.

thanks! I'm checking the soluation as well, I see in openVINO python or C APIs, there is a attribute to open inferencer's batch mode, maybe find out where to open this attribute in IR code could be useful.

@ln23415, did you figure out how to pass multiple tensors in through the wasi-nn API?


Finish up removal of Conditions 🧹

Changes

In https://github.com/tektoncd/pipeline/pull/4942, we removed Conditions. However, there was some logic that was left over. In this change, we clean up the remaining logic for Conditions.
Issue: https://github.com/tektoncd/pipeline/issues/3377
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[n/a] Docs included if any changes are user facing
[n/a] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in (if there are no user facing changes, use release note "NONE")

Release Notes

NONE

/lgtm
Ooops, I did miss a little bit. =)