openfst: 1.7.2 -> 1.7.4

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/openfst/versions.
meta.description for openfst is: '"Library for working with finite-state transducers"'.
meta.homepage for openfst is: '"http://www.openfst.org/twiki/bin/view/FST/WebHome"

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.7.4 with grep in /nix/store/c29mdawmvmzaxsapl7dazdipwkxjflb1-openfst-1.7.4

directory tree listing: https://gist.github.com/b02920da7a2710abf976414f080a3ced

du listing: https://gist.github.com/5d5097a80522b0970e30dbe49c2cc8a1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
openfst

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c29mdawmvmzaxsapl7dazdipwkxjflb1-openfst-1.7.4 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A openfst https://github.com/r-ryantm/nixpkgs/archive/a5554ea7a252052ab333935f506e777bcf13a428.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c29mdawmvmzaxsapl7dazdipwkxjflb1-openfst-1.7.4
ls -la /nix/store/c29mdawmvmzaxsapl7dazdipwkxjflb1-openfst-1.7.4/bin

cc @dfordivam for testing.

From NEWS :

Removes harmful constexpr specifications in FAR (1.7.4)
Improved script API support for EncodeMapper (1.7.4)
New header format for the EncodeMapper (1.7.4)
Imrproved C++17 compatibility shims (1.7.4)
Rewrite of the compactor interface (1.7.4)
Overloads Arc constructors with default weight argument (1.7.3)
Fixes RmEpsilon and Union property checking bugs (1.7.3)
Makes Isomorphic more robust to nondeterminism (1.7.3)
Adds default weight argument to SetFinal (1.7.3)
Cleans up low-level logging (1.7.3)
Adds power-weight mappers (1.7.3)
Adds expander cache (1.7.3)

Nothing asking for a backport


WIP state circuit: implement new spec

don't force push, don't rebase, just use the old boring merge(three way merge)
resolving issue: https://github.com/appliedzkp/zkevm-circuits/issues/356
spec: https://github.com/appliedzkp/zkevm-specs/blob/master/src/zkevm_specs/state.py
rw table: https://github.com/appliedzkp/zkevm-specs/blob/master/specs/tables.md
(Note: https://github.com/appliedzkp/zkevm-circuits/pull/354 is merged for speeding up CI)

[x] renaming according to specs
[x] add more needed columns, like key2_limbs/key4_bytes
[x] remove padding
[x] rewrite using constraint builder (zzhang)
[ ] finish general constraints (mason)   (i am not sure how many of following gates are implemented already, better read code first, maybe for some gates we can just move codes elsewhere into meta.create_gate("General constraints"... )

[ ] 0. key0, key1, key3 are in the expected range
[ ] 1. key2 is linear combination of 10 x 16bit limbs and also in range
[ ] 2. key4 is RLC encoded
[x] 3. is_write is boolean
[ ] 4. Keys are sorted in lexicographic order for same Tag
[ ] 5. RWC is monotonically strictly increasing for a set of all keys
[x] 6. Read consistency

[ ] finish constraints for different rws

[ ] Start = 1
[ ]     Memory = 2. (most done)
[x]     Stack = 3
[x]     Storage = 4
[ ]     CallContext = 5
[ ]     Account = 6
[ ]     TxRefund = 7
[ ]     TxAccessListAccount = 8
[ ]     TxAccessListAccountStorage = 9
[ ]     AccountDestructed = 10

[ ] assign witness of all kinds of rws
[ ] write all tests according to specs
[ ] optimization: like change tag column to 4 boolean column, MonotoneChip for address range etc
[ ] more polish: reuse more codes in witness assignment between state circuit and evm circuit

what about merging with upstream/main first? so the "File changed" can be more friendly to read?

@z2trillion i think there is something going wrong in the git history?   We did not modify these files..

replaced by https://github.com/appliedzkp/zkevm-circuits/pull/462


Themis 0.13.2

Hotfix for Carthage, removing dysfunctional ObjCThemis.xcodeproj.
Provisional tag 0.13.2 currently points to this commit, will retag and release once merged.
Checklist

[X] Change is covered by automated tests
[X] Changelog is updated


Support #![no_std]

From the readme

In the future, we hope to support #![no_std] with the alloc crate when std is not enabled.

It was my understanding that we were holding back on this until alloc was stabilized, which happened fairly recently, in 1.28

If you check the links, those stabilized alloc APIs were actually just for the module alloc, accessible through core::alloc or std::alloc, and these are just the raw allocator APIs.
The alloc crate will finally be stabilized in 1.36 (https://github.com/rust-lang/rust/pull/59675/), which will include the alloc::vec::Vec we need to easily support num-bigint.

Hm, I didn't realize what exactly we needed when writing this issue, but alloc::vec::Vec makes more sense. 1.36 will probably be released around the end of June. We could just keep this issue open until then.

Yeah, that's fine. I'm even going to self-assign this, because I have a WIP branch around here somewhere... :)

As 1.36 was release last week it would now be possible to attack that issue again. Can I somehow help to make it happen?

Tried this. Looks like std::error::Error trait does not have a alloc or core counterpart. Do not know how to solve that. Do you want me to make an WIP PR?

Yeah, Error will need to a cfg for std only.
As mentioned, I do have a WIP branch myself, just need to get around to it. I will try to do this soon...

See draft PR #101, if you'd like to test.


Remove Custom Timeouts From Tests

Summary
Timeouts should be defined from the global level for wait. This allows us to update in one place if needed.
Our global timeout is defined as: 3000
More info on webdriver.io config option: http://webdriver.io/guide/getstarted/configuration.html#waitforTimeout

@yuderekyu I think when @mhemesath setup the wdio initially, he chose 3000 and we haven't needed to adjust it.


Regarding LGACSendDeno

Hey,
I have a confusion regarding what that wire library is doing there and what device you are using to take input using Wire library.
Thank you

I'm not sure what you're referring to.  The string "LGACSendDemo" does not appear in my project, and I don't use a "wire" library.  Would you mind pointing to a specific file?
As mentioned in the README, the hardware I use is that described here: http://alexba.in/blog/2013/03/09/raspberrypi-ir-schematic-for-lirc/.


https://www.chatbotui.com/ no longer works?

I haven't checked in at https://www.chatbotui.com/ in a while. Today I noticed that chatbotui has not chat bot or UI :/

Any ideas if something's changed here?

+1 was quite convenient to just visit a hosted version :)

I had it pinned and used it daily. Once 1 click to vercel is up I'll use that instead I think, but the easy access was great for sharing with people because it was a great tool

you can use https://yakgpt.vercel.app/

That's okay for the time being, but honestly it doesn't really solve for my use case.
I have a lot of custom prompts that I use on a regular basis. Honestly I was surprised when Chatbot UI went down because I didn't see a notification and now my prompts are gone.
There wasn't a warning except on the GitHub repo, and I hadn't checked that in months, though that sort of deviates from the purpose of this thread, which is specifically to discover if a hosted version will be returning.

@jarrenrocks you can retrieve your prompts from localStorage

A data export was meant to be automatically triggered. I’ll fix this bug.
As far as a hosted version you can expect that next week, though it will be $10/mo.
The cloud bill at this point is just too much to be free. While inference is paid for by the user, we pay for hosting, storage, edge function usage, etc.

you can use https://apiskey.com/

您可以使用https://apiskey.com/

it can’t be used


WIP: part 2 of the distroless/static move

TODO

[ ]  intel-vpu-plugin
[ ]  copy toybox/musl license

@bart0sh @rojkov this is now ready


Elliptical area tools Status: OPEN Priority:

Name: Elliptical area tools
CUID: 863gcrxh8
Link: https://app.clickup.com/t/863gcrxh8
Description:
Created by: Zeyad Rashed
Priority:
Status: OPEN
Status Type: open
Assigned to:
Due date:

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


Bogus diagnostics in macro modules?

The Fennel manual describes using macro modules to export commonly re-used macros.  In macro modules, macros are defined not using (macro) but rather as plain (fn) functions.  This leads to hotpot mistakenly treating macro code as "run-time" (rather than "compile-time") code, reporting errors such as

"unknown-identifier: assert-compile"
"symbols may only be used at compile time"

etc.
Is there some way to configure hotpot so that it knows how to distinguish between regular (run-time) modules vs. macro (compile-time) modules?

There is https://github.com/rktjmp/hotpot.nvim/blob/b942e8760ea26f6ff3782f675a8d6c1323f3e7d4/fnl/hotpot/api/diagnostics.fnl#L118-L126 (under :h hotpot.api.diagnostics.set-options but the docs are lacking, PR's welcome).
You should be able to call that with macro compiler options and it will call the handler internally. I haven't tested this rigorously, but that's the idea from memory.
I would either create a bind, or auto-cmd that calls that for files you consider "macro files".
See also :h hotpot-setup for the default compiler options to pass for macros.
The options will override what's set here:
https://github.com/rktjmp/hotpot.nvim/blob/b942e8760ea26f6ff3782f675a8d6c1323f3e7d4/fnl/hotpot/api/diagnostics.fnl#L71-L72
So you may want to pass in a filename and allowed globals in addition to any env options.
I don't think there is a really safe way to detect "macro modules", besides perhaps if they are called init-macros.fnl which is why we don't set anything like this automatically currently.

Thanks!  This set-options thing seems useful for sidestepping the "unknown identifier: assert-compile" error, but it seems to have no effect on the "symbols may only be used at compile time" issue (presumably, since that's not an unresolved global variable issue).
For reference, here's what I ran (as a vim command, via lua):
lua require 'hotpot.api.diagnostics'['set-options']({ env = '_COMPILER' })

Which, per the Fennel API docs, "will cause the code to be run/compiled in a context which has all compiler-scoped values available. This can be useful for macro modules or compiler plugins."
Upon running that, the "unknown identifier: assert-compile" error did indeed go away, but "lists/symbols may only be used at compile time" errors remained.
Perhaps this is a Fennel-side issue that I should take up with them?

Hmm, it's because macros are kind of always eval-at-compile-time but not technically compiled.
When you compile a regular module that uses a macro, the macro module is evaluated during compile and the functions are basically added to the Fennel runtime, there is never any resulting lua code for the macro module.
To get the diagnostics for normal modules we give the code to the compiler and show any errors, but for macros that wont work.
Swapping compile-buffer to eval-buffer (with the env alteration) will let it work but:

it can only detect errors in unquoted code because the quoted code just compiles out to a list, it's never evaluated, so (bad-let ,(bad call) will show an error for (bad call) but not (bad-let.
there's the potential for harmful side effects  as eval'ing the code will actually run it, which might accidentally run code that you don't want to run!
you could get around this probably by passing in an env that has compiler symbols and dead stubs for stuff like fopen etc.

AFAIK Fennel upstream doesn't provide any way to "check a macro compiles" as we are seeing. Unsure how hard that would be to implement. I know that Andrey Listopadov wrote some "eval-safely" stuff for his fennel-doc project.
I can add an additional function, perhaps (set-mode buf :compile|:eval) which would solve the issue but it wont ever be turned on by default due to the  potentially unsafe nature.

I've added an extra argument to set-options, (set-options buf opts :compile|:eval|nil) which effects how code is run, as above, be very careful you are not writing potentially damaging code and evaluating it unexpectedly.
Probably there is room in the API for diagnostics.check-once where you can explicitly force a diagnostic run on a buffer when you know its safe, if you didn't want it checked after each insert leave.
Changes: https://github.com/rktjmp/hotpot.nvim/commit/0c192b64addebfdc97d92803ce1e73d8600a2b03

Should be fixed, requires macros to be in a file that ends in macro.fnl or macros.fnl, doc: https://github.com/rktjmp/hotpot.nvim/blob/e77fc345e3f7b8bdcc18f7da22edb4cde01613f4/doc/hotpot-api.txt#L79-L80


Fix minor issues

Codecov Report

Merging #293 (861b98a) into master (b7dcb28) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #293   +/-   ##
=========================================
  Coverage     76.94%   76.94%
  Complexity      998      998
=========================================
  Files           140      140
  Lines          2646     2646
  Branches        356      356
=========================================
  Hits           2036     2036
  Misses          530      530
  Partials         80       80

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 b7dcb28...861b98a. Read the comment docs.


QueryOutputTypeDef["Items"] doesn't represent actual DynamoDB output

Describe the bug
query_output["Items"] is actually a list of {"AttributeName": {"Type": value}}
It is defined as follows:
QueryOutputTypeDef = TypedDict(
    "QueryOutputTypeDef",
    {
        "Items": List[
            Dict[
                str,
                Union[
                    bytes,
                    bytearray,
                    str,
                    int,
                    Decimal,
                    bool,
                    Set[int],
                    Set[Decimal],
                    Set[str],
                    Set[bytes],
                    Set[bytearray],
                    Sequence[Any],
                    Mapping[str, Any],
                    None,
                ],
            ]
        ],
        ...
    },
)

...yet DynamoDB returns something like {'StringAttribute': {'S': 'value'}, 'NumericAttribute': {'N': '123.4'}, ...}
To Reproduce
import boto3

client = boto3.client("dynamodb")
data = client.query(
    TableName="Foo",
    KeyConditionExpression="PK = :PK",
    ExpressionAttributeValues={
        ":PK": {"S": "Foo"},
    },
)
items = data["Items"]

print(items[0]["NumericAttribute"]["N"])
# prints the correct numeric value

pyright file.py
Actual output
C:\Users\...\file.py
  C:\Users\...\file.py:7:7 - error: Argument of type "Literal['N']" cannot be assigned to parameter "__s" of type "slice" in function "__getitem__"
    "Literal['N']" is incompatible with "slice" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: Argument of type "Literal['N']" cannot be assigned to parameter "__i" of type "SupportsIndex | slice" in function "__getitem__"
    Type "Literal['N']" cannot be assigned to type "SupportsIndex | slice"
      "Literal['N']" is incompatible with protocol "SupportsIndex"
        "__index__" is not present
      "Literal['N']" is incompatible with "slice" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "int" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "Decimal" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "bool" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "Set[int]" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "Set[Decimal]" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "Set[str]" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "Set[bytes]" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: "__getitem__" method not defined on type "Set[bytearray]" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: Argument of type "Literal['N']" cannot be assigned to parameter "index" of type "slice" in function "__getitem__"
    "Literal['N']" is incompatible with "slice" (reportGeneralTypeIssues)
  C:\Users\...\file.py:7:7 - error: Object of type "None" is not subscriptable (reportOptionalSubscript)
12 errors, 0 warnings, 0 informations

Expected output
0 errors, 0 warnings, 0 informations

Additional context
Windows 10, Python 3.9.5, boto3==1.22.1, mypy-boto3-dynamodb==1.22.0.post1

Hello! Thank you for the report. Probably boto3 alters the underlying botocore shape. I will take a look

It seems to work now, thank you!


Specifying parameterized benchmarks and performing parameter sweeps

I want to run a "family of benchmarks" as described in the google benchmark documentation. E.g. running the same benchmark for different thread counts, different problem sizes etc.
The only option that I can come up with after going through the docs is manually duplicating existing benchmarks. I was unable to find anything in the documentation regarding this. Is this possible in release 1.22.0?

For sure, just try something like this for running 7 different benchmarks with different parameterization:
import Benchmark

let benchmarks = {
    let tableCounts = (0..<10).map { 1 << $0 } // 1, 2, 4, ... 512

    tableCounts.forEach { tableCount in
        Benchmark("TransactionsWith\(tableCount)Tables") { benchmark in
             print("Running benchmark for \(tableCount)")
    }
}

See documentation updated in
https://github.com/ordo-one/package-benchmark/releases/tag/1.22.1


Add IsNull to the Delete data expression interface

so that rows can be deleted by null  Fixes #191

Just an FYI that this can be accomplished by using .Row(new { Column1 = (string)null }) in the codebase

Thanks for sharing.
That makes perfect sense but I would never have thought of it.

Yeah no problem.  It is useful if you need to do a delete (or update) based
on a column being null and another column having a value, or 2 columns
being null, etc.
On Mon, Nov 28, 2011 at 12:39 PM, Andrew Busby <
<EMAIL_ADDRESS>
wrote:

Thanks for sharing.
That makes perfect sense but I would never have thought of it.

Reply to this email directly or view it on GitHub:
https://github.com/schambers/fluentmigrator/pull/192#issuecomment-2906879

--
Jeff Treuting
Truburn Solutions, LLC
(206) 393-0717
www.truburn.net
<EMAIL_ADDRESS>

So is this pull still needed or not ?

Yes, although you can achieve the same result with trickery this method makes it clear.
------Original Message------
From: Tom Marien
To: Andrew Busby
Subject: Re: [fluentmigrator] Add IsNull to the Delete data expression interface (#192)
Sent: 17 Dec 2011 16:08
So is this pull still needed or not ?

Reply to this email directly or view it on GitHub:
https://github.com/schambers/fluentmigrator/pull/192#issuecomment-3190023
Sent from my BlackBerry® wireless device


Generic backup contents and not contents related to Azure table storage backup

This page which falls under Azure table storage should contain details about Table storage backup. But it talks about blobs and other services.

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

ID: d8314bbb-3e1b-7a68-dcd1-f7dfe34221a2
Version Independent ID: 5c26cb3f-ec5c-b028-f456-53998a67749e
Content: Disaster recovery and storage account failover - Azure Storage
Content Source: articles/storage/common/storage-disaster-recovery-guidance.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@haripraghash Thank you for your feedback . We will investigate and update the thread.

#reassign: @tamram

@haripraghash - Thanks for your feedback! This article is about storage account recovery and failover. So it applies to all of storage services (blob, queue, table, and file).
To back up a table, you can use AzCopy v7.3. If you're looking for a more sophisticated solution, Cosmos DB has a built-in backup option.
#please-close

Thank you. Its just that the link was under Azure table storage documentation and assumed that links under table storage documentation should only deal with Table storage


Fixed epsilon value for exploration

Fixes #104

It seems whenever I need a non-zero epsilon, I have passed it explicitly.
It is now unsafe to change the default value.

Got it. Thanks


StreamWatcher memory leak

We are using the StreamWatcher and seeing extremely high memory allocations. Attached is a memory profile:
pprof.pilot-discovery.alloc_objects.alloc_space.inuse_objects.inuse_space.033.pb.gz
From this we have 9.6 GB of memory allocated by the StreamWatcher.
To get to this state I had a deployment with 200 replicas, and every 30 seconds I redeployed all of the pods (kubectl rollout restart). I left this running overnight and saw this memory usage.

/remove-lifecycle rotten

@howardjohn issues for api-machinery are managed https://github.com/kubernetes/kubernetes/issues
could you resubmit there?

@howardjohn issues for api-machinery are managed https://github.com/kubernetes/kubernetes/issues
could you resubmit there?

Submitted  https://github.com/kubernetes/kubernetes/issues/91686.

thanks, tracking in https://github.com/kubernetes/kubernetes/issues/91686
/close


Running deno test -A not working (development)

This is an awesome project (love the simplicity of this framework). I'm looking to learn about how Fresh works and contribute.
Assuming that the tests are supposed to be passing on the main branch, I'm unable to get the tests to run properly.
Context

WSL 2 on Windows 10,  Ubuntu 22.04.1 LTS
Deno installed at /home/wchen/.deno/bin/deno

Steps to reproduce

Pull this repo and then cd fresh
Run deno test -A; for me 28 tests in 2 steps failed, I got the following error on each one:

error: Error: Could not find browser revision 1022525. Run "PUPPETEER_PRODUCT=chrome deno run -A --unstable<EMAIL_ADDRESS>to download a supported browser binary.
      if (missingText) throw new Error(missingText);
                             ^
    at ChromeLauncher.launch (https://deno.land/x/puppeteer@16.2.0/src/deno/Launcher.ts:99:30)
    at eventLoopTick (ext:core/01_core.js:183:11)
    at async setUpServer (file:///mnt/c/Users/wchen/projects/fresh/tests/twind_test.ts:18:19)
    at async fn (file:///mnt/c/Users/wchen/projects/fresh/tests/twind_test.ts:192:20)

Run PUPPETEER_PRODUCT=chrome deno run -A --unstable<EMAIL_ADDRESS>I got another error, this is more cryptic:

error: Interrupted: operation canceled
    const result = await reader.read(inspectArr);
                   ^
    at async read (ext:deno_io/12_io.js:103:17)
    at async readDelim (https://deno.land/std@0.93.0/io/bufio.ts:652:20)
    at async readStringDelim (https://deno.land/std@0.93.0/io/bufio.ts:702:20)
    at async readLines (https://deno.land/std@0.93.0/io/bufio.ts:711:18)
    at async waitForWSEndpoint (https://deno.land/x/puppeteer@16.2.0/src/deno/BrowserRunner.ts:168:20)
    at async BrowserRunner.setupConnection (https://deno.land/x/puppeteer@16.2.0/src/deno/BrowserRunner.ts:146:31)
    at async ChromeLauncher.launch (https://deno.land/x/puppeteer@16.2.0/src/deno/Launcher.ts:114:26)
    at async withPageName (file:///mnt/c/Users/wchen/projects/fresh/tests/test_utils.ts:43:21)
    at async fn (file:///mnt/c/Users/wchen/projects/fresh/tests/islands_test.ts:332:5)

I tried running the tests as root, but I get a separate error (this is after updating Puppeteer):
error: NotFound: No such file or directory (os error 2)
    this.proc = Deno.run({
                     ^
    at opRun (ext:runtime/40_process.js:46:14)
    at Object.run (ext:runtime/40_process.js:132:15)
    at BrowserRunner.start (https://deno.land/x/puppeteer@16.2.0/src/deno/BrowserRunner.ts:64:22)
    at ChromeLauncher.launch (https://deno.land/x/puppeteer@16.2.0/src/deno/Launcher.ts:108:12)
    at eventLoopTick (ext:core/01_core.js:183:11)
    at async setUpServer (file:///mnt/c/Users/wchen/projects/fresh/tests/twind_test.ts:18:19)
    at async fn (file:///mnt/c/Users/wchen/projects/fresh/tests/twind_test.ts:118:20)

Not sure where to go from here. The error seems to be coming from the OS, but the fact that it doesn't run under root is strange.

Sorry to reopen this issue but I faced the same problem with the error message :

error: Interrupted: operation canceled
const result = await reader.read(inspectArr);
^
at async read (ext:deno_io/12_io.js:103:17)
at async readDelim (https://deno.land/std@0.93.0/io/bufio.ts:652:20)
at async readStringDelim (https://deno.land/std@0.93.0/io/bufio.ts:702:20)
at async readLines (https://deno.land/std@0.93.0/io/bufio.ts:711:18)
at async waitForWSEndpoint (https://deno.land/x/puppeteer@16.2.0/src/deno/BrowserRunner.ts:168:20)
at async BrowserRunner.setupConnection (https://deno.land/x/puppeteer@16.2.0/src/deno/BrowserRunner.ts:146:31)
at async ChromeLauncher.launch (https://deno.land/x/puppeteer@16.2.0/src/deno/Launcher.ts:114:26)
at async withPageName (file:///mnt/c/Users/wchen/projects/fresh/tests/test_utils.ts:43:21)
at async fn (file:///mnt/c/Users/wchen/projects/fresh/tests/islands_test.ts:332:5)

Then I am stuck at the step you mentioned : running deno task install-puppeteer.
When I run it, I have a single line display : error: No config file found with no other explanation... do you have a clue for me please  :) ? Thanks for the help ^^


support timing expression type checking in addition to function checking

Is it possible to support -Xfrontend -debug-time-expression-type-checking
as explained here: Swift Users Mail List

I just tried -Xfrontend -debug-time-expression-type-checking and my project won't even compile with this in place. I wonder in what version this was introduced (I am on Xcode 8.2.1 and not on the beta).

Ok, this appears to be a beta feature.
"That was released prior to the addition of the new option. Recent snapshot builds from https://swift.org/download/#snapshots https://swift.org/download/#snapshots as well as the more recent Xcode 8.3 betas have it."

Ok after I've downloaded the beta, I see what it's doing. That looks interesting and something I think the analyzer should support. Now to the tricky bit, to find and set aside the time to implement it. ;)

Excellent.
Sorry I should have mentioned that it was only in the beta versions.  Either Xcode Beta 5 is nearing GM release or Apple messed up the build, because when expanded it is named Xcode.app, not Xcode-Beta.app.

@neilt - This was a really nice find. Got some surprising results after the analyzer parsed it. I need to add some info to the instructions screen and communicate the change. In the meantime, if you want to add the new flag, you can try it out using this branch.
Note that the function info (the column to the right) is not available when using this flag.

The new version works pretty well.  Able to knock about 1/3 off my compile times today.  Looking forward to the final version.
I did notice that code changes to reduce expression compile times were not independent.  When one expression was reduced, another near by popped up and took its place with about the same compile times.  But fixing them eventually had a significant impact.  This is not, of course, related to your changes or code.  Its just an observation.

Yes, I noticed the same thing. I sent off an email with a couple of questions to the Apple dev who added it to Xcode earlier. Would like to build a better understanding of why that happened before merging this to master. In my case it was just a simple String property. Nothing complex at all.

For anyone following this - I expect more information about this next week so will park the work on this branch until then...

Merged to master. Still awaiting more info about this option but don't see any harm of merging this in in the meantime.


user requests.Session instead of requests.get|post

It is bad practice to open\close TCP connection for each api request.
Client must create on  __init__ requests.Session and explicitly close it.

How could one fix that @hellysmile?

https://github.com/os/slacker/commit/4405f6c7642ee340c898dc3475462ba04fda3d8f


In rdkafka_sasl_oauthbearer_oidc.c - 'curl/curl.h' file not found

Header Search Paths:
Open your Xcode project, select the target, go to "Build Settings," and add the following path to "Header Search Paths":
/usr/local/opt/curl/include
Library Search Paths:
Add the library path to "Library Search Paths":
/usr/local/opt/curl/lib
Link Binary With Libraries:
Add libcurl.dylib in "Link Binary With Libraries."
installed curl through terminal i did all but still getting the isse please help me out.

Can you try to use the branch from this PR: https://github.com/swift-server/swift-kafka-client/pull/155

Hi Thanks a lot for the response I tried but same issue I am facing can you please help out to resolve this issue


Fix crash on String(describing: value) -> scientific notation.

Gonna fix tomorrow, seems easy.

It needs to use the current format style (not String.init), because otherwise the format/parse asymmetry breaks the percent format style (value is reduced to 100th each time the view is activated).
Problem: String.init was used because parse(format(value)) breaks unexpectedly for some locale-currency pairs.

Used above commented method. It should be fixed in dev branch.


Error: Could not find or load main class com.cooltrickshome.helper.RunProgramDex

Error: Could not find or load main class com.cooltrickshome.helper.RunProgramDex
Encountered errors/warnings while running this program

In general, to run the code on Linux you have to change all occurrences of .; to .:, it seems.

Fixed here, along with fixing the compilation process: https://github.com/CapacitorSet/APKRepatcher


Feature/reorganize dewrangle

Pull Request Name

[ ] closes #xxxx
[ ] README entry added if new functionality
[ ] fixup commits are appropriately squashed

[Description here]
This PR adds functions for checking Dewrangle job status and download results. It also reorganizes the Dewrangle functions to put common functions in a separate file then the ones handling hashing volumes and downloading jobs.

is this related to d3b-420?

@sickler-alex I got this error when I run d3b dewrangle list_jobs
% d3b dewrangle list_jobs -study sd-86n4tk8ekn -bucket d3b-study-us-east-1-prd-sd-32sc9wns
Vm9sdW1lOmNsc3pxODk4cDAwMDI4c29qN3VtODk2cmc=
Traceback (most recent call last):
  File "/Users/xiaoyan/opt/anaconda3/bin/d3b", line 8, in <module>
    sys.exit(main())
  File "/Users/xiaoyan/opt/anaconda3/lib/python3.8/site-packages/d3b_dff_cli/cli.py", line 149, in main
    args.func(args)
  File "/Users/xiaoyan/opt/anaconda3/lib/python3.8/site-packages/d3b_dff_cli/modules/dewrangle/list_jobs.py", line 70, in main
    list_volume_jobs(
  File "/Users/xiaoyan/opt/anaconda3/lib/python3.8/site-packages/d3b_dff_cli/modules/dewrangle/list_jobs.py", line 28, in list_volume_jobs
    jobs = hf.get_volume_jobs(client, volume_id)
  File "/Users/xiaoyan/opt/anaconda3/lib/python3.8/site-packages/d3b_dff_cli/modules/dewrangle/helper_functions.py", line 385, in get_volume_jobs
    comp = datetime.strptime(
TypeError: strptime() argument 1 must be str, not None

@HuangXiaoyan0106 try again. It looks like there was a group of jobs running today. I'm not sure what timezone Dewrangle uses. Maybe those jobs were running when you were testing this? The command is working for me now.


[10.x] Enhance malformed request handling

Solves #50466.
This PR aims to have better handling of malformed requests; in particular those which throw exceptions when certain methods on the request are called, like getMethod with content as described in issue mentioned above.
To Do:

[x] Add and/or adjust tests to verify general behavior
[x] Add test for behavior as specified in #50466
[x] Decide on whether or not to broaden matching to RequestExceptionInterface
[ ] Gather feedback on the approach of this PR

Implementation notes:

I've broadened matching from just SuspiciousOperationException to RequestExceptionInterface, given that Symfony recommends this per documentation in this interface. This is a separate that can be removed if wanted, however it seems more accurate and should generally not make any difference for valid requests. No additional tests have been added for other possible exceptions as part of this broadening; this can be part of a follow-up issue/MR.
Due to CompiledRouteCollection using a copy of the Request instance in the scope of the match method (due to requestWithoutTrailingSlash call), the getMethod call is never called on the 'original' request within the route handling and thus causes an exception when isMethod('HEAD') is performed in the scope of preparing the error response. This is once again caught by the exception handler and then correctly rendered on the second attempt. Albeit technically a little ugly, this is probably not worth addressing further as the outcome is correct and these types of requests should be extremly rare anyways.
The existing Bad hostname provided message seems to be based on this line, but given that the exception also happens on incorrect method values (see test), a generic message seems to be more appropriate.

Hey @jnoordsij if you would like feedback on this PR please mark it as ready for review.

Hey @jnoordsij - this PR makes sense to me, but can you send it to 11.x? Thanks!


np.int is throwing a deprecation error

https://github.com/EpistasisLab/scikit-mdr/blob/master/mdr/mdr.py#L126
is throwing
DeprecationWarning: np.int  is a deprecated alias for the builtin int. To silence this warning, use int by itself. Doing this will not modify any behavior and is safe. When replacing np.int, you may wish to use e.g. np.int64 or np.int32 to specify the precision. If you wish to review your current use, check the release note link for additional information.
Numpy version: 1.24.2
Python version 3.9.1
Deprecation details can be found here

Confirmed over on https://github.com/conda-forge/scikit-mdr-feedstock/pull/2.
It's worth a gander at NEP29, or the superset, SPEC0, to get an idea of upstream support windows.


Update ReleaseNotes

This is a test pr

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


Problems with v3.0.1 and ChatConnector in slack using node.js

In slack when I send a direct message to the boot, randomly I don't get the answer and the following error appears in the trace: "ERROR: ChatConnector: receive - invalid token. Check bots app ID & Password.")
I'm using the node framework.

There was one similar

getting the same issue.   also getting The remote server returned an error: (409) Conflict. when I try to save the upgrade of my bot in the dev.botframework site.
I've set my api/messages endpoint to SSL, updated my appId and appPassword.  My bot works using the consoleConnector, so, I have correctly updated my code for v3.0.1.
I also see this ERROR: ChatConnector: receive - invalid token. Check bots app ID & Password. in the logs.

For reference, it was this one: https://github.com/Microsoft/BotBuilder/issues/657

I had to delete my old v1 bot, and create a new v3 bot from scratch at dev.botframwork.com -- and  create new MS App -- for the 'The remote server returned an error: (409) Conflict.' error to go away.  My newly created bot had no problem connecting to my newly migrated v3 code.
-Colin


Time Series Forecasting model using Python

updated readme, made proper commenys and replaced .py files with .ipynb

@Rutikab12 @Niketkumardheeryan


Docs: draw the logic graph

Even after navigating through the code quite some times, I'm still not sure what happens when generating or updating a project.
I think having this graph would help tremendously new users to understand how Copier works, but developers as well, and help a lot when thinking about design and new features implementation.
For example, it would help resolve these issues: #196, #197, #238 and #240.
Of course we should wait for #203, and then maybe use a mermaid-like Markdown extension to draw the graph in the docs 🙂

We have docs now! https://copier.readthedocs.io/en/latest/
These kind of things can now start to get improved, finally!

Would you please tell me if #248 closes this? Or do you think it should be even better explained?

The docs improvements you made are absolutely great, however I still think a drawing would be very beneficial, both for contributors and users 🙂

Did I get it right?

If yes, we can see two issues that were already reported:

the diff is done "pre-task" (#196), which by the way makes running the tasks on the temporary project useless
tasks are ran again on the current project at the end (#238)

Well, this is only the logic graph for the update system, not for the copy, but it seems quite accurate. There's only one "lie" there:

Because this is not true:

the diff is done "pre-task" (#196), which by the way makes running the tasks on the temporary project useless

As you can see in the code:

Here tasks are run in the tmp copy: https://github.com/copier-org/copier/blob/df33b2953b49449318b776ee072fa9559b49df9a/copier/main.py#L247-L255
Here the diff is extracted: https://github.com/copier-org/copier/blob/df33b2953b49449318b776ee072fa9559b49df9a/copier/main.py#L269-L278

Oh, indeed 😕 Then I'm not sure how I got to this conclusion in #196. I'll have to try and reproduce to debug this.

Yes, that'd be.


fix fix bug that "run build\n" not trigger pipeline

Proposed changes
Issue Number: close #xxx

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

run buildall

run buildall


Issues with getting the typings correctly

TypeScript Version:  3.1.0-dev.20180807

Search Terms:
Extend functions
Generic
Auto-complete
Template
Code
type MapFuncs<T, Key extends keyof T = keyof T> = { [K in Key]: Funcs<T[K]> };

type Funcs<T> =
    T extends ()=> infer R ? R :
    T extends (...args: any[]) => infer R ? T : //  1 or more arguments
    T;

interface PocFuncType {
    n: number,
    c: () => number;
    x:  (s: string) => number;
}

const f: MapFuncs<PocFuncType> = {} as any;

f.c; // returns number as expected
f.n; // returns number as expected
f.x; // return function as expected

// is working as expected, but if we try to use it, it doesnt resolve the type correctly
type MyType<T> = {
    computed?: MapFuncs<T>
};

// factory
function create<T>(options?: MyType<T>){
    return null;
}

// it works we set the type
create<Partial<PocFuncType>>({
    computed: {
        c: 1,

        x(s) {
            if(!this.c){
                return 0
            }
            return this.c;
        },
    }
})

// it sets the {computed?: mapFuncs<any>}
create({
    // doesn't pick up the correct types, is setting as any
    computed:{
        data(){
            return 1;
        },
        dataReturn (){
            return this.data; // data is any, it should be number
        }

    }
})

create<Partial<PocFuncType>>({
    computed: {
        c: 1,

         x(s) {
            if(!this.c){
                return 0
            }
            return this.r; // invalid prop r, doesn't exist
        },
    }
})

Expected behavior:
this.data in dataReturn() should be interpreted as number based on the Funcs<T> type.
return this.r;  should throw an error Cannot find name 'r'
Actual behavior:
this.data is interpreted different depending on the IDE (not sure if this is typescript compiler issue)

Playground : this is any
Visual Studio Code: this is resolve correctly but the props are all any making not as usefull
Webstorm: just ignores Funcs<T>

return this.r compiler doesn't complain about it, even if it doesn't exist on the type.
Playground Link:
playground
Related Issues:

In a simplified test case:
type MapFuncs<T> = { [K in keyof T]: Funcs<T[K]> };
type Funcs<T> = T extends () => infer R ? R : T;

declare function create<T>(options?: MapFuncs<T>): T;

create({
    data() { return 1; },
    dataReturn() { return this.data * 2; },
});

What do you expect the inferred type argument for the create call to be? We can't use { data(): number, dataReturn(): number } because Funcs<T> will turn that into just number.

What do you expect the inferred type argument for the create call to be?
I expect Funcs<T> to convert the methods to be the result type if is a method without arguments: { data: number, dataReturn: number}

on the case of:
create({
    data() { return 1; },
    dataReturn() { return this.data * 2; },
    calculate(a: number, b: number){
      return a+b;
   }
});

// expect: { data: number, dataReturn: number, calculate: (a: number, b:number)=>number }

A practical example of this is VueJs when using Vue.extend(options?)
Other thing is the compiler doesn't throw error:
create({
    data() { return  this.empty; }, // empty doesn't exist nor is defined
});

@pikax You probably don't have "strict": true set in your tsconfig, so this is allowed to be any.
Based on what you're saying it sounds like you have the parameter and return type reversed? You also need to set ThisType if this is the type of the returned object and not the type of the parameter object.
type MapFuncs<T> = { [K in keyof T]: Funcs<T[K]> };
type Funcs<T> = T extends () => infer R ? R : T;

declare function create<T>(options?: T & ThisType<MapFuncs<T>>): MapFuncs<T>;

const x = create({
    data() { return 1; },
    dataReturn(): number { return this.data * 2; },
});
x.data * x.dataReturn; // works

@pikax You probably don't have "strict": true set in your tsconfig, so this is allowed to be any.
Sorry, forget using tsc index.ts doesn't use the tsconfig

That seems to be work, thank you, is there any documentation for ThisType and other interfaces?

Microsoft/TypeScript-Handbook#649


Use '*const libc::c_char' instead of '*const i8' for lstat argument

Following https://github.com/romanz/electrs/issues/52 (building on Raspberry Pi fails).

This was pushed to crates.io as v0.3.4. Thanks for the fix!


Thanks, and Resource Owner "password" grant

This is a wonderful demonstration project.  Thanks for putting it together.
I'm trying out the various grants and permissions and learning about the Spring OAuth implementation.  That's all great.
I decided to see if I could implement "Password Grant", but haven't had much luck.  Here is the essence of what i've tried.  (I've tried many variations too :-)

I created a new oauth_client_details record like this.

INSERT INTO oauth_client_details
(client_id, resource_ids, client_secret, scope, authorized_grant_types, web_server_redirect_uri, authorities, access_token_validity, refresh_token_validity, additional_information, autoapprove)
VALUES
('password-client', 'todo-services', 'password-client-secret', 'read,write', 'client_credentials, refresh_token, password', '', 'ROLE_ADMIN', 7200, 0, NULL, 'false');

I rebuilt, restarted, etc.    This second test tells me that the "password-client" is found, and that the "authorized_grant_types" includes "client_credentials" and that it is reading it from the database.
===
Did you ever make more progress on implementing "password" grant?  I'll be investigating and if I solve it I will report it back here.
Thanks, Tom

I think I solved this.  The big mistake I had was an extra space after the commas in the authorized_grant_types column.

In AuthorizationServerConfigurerAdapter inject an authenticationManager

import org.springframework.security.authentication.AuthenticationManager;

public class OAuthConfiguration extends AuthorizationServerConfigurerAdapter {
   @Autowired
   private AuthenticationManager authenticationManager;

  ...
    @Override
    public void configure(AuthorizationServerEndpointsConfigurer endpoints) throws Exception {
    	endpoints.authenticationManager(authenticationManager);
        endpoints
                .approvalStore(approvalStore())
                .authorizationCodeServices(authorizationCodeServices())
                .tokenStore(tokenStore());
    }

Add the client definition (note - no spaces after the commas.  VERY IMPORTANT!)

INSERT INTO oauth_client_details
  (client_id, resource_ids, client_secret, scope, authorized_grant_types, web_server_redirect_uri, authorities, access_token_validity, refresh_token_validity, additional_information, autoapprove)
VALUES
  ('password-client', 'todo-services', 'password-client-secret', 'read,write', 'client_credentials,refresh_token,password', '', 'ROLE_ADMIN', 7200, 0, NULL, 'false');

Test is

$ curl -s -u password-client:password-client-secret -X POST localhost:8081/oauth/token -d 'grant_type=password&username=user&password=user'
{"access_token":"0449a561-7a2e-4a0f-9fcc-18f59479b643","token_type":"bearer","refresh_token":"79862523-338a-442e-8031-63339eaa888d","expires_in":6145,"scope":"read write"}

Hey! Sorry for the late answer (Easter with family...)! Glad that the project helps you.
Thanks for your detailed report! I actually did not yet try the password grant yet. Seems like you got it to work.
I'd be interested why the authentication manager has to be set explicitly on the endpoints! If I find the time I'll look into it soon and try to write an example client that showcases this flow.
I also already started to migrate to Spring Boot 2 (although I would keep the 1.x version on a branch since not everyone has the flexibility to do that) which has some interesting changes.


Include ztunnel in release

To do it properly, need https://github.com/istio/ztunnel/issues/394. For now this is a hack to unblock amd64 release.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio_exp
bbd7641d8ae764470c263533bbeb81716f90c1e0
link
true
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio_exp
bbd7641d8ae764470c263533bbeb81716f90c1e0
link
true
/test release-test

integ-ambient_istio_experimental-ambient
bbd7641d8ae764470c263533bbeb81716f90c1e0
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio_exp
10c4cde468be5864c3d417328e684397a330c5f1
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio_exp
10c4cde468be5864c3d417328e684397a330c5f1
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security


unknown options: -ios_simulator_version_min -sdk_version

./gradlew createSwiftPackage fails with
e: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld invocation reported errors
ld: unknown options: -ios_simulator_version_min -sdk_version
since macOS 14

Updating dependencies to the latest helped

@tristangrichard do you mind sharing what kind of dependencies you updated?

I don't recall exactly what did the trick but from I can in the commit that I bumped to following versions:
kotlin("multiplatform").version("1.9.10").apply(false)
kotlin("plugin.serialization") version "1.9.10"
id("io.github.luca992.multiplatform-swiftpackage") version "2.1.4"
jvmTarget = "17"


Input bindings don't update when changes are reverted within a setter or changeHandler

I think these examples will show the issue clearly enough to void more explanation. The interpolated text shows the real value but the inputs don't revert to the underlying value.
getter/setter example: https://gist.run/?id=8c56fe352fd849462d39311ede2c8b5d
computed getter/setter example: https://gist.run/?id=14ce505a70736ca3c76943ac762fe836
changeHandler example: https://gist.run/?id=45e93cac4e74d8ffb702325d56a7192a
I believe the same can be said for textboxes too. I have alarm limits whose ranges are validated (which is related to this). If the limit is at 100, it cannot exceed 100 and 101 is entered it is reverted to a value of 100 but the input itself doesn't reflect this change.
Any ideas? Is this something that can be fixed in the binding system?

I implemented a work around by using a binding signaler on the input - I don't consider this an acceptable 'fix' however.
Below is code for the numeric limit input. I only signal when the value has been clamped back to the same old value (clamped && limit === oldLimit).
<input value.bind="limitConfig.margin & signal:limitConfig.marginSignal & updateTrigger:'blur'">

  limitChanged(limit, oldLimit) {
    if (typeof limit !== 'number') {
      limit = Number(limit);
      this.limit = limit;
    }

    let clamped = false;

    if (this.enabled) {
      if (this.lowerLimitConfig !== null && this.lowerLimitConfig.upperBound > limit) {
        limit = this.lowerLimitConfig.upperBound;
        clamped = true;
      }

      if (this.upperLimitConfig !== null && this.upperLimitConfig.lowerBound < limit) {
        limit = this.upperLimitConfig.lowerBound;
        clamped = true;
      }
    }

    if (clamped) {
      this.limit = limit;
    }

    if (clamped && limit === oldLimit) {
      this.bindingSignaler.signal(this.limitSignal);
    }
  }

A beforeUpdate(newValue,oldValue, cancel) would be nice here
I've opened an issue some while ago with a very similar request:
https://github.com/aurelia/templating-resources/issues/137
The answer is once more: a custom bindingbehaviour :)
It turns out that with Aurelia you can easely generate demo apps and prototypes. But when it comes down to some very usual use cases like converting values (http://stackoverflow.com/questions/37882659/force-view-to-be-updated-from-within-a-valueconverter), or rejecting changes like mentioned here we often need to take a deep plunge and use much more advanced concepts, possibly scaring away people from using this nice framework after they have mastered the demo apps and tutorial phase.
So what can we do.
Either those missing pieces in the default concepts in valueConverter and propertyChanged gets added or a set of default bindingbehaviours should be added to the product.

Thanks for the link to that issue @fopsdev - those advanced techniques are quite well... advanced! I agree this should be a little easier to accomplish.
However I think to fix this issue in particular it needn't be something the developer has to handle themselves. I expect the input (value) binding should recheck the value after setting it and reset the input/checked value appropriately.

I'm with @AdamWillden on this. I was quite surprised to find that value converters don't support this behavior out of the box. It's a common use case to do some normalisation like trim on an input, and I would like to be able to simply specify this as:
<input value.bind="myProp | trim & validate" />

If I use something like the above now, the normalised value is passed to the model and used for validation - which is exactly what we want. However, some changes applied by trim are reflected back to the screen and others aren't, which results in a very confusing user experience.
For example: if I type some spaces in the input with the trim converter, the first space is ignored (if the model value started with undefined) and the next ones are entered. If I type a character after that, all the preceding spaces suddenly disappear. And if I type any spaces afterwards, they aren't removed even though the value that will eventually be used won't include these spaces.
Right now if I want to normalise and keep my screen and model value in sync, my options are to

create a binding behavior  to wrap the binding's updateSource method and if necessary call updateTarget with the normalised value
build a custom attribute or element to do the normalisation and keep the view value in sync
add a blur / input trigger and do the normalisation and validation myself

These solutions are all doable, but IMO overkill for what should be a simple and common use case.

For now I've built this TypeScript base class for binding behaviors that do normalisation. Maybe it will be of use to others.
export abstract class NormalisationBindingBehavior {

	protected abstract normalise(value: any): any;

	private get scopeName() {
		return this.constructor.name;
	}

	bind(binding: any) {
		const normalise = this.normalise.bind(this);
		const updateSource = binding.updateSource.bind(binding);

		binding[`${this.scopeName}UpdateSourceOriginal`] = binding.updateSource;
		binding.updateSource = function(value: any) {
			const normal = normalise(value);
			updateSource(normal);
			if (normal !== value) {
				this.updateTarget(normal);
			}
		};
	}

	unbind(binding: any) {
		binding.updateSource = binding[`${this.scopeName}UpdateSourceOriginal`];
		delete binding[`${this.scopeName}UpdateSourceOriginal`];
	}
}

Example use:
import {NormalisationBindingBehavior} from "./normalisation-binding-behavior";

export class TrimBindingBehavior extends NormalisationBindingBehavior {

	protected normalise(value: string) {
		return value.trim();
	}
}

<template>
  <require from="bindingbehaviors/trim"></require>

  <input value.bind="myVal & updateTrigger:'blur' & trim"/>
</template>

(Note that I add updateTrigger:'blur' so that the user can still add spaces between words - if the input is trimmed after every change it wouldn't be possible to type spaces at all)


cmctl convert not working for converting certmanager.k8s.io/v1alpha1 to cert-manager.io/v1

Describe the bug:
cmctl convert is unable to convert certmanager.k8s.io/v1alpha1 to cert-manager.io/v1.
Expected behaviour:
I expect cmctl convert to convert Certificates to cert-manager.k8s.io/v1 and output on stdout.
Steps to reproduce the bug:
$ cat cert.yaml
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  annotations:
    name: wildcard-dev-pac
    namespace: pac-uat
spec:
  acme:
    config:
      - dns01:
        ingressClass: nginx
        provider: route53
        domains:
        - '*.cz.uat.pac.corp.foo.com'
        - cz.uat.pac.corp.foo.com
  dnsNames:
  - '*.cz.uat.pac.corp.foo.com'
  - cz.uat.pac.corp.foo.com
  issuerRef:
    kind: ClusterIssuer
    name: letsencrypt-prod
  secretName: wildcard-dev-pac
$ cmctl convert --output-version cert-manager.io/v1 -f cert.yaml
error: unable to decode "cert.yaml": no kind "Certificate" is registered for version "certmanager.k8s.io/v1alpha1" in scheme "pkg/runtime/scheme.go:100"

Anything else we need to know?:
Environment details::

Kubernetes version: 1.20
cert-manager version: v0.10.0
cmctl version: v1.9.1
Install method: Helm

/kind bug

i am looking for same thing.. we have 10000s of cert with certmanager.k8s.io/v1alpha1 version.. for some reason, even kubectl convert is not working... i think cmctl convert tool supports conversion between different api version of same group..like cert-manager.io/v1beta1 to cert-manager.io/v1..atleast that's what i see in certmanager conversion logic..

v1alpha1 has never been supported by conversion as it represented a dramatic shift in how resources are configured (configuration for the ACME provider was moved from the Certificate object to the Issuer in a way that isn't possible to convert).
For details on how to go from v1alpha1 to v1alpha2 (or any other newer release which can be converted), see the release notes for v0.11: https://cert-manager.io/docs/release-notes/release-notes-0.11
We won't be changing this/support this in future either - note that cert-manager v0.11 came out almost 3 years ago to the day, which means your deployment is significantly behind and out of our support window! https://github.com/cert-manager/cert-manager/releases/tag/v0.11.0


Change #Lineage.joinSchema from _ (top) to open struct with version

#Lineage.joinSchema defines the join/least upper bound that must be maintained by all schemas in a lineage. Currently, it starts as top, _:
https://github.com/grafana/thema/blob/b7b433093f2fd56c11e68a45b0c3ee7b7850ca8c/lineage.cue#L11-L24
This isn't great:

It makes injecting a themaVersion field complicated, since we can't universally assume all schemas are a struct at base (could be scalar or list)

We can't even assume that all schemas are structs within a lineage

It's plausible that other bits of thema's helper CUE logic may be subtly assuming a struct type here as well
I don't see a use case for scalars or lists as a base schema type, for essentially the same reasons that

I'm sure i want it to be an open struct, {...}. i was worried about open/closedness here, but after some poking on the playground, i think we can make the shift without forcing any decisions on openness, which is great - that's a can of worms.
I don't see an immediate reason why this change would be anything other than changing just the one line - i'm mostly writing this issue up for posterity and as a place to dump that link to the playground. (also have it in a gist)

Thinking on this further, it may be that we want to actually inject this instead:
joinSchema: {
    themaVersion?: [int & >= 0, int & >= 0]
    ...
}

But i'll probably leave that for a follow-up

When talking all this through with @Lyoness and @myitcv earlier today, i realized that this, the possibility of adding the themaVersion? field, and #76 can be taken care of all in one motion by something like this:

Making joinSchema into {...} as this originally proposed, and renaming it to `allSchem
Adding an allSchemasMust, which is a struct that must be valid when unified against all schemas in the lineage, but the result of that unification is not part of the actual used schema.

Not going to inject version just yet. Will explore that in a later pass.


Can't translate search button

Hi @Floppy!!
After reviewing the changes applied and the new version of Manyfold I can confirm that all translations are correct except for some components that follow in English because they are not available to translate currently such as the search button

And on the other hand, I found a strange error in the html. It seems that when the application is in English everything works correctly but when I make the language change, I have a strange HTML component:

I don’t know if you need more information about this, but I am at your disposal to help you

Originally posted by @juanjomurga in https://github.com/manyfold3d/manyfold/issues/2769#issuecomment-2402907549

thanks @juanjomurga, good spot on the search button! I think I know what the other thing is too, I'll get it fixed.

#2908 solves both of these issues. Should be in the next release.

I have been checking which components don't have a translation. I pass you a list, although I sure that I didn't find all:
Message when the session on the server expires:
Text: Your session has expired. Please log in again to continue.
Page Upload file:
Label Creator
Label Collection
Label Licence
Massive Edition
Label Creator
Label Collection
Label Licence
Label New library
Label Organize
In table list:
	Column _Collection_
	Column _Creator_

Page a model
Button Follow
Page Editor of a model
Label Preview file
Page Massive editor of model files
Label Printed
Label Presupported
Label Y up
Button Split selected files into a new model
In table:
	Column _Name_

Page Editor of a model file
Label Presupported version
Page New Creator
TextBox label Any related web page
--Page when selecting a creator
Button Follow
--Page New Collection
TextBox label Any related web page

Oh, excellent, thank you!

@juanjomurga OK, I've found a couple more untranslatable strings from that list and will sync those up to translation.io. But, the rest should be translatable - have a look at the activerecord.attributes.* keys.


Enhancement use read buffer when read index bytes in compound reader

Proposed changes
Read IO would be a problem when reading inverted index from disk.
Using read buffer to reduce IO.
Problem summary
Set use buffer flag to be true when reading internal bytes in compound reader for inverted index.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

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

run buildall


chore(factorial): add translation fr-FR

add fr-FR (french) translation for Algorithm - Math - Factorial README.md
update link to this translation from fr-FR root README.md
update link list to other language in factorial english README.md

I close this to make a bigger one with all the maths translations


refactor!: Move tableprinter into internal package

Prerequisite checklist

[x] Read the contribution guidelines regarding submitting new changes to the project;
[x] Tested your changes against relevant architectures and platforms;
[ ] Ran make fmt on your commit series before opening this PR;
[ ] Updated relevant documentation.

Description of changes
Moved tableprinter from utils package into its own tableprinter pkg inside internal directory.

@nderjung Created this new PR to ease merging and Moved tableprinter into internal directory & updated all the refrences.

Hi @MdSahil-oss, just one change needs to be addressed.  Move tableprinter into internal package

Signed-off-by: ...etc.

Done! 👍🏽  @nderjung.


[BUG] Import Error

Describe the bug
Getting the following error when running the example code.
##Code##
import torch
from gemini_torch import Gemini
Initialize the model
model = Gemini(
num_tokens=50432,
max_seq_len=8192,
dim=2560,
depth=32,
dim_head=128,
heads=24,
use_abs_pos_emb=False,
alibi_pos_bias=True,
alibi_num_heads=12,
rotary_xpos=True,
attn_flash=True,
attn_kv_heads=2,
qk_norm=True,
attn_qk_norm=True,
attn_qk_norm_dim_scale=True,
)
Initialize the text random tokens
x = torch.randint(0, 50432, (1, 8192))
Apply model to x
y = model(x)
Print logits
print(y)
##Error below##
ImportError                               Traceback (most recent call last)
Input In [1], in <cell line: 2>()
1 import torch
----> 2 from gemini_torch import Gemini
4 # Initialize the model
5 model = Gemini(
6     num_tokens=50432,
7     max_seq_len=8192,
(...)
20     attn_qk_norm_dim_scale=True,
21 )
File E:\Anaconda3\lib\site-packages\gemini_torch_init_.py:2, in
1 from gemini_torch.model import Gemini
----> 2 from gemini_torch.utils import ImgToTransformer, AudioToTransformer
3 from gemini_torch.tokenizer import MultimodalSentencePieceTokenizer
5 all = [
6     "Gemini",
7     "ImgToTransformer",
8     "AudioToTransformer",
9     "MultimodalSentencePieceTokenizer",
10 ]
ImportError: cannot import name 'AudioToTransformer' from 'gemini_torch.utils' (E:\Anaconda3\lib\site-packages\gemini_torch\utils.py)
To Reproduce
Steps to reproduce the behavior:

Install the library by following the Readme.md
Run the example.py in JupyterNotebooks
See error

Expected behavior
The program displays a matrix.
Screenshot attached.

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

@corous this bug has been eliminated


Add an option in the UI to send report by email

In the saved reports page there should be a new option to "Send by email" that triggers the controller action created in https://github.com/Reconmap/api-backend/issues/23

Fixed in e8ea6cac8998c46ec9f61a1f8e972310697b3a74


Mark commands do not work

Mark commands look like not to work. Is it only on my PC?
https://github.com/inkdropapp/inkdrop-vim/blob/master/keymaps/vim.json#L85-L87
When I set other key to the commands, but the marking did not work in a similar way.
Other keybinds work correctly. (ex: f vim:find)

Oops, there are duplicate keybinds:
"\"": "vim:move-to-mark"
"\"": "vim:register-prefix"

vim:move-to-mark should be bound with ' as the original CodeMirror implementation:
https://github.com/inkdropapp/inkdrop-vim/blob/master/src/keymap.js#L111

landed in v2.1.1🎉

Thank you for quick fix!


CI failing for macOS / iOS builds

The last 3 runs failed due to macOS and iOS failures...
https://github.com/CesiumGS/cesium-unreal/actions/runs/9179032103
https://github.com/CesiumGS/cesium-unreal/actions/runs/9158518614
https://github.com/CesiumGS/cesium-unreal/actions/runs/9118270660
Seeing some space related errors, hopefully that's all it is...
No space left on device : '/Users/runner/runners/2.316.1/_diag/pages/489f42eb-07f5-4d6d-a2c6-58e3fd7262b3_9b070b38-896b-5cd
Might need a similar space fix as we did on Linux...
https://github.com/CesiumGS/cesium-unreal/blob/3f830c5fadb765a66e85e782dc7d56f52ffc9141/.github/actions/install-unreal-linux/action.yml#L30

Disk space available on various GitHub macOS runners:

Runner
Disk Space Free

macos-12
63 GiB

macos-13
155 GiB

macos-14
97 GiB

macos-latest
97 GiB

We're currently running on macos-12, and 63 GiB is really tight for the UE ZIP plus extracting it, and getting under the limit by excluding things from extraction is going to be tedious and error prone (I tried and have failed so far). I think the best move is to switch to the macos-13 or macos-14 runner instead.


Interface blocked on open two times Dialog window

Hi Samir,
seems like something is blocking interface after opening datepicker in a dialog window more than once.
You can test it in your plunker example.

This is known issue, it is caused by angular material dialoge service md-scroll-mask.
its bug and work around for that is
       vm.showCalander = function(ev){           options.targetEvent = ev;           smDateTimePicker(vm.currentDate,options)           .then(function(selectedDate) {             vm.currentDate = selectedDate;             var ele = document.getElementsByClassName("md-scroll-mask");             if(ele.length!==0){                  angular.element(ele).remove();             }                       });                   }
you cann removed it once ur date is selected


Fix import path of Spinning usage

What does this PR do?
This PR updates the import path of the Spinning usage.
Where should the reviewer start?
What testing has been done on this PR?
How should this be manually tested?
Any background context you want to provide?
What are the relevant issues?
Screenshots (if appropriate)

Thanks for your contribution.


Update Plugin Version in helm chart

Issue #, if available:
Description of changes:
Once #829 merges and postsubmits complete. Merge this to trigger new deployment of plugin with updated version for testing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


[Bug]: Optimize error messages when the database is empty during template creation

ODC version
ODC4.3.0
OB version
No related.
What happened?
Optimize error messages when the database is empty during template creation.

What did you expect to happen?
Error messages should be optimized，such as：The number of databases must be greater than 1 and not more than 100.
How can we reproduce it (as minimally and precisely as possible)?
Do not select the database when creating the template and save it.
Anything else we need to know?
No response

Save the template and when the data is empty, it will prompt correct


Fix some typos (found by codespell)

Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

That file is copied from spec, the typos have since been fixed based on the PR in OCR-D/spec. Thanks!

Unrelated question: How is https://ocr-d.github.io/ managed, or more precisely, how can I send pull requests for that content?

https://github.com/OCR-D/ocr-d.github.io should be public now.

Thank you!


Layout

Simple blog layout

Good work @WendyStonegood  :+1:
Thanks for contributing.
Hoping more collaboration in future. :smile: