ModuleNotFoundError: No module named 'diff_gaussian_rasterization'

Got stuck at this error in google colab.
Last part of the log is:
Sampling: 100% 12/12 [00:08<00:00,  1.37it/s]
Sampling: 100% 12/12 [00:25<00:00,  2.10s/it]
Rendering: 0it [00:00, ?it/s]
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/gradio/queueing.py", line 536, in process_events
response = await route_utils.call_process_api(
File "/usr/local/lib/python3.10/site-packages/gradio/route_utils.py", line 322, in call_process_api
output = await app.get_blocks().process_api(
File "/usr/local/lib/python3.10/site-packages/gradio/blocks.py", line 1935, in process_api
result = await self.call_function(
File "/usr/local/lib/python3.10/site-packages/gradio/blocks.py", line 1520, in call_function
prediction = await anyio.to_thread.run_sync(  # type: ignore
File "/usr/local/lib/python3.10/site-packages/anyio/to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 2505, in run_sync_in_worker_thread
return await future
File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 1005, in run
result = context.run(func, *args)
File "/usr/local/lib/python3.10/site-packages/gradio/utils.py", line 826, in wrapper
response = f(*args, **kwargs)
File "/content/TRELLIS/app.py", line 115, in image_to_3d
video = render_utils.render_video(outputs['gaussian'][0], num_frames=120)['color']
File "/content/TRELLIS/trellis/utils/render_utils.py", line 96, in render_video
return render_frames(sample, extrinsics, intrinsics, {'resolution': resolution, 'bg_color': bg_color}, **kwargs)
File "/content/TRELLIS/trellis/utils/render_utils.py", line 73, in render_frames
res = renderer.render(sample, extr, intr, colors_overwrite=colors_overwrite)
File "/content/TRELLIS/trellis/renderers/gaussian_render.py", line 223, in render
render_ret = render(camera_dict, gausssian, self.pipe, self.bg_color, override_color=colors_overwrite, scaling_modifier=self.pipe.scale_modifier)
File "/content/TRELLIS/trellis/renderers/gaussian_render.py", line 58, in render
from diff_gaussian_rasterization import GaussianRasterizer, GaussianRasterizationSettings
ModuleNotFoundError: No module named 'diff_gaussian_rasterization'

You can refer to https://github.com/microsoft/TRELLIS/issues/12

run these commands:
find / -name 'diff-gaussian-rasterization'  to find which folder has these two diff-gaussian-rasterization and simple-knn
cd tmp/extensions/mip-splatting/submodules (this is the location i had both of the submodules)
pip install diff-gaussian-rasterization simple-knn

run these commands:
find / -name 'diff-gaussian-rasterization'  to find which folder has these two diff-gaussian-rasterization and simple-knn
cd tmp/extensions/mip-splatting/submodules (this is the location i had both of the submodules)
pip install diff-gaussian-rasterization simple-knn

Already tried, I get:
ERROR: Could not find a version that satisfies the requirement diff-gaussian-rasterization (from versions: none)
ERROR: No matching distribution found for diff-gaussian-rasterization

nvcc --version must show cuda 11.8

Using at home I got this: To create a public link, set share=True in launch().
Sampling: 100%|████████████████████████████████████████████████████████████████████████| 12/12 [00:02<00:00,  4.83it/s]
Sampling: 100%|████████████████████████████████████████████████████████████████████████| 12/12 [00:01<00:00,  6.93it/s]
Rendering: 0it [00:00, ?it/s]
Traceback (most recent call last):
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\gradio\queueing.py", line 536, in process_events
response = await route_utils.call_process_api(
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\gradio\route_utils.py", line 322, in call_process_api
output = await app.get_blocks().process_api(
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\gradio\blocks.py", line 1935, in process_api
result = await self.call_function(
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\gradio\blocks.py", line 1520, in call_function
prediction = await anyio.to_thread.run_sync(  # type: ignore
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\anyio_backends_asyncio.py", line 2505, in run_sync_in_worker_thread
return await future
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\anyio_backends_asyncio.py", line 1005, in run
result = context.run(func, *args)
File "F:\TRELLIS\TRELLIS\venv\lib\site-packages\gradio\utils.py", line 826, in wrapper
response = f(*args, **kwargs)
File "F:\TRELLIS\TRELLIS\app.py", line 113, in image_to_3d
video = render_utils.render_video(outputs['gaussian'][0], num_frames=120)['color']
File "F:\TRELLIS\TRELLIS\trellis\utils\render_utils.py", line 96, in render_video
return render_frames(sample, extrinsics, intrinsics, {'resolution': resolution, 'bg_color': bg_color}, **kwargs)
File "F:\TRELLIS\TRELLIS\trellis\utils\render_utils.py", line 73, in render_frames
res = renderer.render(sample, extr, intr, colors_overwrite=colors_overwrite)
File "F:\TRELLIS\TRELLIS\trellis\renderers\gaussian_render.py", line 223, in render
render_ret = render(camera_dict, gausssian, self.pipe, self.bg_color, override_color=colors_overwrite, scaling_modifier=self.pipe.scale_modifier)
File "F:\TRELLIS\TRELLIS\trellis\renderers\gaussian_render.py", line 58, in render
from diff_gaussian_rasterization import GaussianRasterizer, GaussianRasterizationSettings
ModuleNotFoundError: No module named 'diff_gaussian_rasterization'

share your machine specs , do you have gpu, what torch and cuda toolkit versions you are using?

No I didn't.
https://github.com/alexdepario
Another guy
;)

Same problem.
nvcc --version showed cuda 11.5, so I upgraded to 11.8, but it didn't help

@darkon12
If you have cuda 11.8 in the machine but nvcc doesn't point to it. [generally below is the location]
export PATH=/usr/local/cuda-11.8/bin:$PATH
export LD_LIBRARY_PATH=/usr/local/cuda-11.8/lib64:$LD_LIBRARY_PATH

if you want to download cuda 11.8 first then repeat above command. and confirm using echo command. use gpt.
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin
sudo mv cuda-ubuntu2004.pin /etc/apt/preferences.d/cuda-repository-pin-600
sudo apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/3bf863cc.pub
sudo add-apt-repository "deb https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/ /"
sudo apt-get update
sudo apt-get install -y cuda-11-8

share your machine specs , do you have gpu, what torch and cuda toolkit versions you are using? you switched from colab to windows?

Warp 1.5.0 initialized:
CUDA Toolkit 12.6, Driver 12.6
Devices:
"cpu"      : "Intel64 Family 6 Model 151 Stepping 2, GenuineIntel"
"cuda:0"   : "NVIDIA GeForce RTX 3090 Ti" (24 GiB, sm_86, mempool enabled)
I'm trying to install and run using this code in a install.bat file: git clone --recurse-submodules https://github.com/microsoft/TRELLIS.git
cd TRELLIS
conda create -n trellis python=3.10
conda activate trellis
pip install torch==2.5.1 torchvision --index-url=https://download.pytorch.org/whl/cu124
pip install xformers==0.0.28.post3 --index-url=https://download.pytorch.org/whl/cu124
pip install pillow imageio imageio-ffmpeg tqdm easydict opencv-python-headless scipy ninja rembg onnxruntime trimesh xatlas pyvista pymeshfix igraph transformers
pip install git+https://github.com/EasternJournalist/utils3d.git@9a4eb15e4021b67b12c460c7057d642626897ec8
pip install https://github.com/bdashore3/flash-attention/releases/download/v2.7.1.post1/flash_attn-2.7.1.post1+cu124torch2.5.1cxx11abiFALSE-cp310-cp310-win_amd64.whl
pip install kaolin -f https://nvidia-kaolin.s3.us-east-2.amazonaws.com/torch-2.5.1_cu124.html
git clone https://github.com/NVlabs/nvdiffrast.git ./tmp/extensions/nvdiffrast
pip install ./tmp/extensions/nvdiffrast
git clone --recurse-submodules https://github.com/JeffreyXiang/diffoctreerast.git ./tmp/extensions/diffoctreerast
pip install ./tmp/extensions/diffoctreerast
git clone https://github.com/autonomousvision/mip-splatting.git ./tmp/extensions/mip-splatting
pip install ./tmp/extensions/mip-splatting/submodules/diff-gaussian-rasterization/
xcopy /E /H .\extensions\vox2seq\ .\tmp\extensions\vox2seq
pip install ./tmp/extensions/vox2seq
pip install spconv-cu120
pip install gradio==4.44.1 gradio_litmodel3d==0.0.1
set ATTN_BACKEND=flash-attn
set SPCONV_ALGO=native
python ./app.py

I receive the same error. Are you running other than 4090 gpu? @alexdepario

If you're using GCC 13, you  may  need to apply this patch.  See here for more info.
Doing this allowed ./setup.sh --mipgaussian to complete in a Linux container with CUDA 12.6.  The file in question, on my system anyway, was at  /tmp/extensions/mip-splatting/submodules/diff-gaussian-rasterization/cuda_rasterizer/rasterizer_impl.h.  It showed up after  ./setup.sh --mipgaussian  failed to build, but a subsequent attempt post-patch worked.
To install xformers, which also had a cuda-incompatibility issue I think, I just manually did pip3 install -U xformers --index-url https://download.pytorch.org/whl/cu124  Replace cu124 with your version of cuda. I'm using a rather new one, not 11.8 or whatever.
I think this is all I did to get the demo app working.

Same problem. nvcc --version showed cuda 11.5, so I upgraded to 11.8, but it didn't help
UPD: rebooted the system, redo . ./setup.sh --basic --xformers --diffoctreerast --spconv --mipgaussian --kaolin --nvdiffrast problem solved

thanks


Change code for Resources merge/indirection

Let's change the code for Resources merge/indirection.

Closed by 3722304.


Updated docs, moved isplots_S4 to S4 ecf, added simple S3 pytest and smaller changes

Changes:

docs: include a description of the various parameters in the Eureka! Control Files (.ecf)
docs: replaced the previous Jupyter Notebook with a new one, written by Laura for Day 2 of the JWST ERS Pre-Launch Data Hackathon going through the S3 code and discussing the basics of data reduction
docs: incorporated @gianninapr ‘s “Contributing to Eureka” tutorial

moved all contents of docs/media into docs/source

if okay I would like to delete docs/media

renamed & moved docs/index.md into docs/source/contribute.md

if okay I would like to delete docs/index.md

added markdown files to source_suffix in docs/source/conf.py

docs: added new requirements for ReadTheDocs
moved "isplots_S4" from S3 ecf to S4 ecf
added some documentation to lib.util
added simple pytest for S3 by testing the lib.util.trim function
removed ./lib directory (had only poet_models.py in it and is duplicate of eureka/lib/modelsPOET.py)

Oh, are we going to run both Read The Docs and MkDocs in the future?


Does not work on Neovim

I have tried a number of the fixes here - the plugin loads with lazy and I am adding some enterprise server options (the ones provided directly from the Codeium website). Codeium Auth works (and takes me to the correct enterprise site) then... nothing, no completions or errors.
Config in Lazy:
	{
		"Exafunction/codeium.vim",
		dependencies = {
			"nvim-lua/plenary.nvim",
			"hrsh7th/nvim-cmp",
		},
		event = "BufEnter",
		config = function()
			vim.keymap.set("i", "<C-Space>", function()
				return vim.fn["codeium#Accept"]()
			end, { expr = true, silent = true })
		end,
	}

try to use :imap <c-space> to check if any other plugin has occupied the key map, if nothing bound, run :checkhealth to test if the the plugin is working regularly, if reveals warning that language server failure or others, delete codeium directory from .cache/nvim/codeium, that will redownload and reinstall language server from internet. Maybe it works.

Related #399

I got the very same issue – I may be wrong, but I reckon it isn’t straightly related to #339.
My key-binding settings for Codeium are (nvChad):
  ai = {
    i = {
      ["<M-Right>"] = {
        vim.fn["codeium#Accept"],
        "accept suggestion",
      },
      ["<M-Down>"] = {
        function()
          return vim.fn["codeium#CycleCompletions"](-1)
        end,
        "previous suggestion",
      },
      ["<M-Up>"] = {
        function()
          return vim.fn["codeium#CycleCompletions"](1)
        end,
        "next suggestion",
      },
      ["<M-Left>"] = {
        vim.fn["codeium#Clear"],
        "clear current suggestion",
      },
    },
  },

I tried to use function() return vim.fn["codeium#Accept"]() end instead of vim.fn["codeium#Accept"] directly, same outcome.
I also tried to use another functions in place of vim.fn["codeium#Accept"], and they work fine, the functions that don’t work are:

codeium#Accept (does nothing)
codeium#CycleOrComplete (only cycles)
codeium#Complete (does nothing)
codeium#AcceptNextWord (does nothing)
codeium#AcceptNextLine (does line)

By the way, the suggestion has been shown correctly, so I cannot help but think it’s an codeium#Accept (and similar functions) issue.

Please give steps to reproduce outside of NvChad, with normal nvim style mappings.


ERROR: cached plan must not change result type

Is there a way to invalidate the query plan cache when this error occurs? Some other drivers have an options to deal with this scenario.
This is cause be migrating the database during a running sqlx connection pool and changing the schema in such a way that the result is different than the query plan cache. This is problematic in a production environment if you have to restart the application servers after migration.

Hey I ran into a same issue and had success with this https://www.postgresql.org/docs/9.4/sql-discard.html

You can use https://docs.rs/sqlx/0.5.5/sqlx/trait.Connection.html#method.clear_cached_statements to reset ALL cached statements. This should definitely be ran after any DDL if you have any open connections.
However.. we don't have an easy way to run this automatically or even for all connections in the pool. Some ideas:

A method on pool to run a function on every connection once:

pool.for_each_connection(|conn| conn.clear_cached_statements());

A method on pool to discard all open connections and reconnect: pool.recycle().

Thanks @mehcode I realised that not all connections is clear. This leads to my question: how does this behave if I have load balancing servers connect to the same database? i.e. how I can notify all the servers of the changes?
In my particular case, I have a system to help users to alter different tables from time to time. Do you know a way to to discard cached plan for a table/schema? if not is there a way to disable cache plan for sqlx or any better way to let users adjust schema dynamically?
Thanks in advance.

Hey @mehcode not sure if it has any value but Rails has the same issue and what they do is to clear the cache and retry it
https://github.com/rails/rails/blob/main/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb#L725-L737
For transaction, they need to handle it a bit more carefully, they have to rollback the transaction first before clearing the cache
https://github.com/rails/rails/blob/8db23109bf61052eef437629b6ef27a94e0b5bd9/activerecord/lib/active_record/connection_adapters/abstract/transaction.rb#L323-L327

+1000 to this, it's a giant footgun: you run a migration and your sqlx app goes completely down until you restart it.  I haven't seen any other postgres lib in any language failing like this.
It would be great if sqlx could detect stale cached statements and automatically recover.
A workaround is setting .statement_cache_capacity(0) in PgConnectOptions, but that has a bad performance hit.

We can work on ways to address this. It could be something on ConnectOptions to tell the connection to automatically flush the prepared statements if it encounters this error instead of emitting it. It's really just a sanity check.
However, at the same time I'm wondering if this is a symptom of a deployment procedure issue. If you push a migration that changes the output of a query, isn't that likely to break your application anyway? This is why we prefer to embed migrations in the application binary, so that schema changes always coincide with an app upgrade. We never run into this error in our deployments.

If you push a migration that changes the output of a query, isn't that likely to break your application anyway?

This is a system where the main app who manages migrations is written in Go, and there's a Rust service reading only a handful of fields from a particular table. We ensure the main Go application never breaks these fields for the Rust service. Restarting the Rust service for every Go deployment is not an option, it's an IoT broker handling long-lived connections, its whole purpose is to keep these connections alive across application deployments.
I can imagine cases where this is an issue even with a single Rust service: if you want to do zero-downtime deployments you keep the old instances around while the new instances are starting up and doing the migrations (making sure migrations are "backwards compatible" of course). This bug will break the old instances, preventing the deployments to be zero-downtime.

We're running into this issue and are doing exactly what the previous comment is suggesting: we do zero-downtime deployments by keeping old instances around while new instances are starting up. We in fact pulled the migrations out of our main service instances and run them from a separate binary to gain more control over when they happen.
It would be great if sqlx could address this internally. I'm also still wondering about the scope of when this happens. For example, we're currently seeing this on adding a new column that would be currently unused by any query. Specifically, I wonder if we could work around this issue by avoiding SELECT * (and RETURNING *) clauses.
If someone wants to give me some guidance on where this change could fit in and what the best way is to specifically distinguish this error, I would probably be able to contribute changes in this direction.

Specifically, I wonder if we could work around this issue by avoiding SELECT * (and RETURNING *) clauses.

That's correct. You should only be seeing that error if you've made changes that affect the query plan of existing queries.

Looking back at this issue, there isn't any reason why we shouldn't capture that error and re-prepare the query. Similar to what's described here: https://github.com/launchbadge/sqlx/issues/1250#issuecomment-878249285

Hey peeps, just want to bubble up this issue once more.
As sqlx ecosystem is getting bigger, it is getting more important to fix the issue at the core of sqlx.
For example, https://github.com/SeaQL/sea-orm is not going to work correctly without this fix.

This issue seems to have been open for a while and is increasingly affecting a number of users, including @Roba1993  and myself. Given the significant impact it has on production environments, especially for those of us with frequent change on database schemas, it would be beneficial to prioritize a solution. Right now we have to set .statement_cache_capacity(0), which is ... suboptimal.

@mehcode Is there a chance to get this error/request into your backlog within launchbadge?

I'd like to respectfully emphasize the importance of addressing this issue. The "cached plan must not change result type" error continues to be a significant pain point for many production environments, particularly those that:

Require zero-downtime deployments
Have dynamic schema changes
Run distributed systems with multiple services accessing the same database

While the current workaround of setting .statement_cache_capacity(0) exists, it comes with notable performance penalties that aren't ideal for production systems. The suggested solution of automatically detecting and recovering from stale cached statements (similar to Rails' implementation) would greatly improve SQLx's robustness in real-world scenarios.
Given that this issue has been open since 2021 and affects many users, would it be possible to prioritize this enhancement?


feat: switch to github packages

This change isn't necessary - the repo is public but the link added to the readme is private. And the npmPublish field shouldn't be necessary.


Pycodestyle linting for pond

Started doing this and couldn't do it halfway, so here it is.

Closing because v stale and also looks like Ben incorporated some of this into a different PR, can reopen later if needed


Lunch time, refactored particles

shrug

Oh good, more things I don't understand :P

It's simpler :P
Trying to remove complexity. Also, we should probably look at webpack at some stage?

I just made a batch file ¯_(ツ)_/¯

I've just been going 'tsc -p .' but more that it would pack it into a single JS file, so we don't have a million js files :P

Oh yeah, thats probably worth doing. tsc will do that, but not with CommonJS modules, and it doesn't compile with amd or system. I've just been using VS Code, but silently dreading the first time I have to add a new JS file.


coordinator cmdDel failure with wrong type assert

Describe the version
version about:

spiderpool v0.6.0-rc2

Describe the bug
Once I delete one pod but found it was always terminating.
delegateDel: error invoking ConflistDel - \\\"macvlan-vlan100-underlay\\\": conflistDel: error in getting result from DelNetworkList: failed to get host veth device veth0d4f3800576: Link not found / delegateDel: error invoking ConflistDel - \\\"macvlan-vlan0-underlay\\\": conflistDel: error in getting result from DelNetworkList: failed to get host veth device veth0d4f3800576: Link not found\"" pod="ns1012-5875477/pod1012-5856177" podUID=e28ec61f-dae1-4da6-9937-b64a9152cd0c

The type assert is wrong. There's no need pointer type
https://github.com/spidernet-io/spiderpool/blob/38005dd95bc7af815bd558eb7fb4e6717a189028/cmd/coordinator/cmd/command_del.go#L92

https://github.com/spidernet-io/spiderpool/pull/1979


Allow cleanup code to run in process.exit

While trying to add tap-support for our integration test tool we ran into problems with leaking processes. It comes down to the following pseudo-code:
var tap = require('tap')

// ... somewhere in another module
var child = spawn('phanomjs')
process.on('exit', function() { child.kill() })

// back in the test code
tap.test('some failing test', function(t) {
  t.equal(1, 2)
  t.end() // oops, `child` will never exit
})

I'm not sure how to solve this problem for node 0.10 and before but starting with 0.12 tap could use process.exitCode instead of calling process.exit which lets other process#exit listeners run and (for us) fixes everything.

@jkrems unrelated to the actual PR, but for the problem you are describing...
One approach that works well with node is instead of killing the child processes is opening an IPC channel as part of the spawn and then in the child detecting when that pipe goes away and using that as a signal to exit. It's not directly applicable since you are spawning a process that is out of your control, but maybe it gives you some ideas for approaching the problem from another direction.

@rmg I could in theory try to spawn one more level of processes (since I neither control the application under test nor phantomjs) that handles the killing. But I'm hesitant to add another level of complexity. Once I go for hacks, I'd rather monkey-patch process.exit to do the cleanup instead or in addition to using a process#exit handler... ;)

@jkrems ya, I sympathize. I was hoping there was something specific to your case that would allow you to side-step the wrapper process approach.. I wonder if phantomjs would accept a PR that adds a parent IPC check/monitor.

Yeah, child processes are depressingly hard to get right. We also fork the app under test in our tool. Requiring any app that wants to use it to add such a check would be a bit awkward. So, even when we get it into phantomjs, it only gets us half the way there. :(

When the parent dies, unless the child is detached, it should receive a SIGHUP signal, which is normally fatal.  It could be that phantomjs is catching and ignoring that SIGHUP, since you're not running it detached.
We can use process.exitCode, but there are cases where we really want to make sure that we exit, but iirc, there are cases where exitCode changing in the exit event isn't caught properly, which is why this was changed initially.
It'd probably be safest to just make sure that we're always calling process.exit() in the last on('exit') handler.  I'm not sure if that's possible without clubbing the process.emit function.
More research is needed.  In the short term, you can set up your process.on('exit') handler ahead of loading tap, which should cause the behavior you want.

@isaacs So the default behavior of node could be considered a bug?
node -e "console.log(require('child_process').spawn('node', [ '-e', 'setTimeout(function(){}, 60000)' ], { silent: true }).pid); process.exit()"

After that, the pid of the child is still alive (and will be until it exits due to the empty event loop a minute later).

Found a solution in subprocess that works without changes to tap. Thanks for looking into this! :)


Tidy up the root of the repository for v2.1

A bunch of miscellaneous changes in preparation for the v2.1 release:

Move CONTRIBUTING.md to a .github/ folder.
See also: https://help.github.com/articles/setting-guidelines-for-repository-contributors/
Updated the .gitignore to reflect what gets produce in day-to-day iris development
Reduced the amount of redundancy in INSTALL. It now points to the requirements/ directory
which is what we actually test.
Updated minimum dependencies in requirements (because that is all we test):

Numpy>=1.14
Matplotlib>=2
cf_units>=2

:+1: Awesome, thanks @pelson


Correctly detect primary branch

Fixes #518

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7d93c7a) 66.27% compared to head (16dd63e) 66.27%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #669   +/-   ##
=======================================
  Coverage   66.27%   66.27%
=======================================
  Files          22       22
  Lines        2150     2150
=======================================
  Hits         1425     1425
  Misses        591      591
  Partials      134      134

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fixes the number list to increment correctly in the markdown view

Thanks!

Thank you for the awesome lib!!!


infer function generic signature from actual function's return type

Suggestion
function test<T>(fn: (prev: T) => T) { }
test((prev) => ({ a: 1 })); // T is inferred as "unknown"

🔍 Search Terms
Maybe an issue exists, but I wasn't sure what to search for. "Infer generic function type from return value" didn't really help.
✅ Viability Checklist

My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code. not sure
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
T should be inferred as the type of the returned object, {a: number}
📃 Motivating Example
https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABFApgZygHgCoD4AUwYAXIvgA4BOKAbqdgJSIC8uijiA3ogL4BQqDPgrUaTVmW4BDUgEZeDBgG4+QA
💻 Use Cases
make life easier

It's not that TS doesn't infer the generics, in general, but just that it's inferring it as unknown in this specific case.
test(() => ({ a: 1 })); // T is inferred as "{ a: number }" as you might expect

It looks like the issue here is the unannotated prev, since that's unknown, T ends up as unknown.
In this very simple case (where prev is unused), it's fairly easy to see what the right behavior would be, but I suspect that evaluating the return type of a function and using that to infer the type of its arguments (which usually affect the return type) is not a simple thing to do.

Yeah, I'll reopen #47599 since it's not fully covered

Yeah, I understand.  What bothers me is mostly theoretical - the fact that the current behavior basically amounts to:

What is T?
Ooh, prev is a T, we can infer T from the callback the caller passed in...
...except prev has no type annotation!
Contextual typing says prev is a T, but we don't know what T is yet...
Screw it, we'll say prev: unknown (i.e. the constraint of T).
Therefore, T is unknown.

To be clear, my problem isn’t the prev: unknown part (that part makes sense), but the fact that T ultimately has its own constraint as its inference site.  I guess there’s no mechanism to fix the latter without compromising the former, though.

I believe what actually happens is that we collect candidates for T, find out there are none, so default it to its constraint, which is unknown, and then process the call as if you had written test<unknown>(.
It's weird since if you had written test<unknown>(, that definitely shouldn't be an implicit any error. Maybe we need to make a marker unknown to use in zero-candidate inference that isn't allowed to contextually type a parameter - worth experimenting with, probably.

@weswigham pointed out this example
type Box<T> = { contents: T };
function test<T>(fn: (prev: Box<T>) => T) { }
test((prev) => ({ a: 1 }));

It's not clear how we'd turn this into an error -- somehow it's (speculatively) a "Box<implicit any>" which isn't really a thing - implicit any arises when a binding should have a contextual type but doesn't, but that's not what's happening here. And zero-candidate inference is not a manifest error either:
function test<T>(x?: T): T;
test();

So there seems to be some difficulty in establishing what rule exactly would turn the OP example into an error without either breaking something that shouldn't be broken (benign zero-candidate inference), failing to break something equally suspect (Box<), or both.

Does TypeScript have a Hindley-Milner type system? Because I'm pretty sure it would work with that kind of type inference.
TypeScript would see that the return type and first parameter have to be the same, so it could check for return type and see "oh it's an object literal with type { a: number }". And because it knows that prev must be of the same type, it can say that prev is of type { a: number } too.
It seems like it doesn't work like that now, right?

No, TS's type system is not H-M.  Type inference is done locally.  See https://github.com/microsoft/TypeScript/issues/30134.
Your example of inferring prev based on the return type was [discussed above]:(https://github.com/microsoft/TypeScript/issues/49618#issuecomment-1162391274)
function test<T>(fn: (prev: T) => T) { }
test((prev) => {
  return prev ? 0 : 1;
});

would infer T = 0 | 1 under your proposed behavior, which isn't ideal (number would be more useful).  In general this behavior would tend to infer types that are too narrow.

Interesting points above. I can describe a real-world use case. Suppose we have a memo function that is reactive, and re-runs any time dependencies used inside of the function body change. The memo tool can be called in two ways:
const fname = reactiveVar('John')
const lname = reactiveVar('Doe')

const fullname = memo((prev) => {
  return fname.get() + ' ' + lname.get()
})

fullname() // string, combination of fname + lname

In this first case, prev arguments can only ever be string | undefined, where on the very first run of the reactive expression the initial prev value is undefined. It can never be anything.
Any time that fname.set(string) or lname.set(string) are called, it causes the function passed to memo to re-execute to evaluate the new fullname and trigger other reactive expressions elsewhere that depend on fullname.
The second way to use the memo API is like this:
const fname = reactiveVar('John')
const lname = reactiveVar('Doe')

const fullname = memo((prev) => {
  return fname.get() + ' ' + lname.get()
}, "Godzilla Kong") // <--------------------------- HERE, new movie idea

fullname() // string, combination of fname + lname

In this case, prev arguments will only ever be strings. They will never be anything else, because the initial value use for prev will be "Godzilla Kong".
This works totally fine in plain JavaScript, but the main issue is that in TypeScript, it currently requires too much superfluous type annotation.

@trusktr did you mean to use prev in these examples? Again we have the problem of "you can just omit the parameter".

I have a real-world use case related to a PR in nanostores.
I'm adding a cx function into the computed function. The cx function takes a callback & auto-subscribes to dependencies by adding itself to a global stack while the callback executes. I'd like to have the return type of the cx function be the return type of the callback.
Here is a contrived example to keep it simple. The real use case involves async, but I'm keeping it synchronous for brevity.
let $firstName = atom('')
let $lastName = atom('')
let $fullName = computed(cx => {
  return cx(() => `${firstName()} ${lastName()}`) // How do I infer the return type being a string here from it's usage?
})
declare function computed(cx: ComputedCx)
type ComputedCx<R = any> = // <R> will cause a type error in the computed declaration
  (cb: () => R) => R


Detection category

Hello, if I want to output the target category to the detection image, where should I modify?

In order to display the target category, I added the following content to line 81 of plot.py:
cv2.putText(img, label, (c1[0], c1[1] - 2), 0, tl / 3, [225, 255, 255], lineType=cv2.LINE_AA)
The following content is displayed in the result of the detection image:
Does the 0 in the image represent the category, and does 0.92 represent the confidence level?

Yes, you are right.
Thanks for your interest in our project.

你们的工程是不是把'car', 'bus': , 'truck', 'train'都归为类别0了？

yes

Hi, may I ask how to change 0 to class name like car, truck...?
thank you


Disable Rule 0016 "Caption is missing." for objects of the the API

Related to issue: https://github.com/StefanMaron/BusinessCentral.LinterCop/issues/190.
Because this could be experienced as a breaking change I've provided a setting in the LinterCop.json to enable the current behavior. When an external application uses the metadata of the API's, like the PowerPlatform, you can make the rule 0016 more strict. Not sure if there's a performance penalty I should consider on getting/reading the setting from the json-file?

Found a bug, I'll create a new PR once solved!


bug: CSS now working for new workspace

Provide environment information
System:
    OS: Windows 11 10.0.22631
    CPU: (4) x64 11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz
    Memory: 1.08 GB / 7.80 GB
  Binaries:
    Node: 20.15.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.5.0 - ~\AppData\Roaming\npm\pnpm.CMD
    bun: 1.0.21 - ~\.bun\bin\bun.EXE

Describe the bug
I created new folder named admin in my apps/
apps
---admin(next app)
---expo
---auth-proxy
---nextjs

After created i cd to admin dir and copy next apps all things and pasted in admin folder. i changed admin/package.json's "name": "@acme/admin",
and removed all node_modules, dists and .next and other if generated as well.
then from root i pnpm install and created new command in root package.json "dev:admin": "turbo watch dev -F @acme/admin..." and run pnpm dev:admin.
app is starting fine with all other things like api and auth and everything. but css/style is not being applied to it.
Link to reproduction
https://github.com/t3-oss/create-t3-turbo
To reproduce
nothing fancy. i just explained all.
Additional information
apps/admin :

apps/nextjs :

nm, found bug, i made mistake while copying tailwind.config.ts for apps/admin dir.


Feature request: exclude also i18n URLs

Hello.
It would be great if DJANGO_SONAR['excludes'] could automatically detect language code prefix in the URL path. So instead of setting this:
DJANGO_SONAR = {
    'excludes': [
        '/en/jsi18n/', '/sk/jsi18n/', '/cs/jsi18n/', '/pl/jsi18n/', '/hu/jsi18n/', '/uk/jsi18n/',
    ],
}

it would be able to use a using single path instead:
DJANGO_SONAR = {
    'excludes': [
        '/jsi18n/',
    ],
}

The jsi18n path is defined in urls.py using i18n patterns:
urlpatterns += i18n_patterns(
    path('jsi18n/', JavaScriptCatalog.as_view(), name='javascript-catalog'),
)

Thanks!

Hello again.
Thanks for all these suggestions man.
I think the best way to solve these kind of issues is to support regex on the "excludes" parameter.
In that way one could do something like this:
/*/jsi18n/
I'll look into it for a future release.

Yes, that's exactly what I meant :) Thank you! Looking forward to it.


Implemented validation on request header keys on Req.new

Not sure if I put the logic in the best place but it's where I thought it made sense to me!

Thank you for the PR. It looks good to me, I'm just still trying to figure out whether we should only do the checking on Req.new (and thus on Req.get, Req.post, etc too.) or everywhere, including the lower-level Req.Request.* functions.

@octowombat thank you for pursuing this. This gave me a lot to think about. I decided to:

always downcase header names
warn if they aren't downcased

This is done in #227.
My critical insight was if we ever want to change the behaviour (e.g. noop for maximum performance, raise, etc) it should be done by a compile-time configuration. That is, the __encode_header_name__/1 that I introduced in the PR would become a macro that would return argument as is in :noop mode, generate code that checks and warns at runtime in other mode, etc.
I'm sorry that I won't be merging your PR but it really was very influential, all the edge cases you explored in doc.


Buttons on the add tags view should be equal width

macOS uses equal width buttons for OK / Cancel buttons. Right now the buttons on the add tags view are different sizes meaning that they look out of place on the platform.

They should look more like this:

Strangely it doesn't look like SwiftUI actually provides an easy way to do this. The best documentation I've found on how to approach this so far is https://www.swiftbysundell.com/questions/syncing-the-width-or-height-of-two-swiftui-views/.

Closing as invalid; the add tags view no longer exists.


Fixing XSS vulnerability

HTML-encoded the Markdown before rendering as HTML to remediate the Reflected XSS vulnerability

Thanks @kukfa!

Looks like this ended up breaking something on the Heroku app.. maybe due to the CGI class usage?


[FLOC-2209] Move the CentOS and Ubuntu instructions (above the Alpha and Testing sections)

CentOS and Ubuntu instructions moved so users don't miss essential instructions (these were previously below sections labelled as Alpha & Testing.
Note - while not part of this PR, we shouldn't be using Alpha in the docs. Issue raised: FLOC-2243

Thanks.  Please address that one point and then merge.


Remove unused NewSettings function in server package

Remove unused NewSettings function in server package
Motivation
The NewSettings function in the server package is never really used.

Pull Request status

[x] Initial implementation

Coverage increased (+0.09%) to 88.821% when pulling ed1ccaf380c6c059b541444f55a3f78fb4a810cd on remove-deadcode into 50384d18358babeb3e6ba4b0abc39abdea6f78eb on master.


How to get the current data in TableDataSource?

Currently there's no public attribute for us to get the current data in TableDataSource instance, right?
I check the source code of TableDataSource, it seems the data is stored in rowsSubject, could we change the rowsSubject to a public attribute? so that we can deal the logic with data rows in typescript files.

Hi @cindylulu,
You can access datasourceSubject, which is an array with the data in the table.
Currently the is no outer access to rowsSubject, because that doesn't have to be displayed to outer classes, and it's private for abstraction purposes.


reference as input or parameter

Hi @wasade ,
testing is currently not very convenient, because of the long waiting times. Therefore, I think passing reference tree/alignment would be quite beneficial. I wonder how to design that.
Since both are Semantic Types (FeatureData[AlignedSequence] Phylogeny[Rooted]) they can only be "inputs" not "parameters" right? If so, do you know if it is possible to have optional inputs?
If not, the user needs to always pass reference alignment and reference phylogeny as q2 artifacts. Do we really want to put that burden to users or would we be fine to have two "parameters" (which can be optional) that point to filenames?
P.S. could you invite me to the slack channel for q2?

Sounds good. Unsure about optional inputs but I think not. What about instead of optional inputs, a method for establishing a reference which uses the types you propose, and a method which can take a reference that has been established?

Greg says that optional inputs are possible:
gregcaporaso: @Stefan, yes - see the phylogeny input here: https://github.com/qiime2/q2-diversity/blob/master/q2_diversity/_alpha/_visualizer.py#L266
I am building that in at the moment. I think that is easier than coming up with a new Semantic type of a "Reference"

Now implemented as optional inputs in PR #7


Single Member bugfix

Found a bug in my code addition that caused a failure in the case where the group only had a single member. i.e. line 642 would cause a bug when the $member var only had a single entry, causing it to just be a custom psobject and not an array, therefore it didn't have an op_addition method. Typecasting the var as an array fixes the issue.

Thanks @revoice1 ! Really appreciated! 👍


Nuget Tool Installer version 0.167.4 is failing

Required Information
Nuget Tool Installer version 0.167.4 is failing with message ERR:Invalid Version: null
Bug
Type: Unexpected error
Enter Task Name: Nuget Tool Installer
https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/NuGetToolInstallerV0
Environment

Server - Azure Pipelines
I can provide the account name, team project name, build definition name/build number in a private message
Agent is private running on Windows Server 1803 Server Core with Agent 2.159.2

Issue Description
Nuget Tool Installer 0.167.4 started failing inexplicably after it was updated to 0.167.4. Previous builds using version 0.165.0 worked just fine as of 13 hours ago.
Troubleshooting
Switched to Nuget Tool Installer 1.167.4 and updated nuget version being installed from 4.7.1 to 5.5.1 and our builds no longer receive this error even though both v0 and v1 have the same change from pull request 12635 20 hrs ago.

0.167.3 was also working as of 3 hours ago. We're getting the same error and builds are failing.

We are also facing the same issue, is there any way that we could mitigate this?

Possible solution here. Looks like Nuget 4.4.1 is no longer supported for that pipeline task. The files changed in the pull request indicate 5.4.0. I updated my step include the latest 5.4.0 and my build is proceeding.

https://status.dev.azure.com/_event/183168284

I had same issue. Modified pipeline to use NuGet 5.5.1 and it seems to be working.

This should be resolved with 0.167.5.


write, alert debug etc. not working

Only method delete is working on the next envionment
Environment details

OS: Linux
Node.js version: v8.5.0
npm version: 5.3.0
@google-cloud/logging version: 1.1.4

However, same code runs perfectly on Windows environment ( node version 8.9.1 npm version 5.6.0 and loggin version 1.1.4 )
Steps to reproduce

log.write (or debug, alert, etc)

I'm trying to reproduce, but cannot. Are you receiving an error message?

That's the problem, I am not, it's just like the code does not execute but I don't receive neither message of operation successful nor error message from the request. It's unusual because in fact I can use delete method and it works (only this one it works)

Thank you. Are you running the sample from the command line?

Yes, I am running "node quickstart.js" from samples directory

I found the problem but it makes no sense and I don't know how to solve it. When I run the code on Windows the enviroment shows next vars:
{ IS_APP_ENGINE: false,
IS_CLOUD_FUNCTION: false,
IS_COMPUTE_ENGINE: false,
IS_CONTAINER_ENGINE: false }
...but when I run the same code on Linux the result of environment is:
{ IS_APP_ENGINE: false,
IS_CLOUD_FUNCTION: false,
IS_COMPUTE_ENGINE: true,
IS_CONTAINER_ENGINE: false }
I realize that if I change manually the content of environment the code runs perfectly and I get the same results that If I were running the code on Windows.
Any help would be appreciated.
Thanks in advance.

That is strange. IS_COMPUTE_ENGINE is determined from this function: https://github.com/stephenplusplus/google-auto-auth/blob/765c8a0e85184538bda25f33bb949aa842eeff23/index.js#L217
The check is:
request('http://metadata.google.internal', (err, res) => {
  env.IS_COMPUTE_ENGINE = !err && res.headers['metadata-flavor'] === 'Google';
  callback(null, env.IS_COMPUTE_ENGINE);
});

So, it seems that somehow, the Linux environment you're in is able to respond to that request, and it has the appropriate headers. Is it possible an emulator is running, or any other tooling layer that might be different in the Linux stack?

I have run the code from a server in Compute Engine and from Cloud Shell

Would you mind explaining more complete reproduction steps? I'm uncertain of the environments you're running in, and what you're experiencing.

I am running code on Compute Engine Instance :
Node.js version: v8.5.0
npm version: 5.3.0
version gcloud logging: 1.1.4

Clone this repo https://github.com/googleapis/nodejs-logging
Install the client library with npm install --save @google-cloud/logging
Go to samples directory and run quickstart.js with command node quicktstart.js
Get no error neither any info but log entry does not save int stackdriver logging

That's all info I can give you besides the one you already have.
I hope this helps.
Thanks

Thank you. And your discovery about IS_COMPUTE_ENGINE, when you said:

When I run the code on Windows the enviroment shows next vars:
{ IS_APP_ENGINE: false,
IS_CLOUD_FUNCTION: false,
IS_COMPUTE_ENGINE: false,
IS_CONTAINER_ENGINE: false }

Do you mean within a Windows Compute Engine instance, IS_COMPUTE_ENGINE returns false?
Overall, I'm confused about that discovery that you made, so anything to elaborate would be appreciated. Thanks!

No, the Windows instance I use is not a Compute Engine instance, what I mean is that it seems there is a problem when it's got compute_engine: true because if I modify this param manually, the code runs perfectly. Hope I explain myself better :)

I was running same issue, i think the problem is with 1.1.4, im using nodejs-logging-winston. When I install this package on a compute instance running ubuntu 16.04 it install by default 1.1.4, so I had to manually install first nodejs-logging 1.1.2 then it works.

I am having the same issue.

Perfect !! It works with 1.1.2.
Thanks for your help.

I believe the fix has just been released under 1.1.5. Please try it out and let me know how it goes!


fix for ProgressBar not listening to size changes of parent track

What does the pull request do?
As shown here the indicator does not update if the parent track changes it's size. This can be the case when the layout was not updated yet as well as in other situations. This PR should fix it.
What is the current behavior?
See https://github.com/AvaloniaUI/Avalonia/pull/8488#discussion_r919672258
What is the updated/expected behavior with this PR?
indicator updates whenever the track changes its size
How was the solution implemented (if it's not obvious)?

Do the layout arrangement first and update the track second
listen to bounds changed of the track, if possible.

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues
Do I need to create an issue for this?
ping @maxkatz6

You can test this PR using the following package version. 0.10.999-cibuild0021895-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0022442-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0022477-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Getting error from Scons Multiple ways to build the same target after adding env.Command

Godot version
v4.1
godot-cpp version
1009da4
System information
Windows 11
Issue description
It seems  env.Command conflicting with env.SharedLibrary  after adding copy_bin_to_projectdir function at 843b225. I'm getting the following error when running scons without args.
scons: *** Multiple ways to build the same target were specified for: bin\windows\extension.windows.template_debug.x86_64.dll  (from ['src\\register_types.windows.template_debug.x86_64.obj'] and from [])

The stacktrace pointing to the env.Command call
libraryfile = "bin/{}/{}".format(env["platform"], file)
library = env.SharedLibrary(
    libraryfile,
    source=sources,
)
...
copy = env.Command(libraryfile, None, copy_bin_to_projectdir)
default_args = [library, copy]

SCons at 4.5.2

Opened PR https://github.com/godotengine/godot-cpp-template/pull/19


Removed CodePen samples from article: Add a simple data layer

Removed CodePen samples from article: Add a simple data layer

#sign-off


Disable submit when validation doesn't pass?

Right now, I'm trying to get the submit button to disable when validation hasn't passed. I have no idea how to accomplish such a simple task. I'm currently trying to use Control.button, but that control is strange and seems to want to associate the button with a field. I need the form-level validation status to determine the state of the button. How do I get that? Is there an HOC or something that I can wrap my button with?

Is fieldValue.valid the magic nugget?

And what should the model prop on Control.button be set to when the button really doesn't associate with a form field? I set it to ., but that seems like a hack.

How is your store set up? If you just set up a simple createStore(combineForms(...)), then your form state will be under the forms key. So you can grab your form validity state under:
const mapStateToProps = (state) => ({
  userFormValid: state.forms.user.$form.valid
});

connect(mapStateToProps)(MyForm);

And then use that:
// in render()
<button disabled={!userFormValid}>
  Submit!
</button>

The easiest way to do it would be to use <Control.button>:
<Control.button model="user" disabled={{ valid: false }}>
  Finish registration!
</Control.button>


Integrate relevant SRDB data

The following steps are required to integrate SRDB data into ForC:

[ ]  write a script to rearrange SRDB data into the ForC format
[ ]  write a script to categorize SRDB records into the following categories:
(1) records from unique sites (identified based on unique lat/long) that can be automatically added,
(2) records that are definitely duplicates (based on citation and value) and can be excluded (although they may have some valuable supplementary information associated),
(3) unique measurement records that may be from sites that already have records in ForC, and
(4) potential duplicate or conflicting records that need to be checked manually.
[ ] manually check/ merge categories 3-4 above. Note that without this they could still fit within the ForC structure. They would have different site names but be assigned to the correct geographic.area (a more meaningful category than site) and / or flagged as duplicates.
[ ] revisit original pubs to fill in missing details (again, they can exist in ForC without this; missing information would simply be coded ‘NAC’).

This issue is also recorded here.

A lot hinges on "into the ForC format". This means we'd like to map SRDB -> ForC variables?

Yes,
1- map the SRDB -> ForC variables
2- create a script to rearrange and add to ForC
3- resolve duplicates/ conflicts
4- fill in missing info as needed
I think it would make sense to schedule a call about this before getting started.

There are two major steps:
1- map SRDB fields to ForC fields, then write script to draw SRDB data and populate ForC fields

[ ] @teixeirak will create a document mapping SRDB fields to ForC fields.
2- resolve duplicates.

I've loaded a recent version of SRDB to ForC_private. I've started a document mapping SRDB fields to ForC.

I've finished a first pass at this SRDB-ForC mapping document. I hope it makes sense, but it may still be tricky to follow-- let me know what needs to be clarified. This includes all fields from both SRDB and ForC and can be sorted according to the field order in either one-- currently ForC. @bpbond, the "clarifications" field indicates questions for you. The "KAT action needed" field indicates issues that I still need to address, but most of these will be most efficient following your clarifications. This should certainly be enough to get started.

Looks like the file paths have changed and github redirections are intermittent - the new link to the mapping csv is here: https://github.com/forc-db/ForC_private/blob/master/data to add/srdb/SRDB-ForC variable mapping.csv

Thanks @dlebauer!

I'd like more clarification on Age_ecosystem and Age_disturbance, focusing just on records for which  Ecosystem_type = forest.
There are a some instances where there are records for both, and I'm not sure how to interpret them. Does this mean that the forest stand was established (e.g., post-agriculture) according to Age_ecosystem and later disturbed Age_disturbance = 80. Would Age_disturbance always be a stand-clearing disturbance?
If Age_disturbance>Age_ecosystem (one site), would that just be an error?

There are a some instances where there are records for both, and I'm not sure how to interpret them. Does this mean that the forest stand was established (e.g., post-agriculture) according to Age_ecosystem and later disturbed Age_disturbance = 80.

Right. Their meaning is "how long has this been a forest?" (Age_ecosystem) and "how long since the last disturbance?" (Age_disturbance).

Would Age_disturbance always be a stand-clearing disturbance?

Usually. I think always? Hard to think of a counter-example.

If Age_disturbance>Age_ecosystem (one site), would that just be an error?

Yes. Mmm, that's a good check to add to the SRDB QC script.

The site with is Age_disturbance>Age_ecosystem Tianmu Mountain (2 records).

@teixeirak Thanks! I'll go fix that.
Stage is very qualitative and somewhat inconsistent, but even so, there shouldn't be mature records with age < 20. Another good catch. Go with the quantitative number, I think, not the subjective (Stage) one, but I'll go check.

I believe the mapping document is now complete and ready to implement, except:

[ ] I need to review the manipulations and list those to exclude.  We won't include manipulation types that are specific to soil respiration studies (e.g., litter removal) or some of the more obscure ones (e.g., moose trampling!).
[ ]  ForC HISTORY fields need work. Don't do anything with this yet.

I have (finally!) finished the instructions for merging SRDB into ForC. Instructions are here.


Reduce number of moderators on BEP021

closes https://github.com/bids-standard/bep021/issues/10

TODO: update this change on the main branch too


Liveness detection

Is it possible to do a liveness check and ensure that it is not a printed photo that the user is holding in front of a webcam?

You can look if the eyes blink, you can use dlib to get face landmarks. For more info you can have a look at pyimagesearch  blink detection.


[Starter Projects] ZURB Template - Gulp pages task

How can we reproduce this bug?

Install foundation for sites, via Yeti Launch or Foundation CLI
Add a file html file to partials and include the file with handlebars in layouts/default.html
Run foundation watch in the project folder

What did you expect to happen?
When i edit the html file in my partials folder, gulp task fires and the browser will reload and show the changes that are made.
What happened instead?
The first edit i make in the partials folder works. After that nothing happens. I have to stop foundation watch and re-rerun to foundation-watch to see the changes that are made.

Output from terminal when i run foundation watch
[16:06:58] Using gulpfile ~/dev/callvoip/gulpfile.js
[16:06:58] Starting 'build'...
[16:06:58] Starting 'clean'...
[16:06:58] Finished 'clean' after 6.52 ms
[16:06:58] Starting 'pages'...
[16:06:58] Finished 'pages' after 192 ms
[16:06:58] Starting 'sass'...
[16:06:59] Starting 'javascript'...
[16:06:59] Starting 'images'...
[16:07:00] Starting 'copy'...
[16:07:00] Finished 'copy' after 697 μs
[16:07:00] Finished 'images' after 453 ms
[16:07:00] Finished 'javascript' after 832 ms
[16:07:00] Finished 'sass' after 2.2 s
[16:07:00] Starting 'styleguide'...
[16:07:00] Finished 'styleguide' after 46 ms
[16:07:00] Finished 'build' after 2.45 s
[16:07:00] Starting 'server'...
[16:07:00] Finished 'server' after 37 ms
[16:07:00] Starting 'default'...
[16:07:01] Finished 'default' after 26 ms
[BS] Access URLs:
   Local: http://localhost:8000
External: http://192.x.x.x:8000

      UI: http://localhost:3001

UI External: http://192.x.x.x:3001
[BS] Serving files from: ./dist
[16:07:27] Starting 'pages:reset'...
gulp.run() has been deprecated. Use task dependencies or gulp.watch task triggering instead.
[16:07:27] Starting 'pages'...
[16:07:27] Finished 'pages' after 2.51 ms
[BS] Reloading Browsers...

Try running the project again. Save a change to a partial. You'll see pages:reset run, but you might not see the partial update in your compiled files. Wait a second, then refresh the page and see if the change applied.
I think there might be a timing issue between Panini refreshing the partials and BrowserSync reloading the page.

Related: https://github.com/zurb/foundation-sites/issues/7075

Going to close in favor of #7075. There are two issues here, one trickier to solve than the other.


Cannot find module @pact-foundation/pact-node

I thought this issue was fixed. As in another post I see its already added as a direct dependency:
When I fire npm run "test:pact:consumer"  I am getting below error:
Error: Cannot find module '@pact-foundation/pact-node'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (C:\Users\userid\pact-workshop-js\node_modules\pact\sr
c\dsl\verifier.js:8:24)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)

This should be fixed in the latest edition, as it's a dependency in the root package. Please re-test, and let us know if you're still having any issues.


test: RHTAPBUGS-556 check first errorBuffer before buffer on spi access control e2e test

Description
Unfortunately, some jobs are failing with an empty buffer string when the guest user makes a POST request to spifilecontentrequests, from within a pod.
In order to investigate it (since I was not able to reproduce it locally yet), this PR changes the order of the assertions and improves it to check first if the errBuffer is empty in order to get more information, in case it fails.
Issue ticket number and link
RHTAPBUGS-556
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/retest

/retest

/retest


Compare each page of a pdf one by one

Right now multi page pdf will be converted to just one image. If pdf contains a lot of pages and created image snapshot become to big in size it might be hard to spot subtle differences.
Create new function or add options to configure current one to output snapshot of a pdf as an image per page. Create new and diff versions for only those pages that differ.

I don’t have immediate plans to implement this functionality at the moment, so I’ll be closing the issue for now. If anyone would like to see this feature added in the future, feel free to comment or reopen the issue.


IRegs - Small search terms return too many results from ES

When a user enters a search query that is too generic or small, ES results window exceeds the set limits, causing an Internal Server Error.
Current behavior

User enters a small/generic search term (i.e. "the")
ES raises exception with

elasticsearch7.exceptions.RequestError: RequestError(400, 'search_phase_execution_exception', 'Result window is too large, from + size must be less than or equal to: [10000] but was [14728]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting.')

Expected behavior

No search is performed when small/generic search terms OR gracefully handles too many results and returns such error.

Steps to replicate behavior

Search "the" on IRegs Search.

I moved this one over to our backlog.


[RELEASE-1.8][SRVKS-991] Unify release manifests

This patch is similar with https://github.com/openshift-knative/net-kourier/pull/43
but for net-istio.
The script also changes to unit the files under openshift/release/artifacts/* to the one file 1-net-istio.yaml.

/cc @skonto @ReToCode

/lgtm

/lgtm


Fix for issue created with 0245bd5

'window always on top' didn't have effect on launch.

This is an issue in my signals/settings libraries.
A settings connect automatically invokes the signal right after connection with its current value, whereas a normal signal connect doesn't. I should make that more clear/less easy to mess up.

sorry, I should've looked into it,
should I close this PR then?

@ch-ems You can leave it, it's still valid. I just wanted to make it clear that the reason this happens in the first place is due to the settings/signal library being poorly designed


Update dependencies and links for DiffFusion v0.7.0

This PR updates dependencies and links to reference DiffFusion v0.7.0.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 87.54%. Comparing base (a1bbea8) to head (d998d20).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #17   +/-   ##
=======================================
  Coverage   87.54%   87.54%
=======================================
  Files          11       11
  Lines         265      265
=======================================
  Hits          232      232
  Misses         33       33

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


merge clip+meanAgg

Description
The summary of the proposed changes as long as the relevant motivation and context.
Issues
List the issue or RFC link this PR is working on. If there is no such link, please mark it as n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
List the newly introduced 3rd party dependency if exists.
Tests
Describe the tests that you ran to verify your changes.

closing, will create another one after fixing 'keyerror "resume"'


Useless caveat about root element in a component

With new version of React (v16), many root element are acceptable.

I wouldn't quite agree. This note is to warn people against writing
return (

)

which feels intuitive to many people but gives an obscure parse error.
If you remove this note please add something else instead that calls this out. I've seen people repeatedly do this mistake, over and over.

The messaging before was incorrect and confusing (in my opinion).
I don't think I share the concern about the invalid syntax above, but trusting your judgement- I don't think the previous wording was sufficient to prevent it. 😄
Would be happy to review a PR that adds a new warning for that sort of case though!


Integration of linter for diagnostics

Here is a version of the Jest plugin that can be used for testing : https://gist.github.com/Kendos-Kenlen/fe3a361daa40954fe8d6f45b10bd5514


feat: allow the replace-use-search-params codemod to accept relative paths (INT-2089)

Changes:

added the relative path support for the replace-use-search-params codemod
fix existing TS errors

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


[HUDI-6381] Support bucket bulk insert for CoW table

Change Logs
in #7834, we support bulk insert for bucket index table.  This pr move the more table type check in RDDBucketIndexPartitioner back to RDDConsistentBucketBulkInsertPartitioner since only consistent hash bucket index table have the constraint that supports MoR table only.
Impact
Support bucket bulk insert for CoW table
Risk level (write none, low medium or high below)
none
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[ ] CI passed

Hello, @wulei0302 @bvaradar @jonvex,can you like to help review this pr, thanks~

@danny0405 Could you also have a look at this~


Slack Invite Redirect

I copy-pasted what I did in #54 and changed newsletter -> slack invite and link to slack invite link

once we have integrated Jekyll #60, we can use this: https://github.com/jekyll/jekyll-redirect-from

That's some cringe boilerplate but we'll allow it 👍

Yea Jekyll would be nice


disableKinds change has caused the example site to not work well

A few notes from trying this on Linux with following extended binary
Hugo Static Site Generator v0.74.2-48565DE6/extended linux/amd64 BuildDate: 2020-07-17T17:32:27Z

it definitely doesn't work out of the box, but as implied in the main repo you need to use the exampleSite to test out this theme, ok

Here's the error I see trying the quickstart guide and seeing if it works, nope
hugo server
Building sites … WARN 2020/07/18 20:47:46 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/07/18 20:47:46 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
Built in 12 ms
Error: Error building site: failed to render pages: render of "home" failed: execute of template failed: template: index.html:3:6: executing "main" at <partial "navigation" .>: error calling partial: "/home/admin/Documents/webdev/git-sites/hugotest/quickstart/themes/yourfolio/layouts/partials/navigation.html:2:25": execute of template failed: template: partials/navigation.html:2:25: executing "partials/navigation.html" at <len .Site.Menus.main>: error calling len: reflect: call of reflect.Value.Type on zero Value

Then I google the error and find a thread showing this refers to a type of content that is failing, so I check out the config.yaml site from exampleSite, ah I see some changes, looks like disableKinds line is what I need, so I try it out, however after adding this line
disableKinds: [RSS, taxonomy, taxonomyTerm]

However I see an error that explains that Hugo 0.73.0 made a change to the behavior of "taxonomy" value, but I don't have enough debugging skill to understand what different paramter I'm supposed to use instead of "taxonomy"
hugo server
ERROR 2020/07/18 21:00:56 You have the value 'taxonomy' in the disabledKinds list. In Hugo 0.73.0 we fixed these to be what most people expect (taxonomy and term).
But this also means that your site configuration may not do what you expect. If it is correct, you can suppress this message by following the instructions below.
If you feel that this should not be logged as an ERROR, you can ignore it by adding this to your site config:
ignoreErrors = ["error-disable-taxonomy"]
Building sites … WARN 2020/07/18 21:00:56 found no layout file for "HTML" for kind "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
Built in 12 ms
Error: Error building site: failed to render pages: render of "home" failed: execute of template failed: template: index.html:3:6: executing "main" at <partial "navigation" .>: error calling partial: "/home/admin/Documents/webdev/git-sites/hugotest/quickstart/themes/yourfolio/layouts/partials/navigation.html:2:25": execute of template failed: template: partials/navigation.html:2:25: executing "partials/navigation.html" at <len .Site.Menus.main>: error calling len: reflect: call of reflect.Value.Type on zero Value

At this point I've pretty much given up on trying to use this theme as it seems outdated and partially broken, but it is beautiful and I love the example site, so I may come back to this, hoping serg might try and help fix this to keep this theme up to date, if interested. Or perhaps I haven't followed the exampleSite properly, in which case I do apologize if I've missed something, but I do feel I've spent a decent bit of time trying to set this up and either:

the setup instructions are sub-par in my opinion, OR
due to changes in Hugo and how disableKinds parameter (or some other config paramter) works, this theme is not up to date and cannot be used "out of the box"

Cheers

Hello @theodore-dream
Thank you for your interest to my theme!
Let me help you to run this theme.
As you may heard Hugo is evolve fast and new versions came out is too often. But, Hugo is improving from version to version.
The last version, where I tested theme was 0.72/extended. Some issues appeared and related with renaming for taxonomy terms in 0.73 version. Here is some info about this.
For fixing, you need replace this:
disableKinds: [RSS, taxonomy, taxonomyTerm]

with:
disableKinds: [RSS, term, taxonomy]

The minimum requirement for this theme is 0.64.1 for Hugo version. I will need to think a little bit about the update above for make opportunity to build this theme on the few versions of Hugo before 0.73. I think the best way is mention this in readme.
Also, thank you for pointing me up about adding updates to readme file. I will add the updates about how to build the theme and keynotes about how to use theme (here is some of helpful things, those I would like to describe) when have a time.
Here is a quick optional tip about how to check theme by using only cloned version of this repository (see more info here). Inside cloned folder you could run this command:
hugo server -s exampleSite --themesDir=../..

Please let me know if you got a successful build on your side after applying the updates above or info about any other concerns with build.

@theodore-dream, also, according to your logs, seems like you have issues in menu part for your version of theme. Do you have any menu items, defined in your config.yaml file?

Hi @serg I completely understand apologies if I came across harsh in any way just wanted to bring this to your attention. I am completely new to Hugo but pretty familiar with Linux and thought the error was pretty clear so thought I'd share. But I wasn't aware how quickly Hugo is changing so I can understand its a lot of work to keep a theme up to date.
I did test your fix on my example site, and it did run without the same error but the site was completely blank as obviously I was missing necessary content for the theme. My example site was just testing the functionality I don't have any actual site content built right now just testing. So no my content would not have showed anything even if it did work successfully without error, I'm now realizing. Makes sense.
I did try it again using your exampleSite and with your updated disablekinds parameter it did work! I do like your tip on how to quickly test.
This is resolved, just a few thoughts/realizations

Without the user of the theme or the main owner having a very high level of involvement in the Hugo project and all its updates, it is very hard to sustain a theme's development and keep in line with the upstream, I guess that's just life.
Taking a closer look at your _index.md it does seem you have to manually set the image sizes, so not sure how much of a learning curve is there, but this is definitely my favourite functionality of your theme and I'm honestly a bit worried this would break over time if I were to keep updating Hugo version, I don't know enough to say how "standard" many of your unique pieces are (the highlighting of the images)

Basically it seems (not enough expertise to really know for sure) that your theme's uniqueness is a double edged sword, because it simultaneously makes it very attractive because I like the unique elements, but those unique elements and lack of folks using them in this other/themes (from what I can tell) also means it seems likely that Hugo updates may break that functionality over time. So to be completely honest this makes me want to continue my search for other themes. Bittersweet. Not 100% sure just sharing my thoughts. Really appreciate the prompt feedback regardless Serg!

@theodore-dream, thank you for your feedback! Unfortunately I can't reproduce this issue with default content (provided in theme). I sent you a message to your email with instructions (2 min video) how to install theme on your side. Hope it will be helpful.

@serg yes this issue is resolved, allow me to show you the reproduction steps. This is basically to explain why you must use the exampleSite you provide and my failure to do this caused the issue, I was trying the example steps from Hugo quick start https://gohugo.io/getting-started/quick-start/ and this is what lead to the issue.
So it seems that this is not an issue of one simple config field as I misunderstood, but an overall misunderstanding on my part regarding how this is meant to be setup, and the user of this theme has to use the exampleSite and build from there.

As example please see on the exampleSite folder inside the theme folder for how to configure a website and create content files.
^^^ I should have paid more attention to this
Reproduction steps for issue:
1179  hugo new site quickstart
1180  cd quickstart/
1181  git init
1182  git submodule add https://github.com/serg/yourfolio.git themes/yourfolio
1183  echo 'theme = "yourfolio"' >> config.toml
1184  hugo new posts/my-first-post.md
1185  hugo server -D
hugo server -D
Building sites … WARN 2020/07/19 19:30:39 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/07/19 19:30:39 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2020/07/19 19:30:39 found no layout file for "HTML" for kind "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
ERROR 2020/07/19 19:30:39 render of "home" failed: execute of template failed: template: index.html:3:6: executing "main" at <partial "navigation" .>: error calling partial: "/home/admin/Documents/webdev/git-sites/hugotest/quickstart/themes/yourfolio/layouts/partials/navigation.html:2:25": execute of template failed: template: partials/navigation.html:2:25: executing "partials/navigation.html" at <len .Site.Menus.main>: error calling len: reflect: call of reflect.Value.Type on zero Value
Built in 13 ms
Error: Error building site: failed to render pages: render of "page" failed: execute of template failed: template: _default/single.html:3:6: executing "main" at <partial "navigation" .>: error calling partial: "/home/admin/Documents/webdev/git-sites/hugotest/quickstart/themes/yourfolio/layouts/partials/navigation.html:2:25": execute of template failed: template: partials/navigation.html:2:25: executing "partials/navigation.html" at <len .Site.Menus.main>: error calling len: reflect: call of reflect.Value.Type on zero Value
However I can confirm that yes this works perfectly using your exampleSite as demonstrated in your video!


Some small updates

The two small modifications in this PR are the following:

By default, use the public repo of flups instead of the private one
Specify a fortran compiler to OpenBlas to includes the Lapacke routines in the resulting library

Thanks @pbalty


Explain static memory

It's a bit hard to figure out what we mean by 'static memory' or 'memory with static addresses' from the code.  I had to dig in the git history, but I'm not sure I guessed right.  Please check whether I guessed right.

https://github.com/scroll-tech/ceno/pull/609 did the job better than I could.  Thanks!


GEOMESA-903 Reducing polling time in GenericSimpleFeatureStreamSource

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

I'm going to close this - I think it's a good idea (if a client wants to wait between polling, they can do it explicitly) but I'm not sure if it will affect other projects that rely on the current behavior.


Updating the overview of Functions

Updating the overview of Functions to call out the limitation of the ports that Function Apps can listen on, being ports 80 and 443 (limitation imposed by the App Service sandbox).

Hi @MattTatoczenko, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@MattTatoczenko : Thanks for your contribution to the Azure documentation! The author, @mattchenderson, has been notified to review your proposed change.

@MattTatoczenko I discussed your proposed change with the product team. While all agreed that this information needs to be published somewhere, we probably don't want to clutter the overview topic with these kinds of platform details. I have added your proposed text to this issue in the Azure Functions repo so we can continue to track it. We will let you know when we get the App Service topic and Functions created. In the meantime, I am going to close this PR. Please don't hesitate to help out with Azure documentation in the future.

#close


Not able to pass standalonePassword as kubernetes environment variable. We have mounted secret as volume. Not able to find more information about neodash kubernetes deployments

Guidelines
Please note that GitHub issues are only meant for bug reports/feature requests.
Before creating a new issue, please check whether someone else has raised the same issue. You may be able to add context to that issue instead of duplicating the report. However, each issue should also only be focussed on a single problem, so do not describe new problems within an existing thread - these are very hard to track and manage, and your problem may be ignored. Finally, do not append comments to closed issues; if the same problem re-occurs, open a new issue, and include a link to the old one.
To help us understand your issue, please specify important details, primarily:

NeoDash version: X.Y.Z

Neo4j Database version: X.Y.Z (Community/Enterprise/Aura).

Steps to reproduce

Expected behavior

Actual behavior

Additionally, include (as appropriate) screenshots, drawings, etc.

Yeah - I faced this issue too. Kindly update your story to include more details though.
The problem occurs from the docker script entrypoint.sh in scripts/ folder. It overwrites any and all variables that should be passed to nginx config from kubernetes. The other compounding challenge is that kubernetes cannot modify things directly inside the nginx owned html folder.
I am yet to figure out a clean fix for this, maybe when time permits in future. For now, I'd recommend using the shared URL. If you do need this working earlier, you should modify the entrypoint logic such that the overwrite does not happen (so play with dockerfile).


Fixed 404 response on age restricted videos

Now this YouTube endpoint also require provide client and his version, using here ANDROID because in response we receive always deciphered links so it won't give 403 errors

@Walkyst Just tried this but it's returning no results found for age-restricted videos.
For regular videos, it returns some weird error: https://srcb.in/OLcjfhkGwh,
Any idea why? Did they ban this method again within these 8 hours?

Any idea why? Did they ban this method again within these 8 hours?

Nah, it is because pbj requests require right headers

why this is still not merged and why is the repo so inactive now? @sedmelluq
i have been having this issues for over a week now

why this is still not merged and why is the repo so inactive now? @sedmelluq
i have been having this issues for over a week now

Welcome to open source, where maintainers have a real life and obligations don't exist. If you urgently need, the only real solution is to pay sed for making time now or fork.


Destroy random instance when shrinking

Scrapoxy is brilliant!
Just one improvement I'd love to see. I have a config as follows:
"instance": {
"port": 3128,
"scaling": {
"min": 1,
"max": 4
},
"autorestart": {
"minDelay":	1800000,
"maxDelay":	3600000
}
},
When I push load through Scrapoxy and it shrinks down to 1 instance, it's always the oldest (or first) instance that stays - so once every few weeks I have to go in and destroy it.
Is it possible to randomise which instances get destroyed, so an instance doesn't hang around for a long time?
Thanks,
Adam

I will be in the next release.

Thanks so much. Any way I can say thank you? Paypal/charity donation?

No need :) I enjoy to develop Scrapoxy.
Feel free to speak about Scrapoxy around you, it will be great for the project!
Fabien.


Tracking not working for one website

Hello,
I just setup my server recently i noted one of my websites not begin tracking i don't know the reason is there is any logs i can figure out what is the issue ?

Open up the network panel in the browser developer tools and see what requests are being sent.


Capture mouse clicks (selection) and shift-enter (run) for iframes

Also @KesterTong

This version of colaboratory is no longer supported, please switch to https://colab.research.google.com.


Extended Windows Update Logging

Dear,
Under windows 7 you could configure Extended Windows Update logging :
see the registry keys at https://support.microsoft.com/en-us/help/902093/how-to-read-the-windowsupdate-log-file
How do you do this in Windows 10 ?
Kind Regards

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

ID: 47692487-0a0b-3b1b-6d34-790046c7cbc3
Version Independent ID: 0f66cafe-2bff-4323-b3fc-01014b904b3a
Content: Windows Update log files
Content Source: windows/deployment/update/windows-update-logs.md
Product: w10
GitHub Login: @kaushika-msft
Microsoft Alias: elizapo

Hello, @dfter thank you for providing feedback.
The issues section of this repository is intended for product documentation issues only.
Please consider opening a product support ticket by the following link below for your problem so that it gets resolved quickly.
Windows 10 Support
Thank you.

@officedocsbot close


Better support React 16.3.0

https://github.com/mridgway/hoist-non-react-statics/pull/43

Thanks you for the quick review! I was shopping outside.


Simplify the path of controller related to Task.

Compute template path or redirect path by the given task id.
For example, /task/{taskId}

Finished


Issue with authenticate call

Hi, just trying to run you for example to get the vehicles/vin and this error occurs:

Traceback (most recent call last):
File "myv.py", line 12, in
asyncio.run(main())
File "/usr/lib/python3.7/asyncio/runners.py", line 43, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "myv.py", line 6, in main
vehicles = await client.list_vehicles()
File "/Kubernetes/tesla_api-master/tesla_api/init.py", line 119, in list_vehicles
return [Vehicle(self, vehicle) for vehicle in await self.get("vehicles")]
File "/Kubernetes/tesla_api-master/tesla_api/init.py", line 91, in get
await self.authenticate()
File "/Kubernetes/tesla_api-master/tesla_api/init.py", line 81, in authenticate
expiry_time = timedelta(seconds=self._token["expires_in"])
KeyError: 'expires_in'

I thought the module would authenticate or re-authenticate as needed? But the "expires_in key is missing.
Any help would be appreciated?
running python 3.7.3 on Raspbian 32-bit.

Getting any closer to working on this update?
Kary

On Oct 28, 2021, at 9:53 AM, Sam Bull @.***> wrote:

It's on my list, after some aiohttp maintenance tasks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Allow for uv global instantiation

I would like to see uv recognized for global virtual environments in a similar way to how pyenv works. Instead of focusing solely on in-project folder development, allow for global env instantiation.
In theory, this task should be accomplished by creating all virtual environments via:
uv venv ~/.venvs/my_project_env
To activate the environment:
source ~/.venvs/my_project_env/bin/activate
Alternatively, uv could add the following function to .bashrc/.zshrc:
function uvactivate() {
    source ~/.venvs/$1/bin/activate
}

Then users could activate an environment like this:
uvactivate my_project_env

The solution above works perfectly and seems to be a straightforward replacement for pyenv.
Here’s a bit more detail about my setup:

My virtual environments are located at: /Users/<user>/.config/uv/venv.
I started creating named virtual environments, such as .uvcore12, .uvcore13, etc. Since uv doesn’t support named environments directly, I follow this process:

I run uv venv --python 3.xx, which creates a folder named .venv.
I then rename .venv to my preferred name, like .uvcore12.
To ensure the prompt reflects the new name, I modify the activate script in the renamed folder:

Set VIRTUAL_ENV=/Users/<user>/.config/uv/venv/.uvcore12
Set VIRTUAL_ENV_PROMPT="(core12)"

Additionally, I added the following function to my .bashrc or .zshrc:
function uvactivate() {
    source ~/.config/uv/venv/.uv$1/bin/activate
}

With this setup, I can activate my environment/s from anywhere by simply calling uvactivate core12, and the prompt will show 3.12.6 (core12).
Then any uv pip install ... will install the new packages in the activated environment that works globally. I hope this helps.
Would be nice to have the activate command under uv activate <env_name>

On our end, we simply do
ENV UV_PROJECT_ENVIRONMENT="/usr/local/"

@CharlesPerrotMinotHCHB: your proposed way, under /usr/local/:

you will keep overwriting the default python installation, as it always creates .venv,
you are not allowed to use named env instances
you will also miss on prompt naming
No way on easy diff named env activation.
Instead you will always dip into .venv

@krstp true, but we're running in docker container.
Use case may vary, but for us, it's totally sufficient, and none of the things you say are an issue.

Yeah, for the docker it makes sense. What I am and was aiming for with global setup/instantiation is local env development. If it is only in docker, I agree it does not make sense, but in local imho it does shine.

For the reference to the issue, here seems to be a related tool that somewhat accomplishes similar functionality: https://github.com/AndydeCleyre/zpy

I think we can track this in #1495.

Just for reference, where this really shines is when using code editors for specifying a default release. Currently, user needs to do its own mumbo-jumbo (as specified above) to have such environment. AFAIK most of editors do not allow for in-project venv read.

AFAIK most of editors do not allow for in-project venv read

I don't think this is true, e.g., VSCodes does discover virtual environments in the project directory. What are you referring to here?


Ariel Screen Saver not loading or playing any videos

When I've tried loading the Ariel screensaver on my iMac and MacBook, no images load as screen saver or in preview. They had worked previously, but will no longer load.

@adri430 First thing, please make sure you're running the latest version. https://github.com/JohnCoates/Aerial/releases/tag/v1.2
Second, please make sure the screen saver isn't being blocked by a firewall or proxy.
Let us know how you get on.

Same issue here; presenting first frame of the video, like it's a static image instead of a video.

@brandonedling Are you using the latest version? https://github.com/JohnCoates/Aerial/releases/tag/v1.2
Have you tried caching the videos?

Yep, confirmed that I'm using 1.2 and all videos are cached. I deleted them and re-downloaded them a couple days ago just to make sure cache wasn't corrupt, to no avail.

Yes, same issue on MacOS Sierra 10.12.

I'm having this issue on macOS Sierra 10.12.2
I tried download v1.2 and v1.2 beta 5

I hate Apple. I'm tired of explaining this bug. Last time. Never again.
There are multiple versions of the Swift libraries. Version 1.0, 1.1, 1.2, 2.0 and 3.0.
System Preferences will only load one version of the Swift libraries. Once it has loaded one version it will not load another. Whichever version of the Swift libraries it loads first, that's it until you close System Preferences, the process dies and start again from scratch.
So if you open System Preferences and load a screensaver that uses version 1.0 of the Swift libraries, System Preferences loads version 1.0 of the Swift libraries. And then any screensaver that uses 1.1 or 1.2 or 2.0 or 3.0 of the Swift libraries will show that "You cannot use the XXX screen saver with this version of macOS. Please contact the vendor to get a newer version of the screen saver." error.
Similarly if you open System Preferences to a screensaver that uses version 2.0 of the Swift libraries, System Preferences loads version 2.0 of the libraries and then any screensaver that uses 1.0, 1.1, 1.2 or 3.0 will display the "You cannot use the XXX screen saver with this version of macOS. Please contact the vendor to get a newer version of the screen saver." error.
And so on and so forth for every combination.
If you would like to help please log a bug with Apple here or here or bug an Apple employee on Twitter or phone your Senator or send smoke signals or whatever. I reported this to them back in March through every avenue I could think of. They have done a grand total of diddly-squat to fix it.


[BUG] Lightning Addresses no longer work

Describe the bug
LN Addresses do not appear to be functional now.  I noticed a problem with 0.12.6 and just updated to 0.12.8 but still doesn't seem to work.  I have had the LNURLP extension loaded and configured for quite a while, receiving payments to my account but it stopped working with one of the recent updates.
To Reproduce
I created a test account on https://demo.lnbits.com to verify that it is not isolated to my node.

I have created a test account - https://demo.lnbits.com/wallet?usr=3c8518c4915b4699a0bb0ee677c3876a
Enabled the LNURLP (Pay Links) extension
Created a new payment link with the address<EMAIL_ADDRESS>Viewing https://demo.lnbits.com/.well-known/lnurlp/test123 returns a JSON document with "address not found".
LN decoder pages such as<EMAIL_ADDRESS>also report the same error.

Expected behavior
The expected behavior would be a valid response with payment details?  (Not sure what the correct wording is.)  The functionality that used to work.
Additional context
The account linked above is a test account for this issue.  Feel free to play around with it, use it for troubleshooting, delete it if you like, whatever.

Payments to Lightning addresses appear to be working on https://demo.lnbits.com which is currently running
LNBits 0.12.9 and Pay links extension version 0.5.0  as of Sun Jul 28 05:51:52 UTC 2024
Tested:

https://demo.lnbits.com/lnurlp/link/bRRLRy
<EMAIL_ADDRESS>

Note: lnbits v0.12.6 does not work with Pay links 0.5.0 as noted by OP.

Thanks for testing
Closing

I'm not sure what test was performed but this issue is not fixed.

Are you on the latest LNbits version?

This is sending to the official demo instance (demo.lnbits.com) which @bitkarrot claims works.

@bitkarrot did you remove the alias<EMAIL_ADDRESS>after testing?

My tests address was not removed and still does not work.

@prusnak just retested, as of : Tue Jul 30 17:52:44 UTC 2024
LN Address is still there, it was working on sunday, does not seem to be working now. however LNURL is definitely working.

see test video here  as of : Tue Jul 30 17:52:44 UTC 2024
https://github.com/user-attachments/assets/e6650537-2af6-4d98-b5c2-e80b9daa9b1e

Oddly<EMAIL_ADDRESS>

I believe the issue is caused by a conflict between lnaddress and lnurlp in mapping the same route:

lunrlp: https://github.com/lnbits/lnurlp/blob/main/init.py#L20
lnaddress: https://github.com/lnbits/lnaddress/blob/main/init.py#L21

There is no deterministic way in which the extensions are loaded, therefore the unpredictable behavior.
Suggestion: remove lnaddress from demo server since.

lnaddress deactivated on demo. Everyone can pay @bitkarrot now.

Closing issue. Please re-open if you are still experiencing issues.

I can confirm, this fixed my issue on my own server.  This could be an issue for others also running both extensions together.  Should something be put in place to prevent both extensions from loading together causing this behavior?

I can confirm, this fixed my issue on my own server. This could be an issue for others also running both extensions together. Should something be put in place to prevent both extensions from loading together causing this behavior?

You are right. Re-opining the issue and assigning it to me.

Re-opining the issue and assigning it to me.

How do you plan to fix the issue? Is there a possibility to assign priorities to redirect paths? Or we just create a new mechanism that allows to mark two extensions as incompatible with each other?

I can confirm that on my 0.12.10 instance Paylinks did not work until I removed / disabled the LNAddress extension completely. I did not have it configured, just enabled.
I also had to restart the server after this.


Payment Instruction or check details should be shown on the order summary

Bug report
Title
Payment Instruction or check details should be shown on the order summary
Issue Description
Payment Instruction or check details should be shown on the order summary
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- configuration-> sales-> payment methods
2. step2- add instruction or send check to details in Payment methods
3. step3- place an order

Expected result
In order summary, Instruction or check details should be shown
Actual result
Currently, instructions are not showing

fixed


weird unset functionality

As far as I can see, laravel-mongodb overrides unset behavior to trigger drop functionality that makes a database query each time you run $moded->unset($field).  That means if you have some model that goes through multiple services and making unsets in some of the services for example
In service 1:
$model->unset('blocked');

in service 2:
if ($model->price > 2) {
    $model->unset('margin');
}

in service 3 you are doing an actual save of the model
$model->save();

all this will lead to 3 queries, right? For small projects, it maybe not be an issue, but for big projects, it's a huge overhead for the database.  and even worse, it's not a single transaction, and if execution interrupts somewhere it can bring side effects.
I tried to change the behavior of unset to not trigger the drop method but instead just to unset the attribute from the model, but in that case, during the model save, the model does not see changes because isDirty and getDirty methods do not compare with original data to find missing data and does not see changes.
It means you either you killing DB with multiple queries or can't unset the field with eloquent and only set it to null.
Is there any way to fix it???

Thank you for this feedback. I've also be surprised that such atomic operation could trigger a query to the database. Fixing this behavior will be a breaking change: projects will have to ensure that $model->save() is called after a $model->unset('blocked').
A solution would be to add an array of unset properties in the Model class and call $unset on this fields in Model::save(). The field name will have to be removed from this list of fields to unset when it is set again.

@GromNaN totally agrees with this, hope it'll be fixed by the library in some major release.
The workaround I decided to go with is to set the value to null  instead of unset, in some sense it's the same. It's better than fighting with laravel/library on a live project