up_squared：the test shows pass in the twister.log it but does not seem to finish

Describe the bug
The test shows pass in the twister.log but it does not seem to finish, according to observation the twister log is not complete.
Take tests/posix/common as an example.
To Reproduce
Steps to reproduce the behavior:

source zephyr-env.sh
twister -p up_squared --device-testing --device-serial $serial_name -T tests/posix/common/ --west-flash=$HOME/$USER/up_squared_efi.sh -vv
See error
or
2.west build -p always -b up_squared tests/posix/common/
3.screen /dev/ttyUP2 115200
4.west flash $HOME/$USER/up_squared_efi.sh
5.See error

Expected behavior
The test pass both in twister log and in daily report.
Impact
The test shows pass in the twister log but it does not seem to finish.
Logs and console output
Version 2.18.1263. Copyright (C) 2018 American Megatrends, Inc.
Press <DEL> or <ESC> to enter setup.

DEBUG   - DEVICE: >>Checking Media Presence......
DEBUG   - DEVICE: >>No Media Present......

DEBUG   - DEVICE: >>Checking Media Presence......
DEBUG   - DEVICE: >>Media Present......
DEBUG   - DEVICE: >>Start PXE over IPv4.
DEBUG   - DEVICE: Station IP address is <IP_ADDRESS>
DEBUG   - DEVICE:
DEBUG   - DEVICE: Server IP address is <IP_ADDRESS>
DEBUG   - DEVICE: NBP filename is up_squared/zephyr.efi
DEBUG   - DEVICE: NBP filesize is 2246389 Bytes

DEBUG   - DEVICE: >>Checking Media Presence......
DEBUG   - DEVICE: >>Media Present......
DEBUG   - DEVICE: Downloading NBP file...
DEBUG   - DEVICE:
DEBUG   - DEVICE: Succeed to download NBP file.
DEBUG   - DEVICE: *** Zephyr EFI Loader ***
DEBUG   - DEVICE: RSDP found at 0x79c34000
DEBUG   - DEVICE: Zeroing 5075584 bytes of memory at 0x117000
DEBUG   - DEVICE: Copying 32768 data bytes to 0x1000 from image offset
DEBUG   - DEVICE: Copying 94208 data bytes to 0x100000 from image offset 32768
DEBUG   - DEVICE: Copying 2112896 data bytes to 0x5ee280 from image offset 126976
DEBUG   - DEVICE: Jumping to Entry Point: 0x1137 (48 31 c0 48 31 d2 48)
DEBUG   - DEVICE: Running TESTSUITE posix_apis
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_pthread_execution
DEBUG   - DEVICE: Thread 0 starting with scheduling policy 0 & priority 15
DEBUG   - DEVICE: Thread 1 starting with scheduling policy 0 & priority 15
DEBUG   - DEVICE: Thread 2 starting with scheduling policy 0 & priority 15
DEBUG   - DEVICE: Bounce test OK
DEBUG   - DEVICE: Barrier test OK
DEBUG   - DEVICE: PASS - test_posix_pthread_execution in 0.521 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_pthread_error_condition
DEBUG   - DEVICE: PASS - test_posix_pthread_error_condition in 0.1 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_pthread_termination
DEBUG   - DEVICE: Thread 0 starting with a priority of 4
DEBUG   - DEVICE: Cancelling thread 0
DEBUG   - DEVICE: Thread 1 starting with a priority of 3
DEBUG   - DEVICE: Cancelling thread 1
DEBUG   - DEVICE: Thread 1 could not be cancelled
DEBUG   - DEVICE: Thread 2 starting with a priority of 2
DEBUG   - DEVICE: Cancelling thread 2
DEBUG   - DEVICE: Thread 3 starting with a priority of 1
DEBUG   - DEVICE: Cancelling thread 3
DEBUG   - DEVICE: Thread 3 could not be cancelled
DEBUG   - DEVICE: PASS - test_posix_pthread_termination in 1.16 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_multiple_threads_single_key
DEBUG   - DEVICE:
DEBUG   - DEVICE: Different threads set different values to same key:
DEBUG   - DEVICE: thread 0: set value = 6214384 and retrieved value = 6214384
DEBUG   - DEVICE: thread 1: set value = 6214832 and retrieved value = 6214832
DEBUG   - DEVICE:
DEBUG   - DEVICE: PASS - test_posix_multiple_threads_single_key in 0.18 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_single_thread_multiple_keys
DEBUG   - DEVICE:
DEBUG   - DEVICE: Single thread associates its value with different keys:
DEBUG   - DEVICE: key 0: set value = 6215232 and retrieved value = 6215232
DEBUG   - DEVICE: key 1: set value = 6215232 and retrieved value = 6215232
DEBUG   - DEVICE:
DEBUG   - DEVICE: PASS - test_posix_single_thread_multiple_keys in 0.18 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_thread_attr_stacksize
DEBUG   - DEVICE: PASS - test_posix_thread_attr_stacksize in 0.1 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_clock
DEBUG   - DEVICE: POSIX clock APIs
DEBUG   - DEVICE: POSIX clock APIs test done
DEBUG   - DEVICE: PASS - test_posix_clock in 2.5 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_semaphore
DEBUG   - DEVICE: PASS - test_posix_semaphore in 2.305 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_normal_mutex
DEBUG   - DEVICE: mutex lock is taken
DEBUG   - DEVICE: PASS - test_posix_normal_mutex in 0.203 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_recursive_mutex
DEBUG   - DEVICE: recursive mutex lock is taken
DEBUG   - DEVICE: PASS - test_posix_recursive_mutex in 0.4 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_mqueue
DEBUG   - DEVICE: PASS - test_posix_mqueue in 0.11 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_realtime
DEBUG   - DEVICE: PASS - test_posix_realtime in 1.802 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_timer
DEBUG   - DEVICE: POSIX timer test
DEBUG   - DEVICE: Timer fires every 0 secs and  100000000 nsecs
DEBUG   - DEVICE: Time remaining to fire 0 secs and  899000000 nsecs
DEBUG   - DEVICE: Handler Signal value :20 for 1 times
DEBUG   - DEVICE: Handler Signal value :20 for 2 times
DEBUG   - DEVICE: Handler Signal value :20 for 3 times
DEBUG   - DEVICE: Handler Signal value :20 for 4 times
DEBUG   - DEVICE: Handler Signal value :20 for 5 times
DEBUG   - DEVICE: Handler Signal value :20 for 6 times
DEBUG   - DEVICE: Handler Signal value :20 for 7 times
DEBUG   - DEVICE: Handler Signal value :20 for 8 times
DEBUG   - DEVICE: Handler Signal value :20 for 9 times
DEBUG   - DEVICE: Handler Signal value :20 for 10 times
DEBUG   - DEVICE: Handler Signal value :20 for 11 times
DEBUG   - DEVICE: Handler Signal value :20 for 12 times
DEBUG   - DEVICE: PASS - test_posix_timer in 2.112 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_posix_rw_lock
DEBUG   - DEVICE:
DEBUG   - DEVICE: main acquire WR lock and 3 threads acquire RD lock

Environment:
OS: Linux,
Toolchain Zephyr SDK 0.14.1
Commit SHA or Version: 4cc5c56d8c4a4727bcfb6a49cdc2d6ffba39295f

@enjiamai is this possibly a duplicate of https://github.com/zephyrproject-rtos/zephyr/issues/45942? Could you please close in favor of that issue if so, since it has a PR?

Hi @mbolivar-nordic  @MaureenHelm,  yes, they are the same issue which is a twister issue. It duplicates with #45942.  So I am going to close it.
By the way, the  #45929 is refer to an issue of x86, different with this one. Though it happens on the same case.


Fix issue with spread operator for objects

This is not supported by V8 version 7.4 that SH is using and the evalscripts fail.
I guess we'll have to run the evalscripts in V8 instead of node at some point. I tried nodejs14 which supposedly uses V8 7.4 but it passed.

Fix looks ok. There are other occurrences of spread operator used on objects, is that not problematic?

Fix looks ok. There are other occurrences of spread operator used on objects, is that not problematic?

Thanks, I checked again and I indeed found one more in merge_cubes, now there shouldn't be any more hopefully.

I believe elsewhere spread is only used on arrays, so we should be good.
Just a note that Object.assign modifies original object. It might be safer to use Object.assign({}, ..., ...);
I don't think it's an issue with modifying arguments though.

I believe elsewhere spread is only used on arrays, so we should be good.
Just a note that Object.assign modifies original object. It might be safer to use Object.assign({}, ..., ...);
I don't think it's an issue with modifying arguments though.

@mitjak You're right, fixed.


Grey out non-supported languages on settings page for default search

Only allow checkbox on the ones that work

Disable on English also until we can allow blank languages in that result set.


Update mgba-dev.json

Changed the name of bin to avoid conflict with the stable version.
Fix: current directory is moved
Closes #342

@Calinou not sure why this was done but probably can close

@Calinou not sure why this was done but probably can close

Isn't the original issue still present right now?

@Calinou if you want to alias dev/nightly bin and shortcuts then it should be merged.

@Calinou this can be closed everything has been addressed in this pr and it's not defunct.

Closing per @beyondmeat's comment. Thanks for the contribution nonetheless :slightly_smiling_face:


Eth: example eth to tft to deploy vm

Completes #63:

Added example
Added documentation

While the code looks great, I think the example should not ask for a Stellar and Tfchain key.
The main reason we want to have this example is to have a seamless experience for an ethereum user having only an ethereum key. All the other keys should be generated on the fly as they are not provided by the user.

Agree but this PR has some necessary changes and value without that functionality too. I would merge this PR and leave that functionality as a TODO in the github issue.

Since the main purpose of this example are demo's, I would default all networks to production.

The Ethereum Goerli network is marked as deprecated, it requires special knowledge how to configure your Ethereum client and getting Goerli Eth.
Stellar testnet is reset regularly
Testnet bridges are not guaranteed to be up
devnet tfchain and grid are subject to frequent changes which might cause downtime and incompatibilities  and we don't want to make devnet a 'production' version  which it will become if it is used for demo's.

In other words, testnets and devnets are for developers
This will also make the manual simpler


Quit to menu option still carries over Despardo stacks

I noticed while tested out some mods, that when I die the stacks are properly removed. However, when I clicked on 'Quit to Menu' and did another run as Bandit with EITHER Desperado or Lights Out, I still had the Desperado stacks carrying over.
After gaining 10 stacks of Desperado, I quit to menu:

Starting a new run (even with 'Lights Out') I start with 2 stacks:

Thank you for the report!
Once I get the build automation going I'll be fixing this.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Upgrade kernel to 4.19.8 to fix blk-mq bugs

There has been a severe issue in blk-mq in the Linux kernel, which might cause filesystem corruption in some cases.
That issue was fixed by blk-mq: fix corruption with direct issue, and it was backported to a stable kernel 4.19.8.
Once the upstream Container Linux updates kernel to 4.19.8 in the alpha channel, we also need to follow it.

Done: https://github.com/flatcar-linux/manifest/releases/tag/v1995.0.0


Initial commit for new error codes for GET_DIGESTS

Signed-off-by: Steven Bellock<EMAIL_ADDRESS>

Would you please don't use Merge feature - Merge branch 'main' into error_convert ?

Would you please don't use Merge feature - Merge branch 'main' into error_convert ?
Other looks good. Please rebase and merge.

I'll just open a new pull request.


Static init in Bridge doesn't work the same as in .NET.

Expected
Foo
Bar
Actual
Bar
Foo
Steps To Reproduce
Dot Net Fiddle
Live Bridge
using System;

class Foo
{
    static Foo()
    {
        Console.WriteLine ("Foo");
    }
}

class Bar
{
    static int i = Init();

    static int Init()
    {
        Console.WriteLine("Bar");
        return 0;
    }
}

public class Test
{
    public static void Main()
    {
        Foo f = new Foo();
        Bar b = new Bar();
    }
}

@michaelcheers, that is a nice catch, thank you. We will fix it in 1.15 or post 1.15 release.


Update GitHub Action Versions

GitHub Actions Version Updates

saadmk11/github-actions-version-updater published a new release v0.7.1 on 2022-10-29T16:38:42Z

Codecov Report

Merging #17 (87520ee) into main (c172067) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #17   +/-   ##
=======================================
  Coverage   95.67%   95.67%
=======================================
  Files           6        6
  Lines         185      185
=======================================
  Hits          177      177
  Misses          8        8

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


National languages

Web app client must be primary path for general promotion, and need national language adaption as well as desktop.
I have set up local test site already, and waiting for the language selection capability available at core team repo.
Thank you.

@sekisanchi Thank you. The web client multilingual support is on our to-do list.


remove big temporary binary file committed in repo

18MB less, really hurt clone

good catch, sadly now it's already in it ...


Switch or Create New Browser

Is your feature request related to a problem? Please describe.
New Context by default either attaches to existing browser or creates a one with default options. For several cases default options are not good enough. For instance a headfull browser might be needed or a firefox.
add an option to Switch or Create New Browser that can find the right default browser for you.

https://github.com/MarketSquare/robotframework-browser/pull/1318

New Implementation done.
Fixed By #2626


k3s_1_28: 1.28.11+k3s2 -> 1.28.12+k3s1

https://github.com/k3s-io/k3s/releases/tag/v1.28.12%2Bk3s1
(cherry picked from commit https://github.com/NixOS/nixpkgs/commit/4018f62f912bea43655fcc5a807feda93d0eb49a)
Auto backport failed due to conflicts. Parent PR: https://github.com/NixOS/nixpkgs/pull/334630
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 335656 run on x86_64-linux 1
1 package built:

k3s_1_28


Removed DB Blade Compiler #7067

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/7067

@devansh-webkul
Getting the exception, while trying to visit the shop in the default theme. Please find the screenshot Here

@devansh-webkul
Still not working, the products are not listed on the velocity home page. Please find the screenshot here

@devansh-webkul
Now, this is working fine.


Relax peer dependency on grunt

This relaxes the peer dependency on grunt, as recommended here: http://gruntjs.com/blog/2016-02-11-grunt-1.0.0-rc1-released#peer-dependencies
That makes it play better with NPM and grunt release 1.0

Any chance to get this merged?


sketch_rnn_train - error when running with no arguments

When running sketch_rnn_train with no arguments, it tries to download a file that doesn't exist anymore: https://github.com/hardmaru/magenta/raw/master/aaron_sheep.npz
Which then gives the error
IOError: Failed to interpret file <cStringIO.StringI object at 0x7fc81010bb58> as a pickle

Should be resolved with Issue #734. Let me know if any problems still.


Migrate project infrastructure to Task

The Task tool is used as the standard way to perform common development operations in Arduino tooling projects. This project is hereby brought into alignment with that convention.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


hangs with plots [BUG]

description
Weave hangs if plots are includes.
versions

using InteractiveUtils; versioninfo():

Julia Version 1.6.2
Commit 1b93d53fc4 (2021-07-14 15:36 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-11.0.1 (ORCJIT, haswell)
Environment:
  JULIA_NUM_THREADS = 4

using Pkg; Pkg.status():

      Status `~/.julia/environments/v1.6/Project.toml`
  [69666777] Arrow v1.6.2
  [ad839575] Blink v0.12.5
  [336ed68f] CSV v0.8.5
  [324d7699] CategoricalArrays v0.10.0
  [944b1d66] CodecZlib v0.7.0
  [a93c6f00] DataFrames v1.2.2
  [1313f7d8] DataFramesMeta v0.9.0
  [31a5f54b] Debugger v0.6.8
  [31c24e10] Distributions v0.25.11
  [cc61a311] FLoops v0.1.10
  [becb17da] Feather v0.5.9
  [da1fdf0e] FreqTables v0.4.4
  [09f84164] HypothesisTests v0.10.4
  [7073ff75] IJulia v1.23.2
  [82e4d734] ImageIO v0.5.7
  [916415d5] Images v0.22.5
  [c8e1da08] IterTools v1.3.0
  [babc3d20] JDF v0.4.4
  [9da8a3cd] JLSO v2.6.0
  [b9914132] JSONTables v1.0.1
  [b964fa9f] LaTeXStrings v1.2.1
  [23fbe1c1] Latexify v0.15.6
  [ae8d54c2] Luxor v2.15.0
  [ff71e718] MixedModels v4.0.0
  [5fb14364] OhMyREPL v0.5.10
  [9b87118b] PackageCompiler v1.3.0
  [b98c9c47] Pipe v1.3.0
  [f0f68f2c] PlotlyJS v0.15.0
  [91a5bcdd] Plots v1.20.1
  [c3e4b0f8] Pluto v0.15.1
  [7f904dfe] PlutoUI v0.7.1
  [6cfbe66a] QRCode v0.1.0
  [6f49c342] RCall v0.13.12
  [79098fc4] Rmath v0.7.0
  [2913bbd2] StatsBase v0.33.9
  [3eaba693] StatsModels v0.6.24
  [f3b207a7] StatsPlots v0.14.26
  [fd094767] Suppressor v0.2.0
  [ebf5ac4f] TexTables v0.2.4
  [b8865327] UnicodePlots v2.0.0
  [44d3d7a6] Weave v0.10.10
  [a5390f91] ZipFile v0.9.3
  [a63ad114] Mmap

minimum reproducible steps

Put the following code in 00.jl and run weave("00.jl", cache=:off, out_path="output/") .
#' # Plot
x = rand(2, 10)
#' Create a histogram.
using Plots
plot(x[1,:])
#' Create a scatter plot
plot(x[1,:], x[2,:])

The weaving hangs at
julia> weave("00.jl", cache=:off, out_path="output/")
┌ Info: Weaving chunk 1 from line 2
└   progress = 0.0
┌ Info: Weaving chunk 2 from line 4
└   progress = 0.3333333333333333
┌ Info: Weaving chunk 2 from line 7
└   progress = 0.6666666666666666

Just found that things work in VSCode, but not in the repl nor emacs with vterm.

If I start julia from a terminal, then it works. Maybe this is a problem for emacs julia-repl with vterm. I will test further.

I do not fully understand the cause, but the problem is related to using X server with gksqt. Here is a workaround:
ENV["GKSwstype"]="nul"
weave("00.jl", cache=:off, out_path="output/")
ENV["GKSwstype"]="gksqt"

The first line ENV["GKSwstype"]="nul" activates the NULL device so that X server will not be requested. After this, weave("00.jl", cache=:off, out_path="output/") works as expected. The third line ENV["GKSwstype"]="gksqt" activates gksqt in case some plots need to be displayed.

ENV["GKSwstype"]="nul"

I can report this walk-around does work.

I just got hit by this bug too, when I tried to run Weave from my terminal. The fix worked though.

It seems that there had not been any bug-fixing for quite a while. I wonder if the project has been abandoned? Can we make some donations so as to motivate the maintainer to fix some bugs?

@newptcai I am pretty sure that the project is still maintained. I mean so many people use Weave for everything. It might just be that a lot of the code is pretty stable? That is what I am hoping. I still use Weave for so many things, not sure what would replace it.

https://discourse.julialang.org/t/deactivate-plot-display-to-avoid-need-for-x-server/19359/6
it is basically the same, but w/ a function call:
Plots.default(show=false) could be put after the using Plots


wifi ignores initial "command not found" error

Fixes #611

The implementation looks good and I ran through some smoke tests with positive results:
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi
INFO Looking for your Tessel...
INFO Connected to horse.
INFO Connected to "technicallyHome"
INFO IP Address: <IP_ADDRESS>
INFO Signal Strength: (67/70)
INFO Bitrate: 41mbps
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi --off
INFO Looking for your Tessel...
INFO Connected to horse.
INFO Wifi Disabled.
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi
INFO Looking for your Tessel...
INFO Connected to horse.
WARN horse is not connected to Wi-Fi (run "t2 wifi -l" to see available networks)
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi -n technicallyHome -p Rusty007
INFO Looking for your Tessel...
INFO Connected to horse.
INFO Wifi Enabled.
INFO Wifi Connected. SSID: technicallyHome, password: Rusty007, security: psk2
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi
INFO Looking for your Tessel...
INFO Connected to horse.
INFO Connected to "technicallyHome"
INFO IP Address: <IP_ADDRESS>
INFO Signal Strength: (67/70)
INFO Bitrate: 14mbps
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi --off
INFO Looking for your Tessel...
INFO Connected to horse.
INFO Wifi Disabled.
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi
INFO Looking for your Tessel...
INFO Connected to horse.
WARN horse is not connected to Wi-Fi (run "t2 wifi -l" to see available networks)
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi --on
INFO Looking for your Tessel...
INFO Connected to horse.
INFO Wifi Enabled.
➜  t2-cli git:(HipsterBrown-wifi-off-error) t2 wifi
INFO Looking for your Tessel...
INFO Connected to horse.
INFO Connected to "technicallyHome"
INFO IP Address: <IP_ADDRESS>
INFO Signal Strength: (57/70)
INFO Bitrate: 15mbps

The only thing missing is an update to our unit test suite. I will add some and open a PR on your PR.

@HipsterBrown https://github.com/HipsterBrown/t2-cli/pull/5.

@johnnyman727 Your tests have been added to this PR. Thanks for making them. :+1:

Looks good!


Fix FDB max_document_size, binary_chunk_size, and max_attachment_size checks

Overview
Currently the max_document_size, binary_chunk_size, and max_attachment_size parameters can exceed the limits of FDB. This PR checks these parameters against hardcoded limits to ensure that the limits of FDB are not exceeded.
Testing recommendations
Change the parameters to integers above the hardcoded limits:

Greater than 8000000 bytes for max_document_size
Greater than 96000 bytes for binary_chunk_size
Greater than 8000000 bytes for max_attachment_size

Then, add log statements to ensure that the limits are not exceeded. That is, max_document_size should remain at 8000000 bytes or below, binary_chunk_size should remain at 96000 bytes or below, and max_attachment_size should remain at 8000000 bytes or below.
Furthermore, the responses returned should no longer contain the FDB 2103 or 2101 status codes. Each transaction that exceeds the limits should return the response 413 {"error":"document_too_large", "reason":"<DocID>"}.
Related Issues or Pull Requests
Max document size check is inaccurate: https://github.com/apache/couchdb/issues/3354
Checklist

[x] Code is written and works correctly
[x] Changes are covered by tests
[x] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

Should we log cases when the configured size exceeds the limit?

For max_document_id_length I think it was chosen as 512 in the ML discussion.

For max_document_id_length I think it was chosen as 512 in the ML discussion.

max_document_id_length has been changed to 512 bytes instead of 238 bytes. 238 bytes was intended for the database name, not document ID.


pihole-ftl: init at 5.8.1

Motivation for this change
The first part of a trio of PRs (to be followed by pihole and pihole-admin). Based on the work of @nuxeh and the pi-hole-ftl Arch Linux package
#61617
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108055 run on x86_64-darwin 1

1 package failed to build and are new build failure:

pihole-ftl: log https://termbin.com/sgpu

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108055 run on x86_64-darwin 1

1 package failed to build and are new build failure:

pihole-ftl: log https://termbin.com/sgpu

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108055 run on x86_64-linux 1

1 package blacklisted:

tests.nixos-functions.nixos-test

1 package built:

pihole-ftl

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108055 run on x86_64-linux 1

1 package blacklisted:

tests.nixos-functions.nixos-test

1 package built:

pihole-ftl

I will mark this package as linux only. Fixes for mac should be made upstream.

I will mark this package as linux only. Fixes for mac should be made upstream.

@SuperSandro2000 Ready for re-review

@cole-h I think this iteration is ready for review.

Great! Unfortunately, I'm a bit swamped at the moment... I'll be able to take a look Monday at the earliest. Sorry for the inconvenience.

Not a problem. I know the feeling 😅. This PR has been open for a while, so there's no rush!

Any updates on the current state of this PR?

@Kranzes I haven't had a chance to work on this PR recently. I think it is relatively close, so feel free to pick up the remaining work to get it merged.

I would really like to get pihole into nixpkgs but I think it won't be easy and almost not feasible because it assumes almost everywhere writable FHS directories like https://github.com/pi-hole/pi-hole/blob/master/advanced/Scripts/piholeLogFlush.sh

Closing this PR as I don't intend to continue with it. I'll leave the branch around if anyone wants to pick up where I left off.

For those who may be interested, I'm currently picking up this work. For now it lives in my personal Flake.
I've got pihole-ftl is running alongside the Admin UI in a mostly functional and declarative state. I'll raise a draft PR once I've ironed out more of the kinks.


livecheck: add user_agent

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
Allow for user_agent to be specified for livecheck curl requests. In essence, it would reuse the existing implementation from the url stanza and apply it to the livecheck url if needed.
What is the motivation for the feature?
Increasing number of casks are failing livecheck audits due to CDNs blocking the requests. This would add the flexibility to use user_agent if needed. See https://github.com/Homebrew/homebrew-cask/pull/146350 https://github.com/Homebrew/homebrew-cask/pull/146223 https://github.com/Homebrew/homebrew-cask/pull/146330 for recent failures.
How will the feature be relevant to at least 90% of Homebrew users?
Maintainers will spend less time troubleshooting livechecks which will increase the time they spend on other user-facing projects.
What alternatives to the feature have been considered?
Not implementing it and just skipping CI when the issue comes up.

I think this is likely due to https://github.com/Homebrew/brew/pull/15099 still being open.

Nevermind, these are using :page_match, so doesn't seem related to the HEAD request issue.

Increasing number of casks are failing livecheck audits due to CDNs blocking the requests.

Does using a different user agent actually fix that though? Livecheck already uses two different user agents (Homebrew and fake Safari).

This is a planned feature that I already have implemented locally but it depends on the "options" feature and I need to create a PR for that first (that work is also done but there may be some discussion about the shape of it). I'm working my way towards those PRs but I'm currently working on the GitHub strategy PRs and I also need to wrap up that HeaderMatch PR that Markus mentioned.

When I try to add the livecheck url for the cask hookmark, it seems that the livecheck command is working good. But the audit is failure, since the livecheck URL is not reachable by error code 403.
After digging an hour, finally noticed that the reason why those two commands are working in differ is the existence of the user-agent header.
https://github.com/Homebrew/brew/blob/master/Library/Homebrew/cask/audit.rb#L810
Is this feature development ongoing? or should I drop my changes?

Oh... two of the examples are hookmark and this is the problematic cask! I visited again this package haha.

Is this feature development ongoing? or should I drop my changes?

@daeho-ro Oddly enough, I was working on this again yesterday. I had a working implementation when I last left it but I'm reworking the changes to the livecheck block DSL before creating a PR. Depending on how I approach it, I may have to make some changes to Utils::Curl beforehand but I'm working on getting user agent support done soon (while also laying the groundwork for other needed curl-related features).

Allow for user_agent to be specified for livecheck curl requests.
Livecheck already uses two different user agents (Homebrew and fake Safari).

The more I think about this: the more I think we shouldn't be changing/faking our user-agents at all, let alone let them be customised per-formula.
Ultimately our user agents being blocked is a response by the upstream project to our requests. We should respect that and do something different rather than just workaround it.

The more I think about this: the more I think we shouldn't be changing/faking our user-agents at all, let alone let them be customised per-formula.
Ultimately our user agents being blocked is a response by the upstream project to our requests. We should respect that and do something different rather than just workaround it.

I agree that we shouldn't use a different user agent if a server specifically blocks requests because HOMEBREW_USER_AGENT_CURL includes "Homebrew", as that's a clear signal about upstream's wishes. However, if we're simply blocked because our user agent isn't something common/typical (e.g., a browser) or shares some characteristics with bots (e.g., including "curl" text), that may not be as strong of a signal in terms of upstream's intentions.
This only affects casks at the moment, likely because commercial/closed-source software websites can be more aggressive about blocking atypical requests. We've had some livecheck blocks that work locally but fail on CI because the combination of the server's IP address and a non-browser user agent is enough to trigger server-side anti-bot measures (this can also happen locally if you use a VPN). In some of those cases, using a :browser user agent allows the check to work fine on CI.
livecheck has had logic to fall back to the :browser user agent if :default fails since mid-2021, so specifying the user agent in a livecheck block is simply about efficiency (avoiding unnecessary requests that we know will fail) and clarity. [My plan has always been to remove the automatic user agent retry logic in the Livecheck::Strategy methods once we can specify a user agent in livecheck blocks, as the former was just a stop-gap measure until the latter is available.]
In my current implementation, user agent support is simply part of being able to specify #curl_args args in a livecheck block, as that would allow us to handle other weird situations (if that's too much, I could limit it to setting a user agent). If we're against swapping user agents in general, we would have to remove existing user agent-switching logic throughout brew, remove packages as soon as they're unreachable with our user agent (there are currently 40 casks like this), and disallow new packages based on this criterion. As mentioned, some requests only fail on CI, so it seems like a shame to drop working packages simply because of user agent weirdness.
365d install counts for existing casks specifying a user_agent for the cask url are as follows:
adobe-acrobat-pro: 2479
adrive: 2943
attachecase: 89
chalk: 109
clickcharts: 37
coinomi-wallet: 53
dehelper: 57
disk-inventory-x: 3230
elgato-wave-link: 383
eudic: 1143
font-andagii: 18
font-constructium: 16
font-fairfax: 14
frhelper: 33
hookmark: 280
hopper-disassembler: 36
ithoughtsx: 85
jt-bridge: 8
jump: 228
keycue: 214
latexit: 1837
ludwig: 28
neteasemusic: 2649
outguess: 395
pages-data-merge: 55
paraview: 1854
photozoom-pro: 10
pikopixel: 52
popchar: 54
subsurface: 90
tableau: 1169
tableau-prep: 142
tableau-public: 265
tableau-reader: 52
todesk: 2029
typinator: 172
unite-phone: 5
yandex: 1483
youdaonote: 281

However, if we're simply blocked because our user agent isn't something common/typical (e.g., a browser) or shares some characteristics with bots (e.g., including "curl" text), that may not be as strong of a signal in terms of upstream's intentions.

Agreed 👍🏻

remove packages as soon as they're unreachable with our user agent (there are currently 40 casks like this), and disallow new packages based on this criterion

I'd agree with this 👍🏻

As mentioned, some requests work locally but fail on CI, so it seems like a shame to drop working packages for that reason.

I could see us allowing these to remain if so.


Support declaring internal module regex or respect import/internal-regex setting

Resolver performs way too slow on a medium to large TS project where every local/internal import is absolute from the project root, since https://github.com/import-js/eslint-import-resolver-typescript/blob/71b23a206514842fef70a99220e5ffb1d6da2a0e/src/index.ts#L276 optimization branch is not used.
It would be useful to allow users to specify internalRegex similar to https://github.com/import-js/eslint-plugin-import/tree/a89eadf3247af844da6b0f9e7bca7690777bf665#importinternal-regex.
Worth mentioning that using above import/internal-regex did speed up the linting times, but unexpectedly I have seen more improvements when implemented a custom resolver like below using the same regexp, so perhaps there is a bug (or misunderstanding) there and no new option is needed, just addressing that one.
export function resolve(
    importPath: string,
    importerFileAbsolutePath: string,
    tsResolverOptions: TsResolverOptions
): ResolveResult {
    if (internalModuleRegexp.test(importPath)) {
        const absoluteImportPath = path.resolve(`./${importPath}`);
        return {
            found: true,
            path: absoluteImportPath,
        };
    }

    return eslintImportResolverTypescript.resolve(importPath, importerFileAbsolutePath, tsResolverOptions);
}

I don't quite follow you meanings, why internalModuleRegexp matched means the related absoluteImportPath as resolved.

however we could just resolve it faster since we have foo and bar are our top level folders and we use absolute import paths

This seems not always true?
For a common mono repo, the structure would be:
- packages
  - foo
    - nested
      - file1.ts
  - bar
    - nested
      - file2.ts
- package.json

How can we resolve it faster for bar/nested/file2 in this case?

if we base tsconfig path while resolving not the package.json, this would work right?, though complicated when there are multiple projects linting via same config. Also we could ask for users to provide path to root folder 🤷♂

I still can't fully get your point, but a PR for showing case would be appreciated. 👍

Perhaps it's also hard to implement in a generic way, that's why my explanation doesn't make a lot of sense but I'll give it a try when I have time.


[ Recurrent ] Implement Dropout for Recurrent Net

In this commit, drop out for recurrent network is intrduced.
dropout property is introduced and if the element value of random
tensor is smaller than dropout rate, then it will be set zero.
The element which is not set zero, then it will scale with
1.0/(1.0-dropout).
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1321. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

Please add dropout as a layer than adding it as a property of a layer. With the current design, each layer will have to inidividually implement dropout. But if dropout is a layer, then each layer can use dropout by attaching it in front of it. Please update the design.

I think this should be differently. This pr only for the recurrent network. We can implement drop out layer as an formal layer later.

Please add dropout as a layer than adding it as a property of a layer. With the current design, each layer will have to inidividually implement dropout. But if dropout is a layer, then each layer can use dropout by attaching it in front of it. Please update the design.

I think this should deal differently. This pr only for the recurrent network. We can implement drop out layer as an formal layer later.

IMHO, it is a very small task to implement a dropout layer (less than half a day) but maintains extensibility and available for LSTM/GRU etc layers, as well as easier to debug and deal with. Given when dropout layer is added, this code will be removed, I think directly creating dropout layer will be better. I leave the final decision up to you.

Please add dropout as a layer than adding it as a property of a layer. With the current design, each layer will have to inidividually implement dropout. But if dropout is a layer, then each layer can use dropout by attaching it in front of it. Please update the design.

I think this should deal differently. This pr only for the recurrent network. We can implement drop out layer as an formal layer later.

IMHO, it is a very small task to implement a dropout layer (a few hours max) but maintains extensibility and available for LSTM/GRU etc layers, as well as easier to debug and deal with (this PR adds repeated code for both RNN/LSTM which reduces maintainability). Given when dropout layer is added, this code will be removed, I think directly creating dropout layer will be better.

I don't think it is just small task. (If you think it is, - like you said few hours max task, then you can do it, please). Also in the API point of view, other frameworks supports this way as a property. If you are asking to use explicit layer declaration, then I will say no. We could support this drop out like flatten property and if we are going to, then needs realization and it takes more time including test. If you are saying both of them, then it is ok. So I guess this can be done later after the refactoring is finished. I'm fully aware of this, so don't worry too much. I'm sure it can be done after refactoring. ( again, if you like to do it while you are refactoring, then you can do it. Cause, it is just a few hours tasks. So please. ).

Also, this breaks LayerV2 migration and refactoring.

I don't see why it breaks LayerV2 migration and refactoring? If it is because of just adding another property, then it should be supported.

I don't think it is just small task. (If you think it is, - like you said few hours max task, then you can do it, please.). Also in the API point of view, other frameworks supports this way as a property. If you are asking to use explicit layer declaration for this kind of scenario, then I will say no. We could support this drop out like flatten property and if we are going to, then needs realization and it takes more time including test. If you are saying both of them, then it is ok. So I guess this can be done later after the refactoring is finished because it might needs changes. I'm fully aware of this, so don't worry too much. I'm sure it can be done after refactoring. ( again, if you like to do it while you are refactoring, then you can do it. Cause, it is just a few hours tasks. So please. ).

Yes, I meant it to be used just like flatten layer concept. I will add a DropoutLayer quickly based on your implementation in RNN/LSTM layers. And then realization will be added with/while refactoring.

I don't see why it breaks LayerV2 migration and refactoring? If it is because of just adding another property, then it should be supported.

This property will ideally be suited best for LayerNode. I guess will have to be done later.

This PR provides an initial implementation for the dropout, and as it is being used with RNN/LSTM for now, lets keep it this way for verification and the implementation can be wrapped in a layer later. Let's go forward with this.

Please add dropout as a layer than adding it as a property of a layer. With the current design, each layer will have to inidividually implement dropout. But if dropout is a layer, then each layer can use dropout by attaching it in front of it. Please update the design.

I think this should deal differently. This pr only for the recurrent network. We can implement drop out layer as an formal layer later.

IMHO, there might not be big overhead to implement a dropout layer (as the implementation has already been added in the PR, it just need wrapping as a separate layer) and maintains extensibility and available for LSTM/GRU etc layers, as well as easier to debug (this PR results in same logic of dropout for both RNN/LSTM).
Also, this might break LayerV2 migration and refactoring.
This PR adds a new property that would be best suited to be inferred at the graph realization, and graph can add a new dropout layer (just like flatten) and extend support of dropout for all layers. That said, lets keep realization for later (after refactor).
If this PR is time sensitive, lets start with the design in this PR, and update to a new layer later.

Please add dropout as a layer than adding it as a property of a layer. With the current design, each layer will have to inidividually implement dropout. But if dropout is a layer, then each layer can use dropout by attaching it in front of it. Please update the design.

I think this should deal differently. This pr only for the recurrent network. We can implement drop out layer as an formal layer later.

IMHO, there might not be big overhead to implement a dropout layer (as the implementation has already been added in the PR, it just need wrapping as a separate layer) and maintains extensibility and available for LSTM/GRU etc layers, as well as easier to debug (this PR results in same logic of dropout for both RNN/LSTM).
Also, this might break LayerV2 migration and refactoring.
This PR adds a new property that would be best suited to be inferred at the graph realization, and graph can add a new dropout layer (just like flatten) and extend support of dropout for all layers. That said, lets keep realization for later (after refactor).
If this PR is time sensitive, lets start with the design in this PR, and update to a new layer later.

I think this design of droput for recurrent layer is also required as we discussed off-line. I will add new dropout layer in layer PR and also update this design with saving mask.


fix(55650): Wrong/missing quick info in JSDoc @implements tag

Fixes #55650

Brother what’s this codes ??
Can u explain to me plz
And if it’s form me also u need steps plz
في أربعاء، 27 ديسمبر، 2023 في 03:45، كتب Oleksandr T. <
@.***>:

Fixes #55650 https://github.com/microsoft/TypeScript/issues/55650
You can view, comment on, or merge this pull request online at:
https://github.com/microsoft/TypeScript/pull/56884
Commit Summary

eb09afb
https://github.com/microsoft/TypeScript/pull/56884/commits/eb09afb2b85472b9f4e79cf0a7ca45856f6cb9d3
fix(55650): show quick info in JSDoc @implements tag

File Changes
(3 files https://github.com/microsoft/TypeScript/pull/56884/files)

M src/compiler/utilities.ts
https://github.com/microsoft/TypeScript/pull/56884/files#diff-1516c8349f7a625a2e4a2aa60f6bbe84e4b1a499128e8705d3087d893e01d367
(11)
A tests/baselines/reference/quickInfoJsDocTags15.baseline
https://github.com/microsoft/TypeScript/pull/56884/files#diff-e1420612c6fe62d29f4e42c5304f8bae262cc66603db45e853651e30a91ced40
(106)
A tests/cases/fourslash/quickInfoJsDocTags15.ts
https://github.com/microsoft/TypeScript/pull/56884/files#diff-fa8c1cd8de489b3e2d2c562f4c19b9e112791a3c88651485b7b1e0d6ce914a31
(26)

Patch Links:

https://github.com/microsoft/TypeScript/pull/56884.patch
https://github.com/microsoft/TypeScript/pull/56884.diff

—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/TypeScript/pull/56884, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A55MQ3XUWSK2U2HLL6FEBWLYLNOQVAVCNFSM6AAAAABBDW3NL6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TMNZXGMYTKNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Revert "🔀 (release) [NO-ISSUE]: Backmerge main into develop"

Reverts LedgerHQ/device-sdk-ts#521

Unwanted contribution, no context of why it's done. Closing


[NEW ALGORITHM] Tower of Hanoi implementation using Stack

Description:
I would like to contribute to the AlgoGenesis repo by adding the algorithm for Tower of Hanoi problem using Stack
Checklist:

[x] Contributor in GSSoC-ext

[x] Want to work on it

Additional Information:
Tower of Hanoi is a very common question relating to implementation of Stack. While a more straight-forward approach is using recursion, implementation using Stack will help enhance understanding of the topic.

i want to contibute in this .I have a good approach for this.


mWeb- Chat - The new message received offline is not displayed in the chat

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

Mobile Web (Safari and Chrome)
Android

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/203863326-c5408604-eab7-463b-ba08-4ca85b3a85f1.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Was able to reproduce:
https://user-images.githubusercontent.com/38236554/204023241-2f8694d3-16a3-409e-92c1-754d2e72c6ab.MP4

From this SO: https://stackoverflow.com/c/expensify/questions/14418

[x] The "bug" is actually a bug:
[x] The bug is not a duplicate report of an existing GH (close the GH and add any novel details to the original GH instead):
[x] The bug is reproducible, following the reproduction steps:
[x] The GH template is filled out as fully as possible -- this means the GH body and title are clear (ie. could an external contributor understand it and work on it?):
[x] The GH was created by an Expensify employee or a QA tester:
[ ] Decide if the GH should be resolved by an External contributor or Internal engineer, add the appropriate label:

Going to tag in engineering, not sure if this will be fixed by sequence numbers?

I can't reproduce it...
I have my iphone New Expensify app logged with<EMAIL_ADDRESS>on LHN and go on airplane mode.
From my Mac online, on firefox I'm connected with<EMAIL_ADDRESS>and send a message to<EMAIL_ADDRESS>I turn off airplane mode from my iphone app, and see the new message appear. Clicking on the chat, I see it appear too...
https://user-images.githubusercontent.com/2463975/204263237-e4649df9-8ec8-415b-bdaf-8b376c48f30e.MP4
@bfitzexpensify @kbecciv Can you still reproduce? How exactly?

@nkuoch You need to use the mWeb/Safari to reproduce it.

Still can't reproduce it ... Can you @kbecciv ?
I sent the message from mac chrome, and received it successfully on mobile web safari after switching airplane mode and clicking on the chat.

@bfitzexpensify Mind jumping in and help confirming whether you get reproduce? If not, let's close the issue.

Wasn't able to reproduce at this moment with the same steps I took in https://github.com/Expensify/App/issues/13023#issuecomment-1327668920, but I suspect the site slowness might be playing a role in that. Have set a reminder to myself to test this again first thing tomorrow. I'll close if I can't reliably reproduce.

Was unable to reproduce - behaved as expected (when coming back online, the message displayed both in the LHN and within the DM when opened). Closing.


Support statically-sized array fields

It's quite common to store an array with a fixed-length inside a struct like so
typedef struct mat4 {
    float data[16];
} mat4;

we should be able to support this. (and maybe even generate Bigarray code for array of floats maybe?)

P.S. I'm cooking again with some extra free time available so should be able to get to this today or tomorrow.


IMP children terms

In perusing Eco for mapping to the standard GO evidence codes, I am finding
things that I would think should be children of the IMP and IGI terms in GO

example:
ECO:0000015 mutant phenotype evidence  DBXref GO:IMP

I would think
mutant visible phenotype evidence ECO:0000176
mutant physiological response evidence ECO:0000174

should be children of ECO:0000015, but they are not.

In fact, many of the terms that would be used to make an IMP annotation have no
relationship to the IMP (eg, RNAi evidence, etc.).

ECO:0000011, genetic interaction evidence. SO I would have thought this would
be equivalent to IGI. However, neither Dbxref or synonym is listed.
There IS genetic interaction evidence used in manual assertion ECO:0000316,
which has an EXACT synonym to IGI, but no dbxref.
I would think however that ECO:0000011 would be the right mapping via dbxref to
GO:IGI, since the child terms are all type of evidence used to claim IGI
(complementation, double mutant pheno, etc.,

Harold Drabkin

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 8 Jun 2015 at 9:36

Hi Harold,
Thank you for your suggestions.  We have discussed the points you made in your comments.
First, we agree with your suggestion about moving mutant visible phenotype evidence ECO:0000176 and mutant physiological response evidence ECO:0000174 to be children of ECO:0000015. I will move them soon.
Regarding your question about IGI mapping to ECO:0000011, there is some established history here: All the GO codes were previously mapped to ECO terms in consensus with GO people (we worked with Chris Mungall @cmungall [LBL/GO] and Rachael Huntley [EMBL-EBI/UniProt GOA] on this in 2013). The file created by Rachael/Chris that contains the full set of ECO classes mapped to individual GO codes & GO references is here: http://purl.obolibrary.org/obo/eco/gaf-eco-mapping.txt. These mappings have been in use by the GO. For example, look at AmiGO and try to filter on evidence: http://amigo.geneontology.org/amigo/search/annotation . You'll see the "...used in manual assertion" terms. Other groups beyond UniProt & GO have been starting to use the "evidence x assertion" terms, as well.
If there is a concern about these being improper mappings between GO codes & ECO terms, then I think GO tracker is probably a more appropriate place to initiate the discussion (unless it is to add a mapping using the same pattern). I do not think that it would be appropriate for ECO to undo/revise the mappings that, I believe, are accepted by GO at this point... But of course, we are happy to take part in any discussions and implement decisions agreed upon by GOC. If you raise this on GO's tracker, please do CC us on this! (@mchibucos)
You also mentioned that additional terms need to be moved under mutant phenotype evidence. Would you be able to provide us a list of such terms that need to be child terms of mutant phenotype evidence (ECO:0000015) but are not child terms of that term in the ontology? We would be happy to move existing terms or add new terms if needed, but we need to make sure that they serve the broader ECO user community and thus aren't too restrictive or specific to GO annotation methods...
Thank you,
Suvvi & Marcus

Immediate issues are resolved. More work done on IMP in #117.


Update values.py for Toyota Corolla Sport 2021

Add fingerprint of engine, eps, and fwdCamera for COROLLA_TSS2.
It is for Toyota Corolla Sport 2021, made in Japan.
I'm from Taiwan.

What is your Dongle ID?

What is your Dongle ID?

id: eb56d1fcf27b442a


READ THIS BEFORE NEW ISSUE

Hello everyone. As you might know Phosphorus is not working. Here I will explain why. All of you are getting the following errors:
Access to XMLHttpRequest at 'https://scratch.mit.edu/projects/xxx/' from origin 'https://phosphorus.github.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Now I will explain what this means and why it happens. On the internet there is a special security feature to keep external servers from accessing your site. This is called CORS or Cross-Origin Resource Sharing. Unless otherwise set, CORS will block requests coming from anywhere besides the host (ex: "scratch.mit.edu"). You can not override this. So the function of getting the code from Scratch will not work, thus making the whole thing not work. The only way around this that I can think of is to make an extension that replaces the Scratch project with the Phosphorus one and to inject the Phosphorus code into the project address. However, Nathan does not seem to be working on this anymore.
For the explanation of the second error:
Error: XHR Error
    at XMLHttpRequest.xhr.onerror

This is really just caused by the CORS error stated above. You can thank Scratch 3 for this. For any other issue it is just caused by the new Scratch 3.0 update changing the code and making this parser not work. In essence this code will only work with a full rewrite, which will not happen.

Just want to say:
That first error is only phosphorus attempting to grab a project's title. That request can fail and nothing bad happens. The second error, however, happens because the location of new Scratch projects changed after Scratch 3. Simply updating the path wouldn't fix anything because, as you said, phosphorus cannot parse Scratch 3 projects. The new API route can actually be fetched by phosphorus without any weird extensions.
I really hate to advertise, but I did actually Scratch 3 projects work in my phosphorus fork. It works... actually pretty well on some projects.

Yeah I misunderstood (I only briefly looked at the errors), because I don't really use it.


Revved up version number of release.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


TypeNode#annotated_types

Returns an array of all types (struct/class/module) with the given annotation.  Addresses some of #7274.
annotation Foo
end

@[Foo(val: 1)]
class Bar
end

@[Foo(val: 2)]
class Baz
end

class Blah
end

{% for a in Foo.annotated_types %}
  pp {{a.annotation(Foo)[:val]}}
{% end %}

# => 1
# => 2

A future PR could add #annotated_methods/#annotated_variables, but #annotated_types is the more useful one IMO.
/cc @vladfaust

Small note – you don't actually check for types in specs, only for their size. I'm also concerned of how does it work with #7326...

In the case of #7326 you actually want to keep duplicates since the values on each could be different.  However, annotated_types you only want the list of types that are annotated, you wouldn't want Klass to show up twice just because you added two annotations to it.
Even if those two annotations had separate values, you would still be able to use #annotations in the for loop to get access to them.

This can be confused with classic type annotations. The choice over Attributes was decided in https://github.com/crystal-lang/crystal/pull/6063

Just a note that things like this push us further and further away from incremental/modular compilation (at this point we should probably drop that idea altogether and accept the existing nature of Crystal).

@asterite if each library/shard is independent from each other, won't it be possible to compile each one and link them to the main program?

@asterite @straight-shoota anything else need to be done?

@asterite incremental macros just means careful tracking of exactly which AST nodes a macro "sees" and being able to verify they're unchanged. I think that can be automated fairly well. We should remove the main blocker for incremental/modular compilation (type restrictions only being restrictions) before blocking other features over that though.
I think this is good to go.

I would like to have the ability to query types/ivars/methods given an annotation type.
I think that the incremental is doable (at some cost).
But what I would like to have a discussion/design before merging this is regarding subtyping. If Bar < Foo, are annotations inherited or not? Would that behavior be better specified in the annotation declaration itself (like in C# IIRC) or to define that upon querying (adding params to the proposed API)

I think it would be better if they were not, and just added to each type explicitly; however I could be convinced otherwise.  IMO, This would make it less likely for unintended things to happen.  Being more verbose but allowing for more control seems to be a fair trade to me.

Renamed that property @straight-shoota, CI failure seems unrelated?

I don't suppose this will make it into 0.29.0?

@Blacksmoke16 I am interested in the feature but I haven't invested time yet to have proper design discussions. From my past experience, I am still inclined to mimic C# interface. But we should also consider how other language features impact: an annotation that is applied in a module that is included in a class does contribute to the annotations?

I'd like to get the discussion around this started again.  I'm getting close to a point where this is kind of a blocker to some Athena stuff I'm working on.  #8133 will be a good temporary solution, but having both this and that would be ideal.

Any movement on this? This really is probably the ideal way for annotations to work, since they won't be hamstrung by needing to loop over annotations inside of a class. I really need this working for a project as well.

Any movement on this? This really is probably the ideal way for annotations to work, since they won't be hamstrung by needing to loop over annotations inside of a class. I really need this working for a project as well.

Yes +1 for this feature

I think this will be needed for the new logging stuff, otherwise how do you find all registered logs?
(I wonder why there's no registry and instead the proposal is using annotations, but it's a separate issue).

It does seem necessary for a number of things, and it's so close to approval

@asterite it's not needed. The following works.
  def self.build_backend(type : String, config : Backend::Config)
    {% begin %}
      case type
      {% for t in Log::Backend.all_subclasses %}
        {% if reg = t.annotation(Log::RegisterBackend) %}
          when {{reg[0]}}
            {{t}}.new(config)
        {% end %}
      {% end %}
      else
        raise "There is no Log::Backend with @[Log::RegisterBackend(\"#{type}\")] annotation"
      end
    {% end %}
  end

It is not a registry as DB drivers because that might lead to a situation where the backend is not registered on time to initialize the Log constants.
Back to coding ... 👋

So the annotation is only for the name, but you still need to inherit Log::Backend. Interesting!
Why not rely on a class method like backend_name? Why use annotations which are not type-safe?

Also a warning: if a generic type inherits Log::RegisterBackend then it will stop working because you won't be able to use that uninstantiated generic type. Maybe there's no use case for generic types, though...

Why not rely on a class method like backend_name? Why use annotations which are not type-safe?

I liked the registry. The case is generated with literals. It can be changed of course, it is not the more important aspect :-). But the annotation based registry is doable.

Also a warning: if a generic type inherits Log::RegisterBackend then it will stop working because you won't be able to use that uninstantiated generic type

This is what #8458 would help with, as it could print Foo(T) as Foo.

@asterite it's not needed. The following works.

It works yes, but IMO it seems less than ideal to have to have a parent type/module just to do this; hence this PR.  Annotating a type should be enough, not for the Log use case specifically but are cases where it would be nice.

@Blacksmoke16 Totally agree. But I don't think anyone made the argument that this PR wasn't useful because there are simple alternatives. It's just not strictly necessary for the Log::Backend example. 👍

As a workaround for now, I realized you could just do Object.all_subclasses.select &.annotation(MyAnn)

Closing you can just use the workaround as defined in https://github.com/crystal-lang/crystal/pull/7648#issuecomment-598167731.


Replace global Logger with Client.Logger

All Clients share a single global Logger:
https://github.com/getsentry/sentry-go/blob/763dc7f49323f467d4c62ec15804723ec5350b37/client.go#L20
That means that calling NewClient mutates global state in surprising ways:
https://github.com/getsentry/sentry-go/blob/763dc7f49323f467d4c62ec15804723ec5350b37/client.go#L105-L113
If a program has multiple clients, setting the Debug option affects all other clients:
go func() {
	c1, err := NewClient(ClientOptions{
		Debug: true,
	})
	if err != nil {
		log.Fatal(err)
	}
	c1.CaptureMessage("message from c1")
}()
go func() {
	c2, err := NewClient(ClientOptions{
		Debug: false,
	})
	if err != nil {
		log.Fatal(err)
	}
	c2.CaptureMessage("message from c2")
}()

The state of Debug logging for c2 is undefined, might be on, might be off. No way to turn it off unless messing with the global Logger value.

Checking in if this needs more discussion or ready to get into the implementation state?

@YashishDua I think the goal here is clear. Thanks for chiming in!

Perfect! Picking this up then.


SVG and charset utf8 dataURIs not supported in PIXI 4.1+

Hey there,
Using the basic example here: http://pixijs.github.io/examples/?v=v4.0.3#/basics/basic.js
I've pasted the following SVG dataURI as the argument in PIXI.Texture.fromImage
const texture = PIXI.Texture.fromImage(`data:image/svg+xml;utf8,<?xml version="1.0" encoding="iso-8859-1"?><!-- Generator: Adobe Illustrator 19.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  --><svg version="1.1" id="Box" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"	 viewBox="0 0 50 50" style="enable-background:new 0 0 50 50;" xml:space="preserve"><style type="text/css"> .Background{fill: #202020;}</style><rect id="Background_9_" class="Background" width="50" height="50"/></svg>`);

Everything works as expected, up until v4.1.0 where the error 'Invalid image type in URL.' gets thrown.
I looked into it and noticed that in the function decomposeDataUri(dataUri)  is where the problem occurs.  The issue being that the regex constant PIXI.DATA_URI does not match dataURIs that are charset utf8|utf-8.
The current regex is : /^\s*data:(?:([\w-]+)\/([\w+.-]+))?(?:;(charset=[\w-]+|base64))?,(.*)/i
I changed it to: /^\s*data:(?:([\w-]+)\/([\w+.-]+))?(?:;(charset=[\w-]+|base64|utf8|utf-8))?,(.*)/i
(forgive my lazy regex)
Then, I got an error about the SVG parsing from a string. getSvgSize(svgString)
"The SVG image must have width and height defined (in pixels), canvas API needs them."
There, the regex PIXI.SVG_SIZE was only looking for the width/height properties of the SVG element, ignoring the viewBox property.
Parsing xml from regex is known to be quite the buggy experience, I would suggest to move to using DOMParser if possible.
const svgDocument = new DOMParser().parseFromString(svgString, 'text/xml')
const svg = svgDocument.getElementsByTagName('svg')[0]

// Grab viewbox data  [x, y, width, height]
const viewBox = svg.getAttribute('viewBox').split(' ').map(Number)

// Attempt to get size from width/height props.
const size = {}
size.width = +svg.getAttribute('width')
size.height = +svg.getAttribute('height')

// If no width is specified, look at viewbox, probably check for validity here too
if (!size.width || isNaN(size.width)) size.width = viewBox[2]

// If no height is specified, look at viewbox, probably check for validity here too
if (!size.height || isNaN(size.height)) size.height = viewBox[3]

Thanks for reading :)

Hi, the SVG support was improved in v4.1, a couple of things:
const texture = PIXI.Texture.fromImage(`data:image/svg+xml;utf8,<?xml ...

Firstly, this is invalid data URI according to the spec, charset is a parameter for media type, after that comes ;base64 if it's base64 encoded data. Change utf-8 to charset=utf-8 and the regex should match. The error should be more accurate. :)
Second, viewBox and width/height are not the same thing, read this for example. It turned out to be impossible to support SVGs without size properties, see https://github.com/pixijs/pixi.js/pull/2614.
Also, it's better to use base64 data if you want to support more browsers, for some reason plain svg doesn't work in all situations, see this comment.

Hey, thanks for the response!
data:image/svg+xml;utf8,<?xml ... is just the shorthand to data:image/svg+xml;charset=utf-8,<?xml .... Certainly this is not supported in all browsers. However, if not supported, I agree with you that a more meaningful error message should be displayed, or perhaps, this issue will educate others. :)
I ended up using base64 after all even after reading comments in this article and posting this issue. For the exact reason of browser support.
Thanks for the viewbox article! I just want to clear up that I wasn't insinuating that viewBox and width/height are one in the same. Viewbox is a powerful attribute that works in tandem with width/height. However, with a high percentage of svg being exported out of Illustrator, I would imagine some support fro missing width/height attributes. (seeing as Illustrator does not export them by default). When no width or height is specified, the SVG is scaled to fit the parent container, maintaining the aspect of the viewBox width/height property.
After reading #2641 it does make sense to require a width/height
Either way, this a great addition to PIXI, thanks @RanzQ

As I said, it's invalid according to the spec, so I wouldn't trust it. :) For example, utf-8 works in Chrome even if you don't have the charset parameter: http://codepen.io/RanzQ/pen/vyKjzM
So I guess it defaults to utf-8 in Chrome. Haven't seen that "shorthand" documented anywhere so I think the author of that article just instructed wrong.
Better to use base64. :)
@XerxesNoble Anyway, thanks, nice to know this feature is useful. I'll try to come up with a PR for more meaningful errors at some point.

I came across to this issue while I was looking for if it's possible to create an atlas in pixi using SVG images, is it? I'm doing some tests but I can't load any atlas in this format, don't know if I'm doing something wrong or if it's not supported as there's little information about this on github or docs. Sorry if it's not the correct place to ask this, thanks.


Switched broken pypip.in badges to shields.io

Hello, this is an auto-generated Pull Request. (Feedback?)
Some time ago, pypip.in shut down. This broke the badges for a bunch of repositories, including hasoffers. Thankfully, an equivalent service is run by shields.io. This pull request changes the badges to use shields.io instead.

Coverage remained the same at 100.0% when pulling 547d337f594c45cc1b6239550a8b58a04791acb5 on movermeyer:fix_badges into 97937ed9f30a26dcfa2bacf41b5fe083f18c810d on jthi3rry:master.


When changing to Use Server DNS or not the QR code is not updated.

When generating a peer with Use Server DNS checked generates a config and QR with DNS settings.
However, if editing the user and removing Use Server DNS; the config is updated but the QR code isn't for the DNS settings. It should remove them.
Allowed IPs is updated in the QR.

Closing in favor of linked PR.


feat: framework - using a cmd library/framework to handle app execution

As developers, i want use libraries like cliff, click, ect. This will allow for a standardization of how to create future command and will help improve flag handling.

Although this is likely a separate feature from this, this feature should also factor into the need to have there be a REST API portion (with auth) of armada, to allow it to be used in complex workflows that don't have the ability to run it locally.
In a python sense, something very similar to openstack practices of CLI calling API.  Also very similar to helm itself except would not suggest another layer of gRPC, but a simple REST framework.  I would keep an eye on what is being done for github.com/att-comdev/drydock as it is leveraging this same model for MaaS using pecan complete with plugins and auth.

Correct when adding this feature we will need to follow something similar to the openstack cli practices or fuels. in order to utilize the armada lib not just as a cli tool, but a library, that just so happens to have a CLI. good add @alanmeadows.

done in #52


Set default upstream branch on failure

Quick fix to resolve the issue.

@todaywasawesome it's seems lint is preventing the merge to happen
Can you fix please?

@lrochette fixed


[DOC-4750] Document kv.allocator.recovery_store_selector cluster setting

[DOC-4750]
Relates to https://github.com/cockroachdb/cockroach/commit/3ce0fd5483a6bf3d4a5102da9cf9775904f5c572#diff-0ef17f0a19fa72bb8e62ee9059086c15959d49920b702da3f8d1aa2659cc225eR90
Previews
Tests

[x] Local build
[x] Linkcheck

This change is


[Bug] Flyout gradient on iOS improperly sized

I totally hacked this together with a hardcoded value b/c I've yet to figure out the CALayer mojo to get the expected result.
https://github.com/davidortinau/Xappy/blob/master/Xappy/Xappy.iOS/Renderers/XappyShellRenderer.cs#L47
fwiw - straight up setting the background color works fine. Gradient is sized for iPhone X. Not:

I just started seeing this on iOS when I updated from XF 4.2 to XF 4.3.   If you compile Xappy with XF 4.3, the flyout view bounds in XappyShellRenderer.OnFlyoutWillAppear are for the full screen.  When the flyout is closed, you see an extra strip of gradient

When you invoke the flyout, the gradient view is full screen width.  Where and when is the flyout width being calculated?


Removing feedback for the docset

See https://dev.azure.com/ceapex/Onboarding/_workitems/edit/510952

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

File
Status
Preview URL
Details

dynamicsax2012-msdn/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix(keyExpectedValue): AzureResourceManager queries convert to a recommendation rather than a current status

Closes #
Proposed Changes

I submit this contribution under the Apache-2.0 license.

LGTM


Feature/generatecerts

Reviewers
@jesuspg  @hmunfru
Description
Create a keystore as /etc/keystorejetty, but only if this file does not exists.
The certificate is auto-signed.
The CN of the certificate is obtained according this algorithm:
-Check external IP using : /usr/bin/curl -m15 -s http://ifconfig.me/ip (there is a timeout of 15s)
-If this commands doesn't get a valid IP, try to obtain a IP with hostname -i
-If this command returns <IP_ADDRESS>, get the IP of the interface where is the default route
Also a pair of new scripts are provided:
-A script to generate the keystore: if no parameter is provided, use the algorithm described, otherwise use the parameter received as CN.
-A script to create a keystore from a keyfile, cert, and certchain. This is useful to import a wildcart cert from an Apache host.
The other changes are in the configuration:
-Use /etc/keystorejetty instead of a file inside /opt/fiware-paas
-Use "password" as password.
Testing
Locally. I've tested only that the package installs without errors, that server starts and that the generated certificate is used.

LGTM

LGTM


feat: Updated Grid with examples and docs. Removed Layout component.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3
- Added 2

Clones removed
==============
+ packages/orcs-design-system/lib/components/Layout/index.js  -3

See the complete overview on Codacy


PII redaction masking not working

Hi,
I have a text file, JSON, and parquet file. The text file contains a text some PII information. When I get an object using the object lambda access point, the PII information is masked and returns as expected result
The JSON file contains an object with some PII information. When I get the object using the object lambda access point, the PII information is masked and returns as expected result
But the parquet file has encrypted JSON object with some PII information. When I get the object using the object lambda access point, the PII information is not masked and returns not expected result

This is the JSON the parquet has
{"record_time":"2023-11-27 06:15:34.640","data":{"name":"Suresh","mail":"sj@softway.com","phone":"2323232323","website":"sj-softway.com","msg":"Test123","language":0,"units":0,"systemTime24":false,"deviceName":1,"deviceNameCustom":"Other","displayBrightness":50,"displayDefaultBrightness":50,"nightModeEnabled":false,"nightModeActive":false,"nightModeLightBarAllowed":true}}


feat: support etcd cluster password authentication

/cc @tangcong @engow
fix #100

cool to see the feature


Fix zeppelin-web development mode

What is this PR for?
After https://github.com/apache/zeppelin/pull/2373, zeppelin-web dev mode does not work properly.
Dev mode always ask user login (even if authentication is turned off) and any login attempt will fail. So it makes difficult to develop front-end.
This PR fixes problem by not adding X-Requested-With: XMLHttpRequest header in dev mode.
What type of PR is it?
Bug Fix
Todos

[x] - Fix devmode

How should this be tested?
run zeppelin-web dev mode and see if you can login / open notebook
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Tested (dev mode), works fine, LGTM

Few days I too was thinking about this, thanks for the fix. LGTM.

Tested locally, LGTM.

Tested and LGTM

Thanks @tinkoff-dwh  @prabhjyotsingh @1ambda @soralee  for review.
Merge to master


Cannot download any release before 0.9.5

Tried Chrome and Firefox, both in Incognito mode:

Firefox just gives me a white screen
Chrome: "Access to doc-14-2k-docs.googleusercontent.com was denied"

This happens for any Linux release before 0.9.5 from the releases page.

I can't reproduce this error. Could it be a temporary problem with google drive? Does the problem persist?

It seems to work again now.


Added Nencki Institute of Experimental Biology, Polish Academy of Sci…

Institutional page: http://en.nencki.edu.pl
Laboratory of Neuroinformatics [OFFICIAL PAGE]: http://en.nencki.gov.pl/laboratory-of-neuroinformatics
Laboratory of Neuroinformatics [LAB PAGE]: https://neuroinflab.wordpress.com
The Laboratory of Neuroinformatics offers a PhD programme for graduate students.

@ziemowit-s Pull request merged.
Please notice that free educational subscription for JetBrains tools is for students and teachers only, and is valid for using the tools for educational purpose only. If employees of this Institute who are not students, nor teachers, also need a license for JetBrains tools, they are eligible for an academic discount for the tools. They can get the discount by email to<EMAIL_ADDRESS>Thank you!
For the record: This institution website is at http://www.nencki.gov.pl


[5.5][SymbolGraph] Fix crasher when retrieving cursor info of method defined in ObjC

In a mixed Objective-C / Swift module, we have a Clang module overlay that’s a Source file, not a serialized AST as is currently assumed. That assumption caused a crash when retrieving the symbol graph as part of a cursor info request to SourceKit, which was invoked on a method defined in the Objective-C part of the module.
To fix the crash, recursively use the same logic that already exists to serialize a module to also serialize the clang overlay module since that function alreayd correctly handles the distinction between source files and serialized ASTs.
Resolves rdar://76951147

@swift-ci Please test

@swift-ci Please build toolchain macOS

macOS Toolchain
Download Toolchain
Git Sha - 2d927e3ad529f53e3533057d2695d774a1cbb6b9
Install command
tar -zxf  swift-PR-37134-958-osx.tar.gz --directory ~/

@swift-ci Please test Windows


Same check-in and check-out date

Hi there,
First of all, really nice plugin!
I'm wondering if it is possible to use this when having the same check-in and check-out date. I want to use it for rentals, but these can be for a single day so logically i want it so the user would click only one day if they want to rent for one day only. I have tried to rewrite the script a bit to accomodate this functionality but i cannot see what will break based on this change.

Did you complete this task? I am trying to do that but not success

I have the same problem and I don't understand how to solve it? How did you do it?


[5.2] Allow models to specify a timezone for $dates

Date mutators depend on a global variable, PHP's default timezone. This can cause incorrect timestamps to be saved to and retrieved from the database if the timezone ever changes, or if two environments use a different timezone setting:
// assume: global timezone is UTC
// assume: my_timestamp column is listed in $dates or $casts

$x = App\SomeModel::find(1);
$y = $x->my_timestamp;				// perhaps 2016-01-02 03:04:05 UTC

// timezone changed (or it's a different app, or the app is running
// with different environment settings, etc.)

date_default_timezone_set('America/New_York');
$z = $x->my_timestamp;
// $z is 2016-01-02 03:04:05 EST
// this is NOT equivalent to the above UTC timestamp

This patch adds a Model property, $timezone. The default value is null and behaves exacty as it does today.
If set to a non-null value, timestamp columns listed in $dates, or listed in $casts as "datetime", will be rendered in the given timezone when written to the database and to the equivalent local time when retrieved from the database:
// assume: global timezone is UTC
// assume: my_timestamp column is listed in $dates or $casts
// assume: the model's $timestamp value is set to 'UTC'

$x = App\SomeModel::find(1);
$y = $x->my_timestamp;				// perhaps 2016-01-02 03:04:05 UTC

// timezone changed
date_default_timezone_set('America/New_York');
$z = $x->my_timestamp;
// $z is 2016-01-01 22:04:05 EST
// this IS equivalent to the above UTC timestamp

Relationship to Laravel's app.timezone value
It's common to set the timezone in config/app.php and it's unlikely that you would change it elsewhere.
However, this is not always the case when Eloquent is used as a standalone ORM, for example, in a legacy non-Laravel app.
The TL;DR is that timestamp values saved to the database should be deterministic, regardless of the global timezone setting or changes to the local environment.

Shouldn't this be a static property?

@JosephSilber Yes and no. Yes: it applies to all instances of the model, so should be static. No: Other similar properties in Eloquent are protected: $table, $dates, $casts, etc. For consistency I defined it as protected. Hopefully a future release of Eloquent will use static properties.

Huh??
All those other properties you mentioned are model-specific properties.
The timezone is a property that should be shared between all models.
And if it's a static property, Laravel core can set it to the config timezone from the database service provider.

Okay, that makes sense. I implemented it per-model-class but it seems unlikely you’d need it to be different from one model to the next.

I totally agree with @JosephSilber on this. Timezone is a property that should be shared between all models. If it is set as a static property, then Laravel can directly load from the timezone property in config.

If we make it shared across all models we're just asking for a later PR asking it to be model specific.

@taylorotwell

I don't see how this makes sense to be model specific.
If it's model specific, this can't be handled by Laravel automatically. Big drawback.

Because someone will want to make it model specific.

For now just override fromDateTime and asDateTime in a base model and you can solve this in user land.


Fixed OAuth 1 for some methods

When GET request with content-type application/x-www-form-urlencoded is made I get
java.lang.ClassCastException: org.apache.http.impl.client.RequestWrapper cannot be cast to org.apache.http.impl.client.EntityEnclosingRequestWrapper

HTTPRequest is an instance of EntityEnclosingRequestWrapper only when body or form-param is sending
also, URLEncodedUtils.parse(entity); can return NameValuePair with null value (instead of empty string)

Thanks a lot!


Add TODOs Badge to README

Hi there! I wanted to propose adding the following badge to the README to indicate how many TODO comments are in this codebase:

The badge links to tickgit.com which is a free service that indexes and displays TODO comments in public github repos. It can help surface latent work and be a way for contributors to find areas of code to improve, that might not be otherwise documented.
The markdown is:
[![TODOs](https://badgen.net/https/api.tickgit.com/badgen/github.com/chromedp/chromedp)](https://www.tickgit.com/browse?repo=github.com/chromedp/chromedp)

Thanks for considering, feel free to close this issue if it's not appropriate or you prefer not to!
(full disclosure, I am the creator/maintainer of tickgit)

No.


Add saving correlation to EZ sweep

This pull request is dependent on greenelab/tybalt#136 (the hash in ccc2ba1 is going to update). I will also likely rebase this PR - I will remove the WIP tag once this is done.
I add saving correlation (Pearson and Spearman) to both samples and genes before and after compression across different algorithms. I also update the README and analysis scripts accordingly.

Successful rebase - converted a rough-to-review PR into one that's hopefully more manageable!

@danich1 - any follow-up comments?


make the parser mode configurable (fastest, smallest, standard)

WyriHaximus/HtmlCompress comes with several presets, currently the smallest scheme is used.
This can cause problems with inline javascript, inline js is compressed too and some of the minifiers are producing invalid js code.
The fastest/standard modes are more reliable.

This is a fantastic idea. I was about to implement something similar but thought I'd check to see if someone already had a pull request for this exact configuration option.

Another option might be to just make the $parser property protected instead of private. That way anyone could easily extend Extension and set $parser using one of the other Factory static methods.


Fix default options in @parity/electron

I'm not really satisfied, because we define 2 times each default option. But unfortunately because of https://github.com/TypeStrong/typedoc/issues/522, it's either nice code or nice docs. I went for nice docs.

Pull Request Test Coverage Report for Build 117

0 of 6 (0.0%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.03%) to 42.522%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/electron/src/fetchParity.ts
0
1
0.0%

packages/electron/src/runParity.ts
0
1
0.0%

packages/electron/src/isParityRunning.ts
0
1
0.0%

packages/electron/src/getParityPath.ts
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

packages/electron/src/runParity.ts
1
0.0%

Totals

Change from base Build 115:
0.03%

Covered Lines:
823

Relevant Lines:
1933

💛  - Coveralls


[].slice || ... generates broken code

Looks like [].slice || (...anything) gets replaced with emptystring.
For example: [].slice||1; 1 becomes ,1  (link)
A less contrived example: var slice = [].slice || function() {...}, somethingElse = 1; becomes var slice=,somethingElse=1 (link)
Seems to happen with .slice and other array methods like indexOf, but not for any old property (i.e. [].foo is fine)

Released 0.4 with the fix, thanks


fixed dependency on abandoned (renamed) package

https://packagist.org/packages/endroid/qrcode is marked as Abandoned (was just renamed to https://packagist.org/packages/endroid/qr-code)

Thanks!


feat(api): Expose application metadata and functions to JS api - fix #1387

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] New Binding Issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes. Issue #___
[x] No

The PR fulfills these requirements:

[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
New functions exposed to javascript API:
- getVersion
- getName
- getTauriVersion
- exit
- relaunch

Examples have been updated as well.

This will conflict with #1444 but i'll deal with it.


[AMBARI-24408] Update org.eclipse.jetty version to 9.4.11.v20180605 to avoid CVE issues

What changes were proposed in this pull request?
Update org.eclipse.jetty version to 9.4.11.v20180605 to avoid CVE issues.
See https://dev.eclipse.org/mhonarc/lists/jetty-announce/msg00123.html for reported issues.
This was cherry-picked from #1972 .
How was this patch tested?
Manually tested as few scenaios
Unit tests pending...
Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3462/
Test PASSed.


Rename bazel_features.bzlmod to bazel_features.repos

Continuing the trend of de-emphasizing the name "Bzlmod". I think it would make more sense to group features related to external dependencies together, instead of just Bzlmod features. Not sure whether this should be called external or external_deps or just repos, so I just went with the shortest one.

I slightly prefer external_deps a bit since it's more intuitive.

@alexeagle Can you add @fmeum as a collaborator on this repo? It seems I cannot assign him as reviewer.

I am in the rules_authors team now, but don't seem to have permissions for this particular repo.

@fmeum would you prefer external_deps as well? I'm personally undecided so will go with the majority vote.

I also prefer external_dep as module extensions naturally fall under it, but aren't repositories.

@fmeum what access would you like that you don't get as a rules-authors team member?

@fmeum what access would you like that you don't get as a rules-authors team member?

Given that we probably want to protect the main branch with required reviews, could you give me write permissions so that I can approve PRs?


Flutter web - Cache management with flutter >= 3.22

Steps to reproduce
When I launch the first time a flutter web app, lots of file are loading:

For example, i have 899 requests in my example
How to manage cache in these case:

Keep flutter js file in cache when i refresh my browser (F5) or launch the app
Refresh cache when the project has an update (new main.dart.js)

Expected results
Don't load each time js files as long as no updates is deployed
Actual results
Load each time js files when i launch the app in my browser
Code sample
index .html
<!DOCTYPE html>
<html>

<head>
  <base href="$FLUTTER_BASE_HREF">

  <meta charset="UTF-8">
  <meta content="IE=Edge" http-equiv="X-UA-Compatible">

  <!-- iOS meta tags & icons -->
  <meta name="apple-mobile-web-app-capable" content="yes">
  <meta name="apple-mobile-web-app-status-bar-style" content="black">
  <link rel="apple-touch-icon" href="icons/Icon-192.png">
  <link rel="manifest" href="manifest.json">

  <script>
    var serviceWorkerVersion = '{{flutter_service_worker_version}}';
  </script>
  <!-- This script adds the flutter initialization JS code -->
  <script src="flutter.js" defer=""></script>

  <meta content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" name="viewport">
</head>

<body>
  <script>
    window.addEventListener("load", function (ev) {
      // Download main.dart.js
      _flutter.loader.loadEntrypoint({
        entrypointUrl: "main.dart.js?v=" + serviceWorkerVersion,
        serviceWorker: {
          serviceWorkerVersion: serviceWorkerVersion,
        },
        onEntrypointLoaded: function (engineInitializer) {
          engineInitializer
            .initializeEngine({
              useColorEmoji: true,
            })
            .then(function (appRunner) {
              appRunner.runApp();
            });
        },
      });
    });
  </script>
</body>
</html>

Manifest.json
{
    "name": "",
    "short_name": "",
    "start_url": ".",
    "display": "standalone",
    "background_color": "#000000",
    "theme_color": "#000000",
    "description": "",
    "orientation": "portrait-primary",
    "prefer_related_applications": false,
    "icons": [
        {
            "src": "icons/Icon-192.png",
            "sizes": "192x192",
            "type": "image/png"
        },
        {
            "src": "icons/Icon-512.png",
            "sizes": "512x512",
            "type": "image/png"
        },
        {
            "src": "icons/Icon-maskable-192.png",
            "sizes": "192x192",
            "type": "image/png",
            "purpose": "maskable"
        },
        {
            "src": "icons/Icon-maskable-512.png",
            "sizes": "512x512",
            "type": "image/png",
            "purpose": "maskable"
        }
    ]
}

main.dart
import 'dart:async';
import 'package:aedex/router/router.dart';
import 'package:flutter/material.dart';
import 'package:flutter_localizations/flutter_localizations.dart';
import 'package:go_router/go_router.dart';
import 'package:url_strategy/url_strategy.dart';

Future<void> main() async {
  setPathUrlStrategy();
  runApp(
    ProviderScope(
      child: const MyApp(),
    ),
  );
}

class MyApp extends ConsumerStatefulWidget {
  const MyApp({super.key});

  @override
  ConsumerState<MyApp> createState() => _MyAppState();
}

class _MyAppState extends ConsumerState<MyApp> {

  @override
  Widget build(BuildContext context) {
    final router = ref.watch(routerProvider);

    return MaterialApp.router(
      routerConfig: router,
      debugShowCheckedModeBanner: false,
      theme: ThemeData(
        brightness: Brightness.dark,
        useMaterial3: true,
      ),
      darkTheme: ThemeData(
        brightness: Brightness.dark,
        useMaterial3: true,
      ),
      localizationsDelegates: const [
        AppLocalizations.delegate,
        aedappfm.AppLocalizations.delegate,
        GlobalMaterialLocalizations.delegate,
        GlobalCupertinoLocalizations.delegate,
        GlobalWidgetsLocalizations.delegate,
      ],
    );
  }
}

Screenshots or Video
No response
Logs
No response
Flutter Doctor output
[✓] Flutter (Channel stable, 3.22.3, on macOS 14.5 23F79 darwin-arm64, locale fr-FR)
    • Flutter version 3.22.3 on channel stable at .asdf/installs/flutter/3.22.3-stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b0850beeb2 (5 weeks ago), 2024-07-16 21:43:41 -0700
    • Engine revision 235db911ba
    • Dart version 3.4.4
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Library/Android/sdk
    • Platform android-34, build-tools 33.0.1
    • ANDROID_HOME = /Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.92.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.94.0

[✓] Connected device (3 available)
    • macOS (desktop)                 • macos                 • darwin-arm64   • macOS 14.5 23F79 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         • macOS 14.5 23F79 darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript • Google Chrome 127.0.6533.120
    ! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area network
      as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources
    • All expected network resources are available

are you experiencing this in debug or running something like
flutter build web
dhttpd --path build/web/

@iapicca in debug mode

Hi @redDwarf03, do you get this issue with the counter app? How are you launching the app? Are you running it with a specific port or are you leaving it to the tool (ie flutter run -d chrome). Did this work for you in any version prior to 3.22?

Hi @danagbemava-nc

No, this issue comes from an app i developed
I launch the app with VSCode in debug mode
The port is defined by the system. I don't use specific port
I'm in flutter 3.22.3 (cf Flutter Doctor output)

Hi @redDwarf03, can you try specifying a specific port for your application to see if you still experience this issue?
Can you also upgrade to stable 3.24.0 to see if you still experience this?


RouteNotFound in version 1.0 beta 3

is there a way of handling when users input an incorrect path to redirect to a default 404 page?
RouteNotFound seems to be avaliable in 0.13.0 but I see no mention of it in the 1.0 beta documentation

Just write <Route path="*" component={NotFound} /> as last route and it will catch all non-existing routes and render your 404 component. But yea, it is missing from the docs, I found it in examples: https://github.com/rackt/react-router/blob/master/examples/master-detail/app.js#L157

Thanks for the comment here, @eXtreme ! :)