flatpak error

First, sorry for my english :)
When i try to execute the command: /betterdiscordctl install --flatpak
I've got an error: "ERROR: Discord installation not found."
So, I added comments on the following rows:
flatpak_location=$("$flatpak_bin" info --show-location com.discordapp.Discord)
flatpak_location=${flatpak_location##*$'\n'}
discord=${flatpak_location:?}/files/extra
and add this one to set discord variable with the real folder:
discord='/var/lib/flatpak/app/com.discordapp.Discord/x86_64/stable/8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378/files/extra/'
The command "./betterdiscordctl install --flatpak" is now ok.
So, I think there is a problem with the row:  flatpak_location=$("$flatpak_bin" info --show-location com.discordapp.Discord) and the option "info" of flatpak.
Thank You

What's the output of flatpak info --show-location com.discordapp.Discord?

flatpak info --show-location com.discordapp.Discord
error: Unknown option --show-location
flatpak --version
Flatpak 0.8.9
OS: Linux Mint Debian Edition 3
uname -a
Linux pc1 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86_64 GNU/Linux

Can you update flatpak? It seems that --show-location was introduced in v1.0.0.

No i can't . Flatpak installation depends on update system of LMDE .
So it's not a problem of your script but a version problem of flatpak.
In this case, you could obtain the directory of Discord with the command:
flatpak info com.discordapp.Discord
The return of this command is:
app/com.discordapp.Discord/x86_64/stable flathub 8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378
If you replace " flathub " (wtith space befor and after) in this previous string by the last string you can build the installation directory:
discord='/var/lib/flatpak/app/com.discordapp.Discord/x86_64/stable/8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378/files/extra/'
It's just an idea :)

I can't find a way to reliably get the location since v0.8.9 doesn't show whether it was installed system-wide or per-user. Moreover, the output of flatpak info is way too inconsistent between versions:
v1.4.0
$ flatpak info com.discordapp.Discord

Discord - Chat client

          ID: com.discordapp.Discord
         Ref: app/com.discordapp.Discord/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 0.0.9
     License: LicenseRef-proprietary
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 3.0 MB
     Runtime: org.freedesktop.Platform/x86_64/18.08
         Sdk: org.freedesktop.Sdk/x86_64/18.08

      Commit: 8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378
      Parent: 0b2fdc203d5e26872dcec04ed18fa87edfc3c548ae57518a89baa2e1f39ff46d
     Subject: Use xdg-run/app/$id dir instead of custom one (f9017362)
        Date: 2019-05-29 01:22:17 +0000
$ flatpak info --show-location com.discordapp.Discord
/var/lib/flatpak/app/com.discordapp.Discord/x86_64/stable/8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378

v1.0.7
$ flatpak info com.discordapp.Discord
Ref: app/com.discordapp.Discord/x86_64/stable
ID: com.discordapp.Discord
Arch: x86_64
Branch: stable
Origin: flathub
Collection ID: org.flathub.Stable
Date: 2019-05-29 01:22:17 +0000
Subject: Use xdg-run/app/$id dir instead of custom one (f9017362)
Commit: 8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378
Parent: 0b2fdc203d5e26872dcec04ed18fa87edfc3c548ae57518a89baa2e1f39ff46d
Location: /var/lib/flatpak/app/com.discordapp.Discord/x86_64/stable/8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378
Installed size: 3.0 MB
Runtime: org.freedesktop.Platform/x86_64/18.08
Sdk: org.freedesktop.Sdk/x86_64/18.08
$ flatpak info com.discordapp.Discord | sed -n 's/Location: //p'
/var/lib/flatpak/app/com.discordapp.Discord/x86_64/stable/8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378

v0.8.9
$ flatpak info com.discordapp.Discord
app/com.discordapp.Discord/x86_64/stable flathub 8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378
$ flatpak info com.discordapp.Discord | sed 's| flathub |/|'
app/com.discordapp.Discord/x86_64/stable/8a0fc700c701feacfc3e8cc630fbcbd7ff98c13045cfdf5cbc1aea6e7b307378
$ # ^ closest I can get to the full path

What I'm gonna do instead is make it so the -d, --discord & -m, --modules options can be used with --flatpak to manually specify the location:
betterdiscordctl $bdctl_command --flatpak \
  -d /var/lib/flatpak/app/com.discordapp.Discord/current/active/files/extra \
  -m ~/.var/app/com.discordapp.Discord/config/discord/$discord_version/modules

Replace $bdctl_command with whatever command you need (e.g. install).
Replace $discord_version with the current Discord version (e.g. 0.0.9).
If Discord was installed with --user then /var/lib/ should be ~/.local/share/.

Ok, you could suggest this options when  "ERROR: Discord installation not found" message appear.
Anyway, thank you ++

@ObserverOfTime This does not work.
betterdiscordctl install --flatpak \
-d /var/lib/flatpak/app/com.discordapp.Discord/current/active/files/extra \
-m ~/.var/app/com.discordapp.Discord/config/discord/0.0.9/modules

Simply produces:
ERROR: Discord installation not found.

This is installed as system not user and in fact the "extra" folder doesn't even exist. The only folders that exist are bin, discord, lib, and share.

@ObserverOfTime Nice workaround, but do note for some reason the "extra" folder did not exist for me and I had to manually create it.

@ryaniskira What version of flatpak are you using?

@ObserverOfTime

/var/lib/flatpak/app/com.discordapp.Discord/current/active/files/discord

I actually tried that first and it didn't work, manually creating the extra folder then pointing to that did work.

It works for me.
Comments following lines (from 425 to 436):

  flatpak_version=$("$flatpak_bin" --version | sed -n 's/Flatpak //p')
  if [[ $(Semver::compare "$flatpak_version" '1.0.0') -eq -1 ]]; then
    die 'ERROR: You are using an unsupported version of Flatpak.' \
        'See https://github.com/bb010g/betterdiscordctl/issues/45'
  fi
  # flatpak sucks and doesn't use stderr for warnings.
  # https://github.com/flatpak/flatpak/blob/13e449b/app/flatpak-main.c#L259-L286
  # This really should be better for directories with newlines, but...
  # We're just going to grab the last line and hope for the best.
  flatpak_location=$("$flatpak_bin" info --show-location com.discordapp.Discord)
  flatpak_location=${flatpak_location##*$'\n'}
  discord=${flatpak_location:?}/files/extra

and add

  discord='/var/lib/flatpak/app/com.discordapp.Discord/current/active/files/discord/'

You can achieve the same thing by using -d '/var/lib/flatpak/app/com.discordapp.Discord/current/active/files/discord/'.


Error image with custom Placeholder fix

This fixes an issue where custom Placeholders are never removed when an error occurs even when there is an Error Image that should be shown instead.
Steps to reproduce:

Add custom placeholder
Add Error Image
Load image with an Error
Placeholder always shows because it is never removed

Note: Unit Test added for UIKit failed without fix and passes with fix

Any chance of this being looked at?

@PJ-LT Sorry for the late reply. It looks good to me and I was just a bit busy recently on other projects. I will merge and tag it ASAP! Thanks for the contribution!

@onevcat Awesome, thanks so much!


Set up CD with GitHub Actions

@YasunoriMATSUOKA
CD didn't triggered because branch name master is wrong.
Branch name should be main.
Fix it.


Using the directive with dynamic data

Hi,
I've been trying to use the directive with my own one which retrieves the images from my server. What's the best way to do this? The way I'm doing it displays the images but the animation isnt working.
Here's the mark up calling the directive
<slick autoplay="true" arrows="true" dots="true" class="slider" section="page"></slick>
I've then got my own directive called "slider" which gets the images from the server (using the section attribute to help identify them) and in the template url of the directive I'm doing this
`

`
I also tried putting the slick directive in my own template url - but neither work. The images display but the animation doesn't work.

I have the same problems, I use ng-repeat to dynamic render my slide's items, and then the animation doesn't work...

Hi,
I gave up in the end and used angular-flexslider instead

You don't have to.  Angular-Slick handles data perfectly well.
For my example I'm returning my $resource data to $scope.events.  So...
Just make sure you have this in your :
init-onload=true data="events"
Where "events" is your data.  If it still doesn't work let me see your code.

Hi,
Many thanks for getting back - that's great, thank you

copy that, thanks a lot.

but for data the changes multiple times this still doesn't seem to work :(

@PedroEsperanca  it should still work.. something like :
<slick init-onload=true data="main.awesomeThings" dots=true infinite=false speed=300 slides-to-show=1 touch-move=false slides-to-scroll=1 class="slider one-time">

{{item}}

</slick>


Entries on /admin/members can overflow due to multiple aliases

On the Members page, having multiple aliases can make an entry overflow.

I'd be happy to write a patch. Would you prefer truncating the alias list or expanding the entry?

Thanks for spotting this! Yes we'd prefer the latter: expanding the height of the list item. But the list item needs a minimum height (matching the same fixed height dimensions as today).


Support relative paths for PBR materials

Resolves #286.
Requires: https://github.com/osrf/sdformat/pull/349.
To test, you can modify PBR map URIs similar to the following.


Filtering the items in a list-dialog

Hi Aidan,
I have a situation where the number of elements I need to show in a list-dialog is overwhelmingly high and I'd like to provide the user with a search field so that he can filter the available choices.
From what I understand, your builder's custom-views are just for inflating xml layouts, but I can't associate code with anything, right?
I know the library (which is beyond awesome) is not designed for overly complex scenarios, so I don't expect it to be possible, but hey, maybe I'm just missing something huge here!

That's very possible, you just need to make a custom layout which includes the search field and list below it. Your custom list adapter could do filtering for you.


[New Feature] Chat Component

I'm submitting a ...  (check one with "x")

[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository

Issue description
Can we have chat component like  Fuse chat http://angular-material.fusetheme.com/apps/chat
Current behavior:
No chat functions currently
Expected behavior:
Having chat functions will make the ngx-admin more exhaustive application allowing communication.
Steps to reproduce:

Related site:
http://angular-material.fusetheme.com

Hi @nOmi7, we've released Chat UI in the Nebular. A showcase will be added in the ngx-admin soon.


[ruff] Empty branches (RUF050)

Summary
Resolves #13929 and #9472.
Test Plan
cargo nextest run and cargo insta test.

In such cases, I would move the conditions to another function to take advantage of early returns, but that's just me.

That's fair. I just think it's too opinionated for this rule. Such a branch isn't needless; it's more of a stylistic choice; you don't want any empty branches.

As for splitting, I would like to use and reserve the RUF06* block, if that's alright with you. That way, it would be easier to select all of these closely related rules using a single selector.

I don't think we want to block off an entire range for just a few rules.
Let's also hear from @AlexWaygood to ensure we're aligned to avoid changing our approach mroe than once

That's fair. I just think it's too opinionated for this rule. Such a branch isn't needless; it's more of a stylistic choice; you don't want any empty branches.

I agree. My intention when I opened the issue was just to detect what is most likely unintentional dead code (e.g., empty conditionals from other auto-fixes/formatters). I would not want deliberate style choices to get flagged, especially the empty branches with comments.

Thanks for keeping this PR up to date. I talked to @AlexWaygood, and we agree that we should split this rule into multiple smaller rules. I'll comment on the issue with a suggestion. I'm sorry to have lead you in the wrong direction :(


Added Resource

This isn't the best place to promote your content, but thanks for the suggestion. Closing this request without merging.


Adds smart key example.

Adds smart key example.
Refactors all helper example namespaces under a common package.

Codecov Report

Merging #22 (71e1b7d) into main (171a7c7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #22   +/-   ##
=========================================
  Coverage     35.59%   35.59%
  Complexity       33       33
=========================================
  Files            14       14
  Lines           809      809
  Branches         84       84
=========================================
  Hits            288      288
  Misses          495      495
  Partials         26       26

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 171a7c7...71e1b7d. Read the comment docs.


The question about the GlShaderCache

Hi, I'm impressed by your work SuMa. It's a great work of lidar mapping in large-environment. But I'm confused about the function GlShader::fromCache(ShaderType::VERTEX_SHADER, "shader/gen_vertexmap.vert"). I'm sorry I can't figure out how to find the file "gen_vertexmap.vert" in this function. I have noticed that the COMPILE_SHADER in your CMakeLists.txt and some other tricks. Could you please give me some help about how to implment this function and how it works？ I really need your help. Thank you very much

That's a good question and I'm still happy about the solution, even if it is a little bit of magic involved.
First, the cmake command COMPILE_SHADER takes the code in the text file and copies it into a class CacheInitializer (see visualization_shader.cpp or computation_shaders.cpp in the build folder). There the constructor gets an instance of the GlShaderCache and adds the corresponding shader sources from the COMPILE_SHADER macro.
Now comes the magic: the CacheInitializer is used as a static variable: static CacheInitalizer __init__; inside the same cpp file. :tada:
The static variable will be initialized as you define it using the constructor. Thus it will add the shader sources to the cache, et voila. The shaders are added without explicitly calling ever some initialization code!
You just have to now link the cpp into the binary and that's it. Real magic! :tophat: :sparkle:


Padded zero log names and tests

Presumptively extended file name padding to 12 digits whilst fixing tests to correspond to new file name format. 12 digits make comparison with Kafka max log size mute.

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


Support for IOS

Please can you tell me are you going to support IOS in the nearest time? Need it very much!)

@kl2karpenko I am not an iOS developer, so this would be hard. I am hoping that someone in the community who knows ObjectiveC helps with it. ...

I'm also not an iOS developer, so I'm useless in helping to bring iOS support. However, I would guess that being able to support iOS would greatly improve the adoption of this plugin. I personally wouldn't invest the time to use it knowing that it's only useful for Android. Very few projects target just one platform. In fact, I'd purport that the primary reason most people choose react-native is because they're targeting both iOS and Android. So, this plugin is unfortunately not very useful until it is cross platform.
I know you're waiting to see more interest before you invest the time, but I think that's a chicken/egg problem. I truly believe that making this cross platform will greatly improve interest and usage.
my 3 cents worth

@geirman I do agree that we do need an iOS version of this. I am just waiting for someone to help. In the meantime, I have started learning ObjectiveC - it may be a while before I can get to the iOS version.

Any news about the iOS support ?

+1

@mvayngrib the accepted +1 convention these days is in the form of a 👍 reaction. Would be great if you tried to do that instead going forward :)

@geirman oof, i'm getting to be an old man. Done.

I could help with the iOS version of this library but unfortunately i don't own a Mac right now :s

Did you guys see the work at https://github.com/remobile/react-native-cordova? It seems to support both Android & iOS (MIT license).

Good find @brodybits


Vite 6 PWA build doesn't seem to resolve the correct file

Describe the bug
I've tried to upgrade from v5 to v6, but for some reason, the PWA build seems to not quite do what it did before.
This is the output for v6 in the repro repository
><EMAIL_ADDRESS>build /Users/jacquesg/github/sw-repro
> tsc && vite build

vite v6.0.6 building for production...
✓ 35 modules transformed.
dist/manifest.webmanifest                          0.47 kB
dist/index.html                                    0.70 kB │ gzip:  0.38 kB
dist/assets/react-CHdo91hT.svg                     4.13 kB │ gzip:  2.05 kB
dist/assets/index-BtyAWewE.css                     1.79 kB │ gzip:  0.86 kB
dist/assets/workbox-window.prod.es5-B9K5rw8f.js    5.72 kB │ gzip:  2.35 kB
dist/assets/index-BY4XzQdA.js                    147.58 kB │ gzip: 47.88 kB
✓ built in 242ms

PWA v0.21.1
Building src/sw.ts service worker ("es" format)...
vite v6.0.6 building for production...
[plugin:vite:resolve] [plugin vite:resolve] Module "util" has been externalized for browser compatibility, imported by<EMAIL_ADDRESS>See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "fs" has been externalized for browser compatibility, imported by<EMAIL_ADDRESS>See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "crypto" has been externalized for browser compatibility, imported by<EMAIL_ADDRESS>See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "os" has been externalized for browser compatibility, imported by<EMAIL_ADDRESS>See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "events" has been externalized for browser compatibility, imported by<EMAIL_ADDRESS>See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "net" has been externalized for browser compatibility, imported by<EMAIL_ADDRESS>See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "path" has been externalized for browser compatibility, imported by<EMAIL_ADDRESS>See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
✓ 70 modules transformed.
dist/sw.mjs  41.99 kB │ gzip: 13.30 kB

For v5:
><EMAIL_ADDRESS>build /Users/jacquesg/github/sw-repro
> tsc && vite build

vite v5.4.11 building for production...
✓ 39 modules transformed.
dist/manifest.webmanifest                          0.47 kB
dist/index.html                                    0.70 kB │ gzip:  0.38 kB
dist/assets/react-CHdo91hT.svg                     4.13 kB │ gzip:  2.05 kB
dist/assets/index-BtyAWewE.css                     1.79 kB │ gzip:  0.86 kB
dist/assets/workbox-window.prod.es5-B9K5rw8f.js    5.72 kB │ gzip:  2.35 kB
dist/assets/index-B4lB10bN.js                    146.84 kB │ gzip: 47.51 kB
✓ built in 255ms

PWA v0.21.1
Building src/sw.ts service worker ("es" format)...
vite v5.4.11 building for production...
✓ 46 modules transformed.
dist/sw.mjs  10.91 kB │ gzip: 3.91 kB

From what I can tell, vite seems to be picking the node files instead for the browser files, despite the package.json for broadcast-channel having the following. The errors in the console I believe are related due to trying to use the incompatible node files instead of the browser version.
  "name": "broadcast-channel",
  "version": "7.0.0",
  "description": "A BroadcastChannel that works in New Browsers, Old Browsers, WebWorkers, NodeJs, Deno and iframes",
  "exports": {
    ".": {
      "node": {
        "types": "./types/index.d.ts",
        "import": "./dist/esnode/index.js",
        "default": "./dist/es5node/index.js"
      },
      "deno": {
        "types": "./types/index.d.ts",
        "import": "./dist/esbrowser/index.js",
        "default": "./dist/lib/index.js"
      },
      "browser": {
        "types": "./types/index.d.ts",
        "import": "./dist/esbrowser/index.js",
        "default": "./dist/lib/index.es5.js"
      },
      "default": {
        "types": "./types/index.d.ts",
        "default": "./dist/lib/index.es5.js"
      }
    },
    "./package.json": "./package.json"
  },

Reproduction
https://github.com/jacquesg/sw-repro
Steps to reproduce
pnpm i && pnpm build && pnpm preview
Open http://localhost:4173
The error console should show something like the following:

System Info
System:
    OS: macOS 15.2
    CPU: (14) arm64 Apple M3 Max
    Memory: 2.55 GB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.8.0 - ~/.nvm/versions/node/v22.8.0/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.8.2 - ~/.nvm/versions/node/v22.8.0/bin/npm
    pnpm: 9.12.2 - ~/.nvm/versions/node/v22.8.0/bin/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 131.0.6778.205
    Safari: 18.2
  npmPackages:
    @vitejs/plugin-react: ^4.2.1 => 4.3.4
    @vitejs/plugin-react-swc: ^3.7.2 => 3.7.2
    vite: ^6.0.6 => 6.0.6

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I need to add resolve.conditions when using Vite 6, in the meantime you can use this in the pwa options:
    integration: {
      configureCustomSWViteBuild: inlineConfig => {
        inlineConfig.resolve ??= {}
        inlineConfig.resolve.conditions = ['browser', 'module']
      },
    },

I need to add resolve.conditions when using Vite 6, in the meantime you can use this in the pwa options:
    integration: {
      configureCustomSWViteBuild: inlineConfig => {
        inlineConfig.resolve ??= {}
        inlineConfig.resolve.conditions = ['browser', 'module']
      },
    },

Thank you, that solved that problem for me. Didn't realise that this was needed. I have another module, pino, which also seems to be misbehaving somewhat, even with the above.
This package is slightly different, in that it has the browser key at the top-level of package.json, not inside exports:
{
  "name": "pino",
  "version": "9.6.0",
  "description": "super fast, all natural json logger",
  "main": "pino.js",
  "type": "commonjs",
  "types": "pino.d.ts",
  "browser": "./browser.js",

I'm not sure if this is a bug in the package itself, or if this should also just work?
Log:
PWA v0.21.1
Building src/service-worker.ts service worker ("es" format)...
vite v6.0.6 building for production...
[plugin:vite:resolve] [plugin vite:resolve] Module "node:os" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/pino/pino.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "node:events" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/pino/lib/proto.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "module" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/pino/lib/transport.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "node:path" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/pino/lib/transport.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "worker_threads" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/pino/lib/tools.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "fs" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/sonic-boom/index.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "path" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/sonic-boom/index.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "worker_threads" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/thread-stream/index.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
[plugin:vite:resolve] [plugin vite:resolve] Module "path" has been externalized for browser compatibility, imported by "/Users/jacquesg/dev/projects/asterias/antaeus/node_modules/thread-stream/index.js". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
✓ 395 modules transformed.
dist/service-worker.mjs  295.61 kB │ gzip: 94.41 kB │ map: 1,181.95 kB
✓ built in 965ms

try using:
    integration: {
      configureCustomSWViteBuild: inlineConfig => {
        inlineConfig.resolve ??= {}
        inlineConfig.resolve.alias = { 'pino': './node_modules/pino/browser.js' }
        inlineConfig.resolve.conditions = ['browser', 'module']
      },
    },

try using:
    integration: {
      configureCustomSWViteBuild: inlineConfig => {
        inlineConfig.resolve ??= {}
        inlineConfig.resolve.alias ??= {}
        inlineConfig.resolve.alias['pino'] = './node_modules/pino/browser.js'
        inlineConfig.resolve.conditions = ['browser', 'module']
      },
    },

Yep, I'm aware I can manually force it to use the file. Should this not work out of the box?

The custom sw build done via Vite build, maybe I need to configure a few more things when configuring the options for the build call, still not checked the required fields (for example, latest pwa plugin version not using enviroments entry at all and this may be wrong): https://github.com/vite-pwa/vite-plugin-pwa/blob/main/src/vite-build.ts


Sidebar - closes #5

Allows users to create and open directories (projects).  Currently doesn't support subdirectories.
Added the app menu for #6 but it doesn't have deleting yet.  Holding off on delete until all else is finished in the sprint since the effect of deleting wasn't specified in a task.

updated to use workspace plugin and removed whitespace


Metrics Link in common toolbar should be visible to Org Stewards and AppsMall Admins

Currently Org Stewards do not see a link to metrics

What unable to reproduce this on Latest.
Logged in as org steward
Verified in HUD, Center and WebTop the Metrics link in the Menu drop down DOES exist.
Logged in as basic user
Verified in HUD, Center and WebTop the Metrics link in the Menu drop down DOES NOT exist.


this package is dead ?

This package is dead.

What to use instead? @yuri-devi

@alimertcakar I'm using hls.js in a custom component (pretty much what this package does)

@tonyjaimep do you have an example?


Cookie manager only returns cookies that are not secure

[x] I have read the README
[x] I have already searched for the same problem
[x] I have read and done the setup for Android: IMPORTANT Note for Android and iOS and IMPORTANT Note for Android
[x] I have read and done the setup for iOS: IMPORTANT Note for Android and iOS and IMPORTANT Note for iOS
I have ran the sample app and it does not work there

Environment

Technology
Version

Flutter version
1.24.0-2.0.pre.10

Plugin version
4.0.0+4

Android version
Android SDK version 30.0.2

iOS version
-

Xcode version
Xcode 12.0

Device information: Emulator only so far
Description
Cookie manager only returns cookies that are not secure.
A little more context is that I need to download files from a site with login. I use the flutter_downloader as recommended, but since the downloader seems to run in a separate context the user is not logged in. So I'm trying to add the necessary cookies to the flutter_downloader task, but since I don't get all cookies from inappwebview it doesn't work. At least that's my theory right now.
Expected behavior:
That the cookiemanager returns all cookies
Current behavior:
Cookiemanager only returns cookies where secure = false
Steps to reproduce
              _cookieManager.setCookie(
                  url: url, name: "TEST_COOKIE_SECURE", value: "secure", isSecure: true);
              _cookieManager.setCookie(
                  url: urlInloggad
                  name: "TEST_COOKIE_NOT_SECURE",
                  value: "not secure",
                  isSecure: false);
              List<Cookie> cookies = await _cookieManager.getCookies(url: url);
              cookies.forEach((item) => print(item.name + ": " + item.value));

Output:
I/flutter ( 6607): TEST_COOKIE_NOT_SECURE: not secure

Nah, my bad. Make sure that url has "https://" to get secure cookies.


Make Docker ps more robust to problem containers

As it stands there are quite a few long standing issues with docker ps hanging.
https://github.com/docker/docker/issues/25993
https://github.com/docker/docker/issues/12606
and so on.
At the root one of the biggest issues is that if a single container is blocking, you can no longer iterate through the container list:
can reducePSContainer be made more robust so it can skip a container if it is locked for more than N seconds and prints out the name of the problem container.
This would make it significantly easier to debug this issue and isolate the underlying cause.

Ping @cpuguy83 who I believe was looking into this.

Indeed I am. Still some issues to work out but it's coming along.
https://github.com/cpuguy83/docker/compare/container_memdb

Basic idea is to strip the container object down to configuration only and move runtime state (e.g. IO streams, log driver, etc) to a separate object.
The container object will be on a transactional in-memory store where when requested the daemon gives copies of the container object rather than a pointer reference, which means there is no longer a need to lock this object. It can be used for reporting at any time without risk of blocking.
State manipulation actions (such as start/stop) will still require a lock, but not on the container object itself. This ensures the daemon can still report status, and potentially even warn the user of a problem.

awesome @cpuguy83 !

To help debug this, since we are seeing tons of lockups on 1.12.3 I am patching the docker binary with:
https://gist.github.com/SamSaffron/56a9e47f0c2d4a6e01ee981b30a3b87c
Hopefully this will help me find the culprit backtrace on the problem machines.

@SamSaffron If you can send SIGUSR1 to the daemon and post the backtraces here we can take a look.

We had a hang this morning, but I was not around to get the full stack traces... I did however get this via my logging:
WARN[63172] Holding mutex for longer than 10 secs: pid 6317
  goroutine 1647633 [running]:
github.com/docker/docker/container.(*State).Lock(0xc820060c80)
    /go/src/github.com/docker/docker/container/state.go:41 +0x8d
github.com/docker/docker/daemon.(*Daemon).StateChanged(0xc82046c000, 0xc8210ac240, 0x40, 0x1e408f0, 0xc, 0x0, 0xc8210ac2c0, 0x40, 0x0, 0x0, ...)
    /go/src/github.com/docker/docker/daemon/monitor.go:62 +0xd86
github.com/docker/docker/libcontainerd.(*container).handleEvent.func1()
    /go/src/github.com/docker/docker/libcontainerd/container_linux.go:184 +0xab
github.com/docker/docker/libcontainerd.(*queue).append.func1(0xc821f41c01, 0xc8212dcb40, 0xc82308a1b0, 0xc8219125a0)
    /go/src/github.com/docker/docker/libcontainerd/queue_linux.go:26 +0x47
created by github.com/docker/docker/libcontainerd.(*queue).append
    /go/src/github.com/docker/docker/libcontainerd/queue_linux.go:28 +0x1da

looks like the hang originated from libcontainerd, any tips here?  @cpuguy83

@SamSaffron Hard to tell without seeing what's holding the state lock.
Maybe you can have the patch dump the full stack so we can pick through it?

I am pretty sure the hang is in:
case libcontainerd.StateExitProcess:
		c.Lock()
		defer c.Unlock()
		if execConfig := c.ExecCommands.Get(e.ProcessID); execConfig != nil {
			ec := int(e.ExitCode)
			execConfig.ExitCode = &ec
			execConfig.Running = false
			execConfig.Wait()    // <<< Hangs here
			if err := execConfig.CloseStreams(); err != nil {
				logrus.Errorf("%s: %s", c.ID, err)
			}

			// remove the exec command from the container's store only and not the
			// daemon's store so that the exec command can be inspected.
			c.ExecCommands.Delete(execConfig.ID)
		} else {
			logrus.Warnf("Ignoring StateExitProcess for %v but no exec command found", e)
		}

The code is smart, it grabs the backtrace each time you take a mutex and then spits it out when it detects the mutex was not released
Also getting tons of:
WARN[13080] containerd: unable to save 212a1d3ca5cf0e751e837a028592d2068499ab02ffcb6b654d726ffa6409f942:fdcc2a7743be8a16a06b3eed5ecf93213157e979730c1d4b1c6693a185bf2324 starttime: open /proc/2020/stat: no such file or directory
INFO[13080] containerd: 212a1d3ca5cf0e751e837a028592d2068499ab02ffcb6b654d726ffa6409f942:fdcc2a7743be8a16a06b3eed5ecf93213157e979730c1d4b1c6693a185bf2324 (pid 2020) has become an orphan, killing it

This appears fixed in latest libcontainerd afaik.
My guess is that there is a race conditions where AttachStream never fires copyFunc so .Done() is not called.
I wonder if that Wait should have a timeout?

Oh you're right, that's from lock that's being held not the waiter.
ping @mlaventure
Can you have a look at this?
Looks like exec stdio streams having an issue closing in 1.12.3?

On master I don't think we are even taking the container lock here, which seems to make sense.

Yes, the container lock was removed from master recently.
There's still the case of the execConfig lock though, it can get stuck until all the exec children have released the IO streams.

@mlaventure what if execConfig.Wait() had a 10 second timeout, if it fails to get signalled just have it  CloseStreams unconditionally and rudely. It seems far less risky.

@SamSaffron that would break backward compatibility as those processes will probably just die as a result.
Maybe this wait could be moved into a go routine though, would have to look at the implications.

I just find the hangs far more severe... I am trying out:
                       done := false
			go func() {
				time.Sleep(10 * time.Second)
				if !done {
					logrus.Errorf("%s: Failed to wait for execConfig", c.ID)
					execConfig.Done()
				}
			}()

			execConfig.Wait()

			done = true

What is the worst case scenario here? The container is already restarting anyway so they might as well die

@SamSaffron that case is not only for restarting container.
If the container is restarting because its init process died, this shouldn't block as all processes in that container would have been killed

@mlaventure it looks like my patch worked for us on 1.12
Master and 1.13 no longer lock the container on StateExitProcess however I feel that my fix still should be considered for docker core.
The container that exhibited the issue has been running for the past 3 days, it experienced the issue 8 hours ago.
What somehow happened is that we docker execed something in the container and then dockerd detected that the process exited but AttachStream was somehow stuck waiting on io for exact same process that was execed.
The patch above protects against this condition.

@SamSaffron does this process create any other processes that keeps the standard IOs open?
We cannot just cancel the exec after a timeout as that may break other setups that do just what I've described above.

The container has only one process (PID 1) this process does not fork or create any other process.
We have a monitoring piece that runs this every minute (and a few other command)
docker exec container ps aux

Trouble is there is a 1.12 bug in libcontainer where it can't properly keep track of short lived execs and causes error log flooding.
I will upgrade this server to 1.13 and add logging around that area to ensure nothing gets stuck in "wait" for longer than N seconds and log if it does. I don't want to be leaking goroutines due to this edge case we have.

@SamSaffron I was referring to the exec process creating children.
Do you have daemon logs (in debug mode) showing that the exit event for short lived exec are being ignored in libcontainerd as of 1.12.3?
If that's the case, this requires fixing :)

I think we should pull in the "don't hold container lock on exec exit" fix for a hypothetical 1.12.x at the very least.

any update about this?
docker 1.12.5 has been released. was this introduced in the newest version?

@itai-codefresh there are a couple of fixes in 1.12.4 and 1.12.5.
We don't hold the container lock on exec exit.
Stdio handling is improved (which caused the deadlock while holding the container lock on exec exit)
We now use timeouts on netlink requests and boltdb queries.
So yes, definitely upgrade.

We are seeing the same lockups on docker ps because (*Daemon).containerStart() is stuck waiting for containerd to respond and holding the lock.
(*Daemon).reducePsContainer() is still trying to grab the container lock on master. @cpuguy83 any progress on your memdb patches?

@fabiokung I have not seen these particular lockups in a bit but not entirely sure what we changed to reduce them, short of upgrading. what version are you on?

Not much progress of late, sadly.
There are now a couple of places with timeouts applied that help this situation a bit, particularly timeouts on netlink requests.

@SamSaffron Glad to hear it's cleared up a bit for you.

@SamSaffron we are on v1.12.6, but the bug causing the lockup during starts in containerd hasn't been released yet (it's on the 1.13.x tree, but not in 1.13.1-rc1): docker/containerd#436
On the docker side, it seems valid to hold a lock during (*Daemon).containerStart(), so the fix is indeed to not require locking each container on (*Daemon).reducePsContainer().


Not able to see model skeleton

Hi, I have used this module for posenet, but i can get the predictions output but model is not displayed on screen, can please help me in this?

@anandeva were you able to get it working?


Set release notes for ios and android

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject
How to set release notes for ios and android
Question Description
I'm relatively new to fastlane and would like some help on how to set the release notes. I've tried everything for android and ios but just can't seem to get it to work.
For Ios this is what I have tried.
changelog_from_git_commits(commits_count: 1) deliver(       release_notes: {         'default' => lane_context[SharedValues::FL_CHANGELOG]       }      )
For Android, the docs said to use crashlytics but I can't seem to find the api_token in firebase console, also not sure about how to set the apk_path as i use bundles not apks.
Any help would really be appreciated.

You might want to check out the official docs. https://docs.fastlane.tools/getting-started/android/beta-deployment/#release-notes and https://docs.fastlane.tools/getting-started/ios/beta-deployment/#release-notes


date published inconsistent

[Enter feedback here]
The "date published" for versions 1.2.4487 and 1.2.4485 seem incorrect. The later version has an earlier date:
Updates for version 1.2.4487
Date published: July 21, 2023
Updates for version 1.2.4485
Date published: July 25, 2023

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

ID: 925b1f9c-5c6b-1c11-9678-b157400127d0
Version Independent ID: f4f6c55c-7f88-cac1-c852-1fa94589a407
Content: What's new in the Remote Desktop client for Windows - Azure Virtual Desktop
Content Source: articles/virtual-desktop/whats-new-client-windows.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@cchapin2020
Thanks for your feedback! We will investigate and update as appropriate.

Hi @cchapin2020 - there was some confusion around an Insider release getting a hotfix, then the earlier release coming as a public release on a later date.  I've changed the date back to the original of when it was released so that it's in chronological order again. The change should be visible later today.
#please-close


Automatically update CDK bootstrap if using an older version

Ross https://serverless-stack.slack.com/archives/C01HQQVC8TH/p1643017155087800

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


[SPARK-32808][SQL] Pass all test of sql/core module in Scala 2.13

What changes were proposed in this pull request?
After https://github.com/apache/spark/pull/29660 and https://github.com/apache/spark/pull/29689 there are 13 remaining  failed cases of sql core module with Scala 2.13.
The reason for the remaining failed cases is the optimization result of CostBasedJoinReorder maybe different with same input in Scala 2.12 and Scala 2.13 if there are more than one same cost candidate plans.
In this pr give a way to make the  optimization result deterministic as much as possible to pass all remaining failed cases of sql/core module in Scala 2.13, the main change of this pr as follow:

Change to use LinkedHashMap instead of Map to store foundPlans in JoinReorderDP.search method to ensure same iteration order with same insert order because iteration order of Map behave differently under Scala 2.12 and 2.13

Fixed StarJoinCostBasedReorderSuite affected by the above change

Regenerate golden files affected by the above change.

Why are the changes needed?
We need to support a Scala 2.13 build.
Does this PR introduce any user-facing change?
No
How was this patch tested?

Scala 2.12: Pass the Jenkins or GitHub Action

Scala 2.13: All tests passed.

Do the following:
dev/change-scala-version.sh 2.13
mvn clean install -DskipTests  -pl sql/core -Pscala-2.13 -am
mvn test -pl sql/core -Pscala-2.13

Before
Tests: succeeded 8485, failed 13, canceled 1, ignored 52, pending 0
*** 13 TESTS FAILED ***

After
Tests: succeeded 8498, failed 0, canceled 1, ignored 52, pending 0
All tests passed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/33132/
Test PASSed.

cc @srowen , this patch fixed remaining failed cases of sql core module with Scala 2.13 and all test passed now.

Test build #128507 has started for PR 29711 at commit 8a0bb43.

Merged build finished. Test PASSed.

Test build #128507 has finished for PR 29711 at commit 8a0bb43.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128507/
Test FAILed.

Test build #128530 has started for PR 29711 at commit 10d4953.

Test build #128530 has finished for PR 29711 at commit 10d4953.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128530/
Test PASSed.

@srowen @gatorsmile Is there any other problem in this pr that needs to be fixed? It seems that @cloud-fan  thinks the change is safe.

I'll merge this tomorrow if there are no more objections.

Merged to master

thx~ @srowen @cloud-fan @gatorsmile


Add a wiki: Etrian Odyssey Wiki

Link to origin wiki: https://etrian.fandom.com/wiki/Etrian_Odyssey_Wiki
Link to destination (independent) wiki: https://etrianodyssey.wiki/wiki/Main_Page

Thanks for the submission Gautrot. Etrian Odyssey has not been added as the Fandom wiki has 1,400+ articles, while the independent wiki has 146.


3D camera rotation is broken

🐛 Bug
It seems we introduced a bug in #5701, according to git bisect. The 3D camera rotation is "absolute" instead of relative (i.e: the point you press on the canvas determines the starting point of that rotation).
To Reproduce
import napari
import numpy as np
v = napari.Viewer(ndisplay=3)
pl = v.add_points(np.random.rand(10, 3) * 100)

Then move the camera a few times.

Well... Shit. LOL

Cool I think a quick fix would be to simply revert this change:
https://github.com/napari/napari/pull/5701/files#diff-5c61f0a4d37071dbd71d5b2933f35237bd3148b35e63d65c2828afd6580f83b2R34
-        self._3D_camera = ArcballCamera(fov=0)
+        self._3D_camera = MouseToggledArcballCamera(fov=0)

A deeper fix would be to understand why these lines would have this effect:
        def viewbox_mouse_event(self, event):
            if (
                self.mouse_zoom
                and event.type == 'mouse_wheel'
                or self.mouse_pan
                and event.type in ('mouse_move', 'mouse_press')
            ):
                super().viewbox_mouse_event(event)
            else:
                event.handled = False

found the issue!


Chat - Mention is not fully highlighted when first mention is part of second mention.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: V9. 0.73-6
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
Issue reported by: Applause Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Open a room chat
Enter #22 #2234
Send the message
Note whisper shown for both mentions
Tap yes shown in whisper message

Expected Result:
Mention must be fully highlighted.
Actual Result:
Mention is not fully highlighted when first mention is part of second mention.
Workaround:
Unknown
Platforms:

[x] Android: Standalone
[x] Android: HybridApp
[x] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/bf770b2e-e1e4-4b6d-a7af-43d4743a0bd9
View all open jobs on GitHub

This issue should be handled internally.
Check the ResolveActionableReportMentionWhisper response, since two <mention-report> tags are set to the same reportID.

Still awaiting a volunteer

Issue not reproducible during KI retests. (First week)


Tests?

Was just checking your site, impressive work but couldn't find any tests?
Am I looking in the wrong direction? :-)

We're not very good at tests. We're trying to improve, but for now, that's not in place.

It is really that simple!


Android app loads server but only displays blue screen

When server is connected, the android app only displays a blue screen with a small white box in the middle. Confirmation from other team members that this is what they see on connecting as well.
Looking at google play reviews, this seems to be an issue that others are having when attempting to use the app.
EDIT:
Additional information -
App only connects with an http:// prefix. When using the demo server, the white box eventually expands to become the login screen. Could this be a problem with https:// and loading secure content?

+1
I have the same problem;  Using 'http://my.domain'

I had this problem before, and I can confirm it is not related to http and https.  It is working with an old server I have over https.  But I migrated to a new server and it didn't work on the new server but still works with the old one.
So minuets ago I wanted to test it again. In the android app I had all three servers configured. My old and new servers plus the rocket chat demo server.
I deleted the old server record and while trying to add it again I entered the address of the new one by mistake!
It showed the little window about updating since files and it worked.
It didn't create another server record since it matched the existing one. But maybe that forced it to update our fix something. I deleted the new server record and added it again to test and it works still.

If you have downloaded your app from the Android Playstore.  This is the wrong repo to report the problem.
This repo is for a not-yet-published, you must compile your own, version of a high performance native Android app.
Please report your problem here:
https://github.com/RocketChat/Rocket.Chat.Cordova
In addition - the above problem was due to a bug introduced by a testing version end of last week. If you used the release (stable) version of the server - it should not be a problem.


Upgrade Windows 2019 image Visual Studio 16.8

Hey folks! Just wanted to give you folks a heads-up that a breaking change was introduced into .NET 5 that required mixed Framework / Core projects to use a version of MSBuild that only ships with the latest release. Since the "VS Preview" image was eliminated, there hasn't been a way to build our mixed projects in Azure DevOps for several months.
I'm raising this ticket to make sure VS2019 gets upgraded in a timely manner, so those of us that can't build with dotnet build can still enjoy the magic that is .NET 5. You're awesome, thanks so much! 👊🏻

Hello @robertmclaws,
We keep the visual studio version always up to date. However, deploying images can sometimes take a week(or two).
I will let you know right after the next image rollout.

Waiting for this eagerly, getting an error in AzureDevops pipelines that use MSbuild. Version 16.8.0 of MSBuild missing.

We are also waiting for this, we couldn't build our projects (Azure devops) that we upgraded to .Net 5 and waiting eagerly for the VS 16.8 to be available in the images.

While waiting for the image to be updated a workaround is to update Visual Studio directly within the script.
This can be done like mentioned here : https://www.cazzulino.com/vs-preview-ci.html
I added these steps to my pipeline (it add 5/10 minutes to the build but the build pass now).
- bash: dotnet tool update -g dotnet-vs
- bash: vs install preview sku:enterprise --quiet +Microsoft.VisualStudio.Component.ManagedDesktop.Core +Microsoft.NetCore.Component.DevelopmentTools
- bash: echo "##vso[task.prependpath]$(vs where preview --prop=InstallationPath)\MSBuild\Current\Bin"

No need to use the Net installer to install Net5 in this case as it is included with Visual Studio.
I tried to use the vs update command, but it was not working so I choose to install the preview version like in the blog post.

Hello everyone,
We have some delay with delivering Visual Studio 16.8. This version contains a bunch of breaking changes and could break customers who use Nuget < 5.8. See details in https://developercommunity.visualstudio.com/content/problem/1248649/error-netsdk1005-assets-file-projectassetsjson-doe.html
We are working to mitigate it and trying to reduce impact.
Thank you for your patience

How long are we talking here? Also, I'm more than happy to be called a dick, but seriously, it seems that certain factions within Microsoft were COMPLETELY OBLIVIOUS to the fact that .NET5 was under development. I mean, what's the point of having previews if certain Microsoft infrastructure teams simply have the attitude, "well gee, we'll cross that bridge when we get to it." All the work you are doing to fix this should have been done PRIOR to Tuesday.

Blocked also. An ETA would be highly appreciated. Thanks.

Hi @jackbond, we weren't oblivious but we missed one piece of the puzzle. We are obviously taking it as something to do better next time and planning the work to get it right. As for a timeline, we are targeting early next week. I'll update here if that slips.
Sorry all for the delay!

How long are we talking here? Also, I'm more than happy to be called a dick, but seriously, it seems that certain factions within Microsoft were COMPLETELY OBLIVIOUS to the fact that .NET5 was under development. I mean, what's the point of having previews if certain Microsoft infrastructure teams simply have the attitude, "well gee, we'll cross that bridge when we get to it." All the work you are doing to fix this should have been done PRIOR to Tuesday.

Anyone surprised at the amount of breaking changes, terrible documentation and general frustration that comes along with EVERY release of .NET Core to date really hasn't been paying attention.  Ever since they went 'open source'..

I found myself not wanting to wait 2 weeks for a new release, and also not wanting to wait an additional 10 minutes for already long builds. So I posted a simple solution here: https://github.com/dotnet/core/issues/5120#issuecomment-726362230
Short version: Use Chocolatey to add the latest VS Build Tools to the server, and compile using that.
To the Azure DevOps team: it would make these situations easier if the MSBuild task let you specify alternate msbuild.exe locations.
HTH!

I moved my project over to .NET5 when the first RC dropped, which was advertised as 'production ready and supported', however as my CI build requires Visual Studio my Azure pipeline has effectively been unusable for over two months now.
Looking ahead to .NET6, I think it would be highly desirable to add back support for preview builds of VS on the Windows 2019 image to eliminate this pain point of early adopters and testers of .NET previews.

To the Azure DevOps team's credit, this process is mostly automated, so they push new software up into the image as it is released.
I think the core issue here is 1) the VS / MSBuild team pushed a requirement for a new version of MSBuild that maybe didn't understand the full ramifications of that decision, b) the consolidation of images meant that there is no longer a "VS Preview" image that has the very latest preview bits, and c) the tasks available to the Pipelines don't make it easy to specify different MSBuild executables (mostly because that hasn't been necessary for a long time).
All small problems by themselves, but in the context of trying to "Go Live" with an RC, turned out preventing us from taking advantage of that.
Hopefully my code helps out for now, and then we can get a Preview image that always has the latest stuff.
Thanks!

Hi,
I am facing troubles when I am doing CI/CD with Azure DevOps with dot net 5.0. It's said to build failed. It worked for asp.net core 3.1 but It's not working in .NET 5.0.  I am using VSTS. I am trying it since the release of .NET 5.0
The error I face is
C:\Program Files\dotnet\sdk\3.1.403\Microsoft.Common.CurrentVersion.targets(1177,5): Error MSB3644: The reference assemblies for .NETFramework,Version=v5.0 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks

@saddamhossain I posted how to fix this here: https://github.com/dotnet/core/issues/5120#issuecomment-726362230

@robertmclaws Thank you so much. I found the solution.

Hello everyone!
Just an update, image with VS 16.8 is rolling out right now. Some machines are already updated.
Deployment should be finished in a few days

That's great news @maxim-lobanov ! To set expectations, is the ongoing rollout (and the "few days" duration) applicable to both Azure Devops and Github Actions?

@JamesDSch , Yes, we deploy both Azure DevOps and GitHub Actions in parallel.

@maxim-lobanov  Thanks for the update. Out of interest, does this image have 16.8 and the .NET5 SDK, or is the plan to still add the SDK later?

@p2pbsh This image contains only Visual Studio 16.8 without separate .NET 5 installation. But VS itself contains .NET 5 if you use VS to build apps.
We are going to install .NET 5 on images in a few weeks, see https://github.com/actions/virtual-environments/issues/1891#issuecomment-726802027
Until that, it could be installed in runtime via setup-dotnet task (GitHub Actions) or Use .NET Core task (Azure DevOps)

We have some delay with delivering Visual Studio 16.8. This version contains a bunch of breaking changes and could break customers who use Nuget < 5.8. See details in https://developercommunity.visualstudio.com/content/problem/1248649/error-netsdk1005-assets-file-projectassetsjson-doe.html

Just documenting that I ran into this error starting today with the VS 16.8 upgrade in Windows Server 2019 (20201116 update) #2076:

error NETSDK1005: Assets file 'D:\a[redacted][redacted]\src[redacted]\obj\project.assets.json' doesn't have a target for 'netstandard1.6'. Ensure that restore has run and that you have included 'netstandard1.6' in the TargetFrameworks for your project.
error NETSDK1005: Assets file 'D:\a[redacted][redacted]\src[redacted]\obj\project.assets.json' doesn't have a target for 'net472'. Ensure that restore has run and that you have included 'net472' in the TargetFrameworks for your project.

Fix is to use NuGet 5.8, which nuget/setup-nuget doesn't recognize as latest yet (not ReleasedAndBlessed yet at https://dist.nuget.org/tools.json):
     - uses: nuget/setup-nuget@v1
+      with:
+        nuget-version: '5.8.x'

Our builds broke today due to this, right when we had to release Hotfixes to Production!  If these were breaking, Azure DevOps should have rolled back, or at least introduced another version with the previous image.

Hi @patdaman,
based on our image testing, VS 16.8 itself doesn't contain breaking changes, but it's having issues when working with Nuget < 5.8 https://developercommunity.visualstudio.com/content/problem/1248649/error-netsdk1005-assets-file-projectassetsjson-doe.html We are working on adding backward compatibility with older Nuget versions.
Could you please check if you are using latest Nuget?
If the issue persists with latest Nuget, please, file an issue in our repo with minimal repro steps, and we will investigate it.
Unfortunately, we are not covering all possible use cases with our tests, but we are constantly working on increasing their coverage.

I think this change was rolled out yesterday to the Teams ado instance and the majority of our builds running there started failing. In addition the code signing task started failing as well. Could you roll this back? I'd be great if you could send internal announcements with the breaking changes and what actions needs to be taken by the customers.
In addition there are task that rely on older versions that customers do not own, so more thorough testing would be appreciated.
##[error]C:\Program Files\dotnet\sdk\5.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): Error NETSDK1005: Assets file 'D:\a\1\s\Source\Common\Notifications\obj\project.assets.json' doesn't have a target for 'netcoreapp3.1'. Ensure that restore has run and that you have included 'netcoreapp3.1' in the TargetFrameworks for your project.

The framework 'Microsoft.NETCore.App', version '2.1.0' was not found.
- The following frameworks were found:
3.1.10 at [C:\hostedtoolcache\windows\dotnet\shared\Microsoft.NETCore.App]
You can resolve the problem by installing the specified framework and/or SDK.
The specified framework can be found at:
- https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.1.0&arch=x64&rid=win10-x64
##[error]The process 'C:\hostedtoolcache\windows\dotnet\dotnet.exe' failed with exit code<PHONE_NUMBER>

Seen the exact same on my hosted agents this evening. I have the latest NuGet installed and was using the DotNetCoreCli Task and NO UseDotNet task.

That error is because .NET Core 2.1 is deprecated, it was removed in VS 2019 16.8.
You can however easily fix it by explicitly adding a Use .NET Core task

On the flip side, 16.8 image in combo with NuGet 5.8 and UseDotNet task got all my broken NET5 projects building again, so please don't roll back :)

The issue is more complex as it affects internal ADO tasks that are central and would block many MS orgs.
I think a more reasonable approach would be to roll back and make sure this change is communicated internally to the task owners teams with a timeframe to fix the dependencies.
I don't think its reasonable to ask customers to update 1000+ (our case) build pipelines that are affected by this change.

What I think would be a nice feature is to be able to pass in a specific image release number and the VM would spin up for that one (instead of from a hot pool of windows-latest).
Like a demand, for example:

releases/win19/20201021

Yes, you know it is going to take more time to run the build because you need to wait for VM init, but you know exactly what you are getting.
In the meantime, if you cannot add tasks to a pipeline, a faster fix may be to just switch to a self-hosted pool.

I think the thing that sticks out at me from this .NET 5 release from a DevOps perspective is that Microsoft has data on every task that is being run, and the settings for each task. Microsoft should be able to know telemetry on the makeup of the build processes of their customers, and be able to warn specific customers when upcoming VM image default changes will break builds. They should also be able to have one-click mitigation options, like for example when .NET Core 2.X becomes unsupported, clicking the "Fix Me" button should add the .NET Core 2.1 task in.
At the VERY least, there should be a build log analyzer that knows common failures in the build pipeline and recommends fixes.

@robertmclaws Spot on. Combine your comments with the knowledge that they've had MONTHS of .NET5 previews to prepare for this. This is a colossal **** up that has impacted both internal and external teams. Sorry, not sorry, but someone ought to be fired.

I totally get where you're coming from @jackbond, and in a previous life, I would wholeheartedly agree with you. However, Azure DevOps pipelines are basically just highly customizable Powershell commands, and you can actually do quite a bit yourself (including installing different Visual Studio instances).
If you look at my earlier posts in this thread, I was able to get .NET 5 & the new MSBuild installed and compiling my builds in a couple hours over a weekend, with nothing more than Googlefu + trial and error.  Yeah, breaking the builds sucks, but you need to be in a mindset that your build pipeline cannot be static, it will always be adapting.
I think the biggest issue overall is that the VS team underestimated the impact of requiring updated MSBuild versions would have on customers. That disconnect comes from Microsoft assuming that projects are homogenous (pure .NET 5 that can be built from the command line) vs realizing that different parts of an architecture can and do run different frameworks.

@robertmclaws I think my biggest frustration is that so many groups within Microsoft / Azure were completely unprepared for .NET5 For example, they hype the previews with a go-live license, and they brag about how internally they're already running on the previews. Devops pipelines should have either been ready day 1, or they should have been communicating at the top of their lungs that they wouldn't be. And now in rushing to be ready, they've broken internal builds (which is hilarious to witness in a public forum.) In the past, didn't they have different images for different versions of Visual Studio?

@LanceMcCarthy dotnet 2.1 is not deprecated, its eol date is in August 2021. Both 2.1 sdk and 2.1 runtimes are present on hosted agents. You can check that by running dotnet --list-sdks \ dotnet --list-runtimes through a script task.
@Naninani , the error message ##[error]C:\Program Files\dotnet\sdk\5.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): Error NETSDK1005: Assets file 'D:\a\1\s\Source\Common\Notifications\obj\project.assets.json' doesn't have a target for 'netcoreapp3.1'. Ensure that restore has run and that you have included 'netcoreapp3.1' in the TargetFrameworks for your project. is because of incompatibility of dotnet 5 with older nuget versions(<=5.7). So the more appropriate workaround is to upgrade nuget to 5.8 in your pipeline as suggested by @dahlbyk, rather than downgrading dotnet
Also, can you tell which task is giving this other error message The framework 'Microsoft.NETCore.App', version '2.1.0' was not found., and share the logs?

The ship has sailed, of course, but new MSBuild being incompatible with restores from older NuGet versions seems like something that could have at least been a warning in the build log. I don't suppose NuGet leaves any evidence in packages or obj/ of what version was used to restore?

@dahlbyk we have infact added warning logs to DotNetCLI task and started rolling out on Friday. Are continuing with further rollout.

Visual studio 16.8 was deployed last week.
I'm going to close the issue.
Thanks, everyone for your thougths\suggestions!


Remove the option of Edit tags insecurity group (Ingress rules/Egress rules)

ISSUE TYPE

Bug Report

COMPONENT NAME
component:UI
SUMMARY
Remove the option to Edit tags a security group (Ingress rules/Egress rules)
Steps to reproduce the issue

Create a basic zone

Network >Security Group> Select any Security  Group > Ingress rule /Egress rule

Click on Action item (edit tags)

End user will be unable to add any tag as there is no supporting api call

Screencast from 06-04-23 03:21:24 PM IST.webm
The backend api call doesn't support tags
https://cloudstack.apache.org/api/apidocs-4.18/apis/authorizeSecurityGroupEgress.html
https://cloudstack.apache.org/api/apidocs-4.18/apis/authorizeSecurityGroupIngress.html
https://cloudstack.apache.org/api/apidocs-4.18/apis/revokeSecurityGroupEgress.html
https://cloudstack.apache.org/api/apidocs-4.18/apis/revokeSecurityGroupIngress.html
EXPECTED RESULTS
No option should be provided in the UI to edit security group ingress/Egrees rules
ACTUAL RESULTS
Option is provided in the UI to edit security group ingress/Egrees rules

@kiranchavala It is supposed to use createTags API but the form doesn't seem to work properly at the moment. Will add a fix

fixed by #7424


Styles Config doesn't exist

I cannot find styles config when using Forestry.io or Netlify CMS. Is this fixable?

I am seeing this issue as well.
Screenshot: http://flywheel.link/adba82029ce5

Is there a previous version that isn't broken?

Using Forestry I can see this...

But I can't find anywhere to edit the default color palette or anywhere to create a new one within Forestry.
I did find where to edit the colors within _config.yaml which is good enough but it would be nice to be able to change these within forestry as well...

Great work on this by the way, I absolutely love it!

It’s a pity this is an issue. Is there any older releases previous to this one that might not have the same issue?


[Merged by Bors] - Add TensorFlow Lite build instruction

bors r+
Signed-off-by: Zhao Lufan<EMAIL_ADDRESS>

bors retry


TechDocs: Fix broken page title while the docs are rendering

Expected Behavior

TechDocs generates documentation metadata for an entity from its repository. So, it takes significant time to get information like site name which goes into the title of the page.
While we are fetching the site name and other metadata, we already know the component ID. So, instead of having [object Object] in the page title, we can have the component ID there instead. And then, once we have site name, we can replace the page title with that.
Current Behavior

Undefined values while the metadata loads.

I would like to work on this.

Great @vividh ! Assigned it to you

Thanks!

@OrkoHunter Made the changes in https://github.com/spotify/backstage/pull/3126. Do check it out.
The culprit LOC was the following in TechDocsPageHeader.tsx:
<Header
  title={siteName ? siteName : <CircularProgress />}
  ...
  ...

Turns out the Header component uses title prop for the page title as well. But it also allows overriding it, so the following prop fixes it:
pageTitleOverride={siteName || name}


Update libpopcnt to v2.6

fixed

After some team discussion, we've come to the conclusion that we don't really think we can accept this PR right now. There's some pending internal work that we need to do to get all our OSS dependencies moved over to vcpkg (ala #15855). We can update OSS dependencies, but there's quite a lot of extra (internal) process at this time, that it doesn't make sense to continually ingest small version bumps that don't have any product-critical fixes in them. Considering the only change here is "Fix building on NetBSD" (https://github.com/kimwalisch/libpopcnt/releases/tag/v2.6), that's not really relevant to our product code 🤷

Ok


how to config google app. i try to authen via google but it not working

Hey I won't help you with the issue, but it seems that you just gave out your secret key


Feat: Automatically Discover StyleX Aliases from Configuration Files

[Feature] Automatically Discover StyleX Aliases from Configuration Files
Linked Issues
Fixes #765

Overview
This PR enhances the StyleX Babel plugin to automatically discover alias configurations from Node.js native imports (package.json), tsconfig.json, and deno.json. It ensures normalized paths for cross-platform compatibility and maintains backward compatibility with existing manual configurations.

Implementation Details

JSON5 Parser: Handles configuration files with comments or trailing commas.
Alias Discovery:

Parses package.json for Node.js native subpath imports (aliases with # prefix).
Parses tsconfig.json for compilerOptions.paths and resolves paths relative to baseUrl.
Parses deno.json for the imports field.

Merge Configurations:

Combines configurations from all sources:
Manual > package.json > tsconfig.json > deno.json.

Code Reuse:

Replaced redundant findProjectRoot with getPackageNameAndPath for project root discovery.

Normalized Paths:

Standardizes path separators for cross-platform compatibility.

Error Handling:

Gracefully handles missing or malformed configuration files.

Test Coverage
The following scenarios are tested:
1. Alias Discovery:

Node.js native imports from package.json (subpath imports).
Aliases from tsconfig.json paths.
Aliases from deno.json imports.

2. Configuration Merging:

Merges aliases from all sources with correct priority.

3. Manual Overrides:

Ensures manual alias configurations take precedence over discovered aliases.

4. Error Handling:

Handles missing or invalid configuration files gracefully.

Code Changes
1. state-manager.js (Alias Discovery)

Updated Functionality:

loadAliases:

Now supports Node.js native imports and deno.json.
Removed custom stylex.aliases support.
Simplified project root discovery using getPackageNameAndPath.

Added support for deno.json imports.

2. stylex-transform-alias-config-test.js

Updated Unit Tests:

Tests for Node.js native imports discovery.
Tests for deno.json imports.
Tests for merged configuration from all sources.
Tests for proper handling of invalid configurations.

Potential Future Improvements

Enhanced Test Cases:

Complex alias patterns with wildcards.
Nested directory structures.
Edge cases in path resolution.

Additional Features:

Support for other configuration sources like Webpack config.
More granular control over alias resolution priorities.

Performance Optimizations:

Caching of discovered configurations.
Smarter file system traversal.

Pre-flight Checklist

[x] I have read the Contribution Guidelines.
[x] Performed a self-review of my code.
[x] Added tests for the new functionality.
[x] Verified cross-platform compatibility.
[x] Ensured backward compatibility with existing configurations.

Feedback
Feedback is welcome, particularly for:

Additional test cases to consider.
Improvements to performance or alias resolution edge cases.

Hey @nmn, this is my initial implementation for the issue. Let me know if there are any additional test cases or improvements you'd like me to include. I’m happy to iterate further based on your feedback

Parses package.json for stylex.aliases.

We don't want to add a new stylex.aliases option to the package.json. Instead, please look for the native aliases configuration supported by Node.js:

https://nodejs.org/api/packages.html#imports
https://nodejs.org/api/packages.html#subpath-imports
https://betterprogramming.pub/the-native-way-to-configure-path-aliases-in-frontend-projects-5db70f19a6e0#02ec

Hey @nmn fixed all the changes you requested, i just couldnt pass the size test but apart from that i think its all ready, also updated the PR description and the unit tests, let me know if more changes are needed :)


Allow customizations on the scorecard config checks

What should be done here?

Allow us to pass a config option to the scorecard checks. See: https://github.com/operator-framework/enhancements/blob/master/enhancements/audit-command.md#scorecard-config-manifests-and-options
Improve the current behaviour to run the scorecard tests by looking in the annotations path. See that audit currently only checks in the default path and if the tests are not there will write then.

It shows outdated/done


Node cleanup

Just stumbled upon some code-issues in the node_version and nvm segments.

Nice catch, @dritter!


Update README.md

change sort order of "AWS Examples" section: move deployments that include all DSF components to appear first.

I think it's better to put the PS/Customer examples before the POC/Lab ones because they are the main use case. So the overall order I'm suggesting is: DSF Single Account, DSF, Sonar Single Account, Sonar Multi Account, Sonar Basic, Sonar HADR, Sonar Upgrade. Please remove the Alpha from Sonar Upgrade while you're at it, it's there by mistake. Please also change the order in step 9 of "Installer Machine Deployment Mode".

Please don't include the tree/raw change in this PR, I'm not sure it's valid. If necessary Gabi will create his PR again after your change. You can drop him a note if you want.

Thanks a lot for replacing the sonar_basic_deployment with dsf_single_account_deployment, I thought it was too much so I didn't. However, it is better to put dsf_deployment because dsf_single_account_deployment requires additional steps - the user needs to provide the network infrastructure as input variables. Thank you you for your patience.


Cleanup

Some cleanup. 40fe604 fixes a problem with fish. b59e83c annoyed me for a while :) As for 7173e0d, I came across a tab in a file and just had to replace them all.
Note: This concerns many different things, tell me if you'd prefer to have different PR.

Wow! Thanks!


The time_key setting is not honoured when using data streams

(check apply)

[X] read the contribution guideline
[ ] (optional) already reported 3rd party upstream repository or mailing list if you use k8s addon or helm charts.

Steps to replicate
Specify an option time_key (https://github.com/fluent/fluent-plugin-opensearch#time_key) to get the time from some other parameter but the time is not picked up from that parameter. See https://github.com/fluent/fluent-plugin-opensearch/blob/v1.0.2/lib/fluent/plugin/out_opensearch_data_stream.rb#L196 for details.
Expected Behavior or What you need to ask
The time_key setting should be honoured in opensearch_data_stream similar to opensearch https://github.com/fluent/fluent-plugin-opensearch/blob/v1.0.2/lib/fluent/plugin/out_opensearch.rb#L943-L947.
Using Fluentd and OpenSearch plugin versions
OS version Any
Bare Metal or within Docker or Kubernetes or others? NA
Fluentd v0.12 or v0.14/v1.0
fluentd --version
fluentd 1.12.3
ES plugin 3.x.y/2.x.y or 1.x.y
fluent-plugin-opensearch 1.0.2

OpenSearch Data Streams plugin is still experimental. Would you please send a patch for fixing this?

Thanks @cosmo0920 . When can we expect this fix to be available in release tag?

I'd pushed the v1.0.3 release on rubygems today.


Update pytest_subunit.py

The tests that are skipped do not get updated when used in session scope. Could this be merged please

thx


Upgrade to Rails 5

Hey @fxn!
This is kickoff for Rails 5 upgrade. Everything what I did is based on official guides - http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-4-2-to-rails-5-0.
If you have any ideas which we should implement during this upgrade or any comments related to my code then let me know.
Have a great day!
Daniel

ACK! I have a busy week, but I'll try to look at it soon.

No problem, same here 😄 . Thank you in advance!

Awesome job!

I worked a little bit more on your patch (see later commits in https://github.com/fxn/rails-contributors/commits/master), and this is now deployed to production. Thanks again! ❤

Thank you for your help! Also sorry for missing configs/initializers and for that belongs_to association. I completely overlooked that. 😕


Difference in EMA values between pandas-ta and tradingview

Which version are you running? The lastest version is on Github. Pip is for major releases.
0.3.14b0
Do you have TA Lib also installed in your environment?
Yes
Have you tried the development version? Did it resolve the issue?
No
Describe the bug
I am trying to calculate 200 days ema but the ema from ta is way off.
To Reproduce
import yfinance as yf
import pandas_ta as ta

x = yf.download('ABB.NS', start = "2021-12-08", progress = False)['Close']

ema= ta.ema(x, 200)[-1]

Expected behavior
expected 200 days ema = 2720.93
Additional context
20 days and 50 days ema are matching with TradingView but not 100 and 200 days.
I tried to use help(ta.ema) but not sure which number to use for the offset argument

Hello @thecpshah,
First, offset only shifts the result.
Second, it is not really good to compare a TV datasource (apples) with Yahoo Finance (oranges). Sure, it's possible they maybe equal at times but not a guarantee.
Third since you have TA Lib installed, ta.ema() uses TA Lib for it's calculation which isn't exactly the same at TV. If you want to disable TA Lib for ema, do: ta.ema(x, 200, talib=False) or possibly ta.ema(x, 200, sma=False, talib=False).
Lastly, I recommend updating to the development branch.
Hope this helps!
Kind Regards,
KJ

Thanks for reply. Disabling TA lib, gives me same result as Pandas' EWM.

Also, the difference occurs for longer MAs. The numbers are very close for 20 or 50 days exponential MAs.

Hello @twopirllc
I think it's time to create new release, it's about more than 1 year since the last release on 2021.

Hello @thecpshah,
First, offset only shifts the result.
Second, it is not really good to compare a TV datasource (apples) with Yahoo Finance (oranges). Sure, it's possible they maybe equal at times but not a guarantee.
Third since you have TA Lib installed, ta.ema() uses TA Lib for it's calculation which isn't exactly the same at TV. If you want to disable TA Lib for ema, do: ta.ema(x, 200, talib=False) or possibly ta.ema(x, 200, sma=False, talib=False).
Lastly, I recommend updating to the development branch.
Hope this helps!
Kind Regards, KJ

Hi @baotang2118

Thank for you reply, I think it's time to create new release, it's about more than 1 year since the last release on 2021. Many bugs had been fixed, many documents had been updated.

No worries. Apologies for the slow response.
I have been intending to finish the remaining TA Lib ht_ indicators before making a new release. Unfortunately since the last release, my time has been more sparse than I expected. 😑
Considering my current availability, I will clear up outstanding PRs and abandon the plan to add the ht_ indicators for the next release. 😞
KJ

Hi @twopirllc, just to know do you have an estimated date for the next release? can i still use the current library then will only have to replace by the new one once released?
Thanks,

@jjvvhh2,

do you have an estimated date for the next release?

At my current rate, I estimate a couple of months at best. 🤷🏼♂ Sadly my free time has been limited. 😑

can i still use the current library then will only have to replace by the new one once released?

You can use either, however I recommend the new one when it's updated. It fixes many bugs, improved speed & documentation. You can read more here.


Update version to 1.0.74-3 on staging

Update version to 1.0.74-3

🚀 Cherry-picked to staging in version: 1.0.74-3🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Build phase - Build input files cannot be found

Hi,
I added the SPM, added the executable and the ui...
I assumed I didn't have to install (Aka using mint) as I used the SPM ?
Added the build phase and I'm getting this error...
error: Build input files cannot be found: '/Users/jm/Library/Developer/Xcode/DerivedData/Build/Products/Debug-iphoneos/ArgumentParser.o', '/Users/jm/Library/Developer/Xcode/DerivedData/Build/Products/Debug-iphoneos/ArgumentParserToolInfo.o' (in target 'swift-package-list' from project 'SwiftPackageList')
Any ideas ?
Thanks,
Jules.

Hi Jules,
You have to install it on your machine, either manually or via Mint as described here. The package is only for reading the generated file conveniently!
Let me know if something is still unclear!

Ah ok...
I needed to added export PATH="$PATH:$HOME/.mint/bin/" as mentioned in the other issue.
So the build phase now runs... but I don't seem to be getting any output.
I do have spms with licenses...
Any ideas ?
Jules.

Cool, did you add the file to your project/target as described in step 6 and 7?

No I mean it didn't create a file.

Oh hang on, I had the first checkout checked....
Now I have the original error 🙁

🤦♂

Oh hang on, I had the first checkout checked....
Now I have the original error 🙁

Hmm, what happens if you execute the command manually in your Terminal? I should generate it on your desktop.

🤦♂

This looks fine 🤔

Yeah, it's in the path, so why doesn't it work when ran from the sh script Xcode creates.
If I remove the if statement and just run the two lines, it fails with the same error.

it runs fine from my home folder too... hmmm

Xcode provides it's own environment and the PATH variable where the mint bin folder is added is not the one from your system...
Both methods described in #27 should work, what happens when you try the second method where you create an alias to mint's swift-package-list with ln -s $HOME/.mint/bin/swift-package-list /usr/local/bin/swift-package-list?

Awesome, working :)

Awesome!!


Automata Theory, Language and Computation by Hopcroft Motwani Ullman

What does this PR do?
Added Automata Theory, Language and Computation 3rd Edition by Hopcroft Motwani Ullman
For resources
Description
This classic book on formal languages, automata theory and computational complexity has been updated to present theoretical concepts in a concise and straightforward manner with the increase of hands-on, practical applications. This new edition comes with Gradiance, an online assessment tool developed for computer science.
Why is this valuable (or not)?
With its innovative underlying technology, Gradiance turns basic homework assignments and programming labs into an interactive learning experience for students. By using a series of "root questions" and hints, it not only tests a student's capability, but actually simulates a one-on-one teacher-student tutorial that allows for the student to more easily learn the material. Through the programming labs, instructors are capable of testing, tracking and honing their students' skills, both in terms of syntax and semantics, with an unprecedented level of assessment never before offered.
How do we know it's really free?
It is available free of cost on the link attached and have verified it.
For book lists, is it a book? For course lists, is it a course? etc.
Book.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Reverted the accidental changes to archived format in data mining book

This appears not to be an authorized distribution. Please see docs/CONTRIBUTING.md guidelines.


[website] Update Benny's profile on about us page

[x] I have followed (at least) the PR section of the contributing guide.

Preview: https://deploy-preview-28816--material-ui.netlify.app/about

Regarding the background color @danilo-leal what was the conclusion? I feel that it's a pain to have to keep each avatar of the team members in a specific sequence: blue dark, blue light, green. Maybe we should uniformize on one, or else?

@hbjORbj Congrats Benny! Nice photo there :)

Regarding the background color @danilo-leal what was the conclusion? I feel that it's a pain to have to keep each avatar of the team members in a specific sequence: blue dark, blue light, green. Maybe we should uniformize on one, or else?

@oliviertassinari Agree, yeah. I haven't really thought about the photos bgs, I just left them the way they were. I pretty much prefer a standard color for it instead of a random sequence. We can tackle it in another PR but thanks for bringing this one out!


The plugin does not work?

I'm using the lastest version of both obsidian and plugin
I opened a note (just 1 note) -> scroll and click at a line -> i close the note -> open it again, but the cursor still on top.
Anything i missed? Can someone help?

+1
opened a note A -> switch to reading mode -> switch to other notes -> switch to editing mode  ->  switch back to note A
Note A is in editing mode.

I am also encountering this issue on Obsidian v0.15.9 -- reproduced using the same steps as dwSun listed.

Hello! Note that the plugin doesn't work if you're using the legacy editor (which was the default until very recently), and that the upcoming 0.16, which adds a tabbed interface, effectively renders this plugin obsolete.

Recent versions of Obsidian now default to using the new editor (the Legacy Editor option is turned off by default). AFAICT this plugin still works OK with tabbed interface, too. You can open a new issue if necessary.


How To : Organizing javascript in a asp.net core modularized application (modules in dlls)

My Application is organized in a way that some features are working as a plugin. Each plugin has it's own APIs, Views, Static files etc.. I am using ViewLocationExpander to find the view files owned by plugins which is not in the standard location but in the plugins relative path. Example;
[Starting MVC Application]
|__MainLayOut
|__Modules
    |__Plugin1
        |_Binaries
        |_Views (has shared, _viewimports etc.. local to this module)
        |_wwwroot (has static files local to this module)
    |
    |__Plugin2
        |_Binaries
        |_Views (has shared, _viewimports etc.. local to this module)
        |_wwwroot (has static files local to this module)

As you see in above structure if you delete the a plugin from the Modules folder entire plugin related features will get deactivated. So code for that plugin is 100% within the plugin directory.
Now I am planning to use RequireJS and try to modularize javascripts that is needed by each plugin. However the doucment says:
The requirejs entrypoint for each page will be loaded from ~/Scripts/Controllers/{area}/{controller}/{action}

But in my case RequireJS should be able to load the JS file not from the primary ~/Scripts folder but the /wwwroot/js folder which is inside the Plugin folder (\Modules\Plugin1\wwwroot\js). If I can get this done (May be like ViewLocationExpander), I can have a 100% modularized app.
Is this possible?

I think the section titled "OVERRIDING ENTRYPOINT RESOLUTION" here: http://requirejsnet.veritech.io/setup.html may be of help.  Essentially you can implement your own logic for locating an Entrypoint script

I forgot to mention that I am on .Net 5 and this is not yet ported to support it officially right? However I found : https://github.com/davidsk/RequireJSDotNet/blob/RequireJsDotNet_Core1.0/MVC6/Startup.cs which seems to use the resolver you mention above. Is this what you were talking about? Do you have a plan to officially support .Net 5?

I'm not a maintainer on the RequirejsDotNet project, I've just contributed some updates to the code.  I did work on changes to support .net core but, as you can see from the branch, I haven't looked at it in a while and asp.net core has evolved quite a bit since then.  I'm not sure how much of that code is compatible with asp.net 5.
I expect the way this should be done in asp.net 5 (and how RequireJsDotNet would do it if upgraded) would be to add a middleware component to the request pipeline which could inspect the route and inject the correct script on the page.

From: mkgn @.>
Sent: 06 April 2021 11:49
To: vtfuture/RequireJSDotNet @.>
Cc: Keith Davidson @.>; Comment @.>
Subject: Re: [vtfuture/RequireJSDotNet] How To : Organizing javascript in a asp.net core modularized application (modules in dlls) (#106)
I forgot to mention that I am on .Net 5 and this is not yet ported to support it officially right? However I found : https://github.com/davidsk/RequireJSDotNet/blob/RequireJsDotNet_Core1.0/MVC6/Startup.cshttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdavidsk%2FRequireJSDotNet%2Fblob%2FRequireJsDotNet_Core1.0%2FMVC6%2FStartup.cs&data=04|01||ba4cb60aced44018bf0008d8f8e9a4a0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637533029654993014|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=KwRKe6vRTE6BVSZ0OXclDbPBs3DB5qey4CF1qoNs0bA%3D&reserved=0 which seems to use the resolver you mention above. Is this what you were talking about? Do you have a plan to officially support .Net 5?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvtfuture%2FRequireJSDotNet%2Fissues%2F106%23issuecomment-814023033&data=04|01||ba4cb60aced44018bf0008d8f8e9a4a0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637533029655002975|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=SPZef23zdX9Z7YKv8hwUtSEnnre%2BEjCdiQ7EsQjAL70%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAHN72YTJFW5NNPANYEDQQDTHLRLJANCNFSM42OIJ5WA&data=04|01||ba4cb60aced44018bf0008d8f8e9a4a0|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637533029655002975|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ofeTi2eUhYbAnPN%2BSRQlH2Ab55Bw1qliyZHIiHtGtto%3D&reserved=0.


Add setting to automatically close Working Tree tabs when window is closed or when commit has been made

Although I use git command line for most things, I use the IDE when making commits, and I find that whenever I make a commit, close a project and reopen it at a later point, there are still a whole bunch of Working Tree tabs from before that I do not need to see anymore. I often have a tab for the file itself anyway, so when I reopen the IDE, I basically have two tabs for each file, one of them is the file itself and the other is the diff tab.
It would be nice if there was some sort of config option available to automatically close all these types of tabs whenever a commit has been made and/or when the window is closed. Would keep the IDE a bit tidier for me.
edit: openDiffOnClick does not work for me because I still like to see these diffs.

Related/duplicate:

https://github.com/microsoft/vscode/issues/18651
https://github.com/microsoft/vscode/issues/135276

There are already 47 upvotes on one of the old threads for this - are those counted when deciding if something gets moved to the backlog or do people need to vote on this specific issue?

Yes, this is something that I will be looking at this milestone.

Today's Insiders release (2022-02-10) contains a new setting (git.closeDiffOnOperation) that is meant to address the need to manually close the diff editors after certain git operations. If the setting is enabled, diff editors will automatically be closed when changes are committed, discarded, staged, unstaged. Try out the new setting and let me know your feedback.

I just gave it a go and it seems to work well so far. Initially it felt a bit eager, I thought it would close on commit, not when the file is staged. But I'll try to use it for some "real" work and see how it behaves.
I do still think a manual "Close all tabs with (Working Tree) in the name" action in the command palette would be useful.
Thanks for the updates!

Today's Insiders release (2022-02-16) contains a new command Git: Close All Diff Editors to manually close the diff editors independent of the git.closeDiffOnOperation setting. Please give it a try and let me know if you experience any issues with the command.


throw Error when npm install

拉取项目，执行npm install 到一半，突然报错说无系统权限？？

Try to reopen the cmd window in administrator mode.

Not a Davinci problem. Check your system user permissions.


Capitalize the recommended string for MetaDeploy UI

Capitalize the recommended string for MetaDeploy UI to look nicer in the UI.
Discussed this with @jlantz yesterday. From the code search, it is used only in one file for which I believe it is ok to capitalize. But please check and let me know if we're good to go ahead with this change.
Current screenshot where it is not capital

@shibinkunnath This looks good; thanks for the PR. The builds which are required to merge only run for PRs created from a branch within the SFDO-Tooling organization, so I'll submit a new PR with the same changes.

@davisagli Ok sure, thanks