Career page - Fix EE indentation

Fix Electrical Engineering section indentation
I think the problem should be from the electrical_engineer.md file (thought i'd already fixed this in the previous PR)

https://github.com/nathakits/pupil-labs-website/commit/423a1f9ff24b55474973d51dc57d20ad029af522
The PR is already merged but don't know why it's not working.

Doesn't work in both desktop and mobile - only my localhost works...

https://github.com/pupil-labs/pupil-labs-website/pull/93 - made a new PR to fix this issue

It is a nested list. The indentation is intentional -- it was reverted from your previous PR. Please look through commit messages.


[Bug Report] Sub tabs does'nt work fine in a tab

Element UI version
1.4.7
OS/Browsers version
Ubuntu
Vue version
2.4.2
Reproduction Link
https://jsfiddle.net/garlacour/6nemn8aa/
Steps to reproduce
I do a simple tabs, in the first tab i put 2 others tabs
What is Expected?
the first sub tab have to be set to active
What is actually happening?
active don't work fine when i use sub tabs. The CSS style is not set correctly I dont know why ... :/ Thanks for any help

There is no toto in data: https://jsfiddle.net/6nemn8aa/1/

Thx


My first submission

Language: R
Method: Custom
Submission stored in jpoirier/jpoirier009_submission001.csv corresponds to notebook jpoirier009_submission001.ipynb
Note: cross-validation function took me 16 hours to run. Rest of notebook should be able to run without running CV in a few minutes (incl predictions)

Hi Josh, thanks for the submission – nice to see you here. The CSV file scores 0.469, so something to build on.
I'm afraid I'm a bit thick when it comes to R; I usually double-check that people are using the right data. Some people accidentally do the prediction with the model still only trained on the subset they used cross-validation – you might want to check you haven't done that.
Either way, I hope you get a chance to work on it some more. Cheers! M


[DO-NOT-MERGE] operator: add external OIDC CA as a revision configmap

DO-NOT-MERGE: Currently, this PR facilitates testing for the development of the configuration of an external OIDC provider.
This PR adds a revision ConfigMap to the KAS-o in order to mount the (optional) OIDC CA as a file to the KAS pods.

/hold

For the moment this is used for testing purposes only; closing.
/close


Implement madvise() support

Closes #40
Allows users to notify OS how it intends to use the memory map.
Calling advise() func on non-unix is a noop, and will return an error.

It seems like most of the advices are not POSIX/UNIX one but Linux-specific, like MADV_REMOVE. We should either stick with POSIX one or handle Linux explicitly.

What do you want to do about https://github.com/RazrFalcon/memmap2-rs/runs/5136790624?check_suite_focus=true ?  1.36 is a bit dated
error[E0658]: non exhaustive is an experimental feature
  --> src/advice.rs:11:1
   |
11 | #[non_exhaustive]
   | ^^^^^^^^^^^^^^^^^
   |
   = note: for more information, see https://github.com/rust-lang/rust/issues/44109

As a general comment: I am not sure whether using an enum for the flags is the best approach as these flags do not seem to be exclusive, e.g. it might make sense to request both MADV_SEQUENTIAL and MADV_HUGEPAGE in a single call. So something like bitflags would seem more appropriate even though I am not sure whether this is worth a dependency or should better be built by hand.
I also think this would benefit from squashing the commits before merging.

@adamreichold these are not bit flags
pub const MADV_NORMAL: ::c_int = 0;
pub const MADV_RANDOM: ::c_int = 1;
pub const MADV_SEQUENTIAL: ::c_int = 2;
pub const MADV_WILLNEED: ::c_int = 3;
pub const MADV_DONTNEED: ::c_int = 4;
pub const MADV_FREE: ::c_int = 8;
pub const MADV_REMOVE: ::c_int = 9;
pub const MADV_DONTFORK: ::c_int = 10;
pub const MADV_DOFORK: ::c_int = 11;
pub const MADV_MERGEABLE: ::c_int = 12;
pub const MADV_UNMERGEABLE: ::c_int = 13;
pub const MADV_HUGEPAGE: ::c_int = 14;
pub const MADV_NOHUGEPAGE: ::c_int = 15;
pub const MADV_DONTDUMP: ::c_int = 16;
pub const MADV_DODUMP: ::c_int = 17;
pub const MADV_HWPOISON: ::c_int = 100;

Agree about squashing, but this is something that github does automatically when repo owner merges (merge button has a drop down). You usually don't want to do that before merge to keep all comments properly positioned. In all my repos I disable all other merge methods except for squash.

Yes, I will squash it automatically. Don't worry about it.
As for the enum vs bitflags, it does seems like this is an enum.

Indeed, sorry for the noise. It seems that while the semantics are not exclusive, the interface is, e.g. combining MADV_SEQUENTIAL and MADV_HUGEPAGES does require two separate calls to madvise.  This seems to be a left-over from the original/common advices being exclusive.

@nyurik Thanks for your effort and patience. The update is live now.

And thank you!! :)


Privacy budget discussion

Discussing privacy budge without mathematical equation and explanation is not helpful.
[Enter feedback here]

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

ID: dcd5ca1e-52c2-ee35-6d94-4dc700b0a3aa
Version Independent ID: a6460757-b438-9d89-c0fc-0159b51140f5
Content: Differential privacy in machine learning (preview) - Azure Machine Learning
Content Source: articles/machine-learning/concept-differential-privacy.md
Service: machine-learning
Sub-service: enterprise-readiness
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

@yilanz  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

We have retired this doc. Thank you!
#please-close


[1306][Compare text and select params] PoC for giving specific error messages for partial autocompletes

Context
The goal here is handling the case where a user types something into an
autocomplete field but doesn’t select anything from the resulting
dropdown. Existing behaviour will either ignore the user’s input and
keep the field filled with the previous value, or just blank it out,
which can be confusing.
We want to retain what the user entered into the text field when
re-rendering the page with errors, and provide a specific error message
for that field being partially submitted.
This PR is a spike that makes this change on one page - course details.
Changes proposed in this pull request
This approach submits the text field as well as the select and compares
the two values - if they are different then the user has not selected
something from the autocomplete dropdown. This would need to be modified
if the values for the select are different from the display
Guidance to review
Please ignore the failing tests and rubocop errors as this is just a spike 😄
and enjoy this gif demonstrating it working
Feel free to pull this PR down and run it locally and have a play around with the course details
edit page

 [SPIKE] [1day] Improve handling of freetext responses to autocompletes that require a fixed answer


Use binutils-gdb from tricore-gcc-toolchain 11.3 repository as base

https://github.com/EEESlab/tricore-gcc-toolchain-11.3.0
This is a complete free and open source implementation of tricore-elf-gcc based on GCC 11.3. The compiler works good and supports many architecture version and devices.
Check if it is possible to use this version of tricore-binutils-gdb as base for gdb, or directly include a working gdb inside the toolchain

Work in progress in other repository: https://github.com/NoMore201/tricore-binutils-gdb/tree/feature/gdb-support

Impressive work! I did a quick test with your implementation using mainline QEMU, I get the following error:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/iezzid1/Workspace/aurix-cmake-code-sample/test.elf...
(gdb) set architecture
TriCore:V1.1    TriCore:V1.3    TriCore:V1_6    TriCore:V1_6_2  auto
TriCore:V1.2    TriCore:V1.3.1  TriCore:V1_6_1  TriCore:V1_8
(gdb) set architecture TriCore:V1_6_1
The target architecture is set to "TriCore:V1_6_1".
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
Remote 'g' packet reply is too long (expected 140 bytes, got 176 bytes):<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000800b00002000008000000000000000000000000000000000000000000000000000000000

Launched QEMU with the following command:
./qemu-system-tricore -M KIT_AURIX_TC277_TRB -kernel ../../aurix-cmake-code-sample/test.elf -s -S -display none

If you agree, I would like to use your implementation and contribute to it. I would also like to check if issue #5 is solved with your implementation.
On a side note, how does openocd work? Do I just need a USB JTAG adapter and run the openocd server? Do I need a DAP based debugger for AURIX?

About the issue I'm facing, I think this is caused by the fact that QEMU expects more than 35 registers from the gdb, and their index may be different from the enum you implemented:
https://github.com/qemu/qemu/blob/7872e5fdf38ac0d8d0083aabb98d67da1f530ef4/target/tricore/gdbstub.c#L108-L120
I think the total number of system register should be 43 as implemented in the patch here:
https://github.com/NoMore201/tricore-gdb/blob/e5df2263a28486c584dc090bd1cc1b5faa739a72/tricore-gdb/0006-Rebase-tricore-implementation-from-10.0.50-to-11.2.patch#L14598-L14645

Openocd uses the TAS Server from Infineon and the TAS server handles the on board debugger or miniwiggler. It supports every development board from IFX. Openocd handles the flashing, reset and breakpoint/steping interaction and has a gdbserver integrated (like QEMU).
I can add those registers to gdb, I did not need them yet.  I need to update openocd and gdb together.

Cool, I'll later check openocd with miniwiggler, would be great to directly flash/debug source code from IDE without having to use expensive (and usually buggy) debuggers.
I did some further testing of your GDB after adding the missing registers, it seems to work fine but problem #5 is still there. I'll try to work on an implementation of stack frame unwinding using CSAs.

Yes, that true with the stack frames. It always uses the dwarf frames which do not work properly. This needs to be investigated a bit deeper.  The code for the unwinding itself is not to difficult but the problem is how to get gdb to use the unwinding function and not the dwarf info.

I found the source file in quemu. Strange ordering, I was sorting them by address...
https://gitlab.com/qemu-project/qemu/-/blob/master/target/tricore/gdbstub.c

I fixed the register you mentione.d


Support nif 2.9 in OTP 18.2

Add enif_getenv() function to support nif 2.9. enif_getenv() was introduced to  Erlang/OTP 18.2 by this commit: https://github.com/erlang/otp/commit/ef45d2c9f874354b17c2aca96de7b3306a9eb943
Manually tested with a modified version of ruster_unsafe_demo: https://github.com/tatsuya6502/ruster_unsafe_demo/commit/839db584e147459f714e5658d62e8a580c382bf2
% git remote -v
origin	git@github.com:tatsuya6502/ruster_unsafe_demo.git (fetch)
origin	git@github.com:tatsuya6502/ruster_unsafe_demo.git (push)
% git branch
  master
* nif-2.9
% cargo build
    Updating git repository `https://github.com/tatsuya6502/ruster_unsafe/`
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling ruster_unsafe v0.2.0 (https://github.com/tatsuya6502/ruster_unsafe/?rev=nif-2.9#2f68285f)
   Compiling libc v0.2.4
   Compiling ruster_unsafe_demo v0.0.1 (file:///usr/home/tatsuya/workhub/dev/ruster_unsafe_demo)
% erlc ruster_unsafe_demo.erl
%

% erl
Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]

Eshell V7.2.1  (abort with ^G)
1> ruster_unsafe_demo:getenv("HOME").
"/home/tatsuya"
2> ruster_unsafe_demo:getenv("UNDEFINED").
** exception error: bad argument
     in function  ruster_unsafe_demo:getenv/1
        called as ruster_unsafe_demo:getenv("UNDEFINED")
3> os:getenv("HOME").
"/home/tatsuya"
4> os:getenv("UNDEFINED").
false

Thanks!

Is there any particular reason why this wasn't merged?

I could have sworn I merged this.  Apologies.  Thanks for poking me.

Ah, it makes you hit merge twice as confirmation.  I must have only hit it once the first time.

Ah, right, thank you :)

Would you mind bumping the version number and uploading the newest version to crates? I can make a pull request if it's easier for you.

Crate 0.3.0 has been published.


Unable to submit to review because of release notes.

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
When I want to submit my application for review I get the error message that I hadn't specified release notes in needed language. But I do specify it in the Deliverfile.
Command used:
deliver \
  --skip_binary_upload \
  --skip_screenshots \
  --skip_metadata \
  --submit_for_review

Complete output when running fastlane, including the stack trace and command used
[02:18:05]: Login to iTunes Connect<EMAIL_ADDRESS>[02:18:10]: Login successful

+--------------------------------------------------------------------+-----------------------------+
|                                      deliver 1.10.3 Summary                                      |
+--------------------------------------------------------------------+-----------------------------+
| skip_binary_upload                                                 | true                        |
| skip_screenshots                                                   | true                        |
| skip_metadata                                                      | true                        |
| submit_for_review                                                  | true                        |
| force                                                              | true                        |
| price_tier                                                         | 0                           |
| app_rating_config_path                                             | itunes_rating_config.json   |
| submission_information.add_id_info_uses_idfa                       | false                       |
| submission_information.content_rights_contains_third_party_content | false                       |
| submission_information.content_rights_has_rights                   | false                       |
| submission_information.export_compliance_encryption_updated        | false                       |
| release_notes.en-US                                                | new                         |
| username                                                           |<EMAIL_ADDRESS>          |
| app_identifier                                                     | com.company.app             |
| app_version                                                        | NEW_VERSION                 |
| ipa                                                                | app.ipa				       |
| automatic_release                                                  | false                       |
| screenshots_path                                                   | ./screenshots               |
| metadata_path                                                      | ./metadata                  |
+--------------------------------------------------------------------+-----------------------------+

[02:18:11]: Making sure the latest version on iTunes Connect matches 'NEW_VERSION' from the ipa file...
[02:18:13]: 'NEW_VERSION' is the latest version on iTunes Connect
[02:18:14]: Price Tier unchanged (tier 0)
[02:18:16]: Finished the upload to iTunes Connect
[02:18:18]: Selecting the latest build...
[02:18:22]: Selecting build 1.0.83 (2342)...
[02:18:23]: Successfully selected build
[02:18:23]: Submitting the app for review...
/usr/local/lib/ruby/gems/2.2.0/gems/spaceship-0.23.0/lib/spaceship/tunes/tunes_client.rb:219:in `handle_itc_response': [!] You must detail what's new in this version in English. (Spaceship::TunesClient::ITunesConnectError)
	from /usr/local/lib/ruby/gems/2.2.0/gems/spaceship-0.23.0/lib/spaceship/tunes/tunes_client.rb:708:in `prepare_app_submissions'
	from /usr/local/lib/ruby/gems/2.2.0/gems/spaceship-0.23.0/lib/spaceship/tunes/app_submission.rb:117:in `create'
	from /usr/local/lib/ruby/gems/2.2.0/gems/spaceship-0.23.0/lib/spaceship/tunes/application.rb:269:in `create_submission'
	from /usr/local/lib/ruby/gems/2.2.0/gems/deliver-1.10.3/lib/deliver/submit_for_review.rb:8:in `submit!'
	from /usr/local/lib/ruby/gems/2.2.0/gems/deliver-1.10.3/lib/deliver/runner.rb:87:in `submit_for_review'
	from /usr/local/lib/ruby/gems/2.2.0/gems/deliver-1.10.3/lib/deliver/runner.rb:30:in `run'
	from /usr/local/lib/ruby/gems/2.2.0/gems/deliver-1.10.3/lib/deliver/commands_generator.rb:49:in `block (2 levels) in run'
	from /usr/local/lib/ruby/gems/2.2.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /usr/local/lib/ruby/gems/2.2.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /usr/local/lib/ruby/gems/2.2.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
	from /usr/local/lib/ruby/gems/2.2.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
	from /usr/local/lib/ruby/gems/2.2.0/gems/fastlane_core-0.37.0/lib/fastlane_core/ui/fastlane_runner.rb:23:in `run!'
	from /usr/local/lib/ruby/gems/2.2.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
	from /usr/local/lib/ruby/gems/2.2.0/gems/deliver-1.10.3/lib/deliver/commands_generator.rb:132:in `run'
	from /usr/local/lib/ruby/gems/2.2.0/gems/deliver-1.10.3/lib/deliver/commands_generator.rb:12:in `start'
	from /usr/local/lib/ruby/gems/2.2.0/gems/deliver-1.10.3/bin/deliver:5:in `<top (required)>'
	from /usr/local/bin/deliver:23:in `load'
	from /usr/local/bin/deliver:23:in `<main>'

Configuration Files
This is the Deliverfile:
force true
price_tier 0
app_rating_config_path "itunes_rating_config.json"
submission_information({
	add_id_info_uses_idfa: false,
	content_rights_contains_third_party_content: false,
	content_rights_has_rights: false,
	export_compliance_encryption_updated: false
})
release_notes({"en-US" => "new"})
username<EMAIL_ADDRESS>app_identifier "com.company.app"
app_version "NEW_VERSION"
ipa "app.ipa"
automatic_release false

I have no other configuration files.
Environment
➜  deliver --version
deliver 1.10.3
➜  fastlane --version
fastlane 1.66.0
Do you use bundler, rbenv or rvm? No.

What happens if you remove the skip_metadata flag?

Oh. I didn't think of release notes as metadata. Thanks, the issue's resolved.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain zyapps.com has exceeded the max emails per hour (422/400 (105%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from github-smtp2-ext8.iad.github.net ([<IP_ADDRESS>]:56519 helo=github-smtp2a-ext-cp1-prd.iad.github.net)
by serveur.ex2-p10.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.86_1)
(envelope-from<EMAIL_ADDRESS>id 1afmMl-000ale-VA
for<EMAIL_ADDRESS>Tue, 15 Mar 2016 11:38:28 +0100
Date: Mon, 14 Mar 2016 15:51:24 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1457995884;
bh=LkUyM6Qaovd1u+fLxPx0DR74MEkv5Ph+CTDCw8g8/y8=;
h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=SnV6dW0MP+f8o5U29UeWP+2+M4j8bTWSCIfXQP2O1Z/xvZ5E13nO8klO4P2AIJhQb
TG8LiQl7vzWAnHeXgFr2GB9lS6K7IdJC1hPedxMql7Fmu8G88V1J7dM2oBwNVMq2PY
/O2wV0g2D2XjbFK9mawKqgXBl8oifaRx2HPcc6Qc=
From: Val Polouchkine<EMAIL_ADDRESS>Reply-To: fastlane/fastlane<EMAIL_ADDRESS>To: fastlane/fastlane<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [fastlane] Unable to submit to review because of release notes.
(#3716)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_56e7406c62b1d_59df3f7f11f6f2a013659e";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: vpolouchkine
X-GitHub-Recipient: yanndupuy
List-ID: fastlane/fastlane <fastlane.fastlane.github.com>
List-Archive: https://github.com/fastlane/fastlane
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AA3w3Gc6HeWM02dMNO5OU6FDvje4bvNZks5pteZsgaJpZM4HvqoU
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-Spam-Status: No, score=-2.4
X-Spam-Score: -23
X-Spam-Bar: --
X-Ham-Report: Spam detection software, running on the system "serveur.ex2-p10.com",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  What happens if you remove the skip_metadata flag? --- Reply
to this email directly or view it on GitHub: https://github.com/fastlane/fastlane/issues/3716#issuecomment-196554406
What happens if you remove the skip_metadata flag? [...]
Content analysis details:   (-2.4 points, 5.0 required)
pts rule name              description

-5.0 RCVD_IN_DNSWL_HI       RBL: Sender listed at http://www.dnswl.org/, high
trust
[<IP_ADDRESS> listed in list.dnswl.org]
-0.0 RCVD_IN_MSPIKE_H2      RBL: Average reputation (+2)
[<IP_ADDRESS> listed in wl.mailspike.net]
1.1 DATE_IN_PAST_06_12     Date: is 6 to 12 hours before Received: date
-0.0 SPF_PASS               SPF: sender matches SPF record
1.6 HTML_IMAGE_ONLY_12     BODY: HTML: images with 800-1200 bytes of words
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
X-Spam-Flag: NO
----==_mimepart_56e7406c62b1d_59df3f7f11f6f2a013659e
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
What happens if you remove the skip_metadata flag?

Reply to this email directly or view it on GitHub:
https://github.com/fastlane/fastlane/issues/3716#issuecomment-196554406
----==_mimepart_56e7406c62b1d_59df3f7f11f6f2a013659e
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
What happens if you remove the skip_metadata flag?
—Reply to this email directly or view it on GitHub.

----==_mimepart_56e7406c62b1d_59df3f7f11f6f2a013659e--


Implement UMD commonjsStrict pattern

UMD CommonJS Strict:
https://github.com/umdjs/umd/blob/master/templates/commonjsStrict.js
This allows the library to define it's module using AMD, CommonJS or a browser
global, usually window.
This changes the pattern slightly to provide the DiceRoller and DiceRoll
directly on the browser global as it was doing before. Therefore there are no
changes to this library when used in a browser however, it can now be used with
AMD or CommonJS as well.
Fixes #9

Thanks @Kasuko that's fab.
I've merged your changes into develop. I'm not at my dev machine at the moment, but I'll do a proper release, to master tomorrow, which will be v1.2.2.

@Kasuko I need to add an example of usage, with UMD CommonJS to the "usage" section of the readme.
Would you be willing to provide a sample usage for me to throw in there?
Also, I'd love to see where/how it's being used, if you're happy to share a link to your TiddlyWiki?

Sure, took a bit since I wasn't actually using Node for anything so I have recreated your Usage script but in Node, which is pretty identical except for the requiring and the printing.
// require the dice-roller library
const dr = require("./dice-roller.js");

// create a new instance of the DiceRoller
var diceRoller  = new dr.DiceRoller();

// roll the dice
diceRoller.roll('4d20-L');

// get the latest dice rolls from the log
var latestRoll = diceRoller.getLog().shift();

// output the latest roll - it has a toString method for nice output
console.log(latestRoll.toString());

Once I finish implementing it in TiddlyWiki I'd be happy to share. I only have the library being imported now but I still have to write some TiddlyWiki specific stuff to make it usable.

I have thrown up a quick example with my preliminary implementation of this library in a TiddlyWiki at http://tiddlyd20.tiddlyspot.com/
Right now there are just dice-rolls being rendered in the WikiText. Eventually, I will add more usable examples such as a button to roll dice etc.

Cheers. I've added that example to the readme, and pushed it out as another minor release (v1.2.3)
It's nice to see it in the wild! I'm planning on building a GUI for it in the future, but that's probably a long way off.

Hey, just wanted to let you know. I have finally integrated your library into a TiddlyWiki plugin for tools to run D&D campaigns with.
Source is here https://github.com/Ionshard/tiddly-dragon
and the working example is here http://ionshard.com/tiddly-dragon/
Thanks for the awesome library!
I am getting ready to release the plugin so this library might get some battle testing soon :)

Looks good! I like how the output works. What else are you planning on adding to the site?


fix(.github): read right file for schema version checks

What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area CI
Does this PR require a change in the driver versions?
What this PR does / why we need it:
Which issue(s) this PR fixes:
This amends a refactor mistake merged in #1273.
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
fix(.github): read right file for schema version checks

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 4a9b1d70641ab878f68da83acbb257faa979a554

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Priority does not work on default command with Remainder parameter

I'm trying to make a default command that takes a Remainder, to priorities it under the other commands i added Priority(0) to all commands but the default one while i added Priority(Int32.MinValue) to it. This did not help, the bot still executes the default command if any of the others are called, it just takes the commandname as parameter.
Note: The api support guild could sadly not help me.

We tried, Coach. 🙃
On a more serious note, can you maybe share some sample code that we could use to repro the issue?

I know you tried, just wanted to avoid commands suggesting i ask in the support guild. Also, i will add an examplecode.

ok, that resolved my problem, i wrote Command() instead of Command. Wich produced the issue.