Running in Test Mode?

This is so useful, thank you for writing it.
Is there a way to run this when using mix test? It'd be so helpful to get this kind of display on a failing test, but I'm getting errors when i try
    ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name,
possibly because its application isn't started
    (stdlib 5.0.1) gen_server.erl:386: :gen_server.call/2
    lib/myapp/application.ex:7: (module`)``

I tried adding `Application.ensure_all_started(:telemetry)` to my test_helper but that doesn't change anything.

Even if this can't be done, it's still an awesome library :)

@lauraannwilliams is the issue still relevant?

My apologies!  I thought I'd posted.
Here's my application.ex
defmodule MyApp.Application do
  # See https://hexdocs.pm/elixir/Application.html
  # for more information on OTP Applications
  @moduledoc false

  use Application
  Ecto.DevLogger.install(MyApp.Repo)

  @impl true
  def start(_type, _args) do
    children = [
      # Start the Telemetry supervisor
      MyAppWeb.Telemetry,
      # Start the Ecto repository
      MyApp.Repo,
      # Start the PubSub system
      {Phoenix.PubSub, name: MyApp.PubSub},
      # Start Finch
      {Finch, name: MyApp.Finch},
      # Start the Endpoint (http/https)
      MyAppWeb.Endpoint
      # Start a worker by calling: MyApp.Worker.start_link(arg)
      # {MyApp.Worker, arg}
    ]

    # See https://hexdocs.pm/elixir/Supervisor.html
    # for other strategies and supported options
    opts = [strategy: :one_for_one, name: MyApp.Supervisor]
    Supervisor.start_link(children, opts)
  end

  # Tell Phoenix to update the endpoint configuration
  # whenever the application is updated.
  @impl true
  def config_change(changed, _new, removed) do
    MyAppWeb.Endpoint.config_change(changed, removed)
    :ok
  end
end

my test.exe
import Config

# Configure your database
#
# The MIX_TEST_PARTITION environment variable can be used
# to provide built-in test partitioning in CI environment.
# Run `mix help test` for more information.
config :myapp, MyApp.Repo,
  username: System.get_env("POSTGRES_TEST_USERNAME") || "postgres",
  password: System.get_env("POSTGRES_TEST_PASSWORD") || "postgres",
  hostname: System.get_env("POSTGRES_TEST_HOST") || "postgres",
  database: "myapp_test",
  timeout: 180_000,
  connect_timeout: 180_000,
  pool: Ecto.Adapters.SQL.Sandbox,
  pool_size: 10

if config_env() == :test do
  config :myapp, MyApp.Repo, log: false
end

# We don't run a server during test. If one is required,
# you can enable the server option below.
config :myapp, MyAppWeb.Endpoint,
  http: [ip: {127, 0, 0, 1}, port: 4002],
  secret_key_base: "keybase",
  server: false

# In test we don't send emails.
config :myapp, MyApp.Mailer, adapter: Swoosh.Adapters.Test

# Disable swoosh api client as it is only required for production adapters.
config :swoosh, :api_client, false

# Print only warnings and errors during test
config :logger, level: :warning

# Initialize plugs at runtime for faster test compilation
config :phoenix, :plug_init_mode, :runtime

and my  test_helper.ex
ExUnit.configure(exclude: [pending: true])

Application.ensure_all_started(:telemetry)

Faker.start()

ExUnit.start()

Ecto.Adapters.SQL.Sandbox.mode(MyApp.Repo, :manual)

And finally the error message when i run mix.test:
== Compilation error in file lib/myapp/application.ex ==
** (exit) exited in: :gen_server.call(:telemetry_handler_table, {:insert, [:ecto_dev_logger, :myapp, :repo], [[:myapp, :repo, :query]], &Ecto.DevLogger.telemetry_handler/4, []})
    ** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
    (stdlib 5.0.1) gen_server.erl:386: :gen_server.call/2
    lib/myapp/application.ex:7: (module)

finally..
elixir --version
Erlang/OTP 26 [erts-14.0.1] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns]

Elixir 1.15.4 (compiled with Erlang/OTP 26)

Thank you very much for your time

  Ecto.DevLogger.install(MyApp.Repo)

must be called inside def start(...) do block

thanks, that should have been very obvious


Prepare v1.2.9 release

Only change is fixes for gRPC CVE issues by updating vendor to gRPC 1.23.0 release via PR #3586.
Signed-off-by: Phil Estes<EMAIL_ADDRESS>Preview draft of release notes: https://gist.github.com/estesp/8dfeab5baf156ea1dc92793043193167

Is possible to include https://github.com/containerd/containerd/pull/3245 as well? Recently released GitHub Package Registry doesn't provide Docker-Content-Registry, and stable<EMAIL_ADDRESS>cannot be used with it.

@artch I can open a backport for consideration by the maintainers; there's another ticket tracking issues with the GitHub Package Registry here: https://github.com/containerd/containerd/issues/3291 (so there may still be issues remaining)
/cc @Phanatic

Opened https://github.com/containerd/containerd/pull/3591 for consideration

notes updated with all backports; gist notes preview updated (although missing the CRI vendor update as #3608 is not merged yet.)

LGTM


Width Sharded Height Concat for Row Major Tensors

We wish to add a width sharded height concat operation.
The Problem
First lets visualize the full tensors (unsharded) and look at what we mean by height concat.

The Height Concatenated tensor will be what the tensor looks like on the host. However the tensors are sharded, meaning that per core in the L1s we will have a subset of the tensor. This is what it looks like per core, not that each core has a portion of both tensors.

Per core the operation would be a height concat of the respective shards.

How to Solve It
We already have implemented a solution for height sharded tensors that need to be width concat.

https://github.com/tenstorrent/tt-metal/blob/main/ttnn/cpp/ttnn/experimental/tt_dnn/op_library/concat/multi_core/concat_op_multi_core.cpp#L156

This is the host code for height sharded, width concat.
You will see that the tensor is in Row Major Format.  This is standard format where the elements are in row-major order. We have the notion of a page , which is the smallest granularity of memory. In a row-major tensor , a page is equivalent to a single row in height, and the width of a shard.
In a height sharded example, that is the entire input tensor. In the width shared case, that will be equivalent to the width of the shard.

This is the corresponding kernel. https://github.com/tenstorrent/tt-metal/blob/main/ttnn/cpp/ttnn/experimental/tt_dnn/op_library/concat/kernels/dataflow/reader_height_sharded_width_concat.cpp

Test Cases
In order to test we need to make a width Sharded tensor.  This makes a width Sharded tensor 64x32 each across 2 cores . the output data at the end should be the same as concatting the input with itself on dim 2.
    input_data = torch.randn(shape, dtype=torch.bfloat16)
    x = ttnn.from_torch(
        [1, 1, 64, 64],
        device=device,
        layout=ttnn.ROW_MAJOR_LAYOUT,
        memory_config=ttnn.L1_MEMORY_CONFIG,
        dtype=ttnn.bfloat16,
    )
    shard_config = ttnn.create_sharded_memory_config(
        shape=[1, 1, 64, 64],
        core_grid=ttnn.CoreGrid(y=2, x=1),
        strategy=ttnn.ShardStrategy.WIDTH,
        orientation=ttnn.ShardOrientation.ROW_MAJOR,
        use_height_and_width_as_shard_shape=False,
    )
    x_t = ttnn.to_memory_config(x, memory_config=shard_config, dtype=ttnn.bfloat16)
    y_t = ttnn.concat(x_t, x_t, dim=2)
    y_h = ttnn.from_device(x_t)
    output_data = ttnn.to_torch(y_h)

I started working on this and here is my attempt to support width sharded height concat https://github.com/tenstorrent/tt-metal/pull/13314. Please let me know if you have any feedback, thanks!

@ntarafdar , we think it’s done now.


Modules and Python Interpreter Discovery in venv

Did a build and release on PR 288
Inventory is populating however when running jobs I seem to be having an issue with python interpreter discovery.
Also when I try to reference collections and modules I am running into an issue with discovery.
The interpreter is specified in the ansible.cfg
(ansible-prd) nmoore@itnet-bastion0:~/neteng/automation/ansible$ ansible --version
ansible [core 2.12.0]
  config file = **/home/nmoore/neteng/automation/ansible/ansible.cfg**
  configured module search path = ['/home/nmoore/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/nmoore/anaconda3/envs/ansible-prd/lib/python3.8/site-packages/ansible
  ansible collection location = /home/nmoore/.ansible/collections
  executable location = /home/nmoore/anaconda3/envs/ansible-prd/bin/ansible
  python version = 3.8.8 (default, Apr 13 2021, 19:58:26) [GCC 7.3.0]
  jinja version = 2.11.3
  libyaml = True

(ansible-prd) nmoore@itnet-bastion0:~/neteng/automation/ansible$ cat /home/nmoore/neteng/automation/ansible/ansible.cfg
[defaults]
inventory = /home/nmoore/neteng/automation/ansible/inventory/inventory.yaml
deprecation_warnings = False
remote_port = 22
host_key_checking = False
roles_path = ~/.ansible/roles
collections_path = ~/.ansible/collections
stdout_callback = yaml
**ansible_python_interpreter = /home/nmoore/anaconda3/envs/ansible-prd/bin/python**
ansible_ssh_user = bastion
ansible_network_os = junipernetworks.junos.junos
[persistent_connection]
connect_timeout = 600
[inventory]
enable_plugins = yaml, ini
[ssh_connection]
scp_if_ssh=True

Basic Ping Test using standard ping module
---
- hosts: junos_all
  tasks:
    - name: test connection
      ping:

PLAY [junos_all] ***************************************************************
TASK [Gathering Facts] *********************************************************
[WARNING]: Unhandled error in Python interpreter discovery for host
ams1-cgw1.corp.****.com: unexpected output from Python interpreter
discovery
fatal: [ams1-cgw1.corp.****.com]: FAILED! =>
msg: |-
failed to transfer file to /var/lib/rundeck/.ansible/tmp/ansible-local-114011oijljg5/tmpz7k8bdsf error: unknown command: **/bin/sh/AnsiballZ_setup.py:**
scp: error: unknown command: /bin/sh/AnsiballZ_setup.py: No such file or directory
PLAY RECAP *********************************************************************
ams1-cgw1.corp.****.com : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0

Testing w/ Roles/Collections
(ansible-prd) nmoore@itnet-bastion0:~/neteng/automation/ansible$ cat junos_pull_config_pb.yaml
---
- name: Junos Config Dump
  hosts: junos_all
  connection: local
  gather_facts: false
  roles:
    - junos_pull_config
(ansible-prd) nmoore@itnet-bastion0:~/neteng/automation/ansible$ cat roles/junos_pull_config/tasks/main.yaml
---
- name: "Get committed configuration"
  juniper.device.config:
    timeout: 120
    retrieve: "committed"
    format: "set"
    dest_dir: "{{ playbook_dir }}/roles/junos_pull_config/files/configs/set"
  register: response

ERROR! couldn't resolve module/action 'juniper.device.config'. This often indicates a misspelling, missing collection, or incorrect module path.
The error appears to be in '/home/nmoore/neteng/automation/ansible/roles/junos_pull_config/tasks/main.yaml': line 8, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
#  register: response
- name: "Get committed configuration"
  ^ here
Failed: AnsibleNonZero: ERROR: Ansible execution returned with non zero code.

(ansible-prd) nmoore@itnet-bastion0:~/neteng/automation/ansible$ ansible-galaxy collection list | grep device
juniper.device         1.0.1

Project Settings:
#Thu Mar 03 17:43:02 UTC 2022
#edit below
ansible-binaries-dir-path=/home/nmoore/anaconda3/envs/ansible-prd/bin/
project.ansible-binaries-dir-path=/home/nmoore/anaconda3/envs/ansible-prd/bin/
project.ansible-config-file-path=/home/nmoore/neteng/automation/ansible/ansible.cfg
**project.ansible-executable=/bin/bash**
project.ansible-generate-inventory=true
project.ansible-ssh-auth-type=privateKey
project.ansible-ssh-key-storage-path=keys/project/Self_Service_Portal/nmoorepriv
project.ansible-ssh-passphrase-option=option.password
project.ansible-ssh-user=nmoore
project.description=
project.disable.executions=false
project.disable.schedule=false
project.execution.history.cleanup.batch=500
project.execution.history.cleanup.enabled=false
project.execution.history.cleanup.retention.days=60
project.execution.history.cleanup.retention.minimum=50
project.execution.history.cleanup.schedule=0 0 0 1/1 * ? *
project.jobs.gui.groupExpandLevel=1
project.label=
[project.name](http://project.name/)=Self_Service_Portal
project.nodeCache.enabled=true
project.nodeCache.firstLoadSynch=true
project.output.allowUnsanitized=false
project.ssh-authentication=privateKey
project.ssh-keypath=/var/lib/rundeck/.ssh/id_rsa
resources.source.1.config.ansible-config-file-path=/home/nmoore/neteng/automation/ansible/ansible.cfg
resources.source.1.config.ansible-gather-facts=false
resources.source.1.config.ansible-ignore-errors=true
resources.source.1.config.ansible-inventory=/home/nmoore/neteng/automation/ansible/inventory/inventory.yaml
resources.source.1.config.ansible-ssh-auth-type=password
resources.source.1.config.ansible-ssh-password=*****
resources.source.1.config.ansible-ssh-user=nmoore
resources.source.1.type=com.batix.rundeck.plugins.AnsibleResourceModelSourceFactory
service.FileCopier.default.provider=jsch-scp
service.NodeExecutor.default.provider=com.batix.rundeck.plugins.AnsibleNodeExecutor

Santander Customer is facing this same issue and they already know since this was a Public Repo (Batix) there is a potential solution in the PR 288
This is a blocker for the customer. SF ticket No. 00083945


add an option to not include the location in the Atom content

Posts in my Atom feed have the location they're posted from included inside the Atom content.
  <content type="xhtml">

OH: Your level of commitment to trolling the internet is admirable #domainswap

    Portland,
        Oregon,
        USA

  </content>

While this makes sense for readers, so that you see this information in a feed reader, it doesn't look good when using the Atom feed for syndication, such as how micro.blog can import posts from an Atom feed. http://micro.blog/aaronpk
Maybe there could be a query string parameter on the granary URL that would prevent this from being included in the content? e.g.
https://granary-demo.appspot.com/url?input=html&output=atom&url=http%3A%2F%2Faaronparecki.com%2Fnotes&omit_location=true

done! @aaronpk you can now add &reader=false to your granary URL to omit location.


Any Idea for feature update for targeted speaker transcription?

hi, what do you mean by "targeted speaker transcription"?
I think that if you use an underlying model that supports it, instead of the default Whisper, than it will work.

I mean, suppose multiple speakers speak in an environment ( noisy environment where people are speaking in the background)
I would like to transcribe the main speaker (who is close to mic) only, I tested the "mic_test_whisper_simple.py" it works very well, however it tend to capture all the noises ( still speech but far from mic) in-between my speech.


I HAVE A QUESTION AT _PASSWORD = os.environ.get("IG_PASSWORD", "password*")

Hey i want to enter my account password at the _PASSWORD = os.environ.get("IG_PASSWORD", "password*") . Does i need to remove the sysmbol * in "password*") ?

you need to remove the entire second argument of "password*". os.environ is treated as a dict so if you story your environment var as
{
"IG_PASSWORD": "mySecurePassword"
}

then to get that password you would use
_PASSWORD = os.environ.get("IG_PASSWORD")
# print(_PASSWORD)
# prints 'mySecurePassoword'

so i need to change IG_PASSWORD with my password? so if i ask a stupid question im newbie

My mistake, I thought you wanted to get your password from the environment variable. if you are using this for a personal project and you are not worried your password being in your local project, you can just write _PASSWORD = "yourpassword".
if you want to set you environment var in code however use the following:
>>> os.environ['IG_PASSWORD'] = "yourpass"     # Set a new env. variable (String value)

also the reason that there are two arguments here: _PASSWORD = os.environ.get("IG_PASSWORD", "password*") is because if the environ variable IG_PASSWORD does not exist, it will return password*.

It depends, is this issue your own fork/project? Or is this issue under someone else's project? If the latter, then I'd say no but if this is your project, then ya it's fine.

It depends, is this issue your own fork/project? Or is this issue under someone else's project? If the latter, then I'd say no but if this is your project, then ya it's fine.

I dont have issue or with someonelse. Just me haha

No, I mean when you make a question like you, did, you have to make it on an issue on a repository. This thread we're on right now is called an issue. Did you create that issue thread on your own repository or someone else's

Not my own repo, sorry because of my english I can't understand you very well. I will close this issue


[Event Request] Table 7302 Bin Content - Add parameter to function OnCalcTotalQtyAvailToTakeOnAfterCalcPickQuantityBase

Dear ALAppExtensions Team,
Is it possible to add a parameter to function OnCalcTotalQtyAvailToTakeOnAfterCalcPickQuantityBase in Table 7302 ?

OnCalcTotalQtyAvailToTakeOnAfterCalcPickQuantityBase(Rec, ExcludeQtyBase);
+OnCalcTotalQtyAvailToTakeOnAfterCalcPickQuantityBase(Rec, ExcludeQtyBase, TotalNegativeAdjmtQtyBase);

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Frontend: Site Navigation

Site Navigation

[ ] Links for Home, Sign In/Sign Out, Dashboard.
[ ] Fixed/Sticky Navigation to top of page.
[ ] Logo(Home link)

Some notes about link visibility:

Hide Dashboard if User is not signed in.
Show Dashboard if user is signed in.
Hide Sign Out if user is not signed in.
Show Sign Out if user is signed in.
Hide Sign In if user is signed in.
Show Sign In if user is not signed in.

Thank Sean I will get on it now. I was kinda confused on the direction I needed to takeSent from my iPhoneOn Sep 28, 2023, at 12:57 PM, Sean Standen @.***> wrote:
Assigned #13 to @StormKing777.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>


[CDEC-370] Enable benchmarks for all packages with benchmarks

Description
#3008 added the buildWithBenchmarks function to default.nix, but only enabled it for cardano-sl-wallet-new. This enables it for all packages with benchmark sections in their cabal file.

Linked issue
CDEC-370

Type of change

[~] 🐞 Bug fix (non-breaking change which fixes an issue)
[~] 🛠 New feature (non-breaking change which adds functionality)
[~] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[~] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[x] 🔨 New or improved tests for existing code
[~] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[x] I have read the style guide document, and my code follows the code style of this project.
[x] If my code deals with exceptions, it follows the guidelines.
[x] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[~] I have added tests to cover my changes.
[x] All new and existing tests passed.

QA Steps

Screenshots (if available)

Expecting this to fail CI first time because the cardano-sl benchmark should be broken.

This is supposed to not run them apparently (default behaviour from nixpkgs)

@avieth Just to confirm, this is supposed to build but not run benchmarks.


[release/v2.7] Add docker 23.0 support and set it as default.

Linked issue: https://github.com/rancher/rancher/issues/40731
Note: There are references of docker 20.10 in the validation tests and new automation framework. These references have not been updated to ensure nothing breaks. We will track updating docker version for these tests in a separate ticket.

@snasovich

I have updated the tests to use docker 23.0 version.
I think we should not update the docker 20.10.x references in go.mod. There are some libraries in rancher which are using some packages from docker 20.10.17 which are not present in docker 23.0.


Updates to IDEX L1 code for consistency

There are a few updates we can make to the IDEX L1 code to be more consistent with other instruments' pipelines:

Generate an updated packet definition file with recent version of space_packet_parser
Separate out the L0 decommutation code and the L1 processing code within idex_packet_parser.py, and update unit tests accordingly
Switch CDF attribute definitions to use yaml files instead of dataclasses
Add call to write_cdf() within pipeline so that CDFs get created within the pipeline, instead of within cli.py

You may want to hold off on that final bullet. I think that @greglucas had some compelling reasons as to why the pipelines should not be calling write_cdf().


Bug:

What happened?
A bug happened!
Steps to reproduce

step one...
step two...

What OS are you seeing the problem on?
No response
Relevant log output
failed to open model

Caused by:
    Failed to create a new whisper context.

Location:
    core\src\transcribe.rs:37:65
App Version: vibe 2.6.3
Commit Hash: d24ffccb0d05ea822ff1a3a6edb3b9871be9f368
Arch: x86_64
Platform: windows
Kernel Version: 10.0.26100
OS: windows
OS Version: 10.0.26100
Cuda Version: n/a
Models: ggml-large-v3.bin, ggml-medium.bin
Default Model: "C:\\Users\\Michael\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-large-v3.bin"
Cargo features: vulkan

{
    "avx": {
        "enabled": true,
        "support": true
    },
    "avx2": {
        "enabled": true,
        "support": true
    },
    "f16c": {
        "enabled": true,
        "support": true
    },
    "fma": {
        "enabled": true,
        "support": true
    }
}

https://github.com/thewh1teagle/vibe/issues/370


Update to the new release of cairo-rs

This PR includes all the necessary changes to update to the newest cairo-rs version.
Changes made:

Updated Cargo.toml for the main project and the starknet-rs-py crate to this cairo-rs version
Refactor calls to runner.initialize_function_runner (always add_segment_arena_builtin as False)
Refactor calls to runner.run_from_entrypoint (always program_segment_size as None)

Please pay extra attention to program_segment_size when reviewing!

Codecov Report

:exclamation: No coverage uploaded for pull request base (0.11@b4fba73). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             0.11     #269   +/-   ##
=======================================
  Coverage        ?   73.80%
=======================================
  Files           ?       40
  Lines           ?     2691
  Branches        ?        0
=======================================
  Hits            ?     1986
  Misses          ?      705
  Partials        ?        0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Unable to run from outside particleviz directory

I don't seem to be able to run particleviz from outside the particleviz directory.
For example, if I run python ~/Codes/particleviz/ParticleViz.py --input_file argo_float.nc, I get
Initializing webapp...
Traceback (most recent call last):
  File "/Users/erik/Codes/particleviz/ParticleViz.py", line 64, in <module>
    shutil.copyfile("Current_Config.json", join("ParticleViz_WebApp","src","Config.json"))
  File "/opt/anaconda3/envs/particleviz/lib/python3.10/shutil.py", line 256, in copyfile
    with open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 'ParticleViz_WebApp/src/Config.json'

It seems to be working correctly now.


I am going to upgrade something in new repo, and fix some bugs when using webpack

repo: https://github.com/hxl-dy/clappr-rtmp-plugin/tree/upgrade
upgrades:

jshint -> eslint
webpack1 -> webpack2

fix bugs:
following bugs will occur when I use webpack to package it to my project:

cannot auto play
play button won't change to pause when playing and no action occurs after clicking it
double click video screen won't trigger full screen action
volume control doesn't work

could i ask you for help when getting stuck? thank you!

yep @hxl-dy feel free to reach me any time you get stuck, thanks for helping on the maintenance of this project

repo: https://github.com/hxl-dy/clappr-rtmp-plugin/tree/webpack2
DONE:

jshint -> eslint
webpack1 -> webpack2

TODO:

use uglify#harmony
remove babel

FIXME:

double click video screen won't trigger full screen action

@hxl-dy I wonder if it makes sense to bring the modifications in your branch to this repository, are you still actively using this plugin?


Respect defaultInputValue when provided

Hi, thanks a lot for this UI-less solution: it's been really easy to integrate with our existing UI lib as a substitution of a (really) old jQuery based one!
I'm having one single problem: I provide both a selectedItem and a defaultInputValue to downshift, and since inputValue and selectedItem are decoupled, I'd expect that in my initial rendering I would see defaultInputValue.
In practice this snippet of code in the constructor:
if (state.selectedItem != null) {
  state.inputValue = this.props.itemToString(state.selectedItem)
}

prevents that, effectively coupling the two fields.
I'd suggest to also check wether this.props.defaultInputValue is null in that if condition.

Hmmm... But the only reason selectedItem would not be null is if you're specifying a defaultSelectedItem prop. The inputValue should reflect the selectedItem when the user hasn't made changes to the input value which is why that logic is the way it is. Can you show an example of the kind of UI experience you're trying to build so I can understand better why you want things to not work as they are?

I'm talking about the initial render only (where the default values make sense), I'll show you what I mean shortly.

Here a quick example.
I would like to maintain the decoupling you have when you're changing the input, but the selected item doesn't change yet:

even in the first render (here implemented by a pristine value in the state:

The user experience I'd like to give is: since users haven't interacted with the dropdown yet, I'd like to show them all the viable options.
Now the experience they have is: they see an input without options, and they have to actively clear the input before options are shown
Example: here (I just took one official example, and added a defaultSelectedItem).

That's very interesting. I'm inclined to agree with you. I'm thinking what might be better is an initialInputValue prop, or perhaps a more flexible prop that could allow you to specify the initial state of the entire component:
const ui = <Downshift initialState={{isOpen: true, inputValue: '', selectedItem: items[3], highlightedIndex: 3}} />

What would you say to that?

My understanding was that it was exactly the role of the default_ props (defaultSelectedItem, defaultHighlightedIndex, defaultInputValue, defaultIsOpen), if not I completely missed their point..
Anyway, any solution looks equally promising (where the more flexible one could be useful moar broadly).

That's part of the use case, but another part of the use case is what to do when downshift is reset. The distinction is slight and normally not noticeable. It's probably kinda confusing. But the reason the default isn't being picked up in this case is because the default doesn't make sense when there's a selected item. Default is interpreted to mean: "When there's no other value that makes sense." In this case there is a value that makes sense. And that value is the itemToString value of the default selected item. 😅
Sorry it's confusing. I think I'd merge a PR to add support for initialState. We'd definitely want tests and docs for it. I think it should be considered an advanced prop (for docs purposes).

I got the distinction. I'll try to get a PR with the initial_ props ASAP.
I'd go down the distinct props, as opposed to the initialState, just to keep the same API.
I'll try also to add a short paragraph in the docs to explain the distinction.
Would that be OK?

That sounds fine. Maybe we could get away with not having docs dedicated to each prop? I want to avoid confusion. Most people probably wont need these props so having a single section for "initial props" would probably be sufficient.

agreed!

I have a question: right now on reset only defaultHighlightedIndex is respected, but from your previous comment I thought the default props were meant to be used on reset.
This is the piece of code I'm talking about:
  reset = (otherStateToSet = {}, cb) => {
    otherStateToSet = pickState(otherStateToSet)
    this.internalSetState(
      ({selectedItem}) => ({
        isOpen: false,
        highlightedIndex: this.props.defaultHighlightedIndex,
        inputValue: this.props.itemToString(selectedItem),
        ...otherStateToSet,
      }),
      cb,
    )
  }

Shouldn't it be something more like:
  reset = (otherStateToSet = {}, cb) => {
    otherStateToSet = pickState(otherStateToSet)
    this.internalSetState(
      (state) => {
        return {
          isOpen: this.props.defaultIsOpen,
          highlightedIndex: this.props.defaultHighlightedIndex,
          inputValue: this.props.defaultInputValue || this.props.itemToString(this.props.defaultSelectedItem),
          selectedItem: this.props.defaultSelectedItem,
          ...otherStateToSet,
        }
      },
      cb,
    )
  }

where the current state is completely discarded in favour to the default props?

Yeah, you're right. It really should be using the defaults in the reset. That's a design flaw. I sure wish that we'd realized this before I released 2.0.0 last week 😅
I think this is worth releasing 3.0.0 though. So let's change this and push it as a breaking change. Could you do that?

I'm working on this at the moment and I've got a solution that I like.
The one difference from what we discussed is the changes to the reset function. I will document this, but the expectation of the reset function isn't to totally revert the state of downshift to the initial state, but instead to reset it to the last selected item. Based on how it's used internally and externally, that's the best expectation.
Practically what this means is that the selectedItem will remain the same, and the inputValue will be derived from that value. The highlightedIndex and isOpen state will be based on the defaultValue though.
If someone wanted to completely reset downshift, they could do so by passing overrides:
reset({selectedItem: null, inputValue: ''})
// or, fun fact, we expose setState too, though this is undocumented:
// setState({isOpen: false, highlightedIndex: null, selectedItem: null, inputValue: ''})

All that said, perhaps reset isn't the right name for this function. If you have a better name for it let me know. Thanks!

:tada: This issue has been resolved in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Migrateboard, close #116

remove old board name and add new board name to board list
add keyword, author subs from old to new board
remove old board name and add new board name to pushsum board list, add subs to new board
rename article's board name
merge user old and new board subscription data

Codecov Report

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

@@           Coverage Diff           @@
##           master     #119   +/-   ##
=======================================
  Coverage   59.42%   59.42%
=======================================
  Files           9        9
  Lines         138      138
=======================================
  Hits           82       82
  Misses         55       55
  Partials        1        1

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 d48b5d3...4e09f43. Read the comment docs.


--popper-theme-border-width affects arrow

Description of the bug
If you don't want a border around the popper and use --popper-theme-border-width: 0, this also removes the arrow completely. It looks like the arrow size is linked to the same --popper-theme-border-width variable.
To Reproduce
Steps to reproduce the behavior:

Set arrow property, observe an arrow shows up
Set the --popper-theme-border-width var to 0
Observe arrow is gone

Expected behavior
Arrow size to have independent styling variable from the popper's own border
Screenshots
With border 2px:

With border 0:

Border is correctly removed, but arrow is gone.

@adamreisnz I also faced the same issue.
It seems that along with the 0 value, "px" must be added as well.
Cheers


[ListView] Prevent rendering during an interaction?

I noticed that extreme jitter occurs if a ListView renders rows during a pan interaction. Is there any way to stop the ListView from rendering rows (maybe using InteractionManager)? Thanks!

I implemented this but not sure if it's something that will go into core: https://github.com/facebook/react-native/issues/2990

Fantastic. Thanks, @brentvatne.
Any reason(s) for this not making it into core? It seems to be the only solution for avoiding ListView jitter during animation and user interaction. Isn't that something a lot of people need?

@aleclarson - Well perhaps it could make it actually.. I've been working on something else recently to throttle paging in new rows with requestIdleCallback and had some good success with that too. Combined they make interactions in apps with heavy use of ListViews seem smoother / snappier in a subtle yet certainly noticeable way. Wish I could share a video of a comparison but it's for a private project atm :(

Also, @sahrens is doing a lot of work on ListView :)

Exciting times! Janky ListViews make me physically ill. :smile:

I think using interaction manager is something we want to do, although it's not usually a problem because people don't often navigate before the ListView finishes rendering. You may want to adjust your initial size and other variables to mitigate.
requestIdleCallback could be cool too.
cc @nicklockwood

although it's not usually a problem because people don't often navigate before the ListView finishes rendering

What about long lists? Paging in new rows while the user is scrolling can result in jankiness depending on the complexity of the row view; even if pageSize is limited to one. This is especially noticeable when Image elements are used.

Also, this case could benefit from InteractionManager:

I navigate to a ListView and it starts paging in new rows before its superview has completed its entrance animation.

On a side note, it could be useful to have a preventRowRendering prop in the case that:

I tap something to navigate away from the ListView before it's done paging in new rows. The ListView can be returned to, so it cannot be unmounted.

How does requestIdleCallback work?

Is there a small but powerful prop we could add to ListView's API to configure the incremental rendering behavior? For example, some people might want to use InteractionManager, some people want to use requestIdleCallback, and others might want to use other heuristics such as capping the number of rows per frame (pageSize).
Here's a first take at an API:
<ListView
   shouldRenderRow={(rowData, sectionId, rowId, <what else?>) => boolean}
/>

For convenience we may want to also pass in the number of rows rendered during this pass of the JS event loop -- implementing pageSize is trivial:
shouldRenderRow={(rowData, sectionId, rowId, numberOfMarginalRowsRendered) =>
  numberOfMarginalRowsRendered < pageSize
}

The main things I like about this approach is that ListView doesn't become more of a monster API and it pushes the complexity out of the component and into userspace.

Another option would be to inject a task queue into ListView, which could
be InteractionManager, or a simple queue that checks a shouldRenderRow
function? Seems like maybe the most flexible option?
On Monday, December 7, 2015, James Ide<EMAIL_ADDRESS>wrote:

Is there a small but powerful prop we could add to ListView's API to
configure the incremental rendering behavior? For example, some people
might want to use InteractionManager, some people want to use
requestIdleCallback, and others might want to use other heuristics such as
capping the number of rows per frame (pageSize).
Here's a first take at an API:
<ListView
shouldRenderRow={(rowData, sectionId, rowId, <what else?>) => boolean}/>
For convenience we may want to also pass in the number of rows rendered
during this pass of the JS event loop -- implementing pageSize is trivial:
shouldRenderRow={(rowData, sectionId, rowId, numberOfMarginalRowsRendered) =>
numberOfMarginalRowsRendered < pageSize
}
The main things I like about this approach is that ListView doesn't become
more of a monster API and it pushes the complexity out of the component and
into userspace.
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/issues/4359#issuecomment-162653596
.

it does not solve all the problems listed here but for navigation fluidity related problems, you can check https://github.com/machard/react-native-advanced-navigation

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/listview-prevent-rendering-during-an-interaction
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub. GitHub issues have voting too, nevertheless
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.


Ignite Runtime

removed /var/lib/firecracker
1st Run:
...
DEBU[0000] runtime.auth: registry config dir path: ""
DEBU[0000] latest version 0.32.0 is newer than the current one 0.0.0
INFO[0007] Starting image import...
DEBU[0007] Allocating image file and formatting it with ext4...
DEBU[0007] Copying in files to the image file from a source...
DEBU[0008] Retrieving minimum size for "/dev/loop19"
DEBU[0008] Minimum size: 30447 blocks
DEBU[0009] Truncating "/var/lib/firecracker/image/d0f6d411083c6dee/image.ext4" to 124710912 bytes
INFO[0009] Imported OCI image "networkop/kernel:4.19" (83.9 MB) to base image with UID "d0f6d411083c6dee"
DEBU[0009] Ensuring image networkop/ignite:dev exists, or importing it...
Error: failed to find OCI image ref "networkop/ignite:dev": strict decoding error: unknown field "spec", unknown field "status"

2nd Run:
...
DEBU[0000] runtime.auth: registry config dir path: ""
DEBU[0000] latest version 0.32.0 is newer than the current one 0.0.0
INFO[0006] Starting image import...
DEBU[0006] Allocating image file and formatting it with ext4...
DEBU[0006] Copying in files to the image file from a source...
DEBU[0006] Retrieving minimum size for "/dev/loop19"
DEBU[0006] Minimum size: 12217 blocks
DEBU[0006] Truncating "/var/lib/firecracker/image/208994974d5ee84a/image.ext4" to 50040832 bytes
INFO[0006] Imported OCI image "networkop/ignite:dev" (36.1 MB) to base image with UID "208994974d5ee84a"
DEBU[0006] Ensuring image networkop/cx:4.3.0 exists, or importing it...
Error: failed to find OCI image ref "networkop/cx:4.3.0": strict decoding error: unknown field "spec", unknown field "status"

3rd Run:
DEBU[0013] Importing kernel with ociRef "networkop/kernel:4.19"
INFO[0015] Imported OCI image "networkop/kernel:4.19" (83.9 MB) to kernel image with UID "aa980f386ce190d3"
DEBU[0015] Ensuring image networkop/cx:4.3.0 exists, or importing it...
DEBU[0015] Found image with UID 929a94c5b08a0b1d
INFO[0015] Error AllocateAndPopulateOverlay: strict decoding error: unknown field "spec", unknown field "status"
ERRO[0015] failed deploy phase for node "sw2": strict decoding error: unknown field "spec", unknown field "status"

4th Run is finally fine. but requires a containerlab destroy -t <topofile> up front
This is reproducible behaviour.
Topo is:
name: cvx01

topology:
  nodes:
    sw1:
      kind: cvx
      image: networkop/cx:4.3.0
      binds:
        - sw1/interfaces:/etc/network/interfaces.d/host-mounts
    sw2:
      kind: cvx
      image: networkop/cx:4.3.0
      binds:
        - sw2/interfaces:/etc/network/interfaces.d/host-mounts

  links:
    - endpoints: ["sw1:swp11", "sw2:swp21"]

steiler@vbox:/lab-examples/cvx05$ cat sw1/interfaces
auto swp11
iface swp11
address <IP_ADDRESS>/24
steiler@vbox:lab-examples/cvx05$ cat sw2/interfaces
auto swp21
iface swp21
address <IP_ADDRESS>/24

This is the same error as #1039. Where already some investigation took place.
Closing.


CList crashes is coordinates components are floats

While I was playing around with making #36 work, I noticed that CList doesn't know what to do with floats in the chat.
Just type "0.5 0.5 0.5" in the chat and it should crash it.

Yeah, you're right. I was formatting the numbers the wrong way.


Allow words that are not in the Inflections table to be recognized by lemma

@aarppe said:

it seems that the descriptive FST is still not used, since words with reduplication or lexical preverbs, or grammatical preverbs not in the  full paradigms, are not yet recognized.

I believe this is a tiny error in the lookup algorithm, which will only output a result if it exists in the Inflection table in the database, even if the FST recognizes it. If an analysis is given, and there's it's not a known wordform, it should be passed to the normative generator (minus +Err/Orth tags) and be output as a result, linking to its lemma. See #100.

I'm on this

this is fixed together with #114


Use alloc_constant for parameters for crypto primitives

Motivation
This PR makes two changes:

force all the crypto primitives parameters to be allocated only through alloc_constant, and alloc/alloc_input is now "unimplemented" and will cause a panic
update the DPC to allocate the cryptographic primitive gadgets using alloc_constant
remove the serialization of cryptographic primitive parameters (which at this moment is empty).

Test Plan
Some tests have been executed in gadgets and related dirs.

LGTM


Documentation change

Change to documentation example, from users/:userId to :userId

@fedgrant You've made this PR against your own local fork. You need to make it against the @reactjs/react-router repo.

Thanks for catching that. I think I did it right this time.


Delete public datasets after tests

🚀 🚀 Pull Request
Checklist:

[x]  My code follows the style guidelines of this project and the Contributing document
[x]  I have commented my code, particularly in hard-to-understand areas
[x]  I have kept the coverage-rate up
[x]  I have performed a self-review of my own code and resolved any problems
[x]  I have checked to ensure there aren't any other open Pull Requests for the same change
[x]  I have described and made corresponding changes to the relevant documentation
[x]  New and existing unit tests pass locally with my changes

Changes
Delete testingacc public hub datasets after tests

@farizrahman4u the function scoped tests were purposeful because the name of the dataset paths is the test name. the --keep-storage flag is used so you can go in and browse the outputs for all tests.
session scoped tests don't give us high enough granularity for debugging

I'm not sure if I have enough context to review this. I don't know whether the dataset deletion problem exists currently and if it does I don't know if it is actually being solved by this PR.

I'm not sure if I have enough context to review this. I don't know whether the dataset deletion problem exists currently and if it does I don't know if it is actually being solved by this PR.

@AbhinavTuli, the app looks like this now. I'm not sure if this pr solves the root problem, but we should get rid of this datasets.


Excluding foreign tables

I am trying to exclude foreign tables because I am getting a hypopg error when trying to create an index on them. However even if i pass them in to dexter using --exclude I get the same error.
For example:
dexter --pg-stat-statements -d mydb --exclude foo.bar --log-sql --log-level debug2
results in:
[sql] SELECT * FROM hypopg_create_index('CREATE INDEX ON "foo"."bar" ("column")')
/opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:539:in `exec_params': ERROR:  hypopg: "bar" is not a table or materialized view (PG::InternalError)
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:539:in `block in execute'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:535:in `synchronize'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:535:in `execute'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:604:in `create_hypothetical_index'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:598:in `block (2 levels) in create_hypothetical_indexes_helper'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:597:in `permutation'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:597:in `block in create_hypothetical_indexes_helper'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:595:in `each'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:595:in `create_hypothetical_indexes_helper'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:219:in `create_hypothetical_indexes'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:99:in `process_queries'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/indexer.rb:32:in `process_stat_statements'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/client.rb:27:in `perform'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/lib/dexter/client.rb:9:in `start'
	from /opt/dexter/vendor/bundle/ruby/3.1.0/gems/pgdexter-0.5.2/exe/dexter:7:in `<top (required)>'
	from /opt/dexter/bin/dexter:17:in `load'
	from /opt/dexter/bin/dexter:17:in `<main>'

I am currently running postgres 16 on ubuntu 22.04 any help would be greatly appreciated!

Hi @nobelsmith, thanks for reporting! I'm not able to reproduce the issue with --exclude, but fixed the error with foreign tables in the commit above.


Generated css

I have generated a falavor using https://minicss.org/flavors#build-your-own-flavor and now I have a  mini-custom.scss.
How am I supposed to make a css file out of this?

Your mini-custom.zip file doesn't contains a mini-custom.css and a mini-custom.min.css files a the root?

Well, I solved the configuration problem like this:

Download mini.css-master
Copy the src folder to my project's css folder.
Install Live Sass Compiler to my vscode
Live Sass compiler watches the changes which I make to files in mini folder and generates  output mini-default.css mini-nord.css and the rest.
Just link the desired output .css to my htmlpage.  Very handy!


"pod install" is running on every iOS build with plugins, even if nothing changed

$ cd dev/integration_tests/flutter_gallery
$ flutter build ios
...
Running pod install...                                           1,605ms

Run the same command again, and it will run pod install again even though it doesn't need to.  This adds an extra 1.6 seconds to every build.

_shouldRunPodInstall is returning true because the Podfile.lock timestamp is older than the Podfile.  I'm guessing the Podfile was migrated to a new tool format, which didn't change the Podfile.lock.
https://github.com/flutter/flutter/blob/c3d0f60407f4fe556a73f9bef495aac352d4595b/packages/flutter_tools/lib/src/macos/cocoapods.dart#L298-L311
touching the Podfile.lock after a pod install would probably be enough to fix this.


Git SCM not working after upgrade to 1.12.2

VSCode Version: Code 1.12.2 (19222cdc84ce72202478ba1cec5cb557b71163de, 2017-05-10T13:16:25.899Z)
OS Version: Linux x64 4.10.0-21-generic
Ubuntu Zesty 10.04 (debs: code 1.12.2-1494422229, git 1:2.11.0-2ubuntu0)
Extensions:

Extension
Author
Version

format-php
Kasik96
1.1.2

vscode-docker
PeterJausovec
0.0.14

cpptools
ms-vscode
0.11.0

bash-debug
rogalmic
0.0.7

Git SCM worked before upgrade to 1.12.2. Now SCM is not working with following errors reported:
$ code --verbose .
[1296:0518/185401.221294:ERROR:browser_main_loop.cc(272)] Gtk: Nie można odnaleźć modułu obsługującego motyw w module_path: "adwaita",
[1296:0518/185401.225961:ERROR:browser_main_loop.cc(272)] Gtk: Nie można odnaleźć modułu obsługującego motyw w module_path: "adwaita",
[main 18:54:01] Starting VS Code in verbose mode
[main 18:54:01] from: /usr/share/code/resources/app
[main 18:54:01] args: { _: [ '/home/slodki/src/moneymanagerex' ],
  help: false,
  h: false,
  version: false,
  v: false,
  wait: false,
  w: false,
  diff: false,
  d: false,
  goto: false,
  g: false,
  'new-window': false,
  n: false,
  'unity-launch': false,
  'reuse-window': false,
  r: false,
  performance: false,
  p: false,
  'prof-startup': false,
  verbose: true,
  logExtensionHostCommunication: false,
  'disable-extensions': false,
  disableExtensions: false,
  'list-extensions': false,
  'show-versions': false,
  nolazy: false }
[main 18:54:02] IPC#vscode-machineId
[main 18:54:03] IPC#vscode-workbenchLoaded
[1296:0518/185403.410550:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[1296:0518/185403.410616:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[1296:0518/185403.410645:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[1296:0518/185403.410659:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[1296:0518/185403.410676:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[1296:0518/185403.410689:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[1296:0518/185403.410712:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////usr/share/code/resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[...]

This error is repeated for each file in git repo.
Console inside Developers Tools is full of identical errors for each file in git repo (files inside .git dir are reported too):
[...]
[IPC Library: Watcher] Error: watch /home/slodki/src/moneymanagerex/build/msw-vc-2013e/copy_files.bat ENOSPC
(anonymous) @ ipc.cp.ts:152
[...]

#26808?

@slodki can you try follow these instructions to increase your watch limit? https://code.visualstudio.com/docs/setup/linux#_error-enospc

You are right - something ate all my inotify handles (maybe software updated in the meantime?). Now SCM in code works ok after increasing limit once again.
Doc says: "When you see this error..." - but user see no errors at all while only SCM is not working. So when inotify errors are detected code should notify user about problems with SCM.

To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed.
Thanks for your understanding. Happy coding!


App will not link against shiny in Android release config.

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[x] Android
[ ] UWP
[ ] watchOS
[ ] tvOS
[ ] Tizen
[ ] .NET Standard

Feature Library

[x] Core
[ ] BluetoothLE
[ ] Beacons
[ ] Locations
[ ] HTTP Transfers
[ ] Notifications
[ ] Sensors

Version of Library
Version of OS(s) listed above with issue
Steps to Reproduce

Use version of library since nullable reference types were added (before <IP_ADDRESS>4-beta).

Expected Behavior

App will link ok to shiny.

Actual Behavior

Android app does not link (it gets caught in a linking loop and never finishes).

This is not an issue with shiny itself but rather a xamarin.android issue, I'm just leaving a note here in case other people run into this issue.  I'm using an older version of shiny(<IP_ADDRESS>4-beta) until it is fixed.
Here is a link to the issue: https://github.com/xamarin/xamarin-android/issues/3852

I can't use newer versions with Xamarin Android. My app fails to initialize. It seems to be related to this bug!
Using (<IP_ADDRESS>4-beta) everything still works. Is there a fix coming?

@wagenheimer That error has absolutely nothing to do with this issue.  If you are having an issue, please open an issue with a proper test case  and  I'll look into it.

Seems to work for me now VS 16.5 has been released

I can confirm, that it works now!
-- Eddy

Thanks for confirming the fix everyone


Feature: Option to enable self-signed SSL certificates

Problem
The browser blocks unsafe connections. This is fine as default behaviour but really inconvenient when you are trying to debug a website that uses self-signed SSL certificates because it doesn't give you the option to do it anyway as most normal browsers do. (you can try it with this link)
Fix
After some research I found out that this can be fixed by adding the property ignoreHTTPSErrors: true to the object that is passed to the puppeteer.launch() method in the file /build/ext-src/browser.js at line: 35. (see the relevant documentation)
Request
This works fine if you want to get it to work at all cost but hardcoding it this way seems to be a very inelegant solution. I wonder if it would be possible for you to add an option in the extension settings to toggle this behaviour on and off. It doesn't appear to be a hard thing to implement but I don't have any expirience with making vscode extensions so i'm not sure how one would achive this.

I also have this issue


test: add tests tensor dtype serialization

Signed-off-by: Joan Fontanals Martinez<EMAIL_ADDRESS>Goals:
Test that serialization respects tensor dtype

fyi: @joschkabraun


total_*dyn_deposits and total_*dyn_deposits_scaled() naming off

Issue
The names of total_*dyn_deposits and total_*dyn_deposits_scaled() are probably actually backwards. Pure wei_values are what I would consider unscaled, whereas anything that is decimal(wei/m) has been scaled.
Proposed Implementation
Change names. Just a flip would work, but we might consider some alternative.

@ChihChengLiang thoughts?

I like in_wei


Load kernel from rootfs

When https://github.com/resin-os/meta-resin/pull/1153 is merged in meta-resin, the kernel will be available in the rootfs partition.
Load the kernel from the rootfs partition.
This PR will require the submodules to be updated to the rev that meta-resin is https://github.com/resin-os/meta-resin/pull/1153

merged into https://github.com/resin-os/resin-raspberrypi/pull/219


Support attribute-level dependencies on item collections

Detailed description
:warning: More of a proof of concept than anything real for now.
This adds support for queries like @items.where(kind: 'article'), which would return a collection of all items where the kind attribute is "article".
In behavior, this is nearly identical to @items.select { _1[:kind] == 'article' }, but is more friendly to the dependency tracker and outdatedness checker. For example:

This creates only a single dependency, onto the item collection, rather than individual dependencies for each item. This cuts down on the number of dependencies. A lower number of dependencies means the dependency is smaller, and can be loaded/stored more quickly. For large sites, with many thousands of items, this can make a significant difference.

This prevents items from being marked outdated if their kind attribute changes from something that isn’t "article" to something else that isn’t "article" either (e.g. from "note" to "thought"). This can reduce the number of redundant recompiles.

To do

[ ] Tests
[ ] Refactoring
[ ] Documentation
[ ] Feature flags

Related issues
n/a

Sounds great!! I use this kind of stuff all the time 😅
Very much appreciated improvement proposal 👍


Sebastian.p/orth dgp

Implementation of "Sparse Orthogonal Variational Inference for Gaussian Processes".
Created the following folders:
-- conditionals: needs a specialized form to account for the two different GPs that have to be summed g() and h() as in the paper.
--covariances: needed to compute Cvv and Cvf as in the paper. These covariances rely on the other set of inducing points.
--posteriors.py: different conditionals are needed here.
Currently some tests are failing. Will fix them asap.

cleaned up a bit, mypy still complains on quite a few things, but content wise good enough for a review

The covariances, conditionals and posteriors probably ought to go in GPflow instead.  Maybe we can split these out into a separate PR?

@hstojic @SebastianPopescu note how I've merged all the different model architecture builders. I've tried adding heteroskedastic likelihoods but at the moment some tests with this likelihood are failing, which I have explicitly marked as such.

@SebastianPopescu the PR is now failing on test coverage, mainly due to the untested GPflow customisations.
With a closer look, it seems there are components which have exact duplicates on GPflow, e.g. https://github.com/GPflow/GPflow/blob/develop/gpflow/kullback_leiblers.py
Why do we need to add them here?

provided some quick comments... not sure what to do about testing those conditionals, posteriors etc

I'm waiting for what @sc336 has to say, if he manages to move all this stuff to GPflow in https://github.com/GPflow/GPflow/pull/2027


iOS: Unable to set ACL's for files being uploaded to S3

Describe the bug
I am unable to set the ACL public-read from my iOS application while uploading a photo using Amplify.Storage.uploadData. This S3 bucket is an existing resource and therefor I cannot use the Amplify CLI to configure the bucket.
All images that are uploaded using the accessLevels guest public & private are un-viewable publicly.
Similarly our web client uses the S3 SDK and has an option to set the ACL during upload:
s3.upload({
          Key: filename,
          Body: file,
          ContentType: file.type,
          ACL: "public-read"
        })

Is there a way to obtain this result using the Amplify SDK? Or any other options I could try that don't involve changing permissions on the bucket?
Steps To Reproduce
Attempt to upload an image that requires a public ACL from the iOS Amplify SDK.

Expected behavior
I should be able to set the ACL of a file to 'public-read' or whatever the required permission is from the Amplify SDK.
Amplify Framework Version
1.19.2
Amplify Categories
Storage
Dependency manager
Swift PM
Swift version
5.2
CLI version
4.4
Xcode version
13.3
Is this a regression?
Yes
Device
iPhone 13 Simulator
iOS Version
iOS 13.2

@lawmicha I saw your response here but I think I need a more flexible solution in the long run. Is this something that's posible? https://github.com/aws-amplify/aws-sdk-ios/issues/2233

Any update on this? I noticed that v2.4.0 of the SDK (the latest version at this time) removes AWSS3PutObjectRequest so you can no longer use the escape hatch to solve this issue. Any recommendations @atierian @lawmicha?

Thanks for the example in https://github.com/aws-amplify/amplify-swift/issues/1625#issuecomment-1048004274 I believe this should live in the documentation under the escape hatch.
In terms of the feature request, this seems possible. One way is to pass it in AWSS3PluginOptions https://github.com/aws-amplify/amplify-swift/blob/main/AmplifyPlugins/Storage/Sources/AWSS3StoragePlugin/Configuration/AWSS3PluginOptions.swift#L32 since it's AWS specific.


Copy Paste Text-with-a-line-break.

If you copy-and-paste some text with a line break into a cell, for example,
"foo
bar",
only "foo" will be displayed, but the entire text will be saved to the file, including the enter.

Can you please provide screenshots that demonstrate this behavior?


fix syntax error

Changed Currently the Sky Engine assumes the entry point for your application is a main function is located inside a main.sky file at the root of the package to Currently the Sky Engine assumes the entry point for your application is a main function which is located inside a main.sky file at the root of the package.

Thank you very much for the pull request.  Unfortunately this repository is automatically generated from the mojo repository.  Furthermore the mojo repository is not yet able to accept pull requests (I'm working on it), but rather has as separate contribution process:
https://github.com/domokit/mojo/tree/master#contribute


Fix daynaport emulation regression and remove obsolete work-around (#1306)

Successfully tested by @benjamink.

I'd highly recommend testing this on a SE or older machine before merging. The "obsolete" work around was only needed for slower machines.

@akuker Do you know any user who could run this test?

@uweseimet  I have a Mac SE as well.  I'll see if this will work there later.

@benjamink Excellent! I will reset this PR to a draft for now.

Because the delay handling is not critical I am going to update the branch to only contain the actual fix. Regarding the delay I am going to create a separate ticket. If until the next release there is no use case (slow Mac) that requires the delay it should be removed. The comment in the sources does not mention slow Macs but sounds to me as if the Daynaport driver needs this delay. This is not necessarily the case, as the testing by @benjamink has shown. The work-around for 37 bytes (INQUIRY), on the other hand, is definitely needed, the latest tests and logs prove that. I will update the respective comment for one of the next PRs, so that it reflects the details on why this work-around is required.
@benjamink When testing with your SE, please do not check out the tip of the issue_1306 branch, but commit c46d3b71 insteads.

I think I may need to come up with a new disk image for my Mac SE to work at all.  I've been trying to boot my System 7.5.3 image that I've been using with my Performa 475 but it just freezes on the boot screen.  I can boot up a System 6.0.8 image just fine but it doesn't have Daynaport drivers or anything like that installed yet.  I'll work on this & see what I can come up with but it won't be right away.
Unless someone else has a pre-configured System 7.0.1 or something I could use???

@benjamink Just take your time. The respective test can be done as part of a new ticket, which I will create (also see my comment above). As soon as I have set up the ticket (tomorrow) I will point it out to you, and any conversation can then happen as part of this new ticket.

@uweseimet SGTM.
How about we aim for 11/11 (Saturday) for tagging & prepping the next release? I expect to have the time to spend on the image generation etc. on that day.

@uweseimet I built c46d3b71545fd941db276be887f81b61a532237a & tried it on my Mac SE but it just freezes during boot.  I built a current copy of develop (v23.10.1) & it works great on the Mac SE.  So it looks like the delays are indeed important for older computers.

@benjamink In this case we will keep them, of course, but the current code location setting up this delay is not ideal, and there are other delays that also need verification. Would you be willing to help with improving that? There is already an existing ticket (#1287) for addressing this. The goal is verify which delay is actually needed, whether there is a better way to address the problem, and to add a comment to the sources explaining the reason for any delay that is not covered by the SCSI specification in detail. As we can see in #1098 some of these delays can actually cause compatibility issues.

Yes, I can test.  I moved the SE upstairs in anticipation of running more tests already 🙂

@benjamink :-) I really appreciate your help. Let's continue this conversation in #1287, which is the respective ticket.


Table borders

Hi, I recently came across this app - and it is really nice!
I just checked this markdown file (from the docs of another Markdown editor for PC) in your app (on Android) and found that it would be helpful to have proper table borders.
With this being fixed, I will use this app for writing/viewing my documents for studying. Thank you for this feature-rich app with generous capabilities of managing files without a proprietary sync server or closed-source data format.

Added in https://github.com/redsolver/noteless/releases/tag/v1.2.1 :tada:

Added in https://github.com/redsolver/noteless/releases/tag/v1.2.1 🎉

Looks great, thank you for instantly working on it! 🎉 👍
Closing this.


helm: Add possibility to configure resource requests/limits

Signed-off-by: Julien DOCHE<EMAIL_ADDRESS>

@y2kenny Could you take a quick look at this please ?


SWARM-1014 - Quiet down boot logging

Motivation
Too much useless output when booting.
Modifications
Silence the error-context message by making sure the management fraction
has the error context.
Silence some messages we see in our own testsuite due to @DefaultDeployment
scraping cdi.jar.  This is accopmlished by changing the package name of the
test itself.
Rev the fraction-plugin also, to remove detect classes from the fractions.
Result
Yet quieter logs.

[X] Have you followed the guidelines in our Contributing document?
[X] Have you created a JIRA and used it in the commit message?
[X] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[X] Have you built the project locally prior to submission with mvn clean install?

Retest this please


l2, udpn: Add ipv6 lla gateway field to the ovn pod annotation

📑 Description

For primary UDN layer2 the proper IPv6 gateway that should be configured
with received router advertisements is the one from the local GR IPv6
LLA, this change add field to the ovn pod annotations with that
information so it can be consumed by follow up PRs that will ensure
remove GRs are ignore as layer2 ipv6 gateways.
This is related to the following PRs that remove multipath ipv6 gateway for l2 primary UDNs:
https://github.com/ovn-kubernetes/ovn-kubernetes/pull/4852
https://github.com/ovn-kubernetes/ovn-kubernetes/pull/4847
Based on https://github.com/ovn-kubernetes/ovn-kubernetes/pull/4866, just finalizing it.
Thanks @qinqon
Fixes #
Additional Information for reviewers

✅ Checks

[ ] My code requires changes to the documentation
[ ] if so, I have updated the documentation as required
[x] My code requires tests
[x] if so, I have added and/or updated the tests as required
[ ] All the tests have passed in the CI

How to verify it

previous error was fixed, now it is a known flake
https://github.com/ovn-kubernetes/ovn-kubernetes/issues/4721
Note: maybe would be best to allow running the lanes (or at least some of them), during development, even if UT is failing (using some flag or a chatop directly to build and trigger them)

as far as i can tell the failures aren't related to the PR
https://github.com/ovn-kubernetes/ovn-kubernetes/actions/runs/12250911507/job/34175635923?pr=4878
https://github.com/ovn-kubernetes/ovn-kubernetes/actions/runs/12250911507/job/34175638991?pr=4878
https://github.com/ovn-kubernetes/ovn-kubernetes/actions/runs/12250911507/job/34175644667?pr=4878
but best to rerun / have another opinion please

@qinqon @maiqueb
basically ready for review please, rerunning tests, just to make sure the above aren't related

https://github.com/ovn-kubernetes/ovn-kubernetes/actions/runs/12250911507/job/34175644667?pr=4878
Might be real failure, because i saw it fail twice on this PR and the follow-up

https://github.com/ovn-kubernetes/ovn-kubernetes/actions/runs/12250911507/job/34175644667?pr=4878 Might be real failure, because i saw it fail twice on this PR and the follow-up (#4852)
Summarizing 1 Failure:
  [FAIL] Network Segmentation: services on a user defined primary network should be reachable through their cluster IP and node port [It] L3 primary UDN, cluster-networked pods, NodePort service
  /home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/network_segmentation_services.go:422

There is a flaky issue for this one.

https://github.com/ovn-kubernetes/ovn-kubernetes/actions/runs/12250911507/job/34175644667?pr=4878 Might be real failure, because i saw it fail twice on this PR and the follow-up (#4852)
Summarizing 1 Failure:
  [FAIL] Network Segmentation: services on a user defined primary network should be reachable through their cluster IP and node port [It] L3 primary UDN, cluster-networked pods, NodePort service
  /home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/network_segmentation_services.go:422

There is a flaky issue for this one.

Thanks, i didn't find an issue searching "L3 primary UDN, cluster-networked pods, NodePort service", might worth to open one ?
It fails in pretty high rate, imho would be nice to consider Quarantine or escalation sometimes for those ?

Thanks as we spoke this is the flake https://github.com/ovn-kubernetes/ovn-kubernetes/issues/4829

rebased

Thanks
Removed non required leftover mock

@oshoval needs to be rebased.

rebased only

Thanks
Addressed / answered comments

failures seems unrelated / known flaky

Thanks
@maiqueb you might also want to take another look please ?

https://github.com/ovn-kubernetes/ovn-kubernetes/actions/runs/12480204864/job/34831434078?pr=4878
didnt run fully, need to rerun maybe


libsvmsharp-64bit

hello every one..... please can any one help me in use the "libsvmsharp-64bit" in satellite image classification and explain me the step by step ..... thanks for your answer previously
best regards

For technical details like how to use libsvm or more basically how to use support vector machines, you may want to check official libsvm page.


generated table attributes not draggable at first

After creating a table through a transformation, the table's attributes cannot be dragged around to reorder them, until another transformation takes place, at which point they become draggable (but not for the latest transformed table).

After further investigating, I am pretty sure this is a bug on the CODAP end (it happens even with simple API requests to create data contexts, outside any involvement of our transformations/updating/etc).
I have reported it here.

Fixed here.


Can not log in

Existing Issues

[X] I have searched for existing issues, this is not a duplicate.

Unmodded Twitch

[x] I have checked and this issue only occurs using bttv-android and not with the unmodded Twitch App

What happened?
I recommended the app to someone, who then tried to log in but couldn't.
After logging out myself on the app and trying to log back in, I got the message
"Oops! We encountered an unexpected error. Please try again."
bttv-android version
v0.35.1-beta
android version
11
device
Moto G 10
Anything else?
I can confirm that the exact same logins work on the unmodded Twitch App and in my browser.
I use a password manager, so errors in typing are not a possible.

I'm having the same issue.

same here, even with the old version still can't login

Turns out the passport.twitch.tv backend started failing integrity checks (I think this has something to do with rate-limiting) for "invalid" User-Agents.
This is a marvelously bad idea, as it is easy to circumvent and makes it impossible for other clients to identify themselves towards the server.
It also cost me my morning trying to find this out. Thank you Twitch!
Fix will be released probably tomorrow or the day after as I'm very short on time right now.

It happened to me too....
This app needs to be patched soon.

It's already patched! You maybe need to manually download the new version, I'm not sure if the banner shows up when the user is not signed in.


Add delaunay_triangulation and simplify functions

please look at the CI failure and resolve the merge conflicts.

alright, think they should be fixed


Document or add GitHub action to build framework binaries

Hi,
Thanks for maintaining this project. I think it has many useful concepts/helpers.
I'm using the code examples on the book Unit testing by example, and I'm getting a compiler error using Xcode 13 beta (I guess on Xcode 12.5 it would be reproducible, as latest binaries provided are for Xcode 12.3).
This is the error log:
Module compiled with Swift 5.2 cannot be imported by the Swift 5.5 compiler:
~/Developer/ios/unit-testing-by-example-code/Alert/AlertTests/ViewControllerPresentationSpy.framework/Modules/ViewControllerPresentationSpy.swiftmodule/x86_64.swiftmodule

What I miss are the instructions that I guess you have used to build the frameworks for the Prebuild binaries.
Have you also thought of adding a GitHub action for that, in order for the instructions to be always updated?
Regards

I just added instructions to the bottom of the README for how to build on your own.


List of environment variables for AMC

Hi all,
Per this thread: https://www.filebot.net/forums/viewtopic.php?f=13&t=12684&p=55064#p55064
I'm using this container for AMC and I'd like to add additional environment variables to control notifications via Pushbullet and also to handle archives (unrar + delete leftover files). Are these variables documented anywhere like the table on the https://github.com/jlesage/docker-filebot#environment-variables page?
Any help or advice would be great. Thanks!

Alternatively, do you have any guides on how to pass other AMC commands like unrar behaviour and Pushbullet notification to the container?

Sorry for the late answer.
Do you already know how to achieve that with AMC?
Variables exists for basic stuff, but else there is the AMC_CUSTOM_OPTIONS variable that allows you to do anything you want.

That's okay! I don't know how to do that, sorry. If I set AMC_CUSTOM_OPTIONS in the variables section in the container set up, what format should I use for custom options? Say if I wanted to enable Pushbullet? Once I know the syntax to use I'm happy to have a crack at it. Thanks for your help!

For the archive extraction, I think that AMC will do it automatically.
The supported AMC options are documented here: https://www.filebot.net/forums/viewtopic.php?t=215.  For Pushbullet, the option is --def pushbullet=apikey.  This is what you would put as the content of the AMC_CUSTOM_OPTIONS variable.

Thanks! This worked perfectly for Pushbullet.


Add Maya Protocol

Description
Add support for Maya Protocol chains.
How to test
Run C++, Swift, Kotlin tests
Types of changes

Checklist

[X] Create pull request as draft initially, unless its complete.
[X] Add tests to cover changes as needed.
[X] Update documentation as needed.
[X] If there is a related Issue, mention it in the description.

If you're adding a new blockchain

[X] I have read the guidelines for adding a new blockchain.

Related to this issue https://github.com/trustwallet/wallet-core/issues/3160

Hi @BitolMaya, could you please explain what parts are different between MayaSWAP and THORSwap?
It would be great if you reuse THORSwap existing code my making required changes there.

Hi @BitolMaya, could you please explain what parts are different between MayaSWAP and THORSwap? It would be great if you reuse THORSwap existing code my making required changes there.

Hello @satoshiotomakan, they're actually the same, do you recommend to delete the MAYASwap files and add tests toTHORSwap files relative to MAYAChain?

Yes please, we would like to avoid as much code duplication as possible, also the blockchain type of maya could be Thorchain, it's exactly the same scheme of signature - let's avoid code duplication as much as possible.

@satoshiotomakan because the SWAP feature could be use by any chain (MAYA or THOR) but the differences, like which external chains are available, could cause conflicts what do you think if we have our own Swap.cpp file instead of modifying THORChains??

Hi @BitolMaya, I think there should be a workaround. For example, you can pass supported chains as an array.
If you add your MAYASwap's specific Swap.cpp, then I guess there will be a duplicate of the TWTHORChainSwapBuildSwap FFI function.

because the SWAP feature could be use by any chain (MAYA or THOR) but the differences, like which external chains are available, could cause conflicts what do you think if we have our own Swap.cpp file instead of modifying THORChains??

Could you please explain what is a use case of the MAYASwap, UX, how an end-user app should decide which protocol it should use? How an end-user app should let WalletCore know which protocol we need to use (THORSwap or MAYASwap)?

My approach was to create the new field mfromChain. This because, for example we could want to SWAP BTC -> ETH and that is possible on both THORChain and MAYAChain. To know in the code which chain we should used I introduced mfromChain. Maybe we could add in the frontend or somewhere to set that field when we want to SWAP some asset in order to differentiate which chain to use in the Swap.cpp file.

@BitolMaya sorry for the late answer.
mfromChain is available internally only, you can find all properties that the end-user apps access: THORChainSwap.proto.

To know in the code which chain we should used I introduced mfromChain

If I'm not mistaken, MAYASwap and THORSwap only differ in the list of supported blockchains, e.g MAYASwap supports MAYA chain, and vault_address.
vault_address is configurable on the end-user app side. So if you need to swap BTC -> ETH, it's enough to only set the proper vault_address (please correct me if I'm wrong).
Thus, the only changes need to be done in Wallet Core is to add support for MAYA chain.
What do you think @BitolMaya?

THORChainSwap.proto

Sorry for the late response, I think that will work. Let me implement it that way and then I will come back to you.


libdislocator, optional huge pages support.

Nice addition, thanks.
Where is the definition of USEHUGEPAGE?
mmap with huge pages can fail, so we should do a regular mmap as fall back.
buf = mmap(NULL, LENGTH, PROTECTION,
#ifdef MAP_HUGETLB
           MAP_HUGETLB |
#endif
           MAP_PRIVATE | MAP_ANONYMOUS,
           0, 0);
#ifdef MAP_HUGETLB
  if (buf == MAP_FAILED) {
    // try again without huge pages:
    buf = mmap(NULL, LENGTH, PROTECTION,
               MAP_PRIVATE | MAP_ANONYMOUS, 0, 0);
  };
#endif
if (buf == MAP_FAILED) {
  ...
}


README: add more limitation about usb device [CI SKIP]

Just revise some words.

I find out that rebooting sometime makes this failed, it's not always.
For example, if usb device is /002/002 at the first time, it won't change after rebooting. But, if we already re-plugged in the usb device one time to lead the path change (it might be 002/003 at that moment), then rebooting will reset the path to /002/002.


the trained result

Hi Patrik,
      //regressors.hpp:345
   bool learn(cv::Mat data, cv::Mat labels) override
   {
   	cv::Mat x = solver.solve(data, labels, regulariser);
   	this->x = x;
   	return true; // see todo above
   };

in the paper,we need to learn the $R_k,B_k$, but the solver  return only  a Mat, how to understand the differnce?
Thanks!

Hi @oftenliu,
The $B_k$ is the bias, and it is appended to the data matrix as an additional row (or column, forgot which one it is in the code). If you follow the code, you'll see it. It's a standard method when doing linear regression.

oh, i‘m  clear now, and i have some other questiones about face aligmnet, may i send them to you by email?  my email is<EMAIL_ADDRESS>would appreciate it very much if you could help me

If it is relevant to this repository and the actual algorithm, please post it here on the GitHub issues. However, the GitHub issues are for issues or unclarity about the code here, and not for face alignment or beginner questions. It is very likely those would not be answered. You would probably be much better off posting your questions to a more appropriate website like StackExchange (computer vision sub-page or something like that), /r/computervision, or something along those lines.

oh!  ok，Patrick, thank you  very much .
another question, i  train the sdm model on the ibug-lfpw, ibug, ibug-afw, 300-W, and ibug-helen-tr, when training , i use four regressor and your mean file , but the finnal residual is 2.1 is right??

I don't remember the magnitude of the final residual values, but it's best if you just test the resulting models on some standardised landmark detection benchmark.


chore: set crates repository url

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 86.79%. Comparing base (c7ed156) to head (42b3e03).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   86.79%   86.79%
=======================================
  Files           5        5
  Lines         780      780
=======================================
  Hits          677      677
  Misses        103      103

Flag
Coverage Δ

integration
87.80% <ø> (ø)

unit
0.00% <ø> (ø)

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

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


update npm package

Just leaving a note here, since we changed the name to webtorrent-desktop we'll need to update https://www.npmjs.com/package/webtorrent-app as well.

Done: https://www.npmjs.com/package/webtorrent-desktop


Expose SSE retry time updates via the public API

Issue #5471 was closed with the recommendation to reconnect to SSE streams in the application layer.
It would be helpful to expose the retry times in retry fields from the event stream, so that any reconnection attempts in a higher layer could respect the latest retry time if desired.
Currently, the retry times are parsed but they remain in the internal API only, terminating here:
https://github.com/square/okhttp/blob/aad8a1420d8f22a35138b92d7ecc14efc96155fe/okhttp-sse/src/main/java/okhttp3/internal/sse/RealEventSource.kt#L105

Yep, this seems like a valid part of the API.  Exposed in other frameworks like https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/http/codec/ServerSentEvent.java
And as you say, web EventSource implements retry observing that. https://html.spec.whatwg.org/multipage/server-sent-events.html#event-stream-interpretation
@swankjesse @JakeWharton any objection to exposing?  It would allow building a correct retrying implementation on top.

Let's expose. We don't support automatic retry so we need to surface this to the caller.


Updated CONTRIBUTING.md

Signed-off-by: Chandra-Sekhar-Bala<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Verification

Hey, @GiedriusS I am new to this, can you please help me?

Hi, thank you. If you could check the build that failed. Most likely you need to run the make docs command in the repository. You can use make help to see all the commands and what they do. There is probably some line ending /white space somewhere that needs to be fixed. The docs check fixes that.


Low contrast on the toggle buttons

Issue Description:
The low contrast on the toggle buttons in the Settings modal does not meet WCAG requirements. The toggle buttons in the "off" state do not have sufficient contrast for non-text elements. WCAG requires a minimum contrast of 3:1, but the contrast ratio is currently about 1.3:1. Since the buttons are not disabled but simply "off," they should meet the requirement for better accessibility. Low-vision users might find it difficult to identify and use the controls. This issue extends to other toggle buttons and some sliders in the application.
related to #4163
WCAG Criteria:
1.4.11 Non-text Contrast - AA
Screenshot:

Notes:
This issue also occurs on other toggle buttons and some sliders across the application.
Adding an outline to the toggle button or the entire control should be sufficient to meet the success criteria.
For example:

Bro, I see that you brought up a bunch of a11y standards, involving issues like focus and contrast. If I were the repo author, I’d be super annoyed—you're nitpicking too much. Plus, the interface lost some aesthetics because of the contrast requirements. I have to commend the author for being very responsible, though, because no one is actually required to follow any so-called WCGA criteria.

@SailFlorve I understand your concerns but I am working closely with @derekjackson-das to improve accessibility and they are doing a huge service in pointing these issues out. It is my intention to make LibreChat the most accessible AI chat app there is, because as you said, there is no strict requirement to do this and Claude.ai and ChatGPT have these shortcomings. This ultimately aligns with the mission of LibreChat to bring “Every AI for Everyone.”
I understand the concern for aesthetics but I think we’ve made some improvements in this regard. If there’s anything specific about the aesthetics you feel has changed negatively, please let me know. I personally am still learning how to make interfaces truly accessible and WCAG compliant and we don’t have to completely compromise on style in the process.

I'm worried that this might introduce a huge amount of extra complexity, bring in bugs, and potentially take a long time to troubleshoot and fix a11y issues. But you're right, it's truly meaningful for LibreChat to become the most a11y-friendly chat application. I really appreciate your efforts.

I understand SailFlorve's perspective, but I want to emphasize the critical importance of accessibility in our project. Before I fully learned a11y principles, I made mistakes like not using aria-labels, which caused significant issues for people with visual impairments or those who can't see at all
As we continue to redesign and restyle LibreChat step-by-step, we sometimes overlook these crucial aspects. For instance, the recent switch style issue was an unintended consequence of the settings UI update made by me
@danny-avila, perhaps we could consider implementing an a11y-focused theme? It could function as a toggle, similar to other themes, but specifically tailored for accessibility. This approach might help balance the needs of users who find certain a11y features visually distracting with those who rely on these features for usability
I understand that some users might find elements like focus rings annoying or feel that certain UI components are overly prominent. However, these features are essential for many users. Our goal is to make LibreChat accessible to everyone, and we're committed to finding solutions that work for all users
@SailFlorve, I encourage you to see this as an opportunity for UI improvement. Many a11y enhancements often lead to better overall design and user experience
We're dedicated to addressing these issues and welcome further suggestions or feedback from the community. Your input helps us create a more inclusive and user-friendly experience for all our users, regardless of their abilities or preferences. So, if you have some notes regarding UI, tell us here or on Discord


OpenAL Error 40963 Invalid Value when creating 256 sounds

Not sure if this was submitted or if this is even a cAudio bug but I'm having trouble creating a large number of audio sources.
I essentially have a loop that calls cAudioManager::create repeatedly and it always crashes on sound #256
I'm passing the same filename and a different name at each iteration. I'm passing in false for stream. Code:
IAudioSource* sources[512];
const char fn = "myFile.ogg";
for (int i = 0; i < 512; i++)
{
    std::stringstream n;
    n << "Sound " << i;
    sources[i] = mgr->create(n.str().c_str(), fn, false);
}

I traced the execution and it seems to to be an openal error. Error code 40963. The error string is "Invalid Value". Seems like alGenSources in cAudioSource.cpp (line 51) is what is setting the error state as the state variable was true prior to the checkError() call that comes after the alGenSources call. Any ideas what's up?
I'm running on a develop build of cAudio from commit 86548b947753ec7601f89a5812c2bdb8f9dacdd9

The main issue i could see coming up is the fact that openal is limited to only having 256 active sound sources. If you do not destroy any sound sources you will use all the hardware and virtual sources available to your device.

Ahhh I didn't realize that this was a limitation. Alright no problem. Doesn't seem like there's much that you guys can do on your side then, yeah?

Nope we do the best we can right now. If you need that many sources just check to see if a cAudioSource is done playing if it is then drop the cAudioSoundSource and it will free up the openal sound source. Ive thought about making it to where a sound source is only used while a audio source is playing however currently i do not have the free time it would take to implement this.

I am going to close this issue for now and add it to my todo list. If you have any other issues or suggestions let me know.

Yeah no problem. We actually built a system w/ the same idea as what you're suggesting on top of cAudio so for now everything should be good, I hope :)

Awesome glad you found a way around it. Although i am interested on what you are making that needs 256+ sound sources.

Well at the time we were simply stress testing the system to expose bugs and this came up. We're writing a game and using cAudio for the audio interface so you guys have been of much help to us! I don't think we'll be needing to play 256 sounds concurrently at any time soon :)


Make windows build use Anaconda + update macOS build

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #xyz

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?
This PR disables the pure Python OSGeo4W approach of installing dependencies to using Anaconda binaries for the Windows build. This build has been failing due to the particularities of installing/managing windows DLLs. If these dependencies are eventually removed, the pure Python Windows build would be good to re-enable.

Does this PR introduce a breaking change?
No.

Other information:
Homebrew (macOS) has finally changed its default installed Python from 2.7 to 3.8. The build is now configured to use Python3.8 to run its tests.

Pull Request Test Coverage Report for Build 1941

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 77.421%

Totals

Change from base Build 1939:
0.0%

Covered Lines:
2654

Relevant Lines:
3428

💛  - Coveralls


Bug: Created a group, and appears in both inbox and requests

Describe the bug
Created a group, and it appears in both the inbox and requests/suspected spam, even though I'm the super admin and group creator. It also shows the option to Decline/Join this group on the conversation screen.
Expected behavior
A recently created group should appear only in the inbox and should not show the Decline/Join option (auto consent on group creation).
Steps to reproduce the bug

This isn't an inbox triage bug, those are two different conversations, closing.


Update install instructions.

These README changes won't be valid until #129 is merged and python3-rosdoc2 is available in the ROS repositories.
📜 Rendered

FYI @rkent this is the last change I have planned for the 0.2.0 release to the ROS apt repositories and PyPI. I don't think that this PR needs to be in the release per se. But once the package is available I'd like to merge this.

rosdoc2 0.2.1 is now available in the ROS repositories.


added viewers from OceanDataLab

@mikrup Is the coverage on these viewers going to increase?

@j08lue If you mean that some products seem to have gaps over lands, so I noticed that most of these portals are focused only on open water areas only and presents only frames which include at least partially open water.
BTW I'm not involved into these portals so my knowledge is limited to information which I discover on this website: link, I just discovered them today

There is an information on some of the platforms:
"We only process limited time periods and geographical zones for each products. If you need more, let us know."

Thank you for this PR @mikrup and please excuse my belated response. It's merged into the list now.


Added EnforaEncoder tested on 2818

Hi
wanted to share with you this implementation of the EnforeEncoder, tested and working on 2818.
It was implemented following documentation on http://documentation.nvtl.com/board/download/file.php?id=221, on TCP protocol
Hope you find it useful for others.

Merged, thanks.

thanks to you


Docker environments and other improvements

Apologies in advance for a massive diff. This change required a pretty massive refactoring of the project so I took this opportunity to clean up some things.
Below is the overview of the changes.
Dockerize everything
The pipeline can now be built and run in a docker container. This is achieved by sharing /var/docker.sock into the container to allow redirecting any docker CLI commands to the host.
I added the pipeline to the docker-compose too and as a result the entire project can be now started (locally) with a single make start-development.
Introduce development and production environments
The ./environments folder contains docker-compose files for the development and production deployments. They can have different configurations and different services.
The development environment runs locally and automatically applies database migrations. It works with a local git repository that should allow for very easy testing.
The production environment requires migrations to be run by manually. This is intentional to avoid any risky automation. And of course, the pipeline runs in the github_app mode.
There are .env files for both the development and production environments. This should make it easy for us to set secrets and custom execution options.
Improve logging
When running the pipeline with --verbosity=debug the whole universe prints debug messages about the everything that's happening in the app (it is very very noisy). Our logging module now filters out third-party sources and applies the warning level to them even if your app is in the debug verbosity.
Add references to build and run job ids
This can be later queried by the frontend to generate links to the logs page. This change is not related to docker but I wanted to test the migrations in the docker-compose context so adding this made things easier.
Change the base image from ocurrent/opam to ocaml/opam
Related to https://github.com/ocurrent/current-bench/issues/15. I thought we had made this change already, but maybe we forgot.
Add HACKING.md
With instructions on how to configure and start the development environment. Any feedback on this is very appreciated.
Add a repo for local testing
This change ensures that we can have a reproducible testing repo within current-bench itself (more details in HACKING.md).
Remove unused code in backend
Removes: the old Makefile, the old frontend, systemd init files, the old init sql files and unused utils.
Add wait-for script
It is a common workaround to use "wait-for" scripts that await for a docker compose service to start before starting another service. More info: https://docs.docker.com/compose/startup-order/
I added a wait-for script to be used with the migrations service. We want to make sure that the pg database is ready before running the migrations.

I didn't read the code but followed the HACKING.md instructions and everything went fine. That's very nice to have all this stuff dockerized, amazing work!
I only have 2 suggestions:

Might be worth adding *.env in .gitignore so that when people create their env file from the template, it doesn't get mistakenly committed.
When I started the frontend, I was a bit surprised to actually see data from http://autumn.ocamllabs.io. That would be nice to grab the backend URL from env (it's currently hardcoded in the code). Vite allows reading .env files but from what I understand, they should be located at the root of the project (within frontend/ in our case). Maybe we could copy (and rename) the env file e.g development.env within the frontend folder during one of the docker steps?  Not sure though if that's a good idea 😅

Thanks for the review, @gs0510 and @tatchi!
I think I've addressed all of the comments except https://github.com/ocurrent/current-bench/pull/55#discussion_r595056498
If one of you could try using "/usr/bin/setarch"; "x86_64"; "--addr-no-randomize"; "make"; "bench"; for Docker.pread on an amd64 machine, I would appreciate that.

@tatchi regarding your second point: https://github.com/ocurrent/current-bench/issues/64. Let's add this in a separate PR, if that's ok.

I tried setarch and it works! LGTM! :)


Feature/right click

Closing this PR, opened another one here https://github.com/Outerbridgeio/Outerbridge/pull/168 specific to right click functionality


[CMS-630] Create a command in conversion tool to validate .gitignore

Example

Before: .gitignore file either does not exist or is empty
After: .gitignore file contents:

# Added by Terminus Conversion Tools Plugin.
/vendor
/web/core
/web/modules/composer/*
/web/themes/composer/*
!/web/themes/composer/a_committed_file.txt

Commits listing:

Looks good.
As a form of AC review, could you show some before & after .gitignore files & corresponding command output from a couple of different scenarios, and put it either in this PR or in the Jira story?

Update PR description with an extensive example of the command execution