centos7_docker_image_updater failing on RISC-V

Ref: https://ci.adoptium.net/job/centos7_docker_image_updater/504/execution/node/89/log/
+ docker build -t adoptopenjdk/ubuntu2004_build_image:linux-riscv64 --build-arg git_sha=2a029fd406c6f35f70c32ef5a814933fa11297ee -f ansible/docker/Dockerfile.Ubuntu2004-riscv64 .
ERROR: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/_ping": dial unix /var/run/docker.sock: connect: permission denied

Runs on docker&&linux&&riscv64 and has selected Scaleway machine 1 for that particular run

I've restarted the jenkins agent on the -1 machine in case it wasn't in the correct docker group before. I've been able to run docker operations from the jenkins user on the command line without issues, so hopefully it will be ok.
Looking at -8 it is in a similar situation where running id from the jenkins script console shows that it is NOT in the docker group, but logging into the machine.
All of the others seemed similar - I verified 2, 3, 8. On that basis I've restarted the agent on each of the boards 1 through 10

I've switched docker and dockerBuild for dockerX and dockerBuildX to avoid problems until someone can fix this on the machines.

Memo to self: Retry when the machines are refreshed as a part of https://github.com/adoptium/infrastructure/issues/3719


Owner/Musicmaster permissions not being granted even though ID has been set.

Please tick all applicable boxes.

[X] I am using Python 3.5 or higher (run python --version on the command line)
[X] I have followed the official guides to install the bot for my system
[X] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[X] The latest master version (1.9.7)
[ ] The latest review version

What type of issue are you creating?

[X ] Bug
[ ] Feature request
[X ] Question

Description of issue
Put my own ID as owner and as group MusicMaster (wich has auto skip enabled). Still unable to instaskip my sons.
Steps to reproduce

Run my bot
Try to skip
Get asked to add another skip to qeue so it will actually skip

Log file
musicbot.log
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.

As of the latest update the bot no longer insta-skips when you skip normally if you have permission to do so. This is so you are able to contribute to the vote skip. The new way to insta-skip is by running skip f


Can I only download low-resolution images?

After I run the program, the resolution of the downloaded images is 612. I don’t see the option to download other resolutions in the code, so I would like to ask if there is a way to download high-resolution images.

Hi, I want to ask which version you use.
I use v1.0.2 and no images are downloaded.

hi, I want download HD resolution images, do you have any idea? Help me if you found a solution, tks @ssometimes


Config

Codecov Report

Merging #16 into master will decrease coverage by 8.97%.
The diff coverage is 82.19%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
- Coverage   95.54%   86.56%   -8.98%
==========================================
  Files          19       19
  Lines         673      707      +34
==========================================
- Hits          643      612      -31
- Misses         30       95      +65

Flag
Coverage Δ

#integration
?

#unit
86.56% <82.19%> (-0.66%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.


C++ gRPC server implementation spawns uncontrolled number of threads

Is your feature request related to a problem? Please describe.
We tried using gRPC in one of our projects, a simple microservice that computes math models and returns result to user. We found out that during its work, service can spawn a lot of threads and most of them are waiting on gpr_cv_wait. After further investigation, we understood that it is caused by current ThreadManager implementation, function MainWorkLoop. And there is a comment about that. Uncontrolled thread creation causes huge memory consumption when using standard glibc allocator:

We decided to profile app with gperftools, which requires tcmalloc to make memory measurements, and accidentally found out that memory footprint is several times lower than when using standard linux allocator:

Here is a post that addresses this problem: https://habr.com/en/company/mailru/blog/534414/.
Describe the solution you'd like
As of now, SetResourceQuota won't limit thread spawning, only active threads in some specific moment. How about an idea that ThreadManager manages some underlying thread pool and user can pass it an integer to control threads. This way some problems will be resolved:

removing heavy operation on thread creation and deletion;
service can return RESOURCE_EXHAUSTED right away, if all threads in pool are busy;
there won't by huge and unclear memory footprints when using standard allocator, because number of threads is fixed (here is article about how glibc allocator works: https://sploitfun.wordpress.com/2015/02/10/understanding-glibc-malloc/), due to heavy thread creation, there are lots of memory arenas.

Describe alternatives you've considered
Heavy thread creation can't be avoided with current implementation and tcmalloc can be used to bypass memory consumption problems.

Esun and/or Vijay, can you please take a look at this?  What I find particularly interesting is that they continued to have this problem even when switching to the C++ async API, which I didn't think used the ThreadManager at all, so I'm not sure what's going on here.

Esun and/or Vijay, can you please take a look at this?  What I find particularly interesting is that they continued to have this problem even when switching to the C++ async API, which I didn't think used the ThreadManager at all, so I'm not sure what's going on here.

Maybe this will help a bit. As I understood when was browsing source code, in file src/cpp/server/server_builder.cc:220 in method BuildAndStart, there is always one initial completion queue created and then passed to Server class, then in its constructor sync_server_cqs_ != nullptr check passes and sync_req_mgrs_ gets initialized with single SyncRequestThreadManager instance and then in _Start(grpc::ServerCompletionQueue cqs, size_t num_cqs)_** it calls SyncRequestThreadManager's method Start which then calls Initialize of ThreadManager class.

Maybe this will help a bit. As I understood when was browsing source code, in file src/cpp/server/server_builder.cc:220 in method BuildAndStart, there is always one initial completion queue created and then passed to Server class, then in its constructor sync_server_cqs_ != nullptr check passes and sync_req_mgrs_ gets initialized with single SyncRequestThreadManager instance and then in _Start(grpc::ServerCompletionQueue cqs, size_t num_cqs)_** it calls SyncRequestThreadManager's method Start which then calls Initialize of ThreadManager class.

Can you mention your platform? I believe that I've seen a similar concern about this before which was on the Mac but want to know your platform for the most detailed information.

Can you mention your platform? I believe that I've seen a similar concern about this before which was on the Mac but want to know your platform for the most detailed information.

It is Centos 7.

It is Centos 7.

Are there any new regarding it? We also face this issue :(

@lieroz  the number of arena is limited, here's from your referred article
Number of arena’s: In above example, we saw main thread contains main arena and thread 1 contains its own thread arena. So can there be a one to one mapping between threads and arena, irrespective of number of threads? Certainly not. An insane application can contain more number of threads (than number of cores), in such a case, having one arena per thread becomes bit expensive and useless. Hence for this reason, application’s arena limit is based on number of cores present in the system.
For 32 bit systems:
Number of arena = 2 * number of cores.
For 64 bit systems:
Number of arena = 8 * number of cores.

The number is limited, but one thread can use quite a bit of it and it will be mostly equal in this case, cause each request does the same almost same things. For example, each thread consumes 20mb, total number of arenas is 56 cpus (in this case) * 8 multiplied by 20mb, that becomes 9gb of ram marked by allocator as used. Thus, memory is reused, but footprint is large. That is not the case with tcmalloc, cause it has tls cache for small objects and intermediate list for reusable memory. And allocator doesn’t give memory back in most cases until process exited.
When you have this in k8s cluster with limited memory and cpu for one pod, system will return all cpus for cpu count syscall, you get 400+ arenas on 4gb free mem for your container and it will be OOM killed.
Also this problem was on 3.10 kernel which is quite old, when tested on newer 5+ kernel, there were no such problems. I guess that current server implementation works for most people and to my mind google uses tcmalloc for all their projects.
Think that issue can be closed.


Leaderboard not showing when not logged in

You need to be logged in to be able to see the leaderboard.
We can either:

Change this behaviour
Add a message instead of the empty leaderboard saying "please login to see the results"


[SPARK-11921][SQL] fix nullable of encoder schema

Test build #46520 has started for PR 9906 at commit 8cf99b8.

Test build #46520 has finished for PR 9906 at commit 8cf99b8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46520/
Test PASSed.

Merged build finished. Test PASSed.

cc @marmbrus

Thanks, merging to master and 1.6


Default sort order is reversed and can't be changed

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
3.5.0
Last working release (if known):
Browser and Operating System:
Linux Firefox

Description of problem:
Documentation states that only valid sort_by option is state which is not a default sorting. Default is an entities order in configuration/YAML (doc: "Note that the order of this list matters").
Problem is that this default order of entities in graph is in reverse. sort_dir doesn't work either (it works only with sort_by: state).

Here is the screenshot with three states in order "A, C, B" that are shown in reverse order "B, C, A" in chart:

I deliberately ordered names and entities so that it is well visible that sorting is based on config order and not based on name, entity id or state (value).
Javascript errors shown in the web inspector (if applicable):

Additional information:
It is probably because in function sortBoxes the sorting has been done only in case of sort === 'state' and not otherwise. I'm not sure if sort_dir option would be useful at all without sort_by: state but the order should be fixed nevertheless IMHO.
I don't know where this reversal happens but one way to fix it is inside sortBoxes() function
diff --git a/src/utils.ts b/src/utils.ts
index 2cb63a8..8491a48 100644
--- a/src/utils.ts
+++ b/src/utils.ts
@@ -214,6 +214,8 @@ export function sortBoxes(parentBoxes: Box[], boxes: Box[], sort?: string, dir =
     } else {
       boxes.sort((a, b) => sortByParent(a, b, (a, b) => (a.state < b.state ? -1 : a.state > b.state ? 1 : 0)));
     }
+  } else {
+    boxes.reverse();
   }
   return boxes;
 }

Of course it would be better to find a real cause and fix it properly. Thoughts?

The real issue here is #234 . I will probably fix it in v4
I'll close this as a duplicate


One reaction button crash

Hello. If i want to add only one reaction buton I have a crash.
2020-05-20 09:20:56.986 7096-7096/? E/MessageQueue-JNI: java.lang.ArithmeticException: divide by zero         at com.github.pgreze.reactions.ReactionViewGroup.<init>(ReactionViewGroup.kt:56)         at com.github.pgreze.reactions.ReactionPopup$view$2.invoke(ReactionPopup.kt:30)         at com.github.pgreze.reactions.ReactionPopup$view$2.invoke(ReactionPopup.kt:17)         at kotlin.UnsafeLazyImpl.getValue(Lazy.kt:81)         at com.github.pgreze.reactions.ReactionPopup.getView(Unknown Source:2)         at com.github.pgreze.reactions.ReactionPopup.onTouch(ReactionPopup.kt:55)         at android.view.View.dispatchTouchEvent(View.java:12523)

@Alexinzaz better late than never, I just released a new version 1.2.2 with a fix for this crash.
Hope it can be helpful :)

thank you very much!


Remove CHARACTER_FILTER.filterCharacters function when notify dimension values.

What is the purpose of the change
remove the CHARACTER_FILTER.filterCharacters function when notify dimension values.
The CHARACTER_FILTER.filterCharacters was added because Prometheus gateway does not support invalid characters in metric names. However, for metric values, the Prometheus gateway does not have such restrictions.
Refer to the documentation: https://prometheus.io/docs/instrumenting/writing_exporters.
Therefore, removing this functionality will have no impact and will also support Chinese characters in metric values, making it easier to filter metric values with Chinese characters.

Reviewed by Chi on 05/12/24. Asked submitter questions

Reviewed by Chi on 05/12/24. Asked submitter questions
Hi, @davidradl
I have added a unit test. Could you please review the code again? thank you


Instrumentation started but can not hook anything.

can not hook anything in android 6.0
frida  10.0.5
[INFO] Attached to com.sankuai.meituan.takeoutnew
[INFO] Building injection...
[INFO] Instrumentation started...

Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

It's running but nothing happen.

Hey @z6101681
After the instrumentation has started, you need to use/interact with the app to start capturing the API calls, if it has not already started?
--
Nishant

I'm  pretty sure I have been interact with the app,but still nothing happen.

I'm not using the virtual,Does it affect the appmon hook?

Hey @z6101681, No it doesn't depend on the device type. It should work on both hardware as well as simulator/virtual devices. Does it happen with all the apps or just for some specific app?

I have been try three difference app at mine phone.
firmware:http://firmware.meizu.com/Firmware/Flyme/PRO_6/<IP_ADDRESS>/cn_beta/20170420000800/5cc1becc/update.zip
I use my own  frida scripts is working,I don't know why appmon did not working...

I hawe same problem on Windows.

Needs more info to reproduce the issue. Please reopen once more information is available.


Opening multiplayer tab when in offline mode crashes app

Error: not connected to server
at C:\Users\~\Documents\Projects\bar-lobby\node_modules\tachyon-client\dist\tachyon-client.js:206:24
at new Promise (<anonymous>)
at CommsAPI.request (C:\Users\~\Documents\Projects\bar-lobby\node_modules\tachyon-client\dist\tachyon-client.js:204:16)
at updateBattleList (http://localhost:5173/views/multiplayer/custom.vue:61:43)
at http://localhost:5173/views/multiplayer/custom.vue:53:51
at withAsyncContext (http://localhost:5173/@fs/C:/Users/~/Documents/Projects/bar-lobby/node_modules/.vite/deps/chunk-U53QPFLN.js?v=fcd51258:5343:19)
at setup (http://localhost:5173/views/multiplayer/custom.vue:53:27)
at callWithErrorHandling (http://localhost:5173/@fs/C:/Users/~/Documents/Projects/bar-lobby/node_modules/.vite/deps/chunk-U53QPFLN.js?v=fcd51258:180:18)
at setupStatefulComponent (http://localhost:5173/@fs/C:/Users/~/Documents/Projects/bar-lobby/node_modules/.vite/deps/chunk-U53QPFLN.js?v=fcd51258:5071:25)
at setupComponent (http://localhost:5173/@
```fs/C:/Users/~/Documents/Projects/bar-lobby/node_modules/.vite/deps/chunk-U53QPFLN.js?v=fcd51258:5034:36)

More or less ties in with #132

#132 implemented


[BEAM-12777] Removed current docs version redirect

This PR is a follow up of https://github.com/apache/beam/pull/16327
Removed the .htaccess redirect to a hardcoded URL with the current version of docs.

beam.apache.org/releases/javadoc/current/ stays as it is instead of redirecting to beam.apache.org/releases/javadoc/2.36.0/

See CI.md for more information about GitHub Actions CI.

@roger-mike - Is there a way to verify this is indeed working without the redirect?

@roger-mike - Is there a way to verify this is indeed working without the redirect?

I don't know how it can be tested, ./gradlew :website:serveWebsite doesn't serve the javadocs or the pydocs. I found this https://htaccess.madewithlove.com/ in this PR https://github.com/apache/beam/pull/12945 where they tried to do the same. It tests that the .htaccess is redirecting correctly, but I'm not sure if this is useful to test that the URL is NOT redirecting 🤔.

We can merge. Manually verify. And if it fails revert it. If we do that, I would like to do it at a time when you can be available to check the results.

We can merge. Manually verify. And if it fails revert it. If we do that, I would like to do it at a time when you can be available to check the results.

That sounds good @aaltay, if you set a time I can make myself available 👍

I meant to ask in a new comment:
Today 4pm, pacific time?
tomorrow, 9am, pacific time?
would these work?

9 AM PST works for me. I also sent you a message in the ASF slack, we can keep communicating there.

Merged. Changes should propagate to website.

It looks like there a is problem.
current is pointing to 2.36.0 docs (https://beam.apache.org/releases/javadoc/current/)
but the current version is 2.37.0 (https://beam.apache.org/releases/javadoc/2.37.0/)
Maybe the release process was not updated? (/cc @TheNeuralBit )


Views take around as much memory as object

I was playing around with some visualization on a large dataset, when I noticed some surprisingly high memory usage. I think I've narrowed it down to unexpected memory growth from taking views:
In [1]: import scanpy.api as sc

In [2]: %load_ext memory_profiler

In [3]: %memit adata = sc.read("bm.h5ad")
peak memory: 5317.54 MiB, increment: 5187.05 MiB

In [4]: %memit
peak memory: 2624.52 MiB, increment: 0.00 MiB

In [5]: %memit view = adata[:, (adata.var["n_cells_by_counts"] > 10000)]
peak memory: 5299.68 MiB, increment: 2675.16 MiB

In [6]: %memit
peak memory: 5080.07 MiB, increment: 0.00 MiB

My assumption here being: taking a view shouldn't cause noticeable growth in memory usage. I'm pretty sure it's not just how memory_profiler is counting objects, since top and ActivityMonitor pick this up as well.

Thank you for pointing this out! It's surprising to me. I extensively memory-profiled when introducing the functionality about a year ago.
Right now, I can only think of one thing that would cause this behavior as a result of the design of AnnData being not mature enough: the .uns annotations are deep copied... everything else uses numpy's views in the background.
The other reason for views, besides saving memory (if they work properly) is that one should be able to write to the data matrix of the underlying object, especially in backed mode, that is
adata[batch].X = function(adata[batch].X)

should modify the original data (see here).
Anyways, this is a severe issue and I'll definitely fix it soon if it persists.

In the example I gave, I don't think there was anything in the uns field. Just to be sure, I've run it again with a AnnData object that definitely doesn't have anything in the uns field and gotten similar results.
Question about the syntax for views. What should happen in the following code?
view = adata[adata.obs["total_counts"] > 500, :]
view.X[view.X != 0] = 0
print(view.X.sum())
print(adata[adata.obs["total_counts"] > 500, :].X.sum())

My assumption is the change on the view should be replicated in the base object. That is, both print statements should return 0.

Observed the same when filtering an adata object. For demonstration purposies, here, the same filter is applied over and over again:
import numpy as np
import scanpy.api as sc
import pandas as pd
import numpy as np
import sys
from pickle import dumps

mat = np.ones((10000, 5000))
obs = pd.DataFrame().assign(n_counts = range(10000))

adata = sc.AnnData(mat, obs)

for i in range(10):
    %time adata = adata[adata.obs['n_counts'] > 200, :]
    print("Object size: {}M".format(len(dumps(adata))/1e6))

CPU times: user 35.7 ms, sys: 61.5 ms, total: 97.2 ms
Wall time: 95.5 ms
Object size: 396.298382M
CPU times: user 132 ms, sys: 147 ms, total: 278 ms
Wall time: 277 ms
Object size: 592.445935M
CPU times: user 165 ms, sys: 203 ms, total: 369 ms
Wall time: 368 ms
Object size: 788.593488M
CPU times: user 201 ms, sys: 261 ms, total: 462 ms
Wall time: 462 ms
Object size: 984.741041M
CPU times: user 265 ms, sys: 276 ms, total: 542 ms
Wall time: 542 ms
Object size: 1180.888594M
CPU times: user 313 ms, sys: 342 ms, total: 655 ms
Wall time: 656 ms
Object size: 1377.036147M
CPU times: user 356 ms, sys: 378 ms, total: 734 ms
Wall time: 733 ms
Object size: 1573.1837M
CPU times: user 380 ms, sys: 463 ms, total: 843 ms
Wall time: 841 ms
Object size: 1769.331253M
CPU times: user 432 ms, sys: 485 ms, total: 917 ms
Wall time: 917 ms
Object size: 1965.478806M
CPU times: user 496 ms, sys: 683 ms, total: 1.18 s
Wall time: 1.18 s
Object size: 2161.626359M

Ok, something really shady is going on, which I was not aware of. I'll need to take a deeper look at views of AnnData. Or, @Koncopd, do you have some bandwidth to shed some light on this?

I've been doing a little bit of digging on this, and have some suspicious about what's causing it.
First, a view of a view stores it's parent view in _adata_ref. This means those intermediates won't get gc-ed leading to the linear increase in memory usage in the example above. Demo:
import numpy as np
import scanpy as sc

a = sc.AnnData(np.ones((2, 2)))
v1 = a[0:2, 0:2]
v2 = v1[0:2, 0:2]
v1.isview and v2.isview  # True
v2._adata_ref is v1  # True

Second, I think that each view can be getting a copy of the expression matrix. In particular, line 752 will make a copy when the array is accessed with a boolean array
https://github.com/theislab/anndata/blob/fc7f3cb06c191aff4fcad6af88f0c3012d7d1a65/anndata/base.py#L748-L752
Here's an example of the memory increasing:
import numpy as np
import scanpy as sc

a = sc.AnnData(np.ones((5000, 5000)))

# When view is taken with a slice, no additional memory is used
sc.logging.print_memory_usage()  # Memory usage: current 0.28 GB, difference +0.28 GB
v1 = a[0:5000, 0:5000]
sc.logging.print_memory_usage()  # Memory usage: current 0.28 GB, difference +0.00 GB
v2 = v1[0:5000, 0:5000]
sc.logging.print_memory_usage()  # Memory usage: current 0.28 GB, difference +0.00 GB

# Taken with a boolean array, memory use increases
v1 = a[np.ones(5000, dtype=bool), 0:5000]
sc.logging.print_memory_usage()  # Memory usage: current 0.38 GB, difference +0.09 GB
v2 = v1[np.ones(5000, dtype=bool), 0:5000]
sc.logging.print_memory_usage()  # Memory usage: current 0.47 GB, difference +0.09 GB

My idea for how this could be solved is not to bother actually subsetting X until it's accessed, and just storing the subsetting index until then. This would be updated on every subsequent subset, and should always be an index into the "actual" AnnData.

I don't know whether we discussed this on Slack already or not, Isaac. But your idea is perfect. I think we also discussed on Slack that we don't want _adata_ref to ever be a view, right? So that we don't get this recursion (https://github.com/Cellarity/cifra/commit/a696618a13c8c96fb35f700bfd811061d8884497). Then the memory increase should be gone.

Great. I'm pretty sure what needs to be done is write out how to resolve all the different indexing types (i.e. slice of a slice should be a slice, int array of a slice should be an int array, etc.).


IntelliJ IDEA + scratch writing = dependency issues

I'm trying to follow the tutorial as written, and in the Working a Getting Started guide with IntelliJ IDEA guide, it does say near the bottom:
In case you’d like to start with an empty project and copy-and-paste your way through the guide, create a new Maven or Gradle project in the Project Wizard
Which is what I did.
Unfortunately, there's no other mention of how to inject the dependencies needed after that, either on the main tut page or the IntelliJ page, so there's trouble as soon as we're writing up the resource controller.
I suggest an expandable section somewhere in there, to clue in the random IntelliJ guy taking the long road.

Okay, nevermind. I opened a new Spring project, which is entirely different, and also incorrect.


remove the tls.Config from the quic.Config

The tls.Config now is a separate parameter to all Listen and Dial functions in the quic package.

Codecov Report

Merging #713 into master will decrease coverage by 0.04%.
The diff coverage is 89.29%.

@@            Coverage Diff             @@
##           master     #713      +/-   ##
==========================================
- Coverage   91.25%   91.22%   -0.04%
==========================================
  Files          81       80       -1
  Lines        5637     5637
==========================================
- Hits         5144     5142       -2
- Misses        309      310       +1
- Partials      184      185       +1

Impacted Files
Coverage Δ

h2quic/client.go
86.9% <100%> (ø)
:arrow_up:

client.go
89.94% <100%> (+0.19%)
:arrow_up:

session.go
88.61% <100%> (+0.03%)
:arrow_up:

h2quic/server.go
62.69% <66.67%> (-0.18%)
:arrow_down:

server.go
91.58% <75%> (-0.93%)
:arrow_down:

crypto/config_for_client_1.8.go

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1db20be...dfc6a8d. Read the comment docs.

The problem was a missing re-initializiation of the quic.Config between the handshake RTT tests. Northing worth reviewing, I'll merge directly if the CIs pass.


FEATURE REQUEST: Initial sync choice TESTNET vs MAINNET

When someone installs Raspiblitz for the first time the time required by the download of the complete MAINNET is an unnecessary barrier all he wants is play with his Blitz ASAP, would be great to have the option "sync TESTNET" vs "sync MAINNET" at first start.

Because we the recent refactoring of the setup options for the v1.7.1 we decided to not have the "TESTNET" as an option from the beginning and offer Testnet & Signet as an option you can run in parallel once MAINNET is running.
I know that makes it not easy&fast to setup .. but making sure that the whole setup process is working now with also c-lightning coming as an option with v1.7.1 would double all the testing efforts. Keep in mind that also with v1.8 we plan to introduce another optional setup process with the WebUI next to the SSH - fo first we need to get that stable.
Once the new setup processes are implemented and well tested we might take a look how to provide a quick testnet setup without mainnet .. but I will push this up to v1.8.1 to take another look.

Thank you @rootzoll, makes sense.


Doesn't resolve correct blazor component usings/imports

Issue Description
Steps to Reproduce

Create a new dotnet blazor server project (dotnet new blazorserver -o test)
Open the project in Visual Studio Code, with the C# extension installed
Open any file which uses components (such as Shared/MainLayout.razor) and the _Imports.razor file

(Note that this does not happen in Visual Studio 2019)
Expected Behavior
This extension doesn't show any errors for the generated code
Actual Behavior
All components used in Blazor html markup and in C# @code sections (not present in the generated code) are highlighted in blue or red (info/error) because the extension fails to identify and resolve correct @using directives in the top-level _Imports.razor file
Update
I have disabled all extensions except for the OmniSharp C# one and it is still reporting every single component usage as an error.
Logs
OmniSharp log
OmniSharp log

Starting OmniSharp server at 29.5.2021, 21:14:17
    Target: c:\Users\user\Documents\test\test
OmniSharp server started.
Path: c:\Users\user.vscode\extensions\ms-dotnettools.csharp-1.23.12.omnisharp\1.37.10\OmniSharp.exe
PID: 11868
    Starting OmniSharp on Windows 6.2.9200.0 (x64)

    DotNetPath set to dotnet

    Located 2 MSBuild instance(s)
        1: Visual Studio Community 2019 16.9.31205.134 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin"
        2: StandAlone 16.11.0 - "c:\Users\user\.vscode\extensions\ms-dotnettools.csharp-1.23.12\.omnisharp\1.37.10\.msbuild\Current\Bin"

    Registered MSBuild instance: Visual Studio Community 2019 16.9.31205.134 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin"

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.Completion.CompletionOptionsProvider, Order: 0

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140

    Detecting Cake files in 'c:\Users\user\Documents\test\test'.

    Could not find any Cake files

    No solution files found in 'c:\Users\user\Documents\test\test'

    Queue project update for 'c:\Users\user\Documents\test\test\test.csproj'

    Detecting CSX files in 'c:\Users\user\Documents\test\test'.

    Could not find any CSX files

    Configuration finished.

    Omnisharp server running using Stdio at location 'c:\Users\user\Documents\test\test' on host 7776.

    Loading project: c:\Users\user\Documents\test\test\test.csproj

    Successfully loaded project file 'c:\Users\user\Documents\test\test\test.csproj'.

     Is there any other workaround besides switching to VS?

same here.
_Imports.razor: error finding .Shared folder;
App.razor: Router component can't be found;
Code template generated by dotnet new command
Compiling without a problem.

Hi All, had the same issue. I found a work-around in VS Code by downgrading from the current version 1.23.12 to 1.23.11. You can do this in the the extensions panel by clicking on the config button for the C# extension and click 'Install another version', then select the previous version. Version 1.23.12 was released about 12 days ago, and obviously has broken razor intellisense

Hi All, had the same issue. I found a work-around in VS Code by downgrading the C# extension from the current version 1.23.12 to 1.23.11. You can do this in the the extensions panel by clicking on the config button for the C# extension and click 'Install another version', then select the previous version. Version 1.23.12 was released about 12 days ago, and obviously has broken razor intellisense

1.23.9 worked for me! Thank you!

Hi All, had the same issue. I found a work-around in VS Code by downgrading the C# extension from the current version 1.23.12 to 1.23.11. You can do this in the the extensions panel by clicking on the config button for the C# extension and click 'Install another version', then select the previous version. Version 1.23.12 was released about 12 days ago, and obviously has broken razor intellisense

Had the same issue, downgraded to 1.23.11 and looks like it is working with the downgrade workaround.

Could you all verify if this is what you're running into: https://github.com/OmniSharp/omnisharp-vscode/issues/4573
Specifically the mentioned NRE in the OmniSharp log:

@NTaylorMullen I attached my OmniSharp log in my issue. It doesn't throw an unhandled exception of any kind, and I'm targeting .NET 5, not 6, so I don't think #4573 relates to this one (this appears to describe the same issue though: dotnet/aspnetcore#33350)

Oddly enough downgrading to 1.23.11 fixed the issue, but then I upgraded back to 1.23.12 and it keeps working. 😵

Having similar issue. New BlazorWasm application has many errors/warnings. Downgrading to 1.23.11 fixes the issue. (reinstalling 1.23.12 just brought the errors back)

1.23.11 works for me also. Hope it get fixed by 1.23.13 release.

It seems the tracking work is here: #33858

This issue seems to be back with the new v2 C# extension. The  _Imports.razor file it's complete ignored, then the intellisense go nutz.
The downgrade it's a working around, going back to v1.26.0 solved it for me.

This issue seems to be back with the new v2 C# extension. The _Imports.razor file it's complete ignored, then the intellisense go nutz.
The downgrade it's a working around, going back to v1.26.0 solved it for me.

Same for me.

same issue here.

Can reproduce as of the latest prerelease. Also getting 'RenderTreeBuilder' does not contain a definition for 'AddComponentParameter' and no accessible extension method 'AddComponentParameter' accepting a first argument of type 'RenderTreeBuilder' could be found (are you missing a using directive or an assembly reference?) repeatedly from intellisense.

tagging @davidwengier for a Razor issue

Can reproduce as of the latest prerelease. Also getting 'RenderTreeBuilder' does not contain a definition for 'AddComponentParameter' and no accessible extension method 'AddComponentParameter' accepting a first argument of type 'RenderTreeBuilder' could be found (are you missing a using directive or an assembly reference?) repeatedly from intellisense.

https://github.com/dotnet/razor/pull/9265 fixes this.
Will see if I can repro the other issues, but would appreciate any logs from anyone reproing this issue in the latest C# extension version.

@davidwengier Thanks for looking into this. Here is the Razor Log from my project, where IntelliSense works fine in Visual Studio, but not in VS Code (Preview).
razor-logs-from-my-project.txt

Project structure (stripped out all unnecessary context)
.
├── App.razor
├── Program.cs
├── Servicios.cs
├── WebIndemnizacionesVM.csproj
├── _Imports.razor
├── appsettings.json
├── Shared
│   ├── MainLayout.razor
│   ├── Componentes
│   │   ├── NavMenu.razor
│   │   ├── SideBar.razor

_Imports.cs
@using System.Net.Http
@using Microsoft.AspNetCore.Authorization
@using Microsoft.AspNetCore.Components.Authorization
@using Microsoft.AspNetCore.Components.Forms
@using Microsoft.AspNetCore.Components.Routing
@using Microsoft.AspNetCore.Components.Web
@using Microsoft.AspNetCore.Components.Web.Virtualization
@using Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage
@using Microsoft.JSInterop
@using WebIndemnizacionesVM
@using WebIndemnizacionesVM.Shared
@using WebIndemnizacionesVM.Shared.Componentes
@using WebIndemnizacionesVM.Data
@using WebIndemnizacionesVM.Data.Microservicios
@using Compartido.DTO.Microservicios.Login
@using System.ComponentModel.DataAnnotations
@using Blazored.Toast
@using Blazored.Toast.Services
@using Blazored.Modal
@using Blazored.Modal.Services
@using MudBlazor
@using CurrieTechnologies.Razor.SweetAlert2
@using Compartido.Utils

MainLayout.razor

Razor-logs.log

@blackshot To set verbosity, open File -> Preferences -> Settings and search for razor.trace

Thanks, i updated the comment with the verbose logs

Thanks for the logs @blackshot
The good news is that the red component tags are fixed by https://github.com/dotnet/vscode-csharp/pull/6304, so should be in a release soon.
The bad news is there is nothing in the logs that indicates any problem with Razor tooling, which means the NavMenu not being discovered is caused by something else. The _Imports.razor file seems to be being processed properly, because things like PageTitle are discovered fine, but for whatever reason when we ask Roslyn for the list of components that are available, NavMenu must not be in the list. You could try attaching the project.razor.vscode.json file, from the obj directory, but I suspect that will just show that the NavMenu component isn't in the list.
Is there anything "interesting" about NavMenu? An @inherits or @namespace directive perhaps? If you open NavMenu.razor in VS Code are there any errors reported in it? Also, in the file layout you included it looks like maybe the "Componentes" folder starts with a space? Or is that just a typo?
@PeterDraex thank you also for the logs. Other than a couple of requests at the start where folding range requests failed (thats trying to get the areas that can be collapsed with the little arrows in the editor margin) everything looks fine, but perhaps there are requests that are supposed to be there that never happened. When you say "IntelliSense", what exactly do you mean? Do you mean the light bulb suggestions, or the completion suggestions as you type? The logs you attached don't seem to have any typing in them, but I can see a few light bulb requests. Unfortunately nothing that indicates a problem, though to be fair we also don't log if we're returning 0 or 100 lightbulb actions. If the issue is with lightbulbs no showing, which one(s) were you expecting? Unfortunately for various technical reasons VS and VS Code are not quite at parity with which Razor lightbulbs they support, specifically the "Add using" can't be offered in VS Code.
The "no project context" thing can be ignored, VS Code doesn't support that (yet!), and it doesn't indicate a problem. Just means there wasn't a project context sent with the request, so we'd operate on the default context. Totally expected in VS Code.

@davidwengier
Oh, I tried to make the logs cleaner (by restarting VS Code, and sending only the beginning) and it looks like the important parts got left out. I'll describe the issue and send new logs now.
My file Purchase.razor begins like this:
@page "/inventory/purchase"
@using System.Collections.Immutable
@using Microsoft.AspNetCore.Components.Web

@code {
    SupplierInInventoryPurchase[] suppliers = Array.Empty<SupplierInInventoryPurchase>();

    Layout.ContentTemplate.BreadcrumbItem[] breadcrumbs = new Layout.ContentTemplate.BreadcrumbItem[]
    {
        new Layout.ContentTemplate.BreadcrumbItem("Inventory"),
        new Layout.ContentTemplate.BreadcrumbItem("Purchase", "/inventory/purchase"),
    };

VS Code is reporting a problem:

The type or namespace name 'ContentTemplate' does not exist in the namespace 'Layout' (are you missing an assembly reference?)RoslynCS0234

When I locate my cursor after Layout.ContentTemplate. and press CTRL+Space, it shows general keyword suggestions, not relevant in the context. When I click on BreadcrumbItem or Layout and press F12, I get a message that no definition is found.
Here's a new log file, while the error was displayed, I tried bringing up the suggestions and going to definition. Is it helpful?
razor-logs2.txt

Thanks for that info, thats very helpful. Unfortunately I'm not sure how helpful I can be. I can think of two possibilities:

Given that your "type or namespace not found" error comes from a C# block, not a component, the most likely explanation is there are multiple things called "Layout" in scope, and Roslyn is binding to one you don't expect. eg, there is a Layout.razor in your client project, which would mean a type called "Layout", as well as the folder called "Layout" in AdminClient, which would create a namespace called "Layout". Is client referenced from AdminClient? And more importantly, is the "Client.Layouts" namespace included in the _Imports.razor in AdminClient?

For some reason ContentTemplate.razor is not being discovered or compiled properly by Razor. I can see it in the logs, so it appears to be in the project correctly etc. Similar to the questions above, does it have errors in it if you open it? Anything in it that would affect compilation, like a @namespace or @inherits  directive?

Unfortunately without access to the code it will be hard to diagnose this one with just the logs. Don't suppose its open source? :)
One other option is to use the "Razor: Show Razor CSharp" function in VS Code when you have Purchase.razor open. That will show you the compiled C#, and you'll be able to see all of the using statements etc. that are in scope, which might help narrow it down. You could even try copying the code out of that window, and putting it in a new .cs file in the project, and maybe Roslyn will even highlight which parts are ambiguous, or not found. Potentially doing that with ContentTemplate.razor might be illustrative too, perhaps checking that the namespace declared in it is the one you expect.
To be very clear here, I'm not saying this isn't a Razor bug, or that it's your codes fault, just that it seems to be something to do with the compiled files, and the compiler doesn't have any logs we can access. The project state seems to be correct from the logs, though if the namespace in the generated files are wrong, then clearly that's not the case.

Thanks for the logs @blackshot
The good news is that the red component tags are fixed by #6304, so should be in a release soon. The bad news is there is nothing in the logs that indicates any problem with Razor tooling, which means the NavMenu not being discovered is caused by something else. The _Imports.razor file seems to be being processed properly, because things like PageTitle are discovered fine, but for whatever reason when we ask Roslyn for the list of components that are available, NavMenu must not be in the list. You could try attaching the project.razor.vscode.json file, from the obj directory, but I suspect that will just show that the NavMenu component isn't in the list.
Is there anything "interesting" about NavMenu? An @inherits or @namespace directive perhaps? If you open NavMenu.razor in VS Code are there any errors reported in it? Also, in the file layout you included it looks like maybe the "Componentes" folder starts with a space? Or is that just a typo?
@PeterDraex thank you also for the logs. Other than a couple of requests at the start where folding range requests failed (thats trying to get the areas that can be collapsed with the little arrows in the editor margin) everything looks fine, but perhaps there are requests that are supposed to be there that never happened. When you say "IntelliSense", what exactly do you mean? Do you mean the light bulb suggestions, or the completion suggestions as you type? The logs you attached don't seem to have any typing in them, but I can see a few light bulb requests. Unfortunately nothing that indicates a problem, though to be fair we also don't log if we're returning 0 or 100 lightbulb actions. If the issue is with lightbulbs no showing, which one(s) were you expecting? Unfortunately for various technical reasons VS and VS Code are not quite at parity with which Razor lightbulbs they support, specifically the "Add using" can't be offered in VS Code.
The "no project context" thing can be ignored, VS Code doesn't support that (yet!), and it doesn't indicate a problem. Just means there wasn't a project context sent with the request, so we'd operate on the default context. Totally expected in VS Code.

(adding some components to the context in order to understand NavMenu.razor)
.
├── WebIndemnizacionesVM.sln
├── Compartido (ClassLib)
├── DAS (ClassLib)
└── WebIndemnizacionesVM (Blazor Server)
    ├── App.razor
    ├── Program.cs
    ├── Shared
    ├── WebIndemnizacionesVM.csproj
    ├── _Imports.razor
    ├── appsettings.Development.json
    ├── appsettings.json
    └── Shared
        ├── MainLayout.razor
        ├── LoginCascading.razor
        ├── MainLayout.razor
        ├── Protegido.razor                 (used by NavMenu.razor [should be imported globally])
        └── Componentes
            ├── Badge.razor
            ├── Carta.razor
            ├── CartaMaterial.razor
            ├── CrearCuentaBancariaModal.razor
            ├── NavMenu.razor
            ├── SeleccionOrdenModal.razor
            ├── SideBar.razor
            ├── SpinnerHDI.razor
            └── VerAnotacionesModal.razor
            └── SideBarComps                (used namespace by NavMenu.razor)
                ├── NavItem.razor           (used by NavMenu.razor)
                └── NavItemDropdown.razor   (used by NavMenu.razor)

I think there is nothing special in NavBar.razor, but razor couldn't find "WebIndemnizacionesVM.Shared.Componentes.SideBarComps" namespace when i opened the NavBar.razor file.

Could not find "Protegido" which is imported in _Imports.razor

NavBar.razor
@using Compartido.DTO.Microservicios.PermisosWebIndemnizacionVM;
@using WebIndemnizacionesVM.Shared.Componentes.SideBarComps
@inject NavigationManager NM;
@inject SessionService ss;

@code{
    [CascadingParameter]
    RespuestaLogin? login { get; set; }

    [CascadingParameter]
    Permisos? permisos { get; set; }
}

        <button class="navbar-toggler button-small hdi-btn-tertiary" type="button" data-bs-toggle="collapse" data-bs-target="#menuMobile" aria-controls="menuMobile" aria-expanded="false" aria-label="Toggle navigation">

        </button>

                @if (permisos is null)
                {
                    <SpinnerHDI />
                }
                else
                {
                    <Protegido Permiso="BAND-GEST">
                        <NavItem Icono="fa fa-check" Texto="Casos gestionados" Url="" />
                    </Protegido>

                    <Protegido Permiso="SEC-PT">
                        <NavItemDropdown Icono="fa-solid fa-car-burst" Texto="Pérdidas Totales">
                            <Protegido Permiso="BAND-PEND">
                                <NavItem Icono="fa fa-edit" Texto="Casos pendientes" Url="perdidas-totales/" Match="NavLinkMatch.All" />
                            </Protegido>
                        </NavItemDropdown>
                    </Protegido>

                    <Protegido Permiso="SEC-PP">
                        <NavItemDropdown Icono="fas fa-building" Texto="Pérdidas Parciales">
                            <Protegido Permiso="BAND-PEND-PP">
                                <NavItem Icono="fa fa-check" Url="perdidas-parciales/" Texto="Casos pendientes" Match="NavLinkMatch.All" />
                            </Protegido>
                        </NavItemDropdown>
                    </Protegido>

                    <Protegido Permiso="BAND-AUTH">
                        <NavItem Icono="fa fa-lock" Texto="Pendientes autorización" Url="bandeja-autorizacion" />
                    </Protegido>
                    <Protegido Permiso="BAND-BLOQ">
                        <NavItem Icono="fa fa-ban" Texto="Casos bloqueados" Url="bandeja-bloqueados" />
                    </Protegido>
                }

                @*<NavItemDropdown Icono="fa-solid fa-car-burst" Texto="Submenu links" >
                    <NavItem Url="subitems/uno" Texto="Sub item 1" />
                    <NavItem Url="subitems/dos" Texto="Sub item 2" />
                </NavItemDropdown>

                <NavItem Icono="fa-solid fa-house-crack" Texto="Recepción de vehículos" Url="recepcion-vehiculo" />
                <NavItem Icono="fa-solid fa-circle-dollar-to-slot" Texto="Pagos disponibles" Url="pagos-disponibles" />*@

                @*<NavItem Icono="fa fa-user" Texto="Mi perfil" Url="mi-perfil" />*@
                <NavItem Icono="fa fa-lock" Texto="Cerrar sesión" Url="#"<EMAIL_ADDRESS>

        <form class="d-flex align-items-center hidden-xs hidden-sm" role="search">
            @*

                <input type="text" class="hdi-form-small-input m-0" placeholder="Buscar">

*@
            @if (login is not null)
            {

                    <button class="button-small hdi-btn-primary" type="button" data-bs-toggle="dropdown" aria-expanded="false">
                         Bienvenido @login?.Usuario.Nombre
                    </button>

                        @*
 Mi Perfil
*@

<a class="dropdown-item" href="#"<EMAIL_ADDRESS>class="fa fa-lock mr-1"> Cerrar sesión

            }
        </form>

check this out, while i was writting this, i just restarted vscode with NavBar.razor file opened in order to generate a clean log with the error. and this happened...

It loaded well WebIndemnizacionesVM.Shared.Componentes.SideBarComps namespace and some other components that didn't loaded well the first time.

Indeed, its odd that you would get a green tag with a "could not find component" warning, as both come from data the compiler provides us. What might have happened is that after the project first loaded, and everything was fine, something updated the project.razor.vscode.json file and left out those components for some reason, but VS Code doesn't refresh colors very often.
FYI @phil-allen-msft since I'm OOF for a few weeks. Looks like something odd happening with component discovery, potentially inconsistent project loading and Roslyn giving us mixed info for the project.razor.vscode.json file, or possibly an issue with different events fighting over writing that file. Seems like its inconsistent and will probably be hard to repro unfortunately. A slightly more complication project that normal might help

Also, in the file layout you included it looks like maybe the "Componentes" folder starts with a space? Or is that just a typo?

it was a typo writting here in github, forldername is fine

just in case is helpful, here are my enabled extensions at the moment bug happened.
$ code --list-extensions --show-versions | % { "code --install-extension $_" }

code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>code --install-extension<EMAIL_ADDRESS>

After update to new version of VS Code Insiders, I am seeing a System.InvalidOperationException in C# Output window.

Expand logs
Using dotnet configured on PATH
Dotnet path: C:\Program Files\dotnet\dotnet.exe
Activating C# + C# Dev Kit + C# IntelliCode...
waiting for named pipe information from server...
[stdout] {"pipeName":"\\\\.\\pipe\\70987ca1-88df-4050-a63c-98fd16286a13"}
received named pipe information from server
attempting to connect client to server...
client has connected to server
[Info  - 1:15:06 PM] [Program] Language server initialized
[Error - 1:15:16 PM] [LanguageServerHost] System.InvalidOperationException: Was not able to get hello world response from remote - line 39
   at Roslyn.Utilities.Contract.Fail(String message, Int32 lineNumber) in /_/src/Workspaces/SharedUtilitiesAndExtensions/Compiler/Core/Utilities/Contract.cs:line 154
   at Microsoft.CodeAnalysis.LanguageServer.BrokeredServices.Services.HelloWorld.RemoteHelloWorldProvider.SayHelloToRemoteServerAsync(CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Microsoft.CodeAnalysis.LanguageServer/BrokeredServices/Services/HelloWorld/RemoteHelloWorldProvider.cs:line 39
   at Microsoft.CodeAnalysis.LanguageServer.BrokeredServices.ServiceBrokerFactory.CreateAndConnectAsync(String brokeredServicePipeName) in /_/src/Features/LanguageServer/Microsoft.CodeAnalysis.LanguageServer/BrokeredServices/ServiceBrokerFactory.cs:line 82
   at Microsoft.CommonLanguageServerProtocol.Framework.QueueItem`3.StartRequestAsync(TRequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Microsoft.CommonLanguageServerProtocol.Framework/QueueItem.cs:line 136
[Error - 1:16:36 PM] [LanguageServerHost] System.ArgumentException: Range={ Start={ Line=111, Character=37 }, End={ Line=900, Character=0 } }. text.Length=29910. text.Lines.Count=785
 ---> System.ArgumentOutOfRangeException: The requested line number 900 must be less than the number of lines 785. (Parameter 'Line')
   at Microsoft.CodeAnalysis.Text.TextLineCollection.GetPosition(LinePosition position) in /_/src/Compilers/Core/Portable/Text/TextLineCollection.cs:line 67
   at Microsoft.CodeAnalysis.Text.TextLineCollection.GetTextSpan(LinePositionSpan span) in /_/src/Compilers/Core/Portable/Text/TextLineCollection.cs:line 78
   at Microsoft.CodeAnalysis.LanguageServer.ProtocolConversions.RangeToTextSpan(Range range, SourceText text) in /_/src/Features/LanguageServer/Protocol/Extensions/ProtocolConversions.cs:line 298
   --- End of inner exception stack trace ---
   at Microsoft.CodeAnalysis.LanguageServer.ProtocolConversions.RangeToTextSpan(Range range, SourceText text) in /_/src/Features/LanguageServer/Protocol/Extensions/ProtocolConversions.cs:line 298
   at Microsoft.CodeAnalysis.LanguageServer.Handler.SemanticTokens.SemanticTokensHelpers.ComputeSemanticTokensDataAsync(ClientCapabilities capabilities, Document document, Range[] ranges, ClassificationOptions options, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Handler/SemanticTokens/SemanticTokensHelpers.cs:line 85
   at Microsoft.CodeAnalysis.LanguageServer.Handler.SemanticTokens.SemanticTokensHelpers.HandleRequestHelperAsync(IGlobalOptionService globalOptions, SemanticTokensRefreshQueue semanticTokensRefreshQueue, Range[] ranges, RequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Handler/SemanticTokens/SemanticTokensHelpers.cs:line 50
   at Microsoft.CodeAnalysis.LanguageServer.Handler.SemanticTokens.SemanticTokensRangeHandler.HandleRequestAsync(SemanticTokensRangeParams request, RequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Protocol/Handler/SemanticTokens/SemanticTokensRangeHandler.cs:line 45
   at Microsoft.CommonLanguageServerProtocol.Framework.QueueItem`3.StartRequestAsync(TRequestContext context, CancellationToken cancellationToken) in /_/src/Features/LanguageServer/Microsoft.CommonLanguageServerProtocol.Framework/QueueItem.cs:line 176
[Error - 1:16:36 PM] Request textDocument/semanticTokens/range failed.
  Message: Range={ Start={ Line=111, Character=37 }, End={ Line=900, Character=0 } }. text.Length=29910. text.Lines.Count=785
  Code: -32000
[object Object]

@blackshot, @PeterDraex no resolution on this?
@davidwengier I'm facing the same issue right now and my project is open. I've created a snapshot branch here.
It's working like a charm in VS, hit this issue as I'm trying out VS Code as alternative:

Clone a fresh repo
Restore MAUI workloads
Rebuild the solution, first time it takes a while
Open a file - EventComponent.razor will do.

Symptoms seem consistent with what's described here. Specifically:

_Imports.razor usings aren't resolved
Inline components (no code behind class) don't seem to be registered as namespaces by the compiler.
Custom components are not resolved (RZ10012) - this is true even if I add the relevant using in the same file.

If you need something else to debug this, please share.

@achobanov I'm still experiencing the issue as well

@achobanov do you have a project.razor.vscode.bin folder in obj\Debug\<tfm>? If so, how big is it?
When I cloned your repo locally, I couldn't get anything restoring or building, but I suspect that is due to missing .NET SDKs. Your global.json targets 5.0 (which VS Code seems to tell me is invalid 🤷♂) so thats not very surprising, as my machine is definitely not "clean" when it comes to the various builds I have installed. I also got errors about targeting net6.0-androind which is apparently out of support. If I remove the global.json then things restore properly, but components are still not discovered in the EMS.Judge.UI project. I can tell this because the project.razor.vscode.vin file is about 2KB. Upgrading things to .NET 8 (literally just replacing the "7" with an "8" in the EMS.Judge.UI.csproj and the "6" with an "8" in the EMS.Witness.csproj to get rid of the android warnings, I then got a project.razor.vscode.bin file of 800+KB and everything seemed to work fine when opening the EventComponent.razor file. No errors, all components were green etc.
Unfortunately we don't have a good story for logging anything when the project.razor.vscode.bin file is missing information. Generally speaking it means the Roslyn project can't see the types/components in question, or maybe Roslyn can but the compiler rejected the compilation for some other reason. Another thing to check that might indicate what is happening is to run the "Show Razor CSharp" command in VS Code and check that the namespace of the generated file is correct:

If project information isn't available to Razor this will be "ASP" or even "__GeneratedComponent"

@blackshot, @PeterDraex no resolution on this?
@davidwengier I'm facing the same issue right now and my project is open. I've created a snapshot branch here.
It's working like a charm in VS, hit this issue as I'm trying out VS Code as alternative:

Clone a fresh repo
Restore MAUI workloads
Rebuild the solution, first time it takes a while
Open a file - EventComponent.razor will do.

Symptoms seem consistent with what's described here. Specifically:

_Imports.razor usings aren't resolved
Inline components (no code behind class) don't seem to be registered as namespaces by the compiler.
Custom components are not resolved (RZ10012) - this is true even if I add the relevant using in the same file.

If you need something else to debug this, please share.

I'm also experiencing the same issue but I found a workaround and hope it helps troubleshoot the issue. Just like others have said I'm also having issues with some components not being picked up by vscode and I noticed that some work ok, while others don't. After some experimentation, I noticed that the components that were being picked-up correctly were using a .cs partial class and they explicitly inherited from ComponentBase in the c# fire. I refactored all components to have a cs file, even those without any code block, and one by one they started working as soon as I added the ComponentBase inheritance in the c# partial class. This is far from a solution because while CS code behind files is great for complex components its not ideal for very simple components or components that don't even require a "@code" block. Hope this helps you get to the bug and find a solution

Have the same issue when I reference any of my components. However, when I open the referenced component in VSCode, the "Razor(RZ10012)" warning disappears.
I do not have the issue when I am creating a new dotnet new project on the same computer. I tried "dotnet clean" but it changed nothing. Using .NET 8 as target platform for the existing and new projects.
I tried creating a new project with over 500 small components and get the same behaviour for a few seconds, but then it seems to resolve itself somehow. I struggling to find why it is not happening on the existing project. My only guess currently is that it is the size of the project...

Getting the same error Razor(RZ10012) for common blazor components. Intellisense is basically broken. Downgrading C# extension solve the error, but then, I cannot build or debug to my android device

I can confirm that this is not working. I am using latest C# Dev Kit (1.8.8) and in a freshly created project via
dotnet new blazorwasm
the namespace of the project and the App component is marked as unknown as shown in this screenshot:

I have tracked down the C# extension versions:

2.30.28 works
2.31.16 does not work

I have tracked down the C# extension versions:

2.30.28 works
2.31.16 does not work

Solves partially. Sometimes doesn't recognize components until the .razor file of the component is opened

Working for me on version v2.34.12
Tested with pre-release and got the issue back

There's a big issue with the latest versions (after 2.32.14) where the dev console is filled up with errors, that also manifest with incorrect Razor errors showing. It was transferred to the Razor repo. Hopefully will get fixed.
https://github.com/dotnet/vscode-csharp/issues/7246

I noticed in the changelog for 2.33.17 (where the problem first occurs) that Razor was updated to prerelease of v9:
Bump Razor to 9.0.0-preview.24281.3

Jesus Christ it is 2+ years. Every time i try to open my existing Blazor project in VSCode with the latest or preview version of the C# extension  i get 50 to 100 problems. The numbers of problems jumps around that number over time for no reason and even when i am not touching something.
The fact that it doesn't even work with the official templates from dotnet CLI after 2+ years tells me that MS does not want this to work in order to get more users on Visual Studio Community/Pro.

Jesus Christ it is 2+ years.

Nah, the C# extension, which is this repo, is not nearly that old. There was OmniSharp before it and that might have had some of the same bugs, but the amount of changes both in Roslyn and Razor since then is huge, and it's not fair to blame OmniSharp for our bugs. We earned ours fair and square, all on our own!

MS does not want this to work in order to get more users on Visual Studio Community/Pro.

Unfortunately nobody told any of us on the team this, and we've accidentally published v2.39.28 (pre-release) which hopefully fixes the issue, or at the very least makes it a lot less prevalent. If only you got here sooner to warn us.
If anyone wants to update and try it out, please do let us know how it goes. Of course we probably will be unable to respond because we'll have all been fired due to the resultant slowing sales of VS Community. Then again VS Community is free so maybe not?

There's a big issue with the latest versions (after 2.32.14) where the dev console is filled up with errors, that also manifest with incorrect Razor errors showing. It was transferred to the Razor repo. Hopefully will get fixed.
#7246

Is it too much to hope that this nasty problem is fixed with this update? I didn't see any reference in the update notes. Will check, with fingers crossed.

For context, the big update here is a complete change in how we sync data between Roslyn and Razor, from being file based to using a named pipe. This avoids a bunch of potential races and issues, for example I/O contention on the Roslyn side as its writing the file, if events come in at the same time, or missed file system events on the Razor side where it detects that the file has been updated.
Unfortunately @jtsom the issue that you are referencing is unlikely to be directly solved by this change. There is a chance that a more reliable system underneath makes everything on top work better - perhaps there are assumptions in the code being violated by bad communication - but I wouldn't want to give you any false hope. Your issue is currently tracked by https://github.com/dotnet/razor/issues/10505 which is still open, and is being investigated.

@davidwengier upgrading to v2.39.28 (pre-release) fixed a lot of the issues I was having in VS code.
Thank you!


Fix play build script osx

Two main things:

Fixes script so that it's portable to OS X and not Linux only (BSD compatible instead of GNU)
Adds ability to auto-publish to S3 so that we can let Heroku use new builds

:+1: #complete


 Only hyper list give me that
     POD ID                      POD Name             VM name    Status
  pod-odraXDudfq             ubuntu-6296703420                     succeeded

Can someone help me, what I'am doing wrong or what I may be missing?
Thanks
Here is some basic info....
uname -a
Linux w1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u2 (2015-07-17) x86_64 GNU/Linux
xl info
host                   : w1
release                : 3.16.0-4-amd64
version                : #1 SMP Debian 3.16.7-ckt11-1+deb8u2 (2015-07-17)
machine                : x86_64
nr_cpus                : 2
max_cpu_id             : 3
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1821
hw_caps                : bfebfbff:20100800:00000000:00000900:0000e3bd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 4095
free_memory            : 3022
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 5
xen_extra              : .2-pre
xen_version            : 4.5.2-pre
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          :
xen_commandline        : placeholder dom0_mem=1024M
cc_compiler            : gcc (Debian 4.9.2-10) 4.9.2
cc_compile_by          : root
cc_compile_domain      : nanox.cz
cc_compile_date        : Wed Jul 29 12:16:20 CEST 2015
xend_config_format     : 4
hyper info
Containers: 3
PODs: 1
Total Memory: 905072 KB
Operating System: Debian GNU/Linux 8 (jessie)
docker info
Containers: 3
Images: 4
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 10
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
CPUs: 2
Total Memory: 883.9 MiB
Name: w1
ID: IMNK:SD2T:EHW5:I4GK:FCGR:SENG:FZZ3:HAQI:IJ4K:KEPI:JRLK:XGS4
WARNING: No memory limit support
WARNING: No swap limit support
XEN log:
qemu: terminating on signal 1 from pid 5693
HYPER log:
[HYPER INFO  0804 15:31:.11 06045 server.go] Calling GET /list
[HYPER INFO  0804 15:31:.11 06045 job.go] +job list(pod)
[HYPER INFO  0804 15:31:.11 06045 job.go] -job list(pod) OK
[HYPER INFO  0804 15:31:.20 06045 server.go] Calling POST /pod/run
[HYPER INFO  0804 15:31:.20 06045 job.go] +job podRun({"id":"ubuntu-6296703420","containers":[{"name":"ubuntu-6296703420","image":"ubuntu","command":[],"workdir":"/","entrypoint":[],"ports":
[],"envs":[],"volumes":[],"files":[],"restartPolicy":"never"}],"resource":{"vcpu":1,"memory":128},"files":[],"volumes":[],"tty":true,"type":""})
[HYPER INFO  0804 15:31:.20 06045 pod.go] {"id":"ubuntu-6296703420","containers":[{"name":"ubuntu-6296703420","image":"ubuntu","command":[],"workdir":"/","entrypoint":[],"ports":[],"envs":[]
,"volumes":[],"files":[],"restartPolicy":"never"}],"resource":{"vcpu":1,"memory":128},"files":[],"volumes":[],"tty":true,"type":""}
[HYPER INFO  0804 15:31:.20 06045 init_comm.go] Wating for init messages...
[HYPER INFO  0804 15:31:.20 06045 xen.go] Start VM as domain 6
[HYPER INFO  0804 15:31:.26 06045 init_comm.go] Get init ready message
[HYPER INFO  0804 15:31:.26 06045 vm_states.go] begin to wait vm commands
[HYPER INFO  0804 15:31:.49 06045 vm_states.go] got spec, prepare devices
[HYPER INFO  0804 15:31:.50 06045 vm_states.go] pod start success
[HYPER INFO  0804 15:31:.50 06045 job.go] -job podRun({"id":"ubuntu-6296703420","containers":[{"name":"ubuntu-6296703420","image":"ubuntu","command":[],"workdir":"/","entrypoint":[],"ports":
[],"envs":[],"volumes":[],"files":[],"restartPolicy":"never"}],"resource":{"vcpu":1,"memory":128},"files":[],"volumes":[],"tty":true,"type":""}) OK
[HYPER INFO  0804 15:31:.50 06045 server.go] Calling GET /list
[HYPER INFO  0804 15:31:.50 06045 job.go] +job list(container)
[HYPER INFO  0804 15:31:.50 06045 job.go] -job list(container) OK
[HYPER INFO  0804 15:31:.50 06045 server.go] Calling POST /attach
[HYPER INFO  0804 15:31:.50 06045 job.go] +job attach(container, 0a919ef87a43a98efc3e18c8891b6062eae71073dfd57d9138323b329e69e2a5, y3ksovnx)
[HYPER INFO  0804 15:31:.50 06045 server.go] Calling POST /tty/resize
[HYPER INFO  0804 15:31:.50 06045 job.go] +job tty(pod-odraXDudfq, y3ksovnx, 51, 190)
[HYPER INFO  0804 15:31:.50 06045 job.go] -job tty(pod-odraXDudfq, y3ksovnx, 51, 190) OK
[HYPER INFO  0804 15:33:.20 06045 vm_states.go] Connection interrupted, quit...
[HYPER ERROR 0804 15:33:.20 06045 vm_states.go] Shutting down because of an exception: connection to VM broken
[HYPER WARN  0804 15:33:.30 06045 vm_states.go] Qemu did not exit in time, try to stop it
[HYPER ERROR 0804 15:33:.30 06045 vm_states.go] Shutting down because of an exception: vm terminating timeout
[HYPER ERROR 0804 15:33:.30 06045 init_comm.go] read init data failed
[HYPER ERROR 0804 15:33:.30 06045 tty.go] read tty data failed
[HYPER INFO  0804 15:33:.31 06045 job.go] -job attach(container, 0a919ef87a43a98efc3e18c8891b6062eae71073dfd57d9138323b329e69e2a5, y3ksovnx) OK
[HYPER INFO  0804 15:33:.32 06045 vm_states.go] Got VM shutdown event while terminating, go to cleaning up
[HYPER INFO  0804 15:33:.32 06045 vm_states.go] resources reclaimed, quit...
[HYPER INFO  0804 15:33:.32 06045 init_comm.go] vm channel closed, quit

@puresoul Hi, are  you using the hyper/hyper-kernel/hyper-initrd.image installed from hyper.sh or compile it yourself?

Hi, first I try install by hyper.sh and got that issue, after that I compiled everything myself and problem still presist.

@puresoul sorry for late response, qemu: terminating on signal 1 from pid 5693  Can you check who is the pid 5693, is it hyperd? And you can run hyperd with -v=3, this will print more information. Thanks!

so, that pid isn't hyperd and I can't track process to that pid. Here is log with -v=3, only thing what I've done in vm was apt-get update. Vm stuck in the middle of that process.
log of hyperd http://pastebin.com/CMdZp6vJ

@puresoul please reset hyperstart to this commit https://github.com/hyperhq/hyperstart/commit/46ffda72bdd85009af7380fc81812d8b745a7ae6, and have a try. We will update hyper to support NEXT message asap.

It produce more output but still same problem, do you have some another guess to try? Thanks
http://pastebin.com/DFrWsZ9m

@puresoul Sorry for late response, Can you check if you replace the old initrd under /var/lib/hyper/ with the compiled new initrd? it seems like hyperstart are busy handling pts data and had no chance to handle control data. but this bug is fixed by hyperstart, so it's weired.

could you post what revisions of xen and hyper is verified to works. Then I'll checkout source, build and try it once more? Thanks

ok, so now i can't startup vm. Only that:
root@w1:/etc/hyper# hyper run ubuntu
hyper ERROR: QEMU response data is nil
root@w1:/etc/hyper# cat /etc/hyper/config
Host= unix:///var/run/hyper.sock
Bios=/var/lib/hyper/bios-qboot.bin
Kernel=/var/lib/hyper/kernel
Initrd=/var/lib/hyper/hyper-initrd.img
Bridge=hyper0
hyperd:
http://pastebin.com/Pt2DTmdm

Ok, so I got it finaly working. xen 4.6rc, hyper-0.2dev and vanila kernel+initrd from installer. One thing that i changed was qemu-system-x86_64 binary. Xen qemu-system-i386 was maybe the problem. Installed qemu from repo and it's working... You may close this issue, thanks

@puresoul The successful case is running qemu without hardware virtualization(xen or kvm)?
Still got hyper runing in dom0 and no as domU what's this means? the error case is running hyper in domU?

hyper vm wouldn't show in "xl list", so it's runing in dom0, and no at xen....

@puresoul did your xen compiled with virtfs support
./configure --with-extra-qemuu-configure-args="--enable-virtfs"

note the double u, it should be double u for  xen 4.5

reference this doc: https://docs.hyper.sh/trouble_shooting/xen.html

I'll try it, tahnks

so, after while i got a question. Maybe here is bad place for that. I can't get from xen qemu-system-x86_64 binary, and qemu-system-i386 isn't compatible
[HYPER INFO  1102 12:06:00 01624 init_comm.go] [:45] [console] This kernel requires an x86-64 CPU, but only detected an i686 CPU.
[HYPER INFO  1102 12:06:00 01624 init_comm.go] [:45] [console] Unable to boot - please use a kernel appropriate for your CPU.

On same machine. Installed stock hyper by curl/bash installation with xen 4.6.  It but may be my own fault?
http://pastebin.com/c32LiEmY

@puresoul panic is program fault definitely, but I can't tell if this is because of new behavior of xen 4.6, and will investigate it.
for the i386 and x86_64 problem, and xen always use qemu-system-i386 by default. As xen does not rely on qemu for CPU emulation, this should not because of qemu build target. I wonder is this mean you build xen itself for i386 target. PS: I just guess the reason, and I am not sure about xen itself.

I'am not build xen for i386 and because as xen does not rely on qemu for CPU emulation, I don't understand what I'am doing wrong.

ok, another strange things. Just overwrite hyper with own compiled one. Now I got hyper vm/pod running in xen:
root@w1:/etc/hyper# xl list
Name                                        ID   Mem VCPUs	State	Time(s)
Domain-0                                     0  2048     2     r-----    2054.9
vm-mpTJiIAepG                                6   128     1     -b----       1.5
but somehow my issues now is again related to network. Now network is broken and if try manage eth0, vm/pod again crashes...

The git repo is ahead of the binary. And we will look into the network issue

that was about mounth old revision, by the way...

there may be some problem with hyper bridge settings. If I network-detach interface and then network-attach, then network works over xen bridge

We will test with the new code and publish a new release later....

Hyperd log from last testings
http://pastebin.com/96WsWas8

So I compiled actual revision a same problem with network presist. But now some new stuff appers at log,
http://pastebin.com/GC76KKLM

@puresoul
as you are using a new version of hyper, you can use ./hyper run -t ubuntu /bin/bash, the -t flag for tty prompt. This may not relate with the problem, just a hint

ok, I'll try

ok, even updated hyperstart won't help. This is weird. Can I somehow enforce another network frontend/backend. Maybe it's related to netback/netfront

@puresoul have you ever tried other images, such as busybox, nginx, etc.? I am afraid it is not pure network issue, might be low memory or something else.

nope, so I'll try it

sorry, misstype. Ok, I'll try

@puresoul What's the memory size of pod? can you try again with bigger memory?
https://docs.hyper.sh/reference/podfile.html

I pull changes from git on hyper, runv and hyperstart. Recompile and start pod with 512mb. If I starts same apt-get with only main repo, it runs ok. After I add universe and multiverse, same situation. Freez and shutdown, it is maybe related to ubuntu image. I may try debian or anything else also....
http://pastebin.com/9EXCMeih

won't resolv. Just drop hyper in favour of LXD.


Add example gallery to docs

There's already nice functionality within stixpy to search & download, and contain and visualise STIX data, we should add an example gallery on how to do all these things for 0.1.1 release.

So I've added the gallery code in #86 just need to populate with some nice examples now.

Done - but it's pretty empty right now.


Visual bug when breaking a vertical slab

Sometimes after breaking a block a technical texture appears or the breaking animation freezes

Could you check if this still occurs in the latest version please?

Has something changed? I don’t see a difference

Thanks


Fix: allow pass custom renderer creating function

Fix for #10
Use as:
https://github.com/eXponenta/web-xr-ogl-js/blob/react/src/XRApp.tsx#L14

Looks good, I'll remove prettier from the CI, too.


UI does not prompt for username/password when user navigates to "/dashboard" when logged out from Rancher

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Logout from rancher.
in the URL enter https://rancher-server/dashboard and hit enter
In the console - Error is seen and a lot of post requests are made
UI page is blank and does NOT load.

When you are logged in and you navigate to https://rancher-server/dashboard, it redirects you to. https://rancher-server/dashboard/c/local/explorer
And there is an error seen in the console: Error: Redirected when going from "/" to "/clusters" via a navigation guard.

Expected Result:
When user is logged out, and user navigates to https://rancher-server/dashboard, username/password page should be shown to the user instead of the error in the console.
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - commit id: 25fa4e47
Installation option (single install/HA): HA

User is able to navigate to https://<>/dashboard without any error. User is shown a login page - username and password.


Null Safety Migration

Hey,
just wanted to check in if you're already working on migrating to null safety. Or are you waiting on a dependency to migrate?

In my app, this is the only package which is not null safe, any plans on migration soon?

Thanks for your PR @anoop4real Would be awesome if you could check https://github.com/Vanethos/flutter_notification_permissions/pull/36 out @Vanethos
Thank you!

@Aulig For the time being may be you can use my fork, add below in pubspec.yaml, then it will use my fork, may be you can also test my changes and as a note once the PR is approved make sure you put back the original as I might not be maintaining this further.
  notification_permissions:     git:       url: https://github.com/anoop4real/flutter_notification_permissions

Thanks again @anoop4real! I've tested it, everything seems to be working in my app on Android and iOS.

Great hope the PR gets approved soon

Approved, in a couple of hours I'll get the new version up, thanks you @Aulig and @anoop4real !

Awesome, thank you!

It will be also deployed to pub.dev

@Vanethos Thanks a lot for approving. Forgot to mention, I was getting deprecation warning from one of the .java file (I think it was for Android), it is worth looking into that also if you have time

@anoop4real at the end of this month I'll carve some time for that if I can :D


kyverno-chainsaw: 0.2.3 -> 0.2.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kyverno/chainsaw/releases.
meta.description for kyverno-chainsaw is: Declarative approach to test Kubernetes operators and controllers
meta.homepage for kyverno-chainsaw is: https://kyverno.github.io/chainsaw/
meta.changelog for kyverno-chainsaw is: https://github.com/kyverno/chainsaw/releases/tag/v0.2.4
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.2.4 with grep in /nix/store/71ig4x6hskqbn1sqy18gpf21cpbd65yl-kyverno-chainsaw-0.2.4
found 0.2.4 in filename of file in /nix/store/71ig4x6hskqbn1sqy18gpf21cpbd65yl-kyverno-chainsaw-0.2.4

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kyverno-chainsaw

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/71ig4x6hskqbn1sqy18gpf21cpbd65yl-kyverno-chainsaw-0.2.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/c69004bedcf25d4ee7428e01085aed28f5f96786#kyverno-chainsaw

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/71ig4x6hskqbn1sqy18gpf21cpbd65yl-kyverno-chainsaw-0.2.4
ls -la /nix/store/71ig4x6hskqbn1sqy18gpf21cpbd65yl-kyverno-chainsaw-0.2.4/bin

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

1 package built:

kyverno-chainsaw

Maintainer pings
cc @Sanskarzz for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kyverno/chainsaw/releases.
meta.description for kyverno-chainsaw is: Declarative approach to test Kubernetes operators and controllers
meta.homepage for kyverno-chainsaw is: https://kyverno.github.io/chainsaw/
meta.changelog for kyverno-chainsaw is: https://github.com/kyverno/chainsaw/releases/tag/v0.2.5
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.2.5 with grep in /nix/store/9rn0g24v97132bc9lkr3h7b170l75sbq-kyverno-chainsaw-0.2.5
found 0.2.5 in filename of file in /nix/store/9rn0g24v97132bc9lkr3h7b170l75sbq-kyverno-chainsaw-0.2.5

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kyverno-chainsaw

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9rn0g24v97132bc9lkr3h7b170l75sbq-kyverno-chainsaw-0.2.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/928da5a0436fb83eaa816fc7838bd39d235036a8#kyverno-chainsaw

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9rn0g24v97132bc9lkr3h7b170l75sbq-kyverno-chainsaw-0.2.5
ls -la /nix/store/9rn0g24v97132bc9lkr3h7b170l75sbq-kyverno-chainsaw-0.2.5/bin

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

1 package built:

kyverno-chainsaw

Maintainer pings
cc @Sanskarzz for testing.


No obvious types for passing fallback data from server component to client component

Describe the bug
I am trying to type the result of fetchOffsetPaginationHasMoreFallbackData to pass it to a client component where it then gets passed as fallbackData. The closest I have found is:
type Result = Awaited<ReturnType<typeof recentBranchesQuery>> extends PostgrestResponseSuccess<infer T> ? T : never;

type Props = {
	fallbackData: {
		data: Result;
		hasMore: boolean;
	}[];
};

But I am not totally sure if this is actually correct, and it would be nice to include some helper types to do something similar? I am happy to open a PR with them.
To Reproduce
If possible, open a PR with a failing test. Otherwise, describe how to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

Oops thsi should be enhancement not a bug

always happy to accept prs! 🫶


how to update channels.xml files

Description
so i know how to run the grabber to scrape my own guide locally, but how can i update the channels.xml files to add more channels to scrape? i manually added a few more channels to one of the xml files by matching names and id's from the guide website but that would take so long to do!

Checkout the Contributing Guide. The same applies to local edits but may as well share with the community if you find some channels that can be added.


[SMALLFIX] Configuration parameter for UFS listing length

Large directory list and delete test pagination in the UFS. To speed up testing the parameter "alluxio.underfs.listing.length" can be set to a small number, allowing testing pagination for smaller directories.
S3 returns a maximum of 1000 list items. Didn't find similar documentation for other UFSs.

LGTM

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11544/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11545/
Test PASSed.

@calvinjia Please take another look.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11552/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11557/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11559/
Test PASSed.

LGTM


lnd: remove deprecated endpoints sendpayment, sendtoroute, sendtoroutesync, and sendpaymentsync

Change Description
This pull request removes the deprecated endpoints sendpayment, sendtoroute, sendtoroutesync, and sendpaymentsync in lightning.proto, rpcserver.go, lntest/rpc/lnd.go, and its related test cases in itest/lnd_routing_test.go and itest/lnd_channel_policy_test.go.
Closes #8175
Steps to Test
I ran the test cases using make check to make sure there were no regressions and all the test cases passed.
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[ ] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[ ] Commits follow the Ideal Git Commit Structure.
[ ] Any new logging statements use an appropriate subsystem and logging level.
[ ] Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
[x]  There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our  Contribution Guidelines for further guidance.

Hey @yyforyongyu, to keep you updated all the test cases are passed in the Travis CI run. That said we need to double check on those assertions:

lnd_channel_policy_test.go#L180 assertion
lnd_channel_policy_test.go#L206 assertion
lnd_routing_test.go#L402

@mohamedawnallah Thanks for the PR! As mentioned in the issue, we won't add this in the upcoming release so this will be marked as low priority atm.


Write ablog article on how to pick a career

No one's gonna read it. You know what? I'm never going to sit down and write this (useless shit) anyways.


chore(master): release 1.18.0

:robot: I have created a release beep boop
1.18.0 (2024-11-02)
Features

blacklist: add lodestone-id field (#533) (895167a)
signups: adds a Notes field for additional signup information (#531) (40f2e91)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.18.0
:sunflower:


[RFE] Add support for ARM64 in the Istio chart/containers

Is your feature request related to a problem? Please describe.
When trying to install the Rancher-Istio chart (102.3.1+up1.18.2), I get the following error:
2023-11-19T18:13:25.719280862+01:00 istioctl-installer: Jobs active: 0, jobs failed: 1, jobs succeeded: 0
Add/Modify event for istioctl-installer: MODIFIED
Error: INSTALLATION FAILED: failed post-install: 1 error occurred:
2023-11-19T18:13:25.812907905+01:00 	* job failed: BackoffLimitExceeded

With the error in the pod:
exec /bin/sh: exec format error

After some looking, I found this Istio issue, explaining that it has to do with a lack of arm64 support. Going through the links, I found that Istio itself added support for arm64 in version 1.15, but when I look up the Rancher Istio chart, I can see that istioctl-installer uses the istio-installer:1.18.2-rancher1 container, which doesn't support arm64.

Describe the solution you'd like
I would like for you to build your containers with arm64 support in mind. Istio already supports it, so it shouldn't be much effort to also start supporting it in the Rancher-specific containers/charts.
Describe alternatives you've considered
Installing Istio through another chart, but I'd have to find another source for the helm chart and I don't know which changes the Rancher chart added for better integration with Rancher and how to add those manually.

I found out that the uninstaller has the same issue, since it also uses the rancher/istio-installer pod

What I can see in rancher/istio-installer's dockerfile, the base image that is used is registry.suse.com/suse/sle15:15.3, which according to the registry supports arm64:

Found this video that describes how to create multi-arch images: https://www.youtube.com/watch?v=AQeGdMuJWIM
With that knowledge and after finding this drone.io plugin I created a pull request to add support for multi arch images

@CC007 Can you please test this now ?

It seems like the tag number wasn't updated (so it's still 1.18.2-rancher1, rather than 1.18.2-rancher2). I believe that this causes my images to not update.

Hmm, it seems that the container is now able to successfully start the shell, but then fails in the kubectl step for a similar reason

I found why. In the Dockerfile:
RUN curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl
RUN mv ./kubectl /usr/local/bin/kubectl && chmod +x /usr/local/bin/kubectl

Here it's specified to specifically install the amd64 version.

I created a Dockerfile patch for both 1.18 and 1.19. This specifies the arch for kubectl, but also istioctl.
Please, when making the next release, use the -rancher2 suffix for the tag instead of updating the old tag, to prevent image caching issues.

It looks like istioctl does work without specifying the architecture, since it is able to detect the arch, but it doesn't hurt to be specific.
I found this out through the uninstall command, which uses istioctl (and doesn't use kubectl unless there is a cattle-dashboards namespace)

@CC007 Can you test now again? I cannot create a brand-new tag. If I do I will to release a new version of chart.

@CC007 I say a bug while installing istio with your new PR. So I reverted it. Can you check that ? Thanks 👍🏽

@CC007 I released a new tag 1.18.2-rancher2. I will go forward a create a new version of Istio 1.18 for release.

@l4zy0n3 For now on, we need to test all test cases for Istio on both x86 and arm.

It seems that the changes from rancher/istio-installer#69 and rancher/istio-installer#70 have not been made available in newer versions of istio-installer.

Ah I see why now. The change was reverted for both 1.18 and 1.19, but the revert was only re-reverted for 1.18, so it didn't get added back to 1.19 and newer. I'll send you another PR

See rancher/istio-installer#84, rancher/istio-installer#85, rancher/istio-installer#86 and rancher/istio-installer#87


Compile Discovery Research Findings

Now that we're winding down during the holiday season, this would be a good opportunity to take some time & compile findings from our discovery research.
Acceptance Criteria:

[ ] Create a guide to find all of our research in one place
[ ] Pull out key findings & insights
[ ] Determine how to present information (document, miro, CIF teams channel)
[ ] Create a summary guide for future knowledge transfer

Hi @jaimiebutton - is it also possible to include all the links where original information/sessions (e.g., Miro Board) are? One of the blocks for CIF is that they don't know/understand where to find all the relevant information.

Hi @jaimiebutton - checking in on the status of this task. Should this be moved into the 'design in progress' pipeline?


[stable/consul] Deprecate stable/consul

Is this a new chart
no
What this PR does / why we need it:
stable/consul is deprecated in favor of HashiCorp's official Helm chart.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

cc @lachie83

/lgtm

Thanks @lkysow


Add Airlock painter

Could either make it take in any hex colour or only specific whitelisted ones (stored on a prototype or whatever)
Colours the required layer on the target airlock after a delay.
Whatever else it can do in ss13

we got em


not building anymore with latest krogoth yocto branch

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Error, the PACKAGE_ARCHS variable (all any noarch armv5hf-vfp armv5thf-vfp armv5ehf-vfp armv5tehf-vfp armv6hf-vfp armv6thf-vfp armv7ahf-vfp armv7at2hf-vfp armv7vehf-vfp armv7vet2hf-vfp armv7vehf-neon armv7vet2hf-neon armv7vehf-neon-vfpv4 armv7vet2hf-neon-vfpv4 cortexa7hf-vfp cortexa7hf-neon cortexa7hf-neon-vfpv4 cortexa7t2hf-vfp cortexa7t2hf-neon cortexa7t2hf-neon-vfpv4 raspberrypi2) for DEFAULTTUNE (cortexa7thf-neon-vfpv4) does not contain TUNE_PKGARCH (cortexa7hf-neonvfpv4).

the culprit is change: 31351ce146bf9c61d779456cd68ff7c2c9d4c8a8

reverting http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=31351ce146bf9c61d779456cd68ff7c2c9d4c8a8 this commit make it work again, but upstream told it might be an issue of your layer

Hi @LocutusOfBorg this seems to be an issue that got solved in the meanwhile as trying now with current master seems to not reproduce your issue. I used:
Build Configuration:
BB_VERSION        = "1.31.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "raspberrypi"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1+snapshot-20160708"
TUNE_FEATURES     = "arm armv6  vfp arm1176jzfs callconvention-hard"
TARGET_FPU        = "hard"
meta
meta-poky
meta-yocto-bsp    = "master:4e889c04ba518dac492c193224a790a877f43f40"
meta-raspberrypi  = "master:43ecd9ac992216974316f954683547e5867c5612"
meta-oe
meta-python
meta-networking
meta-multimedia   = "fixes:9379f00022a1a538d4bc63b90a1ae9642d949953"
meta-qt5          = "master:c16c4662db7947ce48af35e0b93a440fe955588a"

yes, fixed here
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e6917603e2a7ad8a920d3883d2ddf196b6038dc5
G.

Cool. Thanks man.