[changelog] reference closed issues

Is your feature request related to a problem? Please describe.
I am evaluating jreleaser as a replacement for semantic-release for changelog generation. jreleaser doesn't mention the closed issues that are referenced in a conventional commit.
for example, the following commit message:
feat: add FileHeader.getFileName

which returns the Unicode filename if it exists, and the ASCII filename otherwise
the existing methods FileHeader.getFileNameString and FileHeader.getFileNameW are deprecated

closes #34, closes #53

produced the following release note: https://github.com/junrar/junrar/releases/tag/v7.2.0
Describe the solution you'd like
It would be nice if jreleaser could parse the references to issues within commit messages, and add them to the changelog.
In a conventional commit, an issue could be referenced in the footer, like shown above, or directly in the body, for example:
feat: a new feature

this continues the work done in #3 and lays the foundation for #5

Describe alternatives you've considered
other tools like semantic-release can do this

Good suggestion. As I understand it GitHub has a predefined set of keywords that may be used to interact with issues. I suppose GitLab and Gitea can do the same but it's likely the set of keywords is not identical, thus some Git service specific customization may be needed.
How would you like to see the rendered changelog? Given the sample commit message (title & body) you posted there will be 1 row marked as feature but then how should #3 and #5 be laid out? Also, titles and messages for both of these issues would have to be retrieved from the remote server (something JReleaser does not do, yet), with perhaps further processing as there may be other referenced issues.

Note that semantic-release doesn't parse the keywords specific to each git service.
For example, a commit with the message:
feat(rest api): ability to re-analyze a book
working towards https://github.com/gotson/komga/issues/51

would render in the changelog as :
* **rest api:** ability to re-analyze a book ([8e81356](https://github.com/gotson/komga/commit/8e81356908e42d1b7b8edb935a1eaf133cff7035)), closes [#51](https://github.com/gotson/komga/issues/51)

I don't think that's a big drawback, and probably saves a lot of hassle by not having to implement different set of keywords for each git service.

Given the sample commit message (title & body) you posted there will be 1 row marked as feature but then how should #3 and #5 be laid out? Also, titles and messages for both of these issues would have to be retrieved from the remote server (something JReleaser does not do, yet), with perhaps further processing as there may be other referenced issues.

I think something simple, without needing to retrieve the detail of the issue would work well. Just adding , closes #x with a reference to that issue would be sufficient i guess.
If a commit closes more than 1 issue (like this), the changelog can just mention each issue after , closes:
add FileHeader.getFileName ([b6da583](https://github.com/junrar/junrar/commit/b6da583ffbb861219fe20877fb78bf5092996914)), closes https://github.com/junrar/junrar/issues/34 https://github.com/junrar/junrar/issues/53

I also have an edge case where the commit mentions an issue from another repo. It could happen when you have multiple repos in an organization, or in this case where the project is forked and the original repo has been archived.
This commit has the message:
fix: inaccurate file times
thanks @tmyroadctfig

from https://github.com/edmund-wagner/junrar/pull/20

and is rendered as:
* inaccurate file times ([b1f9638](https://github.com/junrar/junrar/commit/b1f96385ff1738c1488b26968f71413f2a5085d4)), closes https://github.com/edmund-wagner/junrar/issues/20

Of course this works as referenced issues are found in the title, or if the body is rendered per commit. Does not work if only the title is rendered and the references are found in the body, which I think is the use case you're after, isn't it?

Yes indeed. The link references is secondary.

Released in v1.4.0 -> https://github.com/jreleaser/jreleaser/releases/tag/v1.4.0


Fix #947 and some other NSProgress incongruities.

NSProgress should fire KVO in a lot more cases than it did. Now it does!

This change is

Is there test collateral associated with this change?

:shipit:

:shipit:

This is currently tested by one of our middleware components, but I can add some tests here.
My concern is that we are growing a significant number of ad-hoc KVO tests, each with a custom implementation, and they need to be unified via a common listener to avoid duplicating the same code over and over in different test facades.

In reply to: 250597295 [](ancestors = 250597295)

This should be part of NSProgress tests.  Part of our long term plan to improve test code coverage is to not check-in code without tests.  I am not worried about duplicating test code.

In reply to: 250880931 [](ancestors = 250880931,250597295)

+100 here.

In reply to: 250881581 [](ancestors = 250881581,250880931,250597295)

:clock1:

@rajsesh-msft  @bbowman test collateral added! finally ;P

        child->_parentPendingUnitCount = inUnitCount;

does child not need to fire KVO for these?

Refers to: Frameworks/Foundation/NSProgress.mm:194 in b2ed69d. [](commit_id = b2ed69da0fd228666504865e533cc40588e0eddd, deletion_comment = False)

:shipit:

:shipit:


Particle DUST create a (Client ?) Heavy latence FIXED

What is the current behavior?
https://cdn.discordapp.com/attachments/483713379857596416/820632476937748480/Bug_Redstone_Particle.mp4
What is the expected behavior?
https://cdn.discordapp.com/attachments/483713379857596416/820633654995714088/Bug_Redstone_Particle_Flame_Compressed.mp4
What steps will reproduce the problem?
Get here a demo: https://github.com/MrBretze/ParticleBugMinestom
What operating system and java version is being used?
Windows 10/Ubuntu 20.04
Windows: https://adoptopenjdk.net/?variant=openjdk11&jvmVariant=hotspot
Linux: https://adoptopenjdk.net/?variant=openjdk11&jvmVariant=openj9
Additional information / Possible thoughts on why this bug is happening
I dont no

FIX: Change this line https://github.com/Minestom/Minestom/blob/master/src/main/java/net/minestom/server/network/netty/NettyServer.java#L207
set this to 0 for unlimited or increase the default value
(MinecraftServer.getNettyServer().getGlobalTrafficHandler().setWriteChannelLimit(0);)


Switch to single threaded tokio runtime

This saves more than 50% RSS memory on runtime.
Before:
> cat /proc/(pidof conmon-server)/status | rg RSS
VmRSS:      3264 kB

After:
> cat /proc/(pidof conmon-server)/status | rg RSS
VmRSS:      1460 kB

Way better than: https://github.com/containers/conmon-rs/pull/8

Eventually, I think we will want some pieces of conmon multithreaded--each container in the pod should not wait on the others for processing container stdout/catching exits. Though, we can build on top of the single tokio's if tokio's is so heavy

@haircommander this change allows for a single threaded event loop, but it should allow for the usual async processing of container events.

ah I see, thanks!

LGTM


don't make inline suggestions

I don't think the code will be acceptable as it is , so instead of showing inline suggestions because the variable name are always different that I want from , captain stack should just show them like copilot does after ctrl + enter.
Or maybe provide a option to do that.
The idea is that we don't exactly copy the code from the stack overflow, we often do tweaks to it and most of the time we go to stack overflow is to get a idea on how a problem can be done, so it might be more suitable if we show all answer with the explanation in the side window and the suitable can be accepted from the window and it will then also don't need us to install the insider version of vs code and then we can also just make thr captain stack available in the visual studio code market place.

You are right, copilot does show all found solutions in a separate window. Though copilot also shows inline suggestions as the default behaviour.
This is not really beneficial as you can click through the results anyways, if someone else finds this important to their workflow and give a proper example and reasoning this might be considered.


cfgplugins optical changes + Cisco deviations

Changes and brief description for the following files:

zr_cd_test: use cfgplugins code + enable operational-mode flag
zr_input_output_test: enable operational-mode flag
zr_inventory_test: deviation for the leaf mfg-date
associated deviation and proto files for 3
zr_temperature_test: use parent interface instead of subcomponents for the temperature sensor telemetry
zr_supply_voltage_test: cosmetic change
cfgplugins/interface.go: use InterfaceConfig and helpers OpticalChannelComponentFromPort, isSubCompOfHardwarePort.

TODO: Once above is conditionally approved, will change the rest of transceiver tests to use the updated cfgplugins InterfaceConfig()

Pull Request Functional Test Report for #3438 / 7927ae97214b70dd9e1c0a95e5b70cc5cebd88ce
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Cisco 8000E

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Cisco XRd

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Juniper ncPTX

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Nokia SR Linux

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Openconfig Lemming

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Cisco 8808

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Juniper PTX10008

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Nokia 7250 IXR-10e

TRANSCEIVER-12: Telemetry: 400ZR Transceiver Supply Voltage streaming.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-4: Telemetry: 400ZR RX input and TX output power telemetry values streaming.TRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Help

I see your note about once getting conditional approval you plan to change more files. Please do not do this.
It really helps to keep changes as small as possible for quick reviews. In the future if you can break the PRs up into small pieces that will be very helpful.

@ejbrever @dplore I agree about keeping the PR small for ease of review. I assumed that all files must be migrated in this PR to not break regression runs, since we are changing the common utility function.
Will split this PR by reducing the changed files. Thanks!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.314%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
1983

Relevant Lines:
3585

💛  - Coveralls


Cache reset doesn't refresh custom emotes from server

Summary
after you clear cache.. it doesn't refresh the custom emotes list.... : is only showing the default emotes
Environment Information

Device Name: iPhone 7 Plus
OS Version: iOS
Mattermost App Version: 1.1.0 - 47
Mattermost Server Version: 4.0.2

Steps to reproduce
log into server
post a chat with a custom emote
reset the cache

notice the custom emote is not rendering
notice the custom emotes are missing from the emote list

Expected behavior
custom emotes working as expected
Observed behavior
custom emotes are forgotten about. simply rendering text

Awesome find, we need to fix this.
Thanks

Closed via #854


Adding PortMapping support to Azure cni.

Azure CNI doesn’t program any port mappings. Its not supported in Azure CNI.
Earlier it worked because the port mapping was programmed through NAT network which was added by accident.
WINCNI does support it and here is the code that does it...

@erfrimod Thanks for contributing! Will there be anything else except for PortMappings in RuntimeConfig?

@saiyan86 I just updated with further changes so that the RuntimeConfig portmappings are converted into Endpoing policy objects and sent to HNS.

@saiyan86 Yes, look at https://github.com/kubernetes/kubernetes/blob/e45d74d00defc9fc35ecd47b0d36310c3b905d15/pkg/kubelet/dockershim/network/cni/cni.go#L336

@saiyan86  Looks like Azure CNI for Linux doesn't handle PortMappings support, and we are just returning nil. Can you take care of implementing this for Linux, when required.
@feiskyer This is the place we would impement DNS Capabilities that you are exposing in Kubelet

/lgtm

@saiyan86 Looks like Azure CNI for Linux doesn't handle PortMappings support, and we are just returning nil. Can you take care of implementing this for Linux, when required.

@madhanrm portmap plugin handles this for linux. please take a look at conflist file. Let me know if I misunderstood your comment.

/lgtm

@erfrimod Could you please resolve the conflicts so we can merge this PR? Thanks!


Fixed 5459 - Purge yum cache before deleting repo config

Description
This fixes #5459: Purge the yum cache and metadata before deleting the yum repository config.
Issues Resolved
Fixes #5459. See also https://github.com/chef-cookbooks/yum/pull/166.
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[X] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

@chef/client-enterprise-linux


vuetifyImportPlugin ignores excluded components/directives from vuetifyModule option

Similar to https://github.com/userquin/vuetify-nuxt-module/issues/226, but with further investigation
Version
vuetify: 3.6.11
nuxt-vuetify-module: 0.14.1
nuxt: 3.12.3
Intro
We have VuetifyOptions with directives and components fields
 { /**
   * @default false
   */
  directives?: Directives,

  /**
   * @default false
   */
  components?: Components
}

However, selected options does't make an effect on vite-plugin, as it still autoimports the components and directives
The reason is https://github.com/userquin/vuetify-nuxt-module/blob/be68923fa4a46c45bf2ade1f0070319b84ceb608/src/utils/configure-vite.ts#L68 is always an empty object
Case
Part of page:

Default output:

When I pass { autoImport: { ignore: ['Tooltip'] } as argument (+ extra log for options):

I expect that options provided in directives and components will effect on autoImports list

I'll keep current behavior, the linked PR no makes sense, check https://github.com/userquin/vuetify-nuxt-module/pull/239#issuecomment-2223534574

I'm going to update the docs... auto import is better than changing the configuration or deal with errors.

I still doubt, because if I register directive via nuxtApp.vueApp.directive() with VTooltipName it will be overrided. Probably we  can address the issue to the vuetify vite plugin itself, but as a compromise i would suggest adding another option inside moduleConfig to fine-tune the vite plugin

Why? If you use some directive/component, the plugin will auto import them for you, that's the expected behavior.
Why do you need to register the directive if the plugin will do it for you? We're using Vite (Rollup), no dead code and no code duplication.

I don't want to use the tooltip provided by vuetify, but want to have own directive with the same name (v-tooltip is very common). The only way for now is to write custom autoimport rule to resolve cutom directive before it's done by vuetify

@AndreyYolkin that's another problem, cannot use x-tooltip for example

I'll try to add ignore directives option, the option will be provided directly to the vuetify plugin


boards: arm: qemu_cortex_m3: Refactor to use mps2_an385.

Previously qemu_cortex_m3 was emulating ti_lm3s as the underlying
soc. This emulated SOC inside the qemu doesn't have the MPU
enabled. Hence we are moving to a newer SOC which is the mps2_an385.
This patch will move the qemu_cortex_m3 from ti_lm3s to mps2_an385.
This patch will also enable the userspace.
Pending on #7035 , #7398 and qemu V2.12
Signed-off-by: Adithya Baglody<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #7399   +/-   ##
=======================================
  Coverage   55.26%   55.26%
=======================================
  Files         467      467
  Lines       51641    51641
  Branches     9886     9886
=======================================
  Hits        28541    28541
  Misses      19190    19190
  Partials     3910     3910

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 5dc2ab4...10bf0c6. Read the comment docs.

Closing this out, we shouldn't modify qemu_cortex_m3 this way, we should just say that the MPS2_AN385 port supports qemu.

@galak I need more explanation than that.
The whole point of this PR is make the old flawed qemu_cortex_m3 to take up a newer more robust version of cortex_m3. Which means that we can enable the MPU after this PR is merged. The lm_3s emulation is flawed and what is the reason to continue using it? I don't see the need to close this PR since I am actively trying to get this to work.
The issue is #4015

The whole point of this PR is make the old flawed qemu_cortex_m3 to take up a newer more robust version of cortex_m3. Which means that we can enable the MPU after this PR is merged. The lm_3s emulation is flawed and what is the reason to continue using it? I don't see the need to close this PR since I am actively trying to get this to work.

I understand the point of the PR, my point is there is no reason to rename the qemu_cortex_m3 board to accomplish supporting a better board/SoC port w/regards to QEMU.  We should just use support the mps2_an385 without renaming things.  In truth we should rename qemu_cortex_m3 to something like lm3s6965evb.

I suggest to do the following:

Leave qemu_cortex_m3 as is initially
make mps2_an385 work as a qemu board, this can be done easily with a few defines
once we have mps2_an385 working for our needs, i.e. MPU support, drop existing qemu_cortex_m3 board and create an alias qemu_cortex_m3 in mps2_an385, i.e. make it run as qemu_cortex_m3

Lets not try and change qemu_cortex_m3 and create a duplicate of mps2_an385, we should maintain only one instance, for backward compatibility, we can alias the board only.

for running arm in qemu, we will use MPS2_AN385, no need to maintain two boards doing the same thing.


Add main Connector facade

This PR adds a new Connector class that acts as a facade for all underlying connectors, which are now marked as "advanced usage", but continue to work unchanged.
The Connector class now makes it trivially easy to create plaintext TCP/IP, secure TLS and Unix domain socket connection streams like this:
$connector = new Connector($loop);

$connector->connect('tls://google.com:443')->then(function (ConnectionInterface $conn) {
    $conn->write('…');
});

Resolves / closes #38

Thanks for the suggestion, updated and squashed to use improved error message :shipit:


⚠ Bofrost.be has degraded performance

In 7deb3f7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1311 ms

Resolved: Bofrost.be performance has improved in 0fed6cd.


Update packages + fix db diagram

I'm not sure if you're looking to update the db diagram in general, if so, should the participant table also include reported_sex, reported_gender, karyotype and meta?

I wasn't intending to yet, it would be good to but I'm just hoping to silence some of the warnings I get from GH.


Trouble building on macOS (my workarounds and suggestions)

This library looks awesome but I had trouble building fstalign on macOS sonoma (the issues likely apply to M1 machines running ventura as well). I will outline the steps I followed to build this library, the issues encountered along the way, and temporary workarounds I developed.

git clone https://github.com/revdotcom/fstalign
mkdir build && cd build
cmake .. -DOPENFST_ROOT="/opt/homebrew/Cellar/openfst/1.8.2" -DDYNAMIC_OPENFST=ON
Issue 1: The following ICU libraries were not found: uc (required)
Reason: The path to icu4c in CMakeList.txt is not for a brew installation:
list(APPEND CMAKE_PREFIX_PATH "/usr/local/opt/icu4c") # for Mac users
Workaround: Run export CMAKE_PREFIX_PATH="/opt/homebrew/opt/icu4c" and export CPATH="/opt/homebrew/opt/icu4c/include" before cmake
make
Issue 2: OpenFST dependency fails to build due to usage of C++17 features
Reason: Like many other macOS users, I manage my dependencies through brew. Unfortunately, brew usually provides only the latest version of a package and the latest OpenFST version is 1.8.2, which uses C++17 features. This library uses C++14 and does not build with C++17. I can't find a straight-forward way to update the CMakeLists.txt to specify a separate C++ version for OpenFST only.
Workaround: Download a old version of brew's openfst formula, uninstall OpenFST 1.8.2 and install the older 1.7.9 version which doesn't require C++17. This requires tweaking the old 1.7.9 ruby formula so it took me a while to figure out. See appendix for detailed steps.
Issue 3: With issue 2 fixed, there's still a remaining issue with the Catch2 dependency.
Reason: Older versions of Catch2 uses some x86 assembly code internally that is not compatabile with ARM. Newer versions updated to support both architectures but the version of Catch2 referenced in this library is too old and does not support ARM.
Workaround: Remove the existing Catch2 submodule and download a newer version. I chose v2.13.8 because it supports ARM and shouldn't cause compatability issues with this library:
cd third-party
rm -rf Catch2
git clone --branch v2.13.8 https://github.com/catchorg/Catch2
Rerun make and it should build successfully now.

After all workarounds are applied, this library finally builds on macOS! To save future users the same trouble as I went through, I have a few suggestions:

Add the brew path to OpenFST in CMakeList.txt
Either update this library to support C++17 or update the CMakeList.txt to support C++17 for OpenFST 1.8.2
Accept libfst.dylib in place of libfst.so on macOS. (Not sure if this is still an issue on OpenFST 1.8.2)
Update Catch2 to at least v2.13.8

Appendix
Workaround to install an older version of OpenFST
Create a file named openfst.rb in the current working directory. Below is the openfst.rb script I adapted from the original formula for 1.7.9. The bottle section has to be updated to use the new syntax.
class Openfst < Formula
  desc "Library for weighted finite-state transducers"
  homepage "http://www.openfst.org/twiki/bin/view/FST/WebHome"
  url "http://openfst.org/twiki/pub/FST/FstDownload/openfst-1.7.9.tar.gz"
  sha256 "9319aeb31d1e2950ae25449884e255cc2bc9dfaf987f601590763e61a10fbdde"
  license "Apache-2.0"

  livecheck do
    url "http://www.openfst.org/twiki/bin/view/FST/FstDownload"
    regex(/href=.*?openfst[._-]v?(\d+(?:\.\d+)+)\.t/i)
  end

  bottle do
    rebuild 1
    sha256 cellar: :any, big_sur: "a0289323819255885b7d45a89e2ebd88512f8153c1c956017258a61b07c29506"
    sha256 cellar: :any, catalina: "b32fb6cb0eb43a7d8775d8bfc760c49471586eeb33797f3d44a8b53cd45dc792"
    sha256 cellar: :any, mojave: "7e5a450f383ddfeddcb7ee8d240e7db576fcc32a25c199d6a35eba40fea920d9"
    sha256 cellar: :any, high_sierra: "0635e790f390be0a97c78a434e723280339fe0f0d86ee55c4a34339840f160a7"
  end

  def install
    system "./configure", "--disable-dependency-tracking",
                          "--disable-silent-rules",
                          "--prefix=#{prefix}"
    system "make"
    system "make", "install"
  end

  test do
    (testpath/"text.fst").write <<~EOS
      0 1 a x .5
      0 1 b y 1.5
      1 2 c z 2.5
      2 3.5
    EOS

    (testpath/"isyms.txt").write <<~EOS
      <eps> 0
      a 1
      b 2
      c 3
    EOS

    (testpath/"osyms.txt").write <<~EOS
      <eps> 0
      x 1
      y 2
      z 3
    EOS

    system bin/"fstcompile", "--isymbols=isyms.txt", "--osymbols=osyms.txt", "text.fst", "binary.fst"
    assert_predicate testpath/"binary.fst", :exist?
  end
end

To uninstall 1.8.2, do:
brew remove openfst

To install the older 1.7.9 from the formula above, do:
brew install openfst.rb

Ignore the Error: Failed to load cask: openfst.rb message.
Brew will create a libfst.dylib file but this library requires a libfst.so file. You need to create a symbolic link named libfst.so to the dylib file for the compiler to find the binary.
ln -s /opt/homebrew/Cellar/openfst/1.7.9/lib/libfst.dylib /opt/homebrew/Cellar/openfst/1.7.9/lib/libfst.so

After the older version is installed, clean the CMakeCache.txt and rerun cmake using the older version:
rm CMakeCache.txt
cmake .. -DOPENFST_ROOT="/opt/homebrew/Cellar/openfst/1.7.9" -DDYNAMIC_OPENFST=ON

Reference: https://nelson.cloud/how-to-install-older-versions-of-homebrew-packages/

@AlienKevin Thank you so much for this thorough exploration and write up! We will start looking into your suggestions. I know that C++17 is top of mind for us and you've already given us a great blueprint for debugging going forward!

Thanks for sharing the steps, I have tried the method to build fstalign on my macOS ventura(M2Max), the cmakelist definately is outdated for adding a wrong cmake prefix path for mac users. I can confirm that installing openfst 1.7.9 solved my problem and I succesfully built the fstalign. The other method of changing Catch2 to newer version doesn't work for me, the openfst1.8.2 got lots of error related to std:: namespace problem, which I believe is still an issue of C++ version.
So, if anyone using macOS is trying to build fstalign for now, I'd recommend you follow @AlienKevin 's step and choose the method of installing the older version of openfst.

@Rehanchy did you update the bottle section for ventura? If yes what values did you use, I can't seem to find it.

I confirm these steps worked for me on my most recent laptop (Apple M3 with OS X 14.5)! Nice!


have problem "Could not find io.github.controlwear:virtualjoystick:1.10.1."

I tried to find solution in google. How to solve? Thank you
Edit: I found Solution just add repo in build.gradle
Executing tasks: [:app:assembleDebug] in project /Users/poj/AndroidStudioProjects/MyApplication

> Task :app:preBuild UP-TO-DATE
> Task :app:preDebugBuild UP-TO-DATE
> Task :app:mergeDebugNativeDebugMetadata NO-SOURCE
> Task :app:compileDebugAidl NO-SOURCE
> Task :app:compileDebugRenderscript NO-SOURCE
> Task :app:generateDebugBuildConfig UP-TO-DATE
> Task :app:checkDebugAarMetadata FAILED
> Task :app:generateDebugResValues UP-TO-DATE
> Task :app:generateDebugResources UP-TO-DATE
> Task :app:mergeDebugResources FAILED
> Task :app:packageDebugResources UP-TO-DATE
> Task :app:parseDebugLocalResources UP-TO-DATE
> Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
> Task :app:extractDeepLinksDebug UP-TO-DATE
> Task :app:processDebugMainManifest FAILED
> Task :app:javaPreCompileDebug UP-TO-DATE
> Task :app:mergeDebugShaders UP-TO-DATE
> Task :app:compileDebugShaders NO-SOURCE
> Task :app:generateDebugAssets UP-TO-DATE
> Task :app:mergeDebugAssets FAILED
> Task :app:processDebugJavaRes NO-SOURCE
> Task :app:checkDebugDuplicateClasses FAILED
> Task :app:desugarDebugFileDependencies FAILED
> Task :app:mergeDebugJniLibFolders UP-TO-DATE
> Task :app:mergeDebugNativeLibs FAILED
> Task :app:validateSigningDebug UP-TO-DATE
> Task :app:writeDebugAppMetadata UP-TO-DATE
> Task :app:writeDebugSigningConfigVersions

FAILURE: Build completed with 7 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find io.github.controlwear:virtualjoystick:1.10.1.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
       - https://repo.maven.apache.org/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mergeDebugResources'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find io.github.controlwear:virtualjoystick:1.10.1.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
       - https://repo.maven.apache.org/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

3: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:processDebugMainManifest'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find io.github.controlwear:virtualjoystick:1.10.1.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
       - https://repo.maven.apache.org/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

4: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mergeDebugAssets'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find io.github.controlwear:virtualjoystick:1.10.1.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
       - https://repo.maven.apache.org/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

5: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:checkDebugDuplicateClasses'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find io.github.controlwear:virtualjoystick:1.10.1.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
       - https://repo.maven.apache.org/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

6: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:desugarDebugFileDependencies'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find io.github.controlwear:virtualjoystick:1.10.1.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
       - https://repo.maven.apache.org/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

7: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mergeDebugNativeLibs'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find io.github.controlwear:virtualjoystick:1.10.1.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
       - https://repo.maven.apache.org/maven2/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 2s
19 actionable tasks: 8 executed, 11 up-to-date

yeah quite the same nooby android developer problem here :)
just a pain in the ass to try to integrate into my own project ^^
i guess 'io.github.controlwear' path must be specified in some magic way :)
but how? :)

I found Solution just add repo in build.gradle

please elaborate to avoid confusion... 'i found the solution' is a pretty bad statement :-/
on my side adding the dependency was no help..

Add this to settings.gradle file:

pluginManagement {
repositories {
gradlePluginPortal()
google()
mavenCentral()
}
}
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
google()
mavenCentral()
maven { url 'https://jitpack.io' }
}
}

After that, Sync your Project with Gradle File:

Could not GET 'https://jitpack.io/io/github/controlwear/virtualjoystick/1.10.1/virtualjoystick-1.10.1.pom'. Received status code 401 from server: Unauthorized

@ozzyyzzo4096
instead of implementation 'io.github.controlwear:virtualjoystick:1.10.1'
you can use implementation 'com.github.controlwear:virtual-joystick-android:master-SNAPSHOT'

I was able to import a version of it by using two of the above steps.
Add the Jitpack url to settings.gradle:
dependencyResolutionManagement {
  repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
      google()
      mavenCentral()
      maven { url 'https://jitpack.io/' } // Add this line
    }
}

And then change the implementation dependency to use the snapshot in your app's build.gradle file:
implementation 'com.github.controlwear:virtual-joystick-android:master-SNAPSHOT'


Add hello-world app for test purposes, based on the echo-poc

This is identical to https://github.com/SalesforceCommerceCloud/pwa-kit/pull/82/, which was already approved. I am working around our branch protections which were added since I started work. The original PR has two unsigned commits, which I can't fix because we have protected the branch from force-pushes!

@kevinxh I forgot to say, I have a fix for the .gitignore issue you found incoming on a second PR (both app templates are affected, not just the hello-world one).


In game custom video playback reading issues

Hopefully i can explain as much as i can in this post.
The game is The Sims 2, disk version.
The GPU is Nvidia 1070 GTX TI

Overall the game runs with no problem with d9VK, however the issue begins when you use in game TV. Just to be brief if you haven't played sims 2 before, there is a custom option to add your own videos to play on the TV. The only format the game reads for custom videos is AVI. The directory would be like this C:\Documents\EA Games\The Sims 2\Movies\Broadcast\TvSBN.

From what i've gathered, the videos built into the game run on a unique codec created by Electronic arts. These run properly with no interference from d9vk.

Here is a typical custom video format.

In the past, these videos used to work on my older Gpu which was a 1gb 6800 ATI radeon HD.
For about a week i had been experimenting with the codecs, and i can confirm this is not a codec issue. Simply put, d9VK which doesn't fully acknowledge AVI videos.

This is what the videos look like with d9vk installed. Although there's a black screen, i could still hear the video. So the video was playing but only from an audio perspective.

These pics were taken without d9vk, as you can see the custom Avi videos work.

Here is the d3d9 report.
Sims2EP9_d3d9.log

I'll need an apitrace to debug this -- preferably one recorded where it works, and one where it doesn't (ie. w and w/o d9vk)
A copy of a working video would also be nice.
@tannisroot can probably help you or provide these.

When you say without d9vk do you mean native D3D or WineD3D?

Please try with this build. It probably won't render the videos correctly but it should hopefully render something (albeit very green)
d3d9.zip

I'll need an apitrace to debug this -- preferably one recorded where it works, and one where it doesn't (ie. w and w/o d9vk)
A copy of a working video would also be nice.
@tannisroot can probably help you or provide these.

Just out of curiosity would that be the dxvk-cache? Either way, i'll speak with Tannis have those sent to you shortly.

When you say without d9vk do you mean native D3D or WineD3D?

Wine3D code name - Loli-Hop.

Please try with this build. It probably won't render the videos correctly but it should hopefully render something (albeit very green)
Please provide a picture if anything changes.
d3d9.zip

Thank you i will report back shortly.

Just out of curiosity would that be the dxvk-cache

no

Wine3D code name - Loli-Hop.

I think you're getting confused with the different things here.

I managed to trace it. There may be lots of pink flashing but I'm able to get a trace of the "gameplay" where the video from the reporter is being played.
https://drive.google.com/open?id=1RrDlbMVaGssmQHzYaWoHhTGE34MB9vhG


Phone Input Extension

Expected Behavior
You can configure the input to accept extensions.
Actual Behavior
It does not allow the extension to be entered in any format.

Hello, can you please give a documentation about what phone extensions are? Do you if this is supported by awesome-phonenumber?
Thanks.

After looking for other issues about extension in other projects (vue-tel-input, react-phone-number-input, awesome-phonenumber), it looks like extensions are complicated to handle, so I won't add this feature sorry.
Maybe the best solution for you is to add another dedicated input for extensions next to the phone input.


Web Build Error 'TypeError: Cannot read properties of undefined (reading: 'init'), null, null)

Hey everyone, I am loving this unofficially official flutter SDK for Datadog. The Android and iOS builds work very smoothly, but I am having an issue with the web build/deployment that I was wondering if someone can help me with/identity the issue.
When running the Chrome development server, I am getting this data in the Chrome console:
VM473:1 This app is linked to the debug service: ws://<IP_ADDRESS>:55452/nO3G8J4sP-4=/ws
errors.dart:251 Uncaught (in promise) Error: PlatformException(error, TypeError: Cannot read properties of undefined (reading 'init'), null, null)
    at Object.throw_ [as throw] (errors.dart:251:49)
    at StandardMethodCodec.decodeEnvelope (message_codecs.dart:607:7)
    at MethodChannel._invokeMethod (platform_channel.dart:177:18)
    at _invokeMethod.next (<anonymous>)
    at async_patch.dart:45:50
    at _RootZone.runUnary (zone.dart:1685:54)
    at _FutureListener.thenAwait.handleValue (future_impl.dart:159:18)
    at handleValueCallback (future_impl.dart:766:44)
    at Function._propagateToListeners (future_impl.dart:795:13)
    at _Future.new.[_completeWithValue] (future_impl.dart:601:5)
    at async._AsyncCallbackEntry.new.callback (future_impl.dart:639:7)
    at Object._microtaskLoop (schedule_microtask.dart:40:11)
    at _startMicrotaskLoop (schedule_microtask.dart:49:5)
    at async_patch.dart:166:15```

There are no failing network requests, meaning all files are being fetched - seems to be limited to compilation error.

Now, when trying to run a production build and generate a `main.dart.js` bundle, I get a slightly more helpful error:
```(index):91 Failed to load app from service worker. Falling back to plain <script> tag.
(anonymous) @ (index):91
main.dart.js:3296 Uncaught PlatformException(error, ReferenceError: DD_LOGS is not defined, null, null)
    at Object.c (https://cedarai.github.io/flutter-mobile/main.dart.js:3296:3)
    at ab6.DB (https://cedarai.github.io/flutter-mobile/main.dart.js:60273:14)
    at https://cedarai.github.io/flutter-mobile/main.dart.js:60346:98
    at anJ.a (https://cedarai.github.io/flutter-mobile/main.dart.js:4486:62)
    at anJ.$2 (https://cedarai.github.io/flutter-mobile/main.dart.js:33181:14)
    at amK.$1 (https://cedarai.github.io/flutter-mobile/main.dart.js:33175:21)
    at SW.kA (https://cedarai.github.io/flutter-mobile/main.dart.js:34133:32)
    at age.$0 (https://cedarai.github.io/flutter-mobile/main.dart.js:33546:11)
    at Object.uq (https://cedarai.github.io/flutter-mobile/main.dart.js:4576:40)
    at a5.ql (https://cedarai.github.io/flutter-mobile/main.dart.js:33478:3)```

Any idea what might be going on? I've tried digging into the main.dart.js, but the minified code isn't giving me much. I can post it later if you can't think of anything.

My Flutter dependencies:
  flutter:
    sdk: flutter
  google_fonts: 2.1.1
  provider: ^6.0.0
  intl: ^0.17.0
  smooth_page_indicator: ^1.0.0+2
  amazon_cognito_identity_dart_2: ^1.0.5
  flutter_dotenv: ^5.0.2
  jiffy: ^5.0.0
  modal_bottom_sheet: ^2.0.0
  collection: ^1.15.0
  byte_flow: ^1.0.0
  hive: ^2.0.6
  hive_flutter: ^1.1.0
  scrollable_positioned_list: ^0.2.3
  scroll_to_index: ^2.1.1
  sticky_headers: ^0.2.0
  datadog_flutter: ^1.5.2
  connectivity_plus: ^2.2.1
  flutter_easyloading: ^3.0.3
  flutter_datetime_picker: ^1.5.1

dev_dependencies:
  dart_code_metrics: ^4.11.0
  flutter_launcher_icons: "^0.9.2"
  flutter_test:
    sdk: flutter```

And a clean bill of health from flutter doctor
[✓] Flutter (Channel stable, 2.10.3, on macOS 12.2.1 21D62 darwin-arm, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] VS Code (version 1.65.0)
[✓] Connected device (1 available)
[✓] HTTP Host Availability

• No issues found!```

When I comment out all import statements and Datadog initialization, everything works just fine. Again, iOS and Android work well.

I am silly - this information resolved my issue. Mostly. Found another bug, going to post now. https://github.com/GetDutchie/datadog_flutter/blob/main/example/web/index.html


Add option to write amount of models in the beginning of the unit

Now:
Crisis battlesuits: Crisis Shas'vre (...), ...
Proposed:
(4) Crisis battlesuits: Crisis Shas'vre(...), ...

Closed by #44


Add support for different color schemes

It's useful to outsource the color assignments also for the legend plot.

@jaeilepp did you check if my substitution of len(x) for len(idx) is okay? I wasn't exactly sure if that was identical.

Yes. It's all good. Thanks.


Country selecting bottom sheet is overlapping with the status bar.

Same here, I guess it has to be wrapped inside a SafeArea Widget.

Resolved. Check #400


Recently Added Methods also required in NugetPackage.

The new methods used to get all anime list collections look really attractive would love to use them.
Hoping to see new methods in a nugetpkg update.
Kindly, let me know when you will update it.

Thank you for using my library!
I have been working on some of my other projects, so I haven't been able to update this project yet. I will push a new update once I finish with some of the todo items. You can expect this update within a few weeks, so let's be patient.

Note: You can get notified of any updates by watching this repository! 😊

It's really been a pleasure using your library!
Completely understandable and patiently awaiting and excited about the updates to the lib.
**Thank you for prompt response. **


The nacos watcher opened a namingClient, but did not close it

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via ASRC(Alibaba Security Response Center) where the issue will be triaged appropriately.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
The nacos watcher opened a namingClient, but did not close it when the watcher stopped, resulting in a connection leak
Ⅱ. Describe what happened
When I added a nacos registry through mcpBridge, I started a namingClient. When I deleted this registry and re added another nacos registry, the connection to the previous namingClient was not closed
Ⅲ. Describe what you expected to happen
When a nacos registry is deleted, the corresponding namingclient should be closed
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

Higress version:
OS :
Others:

@Erica177 Could you create a PR to fix this issue？

i can fix it


Add support for setting different expiration times based on URL patterns

Closes #184. A few PRs later, adding support for this is now pretty simple.
Note that I'll add a bit more documentation for this and other recent changes in a separate 'Advanced Usage' section (#191).

Coverage increased (+0.3%) to 87.037% when pulling 6dc26710840ef2555fa3c9d9faf70cff312344a7 on JWCook:per-url-expiration into 08886efe1841aae9c6a5e133008b69296d23b8b9 on reclosedev:master.

@vulcan25 @shoeffner Since the two of you originally requested this, let me know if this suits your needs.

Hi @JWCook , sorry for not getting back earlier.
This looks very good and is definitely a cool addition, thanks!


latest outputs endpoint

I added a new endpoint called /latest_ouputs its queries outputs based just on a model name and time range, inferring things like model version and lead time based on the latest model version in the db and the latest ouput from that model.
As a note swaggy ui, what fast api uses for its docs seems to have a bug or something rn, idk I didnt super look into it, but testing through the docs page isn't working. You can use this instead, just make sure you fill it out correctly
curl 'http://localhost:8888/semaphore-api/latest_outputs/modelName=ar_inundation_apr_12h/fromDateTime=2024101618/toDateTime=2024101819'  -H 'accept: application/json' -v

Second round of changes is done. There are two sets of changes in this PR. First Sereies Provider request input has a parameter that lets you choose if it should insert into the db or not. Second the API has been updated to have three total endpoints about requesting outputs. There is outputs (which is legacy and untouched) output_latest, and output_time_span. The new endpoints are updated to work with docs and you can fill information there. How I tested was first running pytest but then:

Get some data to work with

docker exec semaphore-core python3 src/semaphoreRunner.py -d ./Inundation/August/ar_inundation_aug_12h.json -p<PHONE_NUMBER>00
docker exec semaphore-core python3 src/semaphoreRunner.py -d ./Inundation/December/ar_inundation_dec_12h.json -p<PHONE_NUMBER>00
docker exec semaphore-core python3 src/semaphoreRunner.py -d ./Inundation/March/ar_inundation_mar_12h.json -p<PHONE_NUMBER>00```
2. Query it with the different endpoints, the model names and time range is below
Model Names:
```ar_inundation_apr_12h
ar_inundation_aug_12h
ar_inundation_dec_12h
ar_inundation_mar_12h```

Time range:
2024103008
2024103008

You can add more data to the DB, manually change things, try the old endpoint do whatever you want but this is how I tested it.

One thing that was cool is I got tired of defining more and more methods in Series provider that were basically just wrappers for method in the ORM, so I refactored it such that there is just one request output methods, that will take any arguments. It will make sure those arguments get to the right method and throws an exception if something went wrong.

output latest works as intended, but only null is returned for the output timespan. I ran the models for 17:00, 18:00, and 19:00.
I tried switching the from time an to time. They produce the same results.
URL I used:
http://localhost:8888/semaphore-api/output_time_span/?fromDateTime=2024110417&toDateTime=2024110419&modelNames=ar_inundation_apr_12h&modelNames=ar_inundation_aug_12h&modelNames=ar_inundation_dec_12h&modelNames=ar_inundation_mar_12h


Add initialization container to import a save file from a url

init container for save import. Import a save from a URL, or manually copy via kubectl. Supporting documentation updated.
should resolve
#32
#33

@zone-zero can you fix some of the linting issues reported from the pipeline?

glad you liked it.


OS-detection, memory monitoring, system printout in YAML

This is a nice release with several cool new features:

os.yaml — run it after loading init (notice how init.sh had been symlinked to init)
os.info — shorter version by not YAML
memory  — conversion routies for bytes into/from GB/MB/KB/etc.
user.my.ip — is now fixed and works again

Version 3.1.5


What's the technology behind MS Edge?

Which programming languages are you using in MS Edge to allow this multi-platform product?

This is a great question to ask at our team's next AMA!


Bugs/Responsiveness and Consistency in Card Feed Section

🛠 Fixes Issue: #82

#82

👨💻 Changes proposed:

[x] Card feed section adjusts to different screen sizes, including desktop, tablet, and mobile devices.
[x] Adjust image display in cards to maintain aspect ratios and avoid distortion on different devices.

📷 Screenshots
https://github.com/Fenrir-04/Algo-Media/assets/72739429/9f2a468b-0e01-4d96-bb78-e543aa2a8c71

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.
[x] I am a participant of GSSOC23

Hello @KOMALDEWNANI, I have sent the pull request for this issue #82 , if possible could you review it. If there is anything else I can provide you with, please let me know.

Hey, please format the code properly.

Thank you for your feedback. Could you provide me with more information or instructions on how to format the code correctly? I'm not entirely sure about the exact requirements, and any tips or references would be super helpful. Thanks again!

Hey, please format the code properly.

I have made changes to match the project's code style, as you requested. Please review them and let me know if there is anything specific that you would like me to add or change.

Thanks for contributing @krishna-nayak 🚀


Jin/41/path for workflow trigger include iac

Changes:

Created a separate workflow file for Terraform - as the current workflow does not accommodate for it
Workflow trigger conditions for push and PR currently include all under the LOB-ILB-ASEv3 directory excluding either the bicep or terraform directory depending on workflow, to allow them to be handled independently.

Note:

I have not been able to test this yet

The paths for -Bicep and -Terraform are opposite. The -Bicep should have /Bicep as the path trigger and the same for Env Module path. The -terraform has /Bicep as the path trigger when it should be for /Terraform

@cykreng please note the not (!) operand
e.g:
- 'reference-implementations/LOB-ILB-ASEv3/'
- '!reference-implementations/LOB-ILB-ASEv3/terraform/'
 this will exclude changes under the `LOB-ILB-ASEv3/terraform/` directory, but include everything else under the `LOB-ILB-ASEv3` directory.

Either case, I still need to test this so will close this PR until tests are completed.

Got it - so it's just the module path that needs to be modified then, since that was pointing to the terraform path in the workflow for Bicep


:arrow_up<EMAIL_ADDRESS>

Adds fuzzy match character highlighting

Awesome, I'll take a look at this today

Also, I'm not totally sure on this, but I feel like we should add highlighting to all the other SelectLists before we ship this (just for consistency) – symbols-view and command-palette off the top of my head

but I feel like we should add highlighting to all the other SelectLists before we ship this (just for consistency)

Yeah, that sounds good

I think this is worth shipping in the next release before we it into the symbols view and command palette, it is probably most helpful in the fuzzy finder where you have lots of paths that may be very similar and the visual cue is really helpful.
Thanks so much for reviewing and merging the fuzzy finder pull request :ship:


FeatureSupport manual and refactor some execution logic

Supports manually triggered JOBs and Tasks
Optimize JOB&TASK display logic
Refactor the executor to support context passing
Proposed changes
Issue Number: close #xxx

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

run buildall

run buildall


PyFerret: Keys on multi-line plots labeled with numeric variable titles

This comes up when labeling a set of lines such as time series from a DSG file.  The key is labeled with the ID's of the features, and if those ID's are numeric, the line samples are drawn but the label isn't.
Can see this in regular PyFerret with the new PLOT/KEY=TITLE qualifier and using a PyFerret font,
set text/font=verdana
let /title="771" var1  = {7,7,1}
let/title="893" var2 = {8,9,3}
plot/line/sym/thick/key=title var1, var2

It turns out that this is way down in PPLUS, when setting up "moveable labels", which are all the labels around a plot such as it's dataset title and the labels in the upper left with location information.  It parses a pplus command string with location, size, and other information about the label, and looks for the non-numeric portion at the end of that command string and makes it into the label.  So, if the label starts with a number, that's lost too.  In the example above,
let /title="my label is 771" var1  = {7,7,1}
let/title="893 and stuff" var2 = {8,9,3}
plot/thick/key=title var1, var2
The first title is ok but the second title will show up with just "and stuff", not the numbers.
In standard Ferret, the label strings are always preceded with a font information, a code like @AS or @AC, so they're treated correctly.  In PyFerret we don't use that info and so don't send it in to PPLUS. Maybe add some kind of known string that will be found and removed later ( maybe @PY?)

This is fixed in put_label.F and symbel.F in the pyferret and pyferret_DSG branches with a new benchmark test.
Other label commands such as LABEL and ANNOTATE are not affected by this bug.


SA1649 should accept OfT in addition to {T}

When file naming is set to StyleCop settings, generic type params can be in a file name like {T}; however, curly braces can cause issues like coverlet-coverage/coverlet#998 when an input string is formatted. I've seen this happen in other projects as well. https://github.com/dotnet/runtime seemed to have solved this by disabling SA1649 and, at least for many files (about half), use OfT. We'd rather not disable SA1649. It would be great if OfT was acceptable as well. It seems this is another common pattern from web searches.

The name is currently configurable between {T} and  `1. See Configuration.md for details.

Backticks will likely (and has, judging from older reports) cause issues downstream, which is why, I imagine, dotnet/runtime chose OfT.

I'm going to resolve this one as external. The current file names are common and valid on all operating systems, so it is not unreasonable to expect downstream tools to handle them correctly.


conformance: remove skipped workflow categories from report

If a registry doesn't support a workflow, that workflow should be removed from the report to reduce clutter and increase the proportion of green results.

maybe a config option..

See PR #130 -- In that pull request, OCI_HIDE_SKIPPED_WORKFLOWS, if set to 1 will hide any skipped flows from the report.

Resolved by PR #130 -- closing the issue


change base url and cname to moveit.picknik.ai

Description
Updated the URL to point to moveit.picknik.ai. This should fix the ssl cert issue.
Checklist

[ ] Required by CI: Code is auto formatted using clang-format
[ ] While waiting for someone to review your request, please consider reviewing another open pull request to support the maintainers

It's up! http://moveit.picknik.ai/foxy/index.html

We need to change the link in MoveIt 1 tutorials as well, or configure a redirect. ie: Foxy link is broken here: https://ros-planning.github.io/moveit_tutorials/


Add --message and --version flags to the app deploy command

WHY are these changes introduced?
Fixes https://github.com/Shopify/app-deploys/issues/471
WHAT is this pull request doing?

How to test your changes?

Post-release steps

Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[ ] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[ ] I've considered possible documentation changes
[ ] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

Still need to work on adding unit tests

However, when I run app deploy with the message flag (the version flag works) for an app with deployments disabled, I get this error:

Is it okay to error out in this case?

I looked at this briefly. The issue is that the Apps::Models::Deployments::CreateStub operation gets a message argument which it doesn't expect.

Which we can easily fix in the backend. But I wonder if we should expect Shopify Core to handle these exceptions and not blow on user's face. @gordonhirsch what are your thoughts?


Update prompt injection model

Description: Existing model used for Prompt Injection is quite outdated but we fine-tuned and open-source a new model based on the same model deberta-v3-base from Microsoft - laiyer/deberta-v3-base-prompt-injection. It supports more up-to-date injections and less prone to false-positives.
Dependencies: No
Tag maintainer: -
Twitter handle: @alex_yaremchuk

per @efriis's suggestion updated to change docs and configurability without changing default behavior, let me know if it looks ok to you @asofter!

@efriis thank you for the suggestion!
@baskaryan thank you for the implementation. It looks great! Probably in another PR, I will add support of ONNX for faster inference but good to go for now.


Future of this project?

I've been using sinopia for over a year and. I maintain docker container for sinpopia on docker and it's seem like the it's the most used npm cache repo on docker.
But it looks like the lead dev abandonded the project - it's an extremely complicated express app - and I need to decide whether or not to take that over or work on something like this that seems promising and does (almost) the same thing. I don't know how rlidwka wrote it - but I usually get 10x the speed of npm - I use docker to proxy in front of nginx caching servers using http/2 / lets encrypt - but it's all zero-config. I and get it up and running with a gogs in 10 minutes. (unlimited private github repos and npm repos / caching on $5 digital ocean servers)
Sinopia was built to run locally - it's a command line app technically.  It's fast (maybe faster than this). But I have no idea how it works. Not sure if you're familiar with sinopia - but if this repo is active and you're interested in some help i'd be willing to contribute

Thanks for the issue! I actually never intended local-npm to be a sinopia replacement, although it's been a much-requested feature. I plan on continuing to develop local-npm exactly as it is (a dumb mirror in front of npm), but I encourage anybody to fork the codebase and learn from what I did in order to make their own sinopia. :)
As it turns out, I think local-npm's approach has some huge advantages over sinopia when it comes to "build your own npm," because sinopia reimplemented nearly all of npm's registry from scratch, whereas local-npm leverages PouchDB to simply sync npm's CouchDB. Hence we get replication for free as well as a lot of behavioral parity.
Closing this issue because I consider it out of scope for local-npm, but again, I encourage anybody interested in this idea to fork! :)


Docker: volume to persist data

Hi, is there a way to mount a volume to persist the data while using the docker image?
Thanks in advance

Hi @urbany
You should be able to do something like this:
docker run -v `pwd`/docker-maildir:/maildir -p 1025:1025 -p 8025:8025 \
mailhog/mailhog /MailHog -storage maildir -maildir-path=/maildir

That should store the messages in a ./docker-maildir directory, though you can change
`pwd`/docker-maildir

to anything

@ian-kent How to do that in a docker-compose.yml file? Can you provide an example? Something with the command key?

Thanks @rogervila .. Sorry for my late reply, but it works great!

The proposed solution worked for me only with some modification: I had to start it under root user.
The reason for that is the folder /maildir has the root owner/group and 755 permission.
By default the Mailhog process is started as "mailhog" user so it doesn't have write permission to the /maildir folder
So working config for me would be:
mailhog:
user: root
container_name: mailhog
image: mailhog/mailhog:v1.0.0
command: ["-storage=maildir", "-maildir-path=/maildir"]
volumes:
- ./volumes/mailhog/volume:/maildir
ports:
- "1025:1025"
- "8025:8025"

@rogervila solution worked, but I had to set 777 permission to the volumes folder.
sudo chmod -R 777 ./volumes

You can also configure using environment values, and set the path to /home/mailhog to avoid the permission issue
version: '3.8'
services:
  mailhog:
    image: mailhog/mailhog
    container_name: mailhog
    volumes:
      - type: volume
        source: mailhog
        target: /home/mailhog
    ports:
      - 8025:8025
      - 1025:1025
    environment:
      MH_STORAGE: maildir
      MH_MAILDIR_PATH: /home/mailhog
volumes:
  mailhog:

This worked for me
version: "3"

services:
  mailhog:
    image: mailhog/mailhog
    container_name: mailhog
    ports:
      - 8025:8025
      - 1025:1025
    volumes:
      - mailhog-maildir:/home/mailhog/maildir
    environment:
      - MH_STORAGE=maildir
      - MH_MAILDIR_PATH=maildir
    restart: unless-stopped

volumes:
  mailhog-maildir:{}


Migrate YAML config sensors (luxtronik2+luxtronik) to current native sensors

The YAML config is not provided > 2023.03.24
It would be worthwhile to implement a migration that searches the YAML configs (luxtronik <- Bouni and luxtronik2) and migrates the sensors to the new ones.
This would preserve the history and activate the sensor automatically. However, the ID will change and the user will have to manually adjust their links in LoveLace and automation.

I'm not sure implementing this is really worth the effort, for a one-off conversion, of parameters that are used by one or maybe a couple of users.
So far we have had several request of users who needed additional parameters. Those have been implemented without much discussion about keeping historical values.
Main question is whether there are still many other parameters that users have added manually, and that are not yet implemented.
If there are only a small amount, manually implementing them like we did so far could work well. My guess would be that at this stage, time spent on manually implementation of some additional sensors (on user requests) would be less work than writing an automated detection and conversion routine. (And users would still have to make changes to dashboards).
Do others feel the same or do you think writing an automatic conversion utility would be simple and less time-consuming?


Friday 23-02-2024 roll call

Roll Call!
Leave a comment with these two things:

A summary of your study using only emojis
Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Good morning!

Good morning

Hey hey hey

gud mrng!

good morning

Hello

Hello

hi

hello!

GoodMorning

morning

good morning

good morning

good morning


App icon refresh

App icon refresh

This one I kind of like although it's a bit too monochromatic to my liking... But I also liked the original one and that's why I more or less reproduced it, just replacing the numbers to emphasize that this is now a different app. And at the same time emphasizing the inheritance and paying some respect to the original author.
Let me think about it.

BTW, I see that you like doing app icons. I have to admit that I'm not super-happy with my QR Clip  icon:

It's kind of fine, but clearly out of sailfish style and I may consider replacing it with something more sailfishy. The idea was (obviously) to somehow combine QR code and clipboard concepts.
(in case if it's not obvious that QR code isn't random, it says harbour-qrclip)

Let me think about it.

Let me know what you prefer to have changed, I will see how I can take that into account. I try to stay as close to the design of the Sailfish OS icon design guidelines, but also respect the preferences of the developers. I truly think both is possible to merge into a beautiful icon.
PS 1. Your QR Clip app has a new icon pull request :)
PS 2. If there are more apps you prefer to have a new icon for, let me know. I hope I can bring a bit of nice Sailfish OS style and design to your well developed apps.


Vue.js 3 example for Base: https://panejs.com/demo/base.html

Hi. Great work on that project. I was really looking for an example for correct way to initialise the pane in a Vue.js 3 project.
Thank you for the answer!

Hello there again! I share my own code from my project as an example, I hope it helps.
const pane = ref<CupertinoPane>();

onMounted(async () => {
// initialise the pane
  pane.value = new CupertinoPane(".sheet-pane", {
    breaks: {
      top: { enabled: true, height: 460 },
      middle: { enabled: true, height: 240 },
      bottom: { enabled: true, height: 40 },
    },
    initialBreak: "top",
    draggableOver: true,
    parentElement: ".app",
    cssClass: "z-50",
    buttonDestroy: false,
  });

  await pane.value.present({ animate: true });
});

In order to understand the options that I implemented in this code, visit the official documentation:
https://panejs.com/settings.html
For breaks property especially, I'd really suggest you to take a look at the official documentation to understand what it means:
https://panejs.com/breakpoints.html

Big thanks @dasturchioka for help.
I will add this to example on docs soon.

@dasturchioka Here is also Vue 3 wrapper, don't sure its up-to-date, but at least can be explored for examples.
https://github.com/Devrax/v-cupertino

Glad to help, @roman-rr. This Vue 3 wrapper didn't work properly the last time I used it. Also the author of this wrapper recommended to use the main library.

Create a good basic example of Panes using with Vue 3 framework.
Including getting control of Panes from parent components and using as standalone service.
https://github.com/tech-systems/panes-vue3-example