Different behavior on amd64 and arm

Hi, I'm trying to use this package on arm devices, but I found inconsistent behavior on arm and amd64 platforms, what's the reason for this?
This is the test code
import constriction
import numpy as np

message = np.array([10, 10], dtype=np.int32)

entropy_model = constriction.stream.model.QuantizedLaplace(
            -20, 20 + 1
        )

encoder = constriction.stream.queue.RangeEncoder()
encoder.encode(message, entropy_model, np.array([10., 10.]), np.array([10., 0.]))

compressed = encoder.get_compressed()
print(f"compressed representation: {compressed}")
print(f"(in binary: {[bin(word) for word in compressed]})")

decoder = constriction.stream.queue.RangeDecoder(compressed)
decoded = decoder.decode(entropy_model, np.array([10., 10.]), np.array([10.,  0.]))
assert np.all(decoded == message) # (verifies correctness)

On amd64
compressed representation: [2042752375]
(in binary: ['0b1111001110000011110110101110111'])

On arm
thread '<unnamed>' panicked at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/probability-0.20.3/src/distribution/laplace.rs:22:9:
assertion failed: b > 0.0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Traceback (most recent call last):
  File "test_script.py", line 13, in <module>
    encoder.encode(message, entropy_model, np.array([10., 10.]), np.array([10., 0]))
pyo3_runtime.PanicException: assertion failed: b > 0.0
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
    from apport.fileutils import likely_packaged, get_recent_crashes
  File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in <module>
    from apport.report import Report
  File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in <module>
    import apport.fileutils
  File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in <module>
    from apport.packaging_impl import impl as packaging
  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in <module>
    import apt
  File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in <module>
    import apt_pkg
ModuleNotFoundError: No module named 'apt_pkg'

Original exception was:
Traceback (most recent call last):
  File "test_script.py", line 13, in <module>
    encoder.encode(message, entropy_model, np.array([10., 10.]), np.array([10., 0]))
pyo3_runtime.PanicException: assertion failed: b > 0.0

The full traceback is
thread '<unnamed>' panicked at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/probability-0.20.3/src/distribution/laplace.rs:22:9:
assertion failed: b > 0.0
stack backtrace:
   0:       0x7f9d20a7ac - std::backtrace_rs::backtrace::libunwind::trace::heaab0e590535aeb3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:       0x7f9d20a7ac - std::backtrace_rs::backtrace::trace_unsynchronized::h89cc7ae9ebb707d7
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:       0x7f9d20a7ac - std::sys_common::backtrace::_print_fmt::h08c31be18fedf422
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:67:5
   3:       0x7f9d20a7ac - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hc38bcf44d9e857e3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:44:22
   4:       0x7f9d226b04 - core::fmt::rt::Argument::fmt::ha5b752f9cd7ef4a3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/fmt/rt.rs:138:9
   5:       0x7f9d226b04 - core::fmt::write::h9fac187ae7486f3c
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/fmt/mod.rs:1094:21
   6:       0x7f9d208358 - std::io::Write::write_fmt::h239e9fb6296b3a7f
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/io/mod.rs:1714:15
   7:       0x7f9d20a5e0 - std::sys_common::backtrace::_print::h52f67cfa8753b0ab
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:47:5
   8:       0x7f9d20a5e0 - std::sys_common::backtrace::print::hdea7481e2c957a93
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:34:9
   9:       0x7f9d20b958 - std::panicking::default_hook::{{closure}}::h7c36fa733369c49e
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:270:22
  10:       0x7f9d20b680 - std::panicking::default_hook::h303eee75f9a8f6a8
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:290:9
  11:       0x7f9d20bf1c - std::panicking::rust_panic_with_hook::h270c94381ec34744
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:707:13
  12:       0x7f9d20bda4 - std::panicking::begin_panic_handler::{{closure}}::h3653e3502bcc1625
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:597:13
  13:       0x7f9d20ac90 - std::sys_common::backtrace::__rust_end_short_backtrace::h6b8510f2f024eeeb
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:170:18
  14:       0x7f9d20bb34 - rust_begin_unwind
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:595:5
  15:       0x7f9d0fe4a4 - core::panicking::panic_fmt::ha96945d7a1b20293
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/panicking.rs:67:14
  16:       0x7f9d0fe514 - core::panicking::panic::h8f06a2df29fa4962
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/panicking.rs:117:5
  17:       0x7f9d11f308 - probability::distribution::laplace::Laplace::new::haefeb509845cc871
                               at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/probability-0.20.3/src/distribution/laplace.rs:22:9
  18:       0x7f9d119a44 - constriction::pybindings::stream::model::QuantizedLaplace::new::{{closure}}::h5e7236efc8092f4a
                               at /home/user/repos/constriction/src/pybindings/stream/model.rs:544:44
  19:       0x7f9d161b7c - <constriction::pybindings::stream::model::internals::ParameterizableModel<(P0,P1),M,F> as constriction::pybindings::stream::model::internals::Model>::parameterize::h135fd1ad8427458f
                               at /home/user/repos/constriction/src/pybindings/stream/model/internals.rs:249:35
  20:       0x7f9d17476c - constriction::pybindings::stream::queue::RangeEncoder::encode::h7a9429b10f1006e7
                               at /home/user/repos/constriction/src/pybindings/stream/queue.rs:314:13
  21:       0x7f9d175934 - constriction::pybindings::stream::queue::_::<impl constriction::pybindings::stream::queue::RangeEncoder>::__pymethod_encode__::hb8e05b89a123d73c
                               at /home/user/repos/constriction/src/pybindings/stream/queue.rs:43:1
  22:       0x7f9d0ff204 - pyo3::impl_::trampoline::fastcall_with_keywords::{{closure}}::he0112aa3b1e49083
                               at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.19.2/src/impl_/trampoline.rs:41:29
  23:       0x7f9d0ff10c - pyo3::impl_::trampoline::trampoline::{{closure}}::h9f46c71dbb4a44d4
                               at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.19.2/src/impl_/trampoline.rs:181:54
  24:       0x7f9d15b494 - std::panicking::try::do_call::hd5234df960a8f95d
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:502:40
  25:       0x7f9d15b720 - __rust_try
  26:       0x7f9d15b268 - std::panicking::try::haeac5d692bf46066
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:466:19
  27:       0x7f9d115570 - std::panic::catch_unwind::h2b95655acc141454
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panic.rs:142:14
  28:       0x7f9d0fed68 - pyo3::impl_::trampoline::trampoline::h82d7e8a0b17fbbdf
                               at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.19.2/src/impl_/trampoline.rs:181:9
  29:       0x7f9d140a94 - pyo3::impl_::trampoline::fastcall_with_keywords::h45c8d979f3ca1f26
                               at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.19.2/src/impl_/trampoline.rs:41:13
  30:       0x7f9d174a48 - constriction::pybindings::stream::queue::_::<impl pyo3::impl_::pyclass::PyMethods<constriction::pybindings::stream::queue::RangeEncoder> for pyo3::impl_::pyclass::PyClassImplCollector<constriction::pybindings::stream::queue::RangeEncoder>>::py_methods::ITEMS::trampoline::h905700428ec8b158
                               at /home/user/repos/constriction/src/pybindings/stream/queue.rs:43:1
  31:           0x488db8 - _PyMethodDescr_FastCallKeywords
  32:           0x512714 - _PyEval_EvalFrameDefault
  33:           0x50b47c - _PyEval_EvalCodeWithName
  34:           0x50dd70 - PyEval_EvalCode
  35:           0x616f84 - <unknown>
  36:           0x617070 - PyRun_FileExFlags
  37:           0x61844c - PyRun_SimpleFileExFlags
  38:           0x6494c8 - <unknown>
  39:           0x649b00 - _Py_UnixMain
  40:       0x7f9db946e0 - __libc_start_main
                               at /build/glibc-4fr630/glibc-2.27/csu/../csu/libc-start.c:310
  41:           0x5aef1c - <unknown>
Traceback (most recent call last):
  File "test_script.py", line 13, in <module>
    encoder.encode(message, entropy_model, np.array([10., 10.]), np.array([10., 0]))
pyo3_runtime.PanicException: assertion failed: b > 0.0
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
    from apport.fileutils import likely_packaged, get_recent_crashes
  File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in <module>
    from apport.report import Report
  File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in <module>
    import apport.fileutils
  File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in <module>
    from apport.packaging_impl import impl as packaging
  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in <module>
    import apt
  File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in <module>
    import apt_pkg
ModuleNotFoundError: No module named 'apt_pkg'

Original exception was:
Traceback (most recent call last):
  File "test_script.py", line 13, in <module>
    encoder.encode(message, entropy_model, np.array([10., 10.]), np.array([10., 0]))
pyo3_runtime.PanicException: assertion failed: b > 0.0

Thanks!

Thank you for reporting! On arm, are you using the precompiled constriction package from pypi (for new Macs with arm64 chips) or did you compile constriction from source? If you compiled from source, did you compile in --release mode? The error message that you see should appear in a debug build but it should not appear in a release build (and the official packages on pypi should all be release builds unless I messed something up in the CI).
In case you indeed compiled from source: I'd be happy to provide precompiled python packages for your platform going forward, but I'd need someone to test them, at least initially. Would you mind telling me what platform you're developing for and would you consider testing a precompiled python package on it?
Background
The second symbol in your example is encoded with a Laplace distribution with parameter b = 0.0, which is not a well-defined distribution (the pdf of a Laplace distribution is $p(x\mid\mu,b)=\frac {1}{2b}e^{-|x-\mu |/b}$, so $b=0$ would lead to a division by zero). The Laplace distribution is implemented in the probability crate, which checks for b > 0.0 using a should! macro, which is defined to be equivalent to debug_assert!. Unless special compiler flags are used, debug_assert! only checks in debug builds and is ignored in release builds.
Notes to Self
We should at least document that the Laplace distribution requires b > 0.0, and maybe the python API should check for it even in release builds. In fact, the provided example works on amd64 only by coincidence. It would fail to reconstruct the original message if we change the second symbol in message to anything other than 10 because probability—justifiably—does not provide a valid quantile function for Laplace distributions with b = 0.0.

Thanks for your repley!
I compiled from source following

compile in release mode (i.e., with optimizations) and run the benchmarks: cargo bench

and

build the Python module: poetry run maturin develop --features pybindings

Because I am pretty new to rust, I am not very sure whether I compiled the package in release mode at that moment.
Unfortunately I dont have the original device to test the solution now. If the behavior is reproduciable on other platform in debug mode, I think this may be the main reason.
By the way, when $b=0$, can I suppose the decode result is $\mu$ ?  Is this a correct workaround?

I make another test on amd64
import constriction
import numpy as np

message = np.array([10, 5, 6], dtype=np.int32)

entropy_model = constriction.stream.model.QuantizedLaplace(
            -20, 20 + 1
        )

encoder = constriction.stream.queue.RangeEncoder()
encoder.encode(message, entropy_model, np.array([10., 10., 10.]), np.array([10., 0., 0.]))

compressed = encoder.get_compressed()
print(f"compressed representation: {compressed}")
print(f"(in binary: {[bin(word) for word in compressed]})")

decoder = constriction.stream.queue.RangeDecoder(compressed)
decoded = decoder.decode(entropy_model, np.array([10., 10., 10.]), np.array([10.,  0., 0.]))

print(decoded)
assert np.all(decoded == message) # (verifies correctness)

the result is
compressed representation: [2042752312  556892819]
(in binary: ['0b1111001110000011110110100111000', '0b100001001100011000001010010011'])
[10  5  6]

May be there is some fallback when $b=0$?

You are right, leakily quantized Laplace distributions with $b=0$ do actually work in release builds. I can't reproduce my tests where these failed, maybe I accidentally tested in debug mode myself.

I compiled from source following

compile in release mode (i.e., with optimizations) and run the benchmarks: cargo bench

and

build the Python module: poetry run maturin develop --features pybindings

Because I am pretty new to rust, I am not very sure whether I compiled the package in release mode at that moment.

This compiles in debug mode (i.e., it will result in a python package that contains more checks and fewer run-time optimizations). This explains the difference in behavior between your two builds.
(For completeness, if you want to compile in release mode, use: poetry run maturin develop --features pybindings --release; I updated the readme accordingly.)
I'm a bit unsure what the conclusion should be. On the one hand, one could interpret a Laplace distribution with $b=0$ as a delta distribution, and one could argue that a delta distribution should work with our leaky quantizer in most cases (see below) because the quantizer integrates the delta distribution over a finite interval, and the leakiness adds some small nonzero probability mass even if the integral does not contain the delta peak. And it indeed seems to work in experiments.
On the other hand, there are two reasons against allowing $b=0$ for Laplace distributions:

parity with the rust API: while all provided precompiled python modules are compiled in release mode, users of the rust API will probably develop in debug mode, and there the probability crate (which is not under my control) forbids $b=0$ (and I think that's the right thing to do for a general purpose probability crate).
There's an edge case where quantizing a delta distribution is not well-defined: when the delta peak is right at the boundary between two bins. In this case, when the leaky quantizer integrates over one of the two adjacent bins, it's not clear whether the peak should be counted towards the probability mass. As far as I can tell, the way the Laplace distribution is implemented in the probability crate, it should evaluate 0.0 / 0.0 for this case on this line, which should result in NaN for both debug and release builds. Weirdly, I can't manage to trigger this issue in practice, so it seems like it's not an issue, but I want to understand why it's not an issue before relying on it.

Request for feedback
To help me decide, could you give me some more background on why you tested with a Laplace distribution with $b=0$? Did this come up in a real use case or were you deliberately coming up with edge cases for stress testing? In other words, would it suffice for your use case if constriction enforced $b>0$ and if this requirement was documented in the python API reference, or would it make your life easier if $b=0$ was accepted and interpreted as a delta distribution?

Thanks for your explanations! I am doing some research on Cool-Chic and encountered the case $b=0$. For my use case, interpreting a Laplace distribution as a Delta distribution is useful when $b=0$. But I think these two reasons against allowing $b=0$ are reasonable. Perhaps adding some options is a good alternative? For example, add a strict=true option in constriction.stream.model.QuantizedLaplace to enforce the check that $b>0$ and strict=false for more flexible interpretation.

Thanks for the background information. I like the idea about a strict=true argument to QuantizedLaplace, but I decided against it for the following reasons (this list is not meant as criticism, it's just to document and communicate my reasoning):

I think it would add unnecessary complexity to the python API where a simpler solution exists (see below);
it would still break the promise that the python API is a subset of the rust API, and would thus prevent users from porting python prototypes to exactly equivalent rust, at least for rust debug builds; and
it relies on somewhat brittle behavior that might break, e.g., with future versions of the probability crate (which are out of my control).

Proposed Solution
The problem of $b=0$ can be easily avoided by adding some small regularization (e.g., 1e-16) to the scale parameter. I added this recommendation to the python API documentation (e.g., here), and I added unit tests to assert that quantizing continuous distributions with even much smaller scales behaves as expected without any numerical issues.
Regarding Precompiled Packages for arm
Unrelated to the specific issue reported here, please let me know if you'd be willing to test a precompiled python package for your computer architecture so I can upload official pip packages to pypi going forward. This would make things easier also for other people with your compute architecture. I'd need to know your host triple to do this (i.e., what rustc --version --verbose says after "host").

Thanks for your reply! Adding a small regularization is a good idea. As in previous comment, I don't have access to that device for now. If I get more detailed information, I will update the information here.

Hi, I have got the original device, and I would like to know if you can provide a precompiled version  now. I would be happy to do some testing. The system info is
rustc 1.77.1 (7cf61ebde 2024-03-27)
binary: rustc
commit-hash: 7cf61ebde7b22796c69757901dd346d0fe70bd97
commit-date: 2024-03-27
host: aarch64-unknown-linux-gnu
release: 1.77.1
LLVM version: 17.0.6

The device is a Jetson nano and the recommanded version of python is 3.6. I found release v0.2.4 support 3.6 but failed to install it. Is it feasible to compile a newer version to the platform?
Thanks in advance!


docs: Plugins

Add spec field to Definition to allow for documenting of complex types

Signed-off-by: John Andersen<EMAIL_ADDRESS>

Codecov Report

Merging #87 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #87      +/-   ##
=========================================
+ Coverage    91.5%   91.5%   +<.01%
=========================================
  Files          50      50
  Lines        3319    3320       +1
  Branches      382     382
=========================================
+ Hits         3037    3038       +1
- Misses        224     227       +3
+ Partials       58      55       -3

Impacted Files
Coverage Δ

dffml/df/types.py
81.81% <100%> (+0.18%)
:arrow_up:

dffml/operation/output.py
45.67% <100%> (ø)
:arrow_up:

dffml/source/source.py
82.08% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b257fb...43294ab. Read the comment docs.


Revert case changes to titles in listings

Changes in this PR:
Revert case changes to titles in listings
Trello card / Rollbar error (etc)
https://trello.com/c/6SUqtJGI/1444-eui-design-review-of-current-site
Screenshots of UI changes:
Before

After

[ ] Requires env variable(s) to be updated

 [EUI] Design Review of current site


wttr.in Let’s Encrypt certificate just expired

The certificate on https://wttr.in just expired. There should be a cron task on the server to run certbot renew to ensure this cert is always current. This should help.
Thanks for running this, it’s amazing 😁

Actually, we have a crontask for that, but there was some misconfiguration in this case. Thank you for reporting!


Consistently reference injector services in config

At the moment we're using different ways to name injectable services:

Short concrete class names without namespaces (FormSchema)
FQCN of PHP interfaces (SilverStripe\Control\Cookie_Backend, SilverStripe\Control\Email\Mailer)
Aliases without a direct corelation to a class (FlysystemPublicAdapter, ErrorHandler)

This will be confusing to SS devs, and make it harder to convince them that DI is a good idea in general.
@sminnee and @tractorcow think service names should be FQCN of PHP interfaces, which means creating those interfaces where they're missing.
Any Injector::inst() uses should refer to the FQCN through a use statement, combined with ::class. Example:
use SilverStripe\Assets\Storage\AssetStore;

$store = Injector::inst()->create(AssetStore::class);

To add to this ,where we need multiple named services based on a common interface we should be using . delimited suffixes. E.g. SilverStripe\Control\Email\Mailer.testmailer.


Cache for open file handles

This is the implementation for the open file handles cache (issue #441)
Please review and let me know if you see any problems with the proposed implementation.
The size of the cache (maximum number of open files) can be set in serverconfig.py with the variable CACHE_MAX_SIZE currently set to 50.
Thanks!
Esther

Build is failing... use python script/run_tests.py to run the same tests that travis does on your local machine

Also the cache doesn't seem threadsafe at all... @jeromekelleher you don't think this is a concern?

This looks good, thanks @eelsther. The majority of this is excellent, and I think we can improve the rest easily enough using the slight restructuring suggested above. I think that encapsulating all the cache functionality into one class will make it easier to see what's going on.
We should also get some unit tests on the cache class, to make sure that it does what it's supposed to do.

Thanks to both of you for the feedback! I am currently doing some fixes taking into accounts your comments. It should be pushed on my branch later today.

This is looking good, thanks @eelsther. I think we need to make the test cases a bit more comprehensive though. We should test a few different scenarios of the cache, like what the cache looks like after adding each file. Do we remove the least recently used, every time? If we re-add the same file, is it treated like a new file? Do we raise an exception if we try to set a max cache size <= 0? What happens if we set the maxCacheSize to a value less than the current size of the cache?

Very clear, thanks @eelsther. I think we're ready to merge, modulo my minor quibbles above. Can you squash the commits down once you've addressed these issues please?

Hi Jerome,
Here are the squashed commits. It also contains some commits from the develop branch because I merged the upstream branch regularly to stay up-to-date
Oddly, I had to do a merge from my own branch before pushing this commit...
Cheers,
Esther

We need to squash this down to one commit  @eelsther. This is done by rebasing against upstream/develop. See http://ga4gh-reference-implementation.readthedocs.org/en/develop/development.html#github-workflow for a quick overview.
There's one small issue I spotted above, which should be resolved also. After that, we're good to go I think!

Sorry, I should have read this part of the documentation before doing anything!
I have now done the rebase against the develop branch, following the instructions in the guide.
Please let me know if there is anything left to be done in terms of rebase/merge (I'm not sure if what I've done is enough in order for the branch to be merged).

Excellent! Thanks @eelsther, I think we're ready to merge. @dcolligan, can you push the green button if you're happy with this please?
+1.


Update dependency workflow should use yarn

Make sure the update deps workflow use yarn

@drptbl can you also have a look please

@fritzschoff @bachstatter LGTM now 👍


fix: allow Truthy values to be returned correctly from translation

Details

This fixes the issue where static common. zipCodeExampleFormat was visible just below the Zip/ Post code.
https://github.com/Expensify/App/assets/47336142/24eb4edb-2017-4888-baa8-39154395a3cd
Fixed Issues

$ https://github.com/Expensify/App/issues/38660
PROPOSAL: https://github.com/Expensify/App/issues/38660#issuecomment-2009381333
Tests / QA Steps

[X] Verify that no errors appear in the JS console

Precondition:

Address is not filled in Private section.

Go to staging.new.expensify.com.
Go to Profile
Click Address.
verify that you do not see common.zipCodeExampleFormat on the screen.

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android: Native
[X] Android: mWeb Chrome
[X] iOS: Native
[X] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[X] MacOS: Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[X] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[X] I verified that all the inputs inside a form are aligned with each other.
[X] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

cc @fedirjh as you were C+ on the offending PR.

A new PR was made here. Closing this PR for now 🙇
@fedirjh, you were assigned as a C+ reviewer in the new PR

@hurali97 you also provided no screenshots as evidence of your testing, which, lacking any explanation or context, is a Rule #2 violation

@roryabraham  I have explicitly added a video of my testing in PR description, if that's not an evidence of testing then I am not sure what is.

My apologies - it was not in the screenshots section of the PR description.


Add Group archive URL to README.

I know this seems minor - but there's education value in reading some of the archives, and they are surprisingly hard to find on Google until you land on a specific thread.

Thanks!


Add desktop shortcut support

Keyboard shortcut
Description

Command or Ctrl + Shift + M
Masks

Command or Ctrl + ,
Settings

Command or Ctrl + N
New Chat

now it's better after bypassing that stupid warning

wait what it doesn't work anymore

its better now


What is this game exactly?

https://github.com/SirCmpwn/TrueCraft/blob/master/README.md

It's a FOSS version of this game: https://minecraft.net/
But it tracks an older version of Minecraft, from around 2011, rather than the newest version. This is for political reasons.


Remove accidental </span> from SSH command output

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/authentication/connecting-to-github-with-ssh/using-ssh-agent-forwarding
What part(s) of the article would you like to see updated?
The first block of code (example output of ssh -v URL command) in Your system must allow SSH agent forwarding section of the article contains an accidental </span> on the 3rd line.
Additional information
No response

@profojak Thank you for opening an issue and linking it to your PR! ✨


Configure CircleCI

Move off Travis to Circle.
Run the entire script on macOS infrastructure.

We're cheating slightly with this implementation,
but seems worth it for speed of build tradeoff:

Use pre-installed XCode for compilers, etc.
Use pre-installed Ruby version.

Related:
https://github.com/thoughtbot/laptop/issues/494

It seemed like some of the longest time spent here was on installing Ruby, which I thought would have been covered by the machine config:
Configuring Ruby ...
rbenv: version `2.4.1' is not installed (set by /Users/distiller/laptop/.ruby-version)
Downloading ruby-2.4.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.4/ruby-2.4.1.tar.bz2
Installing ruby-2.4.1...
ruby-build: use readline from homebrew
Installed ruby-2.4.1 to /Users/distiller/.rbenv/versions/2.4.1

I think I'm going to try echoing a .ruby-version into the CI box.

I think I'm going to try echoing a .ruby-version into the CI box.

That did not do the trick. Think I'm going to merge and then see if we can optimize that post-https://github.com/thoughtbot/laptop/pull/502


fix(config): typo (but in archive branch)

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area documentation
What this PR does / why we need it:
oops (but in archive branch)
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 331a9f380ae485425c591ea4d67fb0509a2f151f

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Added svg mimetype for favicons.

Closes #232.

:+1:

The failing test isn't related to the PR. But it would be kind if you fix the failing test anyway. The penny-arcade.com website seam to have switched to https:
-''
+''


Why is the final bundle so big?

Hi, i'm using this package for while and looking at the code and dependencies can't figure out why the final bundle has 79.5kb minified.
Can someone help me to figure out why?
Thanks!

Is there anyway I could only import what I only need?
I've checked the bundled size and it is importing everything that the component offers.
How do I modify it to only import Photoshop or Sketch for example?

@davidmandeeli Treeshaking isn't supported in this version of vue-color. You can see this for something I hacked together though.

This library should be tree shakeable, 100%. It's way too big.

Uow man, thanks, it helps a lot!
I'm using the Chrome picker was reduced from 80kb to 27kb, the +14kb it's for tinycolor dependency.


[share_plus_macos] bump Flutter SDK version constraint

To fix:
Uploading...
pubspec.yaml allows Flutter SDK version prior to 1.20.0, which does not support having no `ios/` folder.
Please consider increasing the Flutter SDK requirement to ^1.20.0 or higher (environment.sdk.flutter) or create an `ios/` folder.

@miquelbeltran is this why you always publish first and merge later? :laughing:

yes, so if there's anything wrong with the release I can fix it before merging ;)


stringify the fields inside the attr field which were int and  boolean

stringify the fields inside the attr field which were int and  boolean, since unmarshalling of these fields were resulting in errors
json: cannot unmarshal number into Go value of type string
few 'usagePolicy' was set to {} which was set to null
Signed-off-by: chethan-zededa<EMAIL_ADDRESS>

Two things:

Need to understand how to handle the transition with existing model files; If the user has saved a model file using zcli model export-manifest, can it be imported? How do we prevent the creating of a new enterprise to fail (when a set of default models are added)?
We have a script in EVE (pkg/debug/spec.sh) which generates in initial model file. That scipt needs to be changed.

Do we have a document or reference indicating why we need to change this stringification?

it's been a while(like 2-3 months or more) zedcloud started jsonpb marshalling and unmarshalling, jsonpb operations are a bit strict wrt to these kind of type mismatch.

for an existing exported model file, it will continue to fail like today, even today if user tries create or update the model with type mismatch zedcloud will not process the request.
I was not aware of that script, let me take a look of it.

there is no document as such, as I said, model creates of such models were failing during enterprise onboard.

We have a script in EVE (pkg/debug/spec.sh) which generates in initial model file. That scipt needs to be changed.

That change just got merged @eriknordmark -- agree with the rest of your comments. Would love to hear from @chethan-zededa


URL No Longer Exists

The link that is this page refers is no longer exists. I believe that it should refer the latest OData documentation.

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

ID: 1bc2d41b-a16e-2eb8-5acf-963df0a6020b
Version Independent ID: 337d82f5-41e3-05d0-bde4-1ea6bd61b372
Content: Using Filter Expressions in OData URIs - Business Central
Content Source: dev-itpro/webservices/use-filter-expressions-in-odata-uris.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: jswymer

Thanks for catching this. The issue will be fixed with the next doc refresh.


OTAA Join Accept not received by STM32 node through the Gateway

I am currently playing around with LoRaWAN and TTN and try to getting SX1276 Modem (nice RF) to work.
I implemented on STM32l4 board. When OTAA join starts the device gets registered on the TTN console but i never receive the join accept back on my node. So with both MCU’s the join hangs up after EV_JOINING event.
I fiddled around with the timer settings and also change in joining time but it can't joined to node and continuously open Rx window1 and Rx window2 but Rx timeout occurs.
But ABP is properly work.
Could it be possible that this is a problem on the gateway’s side? Or are there any other possibilities that cause those problem? (In the forum i also found problems/solutions regarding the datarate in the RX1 and RX2 windows that weren’t LoRa compliant but according to the change log they resolved that a while ago so it couldn’t be the source of my problem).

ARM Internal Ref: IOTCELL-2453


updated migration script

Coverage increased (+0.05%) to 76.109% when pulling 8f0d2321256cab59394aff7e6881c79cc34e3939 on migration-script into 86d25cb73ece387f02bc42ddb29b22405c0e74ce on master.

Coverage increased (+0.05%) to 76.109% when pulling a7e02428c48442091ea861387348564a5d21f632 on migration-script into 86d25cb73ece387f02bc42ddb29b22405c0e74ce on master.

Coverage increased (+0.05%) to 76.109% when pulling 13fef9e61a2b85f63da874fa99c4bf3672855627 on migration-script into 86d25cb73ece387f02bc42ddb29b22405c0e74ce on master.

Coverage increased (+0.05%) to 76.109% when pulling 13fef9e61a2b85f63da874fa99c4bf3672855627 on migration-script into 86d25cb73ece387f02bc42ddb29b22405c0e74ce on master.


[NavigatorIOS] back button and componentWillReceiveProps

I have 2 components: HomeScreen (initialRoute) and SettingScreen. When the right nav button is clicked, the SettingScreen is pushed to the navigator.
The problem is whenever the back button is clicked, the componentWillReceiveProps function in the HomeScreen triggers. Is this behavior intentional?

@igodzp Any updates?

Unfortunately we don't have anybody working on NavigatorIOS, Navigator is the recommended way to go. I can't comment on whether or not this is intended, but if you can point to why this is a problem for you and explain your use case then we can discuss further! Is it causing issues for you? And is this still happening? :smile: Sorry for not getting back to you more quickly. Feel free to ping me and I can reopen this if this is causing you problems.


Maximal Rectangle

Description
Given a rows x cols binary matrix filled with 0's and 1's, find the largest rectangle containing only 1's and return its area.
DSA Problem
https://leetcode.com/problems/maximal-rectangle/description/

Hey @Dhandeep10 interested to work on this issue if possible can you assign it to me ?

hey @iamdestinychild i am interested in this. Can you assign this to me under hacktoberfest.

@iamdestinychild completed this under #20 please merge that


Fixes app not redirecting when token is expired

The expiry handler is not triggering a redirect when the token is expired resulting in the page hanging in a broken state when a token is invalid or expired. This PR fixes this by forcing a redirect.

When debugging the node server, it is evident that the current history.push is not reaching the node middleware. Changing this to a hard refresh using the window object allows node to pick it up.


WARNING: Could not download DASH manifest: HTTP Error 403: Forbidden

Hello, I'm read all duplicate issues. But this issue very important. I'm using youtube-dl 2015.07.21 version. Warnings / errors do not want to hide.

Duplicate of #5118.


org.owasp.dependencycheck.analyzer.exception.AnalysisException: Failed to request component-reports Unexpected response; status: 400

Describe the bug
Dependency Check fails with a 400 error when requesting something from the Sonatype OSS Index, leading to fewer CVEs found in the report and warnings in the job log like An error occurred while analyzing requirements.txt (Sonatype OSS Index Analyzer).
Version of dependency-check used
The problem occurs using version 9.2.0 of the CLI -- both docker and brew packaging
Log file
https://gist.github.com/francisATgwn/ece673ba589b75110a3aeecc9354708e
To Reproduce
Steps to reproduce the behavior:

Use dependency check CLI with this CLI invocation

$ /usr/share/dependency-check/bin/dependency-check.sh --dbDriverName org.postgresql.Driver --connectionString "$DEPENDENCY_CHECK_CONNECTION" --dbUser "$DEPENDENCY_CHECK_USER" --dbPassword "$DEPENDENCY_CHECK_PASSWORD" --nvdApiKey "$NIST_NVD_API_KEY" --project $CI_PROJECT_NAME --out . --scan . --enableExperimental --format JUNIT --junitFailOnCVSS 4 --format HTML --failOnCVSS 4 --nodeAuditSkipDevDependencies $( [[ -e dependency-check-suppression.xml ]] && echo '--suppression dependency-check-suppression.xml' || echo '' )

Expected behavior

CVEs from Sonatype OSS Index are included in the report
[WARN] An error occurred while analyzing '...' (Sonatype OSS Index Analyzer). does not appear in log
no HTTP 400 resulting in org.owasp.dependencycheck.analyzer.exception.AnalysisException: Failed to request component-reports appearing in the Analysis Exceptions section of the HTML report

Additional context
This does not happen when run with the 8.4.3 docker image from the same environment on the same project at the same time.
The 8.4.3 CLI invocation is similar to the 9.2.0 invocation:
$ /usr/share/dependency-check/bin/dependency-check.sh --project $CI_PROJECT_NAME --out . --scan . --enableExperimental --format JUNIT --junitFailOnCVSS 4 --format HTML --failOnCVSS 4 --nodeAuditSkipDevDependencies --data dependency-check-data $( [[ -e dependency-check-suppression.xml ]] && echo '--suppression dependency-check-suppression.xml' || echo '' )

dependency-check-8.4.3-report.html.txt
dependency-check-9.2.0-report.html.txt

Having the same problem but only for some projects.
problematic requirements file: requirements.txt
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/init.py' (Sonatype OSS Index Analyzer).
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/domain/api/facilities/init.py' (Sonatype OSS Index Analyzer).
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/domain/api/departments/init.py' (Sonatype OSS Index Analyzer).
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/domain/api/contacts/init.py' (Sonatype OSS Index Analyzer).
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/domain/api/api_keys/init.py' (Sonatype OSS Index Analyzer).
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/domain/api/init.py' (Sonatype OSS Index Analyzer).
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/domain/init.py' (Sonatype OSS Index Analyzer).
[WARN] An error occurred while analyzing '/Users/[CUT]/Projects/[CUT]/app/cli/init.py' (Sonatype OSS Index Analyzer).
[INFO] Finished Sonatype OSS Index Analyzer (4 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Known Exploited Vulnerability Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (0 seconds)
[INFO] Finished Unused Suppression Rule Analyzer (0 seconds)
[INFO] Analysis Complete (7 seconds)
[INFO] Writing JSON report to: /Users/[CUT]/Projects/[CUT]/./dependency-check-report.json
[INFO] Writing HTML report to: /Users/[CUT]/Projects/[CUT]/./dependency-check-report.html
[ERROR] Failed to request component-reports
[ERROR] Failed to request component-reports
[ERROR] Failed to request component-reports
[ERROR] Failed to request component-reports
[ERROR] Failed to request component-reports
[ERROR] Failed to request component-reports
[ERROR] Failed to request component-reports
[ERROR] Failed to request component-reports

@jeremylong any advice of where to look for this regression? the diff between 9.1.0 ... 9.20 is most dependabot and a new unrelated(?) analyzer.

This issue is also happening with version 10.0.1.  It appears to be an issue with connecting to Sonatype OSS.  The issue is happening if the OSS Variables (user, password, url) are supplied or not.  I saw two issues with the OSS connection.
/opt/dependency-check/bin/dependency-check.sh --out . -s . -f HTML -f JSON --enableExperimental --exclude '**/.sonar/**' --exclude '**/.cache/**' -l tmp.log

First error which spams the output for just about every node_module file:
[WARN] An error occurred while analyzing '<full path>/node_modules/karma/static/context.js' (Sonatype OSS Index Analyzer).

Second Error:
[ERROR] Failed to request component-reports

Log Message:
DEBUG - Error requesting component reports
java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - Error at index 1 in: "A%"
        at java.base/java.net.URLDecoder.decode(URLDecoder.java:237)
        at java.base/java.net.URLDecoder.decode(URLDecoder.java:147)
        at org.sonatype.goodies.packageurl.PercentEncoding.decode(PercentEncoding.java:78)
        at org.sonatype.goodies.packageurl.PackageUrlParser.parseName(PackageUrlParser.java:135)
        at org.sonatype.goodies.packageurl.PackageUrlParser.parse(PackageUrlParser.java:106)
        at org.sonatype.goodies.packageurl.PackageUrl.parse(PackageUrl.java:293)
        at org.owasp.dependencycheck.analyzer.OssIndexAnalyzer.parsePackageUrl(OssIndexAnalyzer.java:203)
        at org.owasp.dependencycheck.analyzer.OssIndexAnalyzer.lambda$null$1(OssIndexAnalyzer.java:223)
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
        at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
        at java.base/java.util.TreeMap$KeySpliterator.forEachRemaining(TreeMap.java:3064)
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
        at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
        at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
        at org.owasp.dependencycheck.analyzer.OssIndexAnalyzer.lambda$requestReports$3(OssIndexAnalyzer.java:225)
        at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:992)
        at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
        at org.owasp.dependencycheck.analyzer.OssIndexAnalyzer.requestReports(OssIndexAnalyzer.java:221)
        at org.owasp.dependencycheck.analyzer.OssIndexAnalyzer.analyzeDependency(OssIndexAnalyzer.java:136)
        at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)
2024-07-05 09:18:40,386 org.owasp.dependencycheck.AnalysisTask:90

Java Version:
openjdk 17.0.11 2024-04-16 LTS
OpenJDK Runtime Environment (Red_Hat-<IP_ADDRESS>.9-3) (build 17.0.11+9-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-<IP_ADDRESS>.9-3) (build 17.0.11+9-LTS, mixed mode, sharing)

I had the same issue too with the requirements.txt. The reason was blank lines in this file. Try to remove them.

It means you have a different error cause than Francis. "An error occurred while analyzing requirements.txt (Sonatype OSS Index Analyzer)."
I could reproduce it very easily. Adding a new empty line (in between, not at the end of the requirements.txt) causes the above mentioned error.

If that truly is the cause of my error, which I haven't verified yet, then this is a bug report. My requirements.txt is generated by pip-compile and tools that read it should be resilient to the format it writes.

I have upgraded to 10.0.3 and confirmed the error still occurs for me. I have also confirmed @andriyzhurba comment that removing any blank lines in requirements.txt resolves the issue.
I believe that the ODC code which reads requirements.txt should be resilient to the presence of blank lines. In my case, these blank lines are generated by pip-compile, a widely used tool in the python community.

Can a sample requirements.txt be provided that contains spaces?

@jeremylong It's pretty easy.
This file will work:
requests==2.28.2
boto3==1.26.105
aws_lambda_powertools==2.26.0
aws_xray_sdk==2.12.1
langdetect==1.0.9
langchain==0.1.20
openai==1.13.3
orjson==3.9.15
numpy==1.26.4
types-orjson==3.6.2
openai==1.13.3
This will run into error:
requests==2.28.2
boto3==1.26.105
aws_xray_sdk==2.12.1
langdetect==1.0.9
langchain==0.1.20
orjson==3.9.15
numpy==1.26.4
types-orjson==3.6.2
openai==1.13.3

Here's an example generated by pip-compile. Just removing the blank line was sufficient to avoid the error, so I don't think the other non-package lines cause a problem but including it for completeness:
#
# This file is autogenerated by pip-compile with Python 3.12
# by the following command:
#
#    pip-compile
#
--index-url https://REDACTED

[certifi](https://pypi.org/project/certifi/)==2024.6.2
    # via sentry-sdk
[sentry-sdk](https://pypi.org/project/sentry-sdk/)==2.7.1
    # via sentry-python-example (pyproject.toml)
[urllib3](https://pypi.org/project/urllib3/)==2.2.2
    # via sentry-sdk

fix will be included in the next release.


Support G5 command

G5 command is going to be supported by GRBL soon, would be nice to be able to generate those from juicy-gcode
https://github.com/terjeio/grblHAL/issues/30

A command line argument is added to the g5 branch: -b. When it presents, the beziers are generated as G5 commands instead of being interpolated by arcs.

I have just tried the new G5-branch on the attached file, The output only generates one small section of G05 command.
This is the command that I used : juicy-gcode 2.svg -b -o 2.nc
G5 test.zip
In the master branch, I was able to use the same file and generated a good match with bi-arcs, so I think the file is ok.
Am I missing something here ?

Oh, I forgot the recursive step... Could you try it again please?

That looks perfect ! Can we leave this open for a while, I still need to test this some more ( on real hardware )

If it works in simulation, it should be OK on real hardware as well. I'm
going to merge the g5 branch to master and make a new release.
On Mon, May 25, 2020, 6:16 PM ithinkido<EMAIL_ADDRESS>wrote:

That looks perfect ! Can we leave this open for a while, I still need to
test this some more ( on real hardware )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/domoszlai/juicy-gcode/issues/7#issuecomment-633639919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACAQ4GGW74AJU4SX7422WH3RTKKXLANCNFSM4NJJZ5RA
.

A small warning: you get upside down gcode unless you use -m

Ok , thanks for the warning.

a quick simulation

Nice! I close this issue now. The g5 branch will be merged to master and released, so the feature will be available later


fix kubectl get httproute

The name of httproute is not correct.
The last line is automatically edited by GitHub's online editor, likely to be some uncompatible whitespaces.

This is already in the current article. #please-close

https://github.com/MicrosoftDocs/azure-docs/commit/1e699b09166da839253e606d1e1b01b989541268


ResourcesScanner doesn't work since 0.9.10

Since 0.9.10 ResourcesScanner no longer works and will return all .class resources along. Filtering in acceptsInput in there has become useless since it's OR-ed with acceptResult, whose resultFilter is Predicates.alwaysTrue() by default.
Culprit commit is the following:
2f3294c FilterBuilder check for matches for each resource on both file relative path (with /) and fqn (with .)
I never knew what was the motivation to replace slashes with dots in the first place (producing fqns over paths); I agree we should definitely be able to filter on paths. Just not sure it was the rightest way to introduce that (especially with respect to the evaluation overhead which others reported).
If time allows I'd gladly contribute something, but I think a first step would be to revert what has happened there anyway. Any opinion or rationale?
Cheers,
Mika

Just found the same bug today, exactly as mkgl said:

Since 0.9.10 ResourcesScanner no longer works and will return all .class resources along. Filtering in acceptsInput in there has become useless since it's OR-ed with acceptResult, whose resultFilter is Predicates.alwaysTrue() by default.

works after 0.9.10


Adds Pre-Build Event for VS2019

Closes #278
Runs ($SolutionDir)../../VcpkgDeps.bat as a Pre-Build Event to install glew/physfs dependencies prior to trying to build.

The batch file is being run for both NA2D and test projects. Since the installs are per machine we can try to only run it on NAS2D since it's the base project.

I double-checked the file itself. In cases where PLATFORM isn't defined it explicitly runs both the x64 and x86 versions.

Oh, I meant after the initial AppVeyor config to run the batch file, it gets run twice more, once for NAS2D, and then again for the test project (until the later edit to remove it). Each time it goes through each dependency and outputs a large block of text.
In terms of the PLATFORM environment variable, it will be defined throughout the AppVeyor run. I checked the latest run, and there is only output for a single platform. The duplication is simply coming from the extra calls to run the batch file multiple times.


[5.2] PostgresProcessor::processInserGettId | array cast fails to get Id when PDO fetch mode is set to PDO::FETCH_CLASS

function processInsertGetId
How to reproduce:

Enable PDO fetch mode set to PDO::FETCH_CLASS choosing it to cast to a Class that does not have the attributes set directly to the object, like Eloquent models that uses the $attributes property
Use processInsertGetId

Description:
Casting the $results[0] to an array having PDO fetch mode set to PDO::FETCH_CLASS and the chosen class implements magic methods to handle attributes getters and setters (like Eloquent Models) the function would throw an error Undefined index {$sequence} on the assignment:
$id = $result[$sequence];

The problem occurs because the given object would be cast to an array that doesn't have the "id" key on its first level of keys.
About the solution:
On my use cases $result is always an object (on any PDO fetch method) but I still tested it because I was not sure I was covering all the use cases.
Feel free to comment, improve or create a test for this function & PR.

Looks good to me. Also you have inspired me #14121 :)


Create real block context without serialization

Description
We need to create a blockifier block context before executing a transaction. For now we're serializing it from our block header but it's not the right way to do it.
Acceptance criteria

The block context is created by using into() by implementing the From trait in both directions.

Can I get on this one ?

Assigned to you, thanks, and welcome !


KAFKA-12708 Rewrite org.apache.kafka.test.Microbenchmarks by JMH

Rewrite org.apache.kafka.test.Microbenchmarks by JMH

This has been done in https://github.com/apache/kafka/pull/16231. Closing.


[Task] Add custom prefix for each configuration package

Is your feature request related to a problem? Please describe.
Currently, every Discord BOT are having the same command prefix - mc.
Which will become messy easily when there's more than one game deployed in the Discord Server.
Describe the solution you'd like
In the configuration package for each game, each BOT should have their own prefix.
Describe alternatives you've considered
N/A
Additional context
Add any other context or screenshots about the feature request here.
N/A

Implemented in https://github.com/VeriorPies/MineCloud/pull/64


Bot talent

Bot arent picking any talent point, possible issue related to the LFG as they cant pickup role ?

you cant manually assign them either

If you give a bot the command 'talents' they will respond with something like Paladin (pvp) (0/7/3) suggesting they have picked a talent spec, but have not actually learned them.  In the characters_talent table, there are no entries for any bot.
They also seem to not use higher-level spells.  Watched a lvl 80 try to heal themselves with Holy Light Rank 1.

i was looking at the table character_spell i looked up some of the spells, they are talents i assigned with the talents 0-0-0 format. but they are not in character_talent table


Burn fusion optimisation

Looking at the tests: https://github.com/cBournhonesque/burn/blob/d770b1f470d734afd79253d082ea9d084a8d5431/crates/burn-fusion/src/stream/execution/tests.rs#L89
it seems like if a segment doesn't find any optimization, the entire segment is executed with no fusion.
But wouldn't it be possible to just execute the first operation and then restart the fusion exploration on the second one?
On the test it looks like another optimization is potentially possible if [op_2] is added in the queue.

Yes, you are right! In fact, the real fix would be to have a start trigger for optimizations instead of always trying them out. It would be more natural and would avoid some bugs that we would have right now if we had more than just one optimization.
For now we're not missing any optimization because all element-wise operations are "start triggers" and all other ops are "stop trigger".


it seems to delete all volumes, not just orphaned

just one volume directory:
root@boot2docker:/mnt/sda1/var/lib/docker/volumes# ls -la
total 12
drwx------    3 root     root          4096 Jun 24 21:21 .
drwxr-xr-x    9 root     root          4096 Jun 24 21:24 ..
drwxr-xr-x    3 root     root          4096 Jun 24 21:21 bd1e586a629637ffb1153847260e63f810c43d7f9f28f382eecacf9f4a5eb749

and as you can see it IS used by a running container:
✗ docker inspect --format '{{.Volumes}}' database                                                                                ruby-2.2.0 (master) deedf83
map[/var/lib/postgresql/data:/mnt/sda1/var/lib/docker/volumes/bd1e586a629637ffb1153847260e63f810c43d7f9f28f382eecacf9f4a5eb749/_data]

now running the script:
✗ docker run -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker:/var/lib/docker --rm martin/docker-cleanup-volumes --dry-run                                                                                ruby-2.2.0 (master) deedf83

Delete unused volume directories from /var/lib/docker/volumes
Would have deleted bd1e586a629637ffb1153847260e63f810c43d7f9f28f382eecacf9f4a5eb749

Directory /var/lib/docker/vfs/dir does not exist, skipping.

Hi, which version of docker are you running on your host?

Should be fixed with 01cbf4b3b2888be094f00aacaf6f36118c05ddf8
docker pull martin/docker-cleanup-volumes

to update to latest image.
Thanks for reporting.


Ring of Aesir + LMB bug + Vedrfolnir's Core

The Loki ring function does not work.

Odin doesn't work either. But Terra Shatterer without a ring alone works as with it. Putting on the Aesir ring does not change anything.

The Odin ring effect does not work on earth crushers from other mods. for example MythicBotany, AIOT Botania. Possibly related to point 2.

If you have mana, pressing LMB with an item in your hand will teleport in the direction of the cursor.

Vedrfolnir's Core - Sources of damage such as cactus, lava, magma, fire, etc. They damage the core at such a rate that any possible mana is destroyed.

I am gonna work on them ASAP. but today i wont be able to finish it.
I already fixed the last two points.
Thank you for telling me about the issues. Please leave any other errors you might run into here as well.

I am thinking of removing the Loki and thor abilities from the ring of aesir because it is way to difficult to integrate everything into  Botania.
I am not completely sure yet, but it could happen

All of the issues are fixed in the currently processing version (1.20.1-<IP_ADDRESS>). It should be available in half an hour.
I will close this issue now.
Please report any further issues ASAP and i will try to fix them ASAP.


remove node-xmpp-tls-connect

WIP
tls-connect was a fix for Node.js < 0.11
Since we don't support Node.js 0.10 anymore and this is potentially insecure let's remove it.

Coverage increased (+0.05%) to 78.757% when pulling 77d266d2436275f60d6d39923119409fd23add01 on remove-node-xmpp-tls-connect into 999acbb9c7840b2828ef18d4ace7f4ae0d860569 on master.

Coverage increased (+0.05%) to 78.757% when pulling c0d04312f20d7e540807e058a171130cd6b0243f on remove-node-xmpp-tls-connect into 999acbb9c7840b2828ef18d4ace7f4ae0d860569 on master.

Coverage increased (+0.06%) to 78.765% when pulling 32ee7489ed2087a62eef58499f55c5cabea67818 on remove-node-xmpp-tls-connect into 999acbb9c7840b2828ef18d4ace7f4ae0d860569 on master.

Coverage increased (+0.06%) to 78.765% when pulling e3a691a39a5c00fa17fbe71bbbfbc1b49cd8b1ad on remove-node-xmpp-tls-connect into 999acbb9c7840b2828ef18d4ace7f4ae0d860569 on master.

Coverage increased (+0.06%) to 78.765% when pulling 68b337e663a57d4a3d52d734b6ec59b177d6d849 on remove-node-xmpp-tls-connect into 999acbb9c7840b2828ef18d4ace7f4ae0d860569 on master.

Coverage increased (+0.06%) to 78.765% when pulling 55b53ca659d16a0c40d20692d3f3926b87dc6e7a on remove-node-xmpp-tls-connect into 999acbb9c7840b2828ef18d4ace7f4ae0d860569 on master.


One Way Collisions in Tilemap

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Manjaro Linux , Godot 2.1.4 stable
Issue description:
When you set Oneway collision in a tile it works well inside Godot, but when u export the game to any plataform, like linux, windows, mac, android the collision change to normal.
Steps to reproduce:
Make a new scene, make your tiles, add a StaticBody2D and a CollisionShape2D or CollisionPolygon2D in your tiles. Set the StaticBody2D One Way Collisior to Direction (0,1) and Max Depth (1) , export your tiles to .tres, .res or .xml. Add a TileMap node in your main scene, draw your tilemap scene put a player int he scene, export the project to any plataform.
Link to minimal example project:
https://drive.google.com/file/d/0By9n8Akl7DQ4OFBDMUNPc1Rtb00/view?usp=sharing

Did you update your export templates too?

i swear i did it before, but i try update the exports again and all work fine now.

Perfect, closing then :)


Running on localhost:1337 always returns the error "Couldn't resolve host. The given remote host was not resolved."

I'm on OSX 10.9.3 and whenever I run a script that hits localhost:1337, I receive this error in my callback:
Couldn't resolve host. The given remote host was not resolved.
If I pass in a function as the options.process parameter, it is called with the correct response from the server.
Regardless of whether the server returns a status of 400 or 200, I receive the same error message.
I have tried using http://<IP_ADDRESS>:1337 and http://localhost:1337 and they both trigger that error message.

I'm experiencing this issue with OSX 10.13.6.
The server is returning 200 along with the correct data but the error variable on the callback is always "Couldn't resolve host. The given remote host was not resolved."


Support for different Ruby paths (FreeBSD)

I’m running puppet bolt from a Mac to connect to FreeBSD servers. I can successfully use command run with bolt, however I’m now trying to run plans to apply manifests and running into errors. My setup:
bolt.yaml
inventoryfile: "./inventory.yaml"
format: human
ssh:
  host-key-check: false
  user: my-user-name

inventory.yaml
groups:
  - name: server1
    nodes:
      - server1.domain.com
    features: ['puppet-agent']

site/profiles/plans/test.pp
plan profiles::test(
  TargetSpec $nodes,
) {

  apply_prep($nodes)

  apply($nodes) {

    file { '/home/my-user-name/test':
      ensure => directory,
    }

  }

}

When I run bolt plan run profiles::test --nodes server1 --debug --run-as root:
…

Starting: task apply_helpers::custom_facts on server1
Authentication method 'gssapi-with-mic' (Kerberos) is not available.
Skipping submission of 'Transport initialize' event because analytics is disabled
Running task apply_helpers::custom_facts with '{"plugins"=>#<Sensitive [value redacted]>, "_task"=>"apply_helpers::custom_facts"}' on [“server1”]
Running task run '#<struct Bolt::Task name="apply_helpers::custom_facts", file=nil, files=[{"name"=>"custom_facts.rb", "path"=>"/Users/oliver/.rvm/gems/ruby-2.3.7/gems/bolt-1.11.0/libexec/custom_facts.rb"}], metadata={"supports_noop"=>true, "input_method"=>"stdin"}>' on server1
Opened session
Executing: mkdir -m 700 /tmp/cccd3e9b-2719-4483-9906-35483efb5594
Command returned successfully
Executing: chmod u\+x /tmp/cccd3e9b-2719-4483-9906-35483efb5594/custom_facts.rb
Command returned successfully
Executing: chmod u\+x /tmp/cccd3e9b-2719-4483-9906-35483efb5594/wrapper.sh
Command returned successfully
Executing: id -g root
stdout: 0
Command returned successfully
Executing: sudo -S -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  chown -R root:0 /tmp/cccd3e9b-2719-4483-9906-35483efb5594
Command returned successfully
Executing: sudo -S -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  /tmp/cccd3e9b-2719-4483-9906-35483efb5594/wrapper.sh
stderr: /tmp/cccd3e9b-2719-4483-9906-35483efb5594/wrapper.sh: /tmp/cccd3e9b-2719-4483-9906-35483efb5594/custom_facts.rb: not found
Command failed with exit code 127
Executing: sudo -S -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  rm -rf /tmp/cccd3e9b-2719-4483-9906-35483efb5594
Command returned successfully
Closed session
{"node”:”server1”,”status":"failure","result":{"_output":"","_error":{"kind":"puppetlabs.tasks/task-error","issue_code":"TASK_ERROR","msg":"The task failed with exit code 127:\n/tmp/cccd3e9b-2719-4483-9906-35483efb5594/wrapper.sh: /tmp/cccd3e9b-2719-4483-9906-35483efb5594/custom_facts.rb:
not found\n","details":{"exit_code":127}}}}
Finished: task apply_helpers::custom_facts with 1 failure in 2.42 sec
Finished: plan profiles::test in 3.36 sec
{
  "kind": "bolt/run-failure",
  "msg": "Plan aborted: run_task 'apply_helpers::custom_facts' failed on 1 nodes",
  "details": {
    "action": "run_task",
    "object": "apply_helpers::custom_facts",
    "result_set": [
      {
        "node": “server1”,
        "status": "failure",
        "result": {
          "_output": "",
          "_error": {
            "kind": "puppetlabs.tasks/task-error",
            "issue_code": "TASK_ERROR",
            "msg": "The task failed with exit code 127:\n/tmp/cccd3e9b-2719-4483-9906-35483efb5594/wrapper.sh: /tmp/cccd3e9b-2719-4483-9906-35483efb5594/custom_facts.rb: not found\n",
            "details": {
              "exit_code": 127
            }
          }
        }
      }
    ]
  }
}

From my understanding, bolt is uploading certain files to the server that it requires to apply the manifest. When these files are attempted to be executed, they fail with the ‘command not found’ error.
These errors seem to be caused by the shebang used in these two files: custom_facts.rb and apply_catalog.rb which both use a shebang of #! /opt/puppetlabs/puppet/bin/ruby as the path to ruby. However, on FreeBSD the path to ruby is /usr/local/bin/ruby. If I manually edit the files to use this path instead, bolt applies the manifest successfully.
The files are like this in both the brew installed and gem installed versions of bolt:
/opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.11.0/libexec/apply_catalog.rb
/opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.11.0/libexec/custom_facts.rb
.rvm/gems/ruby-2.3.7/gems/bolt-1.11.0/libexec/custom_facts.rb
.rvm/gems/ruby-2.3.7/gems/bolt-1.11.0/libexec/apply_catalog.rb

This is the default location for Ruby on FreeBSD, however, I’d have thought that other systems may put Ruby in different paths too. Would it be possible for these files to search a path for Ruby instead of the current hard-coded path?

We are working on a feature that allows you to map task extensions to interpreters which would effectively allow you to override the shebang in the task executable with a transport configuration option. https://tickets.puppetlabs.com/browse/BOLT-146

@olivermussell Bolt 1.13.0 contains a configuration option to override the interpreter defined in the task. Check out the interpreters configuration option https://puppet.com/docs/bolt/latest/bolt_configuration_options.html#global-configuration-options

After updating to bolt 1.13.0 I updated my bolt.yaml file as follows:
inventoryfile: "./inventory.yaml"
format: human
ssh:
  host-key-check: false
  user: my-user-name
  interpreters:
    rb: /usr/local/bin/ruby

Ran my plan as before, and it now works successfully. Thanks for your help on this, I'm happy for this issue to be closed. @donoghuc

Unfortunately I think I may have closed this prematurely.
When I run the bolt plan with the argument --run-as root, it fails.
Running task apply_helpers::custom_facts with '{"plugins"=>#<Sensitive [value redacted]>, "_task"=>"apply_helpers::custom_facts"}' on ["server1"]
Running task run '#<struct Bolt::Task name="apply_helpers::custom_facts", file=nil, files=[{"name"=>"custom_facts.rb", "path"=>"/opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-1.13.0/libexec/custom_facts.rb"}], metadata={"supports_noop"=>true, "input_method"=>"stdin"}>' on server1
Opened session
Executing: mkdir -m 700 /tmp/19903bcf-e134-4a3d-ba18-401271f85f0c
Command returned successfully
Executing: chmod u\+x /tmp/19903bcf-e134-4a3d-ba18-401271f85f0c/custom_facts.rb
Command returned successfully
Executing: chmod u\+x /tmp/19903bcf-e134-4a3d-ba18-401271f85f0c/wrapper.sh
Command returned successfully
Executing: id -g root
stdout: 0
Command returned successfully
Executing: sudo -S -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  chown -R root:0 /tmp/19903bcf-e134-4a3d-ba18-401271f85f0c
Command returned successfully
Executing: sudo -S -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  /usr/local/bin/ruby /tmp/19903bcf-e134-4a3d-ba18-401271f85f0c/wrapper.sh
stderr: /usr/local/bin/ruby:
stderr: no Ruby script found in input
stderr: (
stderr: LoadError
stderr: )
Command failed with exit code 1
Executing: sudo -S -u root -p \[sudo\]\ Bolt\ needs\ to\ run\ as\ another\ user,\ password:\  rm -rf /tmp/19903bcf-e134-4a3d-ba18-401271f85f0c
Command returned successfully
Closed session
{"node":"server1","status":"failure","result":{"_output":"","_error":{"kind":"puppetlabs.tasks/task-error","issue_code":"TASK_ERROR","msg":"The task failed with exit code 1:\n/usr/local/bin/ruby: no Ruby script found in input (LoadError)\n","details":{"exit_code":1}}}}
Finished: task apply_helpers::custom_facts with 1 failure in 2.47 sec
Finished: plan profiles::test in 3.6 sec
{
  "kind": "bolt/run-failure",
  "msg": "Plan aborted: run_task 'apply_helpers::custom_facts' failed on 1 nodes",
  "details": {
    "action": "run_task",
    "object": "apply_helpers::custom_facts",
    "result_set": [
      {
        "node": "server1",
        "status": "failure",
        "result": {
          "_output": "",
          "_error": {
            "kind": "puppetlabs.tasks/task-error",
            "issue_code": "TASK_ERROR",
            "msg": "The task failed with exit code 1:\n/usr/local/bin/ruby: no Ruby script found in input (LoadError)\n",
            "details": {
              "exit_code": 1
            }
          }
        }
      }
    ]
  }
}

Since setting the Ruby interpreter in the bolt.yaml file to use /usr/local/bin/ruby it's now trying to run /usr/local/bin/ruby /tmp/19903bcf-e134-4a3d-ba18-401271f85f0c/wrapper.sh, which obviously won't work because it's a shell script.
So when the ruby interpreter is set, and the --run-as root argument is passed, it fails due to trying to run the wrapper.sh file with the new ruby interpreter.
I wondered if it would be overridden if I set the correct interpreter for shell scripts so in bolt.yaml I set:
  interpreters:
    .sh: /bin/sh
    .rb: /usr/local/bin/ruby

However, this didn't work and its still trying to run wrapper.sh with /usr/local/bin/ruby.

@olivermussell You have discovered a bug! Thanks so much for trying it out. I ticketed it https://tickets.puppetlabs.com/secure/RapidBoard.jspa?rapidView=846&view=detail&selectedIssue=BOLT-1155 we will work on a fix.

@olivermussell Bolt 1.13.1 contains an update that should fix the bug. Note that the shell script in the example debug output you posted (/tmp/19903bcf-e134-4a3d-ba18-401271f85f0c/wrapper.sh) will not need an entry in the interpreters config. So specifically the apply_helpers::custom_facts task should only require the following (without the .sh: /bin/sh entry):
interpreters:
  .rb: /usr/local/bin/ruby

After updating to Bolt 1.13.1 the plan now runs successfully. Thanks for your help, I can create some plans now :)


[cudapoa] experimental commit to restructure files and remove void*

Closes #407

rerun tests

@r-mafi Realized some of the cmake changes were unnecessary for this PR, so removed them for now. Now mostly the cmake changes are in the cudapoa module, and slight updates to some others.
If you're good with this, let's merge it since it would be good to base the other PRs on top of this.

If you're good with this, let's merge it since it would be good to base the other PRs on top of this.
@tijyojwad yes, looks good. thanks.


Display Only dates between startDate and endDate

I need to display only dates between startDate and endDate, i've read JTCalendar Part of code but i can't find how to show just a period.

It's currently not part of the library. You have many things to change in JTCalendar.m, JTCalendarMenuMonthView.m and JTCalendarContentView.m. Good luck.


Hide sign plus (+)

Hello,
Thanks for the great tool,
I need to hide the initial value sign (+) from the input.
This my code
 <Phone
    classNames={`ltr dib mr4 ${containerClass}`}
    defaultCountry="MA"
    flagsImagePath={flags}
    {...input}
 />

Screen

@saadaouad Rigth now, there's no way to do that. Suggestions on the best way to do it and PRs are welcome.

@mukeshsoni is there any update on this please?

@mukeshsoni Could you please reopen this issue and give us some insights to fix it

There's no way to do it right now and i don't have the time to think of a solution for it. You can raise a PR if you think of a solution. I will close this one since it's not a bug and not high on list of priorities.

@saadaouad You opened this issue in 2017. How did you take care of that requirement in the 2 years since then and now?

You can raise a PR if you think of a solution. I will close this one since it's not a bug and not high on list of priorities.

Can you reopen this to keep trace for that?

Sorry, i don't have the bandwidth and don't think i will take it up any time soon.


[BUG] Regression: Vendored jaraco.text cannot be loaded when using Bazel

setuptools version
setuptools>=71.0.0
Python version
Python 3.10
OS
Arch Linux
Additional environment information
No response
Description
After setuptools' dependencies have been re-vendored, the issue #3072 surfaced again.
The file Lorem ipsum.txt from jaraco.text is loaded again here, which used to be removed in this fix.
This is a problem when using setuptools with Bazel, because it does not support paths with spaces.
Expected behavior
See #3072.
How to Reproduce
See #3072.
Output
See #3072.

Hi @janhicken have you tried to discuss this problem with the bazel maintainers? As noted in #3072 this is not really a bug in the setuptools code base but rather in bazel and/or rules Python.
I did open an issue a while ago in rules_python given a heads up that the patch introduced in https://github.com/pypa/setuptools/pull/3077 was not bullet proof and that the problem could re-surface. The issue was closed in favor https://github.com/bazelbuild/bazel/issues/4327.
I do believe that the best place to solve this problem is in bazel, and it is not really a bug in the setuptools implementation.
/cc @jaraco

I agree with you, maybe #3077 should not have been implemented in the first place, because upgrading to setuptools>=71.0.0 now feels like a regression.
Also, my issue is probably a duplicate of #4487 where this was already discussed in more detail. @jaraco already mentioned is intention to not fix the issue here.
As Bazel 7.0 introduced experimental support for dealing with spaces in paths (--experimental_inprocess_symlink_creation), this missing piece seems to be https://github.com/bazelbuild/rules_python not supporting that.
I'm going to open an issue there and close this one.


GetTick and DelayUntilMs/DelayUntilUs utilities for Delay?

Hi! I think it would be nice to add a DelayUntil utility to delays. In this way, we can have actual periodic tasks, regardless of the time consumed by a task when executing. To do so, we would need to add the following methods to delays:

get_tick(&self) -> u32 (I'm not sure which the return value should be): it returns the current internal clock tick value.
delay_until_ms(&mut self, tick_from: u32, ms: u16): it waits the given amount of milliseconds FROM THE BASELINE.
delay_until_us(&mut self, tick_from: u32, us: u32): it waits the given amount of microseconds FROM THE BASELINE.

With that, we could do something like this:
let tick = timer.get_tick();  // tick now represents the time
do_stuff(); // this takes time...
timer.delay_until_ms(tick, 1_000); // we wait one second starting from before we triggered do_stuff

Thus, we would not delay for one second, but 1 second SINCE WE CAPTURED THE BASELINE.
What do you think? Is there anything I'm missing that makes this a bad idea?

Before I get into the rest of this comment, let me just start by saying this is a very sensible and useful thing to want, and it would be nice to have, but it's a bit tricky...
This crate actually just provides an implementation of the embedded-hal DelayMs and DelayUs traits (soon to be plain Delay in the upcoming 1.0 release) using the Cortex-M SysTick peripheral; other HALs can also provide implementations using timer peripherals etc. Probably the best place for such a method would be embedded-hal itself, but the Delay traits there are basically just a minimum viable delay for now until questions about how to best represent time can be worked out (see https://github.com/rust-embedded/embedded-hal/issues/359).
In the Cortex-M implementation in this crate, you couldn't actually implement your proposed methods - it basically loads the required number of ticks into the SysTick timer, starts it running, then waits for it to run down to 0. There's no ongoing counter in the background, so there's no current "ticks" value.
Another hard part with this is that whatever value you return for get_tick() can overflow, and you can't be sure it hasn't overflowed when someone later calls delay_until(). If it's been more than half the maximum number of ticks between get_tick() and delay_until_ms(), the program can't really detect rollover, but won't wait the right amount of time. Getting this right ends up being quite application specific with regards to how long you expect to keep running and therefore how many bits you're willing to use for the timer (and how fast it runs, what resolution is OK, etc). It's something that specific HALs could provide configuration for, so it could live in a generic trait in embedded-hal too... but probably needs more thought about how to represent the time.
Other embedded projects like embassy can provide exactly what you're looking for by virtue of making more decisions about the platform; see the embassy time docs for example.

Thank you so much for the response, it was very clarifying. I guess that you noticed that I'm quite new in this world of open source and embedded systems.
From what I understood, it seems that embedded-hal is clearly the right place to define a helpful interface for dealing with time and delays (which are vital in embedded systems). However, a right or sound way of dealing with time in multiple platforms is not a straightforward issue, and that is why embedded-has is removing timer in version 1.0.
It seems that embedded-time is quite an appealing alternative for this, and people in the wg of embedded-hal are discussing whether to adopt it or not. I guess that embedded-time will eventually be absorbed by embedded-hal (or at least the latter will implement something similar to the prior).
So, for now, my best option is perhaps to include embedded-time by my own and use it at my own risk.
Am I right? or did I misunderstood your message? Thanks in advance.

Yep, that's about right! A more recent crate, fugit has also been very popular recently as an alternative design to embedded-time, which a number of HALs have started to adopt I believe.

Great, thanks for your time! I'll close the issue.


Skein: Zoom please? Pan is very slow as well. Clear FULL skein in one click?

Just a couple requests here, as per the thread title.
When the skein gets big, it would be REALLY useful to be able to zoom in and out to navigate quickly.
Regarding that, the middle-click panning function is VERY slow and not smooth.
Finally, being able to clear the ENTIRE skein with one click would be very very nice, as the skein gets QUITE full rather quickly as one is building a game. Having to delete every thread individually is very tiresome.
Similarly, it would be very nice if one could select multiple threads to delete in one go, rather than the entire skein (tho both, of course, would be very useful)
Also wondering when an official build will be available for download next. I'm not really "up to" compiling from source.
Thanks for your work! :D

The last update to the Windows build was in March this year: you can get that latest build from http://inform7.com/ or http://ifarchive.org/indexes/if-archiveXinfocomXcompilersXinform7Xexecutables.html
In recent Windows builds there has been some work to catch up with the skein as it is in the OSX front end. On the right-click menu for skein nodes there is "Delete Threads From Here" and also "Trim", which removes all unlocked nodes below.
I don't know quite when the next build will be: the only recent changes have been overhauling the preferences dialog, which isn't quite finished yet.
In general, bug reports are best at http://inform7.com/mantis/view_all_bug_page.php, and new feature requests at https://inform7.uservoice.com/forums/57320-general/. There's still quite a lot of work to do for the Windows front-end to catch up with OSX, so that will most likely be the immediate priority.
Thanks for the suggestions!

I'm closing this issue as the middle-click panning in the skein should be fixed in the latest source. The remaining comments in this issue are really feature requests, which are more suited to being reported at the Inform7 UserVoice page, as noted in the previous comment.


[PE] Fix imports losing data caused by #95

Mentioning #95, should do the job. Thankfully track is kept of who becomes what.

Ready to review?


Logs in new versions are gone - that's quite unfortunate

Hi guys, without a log of requests and their status it is not clear whether they succeed or not, which is extremely important - indicates the need to change VPN location.
This issue is a request to return logs.

reproducible on Windows

To understand logs you must know what is 200/400/500/timeout statuses. We are focused on users, that dont know about this. And there where a lot of questions like "what is 200? everything ok?". So we added this efficiency status bar, where 200/400/500 is ok and every other status is bad. Efficiency bar shows information about last 2k requests.
We understand, that for more advanced users like you - this is bad :(.
Logs where moved to terminal. Just start program from terminal and they will be here - in terminal window :)
Let us know if this is ok for you or you have other suggestions. If ok - I will close issue :)

Ooh alright, I see now. Thought efficiency bar is about parallelism. Thanks!
Maybe makes sence to add some tooltip there with a comment what does it mean? I might be not the only one, hopefully 😄😄

You can run program with this bat file.
:run
"C:\Users\username\AppData\Local\Programs\shield\UA Cyber SHIELD.exe"
pause
goto :run

We where discussing this internally Maybe makes sence to add some tooltip there with a comment what does it mean?. UI stays the same. Problem with logs solved.


Error when trying to inferfence

When I press "Convert", I get this error:
Traceback (most recent call last):
File "C:\Users\lccji\Downloads\Mangio-RVC-Fork-main\my_utils.py", line 14, in load_audio
ffmpeg.input(file, threads=0)
AttributeError: module 'ffmpeg' has no attribute 'input'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\lccji\Downloads\Mangio-RVC-Fork-main\infer-web.py", line 163, in vc_single
audio = load_audio(input_audio_path, 16000)
File "C:\Users\lccji\Downloads\Mangio-RVC-Fork-main\my_utils.py", line 19, in load_audio
raise RuntimeError(f"Failed to load audio: {e}")
RuntimeError: Failed to load audio: module 'ffmpeg' has no attribute 'input'
Traceback (most recent call last):
File "C:\Users\lccji\AppData\Local\Programs\Python\Python310\lib\site-packages\gradio\routes.py", line 437, in run_predict
output = await app.get_blocks().process_api(
File "C:\Users\lccji\AppData\Local\Programs\Python\Python310\lib\site-packages\gradio\blocks.py", line 1349, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "C:\Users\lccji\AppData\Local\Programs\Python\Python310\lib\site-packages\gradio\blocks.py", line 1283, in postprocess_data
prediction_value = block.postprocess(prediction_value)
File "C:\Users\lccji\AppData\Local\Programs\Python\Python310\lib\site-packages\gradio\components.py", line 2586, in postprocess
file_path = self.audio_to_temp_file(
File "C:\Users\lccji\AppData\Local\Programs\Python\Python310\lib\site-packages\gradio\components.py", line 360, in audio_to_temp_file
temp_dir = Path(dir) / self.hash_bytes(data.tobytes())
AttributeError: 'NoneType' object has no attribute 'tobytes'

hi, i have the same kind of problem, did you solve it?

same here

i think i found the problem: is a gradio issue, try installing gradio==3.34.0

I'm guessing this happens if you've installed both, ffmpeg and ffmpeg-python.
uninstall both with:
pip uninstall ffmpeg
pip uninstall ffmpeg-python
for good measure uninstall ffmpy along with these two so
pip uninstall ffmpy
and install ffmpeg-python and ffmpy again with :
pip install ffmpeg-python
pip install ffmpy
This solved the problem in my system :)

I'm guessing this happens if you've installed both, ffmpeg and ffmpeg-python. uninstall both with: pip uninstall ffmpeg pip uninstall ffmpeg-python for good measure uninstall ffmpy along with these two so: pip uninstall ffmpy
and install ffmpeg-python and ffmpy again with : pip install ffmpeg-python pip install ffmpy
This solved the problem in my system :)

How exactly do I uninstall and reinstall in Mangio? I'm new to this so I'm not sure sorry.

I'm guessing this happens if you've installed both, ffmpeg and ffmpeg-python. uninstall both with: pip uninstall ffmpeg pip uninstall ffmpeg-python for good measure uninstall ffmpy along with these two so: pip uninstall ffmpy
and install ffmpeg-python and ffmpy again with : pip install ffmpeg-python pip install ffmpy
This solved the problem in my system :)

How exactly do I uninstall and reinstall in Mangio? I'm new to this so I'm not sure sorry.

he literally said the commands for it, do it on the terminal


Evaluation page: can't parse ? into unknown when input column type is single

All columns are single type.
It's hard to say whether it's a bug or should be expected, but it's definitely blocking try-it-out story

I think this is not a bug,  but we should communicate  exactly what happened there

We'll revisit our error story.


Wfcore 747 master

https://issues.jboss.org/browse/WFCORE-747
Add a marker file to standalone or domain server tmp directory to record server startup state once server is started. It will be removed when server is stopped.
Inside wildfly-init-redhat.sh and wildfly-init-debian.sh, it will read this temporary marker file to exam server startup result before timeout instead of checking volatile log message from console log(key log id changed, log handler removed, etc.)

Linux Build 2101 is now running using a merge of c5ceeef772faaea76730f05c805456d19b0d9340

Core - Full Integration Build 1239 is now running using a merge of c5ceeef772faaea76730f05c805456d19b0d9340

Windows Build 1638 is now running using a merge of c5ceeef772faaea76730f05c805456d19b0d9340

Linux Build 2101 outcome was SUCCESS using a merge of c5ceeef772faaea76730f05c805456d19b0d9340
Summary: Tests passed: 3348, ignored: 62 Build time: 0:34:15

Windows Build 1638 outcome was SUCCESS using a merge of c5ceeef772faaea76730f05c805456d19b0d9340
Summary: Tests passed: 3348, ignored: 62 Build time: 0:35:08

Core - Full Integration Build 1239 outcome was SUCCESS using a merge of c5ceeef772faaea76730f05c805456d19b0d9340
Summary: Tests passed: 2929, ignored: 367 Build time: 0:48:30

Windows Build 1651 is now running using a merge of 43d116b953bfc819834f7ac22315d68625d5b89e

Linux Build 2117 is now running using a merge of 43d116b953bfc819834f7ac22315d68625d5b89e

Core - Full Integration Build 1252 is now running using a merge of 43d116b953bfc819834f7ac22315d68625d5b89e

Windows Build 1651 outcome was SUCCESS using a merge of 43d116b953bfc819834f7ac22315d68625d5b89e
Summary: Tests passed: 3360, ignored: 62 Build time: 0:33:48

Linux Build 2117 outcome was SUCCESS using a merge of 43d116b953bfc819834f7ac22315d68625d5b89e
Summary: Tests passed: 3360, ignored: 62 Build time: 0:37:28

Core - Full Integration Build 1252 outcome was FAILURE using a merge of 43d116b953bfc819834f7ac22315d68625d5b89e
Summary: Tests failed: 1 (1 new), passed: 2926, ignored: 367, muted: 2 Build time: 0:52:41
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>

We should discuss this on the wildfly-dev mailing list. I'm not sure if we want to go here or not.

Please post on the wildfly-dev thread about this design, so anyone interested is aware.

Core - Full Integration Build 1302 is now running using a merge of c193aa1c8be9a3f4ad5eecc67e5d217e1205a8ab

Windows Build 1694 is now running using a merge of c193aa1c8be9a3f4ad5eecc67e5d217e1205a8ab

Linux Build 2165 is now running using a merge of c193aa1c8be9a3f4ad5eecc67e5d217e1205a8ab

Windows Build 1694 outcome was SUCCESS using a merge of c193aa1c8be9a3f4ad5eecc67e5d217e1205a8ab
Summary: Tests passed: 3372, ignored: 63 Build time: 0:35:49

Linux Build 2165 outcome was SUCCESS using a merge of c193aa1c8be9a3f4ad5eecc67e5d217e1205a8ab
Summary: Tests passed: 3372, ignored: 63 Build time: 0:36:18

Core - Full Integration Build 1302 outcome was SUCCESS using a merge of c193aa1c8be9a3f4ad5eecc67e5d217e1205a8ab
Summary: Tests passed: 2912, ignored: 342, muted: 3 Build time: 0:52:18

Core - Full Integration Build 1313 is now running using a merge of c2fc488b68af555892cce4ad2442c266dd289cab

Windows Build 1705 is now running using a merge of c2fc488b68af555892cce4ad2442c266dd289cab

Linux Build 2177 is now running using a merge of c2fc488b68af555892cce4ad2442c266dd289cab

Windows Build 1705 outcome was SUCCESS using a merge of c2fc488b68af555892cce4ad2442c266dd289cab
Summary: Tests passed: 3372, ignored: 63 Build time: 0:34:36

Linux Build 2177 outcome was SUCCESS using a merge of c2fc488b68af555892cce4ad2442c266dd289cab
Summary: Tests passed: 3372, ignored: 63 Build time: 0:35:53

Core - Full Integration Build 1313 outcome was FAILURE using a merge of c2fc488b68af555892cce4ad2442c266dd289cab
Summary: Tests failed: 2 (2 new), passed: 2940, ignored: 344, muted: 2 Build time: 0:53:08
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.mdb.dynamic.DynamicMessageListenerTestCase.test1: <no details avaliable>

org.jboss.as.test.integration.ejb.timerservice.database.DatabasePersistentIntervalTimerManagementTestCase.testResourceExistence: <no details avaliable>

I think this is fine, but i think a better approach would be use tail -f to wait for the write, so that you don't have to sleep loop. That can be a subsequent enhancement.

rebased to resolve conflict, retest this please.

WildFly pull requests Build 7 is now running using a merge of 21330ef0eef970c5f2f6b14e549d4b32b1f409bf

WildFly pull requests Build 1825 outcome was SUCCESS using a merge of 21330ef0eef970c5f2f6b14e549d4b32b1f409bf
Summary: Running Build time: 00:00:02


Support to display the run history for each route

What is the motivation for adding/enhancing this feature?

Currently, we have a feature to display the history for runs, but we need some way to see the history for specific routes as well.
What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[x] YES
[ ] NO

Additional information

@dt2patel Sir, proposed design for this feature.
https://www.figma.com/file/1zV3igEzA2OFHE6tqCmSGH/HC-Ionic-design-system-(Copy)?type=design&node-id=35905-7099&mode=design&t=dBvfPEYLOEAosJuq-0

what are the details that will be presented in the route history?

what are the details that will be presented in the route history?

It will display the details like startTime, endTime, any error in the route and route result.

Clicking on chip from group or routing page will open the history modal


Rename HISTORY.rst to CHANGELOG.rst

Addresses #137
NOTE: The content has yet to be updated.

Current coverage is 100% (diff: 100%)

Merging #161 into master will not change coverage

@@           master   #161   diff @@
====================================
  Files           9      9
  Lines         224    224
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          224    224
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update da1b69a...23e614d

:+1: