primordic/IssueDupesLite huggingface dataset:
Repository: lancedb/lancedb

Issue #1852: bug(python): Query limit([-1 | 0 | None]) not being respected
Created: 2024-11-20T03:51:23Z
LanceDB version
v0.16.0
What happened?
The latest version of lancedb is not respecting the Query limit when set to a "no limit" value. See https://lancedb.github.io/lancedb/python/python/#lancedb.query.LanceQueryBuilder.limit:

Call this method and pass 0, a negative value, or None to remove the limit.

Are there known steps to reproduce?
results_df = (
    db.open_table(lance_schemas.TABLE_NAME)
    .search()
    .select(select_columns)
    .limit(-1)
    .to_pandas()
)

In lancedb v0.15.0 this returns all the results of my table. In lancedb v0.16.0, it only returns the default 10 results.

Duplicate issue #1983: bug(python): plain search limited to 10 by default (regression)
Created: 2024-12-26T16:02:54Z
LanceDB version
v0.17.2
What happened?
New behavior : all query are limited to 10. Typically table.to_arrow() is limited now. According to the BaseQuery doc, plan queries are not limited.
Are there known steps to reproduce?
db = await lancedb.connect_async(uri)
t = await db.open_table(table)
print(await t.to_arrow())

Closing comment (2025-01-06T17:42:05Z): I think this may be a duplicate of #1852
See answer in #1852 (comment)
Repository: lancedb/lancedb

Issue #1517: Feature: add synchronous `to_list` method to the Python async API
Created: 2024-08-07T15:59:30Z
SDK
Python
Description
Because of the difference between the two api (working with asynchronous table and synchronous table) we have to rewrite most of the code, it is not always handy and does not always get the same result.
It would be great to have the same method when working with an asynchronous table when vector_search

Duplicate issue #1515: Feature: `to_list` missing from python async API
Created: 2024-08-07T15:52:46Z
SDK
Python
Description
The synchronous API had a to_list method that was a sibling to to_arrow and to_pandas.  The method simply did to_arrow().to_pylist() but could be helpful for people that are not familiar with arrow and just want to get python data directly.
It would be pretty easy to add back into the async API.

Closing comment (2024-08-07T16:21:44Z): Closing as duplicate of #1517
Repository: lancedb/lancedb

Issue #521: EmbeddingFunction should work across device
Created: 2023-09-30T18:24:52Z
Currently the embedding function does not explicitly move the input to device or the output back to CPU. So if created with device != cpu (the default), then an exception is encountered complaining that the weights and the data must be on the same device

Duplicate issue #1958: bug(python): lancedb saved torch device and it isn't easily mutable
Created: 2024-12-18T19:08:54Z
LanceDB version
No response
What happened?
Currently when adding an embedding over the lancedb registry we are not capable of overwriting / changing the device name. This make the use of lancedb much more difficult than needed. The same is for a lesser extend true for the model name but easier to workaround.
I had a hardware breakdown. Since for read only use cpu isn't that big of a problem we wanted to switch but couldn't.
Are there known steps to reproduce?
Create a table with a vector with GPU as a device. Change the device to CPU / execute on a CPU only docker container and the system will not be able to load.

Closing comment (2024-12-19T00:30:11Z): Could you give me the actual number? The issue you cited is this issue.

Sorry about that. Updated.
Duplicate of #521
Repository: languagetool-org/languagetool

Issue #4630: UNPAIRED_BRACKETS: improve suggestions
Created: 2021-03-17T10:04:09Z
In the rules for XX_UNPAIRED_BRACKETS (in several languages) suggestions are not provided. It is not possible, in general, to know where to put the suggestion. But in some contexts like «This is a sentence with wrong quotes”, good suggestions could be generated.

Duplicate issue #5313: [de] annoying suggestion when applying TYPOGRAFISCHE_ANFUEHRUNGSZEICHEN
Created: 2021-07-07T09:47:50Z
"UNPAIRED_BRACKETS" should not make a suggestion when "TYPOGRAFISCHE_ANFUEHRUNGSZEICHEN" already matched.

  
    
    

    Jul-07-2021.11-47-00.mp4

Closing comment (2021-07-08T07:57:33Z): Related to #4630
Repository: languagetool-org/languagetool

Issue #1926: [es] Spanish names with "acento"
Created: 2019-09-09T16:38:05Z
Feedback from a user:

Spanish names such as Tomas and Hector which in Spanish have an "acento" are not detected by the software as mistakes when there is no"acento"

I can confirm:

Duplicate issue #1949: [es] false alarms PREPOSICION_VERBO
Created: 2019-09-17T16:35:04Z
I collected some phrases where users disabled the rule. Not sure if these are false alarms (I don't speak Spanish).

Formación del vehiculo en
y soy de parla y estoy
del diagnostico o grado d...
has clic en el numero. Gracias
le espera en linea
ocurrido con será un placer
el 0456 entre lineas fijas
programa de apoya al creado
Por ultimo, con que
Agencia sin linea
con numero de
en el genero urbano
Entra en la pagina oficial
No. de paginas 1

@jaumeortola I saw that you were working on that rule recently, does this help?

Closing comment (2019-09-17T16:43:43Z): Seems like some words are missing an "acento". So it seems partially related to #1926
Repository: languagetool-org/languagetool

Issue #4308: Support BasicAuth in browser extension
Created: 2021-02-06T21:02:38Z
I installed my own server and I added Basic Auth to protect it. It works from the command line:
curl --data "language=en-US&text=a simple test" https://<user>:<pw>@languagetool.domain.tld/v2/check

{"software":{"name":"LanguageTool","version":"5.2","buildDate":"2020-12-30 14:55","apiVersion":1,"premium":false,"premiumHint":"You might be missing errors only the Premium version can find. Contact us at support<at>languagetoolplus.com.","status":""},"warnings":{"incompleteResults":false},"language":{"name":"English (US)","code":"en-US","detectedLanguage":{"name":"French","code":"fr","confidence":0.815771}},"matches":[{"message":"This sentence does not start with an uppercase letter.","shortMessage":"","replacements":[{"value":"A"}],"offset":0,"length":1,"context":{"text":"a simple test","offset":0,"length":1},"sentence":"a simple test","type":{"typeName":"Other"},"rule":{"id":"UPPERCASE_SENTENCE_START","description":"Checks that a sentence starts with an uppercase letter","issueType":"typographical","category":{"id":"CASING","name":"Capitalization"}},"ignoreForIncompleteSentence":true,"contextForSureMatch":-1}]}

The browser extension is not working. The extension works when the Basic Auth part of the URL is omitted. I also tried using only lowercase names and passwords, only URL save characters, but I had no luck. Am I missing something?

Duplicate issue #6349: Basic auth support
Created: 2022-02-18T22:37:10Z
Hello,
Would it be possible to add support for basic authentication in the Firefox extension? Is the extension code open sourced somewhere?
The extension throws the following error when using https://foo:bar@foo.bar/v2:
Cannot connect to https://foo:bar@foo.bar/v2/check - please check your internet connection or try again in a minute (#1, code=undefined)

Closing comment (2023-01-01T20:37:02Z): Closing, duplicate of #4308
Repository: languagetool-org/languagetool

Issue #3170: ArrayIndexOutOfBoundsException
Created: 2020-06-28T08:08:27Z

Duplicate issue #3206: jre error
Created: 2020-07-05T22:19:17Z
as per this link bellow, a screen shoot of the error warning is provided
after Changing the JRE from openJDK   11, 13, 14 the same error persist
it LO version 6.4.4.2 running on ubuntu 20.04 and the file type is docx files combined in as master doc file of LO.
a link to the screenshoot of the error is provided
link: https://florycq-my.sharepoint.com/:i:/g/personal/m12919_vip365_ca/EeVpSakwRDpJjNC5gwJFqdEBW2DSYqxZ7ilXF-9h_6xhOQ?e=aiQZSI

Closing comment (2020-07-06T10:01:10Z): This is a duplicate of #3170
Repository: languagetool-org/languagetool

Issue #3731: [de] false alarms DE_AGREEMENT
Created: 2020-10-21T05:29:59Z
Das Wetter schlägt gern in die hohen Türme.


Vielen Dank für die guten Ratschläge!

Duplicate issue #3730: [de] false alarm DE_AGREEMENT
Created: 2020-10-21T05:28:08Z
Das Wetter schlägt gern in die hohen Türme.

Closing comment (2020-10-23T20:17:30Z): Duplicate of #3731
Repository: languagetool-org/languagetool

Issue #766: Bilingual support
Created: 2017-08-11T08:37:37Z
See languagetool-org/languagetool-browser-addon#75 for ideas - but it's not specific to the add-on, so the issue should be discussed here.
Keywords: mixed languages support

Duplicate issue #819: Suggestion: auto-detect language for quotes
Created: 2017-10-24T15:10:24Z
It is often the case that some text will contain quotes written in another language. This raises lots of errors and clogs the error list so that looking for legitimate errors can become frustrating. I suggest that all text found between two quotation marks be either skipped or analyzed and checked in its original language.

Closing comment (2018-02-02T10:54:52Z): Closing, mostly a duplicate #766
Repository: languagetool-org/languagetool

Issue #1951: [en] false alarm PUNCTUATION_PARAGRAPH_END
Created: 2019-09-18T12:57:10Z
When pasting emails I always stumble upon this:

Haven't checked all languages but it doesn't seem to happen in German and French.

Duplicate issue #1962: [de] false alarm PUNCTUATION_PARAGRAPH_END
Created: 2019-09-23T11:55:04Z
Da werde ich leicht sehr sauer. Möchtest du das?
Gruß vom Bruno

Closing comment (2019-09-23T11:55:40Z): Related to: #1951
Repository: latex3/latex3

Issue #328: l3docstrip: use @@@@ when you need @@?
Created: 2017-01-25T11:56:29Z
Coming back to unicode-math after quite some time, I discovered this at the top of my dtx file:
\input l3docstrip.tex
\begingroup
  \catcode`\_ = 12 %
  \long\gdef\prepareActiveModule#1{%
    \if\relax#1\relax
       \let\replaceModuleInLine\empty
    \else
      \def\replaceModuleInLine{%
        \replaceAllIn\inLine{@@@@}{!!!!!FOURAT!!!!!}%
        \replaceAllIn\inLine{__@@}{__#1}%
        \replaceAllIn\inLine{_@@}{__#1}%
        \replaceAllIn\inLine{@@}{__#1}%
        \replaceAllIn\inLine{!!!!!FOURAT!!!!!}{@@}% i.e., use @@@@ when you need literal @@ in code
      }%
    \fi
  }
\endgroup

I suspect that I needed to do this when interfacing with a fair bit of 2e code… in some ways I think it's nicer than turning the @@ replacement on and off again. On the other hand, for pure expl3 code it should never be needed.
Any thoughts one way or another whether it would be good to add to l3docstrip?

Duplicate issue #323: l3docstrip disable comment
Created: 2016-12-14T17:00:22Z
sometime I want to type \@@par that is replaced by some code.
I could workarround using \cs_set_eq:cc {@@_par} {@ @ par} but it is ugly
At least it should be documented in documentation
% Enable lt3docstrip stripping
%    \begin{macrocode}
%<@@=footmisx>

Closing comment (2018-09-30T15:21:43Z): Duplicate of #328.
Repository: latex3/latex3

Issue #319: Adding `\fp_step_inline:nnnn` and `\fp_step_function:nnnN`
Created: 2016-11-21T12:33:31Z
I believe this would be a useful addition. The caveat would be that the number of steps might be off by one depending on rounding effects due to floating point calculations.
To be honest, I found it useful as part of a set of macros to replace/extend \foreach of PGF.

Duplicate issue #318: Add \fp_step_... functions
Created: 2016-11-21T12:31:57Z
To match \int_step_..., we presumably should have floating point versions.

Closing comment (2016-11-21T12:34:32Z): Dupe of #319
Repository: latex3/latex3

Issue #972: Checking existence in c-type variants
Created: 2021-07-30T06:58:46Z
With c variants, it is possible to use a property list that has never been created. If it is a feature it should be documented.
Actual
Next document outputs "value" whereas no \prop_new:? was ever used.
\documentclass{article}
\begin{document}
\ExplSyntaxOn
\prop_put:cnn{abc}{key}{value}
\prop_item:cn{abc}{key}
\ExplSyntaxOff
\end{document}

Expected
These c variants should raise an error because no abc property list was ever created.
Other functions should raise as well.
Discussion
Actually, no \prop_new:? call is required, which somehow exposes the underlying kernel data structure implementation. Moreover, the c variants silently ignores typing/refactoring errors in client code.

Duplicate issue #983: (doc) \cs_generate_variant:Nn needs a defined parent function?
Created: 2021-08-25T14:14:27Z
Quote from the documentation:

The \cs_generate_variant:Nn function can only be applied if the ⟨parent control sequence⟩ is already defined.

But as the following minimal example shows, the parent function does not need to be defined to be used
in \cs_generate_variant:Nn:
\documentclass{article}
\begin{document}
\ExplSyntaxOn
\cs_if_exist:NTF \__I_am_not_defined:Nn { Defined } { Nope }
\cs_generate_variant:Nn \__I_am_not_defined:Nn { cn }
\ExplSyntaxOff
\end{document}

Using \__I_am_not_defined:cn of created an Undefined control sequence: \__I_am_not_defined:Nn error.

Closing comment (2021-08-28T13:24:34Z): I guess this is similar to #972, although I am not quite sure if I understand the cost-efficiency argument for \cs_generate_variant:Nn. I understand it for prop_item:cn as it can be used in an expansion or mathematical expression and thus checking its existence everytime is redundant. But I do not really see \cs_generate_variant:Nn as something that is used in a loop or in an expression, but rather as an addendum to \cs_new:Npn (So the number of \cs_generate_variant:Nn in a document is capped by the number of\cs_new:Npn). Would it really slow things down that much if it checks its first argument for existence?
Just some thoughts and curiosity on that matter. I also did not know that declaration-checking is costly in LaTeX (I always assumed it to be a quick and easy check).
Repository: latex3/latex3

Issue #843: l3doc: commands and environments to document "things without backslashs" like keys
Created: 2021-01-25T08:50:58Z
There is a growing need to document and index other things than commands, for example key names, hook names, PDF dictionaries, color model names, color export format names and similar.  l3doc is missing here suitable environments and commands to properly format and index these.

Duplicate issue #872: Documenting (and indexing) keys
Created: 2021-04-23T17:07:50Z
The index of interface3.pdf (or any other l3doc-based index) collects commands according to their module.  It ends up listing key-types from l3keys, such as .bool_set_inverse:N, next to commands such as \bool_set_inverse:N, in a category called "bool commands".  This does not seem very helpful, since they are used in very different contexts.
I think l3doc should provide an alternate way to document keys, other than the macro and function environments.

Closing comment (2021-04-25T21:44:12Z): This is a duplicate of #843 .
Repository: latex3/latex3

Issue #843: l3doc: commands and environments to document "things without backslashs" like keys
Created: 2021-01-25T08:50:58Z
There is a growing need to document and index other things than commands, for example key names, hook names, PDF dictionaries, color model names, color export format names and similar.  l3doc is missing here suitable environments and commands to properly format and index these.

Duplicate issue #1354: Better way(s) to index non-command like flag names and key properties
Created: 2023-11-27T06:52:46Z
Currently,

fp flag names documented with module = fp are indexed under "fp commands". Another level 1 name like "fp flags" would be better.
floating-point operators are indexed in level 1. Indexed under "fp operators" in addition would be better.
key properties are indexed under "<module> commands" where <module> is the first part in their names. For example, .tl_set:N under "tl commands" and .groups:n under "groups commands".

Except for key properties, other two types both can be user-defined, hence packages written in expl3 may have similar need to properly index them.

Closing comment (2023-12-22T03:58:20Z): Similar to #843, I am closing this with a link to

#1136
Repository: latex3/latex3

Issue #618: l3doc indexes base form \use:N for \use:c
Created: 2019-08-30T14:18:33Z
l3doc indexes the base form of functions, independently of the used variant. However it ends up indexing inexistent control sequences when a function is defined as the variant to start with. For example, \use:c is not defined on top of \use:N, however the latter is indexed instead:
\documentclass{l3doc}
\begin{document}
\cs{use:c}
\PrintIndex
\end{document}
The easiest way out would be to check whether the base form is defined. Another possibility would be a list of exceptions, but it would require more manual labour...
Also, are there other examples of this issue other than \use:c?

Duplicate issue #892: Documenting F form when TF does not exist
Created: 2021-04-29T10:33:48Z
\file_if_exist_input:nTF is still indexed in interface3.pdf, though deprecated (more precisely, what seems to deprecated is  \file_if_exist:nT).

Closing comment (2021-04-29T14:01:52Z): See #253, which suggests \file_if_exist_input:nnTF (file) (preliminary set up) (true code after the file is input) (false code if not input).  I think we should continue that discussion there.
Here we should keep the indexing issue: the deprecated function \file_if_exist_input:nTF shouldn't be indexed.  What is happening is that \file_if_exist_input:nF is indexed as its base form \file_if_exist_input:nTF.  This is similar to #618 where l3doc assumes that some base form exists when it doesn't actually exist.  Probably the fixes will be related.
Repository: latex3/latex3

Issue #1109: \peek_analysis_map_inline does not work for explicit macro character
Created: 2022-07-03T13:30:31Z
As in title.
MWE: (compile with plain TeX, not LaTeX)
%! TEX program = pdftex
\input expl3-generic.tex
\ExplSyntaxOn
\peek_analysis_map_inline:n {
	\peek_analysis_map_break:
} #
\bye

Error message:
! Parameters must be numbered consecutively.
<to be read again> 
                   ##
l.6 } #
       
? 
! Emergency stop.
<to be read again> 
                   ##
l.6 } #
       

Looks like the code uses \tl_tmp:w to grab delimited argument, but if #1 is an explicit macro character then it's an error.

  
    
      latex3/l3kernel/l3tl-analysis.dtx
    
    
         Line 1278
      in
      ae9d327
    
  
  
    

        
          
           \cs_set_protected:Npn \@@_tmp:w ##1 #1 ##2 ##3 \scan_stop: 
        
    
  


Remark: in comparison, \__tl_analysis_b_char:Nww just check the catcodes one by one. Not sure which method is faster

Duplicate issue #1241: \peek_analysis_map_inline does not work with active character token = implicit param character
Created: 2023-06-30T10:05:18Z
Edit: actually it seems this is fixed in a relatively new version.
--
\ExplSyntaxOn
\catcode `?\active
\let ? #
\peek_analysis_map_inline:n{\peek_analysis_map_break:}?
\stop
Error message:
! Illegal parameter number in definition of \__tl_tmp:w.
<to be read again> 
                   }
l.4 \peek_analysis_map_inline:n{\peek_analysis_map_break:}?
                                                           
?

Closing comment (2023-07-01T08:20:58Z): Dupe of #1109 I think
Repository: latex3/latex3

Issue #491: Runaway argument with fontspec/LuaLaTeX after installing l3kernel 2018-10-17
Created: 2018-10-19T13:32:06Z
I have a document (a book), typeset with Adobe Garamond Pro, that I compile with LuaLaTeX. After the last update of TeXLive it broke (I couldn't compile the document), without any change in the document itself. After restoring l3kernel to the previous version it is OK again (checked with pdf-diff).
tlmgr update log relevant data:
[Fri Oct 19 09:06:16 2018] update: l3kernel (48749 -> 48935)     // broke the document
[Fri Oct 19 14:28:03 2018] restore: l3kernel (48749)                 // document compiles OK

Document compilation log (relevant part, before this the log goes the same way as when compilation succeeds):
Runaway argument?
76543210\q_stop newline  	�������newline  This font family consists o\ETC.
! File ended while scanning use of \__iow_wrap_end_chunk:w.
<inserted text> 
\par 

Linux, TeXLive 2018, LuaTeX 1.07.0

Duplicate issue #492: File ended while scanning use of \__iow_wrap_end_chunk:w
Created: 2018-10-20T09:33:35Z
After update to the latest l3kernel, I have encountered the error message:
File ended while scanning use of \__iow_wrap_end_chunk:w

Here are the two minimal examples
\documentclass{standalone}
\usepackage{xeCJK}
\setCJKfamilyfont{wb}{FZWeiBei-S03}
\begin{document}
English
\end{document}

The error message is:
Runaway argument?
76543210\q_stop newline - 'small caps'  (m/sc) with NFSS spec.: ^^I^^O\ETC.
! File ended while scanning use of \__iow_wrap_end_chunk:w.
<inserted text>

The another example:
\documentclass{standalone}
\usepackage{xeCJK}
\setCJKmonofont[ItalicFont=KaiTi]{FangSong}
\begin{document}
English
\end{document}

Runaway argument?
76543210\q_stop newline  ^^I^^O^^W^^_^^W^^R^^A^^Pnewline  This font f\ETC.
! File ended while scanning use of \__iow_wrap_end_chunk:w.
<inserted text>

Although they may be related with xeCJK package, I reported here since they occurred after updating l3kernel. And I searching google, the only page that contains  \__iow_wrap_end_chunk:w points me to this project.

Closing comment (2018-10-20T12:30:04Z): Duplicate of #491.
Repository: launchbadge/sqlx

Issue #2099: sqlite driver returns result before the actual commit 
Created: 2022-09-18T21:51:51Z
Bug Description
The result of INSERT INTO query is returned before it's actually in the DB.
Lower is attached a snipped of client code. Those 2 queries are 2 different Actix endpoints.
Minimal Reproduction
sqlx::query!("INSERT INTO some_table (id, name) VALUES ($1, $2) RETURNING id", id, name).fetch_one(db_pool.get_ref()).await?.id; // => 1
sqlx::query_as!(SomeStruct, "SELECT id, name FROM some_table WHERE id = $1", id).fetch_one(db_pool.get_ref()).await?; // => sqlx::Error no row found
const result = await api({
      url: `group`,
      method: 'POST',
      data: {
        name,
      },
    });

    if (result.status === 200) {
      await getEntity(result.id);
    }
Info

SQLx version: 0.6.2
SQLx features enabled: ["runtime-actix-rustls", "sqlite", "migrate", "macros", "chrono"]
Database server and version: SQLite 3.31.1
Operating system: Ubuntu 20.04 LTS
rustc --version: rustc 1.62.1 (e092d0b6b 2022-07-16)

Duplicate issue #2893: [SQLite] Pool drop may be too fast ?
Created: 2023-11-21T21:17:18Z
Bug Description
Insertion in an SQLite DB only works if I explicitly slow the program.
Minimal Reproduction
I've this very basic code:
    async fn create(&mut self, site: Site) -> Result<Site> {
        let id = site.id().to_string();

        let site = query_as!(
            Table,
            r#"
            INSERT INTO sites (id, title, description)
            VALUES ($1, $2, $3)
            RETURNING id, title, description
            "#,
            id,
            site.title,
            site.description
        )
        .fetch_one(&self.0)
        .await?;

        Ok(site.into())
    }
The DB does not contain any data after going through this code.
BUT. If I add std::thread::sleep(std::time::Duration::from_millis(1)); right after (in debug. release needs 2ms), the DB now has the data written in it.
Info

SQLx version & features: sqlx = { version = "0.7.2", features = ["sqlite", "runtime-tokio"] }
Database server and version: SQLIte 3.39.5
Operating system: MacOS and Linux
rustc --version: rustc 1.73.0

Closing comment (2023-11-21T21:38:47Z): Looks like a duplicate of #2099
Repository: launchbadge/sqlx

Issue #3820: Breaking change added in minor release
Created: 2025-04-14T05:27:26Z
I have found these related issues/pull requests
none that I could find
Description
After the release of sqlx 0.8.4 sea orm (and probably others) broke do to a breaking change being added to a minor semver release. TransactionManager::begin has a new parameter added to it so when cargo automatically bumps the version of sqlx used it breaks.
Reproduction steps
use anything that does not have a specific version of sqlx pinned.
SQLx version
0.8.4
Enabled SQLx features
sqlx-postgres, runtime-tokio-native-tls
Database server and version
Postgres
Operating system
Linux
Rust version
1.86.0

Duplicate issue #3822: Semver breaking change released in patch version bump
Created: 2025-04-14T07:15:37Z
I have found these related issues/pull requests
Searching for "semver" or "breaking" or "0.8.4" does not return any relevant issues
Description
It appears that a semver breaking change made it into a patch version bump (0.8.3 -> 0.8.4). TransactionManager::begin took one parameter in 0.8.3 and now it takes two in 0.8.4. This is breaking, for example, SeaORM (related issue).
error[E0061]: this function takes 2 arguments but 1 argument was supplied
  --> /Users/spencer/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/sea-orm-1.1.9/src/database/transaction.rs:57:17
   |
57 |                 <sqlx::Postgres as sqlx::Database>::TransactionManager::begin(c)
   |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^--- argument #2 of type `std::option::Option<Cow<'static, str>>` is missing
   |
note: associated function defined here
  --> /Users/spencer/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/sqlx-core-0.8.4/src/transaction.rs:25:8
   |
25 |     fn begin<'conn>(
   |        ^^^^^
help: provide the argument
   |
57 -                 <sqlx::Postgres as sqlx::Database>::TransactionManager::begin(c)
57 +                 <sqlx::Postgres as sqlx::Database>::TransactionManager::begin(c, /* std::option::Option<Cow<'static, str>> */)

For more information about this error, try `rustc --explain E0061`.
error: could not compile `sea-orm` (lib) due to 1 previous error

I see this trait is only intended to be used if implementing Connection, so maybe there's some context between sqlx and sea-orm that I'm not aware of where this is an expected consequence of using a hidden trait. IMO since this is a public trait the change should have been in an appropriate version bump (0.9.* in this case), but if there's a different policy you follow for hidden traits that I'm not aware of then feel free to close. However, from my perspective this seems like it was simply released as a patch version by mistake.
Reproduction steps
Build the latest SeaORM (currently 1.1.8)
SQLx version
0.8.4
Enabled SQLx features
postgres
Database server and version
Postgres 15.3
Operating system
Mac
Rust version
rustc 1.86.0 (05f9846f8 2025-03-31)

Closing comment (2025-04-14T07:18:34Z): Duplicate of #3820
Repository: launchbadge/sqlx

Issue #166: Support geometric types for postgres
Created: 2020-03-26T08:27:01Z
https://docs.rs/geo
https://www.postgresql.org/docs/current/datatype-geometric.html

POINT -> geo::Coordinate<f64>
LINE -> geo::Line<f64>
LSEG -> geo::Line<f64>
BOX -> geo::Rect<f64>
PATH -> geo::LineString<f64>
POLYGON -> geo::Polygon<f64>

Duplicate issue #709: Unsupported Type Geometry
Created: 2020-09-26T02:38:13Z
I was hoping to use this database adapter instead of https://github.com/sfackler/rust-postgres + https://github.com/andelf/rust-postgis for the compile time SQL string checking, however it seems the geometry type is unsupported.
error: unsupported type geometry of column #2 ("origin")

Are these extensions to be implemented inside this crate? Or is there a built in way to extend sqlx that I'm not aware of?

Closing comment (2020-10-17T00:32:59Z): Duplicate of #166
Repository: launchbadge/sqlx

Issue #1440: [offline] Strip whitespace before hashing keys for sqlx-data.json
Created: 2021-09-16T01:47:08Z
sqlx offline mode hashes the query SQL text in order to build keys for sqlx-data.json. I'm using raw multi-line string literals to help with readability:
sqlx::query!(r#"
  SELECT …
"#, foo);
As a result, even a simple cargo run fmt can change the indent of the closing tag and add trailing whitespace, resulting in a different hash, resulting in a cache miss and having to rebuild the file (prepare).
I would suggest applying a .strip() on the query string before hashing. This would not introduce any non-determinism: no SQL dialect will have a behavioral difference caused by leading or trailing whitespace, aka. SELECT 1 and \n\n    SELECT 1\n\t  \t\n are identical.

Note: this won't solve the issue of eg. indenting the whole block of SQL, but I don't want to suggest dealing with this, because that'd risk affecting the SQL body. To be safe this would require being able to parse SQL, which is a non-goal of sqlx.

Duplicate issue #2410: `query!`'s check fails due to indentation changes
Created: 2023-03-17T14:56:47Z
Bug Description
Changing indentation of the string literal in query! macro makes for a compile error.
Minimal Reproduction
This is not minimal, I can add more information later if necessary.
This compiles for me:
use chrono::NaiveDateTime;

fn main() {
    let _ = sqlx::query!(
        "INSERT INTO client_errors
                    (time_monotonic_client, timestamp_server, session, error)
                    VALUES ($1, $2, $3, $4)
                ",
        0_i64,
        NaiveDateTime::MAX,
        0_i32,
        Some("example".to_string()),
    );
}
But if I add OR remove a single leading whitespace from one of the last three lines of this string:
        "INSERT INTO client_errors
                    (time_monotonic_client, timestamp_server, session, error)
                    VALUES ($1, $2, $3, $4)
                ",
Like this:
        "INSERT INTO client_errors
                    (time_monotonic_client, timestamp_server, session, error)
                     VALUES ($1, $2, $3, $4)
                ",
I get this error:
error: failed to find data for query INSERT INTO client_errors
                           (time_monotonic_client, timestamp_server, session, error)
                           VALUES ($1, $2, $3, $4)

Info

deps:

[dependencies]
sqlx = { version = "0.6.2", features = [
    "runtime-tokio-rustls",
    "postgres",
    "migrate",
    "offline",
    "chrono",
    "uuid",
] }
chrono = "0.4.19"

Database server and version: psql (PostgreSQL) 15.2
Operating system: Arch Linux
rustc --version: tested on stable 1.68.0 and 1.70.0-nightly

Closing comment (2023-03-20T22:44:54Z): Duplicate of #1440
Repository: launchbadge/sqlx

Issue #981: Compiler hangs when using SQLite, query_as! and GROUP BY
Created: 2021-01-13T17:51:38Z
On macOS.
$ sqlite3 --version
3.32.3 2020-06-18 14:16:19 

$ rustc --version
rustc 1.49.0 (e1884a8e3 2020-12-29)

Reproduction
# Create the db on the cli
sqlite3 parts.db "create table parts (Document TEXT)"
# .env
DATABASE_URL=sqlite:parts.db
# Cargo.toml
[dependencies]
sqlx = { version = "0.4", features = [ "sqlite", "runtime-async-std-rustls"  ] }
async-std = { version = "1.6", features = [ "attributes" ] }
// src/main.rs
use sqlx::sqlite::SqlitePool;
use std::env;

struct Document {
    name: Option<String>,
}

#[async_std::main]
async fn main() -> Result<(), sqlx::Error> {
    let connection_string = env::var("DATABASE_URL").unwrap();

    let db_pool = SqlitePool::connect(&connection_string).await.unwrap();

    let _result = sqlx::query_as!(
        Document,
        "
SELECT Document AS name
FROM parts
GROUP BY name
        ",
    )
    .fetch_all(&db_pool)
    .await;

    Ok(())
}
Try running.
$ cargo run
   Compiling sqlx-test v0.1.0 (/Users/me/Dev/Rust/sqlx-test)
   Building [=====================================================> ] 189/190: sqlx-test(bin)

# It gets stuck here and never finishes.
Observations
Removing the GROUP BY allows the program to compile.
Another observation is that this works
SELECT DISTINCT Document AS name
FROM parts
But then adding an ORDER BY causes the never ending compile again.
SELECT DISTINCT Document AS name
FROM parts
ORDER BY Document
When the compiler stalls, I am still able to interact with my sqlite3 db (make queries etc.).

Duplicate issue #1012: [SQLite] Multiplying 2 numbers without CAST inside GROUP BY results in over 220x slower compilation
Created: 2021-01-23T22:08:28Z
UPDATE: It was not the Blobs causing the issues - it was the lack of CAST and the GROUP BY
I mistakenly attempted to multiply two blobs in SQLite and the compilation times shot up from 0.36s to 1m20s (over 220x slower).
I'm not sure what expected behaviour for multiplying two blobs is - an error maybe - but these compile times are quite bizarre.
My Code
        let total = sqlx::query!(
            r#"
                SELECT
                    SUM(parts.quantity * packages.quantity) AS total
                FROM parts
                INNER JOIN packages ON parts.package_id = packages.id
                WHERE parts.id = ?
                GROUP BY parts.id
            "#,
            part_id,
        )
Output without the blob multiplication (above commented out)
Finished dev [unoptimized + debuginfo] target(s) in 0.36s
Output with the blob multiplication
Finished dev [unoptimized + debuginfo] target(s) in 1m 20s

Closing comment (2021-01-24T00:26:50Z): Possibly a duplicate of #981 ?
Repository: launchbadge/sqlx

Issue #481: Isolation level support
Created: 2020-07-05T17:16:05Z
There are four transaction isolation levels in SQL language and most of database support them.  But I can't find how to set isolation level for transactions in sqlx.
Is it a missing feature?

Duplicate issue #1182: SQLite: Missing IMMEDIATE and EXCLUSIVE Transaction Functionality
Created: 2021-04-19T21:41:43Z
It does not appear that there is a way to start an IMMEDIATE or EXCLUSIVE transaction for a SQLite database. All Transactions are started using BEGIN, but SQLite supports BEGIN IMMEDIATE and BEGIN EXCLUSIVE. The former is of some import for simplifying some code I'm writing.  It would allow me to catch SQLITE_BUSY and retry at the start of the transaction rather than having to catch it at any point throughout a sequence of queries and add complex replay logic.
I took a look at the codebase, but didn't see an easy way to add the functionality since Transaction is generic over databases and this would be a SQLite specific feature.  Perhaps begin could have some kind of TransactionOptions parameter added that could toggle database specific features?  To reduce API breakage a begin_with_options API could be added.
Thank you.

Closing comment (2021-04-26T07:34:31Z): Duplicate of #481
Repository: launchbadge/sqlx

Issue #199: [Proposal] Support named bind parameters
Created: 2020-03-30T08:35:56Z
struct Query {
  fn bind_as<T>(name: &'static str, value: T) -> Self;
}
query!("SELECT ?name", name = 320);

Duplicate issue #590: Named bindings
Created: 2020-07-29T22:54:36Z
As discussed on Discord, it would be nice if SQLx supported (for compatible databases)
query!(
    "INSERT INTO foo (a, b, c) VALUES (:a, :b, :c)"
    a=value_for_a,
    b=value_for_b,
    c=value_for_c,
)

Closing comment (2020-07-29T22:55:44Z): Duplicate of #199
Repository: ldc-developers/ldc

Issue #1883: Integrate CI builds with dlang/install.sh
Created: 2016-11-14T10:47:24Z
It'd be very nice to have something similar to the Windows master packages, but then also for Linux / Mac.
We could try to get the builds hosted here: https://nightlies.dlang.org/
(@MartinNowak)
Or we could publish them on Github like is done already for the Windows master packages.
Thanks!

Duplicate issue #2123: Provide nightly builds
Created: 2017-05-20T15:48:03Z
Hi there,
I am currently going through the repos of dlang-community and enabling dmd-nightly in the Travis CI config combined with daily cron jobs at Travis, e.g.

https://docs.travis-ci.com/user/cron-jobs/
https://blog.travis-ci.com/2016-12-06-the-crons-are-here

Hence, I was wondering whether you have any plans to provide nightly builds of the latest, greatest LDC release? Imho the D community would be happy to enable & test them.

Closing comment (2017-05-22T19:02:50Z): Duplicate of #1883.
Repository: ldc-developers/ldc

Issue #3472: ldc2-1.22.0-windows-multilib.7z: Trojan detection for libcurl.dll
Created: 2020-06-17T04:25:18Z
This is to make you aware McAfee Endpoint Security reports in archive ldc2-1.22.0-windows-multilib.7z a trojan RDN/Generic.dx in lib/libcurl.dll and lib64/libcurl.dll.

Duplicate issue #3563: Blocked on Anti-virus solutions. (Windows-x64, LDC2-1.23.0)
Created: 2020-09-19T08:08:02Z
Hi. Title is description.

Target: ldc2-1.23.0-windows-x64.7z, bin/libcurl.dll
VirusTotal : 23 engines detected 

I don't know why. Maybe misdiagnosis or not?

Closing comment (2020-09-20T21:09:12Z): Duplicate of #3472.
Repository: ldc-developers/ldc

Issue #1700: Pass through linker flags to GCC
Created: 2016-08-17T05:12:39Z
Hi!
Many (if not all) libraries on Linux systems ship with pkg-config1 files, which makes it easy for projects to find the libraries and apply the necessary compiler flags and additional libraries to link against it.
Those compiler flags / libs may include -pthread to enable threading support with the pthreads library. A lot of libraries set this flag, including the very important GLib library.
Of course, LDC has no idea what the -pthread flag is supposed to be and errors out, making it impossible to link against these libraries.
It would be awesome if LDC could simply recognize this flag, or just ignore it in case someone passes it, instead of throwing an error.
Changing all the Cflags/Libs entries in pkg-config files will not be possible (may break things, even if I would trick upstream into making the change), and filtering the flags out (which I suppose is what dub does) is only a workaround and only works if the buildsystem supports it.
Having LDC deal with this directly is IMHO the best and easiest option.

Duplicate issue #1729: 'brew install ldc' fails on linux
Created: 2016-08-31T21:01:22Z
bringing this issue to your attention, it'd make ldc much more accessible on linux if this were fixed:
https://github.com/Linuxbrew/homebrew-core/pull/509

Closing comment (2016-08-31T22:14:43Z): So is this a duplicate of #1700?
Repository: ldc-developers/ldc

Issue #3675: lld-link: error: failed to write the output file: permission denied
Created: 2021-02-22T12:43:11Z
When compiling a (simple) D program, LDC 1.25.0 show:
lld-link: error: failed to write the output file: permission denied
And no executable generated but xxx.exe.xxxxxxx. In 1.24.0, no such error.
The OS is Win7 x64, FS is NTFS.

Duplicate issue #3676: lld-link: error: failed to write the output file: permission denied
Created: 2021-02-22T12:49:32Z
When compiling (simple) D program, LDC 1.25.0 show:
lld-link: error: failed to write the output file: permission denied
And no executable generated but xxx.obj. In 1.24.0, no such error.
The OS js Win7 x64, FS is NTFS.

Closing comment (2021-02-22T15:24:00Z): Duplicate of #3675.
Repository: ldc-developers/ldc

Issue #4246: Invalid bitcast for alias this
Created: 2022-11-07T18:09:22Z
ldc2-1.30.0-beta1-windows-multilib
Invalid bitcast
  %16 = bitcast %"sidero.base.errors.result.Result!float.Result"* %15 to float, !dbg !145192
in function �_D6sidero4base4math14linear_algebra6vector__T6VectorTfVmi3ZQo10dotProductMFNbNiNfxSQDdQCzQCxQCvQCi__TQCeTfVmi3ZQCoZf
LLVM ERROR: Broken function found, compilation aborted!

Broken:
struct Vector(Type, size_t Dimension) {
    Type[Dimension] data;
    Type dotProduct(const scope Vector other) scope {
        auto got = .dotProduct(this.data[], other.data[]);
        assert(got);
        return got;
    }
}
Working:
    Type dotProduct(const scope Vector other) scope {
        auto got = .dotProduct(this.data[], other.data[]);
        assert(got);
        return got.get;
    }
It appears the alias this to get inside Result is generating bad IR in dotProduct.

Duplicate issue #4882: Codegen error
Created: 2025-03-17T14:45:34Z
LDC doesn't like this:
struct S
{
nothrow @nogc:

    alias toString this;

    const(char)* ptr;

    // comment this and the error goes away
    this(ref inout typeof(this) rhs) inout pure {}

    const(char)[] toString() const pure
        => ptr[0 .. ptr[-1]];
}

class Test
{
    S s;
    const(char)[] test()
    {
        return s;              // ERROR: this causes the error (result should coerce via alias-this)
//        return s.toString(); // WORKS: explicit call makes the error go away
    }
}
1>Function return type does not match operand type of return inst!
1>  ret ptr %3, !dbg !20962
1>COMPILED : { i64, ptr }LLVM error : Broken module found, compilation aborted!
1>Exception Code: 0xC000001D

Remove the copy constructor and this error goes away.
Alternatively, call toString explicitly rather than falling to alias-this also makes it go away.

Closing comment (2025-03-17T15:54:09Z): Oh, this is most likely a duplicate of #4246.
Repository: ldc-developers/ldc

Issue #950: DMD asm: Cannot access struct members
Created: 2015-05-30T23:27:52Z
The following code compiles with DMD but not with LDC:
module app.d;

import std.stdio;

struct test {
        uint a = 42;
        uint b = 7;

        uint getA() {
                uint temp;
                asm {
                        mov RBX, this;
                        mov EAX, a[RBX];
                        mov temp, EAX;
                }
                return temp;
        }
}

public static void main() {
        writeln("asm 'this' test");
        test t;
        writeln("test.getA(): ", t.getA());
        assert(t.getA() == t.a, "getA() failed");
}

Reported by this.getName() in ldc forum.

Duplicate issue #2771: ASM compilation failure trying to assign to field - "end of instruction expected, not this"
Created: 2018-07-11T00:03:04Z
This code fails to compile with LDC v1.10.0. It compiles and prints sane output with DMD v2.060 through v2.080.0.
https://run.dlang.io/is/8HH3tV
void main()
{
    import core.stdc.stdio : printf;
    static struct TS
    {
        ulong state;
        void initialize()
        {
            version(D_InlineAsm_X86_64)
            {
                asm
                {
                    rdtsc;
                    // RAX: low 32 bits are low bits of timestamp, high 32 bits are 0.
                    // RDX: low 32 bits are high bits of timestamp, high 32 bits are 0.
                    shl RDX, 32;
                    xor RDX, RAX;
                    // Copy RDX to `this.state`.
                    mov RAX, this;
                    mov this.state.offsetof[RAX], RDX;
                }
            }
            else
            {
                static assert(0, "D_InlineAsm_X86_64 not supported");
            }
        }
    }
    TS s;
    s.initialize();
    printf("%ld\n", s.state);
}

Closing comment (2018-07-11T00:09:39Z): This seems to be a duplicate of #950. Closing.
Repository: leggett/simplify

Issue #253: Support "No Split" view for Preview Pane
Created: 2020-02-14T18:30:45Z
Ideally, this looks and works the same as Preview Pane being disabled. Do this because some people don't want to use Preview Pane, would like to disable it, but can't because they have the setting forced to on by GSuite admin.

Duplicate issue #258: Preview Pane In Gmail causing issues with simplify?
Created: 2020-03-05T18:34:44Z
Good Day Michael.
We have chatted in the past re Simplify,but i completely forgot how we communicated? sorry.
I just wished to let you know that one gmail account (not my others) is conflicting with Gmail preview pane? I keep receiving a dialogue box,I took a screen snip and attach it here.I do not have split screen enabled and I have toggled on and off and unloaded simplify and reloaded but it as not helped and you can see the text at bottom as follows(am not sure if its clear on the screen snip)

0.16 GB (1%) of 15 GB used,Manage Terms · Privacy · Programme Policies Last account activity: 57 minutes ago

The snip is below..my email is amewi6x6@gmail.com
All the best Steve

Closing comment (2020-03-05T20:45:10Z): Thanks for the report and screenshot.
This is an unfortunate state that I learned some are in (they actually want to have preview pane on in advanced settings and toggle it on/off). I won't have a fix for that until I rebuild support for Preview Pane on (in settings) and off (set to No Split) and kill this warning.
That is being tracked in #253 so I'm closing this bug. Let me know if you think it isn't covered there or I'm missing something.
Repository: leggett/simplify

Issue #131: Search can't be focused on click
Created: 2019-05-01T07:08:56Z
You can see in this image that the search field is auto expanded but not focused. I can not it, except by using the / keyboard command. If invoke focus via the keyboard command and then esc out, goes back to looking like the screenshot.
I've checked to make sure I don't have any other browser extensions or Gmail add-ons that might be messing with this. I previously had Boomerang, but it is currently disabled.

Duplicate issue #132: Actions and settings overlap search bar
Created: 2019-05-01T07:18:53Z
Browser: Chrome 74.0 on macOS
As you can see, all the actions and settings overlap the search bar, which also disables the search bar. I've tried to turn off some extensions like Stylus, but it still doesn't work.

Closing comment (2019-05-01T12:01:10Z): This is related to #131
I noticed though that this is only happening in my personal Gmail account. My G-Suite account works fine.
Repository: leggett/simplify

Issue #41: Replace empty checkboxes with profile picture
Created: 2019-04-09T09:23:04Z
Is it technically possible to bring the profile icons (of senders) to the mail list instead of those pointless empty checkboxes - just like Inbox did?

Duplicate issue #254: Profile pics in the inbox list view
Created: 2020-02-19T00:02:18Z
[Feature request]
Ideally, this would be the icons as shown in the hover card, but failing that, some color based on a hash with the first letter shown in the middle of the circle.

I noticed that the email address and name itself is in the DOM:

, so it's do-able to at least get something, albeit, not as good as what was in Inbox. Ideally, they would appear where checkboxes are, and change to a checkbox on hover, (and when one is checked, they all become checkboxes) as they did in Inbox.
This would probably be a similar complexity to #56.

Closing comment (2021-03-17T03:43:45Z): Closing this as it is a dup of #41
I looked into this some for Simplify v2 but it didn't make it because (a) it is hard to do well and (b) I was surprised how many people do not have a profile photo. It is still on my list as a someday maybe.
Repository: leggett/simplify

Issue #167: Layout broken
Created: 2019-05-16T07:59:51Z
Starting of today, the layout seems to be broken, most probably related to changes Google made to the HTML or CSS:

It was working perfectly before and I did not install any new extensions.

Duplicate issue #169: Sidebar overlapping filter menu
Created: 2019-05-16T08:09:11Z
Here is a screenshot of the overlap
https://www.screencast.com/t/GCMAnOCXj1

Closing comment (2019-05-16T13:47:38Z): fix coming. duplicate of #167
Repository: leggett/simplify

Issue #167: Layout broken
Created: 2019-05-16T07:59:51Z
Starting of today, the layout seems to be broken, most probably related to changes Google made to the HTML or CSS:

It was working perfectly before and I did not install any new extensions.

Duplicate issue #172: email list overlapping  top bar
Created: 2019-05-16T12:53:10Z
The email list is now overlapping the top bar buttons and main menu button.

Closing comment (2019-05-16T13:47:18Z): fix coming. duplicate of #167
Repository: leggett/simplify

Issue #335: Popped-out reply message still crosses with the email content
Created: 2020-09-01T15:53:09Z
I'm using Simplify v2 on a 13' MacBook on its native non-scaled resolution. When I pop out the reply it still crosses with the text. The preferred behavior for me would be to still make both columns more narrow but separate them clearly.
I don't think it'd be too narrow because Superhuman looked OK when doing the same.

Duplicate issue #548: Change message width when compose mole is open
Created: 2021-03-02T18:03:09Z
Now that I support wider message views, should I make the message less wide when you open a compose mole so they don't overlap? I could go further on smaller screens and make sure they don't overlap at all.

Closing comment (2021-03-16T18:34:03Z): Duplicate of #335