fix support query hive view created by spark

What problem does this PR solve?
Problem Summary:

When using Spark to create hive view, the inputFormat saved in hive view is SequenceFileInputFormat.
I think this is a bug of Spark.
Actually, we don't need to check input format for view, so we skip the format check for hive view.

Fix a bug that when analyzing hive view, we should set both catalog and db in temporary connection context,
otherwise, the parse of hive view sql may fail, and will also reset the default db of current connection context,
causing following statement executed in this session failed because no default db is found.
Release note
None
Check List (For Author)

Test

[x] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall


Adding Folder in CLI Fails

Adding a folder is failing in the cli
Command
tableau_utilities --clean_dir --location local --file_path '/Users/jayrosenthal/Downloads/Costs copy.tdsx' --save_tds --debugging_logs datasource --column_name NAME --folder_name 'Jay FOlder 1231'

Error when opening file
Unable to complete action
Errors occurred while trying to load the data source "Costs". The load was not able to complete successfully.
Error(2297,69): value 'None' not in enumeration (id: /var/folders/b5/zgd5y94951x5gphxds76x5n00000gn/T/tableau-temp/1748688429/Costs.tds)

This no longer fails


cuda not detected in 0.39.0, but detected in 0.38.1

With pip install I get the same bug as many others (CUDA detection failed), this only happens with the version 0.39.0, while it works fine with 0.38.1. See bug report below.
When I try to install from source, I get the following bug during the make:

make: /usr/bin/g++: Command not found
make: *** [Makefile:85: cuda11x] Error 127

Even though I have preloaded gcc/9.3.0.
Error from python -m bitsandbytes:
bin /scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/libbitsandbytes_cuda114.so
False
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/tmp/jolicoea')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('-10')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/tmp/sshauth.16gYznUzisjyit6')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('1;/cvmfs/soft.computecanada.ca/easybuild/modules/2020/Core'), PosixPath('1;/home/jolicoea/.local/easybuild/modules/2020/Core'), PosixPath('1;/cvmfs/soft.computecanada.ca/easybuild/modules/2020/avx2/Compiler/gcc9'), PosixPath('1'), PosixPath('1;/cvmfs/soft.computecanada.ca/easybuild/modules/2020/avx2/MPI/gcc9/cuda11.4/openmpi4'), PosixPath('1;/home/jolicoea/.local/easybuild/modules/2020/avx2/Core'), PosixPath('1;/cvmfs/soft.computecanada.ca/easybuild/modules/2020/avx2/CUDA/gcc9/cuda11.4'), PosixPath('1;/cvmfs/soft.computecanada.ca/custom/modules'), PosixPath('1;/cvmfs/soft.computecanada.ca/easybuild/modules/2020/avx2/Core'), PosixPath('2;/cvmfs/soft.computecanada.ca/easybuild/modules/2020/avx2/CUDA/cuda11.4'), PosixPath('1;/cvmfs/soft.computecanada.ca/easybuild/modules/2020/CUDA/cuda11.4')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('imkl/2020.1.217'), PosixPath('mii/1.1.2'), PosixPath('python/3.9.6'), PosixPath('StdEnv/2020'), PosixPath('arrow/11.0.0'), PosixPath('pmix/3.1.5'), PosixPath('gcccore/.9.3.0'), PosixPath('gentoo/2020'), PosixPath('gcc/9.3.0'), PosixPath('rust/1.65.0'), PosixPath('cudnn/8.2.0'), PosixPath('cuda/11.4'), PosixPath('blis/0.8.1'), PosixPath('CCconfig'), PosixPath('libffi/3.3'), PosixPath('ucx/1.8.0'), PosixPath('gdrcopy/2.1'), PosixPath('ipykernel/2023a'), PosixPath('thrift/0.18.1'), PosixPath('libfabric/1.10.1'), PosixPath('openmpi/4.0.3'), PosixPath('flexiblas/3.0.4'), PosixPath('scipy-stack/2023a'), PosixPath('cudacore/.11.4.2')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/home/jolicoea/.local/easybuild/modules/2020/Core'), PosixPath('/home/jolicoea/.local/easybuild/modules/2020/avx2/Core')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//debuginfod.centos.org/ '), PosixPath('https')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('() {  ( alias;\n eval ${which_declare} ) | /usr/bin/which --tty-only --read-alias --read-functions --show-tilde --show-dot $@\n}')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('() {  eval "$($LMOD_DIR/ml_cmd "$@")"\n}')}
  warn(msg)
/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: Found duplicate ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] files: {PosixPath('/cvmfs/soft.computecanada.ca/easybuild/software/2020/Core/cudacore/11.4.2/lib/libcudart.so.11.0'), PosixPath('/cvmfs/soft.computecanada.ca/easybuild/software/2020/Core/cudacore/11.4.2/lib/libcudart.so')}.. We'll flip a coin and try one of these, in order to fail forward.
Either way, this might cause trouble in the future:
If you get `CUDA error: invalid device function` errors, the above might be the cause and the solution is to make sure only one ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] in the paths that we search based on your env.
  warn(msg)
CUDA SETUP: CUDA runtime path found: /cvmfs/soft.computecanada.ca/easybuild/software/2020/Core/cudacore/11.4.2/lib/libcudart.so.11.0
CUDA SETUP: Highest compute capability among GPUs detected: 8.0
CUDA SETUP: Detected CUDA version 114
CUDA SETUP: Required library version not found: libbitsandbytes_cuda114.so. Maybe you need to compile it from source?
CUDA SETUP: Defaulting to libbitsandbytes_cpu.so...

================================================ERROR=====================================
CUDA SETUP: CUDA detection failed! Possible reasons:
1. CUDA driver not installed
2. CUDA not installed
3. You have multiple conflicting CUDA libraries
4. Required library not pre-compiled for this bitsandbytes release!
CUDA SETUP: If you compiled from source, try again with `make CUDA_VERSION=DETECTED_CUDA_VERSION` for example, `make CUDA_VERSION=113`.
CUDA SETUP: The CUDA version for the compile might depend on your conda install. Inspect CUDA version via `conda list | grep cuda`.
================================================================================

CUDA SETUP: Something unexpected happened. Please compile from source:
git clone git@github.com:TimDettmers/bitsandbytes.git
cd bitsandbytes
CUDA_VERSION=114 make cuda11x
python setup.py install
CUDA SETUP: Setup Failed!
Traceback (most recent call last):
  File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx2/Core/python/3.9.6/lib/python3.9/runpy.py", line 188, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx2/Core/python/3.9.6/lib/python3.9/runpy.py", line 147, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx2/Core/python/3.9.6/lib/python3.9/runpy.py", line 111, in _get_module_details
    __import__(pkg_name)
  File "/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/__init__.py", line 6, in <module>
    from . import cuda_setup, utils, research
  File "/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/research/__init__.py", line 1, in <module>
    from . import nn
  File "/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/research/nn/__init__.py", line 1, in <module>
    from .modules import LinearFP8Mixed, LinearFP8Global
  File "/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/research/nn/modules.py", line 8, in <module>
    from bitsandbytes.optim import GlobalOptimManager
  File "/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/optim/__init__.py", line 6, in <module>
    from bitsandbytes.cextension import COMPILED_WITH_CUDA
  File "/scratch/jolicoea/qlora_/env/lib/python3.9/site-packages/bitsandbytes/cextension.py", line 20, in <module>
    raise RuntimeError('''
RuntimeError:
        CUDA Setup failed despite GPU being available. Please run the following command to get more information:

        python -m bitsandbytes

        Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
        to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
        and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues

@AlexiaJM The makefile harcode the path to the g++ executable, you can override it with : CUDA_VERSION=114 make cuda11x GPP=$(which g++) -j 2.

Thanks Charles, I did use this command successfully and was able to build it from source, but the bug persists. It's a bug caused by the bitsandbytes library sadly in their latest version 0.39.0.

The code should rely on the env variable CUDA_PATH which is defined when cuda is installed, as primary source.
LD_LIBRARY_PATH is not used on the systems.

This solution is very effective.

Bitsandbytes was not supported windows before, but my method can support windows.（yuhuang）
1  open folder J:\StableDiffusion\sdwebui，Click the address bar of the folder and enter CMD
or WIN+R, CMD  。enter，cd /d J:\StableDiffusion\sdwebui
2  J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes
3 J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes-windows
4 J:\StableDiffusion\sdwebui\py310\python.exe -m pip install https://github.com/jllllll/bitsandbytes-windows-webui/releases/download/wheels/bitsandbytes-0.41.1-py3-none-win_amd64.whl
Replace your SD venv directory file（python.exe Folder） here（J:\StableDiffusion\sdwebui\py310）


Remove radial charts and replace them with a bar chart

https://api.pmo.gov.et/v1/cases/

Decided to include two bar charts in place.

@yohannesHL that is cool


[TextField] aria-live="polite" should be added to input errors

Summary
When an input is in the error state and has an helper text there should be an aria-live="polite" attribute so screenreader users will be notified correctly.
Examples
No response
Motivation
Make the web more accessible
Search keywords: aria-live

Is there an official recommendation for the errored text fields errors to be using aria-live="polite"? It may be a bit too aggressive in my opinion to have it by default.
You can add it yourself by using the slotProps prop, e.g.:
 <TextField
   error
   id="filled-error-helper-text"
   label="Error"
   defaultValue="Hello World"
   helperText="Incorrect entry."
+  slotProps={{ formHelperText: { 'aria-live': 'polite' } }}
 />

cc @colmtuite do you maybe have some suggestion here?

@BennyAlex @mnajdova The required, aria-describedby, and aria-invalid attrs should handle this by announcing the required field and its corresponding helper text when focus is placed back on the invalid input after the attempted form submission.
It would be different if you have a block of error messages above your form, but in that case, the error block would typically be role="alert" anyway.
So either way, adding aria-live="polite" by default is a bit aggressive, yep.

Its not only the textfield its for all errors on inputs, so checkboxes and autocomplete for example would need this to.
When an user types or selects something and the state changes (becomes errorneous) the user needs an feedback. For seeing users this is already solved, but screenreader users only see the difference when they proceed / go down to the helper text.
For such dynamic content aria-live was introduced.

I'll wait for more upvotes or comment before doing any action about this issue. There is a way for users to add the prop if they feel like that is the best use-case for their forms.


GEODE-8864:finish implementation of Redis HScan Command (#5954)

-add test for hscan not returning value removed from hash
-refactor some tests to better reflect use cases
-create HScan DunitTest
-Fix Concurrency issue for Hscan
-add UUID to client
-make hscan on redisHash store/retrieve  snapshot of entryset for each client
-add Unit tests for Redishash.HscanSnapshot
Authored-by: john Hutchison<EMAIL_ADDRESS>(cherry picked from commit b2b31cec3301d976ef8fd4d647e5cffd5d11f176)
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

this pr is a new version of https://github.com/apache/geode/pull/6120, which was just closed

Failures in CI are unrelated to PR, merging backport.


Add relativelyCloseTo implementation

@sooniln source branch appears to have been deleted so won't be able to merge.
if you want to rebase from master, as hamcrest-core and hamcrest-library have been refactored a lot and also deprecated, so that everything is just in hamcrest. we can try again


How to use multiple database with multiple website

I have installed hyn/multi-tenant package successfully now i want to make two website with separate database but i don't know how to configure this
i read your documentation from "https://hyn.readme.io/" but there is only how to install package
just tell how to use code with laravel 5.3 fresh installation

The documentation didn't help?
https://hyn.readme.io/docs/tenants

As discussed on Gitter.

ok got it


AMQNET-639 Add SourceLink support

I'd like to add SourceLink support to this library in order to simplify debugging from referencing projects.
It would be great to first merge AMQNET-638 Add SourceLink support and then update Apache.NMS package reference to v.1.8.1
Please take a look into the small demo of SourceLink in action

For more details on how to enable debugging with SourceLink please check the following guides:

How to Configure Visual Studio to Use SourceLink to Step into NuGet Package Source
Debugging into NuGet packages with SourceLink in Visual Studio for Mac

For more details on SoureLink, please navigate the following links:

dotnet/sourcelink
SourceLink file specification

lgtm

+1 from me also, lets merge this! @lrushl thanks, also re your mail to dev, did you get my reply? one main thing would be that we make sure examples available in artemis.


Create atomic-design-methodology.md

@kellysinterniklaas can you merge?

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


kubernetes-controller-tools: 0.8.0 -> 0.9.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes-sigs/controller-tools/releases.
meta.description for kubernetes-controller-tools is: "Tools to use with the Kubernetes controller-runtime libraries"
meta.homepage for kubernetes-controller-tools is: "https://github.com/kubernetes-sigs/controller-tools"
meta.changelog for kubernetes-controller-tools is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.2 with grep in /nix/store/8llhxw1dflmgpbpqyrfnypcwl9d3rgqh-controller-tools-0.9.2
found 0.9.2 in filename of file in /nix/store/8llhxw1dflmgpbpqyrfnypcwl9d3rgqh-controller-tools-0.9.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kubernetes-controller-tools

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8llhxw1dflmgpbpqyrfnypcwl9d3rgqh-controller-tools-0.9.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kubernetes-controller-tools https://github.com/r-ryantm/nixpkgs/archive/4e8688215ff5ef090fddbe63b9b8b365a707c6bf.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8llhxw1dflmgpbpqyrfnypcwl9d3rgqh-controller-tools-0.9.2
ls -la /nix/store/8llhxw1dflmgpbpqyrfnypcwl9d3rgqh-controller-tools-0.9.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kubernetes-controller-tools

Maintainer pings
cc @michojel for testing.

Result of nixpkgs-review pr 186651 run on x86_64-linux 1

1 package built:

kubernetes-controller-tools


Exception concerning depscan metrics

Hi!
I've just got this error trying to scan a project using depscan as one of the chosen tools:
╭─────────────────────────────────────────────────────────── Recommendation ───────────────────────────────────────────────────────────╮
 │ ✅ No package requires immediate attention since the major vulnerabilities are found only in dev packages and indirect dependencies. │
 ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
 [11:33:57] DEBUG    Depscan and HTML report written to file: /builds/platform/common/xxx/reports/depscan-report-java.json,
                     /builds/platform/common/xxx/reports/depscan-report-java.html 👍
            DEBUG    License check and HTML report written to file: /builds/platform/common/xxx/reports/license-java.json,
                     /builds/platform/common/xxx/reports/license-java.html 👍
 Traceback (most recent call last):
   File "/usr/local/src/scan", line 716, in <module>
     main()
   File "/usr/local/src/scan", line 684, in main
     report_summary, build_status = analysis.summary(
   File "/usr/local/src/lib/analysis.py", line 106, in summary
     metrics, required_pkgs_found = calculate_depscan_metrics(dep_data)
   File "/usr/local/src/lib/analysis.py", line 75, in calculate_depscan_metrics
     metrics[severity] += 1
 KeyError: 'unspecified'

Has there been any recent development that could make this fail?

Can you send a PR?
Here add 3 more keys for unspecified https://github.com/ShiftLeftSecurity/sast-scan/blob/master/lib/analysis.py#L51
This is happening because some CVE has a severity of unspecified.

Sure! I'll send you a PR asap!


News list template should use pagination info from the context

The current News list view would paginate results (10 items per page). We may want to increase the page size, and use the pagination information in the template (cc @gregnewman).

 But I might also hate the consequences of not having pagination. Although I am not quite sure what those are.
Here's one thing that really sucks:

GitHub changed the commits page to be paginated and have only "Back" and "Next." It used to show page numbers, and you used to be able to go directly to any page by editing a query parameter at the back of the URL.
I don't know how much of this is relevant to News pagination if at all, but GItHub's change traumatized me...


Mixed scores for matching results.

I have matches that come through with a score of 2.2+ and then other concrete matches that show a score of 0.01 - I have some code that looks for anything over 2 and anything under 0.1, but are you aware of this?

Hey @ItsJoeTurner, thanks for reporting.
I'm not aware of those issues, but this is just a "dumb" port of Fuse.js, so I'm not familiar with the searching/scoring logic myself. If you could provide an example that produces these results, I could determine if this is an issue with Fuse.js itself or with my port.

If you round($result, 4) the result, you will get 0.0001
Original post:
https://github.com/krisk/Fuse/issues/481#issuecomment-691711949

So this seems to be an issue with Fuse.js itself. Gonna mark this as upstream.


Refactor IrcCommandHandler into separate file

Pytest was complaining about circular imports. I tried to use if TYPE_CHECKING, but with no luck. Pytest gave different AttributeErrors, for example, it didn't like func(server: Server).
I got some help in #python, and the best solution we could get to was importing handle inside of recv_loop().
They did however say that imports in method usually means smelly code. He thought the best option was to put the functions in handle.py in a class.
He also said he didn't like the getattr() solution for a module. He talked about a @register decorator to use with a dict. I'm not sure how that would be done, if it's really a better solution. What do you think?
Here are parts of our conversation:

Regarding a @register decorator and a dict of functions: Mantaray had a @register decorator (named differently), and I deleted it because it was more complicated than it needed to be. The exactly same thing happened in Porcupine's pastebin plugin. See _define_commands() in mantaray's current commands.py for what ChrisWarrick had in mind.

Circular imports: The problem was that when mantatail.py was imported, it imported handle before defining its classes, and then handle imported the not-yet-loaded mantatail and tried to do mantatail.Server in a type annotation. If the import is moved inside a function, it runs much later, when both files are fully loaded and they contain everything you defined in them.
An easy and not smelly fix is to add from __future__ import annotations to the beginning of handle.py. This causes Python to not evaluate the type annotations at all, so even if they do mantatail.Server and mantatail isn't fully loaded yet, Python won't notice it. (This is the default behaviour in Python 3.11 and newer.)


on page refresh, showing undefined for all counter variables

First of all, thanks for this tool. I just installed it in my project, it works fine.
My only gripe is that when the page loads or refreshes, undefined is displayed for all counter variables, if this can be shown as 0 for all variables, it should be fine.
For now, I have put in the check to see if the value is set then show variable or show 0 like below, now I am seeing 0 on page refresh.
{counterResult.projects ? counterResult.projects : 0}
Thanks

let me know if the fix works for you

Thanks John, this fix is working fine now. I am closing this issue.


feat!: v0.2.0

Description

BREAKING! (cubit): do not emit current state on subscription (#closes #52)
BREAKING! (cubit_test): skip defaults to 0 since cubits no longer emit upon subscribing.

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[X] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

closing since this repository has been moved to https://github.com/felangel/bloc


feature (plugins): Call back function to tie plugins together for submitting and updating

Describe Problem
Suggest Solution

controllable updating of ui-plugins is needed
recursive submitting of data to tie different ui-plugins together is needed.

Additional Details

Interesting, where do you plan to use this?

(Some time ago, we decided to implement and test this functionality individually, before having a new meeting to discuss and compare solutions).

What about using the observer pattern?

https://tanstack.com/query/v3/docs/react/overview


Feature Request : Add SSL to site

Description
Add SSL(https) Support to materializecss.com.
You can use openssl Lets Encrypt (Its Open Source).

Materialize is using github hosting in combination with a (I guess) DNS provider. Github hosting offers https but due to the custom domain the certificate is not valid. Maybe Materialize could switch to cloudflare, where a ssl certificate is free and included?

There isn't any sensitive information that should be sent from either side on our website, so I don't think this is all that necessary.

@Dogfalo @acburst Please, look into it https://github.com/Dogfalo/materialize/pull/4278

https should be used by default. It works with Cloudflare and GitHub, see https://websectools.com and https://github.com/DanielRuf/WebSecTools
Modern browsers are pushing more and more to a https-only internet and many apps and search results often redirect to the https version which often causes issues if there is no valid TLS certificate ;-)

There isn't any sensitive information that should be sent from either side on our website, so I don't think this is all that necessary.

To quote from an article of at Googles Web Fundamentals

You should always protect all of your websites with HTTPS, even if they don’t handle sensitive communications.

Maybe (in the future) we should consider to move to netlify
See: https://macwright.org/2017/05/08/https.html & https://netlify.com

I agree with @tomscholz this isn't a priority right now.


Highlighting entities in user examples is not working

Closed by https://github.com/samtecspg/articulate/commit/d018df6d06989b2411ad551e0230707d920dae9e


fix handling translated fake fields

This will fix an issue introduced with  #1488 in PR #1533 found in #1546.
Currently working on some unit tests for CrudTrait as we currently only test CrudPanel

MUCH cleaner than my PR https://github.com/Laravel-Backpack/CRUD/pull/1549!
Thank you @OliverZiegler !

@tabacitu ready and packed with basic tests. 🎉
In FakeColumnsModel some of the $fillables are currently not used, but would like to leave them there for later.
Found some idea for a nice feature here.

Travis's unit tests say go.
My manual tests say go.
So this is a go :-)
Thank you so much @OliverZiegler . Excellent PR.
Of course, leave them, whatever you need. Curious to hear your new feature idea.

@tabacitu here you are #1552
could be nice imho 😅

I think I've come across an issue with translated fake fields where it's saved to the DB correctly but does not decode translated fake fields properly to be displayed in the fake fields during edit. Think the shouldDecodeFake() should also check if the column is translatable?
I've attempted to fix this issue here #1636 (It's a follow up to issue #1633)
Please have a look at the PR


/tmp tmpfs is using the systemd upstream mount.

Issue description
Because of how the tmp mount is defined (it is shipped with systemd), we are unable to configure the mounting of tmpfs without disabling boot.tmpOnTmpfs and providing a custom systemd.mounts. I've been able to do this here:
https://gist.github.com/sheenobu/09947df2480e693161d3b3d83daddd49
Should the tmp.mount systemd unit be generated like above within the nixos config / https://github.com/NixOS/nixpkgs/blob/32b7b0009f168cb7e020d297c2f336ef352e9ec1/nixos/modules/system/boot/tmp.nix ?
Steps to reproduce
Enable tmpOnTmpfs.
Check systemctl cat tmp.mount.
tmp.mount is labelled as shipped with systemd and therefore not something configurable within nixos.
tmp.mount has options listed but no way to change them.
Technical details

System: 16.03.581.e409886
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version:  16.03.581.e409886

I don’t know if this has changed since the report, but it seems you can configure tmp.mount:
{
  boot.tmpOnTmpfs = true;
  systemd.mounts = [{
    where = "/tmp";
    what = "tmpfs";
    options = "1777,strictatime,nosuid,nodev,size=30%";
  }];
}

This generates an override file at /etc/systemd/system/tmp.mount.d/overrides.conf:
[Unit]

[Mount]
Options=mode=1777,strictatime,nosuid,nodev,size=30%
What=tmpfs
Where=/tmp

Perhaps the syntax could be made nicer (if systemd.mounts accepted a set with where as the key, and what were made optional, we could just write systemd.mounts."/tmp".options = "1777,strictatime,nosuid,nodev,size=30%";).


Variable split breaks original variable

Describe the bug
When using the variable split features, sometimes the original symbol gets lost.
To Reproduce
Steps to reproduce the behavior:

gunzip attached program, load it into Ghidra, with analysis
Jump to 0x0101180 and mark it as int main(int argc, char **argv)
Rename pcVar5 (1st assignment to *argv) into prog_name
Jump to line 42 (decompiler view) and use "Split Out As New Variable" on prog_name
Rename it to ret0
Observe that prog_name is now named pcVar6

Expected behavior
pcVar6 should preserve its prog_name value
Screenshots
Screencap of the operation: https://user-images.githubusercontent.com/34467/196301533-3b296965-af7f-4aa3-b41c-83708f6f6124.mp4
Attachments
secr3tfl4g.gz
Environment (please complete the following information):

OS: Archlinux
Java Version: <IP_ADDRESS>
Ghidra Version: 10.1.5
Ghidra Origin: Archlinux official packages

Note: still reproducible with 10.2.3


ptxas warning : Unresolved extern variable

ptxas warning : Unresolved extern variable 'mangled-name' in whole program compilation, ignoring extern qualifier is being triggered when using inline constexpr global variables and static constexpr member variables in device code. This predominantly happens in debug builds; the 30 warnings reduce to 5 when switching to a release build (I imagine due to the variables being optimised out?). This is of course not a big deal as the program still compiles - I'm only mentioning it for completeness.
(I've just finished porting a reasonably complex C++20 application to hipSYCL and I have to say: you've done a fantastic job! Aside from a few Clang bugs and the usual difficulties in setting up C++ build scripts, hipSYCL works perfectly. Thanks again!)

Ah, I think I have seen this before.. May be related to the way constexpr variables get pulled into device code. Thanks for bringing this to my attention and thank you for your kind and motivating words :)

Here's a minimal example of this causing a miscompilation on the sm_75 CUDA platform:
#include <SYCL/sycl.hpp>

constexpr int global = 20;

struct Foo {
    int a;
    int bar() const { return std::min(a, global); }
};

int main() {
    Foo foo{10};
    sycl::buffer<Foo> buffer{&foo, sycl::range<1>{1}};
    sycl::queue{}.submit([&](sycl::handler &cgh) {
        auto access = buffer.get_access<sycl::access::mode::read>(cgh);
        cgh.parallel_for<class kernel>(sycl::range<1>{1}, [access](sycl::item<1> item){
            printf("%d\n", access[item].bar());
        });
    });
}

Compiler warnings:
ptxas warning : Unresolved extern variable '_ZL6global' in whole program compilation, ignoring extern qualifier

Expected program output:
10

Actual program output:
0

I had to toy around with the code a little to stop the compiler from inlining the constant. It sems like the constant memory for this variable is not correctly initialized on the device.


Create Limit for Active Queries on Jobs Page

Find way to limit the number of queries displayed on the Jobs page. Most important is to make sure that the list doesn't become too long and hard to navigate for users. Options:

Limit Number of Queries displayed (deleting old ones) to ~10-20
Allow users to delete Queries
have Queries Time out after a set period of time (this option must be combined with one of the other two above, again, so the list doesn't become too unruly to navigate)

We could do any or all of these.  What is your preference?  The first one would be easy and useful for folks if not too many arrived at once.

Let's go with the first one then (easiest to implement and explain); traffic should be light

Currently limited to 10, but can be changed with the job_list_capacity setting in the config module.
Give it a try.


SfImage improvements

We need a few improvements on SfImage

Make image load lazily (add prop lazy defaulting to true)
Add placeholder (prop placeholder)

Browser native lazy load stills on very early stages (only Chrome supports), lozad is already being used on SfGallery so I think we should also use it on SfImage.
Additionally, would be good to optionally render a <picture>, I would suggest to receive a src string on prop or a picture object with multiple sizes, wdyt?

We have talked about on dicord...

@matheusgnreis

@talissonf @matheusgnreis

@leomp12, 100% agree on both points ;)


Don't recursively update projects which have already been evaluated

Imagine a directory structure like the following:
dirs.proj
Level1\
    dirs.proj
    Level1a\
        Level1a.csproj
    Level1b\
        Level1b.csproj

With the current code it seems that we'll call the NuGetUpdater.CLI for dirs.proj, Level1\dirs.proj, Level1\Level1a\Level1a.csproj, and Level1\Level1B\Level1b.csproj, despite the fact that the first dirs.proj contained references to Level1\dirs.proj, which contains references to the csproj's, so they've all already been checked for the needed updates. This PR is attempting to make sure that we only make the initial call to dirs.proj (and any project file underneath it which was not included by dirs.proj, accidentally or otherwise).
I'm sending this one a bit early so that people can check my logic (and to use the CI for testing since my local instance was being annoying).

As @JoeRobich and @brettfo pointed out offline, it's not just dirs.proj, tests.proj is just as valid etc. I don't THINK any of my changes are dirs.proj exclusive, but someone let me know if you spot something to the contrary.

I would be very surprised if my PR was actually related to that error. I didn't make a change to Nuget.config handling, the error apparently only happened once, and it sounds like the error is "Read-Only File System" which can sometimes indicate file system corruption (linux makes the FS read-only to keep it from doing more damage). My best bet would be a random flaky docker problem.


[cPP Correction] Local Console Types

Provide the location of the issue
Section <IP_ADDRESS>, Application Note 22
What is the correction request for the cPP? Please describe.
Now that a local console is optional, Application Note 22, item c should be deleted.
Additional context
This was a hack to allow TOEs without a true local console to have a path forward under previous versions of the NDcPP.

Recommendation...
Accept Kenji's recommendation as stated in the issue description.

Resolved in PR #126

Agreed.


Missing comma after empty array not detected as invalid

This .json passes validation with 2.6.2 even though it is missing a comma after the [] (which causes the Chef knife command to subsequently fail):
{
  "name": "aname",
  "chef_environment": "anenv",
  "run_list": [
  "role[arole]"
]
,
  "normal": {
    "base": {
      "something": {
        "labels": "alabel"
      }
    },
    "tags": []
    "jlink": {
        "a": {
            "serial": "1"
        },
        "b": {
            "serial": "2"
        }
    }
  }
}

Sorry this sounds likean error with json parsing (ie. the json gem) rather than schema validation (ie json-schema).
Can you please give some example code where you're using this?

I'm closing this, as it appears to be an issue with the json gem rather than json schema


Stored properties cannot be marked potentially unavailable with '@available'

Hi Team,
I am using Xcode version 14.1, with minimum deployment iOS 13 and AnyImageKit version 0.13.5.
When I try building the application getting build error in AssetPickerViewController as shown below. Please help me o fix this issue.
Note: I need to support users from iOS 13

Please update the AnyImageKit to 0.15.0


Utilize HTML parser vs Regex for webpage scraping

Closing for now. May not be necessary or beneficial.


docs: fix TypeIt error on the homepage

fixeds #1537
The reason for this problem is typie version @7.x up to @lasted(8.8.3).
I'm trying to a lot of typeit verison, finally found<EMAIL_ADDRESS>can run normally.

Thanks a lot!


wittamore.com

Please fill out ALL ITEMS below before submitting a new issue. If this is a for an update to an existing site, please ensure "UPDATE" is in the issue title.
PLEASE PROVIDE THE UNCOMPRESSED SIZE ONLY
Link to GTMetrix results: https://gtmetrix.com/reports/wittamore.com/oCpMJPek/
- domain: wittamore.com
  url: https://wittamore.com
  size: 3.56kb

Example completed template for example.com with an UNCOMPRESSED size of 72.5KB:
- domain: example.com
  url: https://example.com
  size: 72.5

Hi! please add my site to your list, thanks!


fix windows ci

On Windows, ensure proper handling of both cl.exe and clang-cl.exe. Previously, our setup did not use clang-cl.exe.

clang-cl doesn't seem to like some boost::archive stuff

clang-cl doesn't seem to like some boost::archive stuff

Indeed, this is related to a current issue on conda-forge that @fabinsch is now fixing :)

Similar to our conda-feedstock, we now get a linker error on Windows with clang-cl.
Not setting the CMP0167 policy, e.g. removing this commit, results in a lot of warning but allows to compile and link on windows with clang-cl.

@fabinsch could you push your fix here?


When pluralization is off there should not be _pluralCardinalEn and _pluralOrdinalEn methods generated

in build.yaml I turned off pluralization but in the generated file I have unused private methods _pluralCardinalEn and _pluralOrdinalEn.
Is it possible not to generate the mentioned methods?

this is fixed in 5..0.1. closing issue


[Dynamic Region] tikv crash for failed to get flushed index

Bug Report

What version of TiKV are you using?

Release Version:   7.2.0-alpha
Edition:           Community
Git Commit Hash:   4f895209960951030b8f05a427c8bb41b0b1a6f0
Git Commit Branch: heads/refs/tags/v7.1.0
UTC Build Time:    2023-05-30 10:02:06
Rust Version:      rustc 1.67.0-nightly (96ddd32c4 2022-11-14)
Enable Features:   pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile:           dist_release
What operating system and CPU are you using?

Steps to reproduce

maybe run w/r workload and restart tikv
What did you expect?
tikv not crash
What did happened?
one tikv always crash
[2023/06/06 16:40:46.795 +08:00] [FATAL] [lib.rs:497] ["failed to get flushed index [region_id=2752] [cf=lock] [apply_trace=ApplyTrace { data_cfs: [Progress { flushed: 1508445, last_modified: 1508445 }, Progress { flushed: 0, last_modified: 0 }, Progress { flushed: 0, last_modified: 0 }], admin: Progress { flushed: 0, last_modified: 0 }, persisted_applied: 0, last_flush_trigger: 0, try_persist: false }]"] [backtrace="   0: tikv_util::set_panic_hook::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/lib.rs:496:18\n   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2032:9\n      std::panicking::rust_panic_with_hook\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:692:13\n   2: std::panicking::begin_panic_handler::{{closure}}\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:579:13\n   3: std::sys_common::backtrace::__rust_end_short_backtrace\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:137:18\n   4: rust_begin_unwind\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:575:5\n   5: core::panicking::panic_fmt\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:65:14\n   6: raftstore_v2::operation::ready::apply_trace::ApplyTrace::recover\n      raftstore_v2::operation::ready::apply_trace::<impl raftstore_v2::raft::storage::Storage<EK,ER>>::new\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/raftstore-v2/src/operation/ready/apply_trace.rs:411:37\n      raftstore_v2::batch::store::StorePollerBuilder<EK,ER,T>::init::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/raftstore-v2/src/batch/store.rs:367:37\n      <raft_log_engine::engine::RaftLogEngine as engine_traits::raft_engine::RaftEngine>::for_each_raft_group\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/raft_log_engine/src/engine.rs:835:17\n      raftstore_v2::batch::store::StorePollerBuilder<EK,ER,T>::init\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/raftstore-v2/src/batch/store.rs:364:9\n      raftstore_v2::batch::store::StoreSystem<EK,ER>::start\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/raftstore-v2/src/batch/store.rs:723:21\n   7: tikv::server::raftkv2::node::NodeV2<C,EK,ER>::start_store\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/raftkv2/node.rs:226:9\n      tikv::server::raftkv2::node::NodeV2<C,EK,ER>::start\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/server/raftkv2/node.rs:133:9\n   8: server::server2::TikvServer<ER>::init_servers\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/server/src/server2.rs:797:9\n   9: server::server2::run_impl\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/server/src/server2.rs:133:25\n      server::server2::run_tikv\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/server/src/server2.rs:171:5\n  10: tikv_server::main\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/cmd/tikv-server/src/main.rs:222:32\n  11: core::ops::function::FnOnce::call_once\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:513:5\n      std::sys_common::backtrace::__rust_begin_short_backtrace\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:121:18\n  12: main\n  13: __libc_start_call_main\n  14: __libc_start_main_alias_2\n  15: <unknown>\n"] [location=/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/raftstore-v2/src/operation/ready/apply_trace.rs:184] [thread_name=main]

Dup #14743


[5.1] SR-11917: Using JSONEncoder's .outputFormatting = .sortedKeys has a memory leak on Linux

Any use of NSString.compare(_:options:range:locale:) with a non-nil locale
would leak on Linux.

_CFCompareStringsWithLocale was leaking the collator on non-macOS
platforms.

Use the collator cache on Linux and Win32 the same way that macOS
does.

(cherry picked from commit 1112582e513f05258dc45f8b66f7e8bcc4add1f3)

Backport of #2655, 5.2 version is #2692
cc @weissi

@swift-ci test

@swift-ci test

@spevans this one failed the macOS Platform test twice, any ideas?

Looks to be unrelated since its python lint tests that are failing in the main swift repo. Note the macOS tests are normally ignored since they dont actually build swift-corelibs-foundation at all or run any of the tests - the CI really needs to be replaced for testing on macOS with something that does.

@shahmishal can we merge this? (See @spevans 's comment)

@swift-ci test macos

This is targeting swift-5.1-branch, we don't currently have plan on releasing new toolchain for 5.1.x.


divergence in p tables for large n

only occurs as the numbers get large
i suspect this is a loss of precision in the default float data type in python
nominally support for arbitrarily big integers but when i coerce to int i get "Python int too large to convert to C long" which seems to be related to 32 vs 64 bit infrastructure.
the fact that i have different outcomes when i try and coerce to int makes me think this is a python thing.

I think this is because I'm using a numpy array to store values in the p-table. numpy.int64 has a max of<PHONE_NUMBER>854775807, and in playing around with different values I get the Python int too large error as the max value of the p table approaches this value.
Fixed by using dtype = object rather than dtype = int? Need to ground-truth values against R implementation but I think this works. https://stackoverflow.com/questions/28552599/is-there-a-numpy-biginteger


fix(cdc-backfill): ensure snapshot read once for each epoch

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Inspired by https://github.com/risingwavelabs/risingwave/pull/12780
Will pick to main later.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Why does cdc backfill also encounter this issue? Upstream DB should not have tombstones

Or is there some other motivation?


how to deploy a cloud version

I have deployed a local neon version under the direction of the readme.md page and it runs very well,
but how can i deployed a cloud neon version ,so that i can start endpoints on different computers or manage storage on different machines. Is there any instruction pages or tools for this work?

@zhouqin try https://github.com/itsbalamurali/neon-operator for k8s

I found an related solution, but it is too old to be workable. https://github.com/neondatabase/neon/issues/2227
And @itsbalamurali solution seems lack enough instruction document for Neon beginners.
Is there any Neon contributors or someone who successfully deployed Neon in several nodes give us some instructions?

@zhouqin try https://github.com/itsbalamurali/neon-operator for k8s

Thanks!
I have tried this . The pods and svc startup successfully, and i can create tanent and timeline using the pageserer api.
but when i startup the computenode , something goes wrong. it seems the safekeepers don't work well.
ps. the env includes 1 pageserver, 2 safekeepers + 1 safe_broke
logfiles:
logs-from-compute-node-in-compute-node-0 (9).log
logs-from-pageserver-in-pageserver-0 (3).log
logs-from-pageserver-in-pageserver-0 (3).log
logs-from-safekeeper1-in-safekeeper1-0.log
so any ideas? thanks very much.

i have deploy neon in k8s successfully, with 3 compute nodes, 1 primary ,1 static and 1 replica. It can read and write data correctly. Two key points in the deployment:

the safekeeper:  the param ‘--listen-pg’ is for the pageserver to connect to pg in the safekeeper, so it cannot be '<IP_ADDRESS>.5454', user safekeeper's hostname instead, in the cluster.
in the compute node param, the spec must have the neon extension added, or the compute node will not extract the backup data correctly.
Next, I'll try the autoscaling component.

@zhouqin please feel free to create a P.R


Project does not get initialized upon creation

General Summary
When I create a new project, I wait for some time and the project name stays as Project Name Uninitialized and nothing else shows up on the workspace.
Steps to Reproduce

Create a new project.

Expected Result
The project should be open and ready to go.
Actual Result
I get a blank page with title Project Name Uninitalized.
The project does get created, as then after I restart the IDE it shows up in the project list and when I open it then all works good.
Enso Version
The build @farmaazon asked to test: https://discord.com/channels/401396655599124480/1071026796709023764/1071042817247432833 ran on Windows 11.
Logs:
PS C:\NBO\ide-builds> .\Enso.exe
PS C:\NBO\ide-builds>
Starting the backend process with the following options: []
Project Manager has been spawned, pid = 25256.
Starting the IDE service.
f [AsyncFunction: createServers]
Starting the IDE client.
[info] [2023-02-06T11:43:55.124Z] [org.enso.projectmanager.boot.ProjectManager$] Starting Project Manager...
Loading the window address http://localhost:8080?platform=win32&frame=true&theme=light&darkTheme=true&dataGathering=true&preferredEngineVersion=2023.1.1-dev&enableNewComponentBrowser=true&emitUserTimingMeasurements=undefined&nodeLabels=true&debug=false
Server started on port 8080.
Serving files from 'C:\NBO\ide-builds/C:\NBO\ide-builds\resources\app.asar'.
[info] [2023-02-06T11:43:55.378Z] [org.enso.projectmanager.boot.ProjectManager$] Started server at <IP_ADDRESS>:30535, press enter to kill server
[info] [2023-02-06T11:43:56.217Z] [org.enso.projectmanager.protocol.ClientController] Client connected to Project Manager [266de62a-9a67-4d0d-bfcc-ca16103d275d]
[info] [2023-02-06T11:43:58.924Z] [org.enso.projectmanager.infrastructure.log.Slf4jLogging] Created project with actual name [Unnamed_3].
[info] [2023-02-06T11:43:58.932Z] [org.enso.runtimeversionmanager.components.RuntimeVersionManager] The engine [2023.1.1-dev] found.
[info] [2023-02-06T11:43:59.025Z] [org.enso.runtimeversionmanager.components.RuntimeVersionManager] Found GraalVM runtime [GraalVM 22.3.0-java11].
[info] [2023-02-06T11:44:00.298Z] [org.enso.projectmanager.infrastructure.log.Slf4jLogging] Project created [Project(fb2747d6-313f-4106-bd3f-bad663c371b1,Unnamed_3,local,UserProject,2023-02-06T11:43:58.930261800Z,None,None,None,None)].
[info] [2023-02-06T11:44:00.35Z] [org.enso.runtimeversionmanager.components.RuntimeVersionManager] The engine [2023.1.1-dev] found.
[info] [2023-02-06T11:44:00.523Z] [org.enso.runtimeversionmanager.components.RuntimeVersionManager] Found GraalVM runtime [GraalVM 22.3.0-java11].
[info] [2023-02-06T11:44:00.526Z] [org.enso.projectmanager.infrastructure.languageserver.LanguageServerBootLoader] Booting a language server [LanguageServerDescriptor(language-server-fb2747d6-313f-4106-bd3f-bad663c371b1,8f035376-eee4-4bc6-ad19-32e8271aa78c,C:\Users\progr\enso\projects\Unnamed_3,NetworkConfig(<IP_ADDRESS>,49152,65535),org.enso.projectmanager.versionmanagement.DefaultDistributionConfiguration$@c312732,2023.1.1-dev,JVMSettings(None,List()),false,None,None,None,Future(Success(Some(ws://localhost:58728/))))].
[info] [2023-02-06T11:44:00.527Z] [org.enso.projectmanager.infrastructure.languageserver.LanguageServerBootLoader] Found sockets for the language server [json:<IP_ADDRESS>:56595, binary:<IP_ADDRESS>:60982].
[info] [2023-02-06T11:44:00.528Z] [org.enso.runtimeversionmanager.components.RuntimeVersionManager] The engine [2023.1.1-dev] found.
[info] [2023-02-06T11:44:00.694Z] [org.enso.runtimeversionmanager.components.RuntimeVersionManager] Found GraalVM runtime [GraalVM 22.3.0-java11].
[info] [2023-02-06T11:44:03.135Z] [org.enso.languageserver.boot.LanguageServerComponent] Starting Language Server...
[info] [2023-02-06T11:44:03.151Z] [org.enso.languageserver.boot.MainModule] Initializing main module of the Language Server from [LanguageServerConfig(<IP_ADDRESS>,56595,60982,8f035376-eee4-4bc6-ad19-32e8271aa78c,C:\Users\progr\enso\projects\Unnamed_3,ProfilingConfig(None,None,None),language-server,scala.concurrent.impl.ExecutionContextImpl$$anon$3@3a12c404[Running, parallelism = 20, size = 2, active = 1, running = 1, steals = 0, tasks = 0, submissions = 0]), info]
[info] [2023-02-06T11:44:06.024Z] [org.enso.languageserver.runtime.RuntimeConnector] Starting the runtime connector.
[info] [2023-02-06T11:44:06.024Z] [org.enso.languageserver.runtime.RuntimeConnector] Runtime connector established connection with the message endpoint [com.oracle.truffle.api.instrumentation.TruffleInstrument$Env$MessageTransportProxy$MessageEndpointProxy@251a20db].
[info] [2023-02-06T11:44:06.264Z] [org.enso.languageserver.text.BufferRegistry] Starting initialization.
[info] [2023-02-06T11:44:06.287Z] [org.enso.languageserver.search.SuggestionsHandler] Starting suggestions handler from [Config(projectContentRoot=***\Unnamed_3, fileManager=FileManagerConfig(3 seconds,20), vcsManager=VcsManagerConfig(5 seconds,3 seconds), pathWatcher=PathWatcherConfig(5 seconds,5 seconds,10), executionContext=ExecutionContextConfig(5 seconds), directories=DirectoriesConfig(***\Unnamed_3)), org.enso.searcher.sql.SqlSuggestionsRepo@229d9d9, org.enso.searcher.sql.SqlVersionsRepo@5ddf1c3d].
[info] [2023-02-06T11:44:07.155Z] [org.enso.languageserver.boot.MainModule] Main module of the Language Server initialized with config [Config(projectContentRoot=***\Unnamed_3, fileManager=FileManagerConfig(3 seconds,20), vcsManager=VcsManagerConfig(5 seconds,3 seconds), pathWatcher=PathWatcherConfig(5 seconds,5 seconds,10), executionContext=ExecutionContextConfig(5 seconds), directories=DirectoriesConfig(***\Unnamed_3))].
[info] [2023-02-06T11:44:07.258Z] [org.enso.languageserver.boot.LanguageServerComponent] Started server at json:<IP_ADDRESS>:56595, binary:<IP_ADDRESS>:60982
[info] [2023-02-06T11:44:07.775Z] [org.enso.projectmanager.infrastructure.languageserver.LanguageServerBootLoader] Language server booted [LanguageServerConnectionInfo(<IP_ADDRESS>,56595,60982)].
[info] [2023-02-06T11:44:07.863Z] [org.enso.languageserver.protocol.json.JsonConnectionController] Initializing resources.
[info] [2023-02-06T11:44:07.866Z] [org.enso.languageserver.boot.resource.DirectoriesInitialization] Initializing directories...
[info] [2023-02-06T11:44:07.867Z] [org.enso.languageserver.boot.resource.DirectoriesInitialization] Initialized directories.
[info] [2023-02-06T11:44:07.869Z] [org.enso.languageserver.boot.resource.RepoInitialization] Initializing suggestions repo [***\suggestions.db]...
[info] [2023-02-06T11:44:08.307Z] [org.enso.languageserver.boot.resource.RepoInitialization] Initialized Suggestions repo [***\suggestions.db].
[info] [2023-02-06T11:44:08.311Z] [org.enso.languageserver.boot.resource.RepoInitialization] Initializing versions repo [***\suggestions.db]...
[info] [2023-02-06T11:44:08.315Z] [org.enso.languageserver.search.SuggestionsHandler] Initializing: suggestions repo initialized.
[info] [2023-02-06T11:44:08.329Z] [org.enso.languageserver.boot.resource.RepoInitialization] Initialized Versions repo [***\suggestions.db].
[info] [2023-02-06T11:44:08.33Z] [org.enso.languageserver.boot.resource.TruffleContextInitialization] Initializing Runtime context...
[info] [2023-02-06T11:44:08.329Z] [org.enso.languageserver.text.BufferRegistry] Initiaized.
[info] [2023-02-06T11:44:10.578Z] [org.enso.languageserver.boot.resource.TruffleContextInitialization] Initialized Runtime context.
[info] [2023-02-06T11:44:10.578Z] [org.enso.languageserver.search.SuggestionsHandler] Initializing: Truffle context initialized.
[info] [2023-02-06T11:44:10.578Z] [org.enso.languageserver.protocol.json.JsonConnectionController] RPC session initialized for client [475854dd-5784-49d8-9c51-9d380835e76e].
[info] [2023-02-06T11:44:10.616Z] [org.enso.languageserver.protocol.binary.BinaryConnectionController] Data session initialized for client: 475854dd-5784-49d8-9c51-9d380835e76e [<IP_ADDRESS>:58755].
[info] [2023-02-06T11:44:10.64Z] [org.enso.languageserver.search.SuggestionsHandler] Initializing: project name is updated to [Unnamed_3].
[info] [2023-02-06T11:44:10.88Z] [org.enso.languageserver.search.SuggestionsHandler] Initializing: got type graph response.
[info] [2023-02-06T11:44:10.961Z] [org.enso.languageserver.search.SuggestionsHandler] Verifying: got verification response.
[info] [2023-02-06T11:44:11.008Z] [org.enso.languageserver.search.SuggestionsHandler] Verified.
[info] [2023-02-06T11:44:11.232Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/2#1057908470] was not delivered. [1] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/2#1057908470] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:11.902Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/3#-1988330107] was not delivered. [2] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/3#-1988330107] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:12.511Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/4#-1077848877] was not delivered. [3] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/4#-1077848877] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:13.162Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/5#-1438819204] was not delivered. [4] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/5#-1438819204] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:13.787Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/6#-1946285699] was not delivered. [5] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/6#-1946285699] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:14.423Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/7#800711399] was not delivered. [6] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/7#800711399] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:15.064Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/8#-937845441] was not delivered. [7] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/8#-937845441] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:15.704Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/9#374658973] was not delivered. [8] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/9#374658973] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[info] [2023-02-06T11:44:16.343Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/10#-2056583514] was not delivered. [9] dead letters encountered. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/10#-2056583514] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[error] [2023-02-06T11:44:16.346Z] [org.enso.languageserver.requesthandler.vcs.InitVcsHandler] Initialize project request [Number(2)] for [475854dd-5784-49d8-9c51-9d380835e76e] failed with: null.
[info] [2023-02-06T11:44:16.368Z] [org.enso.languageserver.protocol.binary.BinaryConnectionController] Connection closed [<IP_ADDRESS>:58755].
[info] [2023-02-06T11:44:16.982Z] [akka.actor.LocalActorRef] Message [akka.actor.ReceiveTimeout$] to Actor[akka://project-manager/system/IO-TCP/selectors/$a/11#1748993265] was not delivered. [10] dead letters encountered, no more dead letters will be logged in next [5.000 min]. If this is not an expected behavior then Actor[akka://project-manager/system/IO-TCP/selectors/$a/11#1748993265] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[1732:0206/124555.170:ERROR:gpu_init.cc(521)] Passthrough is not supported, GL is disabled, ANGLE is
[info] [2023-02-06T11:47:35.592Z] [org.enso.projectmanager.protocol.ClientController] Client disconnected from the Project Manager [266de62a-9a67-4d0d-bfcc-ca16103d275d]
[info] [2023-02-06T11:47:35.595Z] [org.enso.languageserver.runtime.RuntimeKiller] Shutting down the runtime server [Actor[akka://language-server/user/runtime-connector#-1709079040]].
[error] [2023-02-06T11:47:35.599Z] [org.enso.projectmanager.boot.ProjectManager$] Main process execution failed.
[internal-logger-error] Server has disconnected, logging is falling back to stderr.
[info] [2023-02-06T11:47:35.721Z] [org.enso.languageserver.boot.LanguageServerComponent] Terminated truffle context
[info] [2023-02-06T11:47:35.73Z] [org.enso.languageserver.boot.LanguageServerComponent] Terminated json connections
[info] [2023-02-06T11:47:35.731Z] [org.enso.languageserver.boot.LanguageServerComponent] Terminated binary connections
[info] [2023-02-06T11:47:35.744Z] [akka.actor.CoordinatedShutdown] Running CoordinatedShutdown with reason [ActorSystemTerminateReason]
[info] [2023-02-06T11:47:35.785Z] [org.enso.languageserver.boot.LanguageServerComponent] Terminated actor system
[info] [2023-02-06T11:47:35.787Z] [org.enso.languageserver.boot.MainModule] Closed Language Server main module.
[info] [2023-02-06T11:47:35.787Z] [org.enso.languageserver.boot.LanguageServerComponent] Terminated main module

Not re-producible on the current IDE build within Windows so closing for now.


Fix integration tests for Shared Bridge PR

The current shared bridge PR has a lot of integration tests failing. They need to be fixed

Closing as it's a duplicate of #106


Update hyperspectral to support new VNIR camera bands

Between 2017-2018, VNIR camera was replaced. New camera has 939 bands instead of 955, and this is breaking the extractor code for currently unknown reason. May be related to incompatible calibration file or template designed for older camera.
hyperspectral_workflow.sh -d 1 -h --new_clb_mth -i /home/extractor/sites/ua-mac/raw_data/VNIR/2018-08-18/2018-08-18__11-47-47-403/aabc02a5-2fe1-4fdd-b26f-b87bf50c24fe_raw -o /home/extractor/sites/ua-mac/Level_1/vnir_netcdf/2018-08-18/2018-08-18__11-47-47-403/vnir_netcdf_L1_ua-mac_2018-08-18__11-47-47-403.nc

nco_err_exit(): ERROR Error code is -57. Translation into English with nc_strerror(-57) is "NetCDF: Start+count exceeds dimension bound"
ERROR: nco_put_vara() failed to nc_put_vara() variable "cst_cnv_trg_nw"

Will try to update more on error message later

@remotesensinglab and I noticed this issue during the development of the new calibration protocol. I opened the cst_cnt_trg.nc files, it is indeed containing 955 bands (389-1000nm) since it was developed for old VNIR data. See the screenshot below:

The easiest way, but may not a good one, to fix this issue could be - keep the dimension of variables to 939 by discarding 17 values.  Note the new VNIR contains 939 spectral bands ranging from 399 - 1000nm.

it would only make sense to discard the 17 values if these are additional, and the other 939 are the same wavelengths as the old sensor

The new VNIR sensor has 939 bands with the wavelength ranging from 399.98 nm ~ 1000.62 nm, and the old one has 955 bands ranging from 389.41 nm ~ 1000.25 nm.

@Paheding david mentioned you had provided an update about this on Monday, is there any code/pullrequest/summary you can provide here? thanks.

The hackathons resulted in changes I implemented here:
https://github.com/terraref/extractors-hyperspectral/pull/50
Support VNIR new camera bands, as well as SWIR. Required generating some 939-band versions of some calibration files for VNIR, and avoiding the affected code for SWIR (which has no calibration).
Patrick and team have calibration code we can run on new VNIR data once it's generated, and SWIR is also queued.

@max-zilla Great! Does this new update incorporate the shell script "if statement" we sent last time, as well as environmental loggar issues included in the netCDF?  Thanks.


Issue with google login

When logging into d&d beyond with a google auth the app simply goes to the dnd beyond homepage without fetching the cobalt token. This forces users to logout and re-login using a different auth method.

I cannot definitively say this is closed, but after RC1 and the updated fixes I applied to the token detection I am unable to reproduce this. I will be leaving this bug open and if no one else can reproduce it then I will close it.


[Docs][GLib] Placeholder front pages created by Sphinx is still used

Describe the bug, including details regarding any error messages, version, and platform.
GH-40442 introduced front pages for Apache Arrow GLib related API references. They are just placeholder that should be replaced by front pages generated by these API references. But these front pages are still used in the dev docs:
https://arrow.apache.org/docs/dev/c_glib/arrow-glib/
Component(s)
Documentation, GLib

Issue resolved by pull request 40618
https://github.com/apache/arrow/pull/40618


FDG-6089 Deficit Explainer - Glossary term missing for fiscal Year

https://federal-spending-transparency.atlassian.net/browse/FDG-6089

Changes made and Glossary Terms come up on Fiscal Year. All Test passed.


xfce.tumbler, xfce.ristretto: enable JXL and WebP support

Description of changes
Follow up for #340364.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 340472 run on x86_64-linux 1

4 packages built:

xfce.ristretto
xfce.ristretto.dev
xfce.tumbler
xfce.tumbler.dev

other programs might show inaccurate colors (e.g. GIMP with https://jpeg.org/images/jpegxl-home.jxl)

My jxlinfo jpegxl-home.jxl run shows Color space: RGB, D65, Rec.2100 primaries, PQ transfer function, rendering intent: Perceptual instead of ... sRGB primaries .... so my quick guess is if you are using the GIMP built in sRGB color profile it can likely show different colors :thinking:


clean classification records from keywords.

Often, authors set the classification in the keywords field. These classifications should be allocated correctly.
The importer should check, if a keyword starts with some numeric (\d+\.?\d?) followed by a colon and then followed by some characters.
If such string is found in a classification is found in the keywords, it should be removed from the keywords and inserted as classification.

This is moved into a separate service


Include verbosity in calls to custom LogSinks

Currently calls to VLOG(n) map to LOG(INFO).
I would like to map the verbosity in my custom log sink.
So that the impementing class would be aware if LOG(INFO), or VLOG(n) was used and which number n was.
One way would be to add the verbosity as argument to LogSink::send, and LogSink::toString.
static std::string ToString(LogSeverity severity, const char* file, int line,
                              const struct ::tm* tm_time,
                              const char* message, size_t message_len);

would become
static std::string ToString(LogSeverity severity, int verbosity, const char* file, int line,
                              const struct ::tm* tm_time,
                              const char* message, size_t message_len);

LogSink::send would change accordingly.
Since this would break an existing interface, it could be implement as overload.
Please tell me your opionion. If its ok, I would create a PR.

I also would love to be able to have verbosity levels to be reflected in the long sink.

@sergiud Does this mean that this feature won't be implemented, or was it implemented in some commit not linked here? Thanks.


German Update

Updated Pagos Mob Names (didn't see they were there in the first place), did some wording-tweaks in a few triggers and updated what was there to update :>

Thanks as always!


User-defined root finding algorithm in {Field}ODEEventDetector

Prior to the implementation of #223 it was possible to define a custom root finding algorithm for each event via {Field}ODEIntegrator#addEventHandler().
Would be possible to preserve this functionality, for example by adding a getSolver() method to the new ODEEventDetector interface?

There is a redundancy problem with getThreshold in the ODEEventDetector interface and withThreshold in the AbstractODEDetector base class (and the corresponding field variants).
From an event detection point of view, the threshold is related to the event itself, as various events accuracy depend on their meaning. From a solver point of view, the threshold depends on the solver.
If user specifies a solver and specifies a threshold separately, how do we handle that?

Is this need for a solver related to #220?
If #220 is solved without allowing user to specify a custom solver, would this suit your needs?

No, this is related to an old question on the forum: https://forum.orekit.org/t/extract-second-to-last-spacecraftstate-after-event-triggering/1165?u=alberto
I have an event whose g function only returns -1/+1, and is quite expensive to evaluate. At the same time, I am not interested in accurately locating the event, but just stop the integration at the step in which the function switches sign. My workaround was to pass a solver to addEventHandler() that literally does nothing, so that the refinement of the event location stops immediately.
I am open to other options to achieve this, my only constraint is to evaluate the g() function only once per step.
Regarding the first question, the redundancy was already present before the last changes. One option would be let the user to specify either the threshold or the solver, and building a default solver if the user chooses to input the threshold.

Yes the redundancy was present and it was not managed properly.
What happens if you put a maxCheckInterval larger than the largest possible step et a convergence threshold also larger than the largest possible step?
I guess this could drastically reduce the number of calls to the g function, but I also guess the minimum number of evaluations will be 3, which may not suit your needs.
The settings of the numerous parameters in event detectors has been intentionally split in several calls (hence the withXxxxmethods and fluent API) because some detectors were really cumbersome with an ever increasing number of optional parameters. I remember a family of detectors that were merged together and ended up with a dozen different constructors before we switched to the current design.
Perhaps we could assume that the last call to withSolver overrides previous calls to withThreshold and also the other way round, with proper documentation so users refrain from using both, or at least are aware that if they use both settings, the first one will be overridden. This way, the last call would be the only relevant one.

With maxCheckInterval and threshold larger than the largest integrator step and a maxIterationCount strictly greater than 1 it misses the root.
If I set maxIterationCount to 0 or 1, I get the following exception:
Exception in thread "main" org.hipparchus.exception.MathIllegalStateException: ... failed to find root between 61,237.988 (g=-1.0E0) and 62,339.789 (g=1.0E0)
Last iteration at 61,788.889 (g=1.0E0)
	at org.hipparchus.ode.events.FieldEventState.findRoot(FieldEventState.java:384)
	at org.hipparchus.ode.events.FieldEventState.tryAdvance(FieldEventState.java:478)
	at org.hipparchus.ode.AbstractFieldIntegrator.acceptStep(AbstractFieldIntegrator.java:405)
	at org.hipparchus.ode.nonstiff.EmbeddedRungeKuttaFieldIntegrator.integrate(EmbeddedRungeKuttaFieldIntegrator.java:309)
	...
Caused by: org.hipparchus.exception.MathIllegalStateException: maximal count (1) exceeded
	at org.hipparchus.util.Incrementor.lambda$static$0(Incrementor.java:41)
	at org.hipparchus.util.Incrementor.increment(Incrementor.java:237)
	at org.hipparchus.analysis.solvers.FieldBracketingNthOrderBrentSolver.solveInterval(FieldBracketingNthOrderBrentSolver.java:240)
	at org.hipparchus.analysis.solvers.BracketedRealFieldUnivariateSolver.solveInterval(BracketedRealFieldUnivariateSolver.java:177)
	at org.hipparchus.ode.events.FieldEventState.findRoot(FieldEventState.java:373)
	... 7 more

I found a workaround for this:
ODEEventDetector side (assuming forward integration):

g() evaluates to either +1 or -1 (the expensive evaluation) if it is called at time t greater than the last two times at which it has been called. This ensures we are actually in a new integration step.
g() returns immediately 0 if it is called at a time t such that t1 < t < t2, with t1 and t2 last two times at which it has been evaluated. This corresponds to a function call within the root refinement machinery.
maxCheckInterval and tolerance are set to plus infinity
maxIterationCount is set to 1

ODEStepHandler side:
I am logging the output of interpolator.getPreviousState() only if this state is not interpolated, to ensure I am not storing states that correspond to intermediate times (within two integrator steps) computed by the root finding algorithm.
In this way, I evaluate g() and store the "previous state" exactly once per step, without the need of a custom root finding algorithm.

Ok, thank you.

Please, tell me if the API suits you. It adds a withSolver method to event detectors (both double and field).

Yes, this works for me. Thanks again.


An "es6-tutorial" branch needs to be created.

The files tutorial_0.html, etc., are not available for es6.

The instructions in the es-6 branch are pretty confusing, there's no actual tutorials (That I can find) in the es-6 branch.  However the readme states there should be.

At least need to remove the link to a non existing branch. Get a (on development) message or something. Really confusing

Fixed - https://github.com/angular/material-start/blob/es6/README.md

The README in the master branch still has a link to es6 tutorial branch.
Branch Starter - ES6 Tutorials: for ES6 Tutorial steps & development process.

It would be good to fix that and put a note as to whether tehre's any intention towards producing an es6 tutorial branch.
Thank you.

Done - https://github.com/angular/material-start/blob/master/README.md

Awesome, thank you


I can delete the organazition which related to an application

If i have an application which organizition is A . I can delete A directly. After do this,  when I edit the application , it will error.

@hsluoyz I will solve this as soon as possible.
when I delete the organiziton, should I remind the user if there are some applications related to this organizition and delete the applications together？

Record applications in the org, do right CRUD, make them consistent.
For UI, gray out the button for orgs with non-empty apps.

@hsluoyz "Record applications in the org, do right CRUD, make them consistent." is the  mean that "add a field to the organization table in database to record the apps of each org"?

Yes, add Applications []string as a field to org. Remember to update this field in Go backend when app side is updated like app's org update, app rename, app delete.


example for resources in config file

What is missing from the application? Please describe.
The example config file has an empty "resources": [].  It's not obvious what to do with that...list out the folders I want to copy?
Describe the solution you'd like
It turns out that the elements in that array are supposed to be formatted { "from": "x", "to": "y"}
Describe alternatives you've considered
I had to dig into the code in the your webpack config generation to figure out the from/to thing.  Also considered learning webpack but am avoiding that.

Good find. Will update the example.
In the sample app that you create via lwc-create-app is also an lwc-services.config.js file with a value for that populated.

ahh...was working on migrating an existing project and didn't have the luxury of starting from a new project.  That's a whole valid path

Fixed via #46


LaTeX + Plain Text support + Colours

Changes

Add rendering of LaTeX text. This is done by sending a POST request to an external API (basically a Pandoc wrapper), which responds with the HTML. Given that Pandoc supports conversion of Markdown to HTML as well, I've updated the rendering of Markdown to use a similar implementation. There's also a slight delay introduced between each requests. As such, the rendering may not be instantaneous.

Note: the support for LaTeX is quite limited. Some commands are not supported, and would fail silently. Comments using % are not supported as well. For invalid syntax, the WebView would display an error instead

Remove external dependency on Ink (previously used for its Markdown parser)
Add a bunch of different colours that can be used throughout the application
Add plaintext support

I have some concerns over being able to switch between the various markup languages and plaintext freely as I don't think it makes too much sense to be able to do so. I feel that whether the text block is plaintext/markdown/LaTeX/code should be decided at the point of creation. This can be handled through the use of context menus which I feel will be more intuitive to the user. See #6 for an example of what I mean.

Sure, I'll remove it!

Closing in favour of #7


Fix code for data frame to handle null values for infusate and tracer names

BUG DESCRIPTION
Based on current database specifications, infusate.name and tracer.name allow null values. The dataframe code used for study list and animal list would  have errors if some values are null.
Problem
The root problem is due to group by "name" field. Pandas would return an empty dataframe if the field contained null values.  PR576 modified some data frame code but didn't address root cause.
Steps to reproduce
Will link to a test case later
Current behavior
Expected behavior
Although infusate.name and tracer.name should be not null with normal data loading, but the code should handle null values based on current spec. and allow tests with different settings (e.g. enable_buffering or disable_buffering).
Suggested Change
The code for infusate related data frames need to join id and name fields first and then run "groupby".
Comment

ISSUE OWNER SECTION
Assumptions

List of assumptions made WRT the code
E.g. We will assume input is correct (explaining why there is no validation)

Requirements

[ ] 1. List of numbered conditions to be met for the feature
[ ] 2. E.g. Every column/row must display a value, i.e. cannot be empty
[ ] 3. Numbers for reference & checkboxes for progress tracking

Limitations

A list of things this work will specifically not do
E.g. This feature will only handle the most frequent use case X

Affected Components
A list of repository items, dependencies, etc, labeled with add, delete, or
change.  One item per line.  (Mostly, this will be a list of files.)

change: File path or DB table ...
add: Environment variable or server setting
delete: External executable or cron job

DESIGN
GUI Change description
Describe changes the user will see.
Code Change Description
Describe code changes planned for the feature. (Pseudocode encouraged)
Tests

[ ] 1. A description of at least one test for each requirement above.
[ ] 2. E.g. Test for req 2 that there's an exception when display value is ''
[ ] 3. Numbers for reference & checkboxes for progress tracking

👍


Separate statement metrics by database

https://cockroachlabs.atlassian.net/browse/CRDB-396
@taroface @awoods187
This roadmap item is on the SQL JIRA board, but I think it's more relevant to admin UI docs rather than SQL docs.

Adding this comment from the other issue:

Well let's talk about this in our meeting. These are definitely a part of the SQL Product Area even if they touch the webui so we'd definitely need to track them in this project. However, if they should be done by another writer who works with the UI, then we can assign it to that writer but keep it in this project. Let's talk more about it.

@ericharmeling, it's ok that multiple writers will start touching UI docs. This is similar to CC, where writers are contributing to docs depending on the product area. Let's have you try documenting UI changes coming from your area. You can discuss and coordinate with @taroface.

@awoods187
The JIRA epic for this (https://cockroachlabs.atlassian.net/browse/CRDB-396) has the feature marked a "In review/testing". Is this feature complete for v20.2? I haven't seen any docs release note issues for it.

This didn't make it into 20.2. In Jira, I asked @solongordon  to update us on the status of the backend.

Moving this to the Later milestone. We can pull it into 21.1 if relevant.

The JIRA epic is marked as "not started", so I'm assuming this have been descoped.


[vk] Migrate ash structs to builders

I didn't call builder methods for values that were clearly being set to their defaults in the struct. I did leave e.g. calls to *Flags::empty() and other non-obvious defaults, as well as any values that were default but marked as TODO.
PR checklist:

[ ] make succeeds (on *nix)

WSL doesn't have graphics drivers.

[x] make reftests succeeds

I don't have make on Windows, so I manually ran cd src/warden && cargo run --bin reftest --features vulkan -- local

[x] tested examples with the following backends: vulkan

Except mesh-shading (I didn't have that feature).

what is the motivation for doing this?

I'm attempting to add OpenXR support to the Vulkan backend (#3219), and I'm currently running into a problem at the top of Instance::enumerate_adapters where the OpenXR runtime is returning an RUNTIME_FAILURE error in the integration, but doesn't in the supposedly-equivalent code in the openxr crate's Vulkan example. I made these changes to gfx_backend_vulkan::Instance::create to reduce the differences between the two codebases (to make it easier to hunt down the issue).
I figured that the changes might be independently of interest, since I saw some existing places that gfx-backend-vulkan is using the ash builders (added in the last few months IIRC), and assumed that the reason for not using them was that they didn't exist three years ago when most of the code I touched was written. I don't have any particular motivation to get these changes merged; take what makes sense 🙂

Ok, I want to hear out if other members have opinions on this. Otherwise, we'll proceed (let's say, tomorrow)

Ooh, interesting development: my OpenXR diff crashes when based on master, but does not crash when rebased on this branch. So there's maybe an actual bug being fixed by this PR...

@kvark using the builders sounds alright to me :+1: I don't have much of a preference either way since the trade-offs seem pretty minor


orchestrator: a new option for enabling/disabling orchestration initi…

…ally

Coverage increased (+0.08%) to 40.288% when pulling 42a4093a4c72ffc97d057347261ddf5b7158c3a0 on mitake:init-disable into 685bd1d2819490485ce8468809da9a5ef388f2d5 on osrg:master.

Coverage increased (+0.07%) to 40.275% when pulling 42a4093a4c72ffc97d057347261ddf5b7158c3a0 on mitake:init-disable into 685bd1d2819490485ce8468809da9a5ef388f2d5 on osrg:master.

@AkihiroSuda updated the name to skipInitOrchestrator, PTAL

Coverage increased (+0.07%) to 40.256% when pulling a080fdd8dc0486c150124214a3d3a3fe1e1badf3 on mitake:init-disable into 96fdb0ef5f03ec88e94bc0352ae9254752a5b27d on osrg:master.

lgtm
please rebase and merge?

Coverage decreased (-0.0002%) to 40.144% when pulling 5f6a9fa7a0e09a2a4874dd3e22afef55033c24b4 on mitake:init-disable into 4c0fe664827aadbe55bc20067934ac3330f87ed8 on osrg:master.

@AkihiroSuda thanks, merged


CameraX Basic - Task is rejected from java.util.concurrent.ThreadPoolExecutor(RejectedExecutionException))

Hi,
I have installed CameraXBasic without any modification on my phone (Galaxy J8).
I got this issue by following these steps:

Open the app
Take some pictures(press on the take picture button several times)
Click on the preview button to navigate to the preview fragment
Back to the camera fragment and click on the take picture button again
-> I got the issue

I'm wondering if we should recreate cameraExecutor again, because we already cameraExecutor.shutdown() onDestroyView().
Could you please tell me? Thank you very much
Here the logcat is:
E/AndroidRuntime: FATAL EXCEPTION: CameraX-camerax_io_1     Process: com.android.example.cameraxbasic, PID: 26019     java.util.concurrent.RejectedExecutionException: Task androidx.camera.core.-$$Lambda$ImageSaver$S9mrYGMPcUwPIjUa0oK9HMzbx_o@5538a64 rejected from java.util.concurrent.ThreadPoolExecutor@5c03f59[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 188]         at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2085)         at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:848)         at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1394)         at java.util.concurrent.Executors$DelegatedExecutorService.execute(Executors.java:631)         at androidx.camera.core.ImageSaver.postSuccess(ImageSaver.java:240)         at androidx.camera.core.ImageSaver.run(ImageSaver.java:182)         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)         at java.lang.Thread.run(Thread.java:764)

Fixed with #182


Parallel inserts cause increased latency

Hi, I'm using the latest client version to test the performance of bulk inserts. When using multi-threaded insertion, it is found that the response time becomes longer and most threads hang
The test conditions are as follows:
Batch size: 50000 records
Number of threads: 10
"pool-2-thread-8" #21 prio=5 os_prio=31 tid=0x00007fea6d018800 nid=0x9903 runnable [0x000070000fe50000]
   java.lang.Thread.State: RUNNABLE
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
	at java.io.BufferedOutputStream.write(BufferedOutputStream.java:122)
	- locked <0x000000077ac78e48> (a java.io.BufferedOutputStream)
	at java.io.PrintStream.write(PrintStream.java:480)
	- locked <0x000000077ac78e60> (a java.io.PrintStream)
	at sun.net.www.http.ChunkedOutputStream.flush(ChunkedOutputStream.java:145)
	at sun.net.www.http.ChunkedOutputStream.write(ChunkedOutputStream.java:237)
	- locked <0x000000077ac78e80> (a sun.net.www.http.ChunkedOutputStream)
	at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3586)
	at com.clickhouse.client.stream.WrappedOutputStream.flushBuffer(WrappedOutputStream.java:19)
	at com.clickhouse.client.stream.AbstractByteArrayOutputStream.transferBytes(AbstractByteArrayOutputStream.java:43)
	at com.clickhouse.client.stream.AbstractByteBufferInputStream.pipe(AbstractByteBufferInputStream.java:90)
	at com.clickhouse.client.ClickHouseInputStream.pipe(ClickHouseInputStream.java:424)
	at com.clickhouse.client.http.HttpUrlConnectionImpl.post(HttpUrlConnectionImpl.java:284)
	at com.clickhouse.client.http.ClickHouseHttpClient.send(ClickHouseHttpClient.java:123)
	at com.clickhouse.client.AbstractClient.execute(AbstractClient.java:296)
	at com.clickhouse.client.ClickHouseClientBuilder$Agent.sendOnce(ClickHouseClientBuilder.java:284)
	at com.clickhouse.client.ClickHouseClientBuilder$Agent.send(ClickHouseClientBuilder.java:296)
	at com.clickhouse.client.ClickHouseClientBuilder$Agent.execute(ClickHouseClientBuilder.java:351)
	at com.clickhouse.client.ClickHouseClient.executeAndWait(ClickHouseClient.java:824)
	at com.clickhouse.client.ClickHouseRequest$Mutation.executeAndWait(ClickHouseRequest.java:288)
	at com.clickhouse.client.ClickHouseRequest$Mutation.sendAndWait(ClickHouseRequest.java:314)
	at com.clickhouse.jdbc.internal.ClickHouseStatementImpl.executeInsert(ClickHouseStatementImpl.java:177)
	at com.clickhouse.jdbc.internal.InputBasedPreparedStatement.executeAny(InputBasedPreparedStatement.java:117)
	at com.clickhouse.jdbc.internal.AbstractPreparedStatement.executeLargeBatch(AbstractPreparedStatement.java:85)
	at com.clickhouse.jdbc.internal.ClickHouseStatementImpl.executeBatch(ClickHouseStatementImpl.java:568)

"pool-2-thread-9" #22 prio=5 os_prio=31 tid=0x00007fea6d019000 nid=0x9703 runnable [0x000070000ff53000]
   java.lang.Thread.State: RUNNABLE
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
	at java.io.BufferedOutputStream.write(BufferedOutputStream.java:122)
	- locked <0x000000077ac5fd80> (a java.io.BufferedOutputStream)
	at java.io.PrintStream.write(PrintStream.java:480)
	- locked <0x000000077ac5fd98> (a java.io.PrintStream)
	at sun.net.www.http.ChunkedOutputStream.flush(ChunkedOutputStream.java:145)
	at sun.net.www.http.ChunkedOutputStream.write(ChunkedOutputStream.java:237)
	- locked <0x00000007722a8110> (a sun.net.www.http.ChunkedOutputStream)
	at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3586)
	at com.clickhouse.client.stream.WrappedOutputStream.flushBuffer(WrappedOutputStream.java:19)
	at com.clickhouse.client.stream.AbstractByteArrayOutputStream.transferBytes(AbstractByteArrayOutputStream.java:43)
	at com.clickhouse.client.stream.AbstractByteBufferInputStream.pipe(AbstractByteBufferInputStream.java:90)
	at com.clickhouse.client.ClickHouseInputStream.pipe(ClickHouseInputStream.java:424)
	at com.clickhouse.client.http.HttpUrlConnectionImpl.post(HttpUrlConnectionImpl.java:284)
	at com.clickhouse.client.http.ClickHouseHttpClient.send(ClickHouseHttpClient.java:123)

Hi @rrsunhome, thanks for sharing the test results. What's the expectation? Same or even lower latency compare to single thread? Have you tried async insert and/or adjust server threads?
Looking at the stack trace, it seems there's waits for writing. Did you check server status?

你好@rrsunhome，感谢分享测试结果。期望是什么？与单线程相比，延迟相同甚至更低？您是否尝试过异步插入和/或调整服务器线程？
查看堆栈跟踪，似乎等待写入。你检查服务器状态了吗？

Thank you for your reply
The expectation is the same as the single-thread insertion delay
The cpu usage of the server is very high, and the high latency should be caused by this


Added UGIM to account chat filter

Not my plugin, pushed to the original plugin repo but was never pushed to the actual plugin hub.

@MrSableye seems to be active on Github, did you attempt to ask them to update the plugin with your changes?

Looks good to me, change was made a while back but I forgot to submit it here


chore: update jest and jest-config

Summary
This merge request updates jest, the jest-config file and the report paths for SonarQube. This is neccessairy to report the jest test results correctly so that they can be scanned and displayed by sonarQube.

Looks good to me! Did you test the sonarqube-pipeline already?

Thank you! Yes, the sonarqube-pipeline was tested already and does report the coverage correctly now:


Error checking seems to have stopped working

When I code in Python the error checking seems to have stopped working it seems to have been working before the update before the last update and it is really annoying. I would like it to be fixed so it can check for errors again and i have linting turned on for auto save.
python.linting.enabled | Whether to lint Python files. | true
python.linting.pylintEnabled | Whether to lint Python files using pylint. | true
python.linting.lintOnSave | Whether to lint Python files when saved. | true

Please add the following setting into your settings.json (user or workspace settings):
"python.linting.pylintUseMinimalCheckers": false

You can read more about this here https://code.visualstudio.com/docs/python/linting#_default-pylint-rules

that did not seem to work hmm I'm just gonna reinstall vscode

still no working

You do not have the extension running (you would have the interpreter specified in the status bar; did you happen to forget to install it again after the re-install?).  If it's installed and still not working then please ask for help on Stack Overflow.

the extension got reinstalled when i reinstalled vscode and it is enabled

I got error checking to work again It turns out the installation of the ext. was corrupted.