Implementation of pattern matching in the building of type driven algorithms

Proposed title of article
Implementation of pattern matching in the building of type driven algorithms
Proposed article introduction
Pattern matching is the process of determining whether a specific sequence of characters, tokens, or data occurs among the given data. It can also be used to find and replace a matching pattern in a text or code with another text or code. Every application with search capabilities makes use of pattern matching in some way.
In this article, we are going to look in details what pattern matching entails and explore the various methods in which pattern matching is used in the implementation of various concepts. This will be followed by back to back examples for the purposes of description.
Key takeaways

A look at scenarios for pattern matching
A look at pattern matching designs
A look at the implementation of  the basic toll calculations

Article quality
The article mainly aims at providing high quality content that will be well understood by all our learners
References
n/a

Sounds like a helpful topic - lets please be sure it adds value beyond what is in any official docs and/or what is covered in other blog sites. (the articles should go beyond a basic explanation - and it is always best to reference any EngEd article and build upon it).
Please be attentive to grammar/readability and make sure that you put your article through a thorough editing review prior to submitting for final approval. (There are some great free tools that we reference in EngEd resources.)
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.
Please be sure to double check that it does not overlap with any existing EngEd articles, articles on other blog sites, or any incoming EngEd topic suggestions (if you haven't already) to avoid any potential article closure, please reference any relevant EngEd articles in yours. - Approved


FEAT: Added Installer initial Version.

Description
This PR introduces a new widget to help users select the appropriate conda installer based on their needs. The widget will guide users through the available installation options, providing a more user-friendly experience for choosing the right installer.
Related Issue

Resolves Issue #81

Details
This widget will include the following installation options:

Anaconda installer
Miniconda installer
Miniforge installer
Mambaforge installer
Micromamba installer
Pixi

@jezdez @kathatherine Made those changes that were required. Thank you for correcting my mistakes.

@Avik-creator Looking at the preview, I'm seeing no space between the colon and the definition in each of these configuration sections. Could we add spaces there? Such as:
OS: Linux
Architecture: x64
Installer: Miniconda
Default Channel: defaults

This will look cleaner than the above image.

Nice! I think we should start with the type of installer, and then offer platform / architecture choices. Also, are we planning to redirect directly to the installer URL? Right now it only leads to the installation instructions, where the user might not now how to proceed and wonder why they chose a platform and architecture if they have to find that specific item again.

@jaimergp we can give the download URL directly. That won’t be an issue. If you want that do let me know, will then do it that way.

Made the update, that I got as a feedback. Regarding the Positioning we can change it afterwards. Now shall I give the download url instead of Installation Guide? @jaimergp

Now shall I give the download url instead of Installation Guide.

Yes, please. Best thing would be to offer both: direct link to the installer and installation guide.


Draft: Feat: application_controller should be responsible for deleting application revision

Description of your changes

Fixes #5710
I have:

[x] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

Is it still a draft PR or ready for review?

it's draft
@Somefive could you help quick look the PR? whether as expected or not, thanks

@dhanusaputra Sorry for the late reply. Generally this is what we what, moving the revision cleanup function into GarbageCollect. There are several things you could look into

Try to keep GarbageCollect(context.Context, ...GCOption) (bool, []v1beta1.ManagedResource, error) unchanged. The reconcile client should be passed in through the resourceKeeper, not the function parameter.
DisableAllApplicationRevisionGCOption -> DisableApplicationRevisionGCOption
For DisableAllComponentRevisionGCOption, try to merge it to the existing component revision gc in resourceKeeper.

BTW, great job!


Kadane Algorithm

I want to add code to explain kadane algorithm as it is a very important concept.
Can you pls assign this to me.

Hey @aaryahjolia, I'm a GSSoC'23 contributor and a competitive coder as well. I want to add code + diagrammatic explanation of Kadane's algorithm. Could you please assign this task to me?


Reorganize figure generation to its own package

This refactors figure generation functionality into its own package niclips. The purpose of the package is to provide utilities for generating simple figures that run faster than more powerful counterparts in nilearn.

Thanks for the reminder about the linting. I ran it locally and indeed it fixed a bunch of issues. Also I saw your #6 which we'll take care of next.


Updates for kli to work with new Hab changes, one minor fix in challenge verify and removing some prints

Signed-off-by: pfeairheller<EMAIL_ADDRESS>

Codecov Report

Merging #351 (87df89a) into development (8db7658) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development     #351      +/-   ##
===============================================
- Coverage        92.62%   92.62%   -0.01%
===============================================
  Files              116      116
  Lines            36407    36405       -2
===============================================
- Hits             33723    33721       -2
  Misses            2684     2684

Impacted Files
Coverage Δ

src/keri/app/forwarding.py
83.06% <ø> (-0.14%)
:arrow_down:

src/keri/app/indirecting.py
81.46% <ø> (-0.05%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


BUPT#307

📰Poster - Predicting Prosodic Prominence from Text with Pre-trained Contextualized Word Representations
#350
1. Oral / Poster Selection

[ ] 🗣 Oral (15 MIN)
[x] 📰 Poster (5 MIN)

2. Paper Information

Paper
Information

Name
Predicting Prosodic Prominence from Text with Pre-trained Contextualized Word Representations

Recommendation
Predicting Prosodic Prominence from Text

Prior Knowledge
bert bilstm

Year
2019

Author
Aarne Talman, et. al.

GitHub
https://github.com/Helsinki-NLP/prosody

Arxiv
https://arxiv.org/pdf/1908.02262.pdf

3. After Party 🍻

[ ] 🍻 YES! I'll definitely join the After Party!
[ ] 🤔 Maybe. I'd like to decide later.
[x] 🛌 No, I'm afraid not this time.

4. New Friend

[ ] 👥 I'll bring a new friend
[x] 👤 There's no new friend from me

Artificial Intelligence & Machine Learning CLUB, 2018 - 2019 AI ML Club - AMC Member Manual

You should refer to #345 (the blog comments) instead of #350 (which is this pr itself).


[Archery] Crossbow refuses to run on the main branch of a fork

Describe the bug, including details regarding any error messages, version, and platform.
When invoking @github-actions crossbow submit ... on a PR made from a fork's main branch, Archery fails triggering the builds. Example:
https://github.com/apache/arrow/pull/39878#issuecomment-1933766758
Result:
https://github.com/apache/arrow/actions/runs/7828116460/job/21357317509#step:5:18
Run archery trigger-bot \
  archery trigger-bot \
    --event-name issue_comment \
    --event-payload /home/runner/work/_temp/_github_workflow/event.json
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.8.18/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.8.18/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.18/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.18/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.18/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.8.18/x64/lib
    ARROW_GITHUB_TOKEN: ***
    CROSSBOW_GITHUB_TOKEN: ***
fatal: not a git repository (or any of the parent directories): .git
Cloning into '/tmp/tmpze7d9_8y/arrow'...
fatal: refusing to fetch into branch 'refs/heads/main' checked out at '/tmp/tmpze7d9_8y/arrow'
ERROR:archery:Command '['git', '-C', '/tmp/tmpze7d9_8y/arrow', 'fetch', 'origin', 'pull/39878/head:main']' returned non-zero exit status 128.

Component(s)
Archery, Continuous Integration

Reopening as the PR didn't fix the issue.


Can ninja be the default make tool for yotta on linux-based systems?

Can yotta be set to use ninja as the default make tool as it's faster :)
Apparently this is already the case for the windows world.

Yup I think this is a good idea.

Thought you might


Streamline CMake and build system, move to newer protobuf

Should be ready for final review. Changes a lot of stuff, but tested a lot so far (but could use more) More notes on testing in comments below.

Now that protobuf is updated in upstream homebrew, a lot more updates here, but I think it's finally ready for review. All build work on my machine(s) under the following:
canon/apt amd64 (make setup lint build install test) (also appimage)
canon/apt arm64 (make setup lint build install test) (also appimage)
linux/brew amd64 (make setup lint build install test)
mac/brew arm64 (make setup lint build install test)
The github workflows that were changed were tested manually:
test.yml https://github.com/viamrobotics/viam-cartographer/actions/runs/5327906791
appimage.yml https://github.com/viamrobotics/viam-cartographer/actions/runs/5327704981
That said, please test further on your own team and make sure I haven't broken some use case or workflow I wasn't aware of.

@Otterverse I think the lint step is broken on this PR

@Otterverse this looks great to me! Thanks for all the work you put in & for making the cartographer build system much more reliable & maintainable.


render method

This commit replaces the side-effecting __init__ constructor with a
render() method on the Element. This allows delaying attaching
an element until the method is called which in turn allows using
elements as first-class values.
Closes #149

Is this to realize the behavior of a kind of lazy elements/objects which will be instantiated later in run time?

Is this to realize the behavior of a kind of lazy elements/objects which will be instantiated later in run time?

Yes, sort of. It makes it easier to construct and pass Elements around as first-class values because now rendering is not a side-effect of Element construction.


feat(networks): group networks for swarm endpoints

Closes #2021

@itsconquest do you have any error on console in debug tool ? I can't reproduce your behaviour with local dev version nor with portainerci/portainer:pr3028 image.
Make sure to clear cache (ctrl + shift + R) and local storage.

Just reproduced this on my second machine on both chrome & firefox, with nothing reported in console. Have cleared cache, local storage and cookies.

Ubuntu 18.04.2 LTS
Docker 18.09
FireFox 68.0.1 (64Bit)
Chrome 75.0.3770.142 (Official Build) (64-bit)
portainerci/portainer:pr3028 image

@itsconquest after testing with a swarm with 2 nodes I found the bug.
This should be fixed now.


Blog 2 - "Tips and Tricks"

We need to add content for the " Ortelius Tips and Tricks" blog category.  Please create your blog in Google docs under the /blog directory. https://ortelius.io/category/ortelius-tips-and-tricks/
A suggestion would be 'how to publish your microservice to a domain.'

This blog helps us reach our "increase the sign ups by Q2021". Having tips and tricks for informational blogs on setting up Ortelius will be really helpful in meeting this goal.

This blog helps us reach our "increase the sign ups by Q2021". Having tips and tricks for informational blogs on setting up Ortelius will be really helpful in meeting this goal.


adding epel due to error

Without epel enabled on the bastion the following occurs.
ERROR! Attempted to execute "inventory/gce/hosts/gce.py" as inventory script: Inventory script (inventory/gce/hosts/gce.py) had an execution error: GCE inventory script requires libcloud >= 0.13

Adding epel to gcloud.sh bastion resolves this error.

Ah, I'm sorry, I've missed this PR. Please see the #342 instead.


Docs build stability under Vercel

Often when we build a branch, Vercel throws an error. When it's happened to me, Vercel has reported many broken links. However, these links were on pages I hadn't changed in the branch, neither had I changed the destination pages. A rebuild fixes the issue. @janpio has also encountered this issue.
This not only directly slows down the process of working on docs, but the rebuild impacts on other work, because our rebuild takes up server resources.
I can't link to an example, because my affected branches are now deleted, but when it happens again, I'll link to it here.

A good source for ideas where this happend is the #feed-docs-vercel-failures internal Slack channel.

This Slack thread has some examples of deployments with broken links


Cannot call class stub directly

class C():
    def f2(self, x):
        return x*2
c = C()
stub = sinon.stub(c, 'f2')
stub.returns(5)
assert c.f2() == 5
assert stub() == 5 # fails, returns None

Thanks for pointing out this issue.  I didn't know SinonJS can be used in that way.
This could be fixed by modifying __call__ in base.py.

if self.args_type == "PURE":
    return getattr(self.pure, "func")(*args, **kwargs)

An args_type of "PURE" means that the end user created an independent spy/stub with spy = sinon.spy() or stub = sinon.stub()?


when I try to open visual studio the process is sluggish

The system looks very slow!

Can you please describe in a little more details what you are observing?

I think the it's already fixed, now Microsoft Visual studio takes only 18s in the opening process. Maybe some update in the system fitxed it.
thanks for your attention


Context menu

Options for Back, Refresh, Adding as Bookmark, Saving

Done with https://github.com/dotcomboom/gopherit/commit/5999740d119e5ef0ad3735651c366be7f0876a33


Implement Actor Critic Agent

Implement and explore the effectiveness of actor critic agent.

About AC
An effective learning method called Asynchronous Advantage Actor Critic (A3C) published by DeepMind. This algorithm beats the famous DQN by quite a margin.
https://medium.com/@henrymao/reinforcement-learning-using-asynchronous-advantage-actor-critic-704147f91686


Support sharing playlists to other users

I'm imagining some setting in the recipe to specify certain users (default server owner only?) and preferably also a flag to bypass that and add to all users.
Adding the playlist to other users should be relatively straight forward using this https://python-plexapi.readthedocs.io/en/latest/modules/playlist.html#plexapi.playlist.Playlist.copyToUser
Is there a way to delete/update another user's playlist? Overwrite?
I'm also not sure how you would get a list of all users.

There are 2 types of the TOKENs per account, user and server. You as the server admin have access to the server TOKENs that shared users use to connect to your server. With this you can modify somethings for them.
With plexapi:
from plexapi.server import PlexServer
plex = PlexServer(PLEX_URL, PLEX_TOKEN)
account = plex.myPlexAccount()
users = account.users() # get all your plex users
for user in users:
    user_server = PlexServer(PLEX_URL, user_acct.get_token(plex.machineIdentifier))
    user_playlist = user_server.playlist('That Playlist')

With the user_server you can do what you would with your plex object. Obviously you have some restrictions because you're a user and not the admin but most of the methods will return something. user_playlist being one of them.
Here is an example of how I use this method to share playlists.

Finished the functionality. Share to specific users or share to all indicated in recipe, but adding the CLI flag for override now. Pull request coming soon.


Duplicated dockerfile query - "Last User Is 'root'"

It seems there are 2 "non root user" queries -
assets/queries/dockerfile/last_user_is_root
assets/queries/dockerfile/missing_user_instruction

Hi @lioskaderon hope you are doing great!
Those 2 queries have the same objective but they check it in diferent ways.
Last User Is 'root' query checks for the hardcoded user root command when using a multistaged docekrfile.
Missing User Instruction query checks if there is no specified user in a dockerfile.
Let me know what do you think.
In case of any other matter please do not hesitate to contact us!

Hi @lioskaderon,
Can you give us your feedback, please?

Hi @lioskaderon ,
Hope this message finds you well!
I'm closing this issue due to inactivity.
Feel free to re-open the issue if you need our support.


fix(icon): dependency on icon package

Describe pull-request
Updated package-lock to include dep on icon/typo/color
Solving issue
Fixes: CDEP-2709
How to test

Go to Storybook
Check in Icon
Make sure both component and Css Icon works.

Not saying it doesn't, but how does this address the issue linked in Jira?
Just for my own understanding.

Not saying it doesn't, but how does this address the issue linked in Jira? Just for my own understanding.

It updates the package-lock to set the dev dependency between @scania/components and @scania/icons.
All I did to "fix" this was to do a npm i in the components folder.

Tested and passed.
https://deploy-preview-1059--sdds-storybook.netlify.app/?path=/story/component-icons--component page contains icon

Issue related to build config.


conda fermi : problem activating in tcsh

I installed latest fermitools with conda 4.6.14
I did
conda init tcsh
conda init bash
conda activate fermi             works under bash but not under tcsh
under tcsh, 'your shell has not been activated'  and    it just tells me to  conda init tcsh
which then returns 'no action' with a list of the shells scripts.
.tcshrc is modified but does not have the required effect, also when restarting tcsh
I also notice that conda init is 'Experimental' according to conda ---help
I can work with bash but it is not my standard shell.

NB I had previously used conda 4.2 for the init, before upgrading to 4.6
Perhaps the old init was erroneour, but how can I reset it? Edit .tcshrc by hand or is there a better way?

We’ve had another report of problems with csh, which I was able to reproduce. It looks like conda has broken the activation for (t)csh users in their most recent releases. It think you'll have to downgrade conda for now.
The current version of conda is 4.6.14.  Based on the conda release notes, they have made various changes to the activation, especially for Windows, in the last few releases. I'm guessing they broke the csh activation in doing so.  Their support for tcsh/csh has always been problematic.
I managed to downgrade to 4.6.12 (downgrading to 4.6.13 failed) and the activation worked again.
We'll have to file a bug with the conda developers and add a note to our Troubleshooting page.  In the meantime, you can try downgrading conda:

deactivate any conda environments
run conda install conda=4.6.12
Start a fresh shell or log back out and in again to make sure nothing lingers from before.
Activate conda.

thanks, I may try that.
but if a bugfix is expected soon I can live with running under bash for
now.
On 2019-05-06 15:33, Don Horner wrote:

We’ve had another report of problems with csh, which I was able to
reproduce. It looks like conda has broken the activation for (t)csh
users in their most recent releases. It think you'll have to downgrade
conda for now.
The current version of conda is 4.6.14. Based on the conda release
notes [1], they have made various changes to the activation,
especially for Windows, in the last few releases. I'm guessing they
broke the csh activation in doing so. Their support for tcsh/csh has
always been problematic.
I managed to downgrade to 4.6.12 (downgrading to 4.6.13 failed) and
the activation worked again.
We'll have to file a bug with the conda developers and add a note to
our Troubleshooting page. In the meantime, you can try downgrading
conda:

deactivate any conda environments
run conda install conda=4.6.12
Start a fresh shell or log back out and in again to make sure
nothing lingers from before.
Activate conda.

--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [2], or mute the
thread [3].
Links:
[1] https://github.com/conda/conda/blob/master/CHANGELOG.md
[2]
https://github.com/fermi-lat/Fermitools-conda/issues/34#issuecomment-489622031
[3]
https://github.com/notifications/unsubscribe-auth/AEJV6HMFD3HXXRZKIL3MH2TPUAXTVANCNFSM4HK6YC3A

We have a beta release that should fix this issue.  It would be great if you could test it.  You can install the beta (we recommend creating a separate conda environment for testing) with the command:
conda create --name fermi_dev -c conda-forge/label/cf201901 -c fermi/label/beta -c fermi fermitools=1.0.5
Due to some metadata changes, it will probably also install fermitools-data and some other packages again.
You can see full instructions on this page:
https://github.com/fermi-lat/Fermitools-conda/wiki/Testing-the-Fermitools
Let us know if it works.

OK thanks!
I don't quite understand: a new conda release which works for tcsh (if
so what anaconda version is it) or a
new Fermitools which gets around the existing conda 4.6 tcsh problem?
Andrew
On 2019-05-14 17:04, Don Horner wrote:

We have a beta release that should fix this issue. It would be great
if you could test it. You can install the beta (we recommend creating
a separate conda environment for testing) with the command:
conda create --name fermi_dev -c conda-forge/label/cf201901 -c
fermi/label/beta -c fermi fermitools=1.0.5
Due to some metadata changes, it will probably also install
fermitools-data and some other packages again.
You can see full instructions on this page:
https://github.com/fermi-lat/Fermitools-conda/wiki/Testing-the-Fermitools
Let us know if it works.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HOA7BRW2UPOSDDYBZLPVLIGLA5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVLY2RI#issuecomment-492277061
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HLDR6JI54KNGT4M4ETPVLIGLANCNFSM4HK6YC3A

The second, a new Fermitools that includes a workaround.

This might not matter to your testing, but it looks like the beta was installing an old beta version of the fermitools-data package (0.15 vs. the current 0.17) that doesn't have the latest files, like the interstellar emission model.  That wouldn't have affected the activation but could have caused problems if you tried to do an analysis in the fermi_dev environment.  We've corrected that now.

thanks, I did not install it yet so will get the latest.
On 2019-05-14 22:06, Don Horner wrote:

This might not matter to your testing, but it looks like the beta was
installing an old beta version of the fermitools-data package (0.15
vs. the current 0.17) that doesn't have the latest files, like the
interstellar emission model. That wouldn't have affected the
activation but could have caused problems if you tried to do an
analysis in the fermi_dev environment. We've corrected that now.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HKIBML7HS2KL3A2ME3PVMLSZA5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVMUHZI#issuecomment-492389349
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HNFITMCKSABAKFKPLDPVMLSZANCNFSM4HK6YC3A

A fix for this has been included in the latest release of the Fermitools (Fermitools=1.0.5).

thanks! so this is no longer beta (you mentioned before) but I can
happily do
conda updata fermi         ?
On 2019-05-21 16:41, jasercion wrote:

A fix for this has been included in the latest release of the
Fermitools (Fermitools=1.0.5).
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HLYWQ2UOY2JS7GF7QDPWQCX7A5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4EGUQ#issuecomment-494420818
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HK6E7JRAR74YMUIRJDPWQCX7ANCNFSM4HK6YC3A

Yes, you should run: conda update -c conda-forge/label/cf201901 -c fermi fermitools

I did that, have 1.0.5
but it does not help
tcsh:
conda activate fermi
CommandNotFoundError: Your shell has not been properly configured to use
'conda activate'.
To initialize your shell, run
 $ conda init <SHELL_NAME>

Currently supported shells are:

bash
fish
tcsh
xonsh
zsh
powershell

See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running
'conda init'.
[aws@olga4 ~]$ conda init tcsh
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/condabin/conda
no change     /afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/conda
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/conda-env
no change     /afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/activate
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/deactivate
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/etc/profile.d/conda.sh
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/etc/fish/conf.d/conda.fish
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/shell/condabin/Conda.psm1
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/shell/condabin/conda-hook.ps1
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/lib/python3.7/site-packages/xonsh/conda.xsh
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/etc/profile.d/conda.csh
no change     /afs/ipp-garching.mpg.de/home/a/aws/.tcshrc
No action taken.
[aws@olga4 ~]$ conda activate fermi
CommandNotFoundError: Your shell has not been properly configured to use
'conda activate'.
To initialize your shell, run
 $ conda init <SHELL_NAME>

Currently supported shells are:

bash
fish
tcsh
xonsh
zsh
powershell

See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running
'conda init'.
(Also after restarting shell). Do I perhaps have to cleanup .tcshrc  or
something?
On 2019-05-21 19:14, Don Horner wrote:

Yes, you should run: conda update -c conda-forge/label/cf201901 -c
fermi fermitools
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HOFRDN4TTU6U2JMMADPWQUXDA5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4SQAY#issuecomment-494479363
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HLWT2AZVJW24DBVI4DPWQUXDANCNFSM4HK6YC3A

maybe I should do
conda init --reverse               ?
On 2019-05-22 11:08, aws wrote:

I did that, have 1.0.5
but it does not help
tcsh:
conda activate fermi
CommandNotFoundError: Your shell has not been properly configured to
use 'conda activate'.
To initialize your shell, run
$ conda init <SHELL_NAME>

Currently supported shells are:

bash
fish
tcsh
xonsh
zsh
powershell

See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running
'conda init'.
[aws@olga4 ~]$ conda init tcsh
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/condabin/conda
no change     /afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/conda
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/conda-env
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/activate
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/bin/deactivate
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/etc/profile.d/conda.sh
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/etc/fish/conf.d/conda.fish
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/shell/condabin/Conda.psm1
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/shell/condabin/conda-hook.ps1
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/lib/python3.7/site-packages/xonsh/conda.xsh
no change
/afs/ipp/.cs/anaconda/amd64_generic/3/2019.03/etc/profile.d/conda.csh
no change     /afs/ipp-garching.mpg.de/home/a/aws/.tcshrc
No action taken.
[aws@olga4 ~]$ conda activate fermi
CommandNotFoundError: Your shell has not been properly configured to
use 'conda activate'.
To initialize your shell, run
$ conda init <SHELL_NAME>

Currently supported shells are:

bash
fish
tcsh
xonsh
zsh
powershell

See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running
'conda init'.
(Also after restarting shell). Do I perhaps have to cleanup .tcshrc
or something?
On 2019-05-21 19:14, Don Horner wrote:

Yes, you should run: conda update -c conda-forge/label/cf201901 -c
fermi fermitools
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HOFRDN4TTU6U2JMMADPWQUXDA5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4SQAY#issuecomment-494479363
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HLWT2AZVJW24DBVI4DPWQUXDANCNFSM4HK6YC3A

Instead of running "conda init", can you try just running:
source </path/to/conda>/etc/profile.d/conda.csh
where </path/to/conda> is replaced with the path to the top level directory of the Anaconda installation (typically named something like "Miniconda2") and then run conda activate fermi. You may want to comment out any of the conda stuff already in your .tcshrc and start with a clean shell.

thanks, but anaconda is provided by our computer center so making my own
installation is not so nice, I can do it of course.
Is the workaround only valid for the conda.csh you mention below?
what is wrong with conda init --reverse  (I did not want to risk that
yet though)
perhaps I should just wait till anaconda fixes the bug, since running
under bash is not a big deal for the time being.
Andrew
On 2019-05-22 17:42, Don Horner wrote:

Instead of running "conda init", can you try just running:
source </path/to/conda>/etc/profile.d/conda.csh
where </path/to/conda> is replaced with the path to the top level
directory of the Anaconda installation (typically named something like
"Miniconda2") and then run conda activate fermi. You may want to
comment out any of the conda stuff already in your .tcshrc and start
with a clean shell.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HJ62ZLP6YOMNJKAKBLPWVSX7A5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7PESA#issuecomment-494858824
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HP6TRDVPTR7MK7KRD3PWVSX7ANCNFSM4HK6YC3A

I located conda.csh on the computer center installation. Will try it.
On 2019-05-24 10:17, aws wrote:

thanks, but anaconda is provided by our computer center so making my
own installation is not so nice, I can do it of course.
Is the workaround only valid for the conda.csh you mention below?
what is wrong with conda init --reverse  (I did not want to risk that
yet though)
perhaps I should just wait till anaconda fixes the bug, since running
under bash is not a big deal for the time being.
Andrew
On 2019-05-22 17:42, Don Horner wrote:

Instead of running "conda init", can you try just running:
source </path/to/conda>/etc/profile.d/conda.csh
where </path/to/conda> is replaced with the path to the top level
directory of the Anaconda installation (typically named something like
"Miniconda2") and then run conda activate fermi. You may want to
comment out any of the conda stuff already in your .tcshrc and start
with a clean shell.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HJ62ZLP6YOMNJKAKBLPWVSX7A5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7PESA#issuecomment-494858824
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HP6TRDVPTR7MK7KRD3PWVSX7ANCNFSM4HK6YC3A

On 2019-05-24 12:51, aws wrote:

I located conda.csh on the computer center installation. Will try it.
That worked. Thanks.

On 2019-05-24 10:17, aws wrote:

thanks, but anaconda is provided by our computer center so making my
own installation is not so nice, I can do it of course.
Is the workaround only valid for the conda.csh you mention below?
what is wrong with conda init --reverse  (I did not want to risk that
yet though)
perhaps I should just wait till anaconda fixes the bug, since running
under bash is not a big deal for the time being.
Andrew
On 2019-05-22 17:42, Don Horner wrote:

Instead of running "conda init", can you try just running:
source </path/to/conda>/etc/profile.d/conda.csh
where </path/to/conda> is replaced with the path to the top level
directory of the Anaconda installation (typically named something
like
"Miniconda2") and then run conda activate fermi. You may want to
comment out any of the conda stuff already in your .tcshrc and start
with a clean shell.
--
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].
Links:
[1]
https://github.com/fermi-lat/Fermitools-conda/issues/34?email_source=notifications&email_token=AEJV6HJ62ZLP6YOMNJKAKBLPWVSX7A5CNFSM4HK6YC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7PESA#issuecomment-494858824
[2]
https://github.com/notifications/unsubscribe-auth/AEJV6HP6TRDVPTR7MK7KRD3PWVSX7ANCNFSM4HK6YC3A


Getty console spamming log file (Stretch)

Hi. After upgrading to Debian Stretch, Getty keeps writing in logs:
daemon.log :
Jul 1 02:19:00 scw-41e967 systemd[1]<EMAIL_ADDRESS>Service has no hold-off time, scheduling restart.
Jul 1 02:19:00 scw-41e967 systemd[1]: Stopped Getty on ttyAMA0.
Jul 1 02:19:00 scw-41e967 systemd[1]: Started Getty on ttyAMA0.
syslog
Jul 1 02:21:10 scw-41e967 systemd[1]<EMAIL_ADDRESS>Service has no hold-off time, scheduling restart.
Jul 1 02:21:10 scw-41e967 systemd[1]: Stopped Getty on ttyAMA0.
Jul 1 02:21:10 scw-41e967 systemd[1]: Stopped Getty on ttyAMA0.
Jul 1 02:21:10 scw-41e967 systemd[1]: Started Getty on ttyAMA0.
Jul 1 02:21:10 scw-41e967 systemd[1]: Started Getty on ttyAMA0.
auth.log
Jul 1 02:20:50 scw-41e967 agetty[4135]: /dev/ttyAMA0: cannot open as standard input: No such file or directory
On boot :
scw-41e967 systemd[1]: dev-ttyS1.device: Job dev-ttyS1.device/start timed out.
scw-41e967 systemd[1]: Timed out waiting for device dev-ttyS1.device.
scw-41e967 systemd[1]: Dependency failed for Serial Getty on ttyS1.
This happens with Debian Stretch only with an untouched configuration (since first boot), and it was tested on multiple servers (C2S).
I had to disable Getty to stop the logs.
systemctl stop getty@ttyAMA0
systemctl disable getty@ttyAMA0
As I was told, maybe after the update to Stretch, an internal serial port got renamed from ttyAMA to ttyS?

This happens to me too. Any progress on this?

This started happening to me after I installed fail2ban. No idea how to solve it though. @beeriz did you figure something out?

Nope. Sry.

@analytik
systemctl stop getty@ttyAMA0
systemctl disable getty@ttyAMA0
Worked fine for me, I also have fail2ban, but the issue stated way before installing it.

Same issue here with a fresh scaleway debian stretch server.
Oct 23 22:06:02 scw-67fd75 systemd[1]: Started Getty on ttyS0.
Oct 23 22:06:02 scw-67fd75 systemd[1]: Started Getty on ttyS0.
Oct 23 22:06:02 scw-67fd75 systemd[1]: Stopped Getty on ttyS1.

Issue is already discussed here, and maybe this is the root cause?

@beeriz comment worked for me on a Scaleway Debian while the error came with no obvious reason.

i solved it in a very simple way http://robertoviola.cloud/2020/06/24/stop-tty0-from-flooding-your-logs/ :)


add overleaf files

git clone https://git.overleaf.com/64906c638a342c94ac24d64b manuscript
rm -rf manuscript/.git

[ ] Makefile for building the manuscript
[ ] Remove all mentions of googlesheets

[ ] check all files are anonymized.


Can't output text file contents as string to Slack

Most likely this is not an issue, but something I'm just getting wrong. I'm reading in a text file with fs.readFile and assigning the string retrieved to the message to post to Slack. The file is being read, I can trace out the content string to the console, but nothing gets posted in Slack. No error is returned that I can see. Here's a sample of what I'm doing:
fs.readFile('infos/tuesday.txt', 'utf8', function (err,data) {
              if (err) {
                return console.log(err);
              }
              reply = "OK, here you go:\n\n" + data;
            });

bot.reply(message,reply);

An extract from the text file (names have been changed, as have URLs. content structure is the same):
09:00 Doors open // Registration

10:00 *Breaking out of the box*

Speaker: John Smith - https://conf.com/events/speakers/johnsmith

_In this talk John Smith will talk about stuff._

The text files were created with textedit on a Mac. They are plain text, UTF-8, and do not contain any formatting (markup) characters other than the ones you can see above. As I say, the string read in (data) traces out fine.
Any ideas where I could be going wrong?
Thanks!!!

Beginner's error - I was sending the reply outside of the asynch fs.readFile callback. The good news is that all actually works fine when I send the reply from within the callback.


CNCF SIG-Runtime Discussion/Presentation?

Hello Swam team,
I'm one of the co-chairs of the CNCF SIG-Runtime, I'm reaching out and think it would be great for you to present/discuss the project at one of our meetings. For example, discuss things such as architecture overview and use cases.
Let me know if this something you'd be interested in doing. If yes, please feel free to add it to our agenda or reach out to me (raravena80 at gmail.com)
Thanks!

Hi @raravena80,
This is a great idea, and I would love to talk about the project. I still have to figure out how my new year will look like and cannot commit on a presentation for now. I see these meetings happen twice a month, so I might register for a later month when I know more about my available time if this is ok for you.

Hi @raravena80,
This is a great idea, and I would love to talk about the project. I still have to figure out how my new year will look like and cannot commit on a presentation for now. I see these meetings happen twice a month, so I might register for a later month when I know more about my available time if this is ok for you.

Hi @satabin,
That sounds good.
Thanks!

Hi @satabin,
That sounds good.
Thanks!

Hi @satabin,
Just checking-in. Would the team be interested in presenting at our next meeting? (April 1st)
Thanks.

Hello @raravena80,
April 1st won't be possible for me, I didn't have time lately to work on this project. I could think about something for the ones starting from June I think, if that works for you?

Hi @satabin,
Yep, that works!
Thanks!


Peer management multiple PUT request doesn't disconnect properly.

Notice there seems to be a weird case if you perform multiple PUT request on a peer with a url to the original cloud server it creates multiple connections after first request.
Example: Hub1 -> Cloud
curl -X PUT --data url='http://cloud' http://cloud/peer-management/<connection_id_1>
At this point hub1 will disconnect from cloud and reconnect back to cloud.
To force a second disconnect:
curl -X PUT --data url='http://cloud' http://cloud/peer-management/<connection_id_2>
After this request the hub goes into a loop trying to connect to the cloud but receives a 409 conflict because it's already peered.

When using the method PUT on a peer should we be creating a new peer connection? Or just updating the existing one's url?
https://github.com/zettajs/zetta/blob/0cf2f11fc793e5a69ee577807eed1246434d9476/lib/api_resources/peer_management.js#L121-L140


openttd 1.5.3 + El Captain build fixes

@BrewTestBot test this please.

Thanks a lot @veprbl! :tada:


Disable 340 for premerge and nightly

Spark 340 has removed the AnsiCast by https://github.com/apache/spark/commit/5f0bae7af3c39919efd4bf68b1b6f467f0e1b20b, which will probably lead to much work in plugin.
So disable 340 for premerge and nightly now. But need to add it back when the issue #5688 is fixed.

build

build


extend wasm go sdk with OnHttpStreamDone

补充处理http请求时OnHttpStreamDone阶段的封装

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


basic Julia support

I don't think I have the bandwidth to work on this so I'm going to close; anyone else should feel free to reopen or complete.


tests: add mgr nodes to shrink_mon inventory

Since 306ce82 we explicitly fail when there's no mgr node preent in the
inventory.
fatal: [mon0]: FAILED! => {
    "changed": false
}

MSG:

Please add a mgr host to your inventory.

Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>

jenkins test centos-non_container-shrink_mon

jenkins test centos-container-shrink_mon


waffle.io Badge

Merge this to receive a badge indicating the number of issues in the ready column on your waffle.io board at https://waffle.io/rylnd/shpec
This was requested by a real person (user rylnd) on waffle.io, we're not trying to spam you.

Hah.

Lol.

Don't mind me, just clicking random buttons.


How to force sass-loader not to convert escaped string to utf-8

Question!
The issue doesn't related to webpack directly, but tied.
We have discussion on stackoverflow and according to this one when I use fonts as icons I have the following
.foo {
  &:before{
    content:"\e949"
  }
}

Which with webpack sass-loader converted into
.foo {
  &:before{
    content:""
  }
}

Generally speaking it's correct but sometimes it provides weird bug in Chrome: font isn't rendered at all.
To fix this I'd like to prevent such converting by sass-loader but I don't know how to do it. I've tried postcss-sass-unicode but somehow it doesn't work.
According to my config for webpack 5 looks like postcss is started before sass-loader. But if I swap it with sass-loader webpack can't build due to errors...

Any thoughts how it can be resolved ?

I found solution with css-unicode-loader


Documentation issue

The best way to start using inspectIT Ocelot is to attach the java agent when starting your Java program. Use the -javaagent command-line option to reference the inspectIT Ocelot jar:
$ java -javaagent:"/path/to/inspectit-ocelot-agent-0.1.M3.jar" -jar my-java-program.jar
I have attached the agent. now how agent will communicate with open census??

Hi @gsmba6,
you can find the current documentation for inspectIT Ocelot here:
http://docs.inspectit.rocks/releases/latest/
Today we will also launch our new website for inspectIT Ocelot under https://inspectit.rocks where you will find more information.
We also have a new Gitter channel if you have further questions:
https://gitter.im/inspectIT/Ocelot
Regards,
Alex

Hello @gsmba6
we use OpenCensus internally as a framework/library, so there is no standalone component which is used by the agent.
When you've attached the agent, by default it exposes a HTTP endpoint (port 8888) where all metrics are exposed in the Proemtheus format.
Using this endpoint, you can, for example:

use Prometheus for scraping the metrics and storing them in Prometheus itself
use Telegraf to scrape the metrics and write them into InfluxDB

We provide a containerized demo for both scenarios where you can find more information, e.g. how to set them up: http://docs.inspectit.rocks/releases/latest/#_inspectit_ocelot_demo


/health endpoint doing sync write

Hello,
We are in the process of updating our AppMetrics dependencies to 4.1.0 and it seems the HealthCheckEndpointMiddleware is still doing synchronous write on the /health endpoint (other endpoints work well). We already had trouble when migrating our app to ASP.NET Core 3.1 and ended up allowing synchronous writes at Kestrel level. This was a known issue that seems to have been fixed for 4.0.0 onward (according to https://github.com/AppMetrics/AppMetrics/issues/396) but I'm still facing the issue and cannot find anything on this topic (issues or doc).
Here's the end of the StackTrace :
System.InvalidOperationException
Synchronous operations are disallowed. Call WriteAsync or set AllowSynchronousIO to true.
   at Microsoft.AspNetCore.TestHost.ResponseBodyWriterStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.IO.StreamWriter.Dispose(Boolean disposing)
   at System.IO.StreamWriter.Close()
   at Newtonsoft.Json.JsonTextWriter.CloseBufferAndWriter()
   at Newtonsoft.Json.JsonTextWriter.Close()
   at Newtonsoft.Json.JsonWriter.Dispose(Boolean disposing)
   at Newtonsoft.Json.JsonWriter.System.IDisposable.Dispose()
   at App.Metrics.Health.Formatters.Json.HealthStatusJsonOutputFormatter.WriteAsync(Stream output, HealthStatus healthStatus, CancellationToken cancellationToken)
   at App.Metrics.AspNetCore.Health.Core.DefaultHealthResponseWriter.WriteAsync(HttpContext context, HealthStatus healthStatus, CancellationToken token)
   at App.Metrics.AspNetCore.Health.Endpoints.Middleware.HealthCheckEndpointMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.TestHost.HttpContextBuilder.<>c__DisplayClass23_0.<<SendAsync>g__RunRequestAsync|0>d.MoveNext()

(not that this is using the TestServer class but the same problem happens in a real environment).
and here's our configuration:
.UseHealthEndpoints()
.UseMetricsWebTracking()
.UseMetrics(options =>
{
    options.EndpointOptions = endpointsOptions =>
    {
        endpointsOptions.MetricsEndpointOutputFormatter = new MetricsPrometheusProtobufOutputFormatter();
        endpointsOptions.MetricsTextEndpointOutputFormatter = new MetricsPrometheusTextOutputFormatter();
    };
});

Is there anything on this topic ?
Thanks.

Did you figure this out? For me potential workaround would be not to use healthcheck middleware, then write your own middleware which extends healthcheck middleware.
Can you post how you end up doing this? I don't know this myself.

Did you figure this out? For me potential workaround would be not to use healthcheck middleware, then write your own middleware which extends healthcheck middleware.
Can you post how you end up doing this? I don't know this myself.

Currently we are setting AllowSynchronousIO to true in Kestrel server options, but we did so when migrating to .NET Core 3.1 about a year ago and we wanted to remove this workaround while upgrade AppMetrics packages. This is not a blocking issue as you can tweak the HostBuilder directly, but if it could be async all the way the better.

Health check functionality has been removed, MS have an equivalent implementation, no point App Metrics competing with that


[Bug]: open daily note after appending doesn't append text

Bug Description
if I type "od testing the text" then CMD-Enter, in order to "Open daily note afterwards", what gets added to the daily note is:
- 09:16 2022-05-18

But if I don't do "CMD-Enter" and instead just press enter, then switch to Obsidian manually, what's added is the proper text:
- 09:16 testing the text

Relevant Screenshot
No response
To Reproduce
No response
Debugging Log
[09:17:38.558] Logging Started...
[09:17:40.254] Shimmering Obsidian[Script Filter] Queuing argument '(null)'
[09:17:43.565] Shimmering Obsidian[Keyword] Processing complete
[09:17:43.567] Shimmering Obsidian[Keyword] Passing output 'testing the text' to Arg and Vars
[09:17:43.574] Shimmering Obsidian[Arg and Vars] Processing complete
[09:17:43.591] Shimmering Obsidian[Arg and Vars] Passing output '2022-05-18' to Arg and Vars
[09:17:43.592] Shimmering Obsidian[Arg and Vars] Processing complete
[09:17:43.592] Shimmering Obsidian[Arg and Vars] Passing output '2022-05-18' to Write Text File
[09:17:43.592] Shimmering Obsidian[Write Text File] Processing complete
[09:17:43.593] Shimmering Obsidian[Write Text File] Passing output '/Users/derekvan/Library/Mobile Documents/iCloud~md~obsidian/Documents/obsidian/dated/daily/2022-05-18.md' to Conditional
[09:17:43.593] Shimmering Obsidian[Conditional] Processing complete
[09:17:43.594] Shimmering Obsidian[Conditional] Passing output '/Users/derekvan/Library/Mobile Documents/iCloud~md~obsidian/Documents/obsidian/dated/daily/2022-05-18.md' to Open URL
[09:17:43.594] Shimmering Obsidian[Open URL] Processing complete
[09:17:43.595] Shimmering Obsidian[Open URL] Passing output 'obsidian:///Users/derekvan/Library/Mobile%20Documents/iCloud~md~obsidian/Documents/obsidian/dated/daily/2022-05-18.md' to Call External Trigger
[09:17:43.596] Shimmering Obsidian[External] Processing complete
[09:17:43.597] Shimmering Obsidian[External] Passing output 'obsidian:///Users/derekvan/Library/Mobile%20Documents/iCloud~md~obsidian/Documents/obsidian/dated/daily/2022-05-18.md' to Conditional
[09:17:43.597] Shimmering Obsidian[Conditional] Processing complete
[09:17:43.598] Shimmering Obsidian[Conditional] Passing output 'obsidian:///Users/derekvan/Library/Mobile%20Documents/iCloud~md~obsidian/Documents/obsidian/dated/daily/2022-05-18.md' to Run Script

Workflow Configuration

Version & System Information
-------------------------------
Metadata JSONs: 3/3
-------------------------------
INSTALLED VERSION
macOS: 12.3.1
Alfred: 4.6.5

Obsidian: 0.14.12
This Workflow: 2.22.7
Advanced URI Plugin: 1.21.1
Metadata Extractor: 1.0.1
-------------------------------
LATEST VERSION
Obsidian: 0.14.6 (Insider: 0.14.12)
This Workflow: 2.22.7
Advanced URI Plugin: 1.21.1
Metadata Extractor: 1.0.1
-------------------------------

Make sure you have done the following

[X] I have updated to the latest version of this workflow.
[X] I have read the Troubleshooting Documentation.
[X] If the o... main search does not work, I have tried rerunning osetup and it still does not work.

thanks! Sorry for the late response to this, especially since I do not use daily notes myself, I find it hard to maintain this feature. Incorporated in the latest release.

I think the fix introduced a bug unfortunately. When I try to append something to the daily note via "od" it appends it to a note called "{yyyy-mm-dd}" (literally--it doesn't populate the variables). I rolled back to 2.42.2 and instituted my fix above.


Added debug level logs

@trane my rebasing messed up this commit (showing 10 commits)

Current coverage is 92.65%

Merging #105 into master will decrease coverage by -0.43% as of 919d5a6

@@            master    #105   diff @@
======================================
  Files           39      39
  Stmts          752     790    +38
  Branches        37      37
  Methods          0       0
======================================
+ Hit            700     732    +32
  Partial          0       0
- Missed          52      58     +6

Review entire Coverage Diff as of 919d5a6

Powered by Codecov. Updated on successful CI builds.

this is a broken pull request


Decouple topics from tables and generalize SchemaRetriever

Intro
We have had a number of PRs and issues recently that are attempting to do two things:

Support more serialization formats
Support multiple schemas in the same topic

These include:
https://github.com/wepay/kafka-connect-bigquery/pull/238
https://github.com/wepay/kafka-connect-bigquery/issues/216
https://github.com/wepay/kafka-connect-bigquery/issues/175
https://github.com/wepay/kafka-connect-bigquery/issues/206
https://github.com/wepay/kafka-connect-bigquery/issues/178
And more.
Changes
I believe that we can address these issues with the following changes:
Add TableRouter

Adding a pluggable TableRouter that takes a SinkRecord and returns which table it should be written to. (Default: RegexTableRouter)

public interface TableRouter {
  void configure(Map<String, String> properties);
  TableId getTable(SinkRecord sinkRecord);
}

Generalize SchemaRetriever

Changing SchemaRetriever interface to have two methods: Schema getKeySchema(SinkRecord) and Schema getValueSchema(SinkRecord). (Default: IdentitySchemaRetriever, which just returns sinkRecord.keySchema() and sinkRecord.valueSchema())

public interface SchemaRetriever {
  void configure(Map<String, String> properties);
  Schema retrieveKeySchema(SinkRecord sinkRecord);
  Schema retrieveValueSchema(SinkRecord sinkRecord);
}

Change *QueryWriter schema update logic

Changing the way that schema updates are handled in the AdaptiveBigQueryWriter.

This change will be the largest. If we remove SchemaRetriever.updateSchema, we need a way for AdaptiveBigQueryWriter to update BQ schemas when a batch insert fails. Given these rules:
https://cloud.google.com/bigquery/docs/managing-table-schemas

This document describes how to modify the schema definitions for existing BigQuery tables. BigQuery natively supports the following schema modifications:

Adding columns to a schema definition
Relaxing a column's mode from REQUIRED to NULLABLE
It is valid to create a table without defining an initial schema and to add a schema definition to the table at a later time.

All other schema modifications are unsupported and require manual workarounds, including:

Changing a column's name
Changing a column's data type
Changing a column's mode (aside from relaxing REQUIRED columns to NULLABLE)
Deleting a column

The correct behavior is to do when a schema failure occurs is to have the adaptive writer union all fields from all insert batch with all fields in the existing BigQuery table. An example illustrates:
Existing BQ Schema

a					INTEGER				REQUIRED
b 					INTEGER				NULLABLE

Batch Insert Schemas

Row 1
a					INTEGER 			NULLABLE
Row 2
c					INTEGER				NULLABLE
Row 3
a					INTEGER				REQUIRED

Final Schema
a					INTEGER				NULLABLE
b 					INTEGER				NULLABLE
c					INTEGER				NULLABLE

This will require that we have access to the insert batch's the SinkRecord for each row (not just RowToInsert). It will also require that AdaptiveBigQueryWriter has the SchemaRetriever wired in as well.
I think the most straight-forward way to handle this is to have TableWriterBuilder.addRow(SinkRecord record) instead of RowToInsert. The Builder can then keep a SortedMap<SinkRecord, RowToInsert>, and pass that down the stack through to AdaptiveBigQueryWriter.performWriteRequest. AdaptiveBigQueryWriter.attemptSchemaUpdate can then be changed to implement the logic I field-union logic that I described above.
One area that we'll have to be particularly careful about is dealing with repeated records and nested structures. They need to be properly unioned as well.
Benefits
This approach should give us a ton of flexibility including:

It will allow you to pick which table to route each individual message based on all of the information in SinkRecord (topic, key schema, value schema, message payload, etc.)
It will allow us to fix some known schema-evolution bugs in cases where one field is added and another is dropped.
It will allow us to use SinkRecord's .keySchema and .valueSchema rather than talking to the schema registry for schemas.
It will make it easy to support JSON messages, even those that return null for the .keySchema() and .valueSchema() methods--you can implement a custom retriever for this case.

I'm really glad to read about pluggable TableRouter! This will address a lot of issues with API-implementation separation.
Is this still a draft or somebody is already working on it?
I'm going to rebase #238 as soon as the new interface arrives :)

@mkubala no one is working on this at the moment. Our hope was that you would introduce the TableRouter as part of your PR.

@criccomini Do you have any update on this issue ? Is someone working on it ?
In our side, we need multi schemas support (#238) and we will glad to help on it

@criccomini Do you have any update on this issue ? Is someone working on it ?
In our side, we need multi schemas support (#238) and we will glad to help on it

@bingqinzhou @mtagle Do you have any information ?

@sebco59 we have someone beginning this now! :)

@criccomini Nice !
On our side we tried to use Simple Message Transformation to deal with MultiSchema instead of Table Router implementation.
But SMT doesn't work because of the way to retrieve schema on SchemaRegistrySchemaRetriever#getSubject. If we change it, it will open the door for all SMT and no need to implement TableRouter

With SMT, we could extract a lot of complexity from connector to outside

we want to deal with multi subject -> SMT to change topic name in the fly
we want to add kafka system information (offset, partition, ...p) -> SMT to add field with this value on the fly
we want to route topic in a specific bq table depending on a field -> SMT to change topic name with a regex
we want to add header of the record to bq record -> SMT to add field... and so more

With SMT, we have default error handling from kafka connect.
With SMT, we could reuse it in another connector

We have started developing schema retriever logic but we tried to decouple it from the schema update logic. With the current implementation, the BQ table schema updates are entirely based on the latest version available in the schema registry, which doesn't do well with messages with an older incompatible schema.
With the schema retriever, it's still straightforward to handle homogenous batches (as far as the schema is concerned), you can simply use any message from the batch to try to update the BQ table schema.
To handle heterogenous batches, we could rely on a retry logic that will incrementally update the BQ table schema until it gets stable (you can use the first failed message in the batch to try to update the BQ table schema).
That would be a simple alternative before the field-union logic is implemented.
What do you think of this approach (SMT and Schema Update Logic) ?
Can we contribute too ?

@criccomini This seems like a great abstraction to place over the connector and allow it to service a variety of use cases. Excited to see this thing still growing and evolving as the years go by :)
I think @sebco59's suggestion to rely on SMTs is a valuable one. A lot of the problems that are being addressed here aren't specific to BigQuery as an external system and can apply to connectors in general. An SMT is a great way to write code once and reuse it anywhere, and also should help keep the code base for this connector uncluttered. Specifically, I think users should either use the RegexRouter SMT or implement their own instead of the suggested TableRouter interface. Being able to modify the topic of a SinkRecord via an SMT should be enough to give arbitrary control over which table it ends up being routed to.
With regards to the comment about modifying SchemaRegistrySchemaRetriever#getSubject to be able to handle topics with heterogeneous schemas, I think there's some good news and some bad news. Good news: there's already a pluggable interface with a few out-of-the-box implementations to handle this use case, the subject name strategy interface. We could allow users of the SchemaRegistrySchemaRetriever to specify a subject.name.strategy to use, which could default to the TopicNameStrategy (which mirrors the current behavior of the retriever). Bad news: this doesn't address the possibility of heterogenous topics for any other SchemaRetriever implementation. Because of this, I think we should still expand the API to rely on a SinkRecord (and possibly also a TableId, just to best preserve existing behavior), although it'd probably also be nice to add support for user-specified subject name strategies to the SchemaRegistrySchemaRetriever.
I also think that if we evolve the SchemaRetriever API, we should be careful to add default implementations for the new methods so that SchemaRetriever instances developed against the current API will still work normally against newer versions of the connector.
On the subject of automatic schema unionization, I'm wondering about a potential gotcha: if the connector reads a record with a completely mismatched schema that was not meant to be in the topic to begin with, will automatic unionization of the table still happen? I think it will as long as any fields present in that record's schema which aren't already in the table are optional. We probably want to be cautious about accidentally adding columns to a table schema, since deleting them isn't permitted

(We are using SMT approach now. PR is forthcoming :) )


ZS-68 ~ Microgrids profiles

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 EmptyResponseDto.java#L12: Add a private constructor to hide the implicit public one.

All is well.

SonarQube analysis reported 1 issue

 1 major

Watch the comments in this conversation to review them.

All is well.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 EmptyResponseDto.java#L12: Add a private constructor to hide the implicit public one.

All is well.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 EmptyResponseDto.java#L12: Add a private constructor to hide the implicit public one.

All is well.


Make it possible to add the RTD versions menu to the left navigation

Sphinx-book-theme displays the RTD versions on the left navigation menu rather than standalone/floating on the right:

done  in https://github.com/pydata/pydata-sphinx-theme/pull/1005


CA-43 Initial networking tests

Adds the folder test containing Terratest Golang code.
Adds the folder test_examples for having testable TF root modules.
Uses Terratest to assure the module gives out the outputs needed.

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Log all peer dependency warnings from yarn and npm

Nice! Want me to find some test files and get that set up?

@greysteil haven't added the tests yet, sorting some stuff out with a friend so will do tomorrow.
Found found this interesting case:
{
    "name": "test",
    "version": "1.0.0",
    "private": true,
    "dependencies": {
        "apollo-client": "^0.8.0",
        "react": "^15.0.0",
        "react-dom": "^15.0.0",
        "react-apollo": "^0.9.0"
    }
}

If you update react to 16 you get two peer dep warnings:
" ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>" ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 15.* || ^15.0.0"

But then if you update react-dom and react-apollo to the latest you also need to update apollo-client to ^2.3.8 and install graphql.. 🤠
If you go even further back with react-apollo it also has a peer dep on redux... 🤯

@greysteil go for it if you're looking at this otherwise I'll sort it out tomorrow!

@feelepxyz nice one!
I've added a couple of tests but they're currently failing. If you print the error output for both of them you'll see that only one peer dependency warning (the react-apollo one) is coming through. The react-dom one is getting missed for both Yarn and npm.

Also of note: peer dependencies do apply to sub-dependencies. Let's not worry about them for now(!).

@greysteil think this works as expected now, spent ages looking for packages (with few deps) that could be installed with a range that wouldn't give you lax peer dependency requirements. Most packages will relax their peer dependency requirements to allow new React major versions in a patch/minor release!

Nice!


Bug: Clicking on the Logo Redirects to Footer Instead of Homepage

What happened?
When navigating through the website's documentation section and then scrolling down to the footer, clicking on the logo redirects the user to the homepage as intended. However, instead of displaying the top of the homepage, the footer is shown. This behavior is causing confusion and inconvenience to users. The issue needs to be resolved to ensure a seamless and consistent user experience.
Add screenshots
https://github.com/priyankarpal/ProjectsHut/assets/103263909/85cf3940-ac93-42ed-bd6a-33f7571c4ea3
What browsers are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[ ] I want to work on this issue

thank you for creating this issue. we will add soon.

also, if you want to fix this issue you can.
How to solve this issue?

go to src/pages/HomePage.jsx
add the code top the line

https://github.com/priyankarpal/ProjectsHut/blob/5f18ea828f85e4fcff134eff8fad5517522de6eb/src/pages/HomePage.jsx#L11
Sample code
window.scrollTo(0, 0);

assign it to me, I will do it.

assign it to me, I will do it.

assigned to you


SLSA compliant charts

https://github.com/rancher/charts/wiki/7-‐-SLSA-compliant-charts

does not apply


Parse commandline args as separate songs for playlist

This changes the argument handling to allow for 1+ grouped search terms and handling stdin (pipes not tty) the same as arguments to allow piping in a "playlist" set of search terms and/or song urls.
  cloudruby [--config-args] [(search terms|track urls)]

  # Examples

  cloudruby          # query the latest 100 tracks from soundcloud
  cloudruby $search  # query the latest 100 tracks that match the $search keywords

  ## play a soundcloud url directly
  cloudruby http://soundcloud.com/crassmix/feint-clockwork-hearts-crass

  ## create a playlist from arguments (urls and/or grouped search keywords)
  cloudruby --no-shuffle=true https://soundcloud.com/adapt77/auto-ok-ecophal manicanparty heart "sellorekt thunderbolt" https://soundcloud.com/wearesoundspace/premiere-malbetrieb-ghetto "elektroschneider lenny"
  > search terms are grouped when quoted or adjacent to urls or quoted strings

  ## create a playlist from a pipe
  > stdin is also parsed as arguments if piped into the process
  cloudruby --no-shuffle=true < local-playlist-filename
  printf "sellorekt iris\nmanicanparty eyes" | cloudruby

The curses ui is not displayed until the searches are complete and the playlist is generated. So, it appears to stall until the searches are compelte. It may be nice to print out the search terms while they are being processed/searched. Or we could change the ui to list a curses window or something showing the status/progress of searches.


⚠ Bofrost.de has degraded performance

In ad89334, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1062 ms

Resolved: Bofrost.de performance has improved in f55ef97.


Github enterprise support

Thanks for this project!
Is your feature request related to a problem? Please describe.
I'd like to use the github-api related features (e.g. note about first contributions) with github enterprise.
Describe the solution you'd like
All github related variables should not be hardcoded like https://github.com/orhun/git-cliff/blob/main/git-cliff-core/src/github.rs#L37 but overwritable via environment variables or config.
Describe alternatives you've considered

Not using github-related features for now.
changing the variable and compiling locally

Additional context
Version: git-cliff 2.0.2
Neither running it with GITHUB_API_URL=https://costomdomain.tld/api/v3/, nor changing the domain in the macro https://github.com/orhun/git-cliff/blob/main/examples/github-keepachangelog.toml#L17 does help.
 DEBUG git_cliff_core::github    > Sending request to: https://api.github.com/repos/org/testrepo/pulls?per_page=100&page=5&state=closed
 DEBUG reqwest::connect          > starting new connection: https://api.github.com/

Compiling with changed API_URL does work.

Hey, thanks for reporting! This is now implemented in #512


task event terminated -> end

will wait to test the build before merging

moved the change to the other pr


Add OPEN_SCREEN action and saga

Please verify the following:

[x] Everything works on iOS/Android
[x] ignite-base ava tests pass
[x] fireDrill.sh passed

Describe your PR
This adds an action ('OPEN_SCREEN') & saga to enable users to dispatch a command to open any screen.
For Reactotron users, when generating a new app via Ignite, users can retain the useful screens generated by ignite-base, such as 'componentExamples', even if their new app bypasses any Ignite-generated screens on startup, simply by dispatching to Reactotron, like this:
{type: 'OPEN_SCREEN', screen: 'componentExamples'}
In addition, 'OPEN_SCREEN' is helpful while developing screens for an app that have not been set up with any nav links in the app. The developer can work on the new screen and test it via a direct dispatch from Reactotron.
The saga sets the react-native-router-flux option param to type: ActionConst.RESET by default, but users can easily override this by passing in different options. The unit test for the saga demonstrates this.

LGTM! 👍


Unfocused chat is very transparent in multiplayer

I reported this on minecraftforums but not sure if it got acknowledged.

Version: 2.3.0-beta-296-mc1.12 (can't test 1.12.1 because it crashes)
In multiplayer, when not having chat open, the background is very transparent, but when opening chat the background is more opaque

This is a bug because it does not happen in singleplayer. I like this though as a feature, is it possible to make it so when chat is not opened, the background is 100% transparent?

It seems to work fine for me. Can you test in 1.12.1 using the new version I just now uploaded?
(The crash was a problem with the build script and reobfuscation)

Yeah I just tested it on a server and it doesn't seem to be an issue in 1.12.1. Would it be possible for this to be a feature though, like a separate image file for unfocused chat, so you can make that more transparent?


Concerns about the maintenance status

I've noticed that there haven't been any dependency updates for quite some time, and it seems that pull requests (PRs) aren't being pushed either.
Do you have any plans to continue maintaining it, or should we consider it as abandoned?

It is not abandoned, we still use this internally in production.
We have not been doing a lot of active development on the project recently, but we still have been merging security updates (e.g. this one last month). The feature set is pretty stable for our current usage and so has not needed a lot of attention.


Move ParserErrorSink, RazorError and SourceLocation to a better namespace

These files are used somewhat regularly and are no longer only used during the parsing phase.
Associated convo: https://github.com/aspnet/Razor/pull/316#discussion_r26010720

fixed in

3f7c75e
aspnet/Mvc@cef32d4
aspnet/RazorTooling@16b4c64


Remove version: DeepL.DeepL version <IP_ADDRESS>40

New version released, this package/manifest uses a vanity URL and the hash no longer matches
Microsoft Reviewers: Open in CodeFlow

URL: https://appdownload.deepl.com/windows/0install/DeepLSetup.exe
Status Code: 200
(Automated message - build 726)


Add more groups to api documentation - toolbox

In api documentation - toolbox are many different api endpoints in the same heading. please add groups and a short caption to each group:

Toolbox / Postprocessing Filter
Toolbox / XSLT Converter
Toolbox / NIF-Converter

This is implemented. Can I close the issue?

Finished. Thank you!


Allow SVG files as swatches?

Yes. I ready your previous comments and I understand you have little to no time to offer support for this extension.
We just need to be able to display SVG images. Currently /app/code/community/Easylife/Switcher/Helper/Optimage.php throws exception: Unsupported image format
You can see this at http://www.lemps.mx/bikinis/sofia-polka.html
Would you be willing to help us?
We are willing to pay for you time.
Thanks
Ignacio

Forget about this..


Chrome extension does not show data on Windows 10

Expected, serial write "hello" shows "hello" in the editor
(could be misunderstood)
No joy.
Note that it has been possible to obtain serial contact with micro:bit with a program

Known bug. Chrome extensions needs to be updated.

The Chrome extension has been deprecated. Closing bug.


CT-2103: Implement data_type_code_to_name for redshift

resolves #319
Description
Implements RedshiftConnectionManager.data_type_code_to_name() in order to support contract validation.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

Looks like this requires a type update:
dbt/adapters/redshift/connections.py:285: error: Argument 1 of "data_type_code_to_name" is incompatible with supertype "SQLConnectionManager"; supertype defines the argument type as "Union[int, str]"  [override]

@colin-rogers-dbt I've fixed it up. It appears the mypy check in CI is more thorough than the local check.


Create a Reference Topic

Create a top-level table of contents (TOC) heading and reorganize the documentation so that this section contains all reference pages.
Elsewhere in the documentation where the user needs reference information (for example, to choose a specific configuration value or to check the syntax of a command), link to the appropriate reference page.
This issue tracks recommended changes resulting from an analysis of the KEDA documentation commissioned by CNCF. The analysis and supporting documents are here: https://github.com/cncf/techdocs/tree/main/assessments/0011-keda/
Use-Case
Some typical types of reference pages include:

API specifications
CLI specifications
Configuration options

Specifically for KEDA:

The Reference section should be at or near the end of the ToC
Include the following information in the Reference section:

Move the FAQ to the Reference section.
Add a glossary to the Reference section.

Specification
Here is a proposed outline. Links are to existing pages that can be used as-is or provide a starting point.

Reference

Authentication Providers

AWS (IRSA) Pod Identity Webhook
...
Secret

Scaled Object specification (from "Concepts"; https://keda.sh/docs/2.13/concepts/scaling-deployments/#scaledobject-spec)
ScaledJob specification (https://keda.sh/docs/2.13/concepts/scaling-jobs/#scaledjob-spec)
Events
Firewall requirements
...
FAQ
Glossary

This is actively being worked on in https://github.com/kedacore/keda-docs/pull/1389


Feature/tv display

Pull Request Description:

Added a new TV display page to show queue information, using WebSocket to update the display in real-time.
Updated the home page: changed "Top 3 Queues" to "Popular Queues" and implemented a carousel for better display of the queues.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 32.00000% with 17 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

manager/views/queue_views.py
23.52%
13 Missing :warning:

manager/views/participant_views.py
20.00%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Flag
Coverage Δ

unittests
75.60% <32.00%> (-0.23%)
:arrow_down:

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

Files with missing lines
Coverage Δ

manager/models/queue.py
84.12% <100.00%> (ø)

manager/urls.py
100.00% <ø> (ø)

manager/utils/category_handler.py
62.55% <ø> (-0.09%)
:arrow_down:

participant/tests/views/test_homepage.py
100.00% <100.00%> (ø)

participant/views/home_views.py
66.66% <ø> (ø)

manager/views/participant_views.py
40.12% <20.00%> (+0.43%)
:arrow_up:

manager/views/queue_views.py
45.83% <23.52%> (-2.47%)
:arrow_down:

This is a great, adding a TV display page and improves the homepage with a "Popular Queues" carousel. The WebSocket implementation for real-time updates is a fantastic addition!

Wow a tv display is very useful and relatable, good work my G.


Export groups to file

Often after an intense research session (imagine dozens of tabs), I like to save these to a file somewhere in my Dropbox I can retrieve later if needed. No need to be able to import these back, I just don't want to pollute my bookmarks or bog down TT with stuff I don't immediately need or might never need later.
Not a crucial must have, just wrapping my daily workflow around this tool but at the same time I think it's also beneficial to have grouped selective export as well instead of dumping the whole tree.

Other side note, 2.22 - 3 would be pretty stable and feature filled enough to do another round on hn, rdt.

@iKlsR
Nice, yeah. I was thinking about doing another push as well. Though I first wanted to redesign the logo and other chrome store assets.

I second for Export too but having also an Import for future use or baqck-up purpose would be really useful.
Thanks for this addon :octocat:

@mikhoul have you tried the import/export we have currently?

Thanks 👍

@briangonzalez @mikhoul does the response above mean this issue can be resolved?

I think so :)


Replacement of NewtonSoft.JSON by System.Text.Json

Description
Replacement of NewtonSoft.JSON by System.Text.Json, assuming it´s a brand new implementation of JSON parsing and serialization with better benchmarks
Motivation and Context
It´ll reduce a exogenous dependency and improve performance since from .net core 3.1 onward it will use new Span<> faster structures.
This is addressing the issue #58, myself opened it.
Testing
The test which evaluate indirectly this feature is working.
Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

It´s not exactly a breaking change, but since it changes the dependency list, it cares some attention to publish.
Checklist

[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have read the README document
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

I have created PR #103  that consolidates this open PRs along with this change. Because of the breaking changes across the PRs including this one I am planning on a major version bump to 4.
I'm going to close this PR and track the work in #103. Please feel free to review that PR for the changes I made from this PR.


New version: Levminer.Authme version 5.1.1

Pull request has been created with WinGet Updater :rocket:
Microsoft Reviewers: Open in CodeFlow

@wingetbot run