satori-astro fails on Cloudflare Pages due to Node.js built-in module dependency

I'm encountering a build failure when trying to use satori-astro on Cloudflare Pages. The error suggests that there's an issue with bundling the Node.js built-in "fs" module, which is being imported from the @resvg/resvg-js package, which is a dependency of satori-astro (
  satori-astro@0.0.1(astro@4.15.0(@types/node@22.5.1)(rollup@4.21.1)(typescript@5.5.4)):
    dependencies:
      '@resvg/resvg-js': 2.6.2

).
Error message:
[ERROR] [vite] x Build failed in 4.36s
[commonjs--resolver] [plugin vite:resolve] Cannot bundle Node.js built-in "fs" imported from "node_modules\.pnpm\@resvg+resvg-js<EMAIL_ADDRESS>Consider disabling ssr.noExternal or remove the built-in dependency.

This error occurs during the build process and prevents the successful deployment on Cloudflare Pages.
My astro config file:
import { defineConfig, envField } from "astro/config";

import cloudflare from "@astrojs/cloudflare";
import svelte from "@astrojs/svelte";
import auth from "auth-astro";
import tailwind from "@astrojs/tailwind";
import icon from "astro-icon";
import db from "@astrojs/db";
import i18n from "@astrolicious/i18n";
import satori from "satori-astro";

// https://astro.build/config
export default defineConfig({
  site: "xxxxxx",
  prefetch: true,
  integrations: [
    icon({
      include: {
        "material-symbols": ["translate-rounded", "dark-mode-rounded", "light-mode-rounded", "send-rounded", "info-rounded", "brightness-auto-rounded", "borg-rounded"],
        bxl: ["google"],
      },
    }),
    i18n({
      defaultLocale: "en",
      locales: ["en", "it", "es", "fr", "de"],
      client: {
        data: true,
        paths: true,
        translations: true,
      },
      sitemap: true,
    }),
    svelte(),
    auth(),
    tailwind(),
    db(),
    satori(),
  ],
  output: "server",
  adapter: cloudflare(),
  security: {
    checkOrigin: true,
  },
  vite: {
    ssr: {
      external: ["buffer", "path", "fs", "os", "async_hooks"].map((i) => `node:${i}`),
    },
  },
  experimental: {
    contentIntellisense: true,
    env: {
      schema: {
xxxx
      },
    },
  },
});

On Cloudflare Pages I set the compatibility flags to nodejs_compat, but it didn't change anything. Please advise since this is preventing me from pushing a SEO update. Thank you for your work anyways, it works perfectly in dev, its the build that is causing problems.

Update: The repository has been forked, and the code transitioned from resvg to svg2png-wasm. This change eliminates the need for Node, potentially resolving previous issues and possibly enhancing speed, although this has not been tested yet. I will create a PR to hear your thoughts.

I didn't know resvg used fs, not sure what's the best option here 🤔. I guess you're using this package at runtime?

Looks like we can't fix this...unless we swap resvg for another package! Maybe sharp?

Maybe... or something else entirely... I don't really have suggestions, I already implemented svg2png-wasm to try and see if cloudflare liked it (it didnt like it, got some weird errors). I could do a PR and maybe merge in a test branch and see if being installed from npm makes a difference rather that doing everything in a workspace. I also improved the playground, I can do a PR for that too :)

PRs welcome! I'm experimenting with resvg wasm

great, now the project builds
but if i try to access the image i get this error:
i get this error
 "logs": [
   {
     "message": [
       "14:51:14 [ERROR] Error: Wasm has not been initialized. Call `initWasm()` function.\n    at new Resvg2 (pages/og/_lang_/_route_.png.astro.mjs:564:13)\n    at Object.toImage (pages/og/_lang_/_route_.png.astro.mjs:21257:14)\n    at async Object.toResponse (pages/og/_lang_/_route_.png.astro.mjs:21263:21)\n    at async Module.GET (pages/og/_lang_/_route_.png.astro.mjs:21410:10)\n    at async renderEndpoint (chunks/astro/server_D7qu0pls.mjs:72:20)\n    at async lastNext (chunks/_@astrojs-ssr-adapter_REKAsyNY.mjs:1269:23)\n    at async callMiddleware (chunks/_@astrojs-ssr-adapter_REKAsyNY.mjs:590:10)\n    at async RenderContext.render (chunks/_@astrojs-ssr-adapter_REKAsyNY.mjs:1308:22)\n    at async App.render (chunks/_@astrojs-ssr-adapter_REKAsyNY.mjs:2057:18)\n    at async Object.fetch (chunks/_@astrojs-ssr-adapter_REKAsyNY.mjs:2254:22)"
     ],
     "level": "error",
     "timestamp":<PHONE_NUMBER>571
   }
 ],


minor grammar fixes

Also, the expression is commonly written as all of a sudden.

Thanks!

Cheers! :beer:


Appstudio update test-component-pac-aztm

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-aztm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
14 seconds
init

✅ Succeeded
23 seconds
clone-repository

✅ Succeeded
27 seconds
build-container

✅ Succeeded
19 seconds
deprecated-base-image-check

✅ Succeeded
15 seconds
inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
45 seconds
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
22 seconds
label-check

✅ Succeeded
22 seconds
optional-label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-aztm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
14 seconds
init

✅ Succeeded
23 seconds
clone-repository

✅ Succeeded
27 seconds
build-container

✅ Succeeded
15 seconds
inspect-image

✅ Succeeded
19 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
45 seconds
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
22 seconds
optional-label-check

✅ Succeeded
22 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-aztm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
25 seconds
build-container

✅ Succeeded
11 seconds
inspect-image

✅ Succeeded
10 seconds
deprecated-base-image-check

✅ Succeeded
34 seconds
clamav-scan

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
5 seconds
label-check

✅ Succeeded
6 seconds
optional-label-check

✅ Succeeded
4 seconds
show-summary

✅ Succeeded
3 seconds
show-sbom


Running the quad example with the Vulkan backend fails after installing the latest Vulkan SDK from LunarG

Short info header:

GFX version: commit fe1a91f
OS: Windows 10
GPU: GTX 1070

AdapterInfo { name: "GeForce GTX 1070", vendor: 4318, device: 7041, software_rendering: false }
Memory types: [MemoryType { properties: (empty), heap_index: 1 }, MemoryType { properties: (empty), heap_index: 1 }, MemoryType { properties: (empty), heap_index: 1 }, MemoryType { properties: (empty), heap_index: 1 }, MemoryType { properties: (empty), heap_index: 1 }, MemoryType { properties: (empty), heap_index: 1 }, MemoryType { properties: (empty), heap_index: 1 }, MemoryType { properties: DEVICE_LOCAL, heap_index: 0 }, MemoryType { properties: DEVICE_LOCAL, heap_index: 0 }, MemoryType { properties: COHERENT | CPU_VISIBLE, heap_index: 1 }, MemoryType { properties: COHERENT | CPU_VISIBLE | CPU_CACHED, heap_index: 1 }]
ERROR 2018-07-30T10:10:07Z: gfx_backend_vulkan: [Validation]  [ VUID-VkMappedMemoryRange-size-01390 ] Object: 0xf (Type = 8) | vkFlushMappedMemoryRanges: Size in pMemRanges[0] is 0x60, which is not a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize (0x40). The spec valid usage text states 'If size is not equal to VK_WHOLE_SIZE, size must either be a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize, or offset plus size must equal the size of memory.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkMappedMemoryRange-size-01390)
ERROR 2018-07-30T10:10:07Z: gfx_backend_vulkan: [Validation]  [ VUID-VkMappedMemoryRange-size-01390 ] Object: 0x11 (Type = 8) | vkFlushMappedMemoryRanges: Size in pMemRanges[0] is 0x64a28, which is not a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize (0x40). The spec valid usage text states 'If size is not equal to VK_WHOLE_SIZE, size must either be a multiple of VkPhysicalDeviceLimits::nonCoherentAtomSize, or offset plus size must equal the size of memory.' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkMappedMemoryRange-size-01390)
formats: Some([Bgra8Unorm, Bgra8Srgb])
Surface format: Bgra8Srgb

The Vulkan backend worked fine before installing the Vulkan SDK (<IP_ADDRESS>). I'm not sure if the issue is with my installation or GFX, since even the cube example supplied with Vulkan SDK fails when running it with the validations turned on.

This is most likely due to an issue caused by a recent steam update, and affects programs running with validation layers turned on.
Try using the environment variable in the link and see if it fixes the crash for you

Thanks, setting the environment variable fixed the issue. I'm still getting the validation errors, but the example doesn't crash any more.


Dotnet n;ao reconhecido

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
Apareceu a seguinte msg no prompt:
'dotnet' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.

@Smarisco check if you opened a new command prompt after the installation (verifique se abriu um novo prompt de comando após a instalação).
If you receive a 'dotnet' is not recognized as an internal or external command error, make sure you opened a new command prompt. If you can't resolve the issue, use the I ran into an issue button to get help fixing the problem

This is a common question with the same root cause, the cmd window needs to be opened after installing. No reply in 18 days, closing.


Exception handler is not properly handling ParserExceptions

parser specific parse exceptions (in my case player/world parse exception from screenshot) are never handled but argument parse exception is handled instead providing the original exception as reason

You will need to unwrap the argument parse exception. This is mentioned in the documentation: https://cloud.incendo.org/core/#exception-handling


How can i send searched value/criteria to result view ?

Basically i want to search a word in string and then navigate to new screen and highlight text that is searched on searchScreen.
I know how to highlight a string but dont know how to send searched string to new screen.

There is currently no way without a hack. It would require the implementation of a second parameter for the onSelect method.
Like: onSelect: (dynamic value, String criteria) { ... }.


How to setup comment strings with neovim treesitter and commentstring?

I've been trying to figure out how to setup commentstring for a php file.
I'm trying Treesitterplayground to get information, but have no luck setting up correct comment style.
What is the procedure to find out that info?

plugins:
Plug 'tpope/vim-commentary'
Plug 'nvim-treesitter/nvim-treesitter', {'do': ':TSUpdate'}
Plug 'nvim-treesitter/playground'
Plug 'JoosepAlviste/nvim-ts-context-commentstring'

treesitter config:
if (has("nvim"))
lua <<EOF
require'nvim-treesitter.configs'.setup {
  ensure_installed ={ "javascript", "json", "css", "php", "html", "python", "bash", "regex", "ruby", "yaml", "jsonc", "tsx", "lua", "vue" }, -- one of "all", "maintained" (parsers with maintainers), or a list of languages
  highlight = {
    enable = true,
  },
  indent = {
    enable = false
  },
  context_commentstring = {
    enable = true,
    config = {
    php = {
      element = "XXXX %s ",
      start_tag = "YYYYYYY %s zzz",
      attribute = "ZZZZZZz %s zzz",
      html = "111111 %s zzz"
    }
    }
  },
  playground = {
    enable = true,
    disable = {},
    updatetime = 25, -- Debounced time for highlighting nodes in the playground from source code
    persist_queries = false, -- Whether the query persists across vim sessions
    keybindings = {
      toggle_query_editor = 'o',
      toggle_hl_groups = 'i',
      toggle_injected_languages = 't',
      toggle_anonymous_nodes = 'a',
      toggle_language_display = 'I',
      focus_language = 'f',
      unfocus_language = 'F',
      update = 'R',
      goto_node = '<cr>',
      show_help = '?',
    },
  }
}
EOF
endif

Hey! The tree that the PHP treesitter parser creates seems to be a bit weird and it doesn't seem to match the output in the treesitter playground.
For example, in this simple case, the playground shows the tags, but in reality, the HTML part is just text (everything up to <?php):

(I checked the current node under the cursor with :lua print(require'nvim-treesitter.ts_utils'.get_node_at_cursor(0):type()))
This means that there is no container node that can be used as a check for this plugin. The only nodes are text and program.
However, if I add a PHP end tag (?>), then there is a text_interpolation node:

text_interpolation seems like a good check for setting <!-- %s -->.
Everything inside text_interpolation is once again a text node. This means that  any style or script tags cannot be detected 😕
This is the best result I managed to get:
https://user-images.githubusercontent.com/9450943/112734545-1efcbb80-8f4f-11eb-9125-3f25cd6c378b.mov
I used this config:
  php = {
    text_interpolation = '<!-- %s -->',
  },

And setlocal commentstring=//\ %s in after/ftplugin/php.vim

I'm hoping that once https://github.com/JoosepAlviste/nvim-ts-context-commentstring/issues/3 is implemented, we could use language tree to improve this.

Hey @eduardoarandah, just wanted to let you know that #3 has been implemented and PHP should work a bit better now.
However, I still didn't get the injected CSS and JS working because it doesn't seem like they even get injected.
Anyways, if you manage to inject those languages, then the current solution should work 😄 I just couldn't figure out how to get the injection working.
Other than that, let me know if there are any other problems with PHP.


[FEATURE REQ] Provide oauth private_key_jwt (aka cert based auth) client auth for spring boot starter

Is your feature request related to a problem? Please describe.
For security reasons we would like to do a AAD oauth client authentication using certificates (private_key_jwt) with azure-spring-boot-starter-active-directory
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-certificate-credentials
Describe the solution you'd like
Configuring oauth private_key_jwt client auth for auth code flow in the yaml config by suppling the key/cert.
Describe alternatives you've considered
Basic auth is not good enough
Additional context
With the release of spring security 5.5 private_key_jwt has been build into the platform.
https://docs.spring.io/spring-security/site/docs/5.5.0/reference/html5/#authenticate-using-private_key_jwt
However the oauth spec does not cover the x5t header which AAD needs so that also needs to be added.
Using the azure-spring-boot-starter-active-directory  bring added functionality for token mapping etc which is why we would like to use it.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[X] Description Added
[X] Expected solution specified

Hi, @sander-su .
Thanks for reaching out.
Your request make sense.
I added to [2022] January milestone, which means it will be released before 2022-01-07 if everything goes well.

Closing this issue. Because in spring-cloud-azure 4.0, there is no starter for Azure Active Directory, we will provide samples to demonstrate how to use Spring Security with Azure Active Directory.
Please use this issue to track this feature request: https://github.com/Azure-Samples/spring-boot-application-with-azure-active-directory/issues/1


[site-support-request] tutsplus.com

[22:14:19] ❯
youtube-dl --verbose -t -A https://code.tutsplus.com/courses/one-two-knockout/lessons/introduction --username=xxx --password=xxx
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', '-t', '-A', 'https://code.tutsplus.com/courses/one-two-knockout/lessons/introduction', '--username=xxx', '--password=xxx']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.8 - Darwin-13.4.0-x86_64-i386-64bit
[debug] Proxy map: {}
[generic] introduction: Requesting header
[redirect] Following redirect to http://code.tutsplus.com/courses/one-two-knockout/lessons/introduction
[generic] introduction: Requesting header
WARNING: Falling back on generic information extractor.
[generic] introduction: Downloading webpage
[generic] introduction: Extracting information
ERROR: Unsupported URL: http://code.tutsplus.com/courses/one-two-knockout/lessons/introduction; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 530, in _real_extract
    doc = parse_xml(webpage)
  File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 1472, in parse_xml
    tree = xml.etree.ElementTree.XML(s.encode('utf-8'), **kwargs)
  File "/usr/local/opt/pyenv/versions/2.7.8/lib/python2.7/xml/etree/ElementTree.py", line 1300, in XML
    parser.feed(text)
  File "/usr/local/opt/pyenv/versions/2.7.8/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
    self._raiseerror(v)
  File "/usr/local/opt/pyenv/versions/2.7.8/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
    raise err
ParseError: not well-formed (invalid token): line 3, column 383
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 521, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 178, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 869, in _real_extract
    raise ExtractorError('Unsupported URL: %s' % url)
ExtractorError: Unsupported URL: http://code.tutsplus.com/courses/one-two-knockout/lessons/introduction; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

As with #3661 -

I can try working on a pr, but python is definitely not my forte. If you could help by pointing me in the direction of an extractor that would work similar to this (I'm not sure but maybe I should look at the Lynda extractor?) then I'll give it a shot.

So, the same applies here :smile:

if this was a porn site, i don't think that i will wait all this time

works with the latest version.

works only on free ;(

--cookies should work for non-free videos. If not, please open a new issue.

works great - thanks ;)

@manniR - Are you able to download an entire playlist/course with a single command (e.g. just using the course URL to get all vids) or are you running the command for each video?

@brennebeck

extract tutsplus.com cookie from browser into dl-directory as tutsplus-cookie.txt
copy playlist links from course-site into playlist-links.txt

youtube-dl --cookies tutsplus-cookie.txt -a playlist-links.txt -o '#%(autonumber)s - %(title)s.%(ext)s'

@manniR  All I get by running your command is this error
youtube-dl --verbose https://code.tutsplus.com/courses/one-two-knockout/lessons/introduction<EMAIL_ADDRESS>--password=rajuhaigul -a playlist-links.txt
[debug] System config: [u'--abort-on-error', u'--no-mtime', u'--cookies', u'cookies.txt', u'--console-title', u'--continue', u'--autonumber-size', u'2', u'--retries', u'infinite', u'-o', u'%(chapter_number)s.%(autonumber)s- %(chapter)s\u2014 %(title)s-%(resolution)s.%(ext)s']
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'https://code.tutsplus.com/courses/one-two-knockout/lessons/introduction'<EMAIL_ADDRESS>u'--password=rajuhaigul', u'-a', u'playlist-links.txt']
ERROR: batch file could not be read

Any help would be appreciated?

@ahmadawais you'll need to save the list of URLs you want to download in the playlist-links.txt file, if you use a queue file. So put https://code.tutsplus.com/courses/one-two-knockout/lessons/introduction in the playlist-links.txt and any other URLs on a new line each and run the command from the same directory, without the URL flag:
youtube-dl --verbose<EMAIL_ADDRESS>--password=rajuhaigul -a playlist-links.txt

@brennebeck Thanks for that! Is there any way for me to automate the link capture and playlist-links.txt file formation process on Tuts+?

I have a jquery script I've been using in chrome devtools. The same could be done in Phantom probably so that you get the auto write. I'll post the script when I'm back at my Mac 👍
Sent from my iPhone
On Wed, Aug 3, 2016 at 7:26 PM +0800, "Ahmad Awais"<EMAIL_ADDRESS>wrote:
@brennebeck Thanks for that! Is there any way for me to automate the link capture and playlist-links.txt file formation process on Tuts+?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@brennebeck Great! Looking forward!

@ahmadawais here ya' go: https://gist.github.com/brennebeck/fa9f45c6bef202c75ced4509e326462f
So I have those two scripts saved as snippets in devtools. Here are the steps:

Navigate to the page you want the URLs from (e.g. https://webdesign.tutsplus.com/courses/make-the-leap-from-static-mockups-to-moving-prototypes)
Run the jquerify.js first
Run get-urls.js
The console will have a list of URLs that you can copy and paste now 👍

It wouldn't take too much work to get this to work outside of a browser, but this is quick enough for me. Hope it helps.

@brennebeck  Thank! Where am I supposed to run these scripts? A gif maybe. I will work it out and convert them to bash.

@brennebeck Thanks!
I spent some time and built a bash function for this scrapping.
https://gist.github.com/ahmadawais/065cad34038201d97c257daaddeb2237
Just put it inside your alias file and run  elinks http://domain.com/ playlist-links.txt
Cheers!

Awesome it works ;) Thanks guys

How did you get it to work?

@ahmadawais you'll need to save the list of URLs you want to download in the playlist-links.txt file, if you use a queue file. So put https://code.tutsplus.com/courses/one-two-knockout/lessons/introduction in the playlist-links.txt and any other URLs on a new line each and run the command from the same directory, without the URL flag: youtube-dl --verbose<EMAIL_ADDRESS>--password=pass -a playlist-links.txt

Hi @brennebeck can you please delete this comment as it contains my email (shouldn't be public unsure how I posted it like that) and pass phrase should be deleted anyway even though it was random. Appreciate it.


✨ Release app via GitHub Actions workflow

Is your feature request related to a problem? Please describe.
Once the project is at a stage ready to be released, it would be nice to have an app bundle to download.
Describe the solution you'd like
Once GitHub Actions provides macOS 12 runners, a workflow could be used to automatically build and release the app (e.g. on GitHub Releases), e.g. whenever a new tag is pushed.

Hm, wouldn't it be more appropriate to close the issue as not planned? 🤔

Closing as this is done to my knowledge.


Feat: Included SignalR and Added Nav bars

I created an interface for display message and a sidebar, configured signalr and tested the signalr method. Everything works as intended. I learnt a lot from this test issue.


Filter APIs by lifecycle status in API catalog

Once the API Lifecycle Status feature is working, we want to allow users to filter by lifecycle status when browsing the API catalog.
This issue is a placeholder for further discussion, and will be updated when we are closer to working on the task.
Wireframes

API filtering from API catalog

Should we filter out deprecated APIs by default? How can we give a clear visual hint of this then?

I assume when placing multiple values, the filter should be "OR".

What are the usecases for filtering? When would someone want to filter for anything except the "Live - production" APIs?

/cc @bajiat @kyyberi

See related issue #8
Are these potential use cases for filtering of other that production apis:

design: you would like to comment already at the design phase
testing: you want to see what is coming

@marla-singer Could you take this task? You should be reusing filter component from Organization filter.

@baijat Yep

Please estimate

Done


predict_on_batch does not work with multiple inputs

I am trying to use the predict_on_batch method on a model with multiple inputs passed in a list. For all backends, call and predict work but predict_on_batch fails with the message:
ValueError: Layer 'text_encoder' expected 2 input(s). Received 1 instead.

The same code works without issue on tf.keras.
Here are some minimal colabs showing the difference:

tf.keras colab gist
keras_core colab gist

This is now fixed. Thanks for the report.


chore(package): update url-loader to version 0.6.2

Closes #150

Codecov Report

Merging #152 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #152   +/-   ##
=======================================
  Coverage   91.89%   91.89%
=======================================
  Files           1        1
  Lines          37       37
  Branches        9        9
=======================================
  Hits           34       34
  Misses          3        3

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 3631107...f69049e. Read the comment docs.


Jupyter Notebooks not loading

Environment data

VS Code version: 1.78.1 (VSCodium)
Jupyter Extension version (available under the Extensions sidebar): v2023.3.100
Python Extension version (available under the Extensions sidebar): v2023.8.0
OS (Windows | Mac | Linux distro) and version: Ubuntu 20.04.6 LTS
Python and/or Anaconda version: 3.8.10
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Jupyter server running: Local | Remote | N/A

Actual behaviour
.ipnyb are loding forever. This is true for all files in all workspaces.
Logs
vscode-app-1683797658018.log

Thanks for filing this issue, and sorry you are running into this.
Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

If this still fails, can you try to disable all extensions including Jupyter extension and see if the ipynb files load.
If that works, then try disabling all except the jupyter extension and test loading IPYNB file,
Basically confirm that ipynb fails to load only when Jupyter extension is enabled.

See https://github.com/VSCodium/vscodium/issues/1508
I'm having the same issue and it seems to be related to VSCodium build 1.78.1, not this extension.


Documentation for V3 and V4 missing from Spatie website

The documentation for the V3 and V4 are missing from the Spatie.be website:

Fixed by @riasvdv, thanks!


Go fs

• Does any part of it require special attention?
• Does it relate to or fix any issue?
This is the parsing and transformation side of https://github.com/klothoplatform/klotho-history/issues/466.
We look for the fileblob and transform that to the s3 defintition found in https://gocloud.dev/howto/blob/.
Going to do the IAC side after this so it doesnt grow too large
Standard checks

Unit tests: Any special considerations? Added for query and transform as well as some of the helper functions
Docs: Do we need to update any docs, internal or public? Not yet
Backwards compatibility: Will this break existing apps? If so, what would be the extra work required to keep them working? yes, new feature

Need to update this to be in sync with updates in the imports pr


BigQuery Service Account JSON Authentication not working

Describe the bug
Trying to authenticate to BigQuery using Service Account JSON Authentication because I'm running dbt from a docker container. Since storing the creds inside the container is not safe, I am passing each field as environment variable and parsing them in profiles.yml.
Steps To Reproduce
In profiles.yml:
      keyfile_json:
        type: "{{ env_var('BIGQUERY_TYPE') }}"
        project_id: "{{ env_var('BIGQUERY_PROJECT_ID') }}"
        private_key_id: "{{ env_var('BIGQUERY_PRIVATE_KEY_ID') }}"
        private_key: "{{ env_var('BIGQUERY_PRIVATE_KEY') }}"
        client_email: "{{ env_var('BIGQUERY_CLIENT_EMAIL') }}"
        client_id: "{{ env_var('BIGQUERY_CLIENT_ID') }}"
        auth_uri: "{{ env_var('BIGQUERY_AUTH_URI') }}"
        token_uri: "{{ env_var('BIGQUERY_TOKEN_URI') }}"
        auth_provider_x509_cert_url: "{{ env_var('BIGQUERY_AUTH_PROVIDER_X509_CERT_URL') }}"
        client_x509_cert_url: "{{ env_var('BIGQUERY_CLIENT_X509_CERT_URL') }}"

However when trying to run anything I get:
Please log into GCP to continue
Encountered an error:
Got a non-zero returncode running: ['gcloud', 'auth', 'application-default', 'login']

Expected behavior
dbt should run normally
System information
Which database are you using dbt with?
bigquery
The output of dbt --version:
# dbt --version
installed version: 0.16.0
   latest version: 0.17.0

Your version of dbt is out of date! You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation

The operating system you're using: python:3.7.4-slim
The output of python --version: 3.7.4
Additional context
# gcloud --version
Google Cloud SDK 297.0.0
alpha 2020.06.12
beta 2020.06.12
bq 2.0.58
core 2020.06.12
gsutil 4.51
kubectl 2020.06.12

I switch the method to method: service-account-json but now getting

Could not deserialize key data.
The error message is too vague to troubleshoot further.

Fixed. It was an issue parsing the private_key

Does running DBT locally using using Service Account JSON Authentication work. I tried and got an ```Could not deserialize key data.

Does running DBT locally using using Service Account JSON Authentication work. I tried and got an ```Could not deserialize key data.

Fixed. It was an issue parsing the private_key

Hi, I have been facing the same issue. How did you manage to fix this? :)

I am facing the same issue, @obiii did you ever figure it out?

Hi,
I dnt remeber exactly how it got fixed but I was facing problem with the
key. When I copy paste the key into github env secrets some of the
characters got changes automatically and thus I started copying the key
with “ in the start and the end like this
“Somekey” and then it worked.
On Tue, 2 Nov 2021 at 07:46, Mat Miadlikowski @.***>
wrote:

I am facing the same issue, @obiii https://github.com/obiii did you
ever figure it out?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/dbt-core/issues/2553#issuecomment-957142975,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEHRR62RMOGTR4AFMXVGY53UJ6CMBANCNFSM4N766LIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I used the below command to set a local environment variable with the private key:
export BIGQUERY_PRIVATE_KEY=$(jq -r '.private_key' service-account.json)

Then
echo $BIGQUERY_PRIVATE_KEY

to get a suitable value for GitHub secrets.


added /celery volume for gt worker

added /celery to build file and modified bin scripts accordingly.
related jira: https://issues.redhat.com/browse/CSSRE-2058
JIRA: https://issues.redhat.com/browse/CSSRE-2210
cc @pepedocs @Nanyte25

@vinaybommana this /lgtm


More fixes for Ember 1.10

@rwjblue can you review this one? This was the stuff you handled

Yup was working on it with him in slack.

Good enough for me

@rwjblue oh crap, I thought you meant you already reviewed in slack

I'll pull this down later tonight and play with it a bit. Figure out if we have any new edge cases.

Lol. No worries! I wasn't clear.  It is MUCH closer.


[Bug] Emmesive block textures don't actually work

I noticed a child mod within the mod saying "Puzzle Emmesive Textures" and it said it works for entities and blocks. In entities it works, thanks to CEM ,but not in blocks (I use Fabulously Optimized)

Quote from Motschen >>
In reply to MMotyI:
 It's currently not possible to do that in a sodium-compatible way, but (as far as I'm aware) the developer of Continuity is currently working on making it possible.


fix: reconcile gateway client's node port

Description

Fixes #309
How Has This Been Tested?
Tested it manually using two single node kind clusters.
Checklist:

[x] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR requires documentation updates?
[ ] I've updated documentation as required by this PR.
[x] I have ran go fmt
[ ] I have updated the helm chart as required by this PR.
[ ] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have tested it for all user roles.
[ ] I have added all the required unit test cases.
[ ] I have verified the E2E test cases with new code changes.
[ ] I have added all the required E2E test cases.

Does this PR introduce a breaking change?

@narmidm could you please review and approve this PR? this is a duplicate of 333. I have opened a new one as multiple authors/files got added to the previous PR while rebasing and fixing conflicts which are not relevant to the PR, so opened this new clean one.

Sure @kon3m, will review it and update you soon.

report link  'https://kubeslice.github.io/e2e-allure-reports/Kind-worker-operator-2024-04-04T18:04:41-master-463/index.html'

@narmidm a lot of e2e tests seem to fail after the recent update made to the pipeline.

We've identified the root cause of the end-to-end failure; it was due to the last release. Please allow me half an hour to release a new image for automation, after which I will rerun and verify your PR.
Apologies for the delayed response.

@kon3m can you sync your Branch with master once.

@kon3m A fix has been added for the PR pipeline failure. Pls re sync your branch.

@kon3m We have added a small fix for the PR pipeline failure. Please re sync once more..

@mridulgain @narmidm i have just updated it, can you please trigger the e2e pipeline?

report link  'https://kubeslice.github.io/e2e-allure-reports/Kind-worker-operator-2024-04-15T17:03:02-master-468/index.html'

report link  'https://kubeslice.github.io/e2e-allure-reports/Kind-worker-operator-2024-04-15T20:08:08-master-469/index.html'

report link  'https://kubeslice.github.io/e2e-allure-reports/Kind-worker-operator-2024-04-16T06:16:45-master-469/index.html'

report link  'https://kubeslice.github.io/e2e-allure-reports/Kind-worker-operator-2024-04-16T10:14:23-master-470/index.html'


What query is --custom operating on?

What query is --custom operating on? The resource show result?

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

ID: e76a8ad2-efd8-9e8a-9b2b-eebeb1e9d1d4
Version Independent ID: 280b7ea9-eb6c-9601-464b-09bf8e0cff5d
Content: az resource
Content Source: latest/docs-ref-autogen/resource.yml
Service: azure-resource-manager
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

add to S178

Hi @kingces95, many commands have --custom parameter, which command do you refer to?
If you are referring to az resource wait, then it's judgment condition is based on the attributes of resources, which can be viewed through the az resource show command

Hi @kingces95, many commands have --custom parameter, which command do you refer to?
If you are referring to az resource wait, then it's judgment condition is based on the attributes of resources, which can be viewed through the az resource show command

It is repeated with #15489, so close this issue

It is repeated with #15489, so close this issue


portable-ruby: Add mirrors for the patches

For older versions of curl, work around the error:
curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

@sjackman I don't think this is the right solution here. brew install curl is already configured to ensure it's built to be able to access GitHub. Does brew install curl not fix this?

@sjackman May also want to consider adding stripped bottles in here?

brew install curl is already configured to ensure it's built to be able to access GitHub. Does brew install curl not fix this?

/usr/bin/curl on CentOS 5 is not able to access GitHub, since it gives the above error tlsv1 alert protocol version. brew install curl may fix this issue if it installs curl from bottle rather than from source. You prefer that solution?

/usr/bin/curl on CentOS 5 is not able to access GitHub, since it gives the above error tlsv1 alert protocol version

It shouldn't need to access GitHub; only git does for the installation Homebrew installation and brew install curl should not need to use HTTPS to do so.

@sjackman May also want to consider adding stripped bottles in here?

To contradict myself: let's leave these as-is; the debug symbols are present on macOS and have been useful in (rare) Homebrew Ruby crashes in the past.

brew portable-package ruby needs HTTPS access to GitHub to download the two patches.

Yes but if brew install curl has already been run: why can it not use that curl instead?

brew install curl has not yet been run. Recall: brew install curl may fix this issue if it installs curl from bottle rather than from source. You prefer that solution?

I was avoiding installing any brewed packages to avoid any possible interactions between the foo and portable-foo packages. My caution may not be warranted, if the portable-foo packages are sufficiently isolated from the foo packages.

My caution may not be warranted, if the portable-foo packages are sufficiently isolated from the foo packages.

They are sufficiently isolated, brew portable-package and CI test this isolation and this is the same workflow (brew install curl) as required on Leopard to build the Ruby there.

Feel free to close this issue.

Cool, thanks @sjackman.


How do I use / deploy this?

Is technical documentation available somewhere? Thanks - excited to try using this.

Is technical documentation available somewhere? Thanks - excited to try using this.

You can deploy it via docker as i described here: https://github.com/DenisZagitov/dbdiagram-oss/blob/master/web/README.md


⚠ Bofrost.lu has degraded performance

In 472cc92, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2397 ms

Resolved: Bofrost.lu performance has improved in f6dc04c after 10 minutes.


Random Regions being selected

I have Frankfurt in my preferences but items are being created at random regions.
Created a new Bucket - went to Phoenix
A new ADB - Zurich
Also they both went to root compartment, while i did select my own compartment (for the ADB)

EDIT: this item can be closed as it is not an issue - just some wrong configurations

Thanks @TrantorT for providing an update. I had tried to reproduce this but I was not able to. Closing this issue.

Thanks @TrantorT for providing an update. I had tried to reproduce this but I was not able to. Closing this issue.


"QBuffer::seek: Invalid pos" log spam on stderr

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
Chatterino is spamming "QBuffer::seek: Invalid pos: " to stderr while running. The offsets are random every time, and this happens roughly every minute (sometimes longer), spamming about 200 lines at a time. No particular actions were being done at that time, just chatterino running in the background. However, it seems to also randomly happen on joining any channel (not always, might require multiple tries).
Screenshots
stderr.log
OS and Chatterino Version
Chatterino 2.4.0 (commit 4958d0803) built with Qt 5.15.8 Running on Manjaro Linux, kernel: 5.15.89-1-MANJARO

Without more information, there's nothing I can do as I cannot reproduce this
Please create a new issue if you're able to pin down how to recreate this or how to stop it from happening.
You might be able to figure out where QBuffer::seek: Invalid pos is printed in Qt and set a breakpoint there to maybe bubble up to C2 code.

For future reference, I managed to pin this down to kimageformats (after a recent update, v5.102.0) doing something weird with the Qt image decoders. Not sure what exactly, but removing it made the log spam issue go away so there's probably some weird compatibility issue in there.

I'm experiencing the same issue as Muzuwi on Fedora 38 with Qt 5.15.10. Uninstalling kf5-kimageformats did work.
If someone still needs the support for the specific image formats it adds to QImage then maybe using the logging rules that #4637 added is the way to go.
I simply start chatterino with this environment now: 'QT_LOGGING_RULES=*=false'
But careful, this disables all logging.


Azure-cli install on Codeship.com failing missing Public Key.

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
While running install on Codeship.com we are seeing missing public key error.
Below are logged steps around error message.
Get:13 https://dl.yarnpkg.com/debian stable/main amd64 Packages [9,953 B]
Err:3 https://cli-assets.heroku.com/branches/stable/apt ./ InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5DC22404A6F9F1CA
Get:15 http://apt.postgresql.org/pub/repos/apt bionic-pgdg InRelease [46.3 kB]
Get:16 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic InRelease [15.4 kB]
Get:52 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [10.3 kB]
Get:53 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [4,664 B]
Reading package lists... Done
W: GPG error: https://cli-assets.heroku.com/branches/stable/apt ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5DC22404A6F9F1CA
E: The repository 'https://cli-assets.heroku.com/branches/stable/apt ./ InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
To Reproduce
This command is used as pre build step
sudo apt-get update && sudo apt-get install azure-cli
Expected behavior
To install the azure-cli. Which is has been doing fine for months now.
Environment summary
Codeship.com
Additional context

HI @fengzhou-msft could you pls have a  look? thanks.

@devallish the error seems to be caused by the https://cli-assets.heroku.com/branches/stable/apt repo.  There's an existing issue https://github.com/heroku/cli/issues/497 which was referenced multiple times recently.
azure-cli is not from this repo. Please follow our installation instructions for Ubuntu. You may want to temporarily disable the above repo or wait for their fix.


[PROPOSAL] Support HTTP DID Resolver

We should support resolving DIDs via the Universal Resolver Web API
See resolver architecture discussion: https://github.com/hyperledger/aries-rfcs/issues/101#issuecomment-507417223
Reference implementation of a Web Universal Resolver:
https://github.com/decentralized-identity/universal-resolver/tree/master/resolver/java/uni-resolver-web

@troyronda is a universal resolver implementation part of your proposal, or are you suggesting we just connect to https://uniresolver.io/ ?

@llorllale Connect to the API exposed by https://uniresolver.io/ (but the resolver URL can be configured). This proposal is not about building a universal resolver.

Include mocks of the web resolver API.
Unit tests against the mock implementation.
Include a docker-compose integration test and manually test (we will figure out the CI for this integration test later).

created stories
#99 Create Universal DID Resolver
#100 Create Sidetree DID Resolver
#101 Allow regex expression to resolve did method

Just linking and quoting the rationale that @troyronda exposed here:

The larger story is to have built-in support DID resolution via Web APIs. We are also planning to support universal resolver (via Web API): #99
The idea is that we will also have a shortcut for Sidetree (via Web API) to reduce the need for an extra dependency.

Hi all, just wanted to say I'd be excited to work with you on resolving DIDs via the Universal Resolver's API. Or more generally, we should talk about resolving DIDs via any compliant service that exposes DID Resolution functionality over the HTTP(S) binding. The Universal Resolver is just one implementation of this.
+1 to making everything configurable (not locked into the uniresolver.io instance) and +1 to supporting routing of different DID methods (or patterns) to different resolvers.
And in case you're not aware, there is also a proposed DIDComm binding for DID Resolution, i.e. instead of talking to the Universal Resolver via an HTTP(S) API, you could also talk to it via a DIDComm protocol.
We could have a separate call about this if it helps (or just iterate over existing channels).

@peacekeeper thank you for your comments. I've opened #116 for DID resolution using DIDComm.


Completed non-authenticated portion of the comments API

Implemented:

comments.show
comments.show_batch
comments.hot.by_video

Which completes the non-OAuth part of the comments api.
Tests included

@BenjaminSchaaf :+1:
See: https://rubygems.org/gems/youku_client v0.0.3

Cool, thanks :smile:


Seven Theme - Components

On the components, there is only info.blade.php, made it an info bs5 alert:

Cool. push this up!


Reduce PEP-8 errors

See https://github.com/Senzing/g2-python/issues/123

Pull requests:

https://github.com/Senzing/g2updateproject/pull/24


Null Attributes

The API currently returns objects with attributes that are NULL.  This isn't necessary and it shouldn't do this.  Shouldn't be a hard fix.

Fixed.


Multiplatform WS Client

Hi, I'm toying around with Zig and came across this library. I'm creating a simple prototype for an app that uses the websocket client, but it seems that it only supports Linux due to the posix import. Do you have plans to expand to other platforms?
I'm currently using a Mac, but my build failed on the timeout parts of the code using std.posix.timeval are using the Linux specific fields (.sec and .usec vs .tv_sec and .tv_usec).

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

I assume you're using Zig 0.13?  This was a change in Zig itself since then. Try using the zig-0.13 branch

I assume you're using Zig 0.13? This was a change in Zig itself since then. Try using the zig-0.13 branch


HtmlHelper null pointer exceptions

The HtmlHelperExtensions can throw null pointer exceptions when certain variables like htmlHelper.ViewData[DxaViewDataItems.ContainerSize] are not set.
While this data should normally be set, the HmlHelper should not throw a null pointer exception when this data is not available in the ViewData.
Seen in DXA 2.1

One of the occurrences is fixed in #73. There are more similar instances.

Internal issue ID (for tracking purposes): CRQ-14323

Fixed in DXA 2.2


Add Gradle 8 support

When upgrading to Gradle 8, some configuration changes are required. Especially adding namespace to build.gradle files.

Would be great if we could merge this :) cc @MichaelGHSeg


Add yolo v3/4

https://github.com/eriklindernoren/PyTorch-YOLOv3/issues/487
https://github.com/Tianxiaomo/pytorch-YOLOv4

Hello! I'd like to take this up!

@OrthoDex Have a go at it! We would welcome this contribution from your side. Do go through our contributing guidelines before you submit a PR. (https://pytorch-lightning.readthedocs.io/en/latest/CONTRIBUTING.html)

I'm also interested. @OrthoDex Will you publish your code while it's incomplete?
Beside yolo, I also want to rewrite OCR models in lightning.

@OrthoDex any updates on this?

Hey @ananyahjha93, I'll aim to put up a PR sometime this weekend!

@OrthoDex A group in my lab is about to start doing this. Would love to have your PR as a starting point instead of duplicating efforts =].

I created a pull request of my YOLO implementation, which my employer Groke Technologies authorized to contribute to PyTorch Lightning. It was quite difficult to get it right, since many details can only be found from the different versions of the Darknet C++ implementation (and many details are incorrect in the various PyTorch implementations). So if any of you know the YOLO architecture well, it would be great if you could check if you think that I've made any mistakes.


Set kiosk and theme

Ref. https://github.com/kiali/kiali/issues/6268
TODO: Add merged dark mode from Kiali

No needed


Casters might not work as intended

I think the cast detection system in both BRD and MCH will fail with a caster, but I haven't looked into it

Nevermind, they worked on the first try.


Link to Code of Conduct

Purpose
Added link to Code of Conduct
Changes
_Describe the changes that were needed.
Checklist

[ ] My code follows the style of this project.
[ ] The code compiles without warnings.
[ ] I have performed a self-review of the changes.
[ ] I have documented my code, in particular the intent of the
hard-to-understand areas.

CLA acceptance
_Remove if not applicable.
By submitting the contribution I accept the terms and conditions of the
Contributor License Agreement v1.0

link: https://developers.concordium.com/CLAs/Contributor-License-Agreement-v1.0.pdf

[ ] I accept the above linked CLA.

This is a temporary fork of somebody else's repository, so we should not have the code of conduct here. It is meant to be only temporary.


Feature: LayoutClient

Implement all endpoint methods for the Layout endpoints.
Documentation for the endpoints can be found here: https://docs.novu.co/api/layout-creation/
Endpoints

[ ] Layout creation
[ ] Filter layouts
[ ] Get layout
[ ] Delete layout
[ ] Update layout
[ ] Set default layout

Hi @wh1337,
What are the instructions to set up the project in one's local environment? The CONTRIBUTING guide looks like it'd work for JavaScript-based projects.
Then, the README mentions the Clients directory containing the implementation of API calls. But, the folder is missing in the repo. Was it intentionally omitted or was the design of the project changed?
There's a NovuClient.cs file however.
Cc: @unicodeveloper

Hey @J-rayX, apologies about that. I will be getting those documents updated hopefully by the end of tonight.

Alright. I'll eagerly await that. Thanks.

Released as part of 0.3.0


Why does .holdWhen(valve) swallow events from finite streams (regardless of valve)?

I don't understand why the following contrast exists:
Bacon.once(true).log("you will see me once");
// and then it will log `<end>`

versus
Bacon.once(true).holdWhen(Bacon.constant(false)).log("you won't ever see me");
// it will just log `<end>`

This odd behavior disappears when Bacon.once(true) is replaced with Bacon.interval(1000, true) (or a similar non-completing stream).
I've tried to dig in the code but I'm having a hard time understanding what's going on there.

(In your example it probably should be Bacon.constant(true))
It might be related to
Bacon.constant(true).log("t")
// t true
// t <end> // <- breaks `holdWhen` ?

Because
var b = new Bacon.Bus();
b.log();
var p = b.toProperty(true);
p.log("t")
// t true <- no <end>!
Bacon.once(1).holdWhen(p).log("you won't see me");
// nothing printed

@phadej in your example, holdWhen works correctly, because the property holds the value true. But if you
Bacon=require("../dist/Bacon.js")
var b = new Bacon.Bus()
var p = b.toProperty(false);
Bacon.once(1).holdWhen(p).log("you won't see me");
// nothing printed

you can indeed reproduce the bug.

If you replace the bus with Bacon.never() the bug disappears, and this probably has to do with the fact that the property has ended.

Seems that holdWhen is a particularly hard thing to get right :(

If you replace Bacon.once(1) with Bacon.later(0,1) it works fine. So this is one of the things that breaks because of synchronously responding streams.

Related to #367 the fix for which is on my wish-list for version 0.8.

There's not much point in using .holdWhen for a synchrnous stream like Bacon.once(), right? I don't think we'll fix this one until #367 gets fixed, if ever.


fix: change MO HONG to Wuhan as english speakers don't understand what MO HONG means

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] i18n translation has been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ..., provide screenshots if necessary)
fix

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:
change MO HONG to Wuhan as english speakers don't understand what MO HONG means

😂


Trying to run in a sidecar container fails with "Permission denied"

Description
I want to get started with dotnet monitor and since I'm using Docker Compose instead of K8s, I created the following docker-compose.yml based on the dotnet monitor K8s docs:
services:
  exampleapp:
    image: mcr.microsoft.com/dotnet/samples:aspnetapp
    user: app
    volumes:
      - diagvol:/diag
    environment:
      - DOTNET_DiagnosticPorts=/diag/dotnet-monitor.sock
  dotnet-monitor:
    image: mcr.microsoft.com/dotnet/monitor:8
    volumes:
      - diagvol:/diag
    command: ["collect", "--no-auth"]
    environment:
      - DOTNETMONITOR_DiagnosticPort__ConnectionMode=Listen
      - DOTNETMONITOR_Storage__DefaultSharedPath=/diag
      - DOTNETMONITOR_Urls=http://localhost:52323
      - DOTNETMONITOR_Metrics__Endpoints=http://+:52325

volumes:
  diagvol:

When starting the stack via docker compose up, it fails with dotnet-monitor-1  | Unhandled exception: System.Net.Sockets.SocketException (13): Permission denied.

Logs
dotnet-monitor-1  | {"Timestamp":"2024-07-21T12:25:21.1489363Z","EventId":60,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Tell us about your experience with dotnet monitor: https://aka.ms/dotnet-monitor-survey","State":{"Message":"Tell us about your experience with dotnet monitor: https://aka.ms/dotnet-monitor-survey","link":"https://aka.ms/dotnet-monitor-survey","{OriginalFormat}":"Tell us about your experience with dotnet monitor: {link}"},"Scopes":[]}
dotnet-monitor-1  | {"Timestamp":"2024-07-21T12:25:21.1678369Z","EventId":77,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Connection mode: Listen at \u0027/diag/dotnet-monitor.sock\u0027","State":{"Message":"Connection mode: Listen at \u0027/diag/dotnet-monitor.sock\u0027","path":"/diag/dotnet-monitor.sock","{OriginalFormat}":"Connection mode: Listen at \u0027{path}\u0027"},"Scopes":[]}
dotnet-monitor-1  | {"Timestamp":"2024-07-21T12:25:21.1735368Z","EventId":13,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments.","State":{"Message":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments.","{OriginalFormat}":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments."},"Scopes":[]}
dotnet-monitor-1  | {"Timestamp":"2024-07-21T12:25:21.5483490Z","EventId":14,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Now listening on: http://localhost:52323","State":{"Message":"Now listening on: http://localhost:52323","address":"http://localhost:52323","{OriginalFormat}":"Now listening on: {address}"},"Scopes":[]}
dotnet-monitor-1  | {"Timestamp":"2024-07-21T12:25:21.5487628Z","EventId":14,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Now listening on: http://[::]:52325","State":{"Message":"Now listening on: http://[::]:52325","address":"http://[::]:52325","{OriginalFormat}":"Now listening on: {address}"},"Scopes":[]}
dotnet-monitor-1  | {"Timestamp":"2024-07-21T12:25:21.6122573Z","EventId":11,"LogLevel":"Error","Category":"Microsoft.Extensions.Hosting.Internal.Host","Message":"Hosting failed to start","Exception":"System.Net.Sockets.SocketException (13): Permission denied\n   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)\n   at System.Net.Sockets.Socket.Bind(EndPoint localEP)\n   at Microsoft.Diagnostics.NETCore.Client.IpcUnixDomainSocket.Bind(IpcUnixDomainSocketEndPoint localEP)\n   at Microsoft.Diagnostics.NETCore.Client.IpcUnixDomainSocketServerTransport.CreateNewSocketServer()\n   at Microsoft.Diagnostics.NETCore.Client.IpcUnixDomainSocketServerTransport..ctor(String path, Int32 backlog, IIpcServerTransportCallbackInternal transportCallback)\n   at Microsoft.Diagnostics.NETCore.Client.IpcServerTransport.Create(String address, Int32 maxConnections, Kind kind, IIpcServerTransportCallbackInternal transportCallback)\n   at Microsoft.Diagnostics.NETCore.Client.ReversedDiagnosticsServer.Start(Int32 maxConnections)\n   at Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource.ExecuteAsync(CancellationToken stoppingToken)\n   at Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource.ExecuteAsync(CancellationToken stoppingToken)\n   at Microsoft.Extensions.Hosting.Internal.Host.\u003CStartAsync\u003Eb__15_1(IHostedService service, CancellationToken token)\n   at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable\u00601 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List\u00601 exceptions, Func\u00603 operation)","State":{"Message":"Hosting failed to start","{OriginalFormat}":"Hosting failed to start"},"Scopes":[]}
dotnet-monitor-1  | Unhandled exception: System.Net.Sockets.SocketException (13): Permission denied
dotnet-monitor-1  |    at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
dotnet-monitor-1  |    at System.Net.Sockets.Socket.Bind(EndPoint localEP)
dotnet-monitor-1  |    at Microsoft.Diagnostics.NETCore.Client.IpcUnixDomainSocket.Bind(IpcUnixDomainSocketEndPoint localEP)
dotnet-monitor-1  |    at Microsoft.Diagnostics.NETCore.Client.IpcUnixDomainSocketServerTransport.CreateNewSocketServer()
dotnet-monitor-1  |    at Microsoft.Diagnostics.NETCore.Client.IpcUnixDomainSocketServerTransport..ctor(String path, Int32 backlog, IIpcServerTransportCallbackInternal transportCallback)
dotnet-monitor-1  |    at Microsoft.Diagnostics.NETCore.Client.IpcServerTransport.Create(String address, Int32 maxConnections, Kind kind, IIpcServerTransportCallbackInternal transportCallback)
dotnet-monitor-1  |    at Microsoft.Diagnostics.NETCore.Client.ReversedDiagnosticsServer.Start(Int32 maxConnections)
dotnet-monitor-1  |    at Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource.ExecuteAsync(CancellationToken stoppingToken)
dotnet-monitor-1  |    at Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource.ExecuteAsync(CancellationToken stoppingToken)
dotnet-monitor-1  |    at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token)
dotnet-monitor-1  |    at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable`1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List`1 exceptions, Func`3 operation)
dotnet-monitor-1  |    at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
dotnet-monitor-1  |    at Microsoft.Diagnostics.Tools.Monitor.Commands.CollectCommandHandler.Invoke(CancellationToken token, String[] urls, String[] metricUrls, Boolean metrics, String diagnosticPort, Boolean noAuth, Boolean tempApiKey, Boolean noHttpEgress, FileInfo configurationFilePath, Boolean exitOnStdinDisconnect)
dotnet-monitor-1  |    at Microsoft.Diagnostics.Tools.Monitor.Commands.CollectCommandHandler.Invoke(CancellationToken token, String[] urls, String[] metricUrls, Boolean metrics, String diagnosticPort, Boolean noAuth, Boolean tempApiKey, Boolean noHttpEgress, FileInfo configurationFilePath, Boolean exitOnStdinDisconnect)
dotnet-monitor-1  |    at System.CommandLine.Invocation.InvocationPipeline.InvokeAsync(ParseResult parseResult, CancellationToken cancellationToken)
dotnet-monitor-1 exited with code 1
exampleapp-1      | The runtime has been configured to pause during startup and is awaiting a Diagnostics IPC ResumeStartup command from a Diagnostic Port.
exampleapp-1      | DOTNET_DiagnosticPorts="/diag/dotnet-monitor.sock"
exampleapp-1      | DOTNET_DefaultDiagnosticPortSuspend=0

Configuration

Is this related to a specific tool? No
What OS and version, and what distro if applicable? Win11 23H2 (OS Build 10.0.22631.3880)
What is the architecture? x64
Do you know whether it is specific to that configuration? I don't know
Are you running in any particular type of environment? Docker Desktop for Windows (i.e. WSL2 <IP_ADDRESS>)
Is it a self-contained published application? Somehow - it's a prebuilt Docker image (example app of ASP.NET Core, provided by Microsoft)
What's the output of dotnet info:

Output of `dotnet info`
.NET SDK:
 Version:           8.0.303
 Commit:            29ab8e3268
 Workload version:  8.0.300-manifests.34944930
 MSBuild version:   17.10.4+10fbfbf2e

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\8.0.303\

.NET workloads installed:
 [aspire]
   Installation Source: VS 17.10.35027.167
   Manifest Version:    8.0.0/8.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.0.0\WorkloadManifest.json
   Install Type:        FileBased

Host:
  Version:      8.0.7
  Architecture: x64
  Commit:       2aade6beb0

.NET SDKs installed:
  3.1.426 [C:\Program Files\dotnet\sdk]
  5.0.408 [C:\Program Files\dotnet\sdk]
  6.0.100 [C:\Program Files\dotnet\sdk]
  6.0.131 [C:\Program Files\dotnet\sdk]
  6.0.321 [C:\Program Files\dotnet\sdk]
  8.0.303 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.26 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.26 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

Regression?
I don't know, but I found this post in a Docker forum, so I assume that it used to work for the user.
Other information
/

@mu88 There are two requirements to establish connectivity with dotnet-monitor and the app:

The users of each container should ideally be the same
The user needs r/w permissions to the volume mount

In 8.0, we no longer run as root by default. I'm not that familiar with docker compose, but to fix your example, I was able to add user: root to both containers.
Ideally you would have the same non-privileged user running both containers, but you'll need to also grant permissions for that user to the volume.

Thx @wiktork ! Where would I have found this information in the docs?

@wiktork: with the following docker-compose.yml, I can now successfully start the stack:
services:
  exampleapp:
    image: mcr.microsoft.com/dotnet/samples:aspnetapp
    user: root
    ports:
      - "8080:8080"
    volumes:
      - diagvol:/diag
    environment:
      - DOTNET_DiagnosticPorts=/diag/dotnet-monitor.sock
  dotnet-monitor:
    image: mcr.microsoft.com/dotnet/monitor:8
    ports:
      - "52323:52323"
      - "52325:52325"
    user: root
    volumes:
      - diagvol:/diag
    command: ["collect", "--no-auth"]
    environment:
      - DOTNETMONITOR_DiagnosticPort__ConnectionMode=Listen
      - DOTNETMONITOR_Storage__DefaultSharedPath=/diag
      - DOTNETMONITOR_Urls=http://localhost:52323
      - DOTNETMONITOR_Metrics__Endpoints=http://+:52325

volumes:
  diagvol:

According to the API docs of GET /processes, I'd assume that the command curl http://localhost:52323/processes should now work, right? However, this gives me the following error:
myUser@myRaspi:~/temp $ curl http://localhost:52323/processes
curl: (56) Recv failure: Connection reset by peer

Thx @wiktork ! Where would I have found this information in the docs?

Compatibility docs describe the scenario here: https://github.com/dotnet/dotnet-monitor/blob/main/documentation/compatibility/8.0/README.md#docker-non-root-by-default
We can probably add more pointers from the rest of the docs to this existing doc to help people find the information and resolution more easily.

According to the API docs of GET /processes, I'd assume that the command curl http://localhost:52323/processes should now work, right? However, this gives me the following error:
myUser@myRaspi:~/temp $ curl http://localhost:52323/processes
curl: (56) Recv failure: Connection reset by peer

If you adjust the URL to bind to any host instead of localhost, then it works:
- DOTNETMONITOR_Urls=http://localhost:52323
+ DOTNETMONITOR_Urls=http://+:52323

The .NET Monitor image as-is binds its URLs to any host by default.

That works like a charm, thank you very much!

@jander-msft sorry for bothering you again with this issue :/
After upgrading my stack to .NET 9, the previous approach no longer works. In the logs of the dotnet monitor container, I see a bunch of "Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored." warnings.
Have there been any changes related to .NET 9 that I should be aware of? 🤔

Here you find all the logs from the `dotnet monitor` container
{"Timestamp":"2024-12-06T14:39:26.0658354Z","EventId":60,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Tell us about your experience with dotnet monitor: https://aka.ms/dotnet-monitor-survey","State":{"Message":"Tell us about your experience with dotnet monitor: https://aka.ms/dotnet-monitor-survey","link":"https://aka.ms/dotnet-monitor-survey","{OriginalFormat}":"Tell us about your experience with dotnet monitor: {link}"},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:26.1099640Z","EventId":77,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Connection mode: Listen at \u0027/diag/dotnet-monitor.sock\u0027","State":{"Message":"Connection mode: Listen at \u0027/diag/dotnet-monitor.sock\u0027","path":"/diag/dotnet-monitor.sock","{OriginalFormat}":"Connection mode: Listen at \u0027{path}\u0027"},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:26.1213346Z","EventId":13,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments.","State":{"Message":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments.","{OriginalFormat}":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments."},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:26.6978671Z","EventId":14,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Now listening on: http://[::]:52323","State":{"Message":"Now listening on: http://[::]:52323","address":"http://[::]:52323","{OriginalFormat}":"Now listening on: {address}"},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:26.6980055Z","EventId":14,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Now listening on: http://[::]:52325","State":{"Message":"Now listening on: http://[::]:52325","address":"http://[::]:52325","{OriginalFormat}":"Now listening on: {address}"},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:26.8712346Z","EventId":0,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Application started. Press Ctrl\u002BC to shut down.","State":{"Message":"Application started. Press Ctrl\u002BC to shut down.","{OriginalFormat}":"Application started. Press Ctrl\u002BC to shut down."},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:26.8752496Z","EventId":0,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Hosting environment: Production","State":{"Message":"Hosting environment: Production","EnvName":"Production","{OriginalFormat}":"Hosting environment: {EnvName}"},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:26.8755551Z","EventId":0,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Content root path: /app/","State":{"Message":"Content root path: /app/","ContentRoot":"/app/","{OriginalFormat}":"Content root path: {ContentRoot}"},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:47.9858791Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T14:39:48.0006034Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:6d2bcb3d457f4fba9480869225e82fba","TargetProcessId":"1","TargetRuntimeInstanceCookie":"6d2bcb3d457f4fba9480869225e82fba"}]}
{"Timestamp":"2024-12-06T14:39:48.0074402Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:6d2bcb3d457f4fba9480869225e82fba","TargetProcessId":"1","TargetRuntimeInstanceCookie":"6d2bcb3d457f4fba9480869225e82fba"}]}
{"Timestamp":"2024-12-06T14:40:17.1351507Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T14:40:17.1357625Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:4e5f7b8c534043e4a92408d3c824511b","TargetProcessId":"1","TargetRuntimeInstanceCookie":"4e5f7b8c534043e4a92408d3c824511b"}]}
{"Timestamp":"2024-12-06T14:40:17.1359973Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:4e5f7b8c534043e4a92408d3c824511b","TargetProcessId":"1","TargetRuntimeInstanceCookie":"4e5f7b8c534043e4a92408d3c824511b"}]}
{"Timestamp":"2024-12-06T14:40:51.2381770Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T14:40:51.2387901Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:1cc66f6b47cf49c3bc7fa319c73c7c36","TargetProcessId":"1","TargetRuntimeInstanceCookie":"1cc66f6b47cf49c3bc7fa319c73c7c36"}]}
{"Timestamp":"2024-12-06T14:40:51.2390320Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:1cc66f6b47cf49c3bc7fa319c73c7c36","TargetProcessId":"1","TargetRuntimeInstanceCookie":"1cc66f6b47cf49c3bc7fa319c73c7c36"}]}
{"Timestamp":"2024-12-06T14:45:54.5426282Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T14:45:54.5432679Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:81971a695c8a445c9ee90e15b6807f05","TargetProcessId":"1","TargetRuntimeInstanceCookie":"81971a695c8a445c9ee90e15b6807f05"}]}
{"Timestamp":"2024-12-06T14:45:54.5435840Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:81971a695c8a445c9ee90e15b6807f05","TargetProcessId":"1","TargetRuntimeInstanceCookie":"81971a695c8a445c9ee90e15b6807f05"}]}
{"Timestamp":"2024-12-06T15:05:32.3461761Z","EventId":0,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Application is shutting down...","State":{"Message":"Application is shutting down...","{OriginalFormat}":"Application is shutting down..."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:37.7939278Z","EventId":60,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Tell us about your experience with dotnet monitor: https://aka.ms/dotnet-monitor-survey","State":{"Message":"Tell us about your experience with dotnet monitor: https://aka.ms/dotnet-monitor-survey","link":"https://aka.ms/dotnet-monitor-survey","{OriginalFormat}":"Tell us about your experience with dotnet monitor: {link}"},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:37.8515656Z","EventId":77,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Connection mode: Listen at \u0027/diag/dotnet-monitor.sock\u0027","State":{"Message":"Connection mode: Listen at \u0027/diag/dotnet-monitor.sock\u0027","path":"/diag/dotnet-monitor.sock","{OriginalFormat}":"Connection mode: Listen at \u0027{path}\u0027"},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:37.8680855Z","EventId":13,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments.","State":{"Message":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments.","{OriginalFormat}":"WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:39.0373868Z","EventId":14,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Now listening on: http://[::]:52323","State":{"Message":"Now listening on: http://[::]:52323","address":"http://[::]:52323","{OriginalFormat}":"Now listening on: {address}"},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:39.0376199Z","EventId":14,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Now listening on: http://[::]:52325","State":{"Message":"Now listening on: http://[::]:52325","address":"http://[::]:52325","{OriginalFormat}":"Now listening on: {address}"},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:39.5121542Z","EventId":0,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Application started. Press Ctrl\u002BC to shut down.","State":{"Message":"Application started. Press Ctrl\u002BC to shut down.","{OriginalFormat}":"Application started. Press Ctrl\u002BC to shut down."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:39.5169853Z","EventId":0,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Hosting environment: Production","State":{"Message":"Hosting environment: Production","EnvName":"Production","{OriginalFormat}":"Hosting environment: {EnvName}"},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:39.5174841Z","EventId":0,"LogLevel":"Information","Category":"Microsoft.Hosting.Lifetime","Message":"Content root path: /app/","State":{"Message":"Content root path: /app/","ContentRoot":"/app/","{OriginalFormat}":"Content root path: {ContentRoot}"},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:44.6601112Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:44.6782440Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:bb0f9325627e49d28140c6c9e14ce5fe","TargetProcessId":"1","TargetRuntimeInstanceCookie":"bb0f9325627e49d28140c6c9e14ce5fe"}]}
{"Timestamp":"2024-12-06T15:05:44.6839056Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:bb0f9325627e49d28140c6c9e14ce5fe","TargetProcessId":"1","TargetRuntimeInstanceCookie":"bb0f9325627e49d28140c6c9e14ce5fe"}]}
{"Timestamp":"2024-12-06T15:05:57.3403342Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:05:57.3411549Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:59c7b598f8e948d9bf610f60ebdd2e61","TargetProcessId":"1","TargetRuntimeInstanceCookie":"59c7b598f8e948d9bf610f60ebdd2e61"}]}
{"Timestamp":"2024-12-06T15:05:57.3414537Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:59c7b598f8e948d9bf610f60ebdd2e61","TargetProcessId":"1","TargetRuntimeInstanceCookie":"59c7b598f8e948d9bf610f60ebdd2e61"}]}
{"Timestamp":"2024-12-06T15:06:03.6034925Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:06:03.6040053Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:81a3743a5510488880a109f0ca0a25de","TargetProcessId":"1","TargetRuntimeInstanceCookie":"81a3743a5510488880a109f0ca0a25de"}]}
{"Timestamp":"2024-12-06T15:06:03.6042236Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:81a3743a5510488880a109f0ca0a25de","TargetProcessId":"1","TargetRuntimeInstanceCookie":"81a3743a5510488880a109f0ca0a25de"}]}
{"Timestamp":"2024-12-06T15:06:44.9605871Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:06:44.9619404Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:aaf148c93e254a45b3c54b345ef1f1b1","TargetProcessId":"1","TargetRuntimeInstanceCookie":"aaf148c93e254a45b3c54b345ef1f1b1"}]}
{"Timestamp":"2024-12-06T15:06:44.9621844Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:aaf148c93e254a45b3c54b345ef1f1b1","TargetProcessId":"1","TargetRuntimeInstanceCookie":"aaf148c93e254a45b3c54b345ef1f1b1"}]}
{"Timestamp":"2024-12-06T15:06:57.8922407Z","EventId":52,"LogLevel":"Warning","Category":"Microsoft.Diagnostics.Tools.Monitor.ServerEndpointInfoSource","Message":"Unexpected timeout from process 1. Process will no longer be monitored.","State":{"Message":"Unexpected timeout from process 1. Process will no longer be monitored.","processId":"1","{OriginalFormat}":"Unexpected timeout from process {processId}. Process will no longer be monitored."},"Scopes":[]}
{"Timestamp":"2024-12-06T15:06:57.8928563Z","EventId":44,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"Stopping collection rules.","State":{"Message":"Stopping collection rules.","{OriginalFormat}":"Stopping collection rules."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:498ce5bf579f45fd93fb23cae1222473","TargetProcessId":"1","TargetRuntimeInstanceCookie":"498ce5bf579f45fd93fb23cae1222473"}]}
{"Timestamp":"2024-12-06T15:06:57.8931375Z","EventId":45,"LogLevel":"Information","Category":"Microsoft.Diagnostics.Tools.Monitor.CollectionRules.CollectionRuleService","Message":"All collection rules have stopped.","State":{"Message":"All collection rules have stopped.","{OriginalFormat}":"All collection rules have stopped."},"Scopes":[{"Message":"TargetProcessId:1 TargetRuntimeInstanceCookie:498ce5bf579f45fd93fb23cae1222473","TargetProcessId":"1","TargetRuntimeInstanceCookie":"498ce5bf579f45fd93fb23cae1222473"}]}

Here you find my `docker-compose.yml`.
services:
  thisisyourlife:
    image: mu88/thisisyourlife:4.0.0-chiseled
    container_name: thisisyourlife
    depends_on:
      - dotnet-monitor
    user: app
    environment:
      - OTEL_EXPORTER_OTLP_ENDPOINT=http://opentelemetry-collector:4317
      - DOTNET_DiagnosticPorts=/diag/dotnet-monitor.sock
    volumes:
      - ./data/:/home/app/data
      - ./dotnet-monitor/data/:/diag

  # 3 other ASP.NET Core 9 apps following the same pattern like the previous one
  # other services necessary for the observability stack (e.g. Grafana, OpenTelemetry exporter)

  dotnet-monitor:
    image: mcr.microsoft.com/dotnet/monitor:9
    container_name: monitoring-dotnet-monitor
    ports:
      - "<IP_ADDRESS>:52323:52323"
      - "<IP_ADDRESS>:52325:52325"
    user: app
    volumes:
      - ./dotnet-monitor/data/:/diag
    command: ["collect", "--no-auth"]
    environment:
      - DOTNETMONITOR_DiagnosticPort__ConnectionMode=Listen
      - DOTNETMONITOR_Storage__DefaultSharedPath=/diag
      - DOTNETMONITOR_Urls=http://+:52323
      - DOTNETMONITOR_Metrics__Endpoints=http://+:52325


import {ChatCompletionRequestMessage, Configuration, OpenAIApi} from "openai";

Hello, i've finish to configure everything but when i try to launch the bot i got this

Fixed. Please check this Migration OpenAi from v3 to v4


Hi, Are there any plans to release Elastalert plugins for kibana 7.17.4?

kibana-plugin works fine in kibana 7.17.3, but after I upgrade to 7.17.4 it doesn't display properly, is there any plan to release 7.17.4?

I have not released for version >= 7.17.2

I wonder how you used pluigin in 7.17.3. Have you built it yourself?

it doesn't display properly

Please provide more details.

Yes, I modified the kibanaVersion in 7.17.1 to 7.17.3 and it worked fine in kibana 7.17.3. After upgrading kibana to 7.17.4, just modifying kibanaVersion didn't work anymore, so I rebuild KibanaPlugin to generate elastalertKibanaPlugin-1.4.1-7.17.4.zip, but after installing it, it only shows that there is this plugin but not the specific rule.

https://github.com/Karql/elastalert-kibana-plugin/blob/1.4.1/CONTRIBUTING.md
You have done something wrong 😉
I've just released for versions:

7.17.2
7.17.3
7.17.4

https://github.com/Karql/elastalert-kibana-plugin/releases/tag/1.4.1

@Karql It works fine. Thank you very, very much!

No problem 👌


⚠ SceneTime has degraded performance

In 87a43d3, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1330 ms

Resolved: SceneTime performance has improved in 473e1be.


Issues building iOS application

Summary
I am unable to run make build-ios
Environment Information

OS Version: macOS Mojave

Steps to reproduce
Run make build-ios
Expected behavior
My Fastlane environment file is:
APP_NAME="OSMC Chat"
SYNC_IOS_PROVISIONING_PROFILES="true"
MAIN_APP_IDENTIFIER="tv.osmc.chat"
SUBMIT_ANDROID_TO_GOOGLE_PLAY="true"
SUPPLY_TRACK="beta"
BUILD_FOR_RELEASE="true"
SUBMIT_ANDROID_TO_GOOGLE_PLAY="false"
SUPPLY_PACKAGE_NAME="tv.osmc.chat"
EXTENSION_APP_IDENTIFIER="tv.osmc.chatShare"
IOS_APP_GROUP="group.tv.osmc.chat"
IOS_ICLOUD_CONTAINER="iCloud.tv.osmc.chat"
MATCH_USERNAME="myemail"
MATCH_PASSWORD="mypassword
MATCH_APP_IDENTIFIER="tv.osmc.chatShare,tv.osmc.chat"
SUBMIT_IOS_TO_TESTFLIGHT="true"
MATCH_TYPE="appstore"
IOS_BUILD_EXPORT_METHOD="appstore"

Observed behavior
When I try and build the app, I get:
[16:50:47]: ▸ === BUILD TARGET MattermostShare OF PROJECT Mattermost WITH CONFIGURATION Release ===
[16:50:47]: ▸ Check dependencies
[16:50:47]: ▸ Code Signing Error: No profiles for 'tv.osmc.chatShare' were found:  Xcode couldn't find any iOS App Development provisioning profiles matching 'tv.osmc.chatShare'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild.
[16:50:47]: ▸ Code Signing Error: Code signing is required for product type 'App Extension' in SDK 'iOS 12.1'

Possible fixes
I’m not sure why this is the case. I went in to XCode and temporarily renamed the app to tv.osmc.chatShare so that XCode would generate a profile. I see that this is now reflected under Certificates, Identifiers & Profiles on the Apple Developer page.
Many thanks
Sam

I pinged our devs on this and they said that this might help: https://docs.fastlane.tools/codesigning/troubleshooting/.

Hi @samnazarko, the other issue was closed a while ago, let me know if you are still experiencing this issue and need further help with this and we can re-connect with our devs.

Given the related issue was closed https://github.com/mattermost/mattermost-mobile/issues/2347, and there hasn't been recent activity, we'll assume that the problem is fixed or is no longer valid.
If the issue persists, reopen this issue with the relevant information and we'd be glad to help you where we can.


Migrate to C/C++ for embedded systems

Does anyone have plans to rewrite this in C++ or C for integration into embedded devices?

Why... that would be going backwards for no reason. It's written in rust that doesn't stop you from running it on any embedded device that can also run a GPU.

Does anyone have plans to rewrite this in C++ or C for integration into embedded devices?

I'd be willing to help on this.

What hardware are you talking about because MIPS32 is pretty much dead?
The RISCV64 system can work already just pick a distro that uses GLIBC instead of MUSL and call it a day. It's a tier 2 platform with essentially full support.
In any case the real gottcha is probably not even rust but ROCm...

What embedded device has a modern AMD GPU? Just curious

What hardware are you talking about because MIPS32 is pretty much dead?

@cb88,
Since when has it stopped being supported, most switches, firewalls and routers are based on this architecture. You probably have only one live platform, it's x86-64, Rust really still can't compile for MIPS32 and RISCV64, what you're offering is just not working snapshot toolchain.

@GermanAizek Again... Both MIP 32 LE and RISCV64 have supported toolchains. MIPS32 LE you have to build yourself just like any other embedded toolchain, and they provide prebuilt RISCV64 toolchains for a common toolchain version using GLIBC where ROCm will also work.... MUSL is not a common c library for this type of software. If you can't build your own embedded toolchains thats a you problem not something you should blame on others.
I guarantee you ROCm doesn't build on MUSL either in fact there are closed bug reports about it not working (closed without adding support).
And you still haven't referenced a realistic device where you would be connecting a GPU to a MIPS32 CPU... I'm certainly not aware of any.

your embedded devices have GPUs?


Fix typo in README

Since end is a reserved word, I think the documentation meant to refer to the .stop method

Thank you! I'm sure you're right.