Crafting Menu Display

Description
Task: Display with the different items that can be crafted (sword) and show materials
Feature: Crafting system #4
The task is to display the items that are available to be crafted at this stage in the crafting UI. Currently there is only a sword, which will be crafted using wood and steel. This will be displayed on the left side of the crafting menu and the individual item crafting feature will be displayed on the right side of the menu. The individual crafting feature will have the item to be crafted (sword) displayed as well as the items it needs (wood and steel). At this stage, it is assumed that the user has unlimited wood and steel. When the crafting table is selected, there will be a button event handler that displays the menu. This will display the sword as being available to be crafted as well as its individual crafting menu since this is the only item. A bigger image of the sword will be displayed as well as the image of wood and steel at the bottom. Underneath this will be the craft button that handles the crafting of the item and is for Task Ticket #19.
Example

**Crafting feature **

Dependencies

The map where the crafting table is located needs to be implemented.
The visual design of the crafting table needs to be done so it can be selected
The visual design of the crafting UI as well as the sword, wood and steel need to be done so it can be displayed.

Milestones
List of steps that need to be completed for this task.

Adding a button to the map so the crafting menu can be opened (Aug. 19).
Event handler to display the crafting menu (Aug. 23).
Adding the craft button to the menu (Aug. 23).
Display the sword, wood and steel (Aug 28).

Completion Deadline: Aug. 28
Documentation

Crafting System Layout (../wiki/Crafting-System-Layout)

Member

Ly Phung (lyphng) (Ly Phung)

Display has been created and is accessible in game


Update tutorial on Digital Ocean for v1

https://www.digitalocean.com/community/tutorials/how-to-deploy-cockroachdb-on-a-three-node-cluster-on-ubuntu-16-04
Maybe be as little as removing reference to beta, but there may be more to do, too.
cc: @sploiselle, @jess-edwards

@sploiselle, can you look into what needs to be changed when you have a few?

@benesch @bdarnell  Have we made any changes to the binary URLs yet?

Nope, not yet. cockroachdb/cockroach#15982 made it so that unstable
releases won't touch the existing latest link, so we're safe until 1.1.
On Thu, May 25, 2017 at 10:53 AM, Sean Loiselle<EMAIL_ADDRESS>wrote:

@benesch https://github.com/benesch @bdarnell
https://github.com/bdarnell Have we made any changes to the binary URLs
yet?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cockroachdb/docs/issues/1256#issuecomment-304030482,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA15IMWkIyWtknnqYIumpjd-rjWhzlQFks5r9ZXmgaJpZM4M0q_c
.

@sploiselle, I just reviewed the DO tutorial, and it seems that everything's still fine, with the exception of out-dated admin UI screenshots. If you can confirm, we can close this issue for now.

@sploiselle, instead of closing this, I'm moving it to later since we'll eventually want/need to update the tutorial.


RuntimeError: Boolean value of Tensor with more than one value is ambiguous in xLSTM/slstm.py

RuntimeError: Boolean value of Tensor with more than one value is ambiguous in xLSTM/slstm.py
Issue Description
I'm encountering a RuntimeError when attempting to execute a backward pass in my xLSTM model. The error message is:
RuntimeError: Boolean value of Tensor with more than one value is ambiguous
This issue occurs in the slstm.py module, specifically at line 53 during a forward pass. Here's the relevant code snippet:
if i < self.num_layers - 1:
    # Further operations

It seems the variable i, which is expected to be an integer index, is somehow being interpreted as a tensor, leading to an ambiguous boolean condition in the if statement. This happens during the operation lstm_output, hidden_state = self.lstm(input_seq, hidden_state), suggesting that there might be an issue with how the LSTM output or hidden state is handled or initialized.
Request for Help
Could someone help clarify what might be going wrong here or suggest modifications to avoid this issue? Any guidance would be greatly appreciated.
Thank you!

Please check out this out, it should be fixed here

@muditbhargava66
This is actually a duplicate of the issue described here https://github.com/muditbhargava66/PyxLSTM/issues/4


Codesnippets

Offering the addition of VS Code Code Snippets. Using Code Snippets would allow devs to quickly build out custom components that extend the DynamicFormsElement class. When using the JS code snippet, it automatically transforms a filename into the correct class name format. For example lwc/myNewComponent/myNewComponent.js results in a class declaration that reads export default class MyNewComponent extends DynamicFormsElement {. All of the necessary imports, handlers, and callbacks are included. Similar updates included for HTML and js-meta.xml files.

[x] Tests pass (n/a)
[x] Appropriate changes to README are included in PR - Updated custom component section in docs
[x] CLA Submitted

Thanks for this proposal.
The intent of including the sample slider demo component in the README is to show the extension of the DynamicFormsElement component and the event communication mechanisms when creating a custom component.
The included snippet in this PR contains code which only allows the component author to render and edit one field at a time; which is only handful in an elementary example like the slider. This won't be sufficient if the user wants to do anything even slightly complex.
I am not sure that a user of this framework would get much benefit from having this very specific snippet; especially when the code sample is already included in the README.


add KS-GAME-1 to list

Installation worked using GPT(BIOS) in bsdinstall

awesome stuff, thanks @nkfilis


URLs being rewritten as invalid URLs

City of Frisco’s Vaccine Scheduling Site Open for Appointments March 17-18.eml.txt
Attached is an email where a non-image link https://friscotexas.us4.list-manage.com/track/click?u=33cd614c011fb86a5e16e4f59&id=8d0048bd24&e=67a88b413c was rewritten as an invalid URL https://friscotexas.us4./click?u=33cd614c011fb86a5e16e4f59&id=8d0048bd24&e=67a88b413c.

Thanks for the email. Will look into this

Fixed in 0.3.22

I think fewer links are broken, but in the sample email the first now still is. I think it's the link that starts on line 984 and ends on line 985:
To book an appointment <a href=3D"https://FriscoTexas.us4.list-m=
anage.com/track/click?u=3D33cd614c011fb86a5e16e4f59&id=3D8d0048bd24&e=3D67a8

Oops, accidentally left out my fix in 0.3.22. Should be OK now in 0.3.23. Sorry!

That worked, thanks!


Long tests

I was looking at a recent test run and saw this
1000.12s call     tests/model_selection/test_incremental.py::test_basic
17.06s call     tests/model_selection/dask_searchcv/test_model_selection.py::test_as_completed_distributed
10.88s call     tests/test_kmeans.py::test_check_estimator
8.63s call     tests/model_selection/test_split.py::test_20_newsgroups
8.35s call     tests/model_selection/test_incremental.py::test_search_basic
6.90s call     tests/model_selection/dask_searchcv/test_model_selection.py::test_scheduler_param[multiprocessing-4]
6.30s call     tests/model_selection/test_incremental.py::test_warns_scores_per_fit
5.72s call     tests/test_incremental.py::test_score
5.48s call     tests/model_selection/test_incremental.py::test_small
4.98s call     tests/model_selection/dask_searchcv/test_model_selection.py::test_scheduler_param_distributed

It looks like we have a timeout=1000 in one of our tests.
Running this locally test_basic does seem to hang for me for quite a while

Ah, this is bad on master, but not this bad.  I think that this hang is particularly an issue in @stsievert 's recent PR


fix issue5839

This try fix https://github.com/bytecodealliance/wasmtime/issues/5839
The normalize_cmp_value should accept IntCC as extra parameter.
So we can know  If this should signed extend or unsigned extend on int types.

normalize_cmp_value

Maybe routine normalize_cmp_value can accept the compare it singed or unsigned.
right now singed extend is always right.

In the future, could you please mention some words related to the issue in the PR title, rather than just the issue number? I ask this because Wasmtime is a very busy repository and many of us get notifications for all activity, which we then have to filter down manually - for instance, I don't work on Cranelift, so I end up manually muting all Cranelift issues and PRs.
This is a very minor inconvenience and I don't want to be negative on your work. I appreciate your involvement in this project!

@pchickey  Yeah sure.

@afonso360, you've been working on the sign-extension bits this PR relies on, as well as the select lowerings that this affects. What are your thoughts on this PR?
I was wondering if it would be better to pass an ExtendOp to normalize_cmp_value, instead of an IntCC. Most of the callers always want a zero-extend and some of them have to fake a condition code in this PR, so maybe passing the choice of sign-extending or zero-extending directly would be more clear.
I don't know what the best way to do this is. I think I understand this PR though, and if it looks good to @afonso360 then it looks good to me.

@jameysharp  It is hard to decide use IntCC or ExtendOp as  parameter to normalize_cmp_value too.
Because the function named normalize_cmp_value I thought maybe better pass the IntCC.
Actualy IntCC.Equal and IntCC.NotEqual make no differrence.

@jameysharp Maybe a convert So we can accept IntCC and ExtendOP both.

@jameysharp I have changed the parameter to ExtendOp.

@jameysharp @afonso360 I think we are ready.


Python 3 container : bash never give back shell control after commands end

Hello,

VSCode Version: 1.56.2 (user setup)
Local OS Version: Windows 10 with Docker v20.10.6
Name of Dev Container Definition with Issue: Python 3 (default)

Steps to Reproduce:

Open an folder empty folder under a git repository
New python 3 (default python version without node) dev container

Open a terminal : this take a very long time (up to a minute). Same after each command

When I comment the prompt __bash_prompt in /home/vscode/.bashrc this timeout is not happening

@playerla Unfortunately, I'm not able to reproduce this with the same system configuration.  What you describe could in theory be caused if git status is slow or not responding.  That can indicate you have another process somewhere on your system indexing your repository and/or locking it.
If you switch to zsh do you see the same issue?  (Just type zsh.)

You're right the prompt is unable to get repositories informations :

zsh has the same problem
I made a git init and all work fine. zsh show main branch. Bash doesn't even show repo information :
vscode ➜ /workspaces/user/Downloads/test $

Assuming I not want to use a git repository in my container. I had the issue when testing "try remote container" (could be for testing, or under other projects). I think the prompt should not freeze (while trying to display git information from outside the open folder).

I have assumed container isolation from host. I wondered why this behaviour : default workspace bind mount the user's home directory to /workspace. Several ways to fix it - using a default container or setting "HOST_PROJECT_PATH": "${localWorkspaceFolder}" in devcontainer.json as documented here

@playerla If you want a separate cloned copy that is isolated from the host, use the Clone Repository in Container Volume command instead.
Fundamentally in this case, the prompt can't access git status, which is actually quite unusual. Typically tools like Docker Desktop wouldn't cause this to happen unless you were doing something at the exact same time.  This is also  quite common as seen in the ZSH example which every theme in Oh My Zsh! will do (it's just using the standard git library it has).
Commenting out the line in question disables git from appearing in the command line which resolves the problem. Feel free to do that if it suits your needs best.  You can also uninstall git which may be safer since extensions and VS Code itself will likely try to interact in the same way.
FWIW - If you do decide to switch between Windows and Linux, be sure you have line ending set properly or you'll see strange behaviors.  VS Code will also try to interact with git via its source control mechanism. The model here is that you use the container like you would your local machine. However, that's not the common use case we're targeting.

@playerla Oh, one more tip.  If you really want to open a sub-folder without using git, you can use the workspaceMount property in devcontainer.json (or update your docker-compose.yml to mount  point) to mount file system one level up from where your .git folder is located. That's not what VS Code is optimized for (since no git operations or git related extensions will work), but you have that option if you so choose.

Docker desktop warns me that sharing files with container may be slow (https://stackoverflow.com/questions/64484579/docker-desktop-filesharing-notification-about-poor-performance). This was my issue, git status take 1m23.780s. (instead of ~5s on the host). I close the issue, not related to the container itself.
Thank you for all your advices.


Tesseract 4.1 Crash

Environment
Windows 7 Professional 64BIT

Tesseract Version:  4.1.0
Commit Number: not sure, from vcpkg
Platform: Windows

Hardware
CPU: i7-3770 (Intel official website indicates it has AVX,SSE supported)
Current Behavior:
It crashed when it tried to init.
(new tesseract::TessBaseAPI())
Crash Code: C000001D, illegal instruction set.
Have tried to disable avx flag.
avx2_available_ = false;
but its not working either.
*Edit: Tried debug the app, found out it crashed at instruction
vpxor mm mm which is an AVX2 instruction.
Expected Behavior:
Works on every other machine i have. i5 8250U, intel xeon.
Suggested Fix:

Please test tesseract executable instead your own custom code where reporting issue.

Hi @zdenop , yes. i have tried that too. Same thing.
I use the windows pre-built binary on the machine.
It crashed.

Try the latest windows binary from UB Mannheim and if it works try the latest git code.

Yes. My bad. Should have mentioned this.
The binary is from UB Mannheim.

The latest or 4.1.0?

@zhao-lun, please post the full command line which you used and all output from the program.

@zdenop 4.1.0
@stweil  tesseract.exe -v

Try the latest  version + provide full test case (code + how you compile it)

No other output? Please use https://digi.bib.uni-mannheim.de/tesseract/tesseract-ocr-w64-setup-v5.0.0-alpha.20191030.exe.

@zhao-lun, your issue report is not consistent. You write that your binary is from vcpkg, but you also write it is from UB Mannheim. UB Mannheim does not provide versions which only say 4.1, and their executable does not execute AVX instructions when running tesseract -v. There are also no AVX instructions in the constructor of TessBaseAPI.

Hi @zdenop, @stweil . I made a mistake. Apparently, i use the wrong binary, it's from the vcpkg installed\tesseract\x64-windows-rel\bin.
Anyway, i tested out pre-built binary from UB Mannheim, 4.1.0, 5.0.0 alpha it works.
It seem something wrong with the vcpkg built that caused the crash.
Im using the latest rev of vcpkg. which is the rev 4.1.0-3 port.
I have tried running both tesseract -v and launch tesseract.exe alone.
It access to AVX instructions (vpbroadcastid) even though i manually disable all the avx/avx2 flag.
avx2_available_ = false; *in SIMDDETECT.cpp

You  need to pass -DSW_BUILD=OFF to vcpkg  or maybe to build tesseract just with cmake, so you can have better control over build. It should be not big issue if you have leptonica build already.

You need to pass -DSW_BUILD=OFF to vcpkg or maybe to build tesseract just with cmake, so you can have better control over build. It should be not big issue if you have leptonica build already.

How do you pass -DSW_BUILD=OFF to vcpkg?

See https://github.com/microsoft/vcpkg/issues/8991. There is also nice how to Compiling Tesseract and Libleptonica (using vcpkg).


fix: clean up miscellaneous code

Changes

Clean up miscellaneous code.

Tests

[ ] make test passing
[ ] relevant integration tests passing

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@66299b2). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage        ?   73.24%
=======================================
  Files           ?       19
  Lines           ?     2033
  Branches        ?        0
=======================================
  Hits            ?     1489
  Misses          ?      381
  Partials        ?      163


UserType is not relay compatible

Prerequisites
Feel free to just say what you want and remove this template.

[ ] Is it a bug?
[ x] Is it a new feature?
[ ] Is it a question?
[ x] Can you reproduce the problem?
[x ] Are you running the latest version?
[ x] Did you check for similar issues?
[x ] Did you perform a cursory search?

For more information, see the CONTRIBUTING guide.
Description
Currently the UserType returned is not relay compatible and I can't find an easy way to override this so that the returned ID's would be a GlobalID instead of the current integer IDs that are returned. It looks like it would require reimplementation of the fields to then set a custom UserType object.
Any suggestions on how to obtain this or perhaps a new feature would be handy to override id on the models when using relay?

We should fix this. feel free to submit a PR.

BTW there is no need for it to be GlobalID (this is not relay spec compatible as well.) we can just prepend the type name ourselves.


Coffee script mode highlights division as regex

(Original issue 677 created by None on 2011-07-08T17:51:08.143721+00:00)
gy = Math.round(point.y / my)
highlights / my) as a red error of some sort
gx * mx / zd / d
highlights / zd / as a regex

(Original issue 677 last updated on 2012-02-05T08:16:11.835014+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by birkenfeld on 2012-02-05T08:16:11.826015+00:00)
This is meanwhile fixed in tip.


[SPARK-13792][SQL] Addendum: Fix Python API

What changes were proposed in this pull request?
This is a follow-up to https://github.com/apache/spark/pull/13795 to properly set CSV options in Python API. As part of this, I also make the Python option setting for both CSV and JSON more robust against positional errors.
How was this patch tested?
N/A

cc @felixcheung

Test build #60907 has started for PR 13800 at commit 1499753.

Test build #60907 has finished for PR 13800 at commit 1499753.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #3120 has started for PR 13800 at commit 1499753.

Test build #3120 has finished for PR 13800 at commit 1499753.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

cc @davies
any idea why this would fail python tests?

Maybe https://github.com/apache/spark/pull/13793 broke master. It was sent to branch-1.6 but merged into master and branch-2.0.

test this please

Test build #60914 has started for PR 13800 at commit 1499753.

Test build #60914 has finished for PR 13800 at commit 1499753.

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/60914/
Test PASSed.

Merged build finished. Test PASSed.


'There are news from your Corona-Warning-App' / "Es gibt Neuigkeiten von Ihrer Corona-Warn-App" notification is send ...

Feature description
Add a list of the latest news.
Problem and motivation
Occasionally the CWA (2.13.2) informs about news. Sometimes, however, one overlooks the “news” or cannot even determine what the “news” actually referred to.
I would therefore like to make the “news” available in a short list, for example in an additional menu item in the 3-dot menu on the main screen, like:

Aim: to read the latest news or to find out what news there was.
Similar:
"Neuigkeiten" / "Notification" (and the notification reason) like:

"Risk Classification"
"Certificates"
...

To what extent a delete function for 'old news' can be provided, I'll let it open - maybe one option is enough: "Delete all news".
Or, for example, a first-in / first-out stack with a maximum of 5 (?) entries.

Cross reference: "Es gibt Neuigkeiten von Ihrer Corona-Warn-App" notification is send repeatedly with red risk status.

I strongly support this! Since all notifications from the CWA have the same text, this would really be a helpful feature!

I also support this. I've seen the "Es gibt Neuigkeiten" quite a few times recently, and it mostly left me quite puzzled as to what is new. IIRC, sometimes there is an in-app popup or similar that shows some recent added functionality (?), but most of the time there's nothing.
In my case: I've got my mothers certificate stored as well (for 2 vaccinations), but not yet the certificate for her booster shot. When I open the app via the notification, it directly shows my mothers certificate (which is not favourited). I've previously wondered if the "Es gibt Neuigkeiten"-notification wants to tell me that a certificate is already 180 days in the past and should be updated (i.e. one should get a booster shot)? If this is the actual intention, then I'd strongly recommend to communicate it clearer.


Run containerized kraken as a kubernetes/openshift deployment

Further improve the ease of use of containerized kraken by providing an image on quay.io and creating a kubernetes or openshift deployment to run it.   Config can be provided via configmap.

When we run Kraken/Cerberus as a Kubernetes/OpenShift object, there might be cases where the pod which is running the tool might get disrupted unless we add a way to blacklist it during the run. For instance, we might not get the results from the pod running Kraken or Cerberus when the API iteself is down. When we run them external to OpenShift, we can get a signal and catch test failures even when the API is down. Thoughts?
But agree that we might need to support both - running it internal/external to the cluster to improve the ease of use and users can pick the option depending on the use case.

We can do something similar to https://github.com/openshift-scale/cerberus/tree/master/containers keeping in mind to avoid killing anything in namespace/node with kraken running.

@paigerube14 do you want to pick this?

Fixed by https://github.com/openshift-scale/kraken/pull/24. Thanks @paigerube14.


JS An invalid form control with name='input_name' is not focusable.

Laravel Version: 5.6.2
Voyager Version: 1.1.1

Description:
When I use a field Rich Text Box in the BREAD I can't submit the form because I get the following error on Javascript Console.
An invalid form control with name='input_name' is not focusable.
It works if I fill the hidden input with Inspector Tool or with an script.
Steps To Reproduce:

Add Rich Text Box as Field in BREAD
Submit even if the field is not empty

I started the project this week. I'm using Translatable trait on that model if it helps. So I republished the Voyager assets and I get the same error
An invalid form control with name='name_input' is not focusable.

Same here.

Quick workaround is to add novalidate to the form

same problem
An invalid form control with name='body' is not focusable.
when using validation in posts

Don't know if I am late to the party. Unfortunately, I have the same problem. The latest version, freshly published assets. Seems to happen in Chrome when TinyMCE that is required, since TinyMCE is hiding the original textarea.
The bug seems to exists.
https://github.com/tinymce/tinymce/issues/2584.
Which workaround has been tried?

Same here, fresh update 1.1.3 => 1.1.10, publish assets with -force flag, still have An invalid form control with name='body' is not focusable.

to remove the required prop you need either to override the default view or make field NULLable in database, plus change required setting in the data_rows table

I know. I mean as a "final" solution, as Voyager does not need the required prop at all.


Release v3.2.0

Release notes:

Add sandbox generation

My opinion on release notes:
• Adds capability to compute gateway sandbox subdomains based on a transaction ID


macOS/iOS fixes plus other generic fixes for clang and validation warnings

This fixes a recently reported macOS command line build issue against merged PR #965.  In addition this fixes some other macOS issues and adds generic fixes for clang warnings and some validation layer warnings in a few examples:

Fixes macOS command line builds when using cmake's make and ninja generators (restore -ObjC++ compiler flag).
Updates macOS versions of getAssetPath() and getShaderBathPath() to be tolerant of command line and Xcode builds with associated binary locations (e.g. in /bin or /bin/Debug or /bin/Release).
Fixes debugUtilsMessageCallback() to be tolerant of cases when pMessageIdName is null, which can occur when validation is on and using deprecated VK_USE_PLATFORM_IOS_MVK or VK_USE_PLATFORM_MACOS_MVK defines.
Fixes clang type warning in getValueAsInt() and missing overrides in the variablerateshading example.
Fixes validation layer warning on exit in the computeraytracing example - was missing the staging buffer destroy.
Restores the spacebar text visibility toggle in the textOverlay example.  This must have been lost during refactoring.
Adds support for VK_USE_PLATFORM_METAL_EXT which supercedes the deprecated VK_USE_PLATFORM_IOS_MVK and VK_USE_PLATFORM_MACOS_MVK platform defines.  This touches a lot of files but the changes are straight forward.  The only issue is that VK_USE_PLATFORM_METAL_EXT requires initialization using a Metal layer vs. the view, so I had to make a few Apple-only changes to support this.  I retained the deprecated platform options for backwards compatibility, but the default cmake setting is now VK_USE_PLATFORM_METAL_EXT.
Check for supported dynamic state features in the dynamicstate example vs. just the presence of extensions since these are not necessarily the same thing.  This is especially true for VK_EXT_extended_dynamic_state3.
Fixed the vkCmdDraw() vertexCount argument in the particlesystem example since the previous code used the buffer size and not the count.  This lead to multiple drawing artifacts as would be expected.
Updated the examples list and restored the benchmarking script to the top level.  This must have been lost when removing the bin directory.  I still find the script useful when regression testing changes - it's a quick way to run through all the examples (with validation on) without manually running each one.
Fixed validation warning in descriptorindexing example.  Was missing the VK_KHR_maintenance1 extension.
Added check for device max pipeline recursion depth to avoid validation warnings for limited capability devices in the raytracingcallable, raytracingintersection, raytracingreflections, and raytracingshadows examples.
Fixed build settings for OpenMP in the texture3d example for all platforms.  This used to work, but somehow things must have changed and the compiler flag settings and library location were not being set for the target.
Updated and simplified build instructions for macOS.

Tested on Windows 10, Manjaro Arch Linux, and macOS Ventura 13.6.6

The CI script is failing for macOS since the libomp path should now be /usr/local/opt/libomp/lib/libomp.dylib for homebrew on x86_64.   See the updated (simpler) build instructions for macOS in commit https://github.com/SaschaWillems/Vulkan/pull/1117/commits/20570645b180d1c07106b2218713702c60d152c7.
Even though it was building before, OpenMP was not actually working for any platform: Win, Linux, or macOS.

Thank you very much for your PR. This is very much appreciated.
I will take a look at this, but it may take a few weeks.

Thanks for agreeing to look at this.  No rush so feel free to take your time.
There are a lot of small things collected in this PR.  Each commit is a separate item (except VK_USE_PLATFORM_METAL_EXT, which is a bit larger), so hopefully this will make it easier to review.

Thanks for merging.


How does the Solarcoin code get updated?

I followed these instructions to successfully set up a node on my Raspberry Pi. I can update the system periodically that the node runs on but wonder about the node code itself. How does it get updated?
Thanks for pointing me in the right direction.

You can:

sudo systemctl stop solarcoind.service

cd solarcoin

git pull

Then it would show if there were any incremental updates to re-compile, if there were you basically recompile from around step 5 with:

cd src

make -f makefile.unix - e PIE = 1

strip solarcoind

sudo install -m 755 solarcoind /usr/local/bin/solarcoind

sudo systemctl start solarcoind.service

However there is a major new version of solarcoin core coming soon, and the installation process will be different, at that time a new guide may be required.


SudokuGame/DevanshKyada27

Fixes #869
Created a Sudoku game using HTML, CSS and JS.
Hope this solves the issue.
Looking forward for merging this PR.
Developer Checklist

[x] Followed guidelines mentioned in the readme file.
[x] Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)
[x] Starred ⭐ the Repo (Optional)

Summary
Created a sudoku game using HTML, CSS and JavaScript. Works completely fine.
Screenshot

Live Project Link
https://github.com/thinkswell/javascript-mini-projects/assets/143169520/2193bdf9-adac-4aab-917c-baf5c107da42

Hey @NitkarshChourasia you can refer to this PR, done all the changes that was required.
Looking forward for merging this PR.

@PBJI  Isn't the project directory, good?! As. @Haris-Mohanty is saying otherwise so.

Add under SudokuGame/DevanshKyada27 and not SudokuGame folder name.

Ok @PBJI will do it soon

Hey @NitkarshChourasia @PBJI you can refer to PR #1072 there I have made changes so can you please review it and merge it.


fix: use the db status endpoint for checking credentials

Instead of making a graphql query to validate token/clientId/branch, switch to the checking the db status endpoint. This should fix an issue where, when a new branch is created and indexing is still in progress, the query used in checkClientInformation fails because the index hasn't been created yet. This was happening before the waitForDb check and  resulting in Vercel build failures.

Testing this out in a PR deploy and found a few things:
The spinner logic we use doesn't really work well in CI:

The spinner logic we use doesn't really work well in CI:

We can probably check for process.env.CI before showing those types of animations.

The spinner logic we use doesn't really work well in CI:

We can probably check for process.env.CI before showing those types of animations.

Just made that fix!