re-create the GeoDataFrame  for download

Instead of reading ("patches", "data") it might be cleaner to re-create the GeoDataFrame as done in draw_patches. Currently it looses the crs property.
Originally posted by @mathause in https://github.com/romatt/exseas_explorer/pull/33#discussion_r1053689763

Could the crs property not simple be added back?
gdf = gdf.set_crs('epsg:4326')

If it's the same for all then yes of course.

Do you mean for all geometries? If so then yes!


Add 'color' as valid cli option, remove from config

Summary
Fixes #2501. I've also removed colors from normalize.js, because it's not a valid config option and added a note about switching colors off. This may need linguistic adjustments though.
Test plan
works on my machine

Current coverage is 64.83% (diff: 100%)

Merging #2557 into master will not change coverage

@@             master      #2557   diff @@
==========================================
  Files           125        125
  Lines          4871       4871
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           3158       3158
  Misses         1713       1713
  Partials          0          0

Powered by Codecov. Last update fa39ef8...cf1070e


Forbid swiping back

How to forbid swiping back for a scene ?

Check https://github.com/ericvicenti/navigation-rfc/issues/49

@aksonov How do I pass null to panHandlers?
Per https://github.com/ericvicenti/navigation-rfc/issues/49#issuecomment-200945651 the gesture can be disabled by setting panHandlers to null.  When I have a scene that pushed from bottom to top using direction='vertical', I don't want users to swipe down to pop the scene.
<NavigationCard panHandlers={null}/>

Looks like it is not in 0.22 release. Anyway i will post version that pass panHandlers to NavigationCard.

Awesome @aksonov  :+1: !

I also have this problem with the 3.x version. A bit annoying if you are on a map screen. So the sollution will be to pass panHandlers={null} down a Scene?

Yes. However 0.22 doesn't support passing panHandlers yet, probably 0.23 will.

Okey. is there any other way to accomplish this now? We sort of rely on this in order to upgrade to 3.x

Yes, use your own NavigationCard, AnimatedNavigationView and your renderer instead of DefaultRenderer.

Okey, thanks!

@sslash If you do this can you please post it back in this issue so that we can also reuse your code please?
Thanks!

Yes absolutely. I have postponed the task however, not sure when I/we will start, but when we do then yes

Thanks mate @sslash

For me it would be great just to change the pan detector to be on the left half of the screen. iOS sliders now go to the previous page when I decrease their value...

I'm in the same situation than @sslash : I've a full screen map and I can't interact with it after having a Scene change. So it would be very nice to have a way to set panHandlers={null} for a scene!

@mvaivre to disable swiping back, passing panHandlers={null} worked for me, e.g:

@brien-crean on which react-native and react-native-router-flux versions?

I am using
react-native: 0.23.1
react-native-router-flux: 3.2.8

Another solution is to make sure your components don't let go of the panResponder. See https://github.com/jeanregisser/react-native-slider/pull/28

@brien-crean: indeed panHandlers={null} disable the swiping back, but one of the component still continues to "steal" the pan action, as stated by @cridenour, so I can't interact with my map.

@mvaivre interesting, I am not using any map components at the minute. It looks like for a slider component, RNv0.24 will include a fix for the component letting go of the panResponder. I wonder if something similar can/should be implemented for a map component?
See 52ddfd9

Unfortunately I don't believe the default MapView doesn't use the JS gesture system AFAIK.

I am using
    "react": "^0.14.8",
    "react-native": "^0.24.1",

and I set  panHandlers={null} in my Scene definition with map view.  And it seems to work, swiping back is no longer posssible.

little update,
panHandlers={null}

breaks the navbar buttons. Instead I added fake implementation of panHandlers do scene with map.
var _panResponder = PanResponder.create({
        onMoveShouldSetPanResponder: (e, gestureState) => {},
    onMoveShouldSetPanResponderCapture: (e, gestureState) => {},
    onStartShouldSetPanResponder: (e, gestureState) => {},
    onStartShouldSetPanResponderCapture: (e, gestureState) => {},
    onPanResponderReject: (e, gestureState) => {},
    onPanResponderGrant: (e, gestureState) => {},
    onPanResponderStart: (e, gestureState) => {},
    onPanResponderEnd: (e, gestureState) => {},
    onPanResponderRelease: (e, gestureState) => {},
    onPanResponderMove: (e, gestureState) => {},
    onPanResponderTerminate: (e, gestureState) => {},
    onPanResponderTerminationRequest: (e, gestureState) => {},
    onShouldBlockNativeResponder: (e, gestureState) => {},
  });

and
<Scene key="MapView" panHandlers={_panResponder.panHandlers} ...

Thanks

"react": "15.2.1",
"react-native": "0.30.0",
"react-native-router-flux": "^3.35.0"

"panHandlers={null}" does not work for me. Anyone else have this issue?

Looks like it's broken for me too.
"react": "15.3.2",
"react-native": "0.33.0",
"react-native-router-flux": "^3.35.0",
in the Example I can still swipe back from Login2 screen for instance even too panHandler=null in login2 scene.

@sineer  I used hideNavBar= {true} instead

@willyyang It's two different thing no?
panHandler is for swiping gesture to pop the scene and NavBar is the header section with title.
I tried with both NavBar true/false set for Login2 scene or it's parent and panHandler is set to null yet I can always swipe my way back a scene when direction="vertical"... Anyway not a big deal for me right now just a heads up I guess. maybe I am doing something wrong too I'm very fresh using this native stuff and using it through clojurescript also...

Thanks, brien-crean

It works I'm using Route some thing like that.

What about temporary removing panHandlers depending on scene's component state?

is there a way to disable the pan handlers when calling a specific action? Like:
Actions.myAction({ panHandlers: null })

Using version 3.37.0

@redvulps you should set them as null when defining your scenes.
<Scene key="myAction" panHandlers={null} />

To keep platforms' gesture-based navigation, I do:
const activeBackGesture = (Platform.OS ==='android') ? null : undefined;
...
<Scene key="myAction" panHandlers={activeBackGesture} />


[stable/sealed-secrets]feat: Update to 0.12.2

What this PR does / why we need it:
Update to 0.12.2
Special notes for your reviewer:
make diff with https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.12.1/controller.yaml
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

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

/ok-to-test

/assign @srueg @olib963

Please update the image.tag in the README accordingly.

/lgtm

/assign @olib963

LGTM /approve

/approve


pywinauto 0.6.5 with Python 3.7 showing deprecation warnings from common_controls.py

I recently upgraded pywinauto to test with Python 3.7 (previous setup was pywinauto 0.6.4 with Python 2,7). In this new setup I am seeing a large number of DeprecationWarnings being output to the terminal from ..\pywinauto\controls\common_controls.py.
e.g.,
..\testPyWinAutoPython37\venvTestPython37\lib\site-packages\pywinauto\controls\common_controls.py:776: DeprecationWarning: Method .ItemCount() is deprecated, use .item_count() instead.   return self.get_header_control().ItemCount() ..\testPyWinAutoPython37\venvTestPython37\lib\site-packages\pywinauto\controls\common_controls.py:776: DeprecationWarning: Method .ItemCount() is deprecated, use .item_count() instead.   return self.get_header_control().ItemCount() ..\testPyWinAutoPython37\venvTestPython37\lib\site-packages\pywinauto\controls\common_controls.py:179: DeprecationWarning: ListView item properties "text", "state", "image" and "indent" are deprecated! Use methods text(), state(), image() and indent().   'Use methods text(), state(), image() and indent().', DeprecationWarning) ..\testPyWinAutoPython37\venvTestPython37\lib\site-packages\pywinauto\controls\common_controls.py:776: DeprecationWarning: Method .ItemCount() is deprecated, use .item_count() instead.   return self.get_header_control().ItemCount() ..\testPyWinAutoPython37\venvTestPython37\lib\site-packages\pywinauto\controls\common_controls.py:179: DeprecationWarning: ListView item properties "text", "state", "image" and "indent" are deprecated! Use methods text(), state(), image() and indent().   'Use methods text(), state(), image() and indent().', DeprecationWarning) ..\testPyWinAutoPython37\venvTestPython37\lib\site-packages\pywinauto\controls\common_controls.py:776: DeprecationWarning: Method .ItemCount() is deprecated, use .item_count() instead.
I've googled how to suppress these warnings, but none of the suggestions I've seen so far have worked (e.g., suggestions here How to ignore deprecation warnings in Python)
Any advice on how to stop these warnings from being output to the terminal during run of scripts that use pywinauto?

For what it's worth, an edit of line 776 of common_controls.py from:
            return self.get_header_control().ItemCount()
To:
            return self.get_header_control().item_count()
...appears to have fixed the issue at my end.

Good catch! I'll consider this as a high priority for next update release.
This workaround should disable warnings:
import warnings
warnings.filterwarnings("ignore", category=DeprecationWarning)

If it doesn't help, you may need to clear all filters by warnings.resetwarnings() and then apply ignore filter.

Already fixed by @CodyDeGhetto in #565 and #569.

BTW, warning at common_controls.py:179 is relevant. Can be fixed by changing .text by .text() etc.

Getting the same warnings under python 3.6
using latest pywinauto v.0.6.5 available from pip

@parlar any more details? Code sample + traceback would be very helpful.
If you're using CamelCase methods in your code, the warnings are correct: just use pep8_stype methods. If not, please provide the traceback.

BTW, we recently made additional clean ups in commaon_controls.py (see rev: 3b66563b05be9f3061a8be33ef00f0019ed12567). @parlar , you could check it with the current sources from the trunk.


Create submission_B1

Node ID: f78030435465b50f
Node Name: Madilog

@mdlog It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Your submitted log appears modified. It is missing runtime summaries at the end. Please can you resubmit output from the log summary tool without modification to filename or contents.

rejected:B1
It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing
We’ve thus marked B1 as rejected, however if this is a mistake, please upload the log summary and we can re-review.


Style for visited links

I suggest styling the :visited status to avoid bizarre colors in icons and text.
For instance, lines 76-77 of jssocials-theme-flat.css would be:
.jssocials-share-link:hover, .jssocials-share-link:focus, .jssocials-share-link:active, .jssocials-share-link:visited {
   color: #fff; }

Could you make a PR with the suggested change?

Of course, I would be pleased...
Just give me some time as I am pretty busy at this very moment!


chore(search-bar): cleaned up props

Contributes to #4602
This PR cleans up the SearchBar props that were mentioned here. Groups up MultiSelect props for adopter ease of use.
What did you change?
placeHolderText -> placeholderText (changed upper to lower case h)
How did you test and verify your work?
Changes work in my local Storybook instance

@davidmenendez Sorry for the wait! I was busy fixing a problem we've had in Dotcom for a while. Let me know if there's anything else so we can get this merged!

@IgnacioBecerra there are some failing SearchBar tests now, see here.


inline method

simplify class @garydgregory

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

Comparison is base (02eac5e) 92.11% compared to head (5a81f33) 92.11%.

Additional details and impacted files
@@            Coverage Diff            @@
##             master    #1154   +/-   ##
=========================================
  Coverage     92.11%   92.11%
  Complexity     7586     7586
=========================================
  Files           200      200
  Lines         15825    15825
  Branches       2890     2890
=========================================
  Hits          14577    14577
  Misses          674      674
  Partials        574      574

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


Added support for customizable stepSizes

As suggested in https://github.com/Intervention/image/issues/98

one year ping, I know this PR is closed, but are there viable ways to deal with this new feature? We use it in production on a daily basis for a year already and would like to not maintain a fork just for this ;).


[55517] Implemented timed disable/enable of back buttons to prevent them being read first by voiceover

@pavshr like this?


Switched order to render history toolbar in Pxe screen

Fixed consistency issue
Before:

After:

Links
https://bugzilla.redhat.com/show_bug.cgi?id=1393205
Steps for Testing/QA
Compute -> Infrastructure -> Pxe

@romanblanco please add screenshots, then I can merge.  Thx, Dan

@dclarizio updated, thanks

@romanblanco: I wonder if we want this to be fixed as you did (set the toolbars in reverse order)  or if the code rendering the toolbars should always render them in a fixed order.

@martinpovolny I think this fixes the issue for now.  It may be more flexible to allow rendering them in the order they are set.  Otherwise, we would always force a certain order and may need exceptions if other requirements arise.  Either way, will merge this to fix the BZ.  Thx, Dan

Euwe backport details:
$ git log -1
commit a31ffc4a8c5468fbc4ed061ad2b3f43ae3f8994d
Author: Dan Clarizio<EMAIL_ADDRESS>Date:   Thu Dec 1 08:25:47 2016 -0800

    Merge pull request #12882 from romanblanco/bz1393205

    Switched order to render history toolbar in Pxe screen
    (cherry picked from commit 0f603054df81e53b35b281bbc9e166edf64f879c)

    https://bugzilla.redhat.com/show_bug.cgi?id=1401044


Updated DS Mentor/Mentee schema to match backend

Description
DS needs to match BE Mentor and Mentee creation to match their schema and store it.
Type of change

[X] New feature (updated)

Checklist:

[X] My code follows PEP8 style guide
[X] I have removed unnecessary print statements from my code
[X] I have made corresponding changes to the documentation if necessary
[X] My changes generate no errors
[x] No commented-out code
[X] Size of pull request kept to a minimum
[X] Pull request description clearly describes changes made & motivations for said changes

Pair-Programming:
Who you paired with: Matt Grohnke
What pairing method(s) you used: Driver-navigator
How did it go? What did you learn?: The process went well, it sped up the time that it would have taken to make the updates.
Loom video: https://www.loom.com/share/0878bfa264174888b6b3aad964e5e909

Yeah, looks good. No fixes need to be implemented that I can think of. nice job


Zero local variable slat

Fix: #1976

I dont understand:

Why we need zero salt? Salt is usually not secret.

How does this patch work? Compiler may optimize the zero value assignment.


There is no build dist after npm run dev

I am unable to run this in dev mode. How is the dev mode done exactly and what does it do? There is no dist directory after npm run dev. Am I suppose to npm run build first? But it does not rebuild whenever I change the code. Sorry just starting out building chrome extensions
Edit: I tried the https://github.com/extend-chrome/ts-react-boilerplate.git and it works. It builds to dist and hrm also works.

I am unable to run this in dev mode. How is the dev mode done exactly and what does it do? There is no dist directory after npm run dev. Am I suppose to npm run build first? But it does not rebuild whenever I change the code. Sorry just starting out building chrome extensions
Edit: I tried the https://github.com/extend-chrome/ts-react-boilerplate.git and it works. It builds to dist and hrm also works.

Any chance that you don't have yarn installed? In a recent PR they change the dev script to use  yarn. If that is the case then you can either install yarn or change line 14 in package.json to this: "dev": "npm run build:hmr && (npm run wss & nodemon)",

I also encountered this problem recently, how did you solve it?

I am unable to run this in dev mode. How is the dev mode done exactly and what does it do? There is no dist directory after npm run dev. Am I suppose to npm run build first? But it does not rebuild whenever I change the code. Sorry just starting out building chrome extensions
Edit: I tried the https://github.com/extend-chrome/ts-react-boilerplate.git and it works. It builds to dist and hrm also works.

I also encountered this problem recently, how did you solve it?

Would you like to pull the latest source from the repository and try again?
As liqiuqiui said, I suspect the problem is caused by yarn not being installed. Removed yarn inside package.json and replaced it with npm run.

@ilbrigz @liqiuqiui
Would you like to pull the latest source from the repository and try again?
As namnguyen191 said, I suspect the problem is caused by yarn not being installed. Removed yarn inside package.json and replaced it with npm run.

Yes, I am running the latest code and yarn is installed with the latest version. I find that the command line gets stuck after the wss command is executed and does not execute the nodemon command that follows. If I re-execute yarn dev at this point, it reports an error about the port being occupied, and the nodemon command continues to be executed later, and the project runs normally and generates the dist directory. I'm not sure why this is happening.
Translated with www.DeepL.com/Translator (free version)

@ilbrigz @liqiuqiui
Would you like to pull the latest source from the repository and try again?
As namnguyen191 said, I suspect the problem is caused by yarn not being installed. Removed yarn inside package.json and replaced it with npm run.

Yes, I am running the latest code and yarn is installed with the latest version. I find that the command line gets stuck after the wss command is executed and does not execute the nodemon command that follows. If I re-execute yarn dev at this point, it reports an error about the port being occupied, and the nodemon command continues to be executed later, and the project runs normally and generates the dist directory. I'm not sure why this is happening.

I am expieriencing the same problem

@ilbrigz @liqiuqiui
Would you like to pull the latest source from the repository and try again?
As namnguyen191 said, I suspect the problem is caused by yarn not being installed. Removed yarn inside package.json and replaced it with npm run.

Yes, I am running the latest code and yarn is installed with the latest version. I find that the command line gets stuck after the wss command is executed and does not execute the nodemon command that follows. If I re-execute yarn dev at this point, it reports an error about the port being occupied, and the nodemon command continues to be executed later, and the project runs normally and generates the dist directory. I'm not sure why this is happening.

I am experiencing the same problem

hi, bro! I have solved this problem by running "yarn build:hmr && start /b yarn wss && nodemon" instead of "yarn build:hmr && (yarn wss & nodemon)", and the reason is Windows command line does not recognize & command.

@ilbrigz @liqiuqiui
Would you like to pull the latest source from the repository and try again?
As namnguyen191 said, I suspect the problem is caused by yarn not being installed. Removed yarn inside package.json and replaced it with npm run.

Yes, I am running the latest code and yarn is installed with the latest version. I find that the command line gets stuck after the wss command is executed and does not execute the nodemon command that follows. If I re-execute yarn dev at this point, it reports an error about the port being occupied, and the nodemon command continues to be executed later, and the project runs normally and generates the dist directory. I'm not sure why this is happening.

I am experiencing the same problem

Hi, bro! I have solved this problem by running "yarn build:hmr && start /b yarn wss && nodemon" instead of "yarn build:hmr && (yarn wss & nodemon)" command, and the reason is Windows command line does not recognize & command.

Thanks it works, I used concurrently it worked aswell but this way one dependency less

@ilbrigz @liqiuqiui
Would you like to pull the latest source from the repository and try again?
As namnguyen191 said, I suspect the problem is caused by yarn not being installed. Removed yarn inside package.json and replaced it with npm run.

Yes, I am running the latest code and yarn is installed with the latest version. I find that the command line gets stuck after the wss command is executed and does not execute the nodemon command that follows. If I re-execute yarn dev at this point, it reports an error about the port being occupied, and the nodemon command continues to be executed later, and the project runs normally and generates the dist directory. I'm not sure why this is happening.

I am experiencing the same problem

Hi, bro! I have solved this problem by running "yarn build:hmr && start /b yarn wss && nodemon" instead of "yarn build:hmr && (yarn wss & nodemon)" command, and the reason is Windows command line does not recognize & command.

Thanks it works, I used concurrently it worked aswell but this way one dependency less

Sorry, I don't quite understand what the second sentence means

https://www.npmjs.com/package/concurrently

Not worked in dev, build working fine 😎


Title: Improvement in start button of Countdown timer project.

Which pre-existing JavaScript project will you be working on?
Countdown Timer
Describe your enhancement/improvement
The start button is not placed correctly in right position. I would like to fix that issue.
I also like to improve the UI of Countdown Timer project making it more visually appears which improves the user experience.
@swapnilsparsh Please assign me this so that I can work on this under GSSOC'24 with appropriate label.
Anything you need to say to the Reviewers
No response
Add any other context or relevant screenshots about the enhancement here.
No response

@aditig80 Thank you for providing your insight but it is not required as of now.


Send data out immediately on the write-path

When a transactions comes in, the server persist changes to shape logs before sending them to subscribers waiting for new data. This is adding a fair amount of latency to the write path. In this issue we want to stream rows to clients as soon as we find a shape match and persist changes to shape logs in the background.
In order to do that, we're going to buffer row -> [shapeIds] and have a process to persist changes for those shape . We don't ack a transaction from Postgres until all shapes for a transaction have been updated. This allows to recover gracefully from crashes, as the server can continue from where it stopped and just skip shape logs that have alreaby been written.
The buffer has a fixed size (configurable?). Pending transactions are written to disk:

at fixed delay, say 20ms
when the buffer fills (ideally it would stop ingesting more transactions from logical repl)
When there are no pending transactions, but this feels more optimization and we can handle that later

It might happen that Postgres writes to Electric at a faster speed than Electric can handle shape logs. The developer would need to handle that situation by increasing the buffer size, or account for PG WAL size increase.
This task should be done after #1744 as it builds on the assumption that a single process would determine what shapes need to be written (we'd have to revise approach otherwise)

Two conflicting statements: "persist changes to shape logs in the background" vs "We don't ack a transaction from Postgres until all shapes for a transaction have been updated".  In fact, you can ack a transaction as soon as it is persisted, and you can perform shape matching and propagation in a parallel background task that doesn't have to ack.  In case of a crash, either the transaction was not persisted hence not ack'ed, and you get it trom the server; or it was and you get it from the persisted log.   Again, it helps to have a single on-disk log common to all shapes.

In case of a crash, either the transaction was not persisted hence not ack'ed, and you get it from the server;
You can't get the operation from PG WAL once it's acked. We only ack on Pg to be able to recover from the point the server crashed.

Just an observation that a client may be able to re-connect after receiving a response within the buffer window. So we should serve new requests from memory where possible as well as currently blocked live requests.

Yeah, the issue description is not clear about that. In the original RFC I suggest doing that by scanning the common buffer, or holding a buffer for each shape. That needs to be clarified during implementation.
Well spotted. Thanks for raising it.

This was completed? I thought we're still writing to disk before sending to client? Or is that just for the initial snapshot?

@robacourt can you confirm?

@robacourt how much time would this cut off latency


adding BINARY_MAX and BINARY_MIN TPPs

We still need to ASIMD & SVE, hopefully it's as simple as x86


⚠ Bofrost.lu has degraded performance

In e63d26c, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2889 ms

Resolved: Bofrost.lu performance has improved in ed170f9 after 2 hours, 18 minutes.


fitRows Items overlapping in firefox

Test case: https://www.maaklerenleuker.nl/opleidingen/
I used the fitRows layoutmode for this website its isotope filtering and in google chrome it works fine. But in Firefox everything is halved. Check out the link for details.
NOTE: After filtering through the search text input field the grid works normal on the first load it does not work.

I fixed it by adding a height to every element


Multisig proposer must be an active custodian

Task linked: DEMZNE-1120 Only custodians should be able to propose multisig proposals


Why skipping Unix + py35?

I am looking into packaging some software that depends on llvm on conda-forge.
I am wondering why the combination linux + py35 is skipped.

That's a red herring. LLVM/Clang is not specific to any given version of Python. This just avoids compiling the same stuff a bunch of times when the package is not different across versions (Python 2.7, 3.4, 3.5, etc.).

gocha, thanks


[Question] compile and run the opengl and imgui examples

Hi there,
I am not familiar with the use of a such a big library and the nuke tool, so apologies for the question if its obvious.
I followed the readme instructions, but finding the next error when doing the nuke compile command from the powershell:
[ERR] Restore: C:\Program Files\dotnet\sdk\6.0.201\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: para compilar este proyecto, deben estar instaladas las siguientes cargas de trabajo: ios [<RestOfMyFullPath>\Silk.NET\src\Windowing\Silk.NET.Windowing.Sdl\Silk.NET.Windowing.Sdl.csproj]
I tried to install the Silk.NET.Windowing nuget package everywhere, in the source, and in the src/Windowing project, but did not achieve to install it. Dont know where exactly I would need to install it as there are many windowing projects in  src/Windowing.
On the other hand my main interest is to run the imgui and the opengl examples, so I tried to specifuically build those with the commands shouwn in the contributing.md.
I did nuke sln --projects opengl silk.net.vulkan core.win32extras "opengl tutorials" build
The Silk.NET.gen.sln seems to be generated correctly, but if opened I get among other errors:
NuGet Error NU1012. Seems to be related to android.
MSB4018: The task failed unexpectedly
As the main nuke compile fails, then the specific project building failing might be just a consequence of that.
Any guidance or maybe a little more detailed documentation to make this work would be much appreciated.
Thanks a lot in advanced.

That NETSDK1147 error seems to indicate that you are missing ´ios´ workload.
Have you installed all of the required workloads?
dotnet workload install android android-aot ios maui

(thught I did that already) Workload id is not recognized in the powershell console. In spanish: No se reconoce el id. de carga de trabajo android-aot.
Should android studio or SDK Platform Tools be installed?
Thanks in advanced

I also did:
dotnet workload install maui and mani projects seem to be restored in the logs, but now I get this error:
[ERR] Compile: C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\31.0.200-preview.14.106\tools\Xamarin.Android.Tooling.targets(69,5): error XA5300: No se encontró el directorio de Android SDK. Debe establecerse a través de /p:AndroidSdkDirectory. [<RestOfMyFullPath>\Silk.NET\src\Windowing\Silk.NET.Windowing.Sdl\Silk.NET.Windowing.Sdl.csproj]
Seems also related to windowing.
Y installed android studio just in case, but same.

thanks for your answer, let me try later in some hours and let you know if that works

thanks for your answer, let me try later in some hours and'll let you know if that works. Hoever, is that the same as opening Something.csproj and eight-click + build¿¿??.

Building the specific project from the powershell works!
dotnet build ./path/to/Something.csproj

Do not know what was happenning before, as I tried right clicking + build to run the app all of the time.
So after cloning the whole repo, just building and running the respective csproj should work or there is something else that needs to be done?? In either case that might be a useful info to include in the readme for a newbie newcomer as myself.
Thanks for this awesome library, for any comment regarding the question and for your support!