Update backup-and-restore.md

Modify the links which are related to delete user defined restore point based on the SQL Pool type

@realAngryAnalytics
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Court72, This looks good! It can be published.


Add BlockReadFunction and BlockWriteFunction

It seems in base-jdbc, we're missing the Read/WriteFunction mappings for one javaType - the Block type.  This would be useful for things like implementing ARRAY support (#317).
One thing I'm not sure about here is in JdbcRecordCursor - there is only a getObject() function.  Can we assume getObject() will only be called for Block types, and hence add a call to blockReadFunctions there?  Or do we need to add a getBlock (but that would be a change to RecordCursor)?

@findepi Thanks, pushed new commit with your suggested changes.  Do you know the answer to this question:

One thing I'm not sure about here is in JdbcRecordCursor - there is only a getObject() function. Can we assume getObject() will only be called for Block types, and hence add a call to blockReadFunctions there? Or do we need to add a getBlock (but that would be a change to RecordCursor)?

@findepi Thanks, pushed new commit with your suggested changes. Do you know the answer to this question:

One thing I'm not sure about here is in JdbcRecordCursor - there is only a getObject() function. Can we assume getObject() will only be called for Block types, and hence add a call to blockReadFunctions there? Or do we need to add a getBlock (but that would be a change to RecordCursor)?

@vincentpoon i missed that, thanks.
Yes, assume getObject() is for Block type. This will be called from io.prestosql.spi.connector.RecordPageSource#getNextPage when type.getJavaType() is none of boolean, long, double, Slice and the io.prestosql.spi.type.Type#getJavaType says Block is the only other option possible.

In theory, getObject() could be called for other types, but that required require a Type that has a JavaType other than Block (or primitive/Slice) which is not supported today, nor would it be a problem since the JDBC connector wouldn't support that Presto Type.

@findepi @electrum Thanks for the clarification.  Pushed a commit which calls blockReadFunctions from getObject()

@vincentpoon thanks. Could you please squash the commits now?

done

Merged, thanks!


[7.x] Add boolean to types that don't need character options

I was glad to see #30539 got fixed by fccdf7c, but after I updated Laravel to 7.10.3 my issue was still present. I was changing a varchar to a boolean and that one is missing from the list of types that don't need character options. This PR adds it to that list!

Probably needs to go to 6.x?

@driesvints good point, updated!


Run the tests for the specified time

I think it would be great to have an option to define how many time we want to run the tests from the web interface.

Fixed by #656!


Make the threshold whether assets should be inlined configurable for prod builds

For sites which have a large number of images, each of which has a lower probability of being seen,
combined with assets which rarely change, the other situation was inconvenient. Users were forced
to download the same assets over and over again for unrelated changes.
Apart from that, since each image has a low probability of being loaded, aggressively loading all
images is counterproductive.
By making the threshold configurable, but respecting the same default value, developers can use
techniques as lazyloading images when applicable (which cannot be done if they are part of the bundle)
Refs https://github.com/facebookincubator/create-react-app/issues/3437

Where do I add this env variable so I can remove this base64 inline completely?
It breaks any images being imported from node_modules

You can set inlineLimit in your package.json file

@Timer as you commented in #3437, what is your view towards this change?

I think we need to start considering a 'CSP' mode that disables a couple things: no inline runtime script, no inline assets, etc. I'm not sure we want to keep adding these one-off options to toggle behavior.

I'd love to work on that.
Combined with https://github.com/facebook/create-react-app/pull/5354 we can start out with a no-inline version. Would you also want to include the CSP calculations in here?

I don't know if we can ever get to performing the CSP calculations for people, but we can try to get close.
Let's consolidate the runtime chunk feature & disabling asset inlining under a single flag and start the discussion there. Send a PR?

would really like this feature, having to eject to prevent a massive bundle is a bummer

Here's an alternative solution: https://github.com/facebook/create-react-app/pull/6060
Same idea but instead of controlling it via a variable in package.json it's an environment variable instead.
Why env var instead of a variable in package.json? Not sure but considering that's how you control whether JS inlining should happen or not (INLINE_RUNTIME_CHUNK) I thought that was the norm.


Provision a computer for driver deployment problem

Using the Driver extension for VS 2019 after installing the Windows Driver SDK I use the configure devices tool. Add New Device -> enter a valid network host name and hit Next.
The deployment fails with this error from the log:

Progress event: Current: 13, Max: 15, Message: "Configuring kernel debugger settings (possible reboot)"
[14:10:57:864]: Configuring kernel debugger settings (possible reboot)
[14:10:57:864]: Removing any existing files from test execution folder.
[14:10:57:864]: Copying required files for "Configuring kernel debugger settings (possible reboot)".
[14:10:58:125]: An error occured while deploying files to the target machine for test "Configuring kernel debugger settings (possible reboot)": Could not find a part of the path 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Redist\MSVC\14.23.27820\debug_nonredist\X64\Microsoft.VC141.DebugCRT'..
Task result status updated: Fail
[14:10:58:125]: ERROR: Task "Configuring kernel debugger settings (possible reboot)" failed to complete successfully. Look at the logs in the driver test group explorer for more details on the failure.
Progress event: Current: 13, Max: 15, Message: "    ERROR: Task "Configuring kernel debugger settings (possible reboot)" failed to complete successfully. Look at the logs in the driver test group explorer for more details on the failure."
Result completed
Test process exit code: 0

I believe the path it should be looking for is 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Redist\MSVC\14.23.27820\debug_nonredist\X64\Microsoft.VC142.DebugCRT'
That is Microsoft.VC142.DebugCRT instead of Microsoft.VC141.DebugCRT. But I am not sure.

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

ID: ce050ea3-d61e-830c-3038-f725eb4c29e1
Version Independent ID: eb7fc65e-bcfe-dc86-3f8c-336d20eb0c86
Content: Provision a computer for driver deployment and testing (WDK 10) - Windows drivers
Content Source: windows-driver-docs-pr/gettingstarted/provision-a-target-computer-wdk-8-1.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @EliotSeattle
Microsoft Alias: eliotgra

Thanks you, @w103csh We'll look into this. Since this isn't a documentation bug, we'll see if we can't get this in the right hands.
@DOMARS
Can you please take a quick look at this and determine if this should be routed to the windbg team?
Thanks,
Eliot

Looks like a known bug. The directory junction solution posted at https://developercommunity.visualstudio.com/content/problem/596096/visual-studio-2019-wdk10.html works for me.
Perhaps add one of those nifty green boxes to mention this potential blocker?

Here is a simple solution which worked for me (x64):

navigate to "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Redist\MSVC\14.24.28127\debug_nonredist\x64"
copy and paste the VC142 folders here e.g. "Microsoft.VC142.DebugCRT"
rename the copied folder names to VC141 e.g. "Microsoft.VC141.DebugCRT"
build -> deploy -> no more errors

@ycelik - A similar work around is also described on the top level notes on the WDK forum page.
I repaired the link by adding en-us, so that it takes you to the WDK forum page.  Look for "Hardware development kits for Windows 10, Version 1903" and then "Error seen when Provisioning a computer for driver deployment and testing when using WDK 1903 and Visual Studio 16.1 +"


Types support

In this PR:

Included types support;

I am not familiar with TS, so the best I can do is assume that this works.
Since you're not making any changes to the src directory I'm going to go ahead and approve this PR.
That said, please keep in mind that if there's a future update the types will not be updated by myself.

published in 3.1.0

@cklmercer thank you.
About maintain types updated, I am watching this repo so if you change anything that affect types I can keep it updated.


fix(go/adbc/driver/snowflake): handle quotes properly

fixes #1721

I'm fixing CI so we can provide a wheel for testing.

I'm not sure this is the way to go. One, we're basically opening things up to SQL injection attacks if we don't escape/quote input. Two, it breaks the idea that what you pass in is the actual table name, not the concrete syntax.

@lidavidm Ultimately this comes down to the question of who is responsible for ensuring we avoid sql injection vs ease of use.
Because we provide this whole bulk ingestion API via options to define the table name etc, is ADBC itself (and therefore every driver) responsible for ensuring there's no sql injection? Or is the application that is using ADBC responsible for ensuring there's no injection in the value they pass for the option of the table name? Since ADBC itself allows arbitrary SQL strings it feels like it should be the application's responsibility for ensuring there's no sql injection rather than ADBC (and therefore every driver).
There's also the case that blindly adding quotes like we were doing isn't sufficient to prevent sql injection anyways and only served to create failure cases for the ingestion rather than potentially reasonable results (see here).
One possible solution could be for us to try to use the snowflake IDENTIFIER function https://docs.snowflake.com/en/sql-reference/identifier-literal which might solve the issue while preventing injection? it's still not perfect though unless we also check for un-escaped single quotes in the passed in string and forcibly escape them etc.

I feel like the injection thing is a red herring. Mainly, I think this depends on whether or not the API in question is defined as accepting a table name or a table identifier. If the former, then I would expect it to take the desired table name and do whatever is necessary to ensure a table with that name is created, including quoting if necessary. If the latter, then I would expect the identifier to already be quoted properly by the user of the API.
This distinction matters, because if the API allows me to create a table for a non-default schema (or in another database) then I have to be able to supply an identifier. If the separator is the canonical period, then I can't supply a table name containing a period without quoting it myself because anything else would be ambiguous.

if the API allows me to create a table for a non-default schema (or in another database) then I have to be able to supply an identifier

There are separate parameters for schema/catalog, so we're already down the path of name, not syntactical identifier

This is the sqlglot reference.. There is a default dialect and 20 other flavors including snowflake, postgres, etc..
https://github.com/tobymao/sqlglot/blob/main/sqlglot/dialects/dialect.py
def normalize_identifier(self, expression: E) -> E:
"""
Transforms an identifier in a way that resembles how it'd be resolved by this dialect.
    For example, an identifier like `FoO` would be resolved as `foo` in Postgres, because it
    lowercases all unquoted identifiers. On the other hand, Snowflake uppercases them, so
    it would resolve it as `FOO`. If it was quoted, it'd need to be treated as case-sensitive,
    and so any normalization would be prohibited in order to avoid "breaking" the identifier.

    There are also dialects like Spark, which are case-insensitive even when quotes are
    present, and dialects like MySQL, whose resolution rules match those employed by the
    underlying operating system, for example they may always be case-sensitive in Linux.

    Finally, the normalization behavior of some engines can even be controlled through flags,
    like in Redshift's case, where users can explicitly set enable_case_sensitive_identifier.

    SQLGlot aims to understand and handle all of these different behaviors gracefully, so
    that it can analyze queries in the optimizer and successfully capture their semantics.
    """

After talking with @lidavidm and based on the responses from everyone here, I'm gonna update this PR to have the following behavior:

We will still wrap ingesting table names in quotes, following the example of JDBC
I'll fix the behavior so it will properly escape quotes for Snowflake's dialect. We'll first do a pass and replace " with "" before wrapping the input with quotes, this should prevent things from erroring like in the examples in the linked issue.

If an option is desired to allow turning off this auto-quoting to allow a user to provide a literal, we can add that in a follow-up PR.
Does this work for everyone?

@davlee1972 we're not aiming to be a SQL dialect with ADBC, so I don't think that sqlglot is a good comparison here. we're more similar to ODBC and JDBC, which have behavior as quoted by @lidavidm's comments.

I'm not asking you to be a SQL dialect, but you might want to incorporate the dialects into the CI builds so they find the right table name..
Here's some samples..
from sqlglot import exp
from sqlglot.optimizer import optimize

table_names = {
    'lower_case | unquoted': exp.table_("dummy", quoted=False),
    'lower_case | quoted': exp.table_("dummy", quoted=True),
    'upper_case | unquoted': exp.table_("DUMMY", quoted=False),
    'upper_case | quoted': exp.table_("DUMMY", quoted=True),
    'mixed_case | unquoted': exp.table_("duMMy", quoted=False),
    'mixed_case | quoted': exp.table_("duMMy", quoted=True)
}

dialects = ['snowflake', 'postgres', 'mysql', 'tsql', 'oracle']

for dialect in dialects:
    for k, v in table_names.items():
        print("dialect: " + dialect + ", case + quoted: " + k)
        print("in: " + str(v.this))
        print("out: " + optimize(v, dialect=dialect).sql())
        print("")

Dialect results..
dialect: snowflake, case + quoted: lower_case | unquoted
in: dummy
out: "DUMMY"

dialect: snowflake, case + quoted: lower_case | quoted
in: "dummy"
out: "dummy"

dialect: snowflake, case + quoted: upper_case | unquoted
in: DUMMY
out: "DUMMY"

dialect: snowflake, case + quoted: upper_case | quoted
in: "DUMMY"
out: "DUMMY"

dialect: snowflake, case + quoted: mixed_case | unquoted
in: duMMy
out: "DUMMY"

dialect: snowflake, case + quoted: mixed_case | quoted
in: "duMMy"
out: "duMMy"

dialect: postgres, case + quoted: lower_case | unquoted
in: dummy
out: "dummy"

dialect: postgres, case + quoted: lower_case | quoted
in: "dummy"
out: "dummy"

dialect: postgres, case + quoted: upper_case | unquoted
in: DUMMY
out: "dummy"

dialect: postgres, case + quoted: upper_case | quoted
in: "DUMMY"
out: "DUMMY"

dialect: postgres, case + quoted: mixed_case | unquoted
in: duMMy
out: "dummy"

dialect: postgres, case + quoted: mixed_case | quoted
in: "duMMy"
out: "duMMy"

dialect: mysql, case + quoted: lower_case | unquoted
in: dummy
out: "dummy"

dialect: mysql, case + quoted: lower_case | quoted
in: "dummy"
out: "dummy"

dialect: mysql, case + quoted: upper_case | unquoted
in: DUMMY
out: "DUMMY"

dialect: mysql, case + quoted: upper_case | quoted
in: "DUMMY"
out: "DUMMY"

dialect: mysql, case + quoted: mixed_case | unquoted
in: duMMy
out: "duMMy"

dialect: mysql, case + quoted: mixed_case | quoted
in: "duMMy"
out: "duMMy"

dialect: tsql, case + quoted: lower_case | unquoted
in: dummy
out: "dummy"

dialect: tsql, case + quoted: lower_case | quoted
in: "dummy"
out: "dummy"

dialect: tsql, case + quoted: upper_case | unquoted
in: DUMMY
out: "dummy"

dialect: tsql, case + quoted: upper_case | quoted
in: "DUMMY"
out: "dummy"

dialect: tsql, case + quoted: mixed_case | unquoted
in: duMMy
out: "dummy"

dialect: tsql, case + quoted: mixed_case | quoted
in: "duMMy"
out: "dummy"

dialect: oracle, case + quoted: lower_case | unquoted
in: dummy
out: "DUMMY"

dialect: oracle, case + quoted: lower_case | quoted
in: "dummy"
out: "dummy"

dialect: oracle, case + quoted: upper_case | unquoted
in: DUMMY
out: "DUMMY"

dialect: oracle, case + quoted: upper_case | quoted
in: "DUMMY"
out: "DUMMY"

dialect: oracle, case + quoted: mixed_case | unquoted
in: duMMy
out: "DUMMY"

dialect: oracle, case + quoted: mixed_case | quoted
in: "duMMy"
out: "duMMy"

We expect a catalog, schema, and table name, and as others have chimed in above this is typical of database APIs. If Snowflake's quoting rules mean that the SQL identifier dummy results in the name DUMMY, then we expect the latter.
It happened to work before because we were just concatenating SQL strings internally, but this does not work for all drivers and all users - for instance, Flight SQL now has an ingestion API that works on names and not SQL identifiers. And, not all users are using sqlglot to escape names for them, nor would we expect or require them to do so; hence why these APIs all work on names. I'd be supportive of a Snowflake driver-specific option to disable this at the user's own risk, but for the purposes of this PR let's fix the quoting first.

I filed #1766 for an option to disable the quoting behavior

Can we change 1766 from disable quoting to something like allow identifiers.. This would cover both quoting and case sensitivity

@davlee1972 do you mean just changing what it is called? Or are you saying that it should functionally do more than just disable the quoting?

Just the name..

Sure that makes perfect sense to me. I'd be fine with naming it as such.

Sorry for the back and forth.. I think it should called "quoted_identifier" = True by default..
This is a common term used across database products..
A quoted identifier begins and ends with double quotation marks (").

let's shift the discussion to #1766 so that we don't lose track of it


Migrator can add double null-checks when a parenthesized expression has a null-check hint

Currently the migrator will migrate this:
int/*!*/ f(int/*?*/ i) => (i)/*!*/;

to this:
int f(int? i) => i!!;

I think it wants to add a null-check for the hint, and one for the return type.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


Hook up GUI testing to generate and display coverage

Testing on the back-end is well developed.
However, testing of the UI is much less well developed.
Research needs to be done on how to properly test an AngularJS application
https://docs.angularjs.org/guide/unit-testing
Note that the current source does have some setup to use Karma, Jasmine.
However, it is not up to date with 0.4 (workflows, DAG, tools tab, etc.) and may or may not be broken.
Afterwards, hook up coverage information to coveralls.io so that we can track our progress.
https://coveralls.zendesk.com/hc/en-us/articles/201769715-Javascript-Node

Additional ideas:
https://github.com/angular/protractor
https://ghostinspector.com/

Great tutorial about setting up and using jasmine, karma, coveralls and travis: http://fatihacet.com/feci/
It also includes an explanation about using Istanbul, which is a code coverage tool, that can be used before Coveralls and travis

https://www.cypress.io/ This thing seems to be way easier to use and setup compare to protractor, seeing how we've had some problems with protractor, phantomjs and selenium when running the e2e tests.

Currently running and visible at https://github.com/ga4gh/dockstore-ui


Feature Request: Functions, passing variables, reference variables, inputs and constants

Is your feature request related to a problem? Please describe.
We can declare and call functions, pass variables and reference variables, take input from console, support constants
declare function: bhai apun ka naam TaklaFighter(supariAmount, &kitnaTimeLagega)
& for passing reference variables
bula for calling functions
Input variables have a ? in front of them and can be used to take input from console.
Keyword mangta for taking input
bhai yeh hai kitniSupari?
bhai kitniSupari mangta

bole to for constants
Describe the solution you'd like.
Example:
HaoNaBhai bole to sahi
NahiNaBhai bole to galat
PooraHafta bole to 100000

bhai apun ka naam MunnaCircuit(&haftaMilaKya, vasooli)
{
   haftaMilaKya = NahiNaBhai;
   agar bhai (vasooli == PooraHafta) {
       haftaMilaKya = HaoNaBhai;
   }
}

Calling function from main:
hi bhai
  bhai yeh hai haftaMilaKya?
  bhai yeh hai vasooli?
  bol bhai "kitni vasooli hui?"
  bhai vasooli mangta
  bhai bula MunnaCircuit(haftaMilaKya, vasooli)
  agar bhai (haftaMilaKya) {
    bol bhai "Jhakkaaas!!"
  }
  warna {
    bol bhai "Khallaaas!!"
  }
bye bhai

Describe alternatives you've considered
No response
Additional context.
No response

Duplicate of #154 and implemented in #220


Selectively load Sass

What
Only importing the Sass that is needed by the app.
I've gone through and checked each question, plus the error state, the ineligible pages, plus the privacy notice and all look identical to me.
Why
It'll reduce the amount of CSS users need to load, speeding up the service.
Before: 349.36KB of CSS
After: 116.87KB of CSS
With minification: 96.49KB of CSS
Visual differences
None.

Worth testing each page and double checking but on paper this is a great change.

Noticed two components required.
Would be good to get another person to visit every possible page in the journey and check nothing is missing before merging.

Noticed two components required.
Would be good to get another person to visit every possible page in the journey and check nothing is missing before merging.

I've added inset text - what was the other component?

Panel for the confirmation

@injms could you rebase your branch and double check all pages please :pray:

@injms could you rebase your branch and double check all pages please 🙏

rebased and checked x2, including the final page and the ineligible pages.


feat(sync): create state sync client

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2308  👈 (View in Graphite)
#2303
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


TS:1379 An import alias cannot reference a declaration that was exported using 'export type'

Bug Report

🔎 Search Terms
TS1379
An import alias cannot reference a declaration that was exported using 'export type'
🕗 Version & Regression Information
This has always been the behavior as far as I can tell
⏯ Playground Link
Multi file: repro but I will show in playground.
Below are pictures that might be easier to parse
💻 Code
When annotated with type it errors

When not annotated with type it doesn't error:

🙁 Actual behavior
Exports of types annotated with type error while those not annotated as types do not error even though TS understand it is still a type.
🙂 Expected behavior
Honestly I don't know which of these behaviors is correct - this behavior could be completely intentional as well - intuitively I think these should match and I prefer the behavior with no errors but it is unclear to me if this is an emit issue? I'm sorry if this behavior is on purpose and I have wasted your time. Really appreciate the work!

It should be like:
//exporter.ts

type foo = {
  thing: number
}

export type foo

This should work expectedly.

I'm not sure I understand what you mean?
export type foo = {thing: number}

works I agree.
//exporter.ts

type foo = {
  thing: number;
}

export type foo

is a syntax error no? I just don't understand the behavior. It's a very specific function in the checker
the error reporter:

the comment around the function that really does the check

I don't exactly understand why this is. If you don't have the time/think its to in the weeds to explain I totally understand! But I'm pretty curious as to why this is the behavior. I only encountered this corner because I wrote a little script to tag all of exports of types as typeOnly=true. (It's my understanding that this is good practice when ts_loader is set to transpileOnly)

Here might be the issues:

TypeScript version: It's worth noting that TypeScript evolves over time, and there may be differences in behavior between different versions. It's possible that the behavior you're observing is specific to the version you're using.

Configuration or compiler options: The behavior of TypeScript can also be influenced by various compiler options and configuration settings. It's worth double-checking your project's TypeScript configuration files (such as tsconfig.json) to see if any specific settings might be affecting this behavior.

Bug or regression: While you mentioned that this behavior has always been consistent, it's still possible that there is an underlying bug or regression in TypeScript that causes this inconsistency. In such cases, it might be helpful to consult the TypeScript documentation, release notes, or community forums to see if there are any known issues related to import aliases and export type.

You can put type in curly brackets, it sets the boolean isTypeOnly in ExportSpecifier in the AST, the behavior is the same if isTypeOnly is set in an ExportDeclaration. I can check every version of TS, I guess but this behavior is very specific to export declarations themselves (not statements branded with export) tied to import equals declarations - notably this is of course fine in non-importEqualsDeclarations import statements.

Yea so I tested back to 3.7.5 (going through the list playground versions locally) where it was a syntax error on my export type statement - This has always been the behavior.

Not sure how to help. Is AI service available in your current country?

What causes you to keep disliking my answers, @guillaumebrunerie?

@gooddavvy They look AI-generated and particularly unhelpful.

The behavior observed in TypeScript, where exports of type-annotated types result in errors while un-annotated ones do not, is unclear whether this is intentional or a bug/limitation. This behavior has been consistent across different versions of TypeScript, including up to version 3.7.5.

1 answer looks AI-generated. Just 1 @guillaumebrunerie


Hackage revisions are not handled

Describe the bug
A clear and concise description of what the bug is.
adding bzlib to a project with unbounded base dependencies results in:
Error: cabal: Could not resolve dependencies:
[__0] trying: foo-<IP_ADDRESS> (user goal)
[__1] trying: bzlib-<IP_ADDRESS> (dependency of foo)
[__2] next goal: base (dependency of foo)
[__2] rejecting: base-<IP_ADDRESS>/installed-<IP_ADDRESS> (conflict: bzlib =>
base>=4.3 && <4.16)
[__2] skipping: base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS> (has the same
characteristics that caused the previous version to fail: excluded by
constraint '>=4.3 && <4.16' from 'bzlib')
[__2] rejecting: base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>, base-<IP_ADDRESS>,
base-<IP_ADDRESS> (constraint from non-upgradeable package requires installed
instance)

However, the bounds for bzlib have been revised to support that base: https://hackage.haskell.org/package/bzlib-<IP_ADDRESS>/revisions/
To reproduce
Please provide an Short, Self Contained, Correct (Compilable), Example by creating a gist using devenv.nix, devenv.yaml, and optionally devenv.lock.
create a haskell + cabal project with bzlib as a dep.
Make sure to include full logs and what you expected to happen.
Version
Paste the output of $ devenv version here.
devenv: 0.6.3

You need to run cabal update?

Wait, really?!  If that's the case then this is obviously user error on my
part.  However, I expected cabal-install to be provided based on the
compiler version specified by devenv.
I'm not sure if this is a legitimate expectation, but coming from
haskell.nix that was the expectation I had.
On Fri, Sep 15, 2023 at 10:27 AM Domen Kožar @.***>
wrote:

You need to run cabal update?
—
Reply to this email directly, view it on GitHub
https://github.com/cachix/devenv/issues/818#issuecomment-1720965026, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5DC5LRC7G5ZDN4DOTBCCDX2QNRFANCNFSM6AAAAAA4ZKH5SA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
328 Plymouth St
Brooklyn, NY
11201
617 990 7876

This was indeed user error.


Search page tag cloud and format is broken

Describe the bug
On Search page, the Tag Cloud is broken and thus is not displayed. Also, in Search results table, Format column is displayed as empty
To Reproduce
Steps to reproduce the behavior:

Go to Search page while running Dockstore locally
See there is no "Tag cloud" button at top of results table
See there are no contents in "Format" column of results table
See error

Expected behavior
Clicking Tag Cloud button should expand and show correct tag cloud for the current tab (Tools or Workflows)
Format column should show correct format of each entry (WDL, CWL, etc) and should be sortable when you click on the header Format.
Screenshots

┆Issue is synchronized with this Jira Story
┆Issue Number: DOCK-1636
┆Sprint: Sprint 48- Walrus
┆Issue Type: Story

This is working in dev on
Webservice - 8d9d617
UI - 2.6.3-74-g092723ef
Compose Setup - a4858c6
Deploy - null


fix: use TLS or SSL depending on ES version

#180 In version 8 renamed the ssl option to tls.
This commit adjusts the code to reflect this change, ensuring compatibility with Elasticsearch 8.
Rename ssl option to tls
Link to documentation

I would update elasticsearch-js to last version, because last version supported Node.js 16 and more

@mcollina check PR

@mcollina and @jsumners Hi guys, how about this PR?
pino-elasticsearch v7.0.0 is broken, https connection doesn't work. After updating the package @elastic/elasticsearch to version 8.0.0, because in version 8 renamed the ssl option to tls - Rename ssl option to tls

Hi guys, how about this PR?

I would say that this PR should be backward compatible so that it is easier to merge and release. But I really don't have any strong opinion on the module in general. I was just pointing out that the current change will require publishing a major.

Hi guys, how about this PR?

I would say that this PR should be backward compatible so that it is easier to merge and release. But I really don't have any strong opinion on the module in general. I was just pointing out that the current change will require publishing a major.

I can update and use two params (ssl and tls)

I have no issue in shipping a major. This sits in the 300+ notification queue (currently on mobile).


Make mdx2json endpoint relative to dsw installation path

If not set in config file, make request relative to a dsw path

Fixed


Constructor in the SoapClientInterface

Hi,
Please remove __constructor for SoapClientInterface. I find it unnecessary and constraining. If I implement SoapClientInterface, I might need services like logging and etc., but I can not inject anything else into constructor due to __constructor declaration in interface.
Cheers

Hi,
I thikn I understand your issue but could you give me a bigger picture of your project and your needs? So we can figure out the best way to improve the PackageBase project,
thx

Maybe you can take example on @Gemorroj usage at #3


How to execute query automatically?

I'm able to load my graphiql page on the browser with a query: http://mysite:4080/graphql/graphiql.html?query=%0Aquery%20%7B%20%0A%20%20.... The problem is that it doesn't execute the query automatically so the user has to click the Execute button.
Is there a param I can pass to have it execute automatically?
Thanks,
Alvaro

The state management for GraphiQL has been completely refactored for graphiql@2. All of it now lives in contexts and can be consumed by hooks, both of with are defined in the @graphiql/react package.
Solving this specific use-case would looks something like this:
import { useExecutionContext } from '@graphiql/react';

function MyComponent() {
  const { run } = useExplorerContext();
  /**
   * Calling the `run` function will execute the current query. This is a
   * simple example where this is triggered by a button, but you could call
   * it anywhere else, e.g. in an effect that runs after the initial render.
   */
  return <button onClick={run}>Execute</button>
}


SHOW REGION for a time axis should show user-friendly time range

Reported by Ansley B Manke on 21 Aug 2007 17:17 UTC
( this is not new, goes back to v5.41 at least) Reported by Bill Lavelle:
yes? use coads
yes? set region/t=1-jan-1982:1-feb-1990
yes? set mode calendar
yes? show reg
default region:
X/I is unspecified
Y/J is unspecified
Z/K is unspecified
T=-6.2546E+10:-6.2801E+10
Should give date strings.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1532

Comment by<EMAIL_ADDRESS>on 21 Aug 2007 18:15 UTC
From memory (and possibly wrong):  All of what follows is guesswork.
This problem (as I recall) shows up only in the circumstance where no output has
yet been requested.  The problem is that the SHOW REGION command bases its
formatting on one of the low level "contexts" on the context stack and that
context does not get set until after a product has been requested.  Time words
are always stored as numerical values.  The translation into a date string
requires knowledge of a grid (a time axis), which means knowing a context.
A possible fix for this may be in the SHOW REGION command.  If it finds the
dataset to be unspecified in the context that it normally references, then look
up or down (I don't remember which) the context stack to find another context to
use.  Be careful, though.  This may appear to be fixed, only to give you an
outright wrong formatted date when a particular combination of open and closing
datasets and generating products is encountered.  Such a cure would be worse
than the disease.
A tempting but inadvisable approach would be to modify the USE (SET DATA)
command so that it sets the appropriate low level context.  There are serious
risks of side-effects, as this new dataset is likely to be inconsistent with
other information already found in that context.


Adding effects to an UIElement affects WebView

Adding any effect to an UIElement which may or may not contain a WebView control makes the WebView stop working. This makes it unresponsive to any events like click, scroll, etc.
Please fix this.

Hi @AppXDevWP - thanks for reporting this issue!  Could you please tell me what you're trying to accomplish and what you mean by WebView stop working?
For example, are you trying to load a web page on WebView, apply a desaturation effort to the WebView, and subsequently finding that you are no longer able to scroll or push buttons on the WebView?
If you have an example code that demonstrates this problem, that would help a lot with the investigation.
Thanks again!

Hi.
It is very easy to replicate this issue. Let's just say you are applying a temperature tint effect (I was using this, but I checked and turns out it affects all effects) to the LayoutRoot of a page.
On setting this effect, if the page had a WebView, it would cause it to not respond to any clicks, scrolls, etc.
I used the standard code for setting a sprite visual to a grid compositor, but replaced the effect with Temperature Tint effect (but as I have mentioned, all effects have the same issue)
Thanks,
P

Hi @AppXDevWP - I looked at this a little bit.    If so, then you are essentially placing something in front of the WebView that would receive all interactions from that point on (hence why you're not able to interact with it).
To be sure, though, would you mind sharing your code/project for me to verify what's happening in the visual tree?  thanks!

Sorry for delay @hanselo
I am applying the effect to the LayoutRoot of that page and the WebView is present in its visual tree. I can interact with everything except the WebView when the effect is applied.
Here is my code:
`var gridVisual = ElementCompositionPreview.GetElementVisual(LayoutRoot);
            var compositor = gridVisual.Compositor;

            var effectVisual = compositor.CreateSpriteVisual();

            effectVisual.Size = new Vector2(
              (float)100,
              (float)100);

            TemperatureAndTintEffect blurEffect = new TemperatureAndTintEffect()
            {
                Temperature = (float)settings.Values["FluxValue"],
                Source = new CompositionEffectSourceParameter("source")
            };

            var effectFactory = compositor.CreateEffectFactory(blurEffect);
            var effectBrush = effectFactory.CreateBrush();
            effectBrush.SetSourceParameter("source", compositor.CreateBackdropBrush());

            effectVisual.Brush = effectBrush;

            ElementCompositionPreview.SetElementChildVisual(LayoutRoot, effectVisual);`

Unfortunately, I cannot share the code of my actual project, but I can hook you up a temporary project to test.

@AppXDevWP thanks for that sample code.  I'll try it out on a test project and get back to you asap.

@hanselo the xaml of the page is like this:
<Page ...>

...
<WebView .../>
...

@AppXDevWP yep, I created a test app with your code and have communicated your scenario to my team ("Customer wants to apply an effect over a WebView").
We are currently triaging the issue to determine what the proper resolution should be.
Thanks again for using our APIs and reporting this issue!

Hi @AppXDevWP - my apologies for the long delay since our last correspondence.

Alternatively, have you tried using a layer visual? https://msdn.microsoft.com/en-us/library/windows/apps/Windows.UI.Composition.LayerVisual.aspx

At this time, we don’t have a way to enable your scenario just yet, but the team has received your feedback and we are using your feedback to prioritize enabling this scenario for future releases.  Thanks again for your valuable feedback!


Ignore specific checks on validation

The workflow information is not available in check runs and check suites, it is difficult to do anything at this point.


[nrf noup] boot/zephyr/boards: nRF54l15pdk ext flash cfg

Added configuration which allows to build MCUboot for nrf54l15pdk_nrf54l15_cpuapp with external flash used for the secondary slot.

you don't need to do any changes in mcuboot repo. You can put those configuration files in sdk-zephyr/samples/subsys/mgmt/mcumgr/smp_svr/child_image/mcuboot/boards:
nrf54l15pdk_ext_flash.conf -> nrf54l15pdk_nrf54l15_cpuapp.conf
nrf54l15pdk_ext_flash.overlay -> nrf54l15pdk_nrf54l15_cpuapp.overlay
find some details about multi-image builds here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/config_and_build/multi_image.html#permanent-configuration-changes-to-child-images

@de-nordic Need to be reapplied


Schema checking functionality

It should be necessary to check whether entries in the database match the schema. For example, crawl the database to make sure all of the constituent systems can be read in. This is important to check when the schema format is updated.

This should be fixed due to @lyuyangh 's great work on cacheing.


[BUG]

Describe the bug.
I noticed that https://www.asyncapi.com/community/events isn't populated with new events.
Expected behavior
Newly scheduled events should be shown on the list
Screenshots

How to Reproduce
Visit the /events section on the website
🥦 Browser
None
👀 Have you checked for similar open issues?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue ?
No, someone else can work on it

cc @akshatnema @derberg

I think it is because of https://github.com/asyncapi/website/issues/3036

I think it is because of #3036

I guess


Add documentation using docstrings and types

For #71
I added pdoc it should be very easy and straightforward to use.

Thanks for looking into this: I will have a look into pdoc and see if it's suitable.
One comment though: the auto-generated files should ideally not be added to master, but instead to a special branch from which the doc is rendered (typically gh-pages).

Could you create that branch I don't think I have the permissions.
I'll update the PR then.

Thanks for looking into this @Jujhar ! I will need a few days before I have time to evaluate whether pdoc is suitable. I will come back to you about this then.

Hi @Jujhar,
I looked into this now, and I think pdoc is a great choice, and meets all our requirements. Thanks for suggesting it, and for starting to contribute.
I have prepared the following now:

There is now a gh-pages branch, which we can use to deploy the documentation.

The rendered website will then be available at https://computational-cell-analytics.github.io/micro-sam/ (currently just a dummy)
The pdoc documentation also explains how to deploy to gh-pages: https://pdoc.dev/docs/pdoc.html#deploying-to-github-pages (I just skimmed it, but seems to be straightforward)

Including more documentation from markdown is also simple, see ... include Markdown files? in the pdoc documentation.
I will work on a PR where I will prepare a few things for the documentation:

Add a folder doc for all additional documentation material (markdown and images / gifs).
Standardize the doc strings:

We will follow the google docstring style
But use type annotation in all relevant function signatures instead of documenting the types in the doc string.

I will work on the content (creating some initial markdown files, creating and standardizing doc-strings + type annotations) in the next few days.
When you have time you can already look into adapting the doc generation code to what I described here. Let me know if you have any questions, and thanks again for contributing!

I have merged #80 now, so the base things for the documentation are there.

Hi @Jujhar ,
I went ahead and implemented the CI for the documentation here: #88.
Thanks for suggesting pdoc!

Hi @constantinpape, was out of town let me know for anything related to this or CI or automation in general (particularly advanced or very difficult things)


fix(921422) Added \b to groups to avoid unwanted FP's

Added \b to groups of 921422's regex.
Also added a negative test based on reported issue.
This PR fixes #2783.

Very nice. Thank you very much.
Looks like I expected it to look - and how I tested it myself to try the \b out myself.
Merging now.


User: allow superuser (no staff) to list and view users

Superuser (who is not the staff) was able to edit and delete users however he wasn't able to list and view them.

Btw, this can happen in multiple places in DD.

@Maffooch It is slighty different, users who are not Active cannot login. That's the way to deactivate a users without deleting the user object.
I personally see Staff literally, people who are employees of the company and therefore have some more permissions than users who are not Staff (external users who have access to DD but are not employees). This reflects very good how DD works currently and is easy to explain.
The new authorization is about permissions regarding products and product types. It is not designed to address the all other areas, eg. viewing/editing users or test types.
@kiblik I still don't understand your use case, why you need to have superusers that are not staff. DD works fine as long as superusers are staff as well. If we break that up, we should be consequent and check all occurrences of user.is_staff to see if we need to add an or user.is_superuser

There is a new issue to make sure superusers are staff users as well: #5271

This is from the offcial django docs:

So the staff flag controls whether a user can login to the admin site. It works like that in my instance and the demo instance:

If the user has no permissions, he/she can't do anything. But it does allow them login, which makes no sense. The "staff" thing has caused us nothing but confusion. And we're not the only ones if you google for "django staff admin superuser" permission for example: https://stackoverflow.com/questions/20469174/whats-the-difference-between-staff-admin-superuser-in-django

I am with you @valentijnscholten, we should get rid of the staff users. The admin portal should not be relevant for any user. In our next meeting I want to discuss a different approach, where you can give users or groups the permissions to do selected administrative tasks. The good thing is, we can use the Django permission as the backend for it.

Screenshot doesn't work for me as well

@devGregA  To be honest, I don't get what your use case is, when users can see a page where they cannot do anything. But I think we need to understand the use cases, before we can decide how to design a new solutions. Thinking of roles like "security staff" help, because it makes it clearer what these people want to do with DefectDojo.

I will have to check if the pr made it in, but it was an env variable that blocked the actual URL. @Maffooch did that get submitted? @valentijnscholten  I'm confused on your statement. If a superuser is both staff and superuser they will have full access to django admin because they are superuser. Staff doesn't play a part if I understand you. You can go to django admin as staff, but have no permissions, and we don't use any of the functions in django admin (unless there is a PR I missed, which is very possible). We used to use it for the password reset form, which we've since implemented as part of the actual dojo UI.

Looks like we crossposted. Although we spent limited amount of time to think about "security team" roles, I think the roles we have in place are a good start for those scenario's. For example the authorization migration script migrates staff users into being global owner which means they can manage all products and permissions, but not the configuration of Defect Dojo itself. Not sure about tools, credentials, etc. So maybe we need another permission or global role. But let's not call it staff as it confuses everyone as it's a Django internal permission.

@valentijnscholten Not all security people are developers. That is definitely the minority of our users, even though I would generalize and say they are more technically inclined. People get in to trouble with Dojo when we don't put in good guard rails, and choose to do any administration from django admin, which no one really should be for the intended use case of dojo.
Again, I'm not opposed to doing away with the staff status, using a different model, etc, but I do want to preserve the use case.
On intended usage, I'm not overly concerned, and I'm not opposed to your suggested solution, but specifically on intended usage, I believe our mistake was in lack of documentation. Django was created as content management system for news organizations that were 'perfectionists' and didn't want to use wordpress. The point I'm trying to get to is that specifically in regards to intended use of django, is that we are so far outside intended use, and have been since inception, that I don't think it makes sense to measure dojo against django. Has it caused confusion?  Absolutely, and we should address that.
Regarding the django admin portal, a narrow view of staff was used because in django 1.0 managing permissions was a nightmare. So we only used the password reset form. I've provided screenshots, and tested that users with only 'staff' permission (not superuser) do not have access to django admin. They can login, like you mentioned, but they see nothing by default and have no access. Maybe you have non-standard usage around admin that gives staff extra permission? I do think we should block django admin as a default, because for the majority of users, it poses a risk in regards to bricking their instance. I understand that there maybe a usage that is beneficial, which is why we try so hard to not kill use cases, but I do think the default should be what favors the  majority of the community, which can be overwritten and still accessed by flipping the environment variable.


Update package.json

so that it can be lodged on npm

Would you please consider npm publishing this repo? 😄


ignore the test_ls_styles

Breaks the CI too often

@sylvestre That's fair. Do you have an error message for the style test? I haven't seen that one break yet.

@tertsdiepraam

---- test_ls::test_ls_order_birthtime stdout ----
current_directory_resolved:
open: /tmp/.tmp5XjC2o/test-birthtime-1
run: /home/runner/work/coreutils/coreutils/target/debug/coreutils ls --time=birth -t
thread 'test_ls::test_ls_order_birthtime' panicked at 'assertion failed: `(left == right)`
  left: `"test-birthtime-1\ntest-birthtime-2\n"`,
 right: `"test-birthtime-2\ntest-birthtime-1\n"`', /home/runner/work/coreutils/coreutils/tests/by-util/test_ls.rs:580:5

Could you please try to make them work again?

FWIW the re_locale regex r"[a-z-]* \d* \w* \w* \d* [A-Z][a-z]{2} \d{2} \d{2}:\d{2} test\n" fails because it expects two digits for the day, but it's "May  1" (notice two spaces between May and 1 at least on my machine)

Oh that's hilarious! I'll fix it!

ah ah, well spotted :)


Broken stage2 (final system) clang+LLVM

So far gperf, OpenSSL, ninja, and groff fail to build with stage2 clang, but compile fine with stage0 clang.
When configuring groff source:
configure: error: a working C++ compiler is required

And when compiling GNUs binutils [without gold], the make check show lots of failures:
                 === binutils Summary ===

# of expected passes            290
# of unexpected failures        4
# of unsupported tests          2

                === gas Summary ===

# of expected passes            1588
# of unsupported tests          1

                === ld Summary ===

# of expected passes            2373
# of unexpected failures        101
# of expected failures          26
# of untested testcases         1
# of unsupported tests          144

But if i build binutils with llvmtools' gcc & binutils:
                === binutils Summary ===

# of expected passes            293
# of unexpected failures        2
# of unsupported tests          2

                === gas Summary ===

# of expected passes            1588
# of unsupported tests          1

                === ld Summary ===

# of expected passes            2743
# of unexpected failures        46
# of expected failures          63
# of untested testcases         1
# of unsupported tests          47

For both builds, tests ended in error

Stage 2 clang works fine. Past packages that will not compile now compile.
As of commit 095f20913b2e0831b476cbba584beb5bed675686, I'm using elftoolchain instead of binutils


Add concept of regions for sorting

As shown in #16
I tried a few different ways of doing this, with the alternative to a Handlebars helper being to do it client-side in JS. Hopefully this makes sense - happy to take another proposal (assuming you accept the premise of the change)

Should the region list go in constants.ts rather than pages.ts?

Resolves #16


how to get t1_diagnostic in UCCSD(T)

I am now doing a UCCSD(T) calculation t1_diagnostic can be determined in CCSD(T) and when UCCSD(T) can achieve this?

Thanks @ncrubin for the workaround. I'll close this issue. If this feature is desired, feel free to reopen the issue and add the "feature request" label.


LiveSDK Failed to request authorization

Dear all,
i have suffered in this case just a day ago, and there are no other similar case in the internet.
I was able to sign in to Live Services and passed the consent form a day ago. However, i was than failed to sign in through the Auth Dialog 9 hours after the first successful sign in, during the 9 hours, no code changes has been made.
The error message i received from XCode are shown below:

Any Idea?

Are you sure you were connected to the network when you tried to login?  Was the sign in page displayed?  I notice you are using the wl.offline_acess scope.  This grants you a refresh token and the LiveConnectClient will auto-refresh the auth token when it needs to, this way you don't have to sign in on every use of the app.


Remove 'experimental' from frontmatter - no longer used

We use preview now

Is that just these instances?
prisma-docs/content/200-concepts/100-components/06-prisma-studio.mdx
  5,1: experimental: false

prisma-docs/content/200-concepts/100-components/07-prisma-data-platform.mdx
  5,1: experimental: false

Thanks!

It is also in the code of the docs, where this frontmatter property is supported to do things - we do not need that any more.


route().current is inconsistent with laravel

Ziggy version
v1.4.3
Laravel version
any
Description
Go to the seminars.quote page and follow the Ziggy call
Ziggy call and context
console.log(route().params); // logs "devis"
console.log(route().current('seminars.quote', route().params)); // logs false but should be true

Ziggy configuration
{
  "url": "http://<IP_ADDRESS>:8000",
  "port": 8000,
  "defaults": {},
  "routes": {
    "seminars": {
      "uri": "colloques/{page?}",
      "methods": [
        "GET",
        "HEAD"
      ],
      "wheres": {
        "page": "[0-9]+"
      }
    },
    "seminars.quote": {
      "uri": "colloques/devis",
      "methods": [
        "GET",
        "HEAD"
      ]
    }
  }
}

Route definition
Route::prefix('colloques')->group(function () {
    Route::get('{page?}', function () {
        return "Seminars";
    })->where('page', '[0-9]+')->name('seminars');

    Route::get('devis', function () {
        return "Seminars quote";
    })->name('seminars.quote');
});

Analysis of the bug
Looking at the matchesUrl method, it looks like it's not using the wheres property of the route, but it should validate the found route against it, otherwise it matches the parent route which has an optional parameter
A workaround is to just invert the route definition so that the one without parameter gets matched first
Route::prefix('colloques')->group(function () {
    Route::get('devis', function () {
        return "Seminars quote";
    })->name('seminars.quote');

    Route::get('{page?}', function () {
        return "Seminars";
    })->where('page', '[0-9]+')->name('seminars');
});

But for more complex scenarios with overlapping params, this will not be possible, in any case the behavior differs from laravel

Right now Ziggy only uses that wheres key to check for wildcards (*) to avoid encoding slashes in the last segment when necessary. Ziggy doesn't really support actual where constraints on route definitions. That would be useful though, we can look into it (and I'd welcome a PR to add it!).
For now, putting your more specific devis route definition first should fix this.

Yep I just figured the workaround and edited while you where replying
I think there is 2 ways to go here:

Either we make the dehydration aware of the routes and validate the dehydration, this would prove very complex and resource intensive
Or we remove all this dehydration part and just pass the current route name and parameters in the head of the app (so that it works also in cases where using static generation) and use them in route().params and route().current()

PR is done with a bunch of tests and it works wonders in my app

Awesome, I'll take a look this week!


Upgrade to Chromium 84.0.4147.105

Addresses #1115. I will let you know once I have a successful build.

Can confirm a successful build on aarch64 and an ongoing almost-finished one for x86_64 for Manjaro and Arch.
(Actually with just the previous patch – but with sufficiently fuzzy patching, the patches were applied in the same way your commit would've made them apply).

My build succeeded and is running well. Feel free to merge.
@evs-ch Thanks for the kind words!


Add support for instanced meshes in STLEXPORT

CreateSTL has a new param "supportInstancedMeshes" which when set to true exports Instances without baking transforms on source mesh. Exporting instances with supportInstancedMeshes=false and doNotBakeTransforms=false may cause them to change orientation/positions in the scene.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Can't figure out how to add label to this PR. I thought I missed something the first time but can't see an option. Maybe I don't have permission?

Snapshot stored with reference name:
refs/pull/13439/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13439/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13439/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13439/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13439/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13439/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13439/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13439/merge#BCU1XR#0


Update to NixOS 24.11 - nixpkgs: nixos-24.05 -> nixos-24.11

Update NixOS and related channels to 24.11 as possible now
Bump dprint-plugin-kdl with the new schema of dprint

Resolves GH-757

Read and follow https://github.com/NixOS/nixpkgs/blob/8e5e5a6add04c7f1e38e76f59ada6732947f1e55/nixos/doc/manual/release-notes/rl-2411.section.md

:thought_balloon: Want https://github.com/kachick/dotfiles/issues/642 in these task...

TODO: Suppress these warnings
> sudo nixos-rebuild switch --flake ".#$(hostname)" --show-trace && makers apply 'kachick@nixos-desktop'
building the system configuration...
trace: evaluation warning: The ‘gnome.epiphany’ was moved to top-level. Please use ‘pkgs.epiphany’ directly.
trace: evaluation warning: The ‘gnome.geary’ was moved to top-level. Please use ‘pkgs.geary’ directly.
trace: evaluation warning: The ‘gnome.evince’ was moved to top-level. Please use ‘pkgs.evince’ directly.
trace: evaluation warning: The ‘gnome.gnome-calendar’ was moved to top-level. Please use ‘pkgs.gnome-calendar’ directly.
trace: evaluation warning: The ‘gnome.gnome-music’ was moved to top-level. Please use ‘pkgs.gnome-music’ directly.
trace: evaluation warning: i18n.inputMethod.enabled will be removed in a future release. Please use .type, and .enable = true instead
trace: evaluation warning: The ‘gnome.dconf-editor’ was moved to top-level. Please use ‘pkgs.dconf-editor’ directly.
trace: evaluation warning: The ‘gnome.gnome-boxes’ was moved to top-level. Please use ‘pkgs.gnome-boxes’ directly.
trace: evaluation warning: The ‘gnome.mutter’ was moved to top-level. Please use ‘pkgs.mutter’ directly.
trace: evaluation warning: The ‘gnome.gnome-settings-daemon’ was moved to top-level. Please use ‘pkgs.gnome-settings-daemon’ directly.

> sudo nixos-rebuild switch --flake ".#$(hostname)" --show-trace
building the system configuration...
error: builder for '/nix/store/j7r84gckajykldwv700z4m3j3gp9nvj8-bazel-7.4.0.drv' failed with exit code 1;
       last 10 log lines:
       > patching file src/main/java/com/google/devtools/build/lib/bazel/rules/BazelRuleClassProvider.java
       > Hunk #1 succeeded at 568 with fuzz 2 (offset 102 lines).
       > applying patch /nix/store/2y0fhjn87j7b22v3h8v5hxrmgbwmcn11-bazel_rc.patch
       > patching file src/main/cpp/option_processor.cc
       > applying patch /nix/store/9857sd4kzzpl1xcx81hwh98ldma58ya3-nix-hacks.patch
       > patching file src/main/java/com/google/devtools/build/lib/rules/repository/RepositoryDelegatorFunction.java
       > Hunk #1 FAILED at 178.
       > Hunk #2 succeeded at 634 (offset 24 lines).
       > 1 out of 2 hunks FAILED -- saving rejects to file src/main/java/com/google/devtools/build/lib/rules/repository/RepositoryDelegatorFunction.java.rej
       > patching file src/main/java/com/google/devtools/build/lib/shell/JavaSubprocessFactory.java
       For full logs, run 'nix log /nix/store/j7r84gckajykldwv700z4m3j3gp9nvj8-bazel-7.4.0.drv'.
error: 1 dependencies of derivation '/nix/store/vkzr7ymifkl2rwzzm59wxbm6q4bfv9mh-fcitx5-mozc-2.30.5544.102.drv' failed to build
error: 1 dependencies of derivation '/nix/store/l30skrld5wdww2fyy3301yvpqj5zysny-fcitx5-with-addons-5.1.11.drv' failed to build
error: 1 dependencies of derivation '/nix/store/icq9dndhzll0fz9masm01d6kskyjd5yz-dbus-1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/xcq3aq080zirpsx9sqzmw8fx5q9ja423-set-environment.drv' failed to build
error: 1 dependencies of derivation '/nix/store/dv9vnmjfg1zhfvlwfhf5xk5xmlkyyhhg-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/9sfp3658nagpr2pp65qjamzbzm3p297k-nixos-system-algae-24.11.20241116.201a24e.drv' failed to build

building the system configuration...
error: builder for '/nix/store/j7r84gckajykldwv700z4m3j3gp9nvj8-bazel-7.4.0.drv' failed with exit code 1;
       last 10 log lines:
       > patching file src/main/java/com/google/devtools/build/lib/bazel/rules/BazelRuleClassProvider.java
       > Hunk #1 succeeded at 568 with fuzz 2 (offset 102 lines).
       > applying patch /nix/store/2y0fhjn87j7b22v3h8v5hxrmgbwmcn11-bazel_rc.patch
       > patching file src/main/cpp/option_processor.cc
       > applying patch /nix/store/9857sd4kzzpl1xcx81hwh98ldma58ya3-nix-hacks.patch
       > patching file src/main/java/com/google/devtools/build/lib/rules/repository/RepositoryDelegatorFunction.java
       > Hunk #1 FAILED at 178.
       > Hunk #2 succeeded at 634 (offset 24 lines).
       > 1 out of 2 hunks FAILED -- saving rejects to file src/main/java/com/google/devtools/build/lib/rules/repository/RepositoryDelegatorFunction.java.rej
       > patching file src/main/java/com/google/devtools/build/lib/shell/JavaSubprocessFactory.java
       For full logs, run 'nix log /nix/store/j7r84gckajykldwv700z4m3j3gp9nvj8-bazel-7.4.0.drv'.
error: 1 dependencies of derivation '/nix/store/vkzr7ymifkl2rwzzm59wxbm6q4bfv9mh-fcitx5-mozc-2.30.5544.102.drv' failed to build
error: 1 dependencies of derivation '/nix/store/l30skrld5wdww2fyy3301yvpqj5zysny-fcitx5-with-addons-5.1.11.drv' failed to build
error: 1 dependencies of derivation '/nix/store/k6gh4w90hq91cqi13gvd7hqknsjcxhiv-dbus-1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/nxmppry1i95wann88zjfg3jwnlnwy44p-set-environment.drv' failed to build
error: 1 dependencies of derivation '/nix/store/9251lxal9b5hc2784qjyrqrvziqbvga8-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/2gmf54rjirvp24ir842r56p4k5fp7mw9-nixos-system-algae-24.11.20241116.057f63b.drv' failed to build

https://github.com/NixOS/nixpkgs/pull/356802

On macos-13 runner
copying path '/nix/store/wzr76whf1n1j3gnqc6h6wfjkhmg34vrr-cargo-check-hook.sh' from 'https://cache.nixos.org/'...
building '/nix/store/ynjsnb6lj1g2y7c5adr4pd80wn0fp7li-nix-init-0.3.2.drv'...
building '/nix/store/khyg0pj0f8kr10rc5nf3nmvbzcadsvq3-selfup-v1.1.6.drv'...
error: builder for '/nix/store/ynjsnb6lj1g2y7c5adr4pd80wn0fp7li-nix-init-0.3.2.drv' failed with exit code 101;
       last 25 log lines:
       > Executing cargoSetupPostPatchHook
       > Validating consistency between /private/tmp/nix-build-nix-init-0.3.2.drv-0/source/Cargo.lock and /private/tmp/nix-build-nix-init-0.3.2.drv-0/cargo-vendor-dir/Cargo.lock
       > Finished cargoSetupPostPatchHook
       > Running phase: configurePhase
       > Running phase: buildPhase
       > Executing cargoBuildHook
       > error: failed to get `askalono` as a dependency of package `license-store-cache v0.3.2 (/private/tmp/nix-build-nix-init-0.3.2.drv-0/source/license-store-cache)`
       >
       > Caused by:
       >   failed to load source for dependency `askalono`
       >
       > Caused by:
       >   Unable to update registry `crates-io`
       >
       > Caused by:
       >   failed to update replaced source registry `crates-io`
       >
       > Caused by:
       >   failed to parse manifest at `/private/tmp/nix-build-nix-init-0.3.2.drv-0/cargo-vendor-dir/cargo-util-0.2.14/Cargo.toml`
       >
       > Caused by:
       >   error inheriting `edition` from workspace root manifest's `workspace.package.edition`
       >
       > Caused by:
       >   failed to find a workspace root
       For full logs, run 'nix log /nix/store/ynjsnb6lj1g2y7c5adr4pd80wn0fp7li-nix-init-0.3.2.drv'.
error: 1 dependencies of derivation '/nix/store/m00[771](https://github.com/kachick/dotfiles/actions/runs/11887500125/job/33123304262#step:5:772)yz0yisbbck57f6vmzzj3sygkz5-nix-shell-env.drv' failed to build
Error: Process completed with exit code 1.

Looks like the nix-init has been updated to 0.3.2 from 0.3.0 in NixOS 24.11 channel

> </etc/os-release
ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.11.20241119.3b9b505"
CPE_NAME="cpe:/o:nixos:nixos:24.11"
DEFAULT_HOSTNAME=algae
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
ID_LIKE=""
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.11 (Vicuna)"
SUPPORT_END="2025-06-30"
SUPPORT_URL="https://nixos.org/community.html"
VARIANT=""
VARIANT_ID=""
VENDOR_NAME=NixOS
VENDOR_URL="https://nixos.org/"
VERSION="24.11 (Vicuna)"
VERSION_CODENAME=vicuna
VERSION_ID="24.11"

:tada: :camel:

How did you fix fcitx5 error :eyes:

Yeah... Avoiding the issue with using unstable channel for that package :sweat_smile: https://github.com/kachick/dotfiles/pull/943/files#diff-61b40353542a498a195ae238e4f8adaf8b7b17d04cf5af03652df9189ea7a4cfR297

I swear i didnt copy my line from you, too similar 😭😭😭
https://github.com/osbm/nixos-configuration/blob/c656992897381779ee9f7883a9b441a478fc7b0f/common/i18n.nix#L30


Paginate ignoring future:false

I'm still fairly new to Jekyll, but I've ran into a problem with jekyll-paginate-v2.
In my _config.yml i have
future: false

collections:
  mycollection:
    output: true

My pagination page is created with all posts (linked to posted page).  This includes future posts,  but because of the future: false the actual post page is not created.
jekyll-paginate-v2 is ignoring the future setting and creating links to a pages that does not exist.
I need to be able to hide future posts from the pagination pages.

Ah this setting is not considered in the plugin. I will take a look and see if I can't get this fixed.


Applying on a trained model

Hi Mochu, thanks again for the great work!
In your paper, I noticed you studied GrUMoDepth in §1.Introduction, and examined combined result with your design in §4.7.Discussion. These are some vague thoughts I have towards the two:

As a post-hoc method, GrUMoDepth does not require training a new model - it utilizes flipping + gray-scaling + noising + rotation of inputs after the model's inference. But as a result, the uncertainty map is less aligned due to limited sources.

On the contrast, MDEUncertainty introduced a new ranking-based regularizer, which boosts uncertainty quality. However, it is guided through loss in training, and generated as an extra metric in the model's inference. Therefore, it is integrated and has to be trained in a new model.

MiDaS has high resistance to noise thanks to huge training data. It's preferable to make use of both its large training and MDEUncertainty. However, MiDaS does not plan to release training code. Therefore, I would have to either use two models separately, or give up the idea and train from scratch.

Can you share your comments or perhaps point out what is inaccurate? This would be utterly helpful for understanding your work!
Thank you!! Haokun

Hi, here are some of my understandings:

Flip augmentation, for example, should be invariant to model predictions, but the model provides slightly different predictions, and it can reveal uncertainty to some extent. GrUMoDepth back-propagate this different and get intermidiate gradient maps in latent features, and find it to be more correlated with the oracle uncertainty (the actual error).

Our method, is a training-based one, which requires training a model to provide decent uncertainty representations.

If you want to derive uncertainty from MiDaS, you can try: simply measure the difference between flipped inputs / use GruMoDepth to extract gradients of the latent features. However, MiDaS does not provide metric depth, if you want to adapt it to give metric depth predictions you will need to train it anyway.

Thank you so much! This helps a lot, I'll reopen the issue if I have more questions on this topic :D


sanitize() does not handle Windows UNC paths

Hi, I noticed that sanitize() does not seem to recognize Windows UNC paths.
It seems to work with the modification below. My apologies for not having time to write this code prettily and prepare a proper PR with tests etc. Just want to report the issue.
void Path::sanitize()
{
  bool isWindowsUNCPath = m_path.c_str()[0] == '\\' && m_path.c_str()[1] == '\\'; // UNC path

  // Replace any backslashes \ with forward slashes /.
  size_t cur = string::npos;
  while ((cur = m_path.find("\\")) != string::npos) { // assignment intended
    m_path.replace(cur, 1, "/");
  }

  // Replace all double slashes // with a single one
  // Except for the first position, which would be a Windows UNC path
  cur = string::npos;
  while ((cur = m_path.find("//", isWindowsUNCPath ? 1 : 0)) != string::npos) { // assignment intended
    m_path.replace(cur, 2, "/");
  }

Thank you for the hint. I haven't even thought of UNC pathes when I wrote that function. Your contribution is appreciated, I see what I'll make of your code snippet.

If m_path is of zero length (default constructor of Pathie::Path) your suggestion is going to segfault. I have that fixed in my own version of it.
UNC pathes are Windows-specific I think. I'm going to wrap the code in an #ifdef _WIN32 thus, otherwise a Linux user is going to be probably surprised why // is valid at the beginning of a path.

Thanks! Yes, my code was a sketch. A more correct version would not use c_str() but just test the length and then access the string via operator[]().
However, just out of curiosity, why would it segfault? Even if the string is empty, c_str() will exist and point to a single 0 character, which is a valid memory address and value in a C string. Due to short-circuit evaluation of && it should not attempt to access the second character if the first one is not \. And if it is, the second character is always a valid memory address again, even for a length-1 string where it would contain a 0. (That's why I used the c_str() construct in the first place, but that's nevertheless a poor justification for doing that when it's more direct to just check the length.)
Thanks for looking into this!

However, just out of curiosity, why would it segfault?

You are right. Short-circuiting in effect! My bad.

but just test the length and then access the string via operator.

That's what I'm doing now.

Thanks for looking into this!

You're welcome.

Problem should be fixed now.


tendermint-rs: Disallow a block height of 0

Tendermint itself says: "Height must be greater than 0" (code -32603)

@Liamsi sounds good, will hold off.
I know there are a few cases where the block height is represented as 0 (e.g. in priv_validator_state.json) as a placeholder for an uninitialized state.
My personal preference in Rust would be to disallow 0 as a valid block height and use Option<block::Height> to represent potentially uninitialized cases.

My personal preference in Rust would be to disallow 0 as a valid block height and use Optionblock::Height to represent potentially uninitialized cases.

That sounds good to me 👍 Unfortunately, golang doesn't provide us with the same expressiveness as Rust.


enhancement(CX-1287): improve admin menu

The type of this PR is: Enhancement

This PR resolves CX-1287
Description
https://user-images.githubusercontent.com/73339470/119345035-0edc3080-bca1-11eb-8d9c-6463c5f5a6dd.mov

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

Thanks 🙌


Intel  GPU Support

Support Intel GPU alongside with NVIDIA, not sure if that is possible but it may help achieve better performance
check intel deep leaning kit
https://software.intel.com/en-us/openvino-toolkit/

@abdelrahmanmohamed Fyi. Please check this.

You may also check the following github rep
Intel-TF
Intel/MKL-DNN
OpenCL support

I do not think there are promising project which demonstrate good performance on Intel GPUs.
I know that OpenCL can work on these GPUs, but I am not sure about the performance.
This will  definitely need to be a community contribution, as we have no plans for this.
@claynerobison any resources on Intel GPUs you can point us to?

Hi @abdelrahmanmohamed. There are a couple of community supported OpenCL efforts, but nothing officially supported:

https://jonnoftw.github.io/2018/04/04/building-tensorflow-with-opencl-support-on-ubuntu-1604

https://github.com/hughperkins/tf-coriander

https://www.codeplay.com/portal/tensorflow™-for-opencl™-using-sycl™

Does TensorFlow support Intel GPUs in its latest releases?


update packing manager create product

Coverage remained the same at 74.894% when pulling cb8c8369fc04ad15125763384bfabb8c416a38e8 on leslieaula:dev into 60af4cf8b0d2c7e4f5d523e3d0057e5883df3bbe on danliris:dev.


Add Bill Marion's diffuse IAM integration method?

Is there interest in an implementation of Bill Marion's "Numerical method for angle-of-incidence correction factors for diffuse radiation incident photovoltaic modules" https://doi.org/10.1016/j.solener.2017.03.027 ?
Since the method itself just integrates an arbitrary AOI correction model over the relevant portion of the sky, I'm imagining a function like this that you could pass the other IAM functions into:
def marion_integrate(function, surface_tilt, region, N=180):
    """
    Integrate an incidence angle modifier (IAM) function over solid angle
    to determine a diffuse irradiance correction factor using Marion's method.

    Parameters
    ----------
    function : callable func(aoi)
        The IAM function to evaluate across solid angle.  Must take only one
        parameter, the angle of incidence in degrees.

    surface_tilt : numeric
        Surface tilt angles in decimal degrees.
        The tilt angle is defined as degrees from horizontal
        (e.g. surface facing up = 0, surface facing horizon = 90)
        surface_tilt must be in the range [0, 180]

    region : {'sky', 'horizon', 'ground'}
        The region to integrate over.  See [1]_ for details.

    N : int, default 180
        The number of increments in the zenith integration.

    Returns
    -------
    iam : numeric
        The incident angle modifier for the specified region.

    References
    ----------
    .. [1] B. Marion "Numerical method for angle-of-incidence correction
       factors for diffuse radiation incident photovoltaic modules",
       Solar Energy, Volume 147, Pages 344-348. 2017.
       DOI: 10.1016/j.solener.2017.03.027
    """

I think so. Some bifacial irradiance models include a term accounting for reflection of diffuse irradiance. There is a parameter FD in the SAPM equation for effective irradiance pvlib.pvsystem.sapm_effective_irradiance which is the fraction of diffuse irradiance transmitted through module materials to the cells.


ARM decode failure: spurious shift from ARM to THUMB

Describe the bug
the original identification was that "BNE decodes as LSL in ARM mode"... but upon closer inspection, it appears the decoder is changing into THUMB mode without apparent cause:
                         LAB_009bb914                                    XREF[1]:     009bb908(j)
    009bb914 00 00 54 e3     cmp        r4,#0x0
    009bb918 00 00 53 13     cmpne      param_4,#0x0
    009bb91c 01 00           lsl        param_2,param_1,#0x0
    009bb91e 00 1a           sub        param_1,param_1,param_1

when it should decode to the following:
(from Vivisect)
.text:0x027bb914  000054e3         cmp r4,#0x00
.text:0x027bb918  00005313         cmpne r3,#0x00
.text:0x027bb91c  0100001a         bne loc_027bb928

clearly the first two instructions are being decoded correctly, but then Ghidra is decoding the next instruction as THUMB LSL (btw, if imm5==0, it's supposed to be a MOV instruction).
To Reproduce
i believe you simply need to decode these bytes in this order, but since i'm not sure what's causing it, I'm not sure.
if it makes any difference, this is taken from an ELF library compiled for Android.
Expected behavior
i expect the decoder to track the ARM/THUMB state correctly throughout analysis
Environment (please complete the following information):

OS: Linux (Kubuntu) 18.04.2 64-bit
Java Version: 11.0.2
Ghidra Version: 9.0 - public - released 2019-02-28

Additional context
i'm not sure what else to say.  it isn't the target of a branch that I can tell (unless the sudden mode change somehow doesn't show any XREFs to that address), so I'm not sure what would make Ghidra spontaneously shift gears like this.  this is 8-bytes after a branch target, so there's potential for a complicated bug involving the fact that ARM mode execution pipeline has "effective PC" 8 bytes beyond real PC in the Operand decoding context (ie. PC-relative addressing is 8-bytes greater than is intuitively pleasing.

sadly the lib is very large and i cant share it. :(

Works fine for me.  If you clear it and re-disassemble does it come back this way?
Is there much non-returning functions that were fixed up in the binary?
Is there a red bookmark at the location?
It is possible there was bad thumb flow to the location, that was previously cleared because of non-returning functions, and the thumb mode is left there.
There is a hidden thumb register that specifies the mode to disassemble.  Ghidra is very careful to try and follow ARM/Thumb mode disassembly.  The most likely culprit is old flow that was cleared, or somehow the Thumb mode bit got set there (could even be from import).
You can turn the hiden registers on with:
Edit->ToolOptions...->Options->ListingFields->RegisterField->Display Hidden and Default Register values.
You can check before and after analysis to see when this starts occuring.  You can also turn analyzers off, like the Discover No Return functions analyzer to see if it is the culprit.

awesome, thank you.  i'll look into it (i figured i'd learn something about Ghidra in the process).
i have not manipulated the binary in any particular way.  i don't know Ghidra enough to do anything fancy.  i've only ever renamed functions, and i don't think that was on this bin.  it should be in a pretty pristine state.
i'll check out what you indicated, and get back to you.
thanks@

yes, there is a red X by the first thumb instruction.
i did clear and reflow and it looks fine now.  i the closed without saving in case there's anything more i can tell you.
i turned on the hidden registers and the code block now looks like this:
                         LAB_009bb914                                    XREF[1]:     009bb908(j)
    009bb914 00 00 54 e3     cmp        r4,#0x0
    009bb918 00 00 53 13     cmpne      param_4,#0x0
         assume TMode = 0x1
    009bb91c 01 00           lsl        param_2,param_1,#0x0
    009bb91e 00 1a           sub        param_1,param_1,param_1
    009bb920 02 00           lsl        param_3,param_1,#0x0
    009bb922 a0 e3           b          LAB_009bc066
         assume TMode = 0x0  (Default)

Something definitely flowed there incorrectly as thumb before.  Suspect it was a non-returning function that didn't clean up, however it should have cleared.
There is a potential it is an instruction start pattern gone wild.  Or a found heuristic flow from cleared bad code.
If you re-import from scratch, then save.
If you import from scratch and this section is labeled as having the Thumb bit on, then that would be an issue with the import ELF loader
Try analyzing with the Discover NonReturning functions analyzer off, there might be leftover code here.
If it is still the same, then undo and disable another one.  There really aren't many that could cause this though.
I'd try to see how and when the location flowed there as Thumb.  You could try firing up Ghidra in eclipse under debug, and then stopping when a create instruction call is made to the program API, but that might be a little deep.  If you go to the location during before analysis, then analyze, you may catch what it is doing during analysis when the thumb is laid down.
The processor designer must have missed the MOV as the preferred variant.  When building a processor module we try to catch them all, but it is a large instruction set with many variants.
Hope you find Ghidra useful.  It is good to have a full toolbox.

yeah, the recommended ARM aliases have changed a lot over the years, including a massive UAL change, to align ARM and THUMB assembly mnemonics.
thanks.  i'll give these a whirl and see what i can figure out.

The conversation seems to have ended here, and possibly resolved the issue. I'll go ahead and close the ticket.