Disable flaky max request size replication test and fix a retry httpc issue

Disable flaky 413 replication test
It is possible that sometimes a multipart/related PUT with a doc and
an attachment would fail with the connection being un-expectedly
closed before the client (ibrowse) gets to parse the 413 error
response.
That makes the test flaky so it is disabled for now.
In some cases such as when replicator flushes a document received from an
open_revs response, it explicitly sets the number of retries to 0 because
the context for that request might not be restartable and the retry should
happen at a higher level

I have been running soak tests of this PR for 8 or so hours and they haven't failed. Before that test would make it fail withing 10 minutes.

For reference here are two commits to try to fix the issue:
https://github.com/cloudant/couchdb/commit/66a199dc8d4f92a9ee025e5cc0a673db57830e6e
https://github.com/cloudant/couchdb/commit/72b988bcea788aea5f9f8ae89f7297c4a8232a65
They helped some, it took much longer for the test to fail, however it is not a 100% solution.


[PE-D][Tester B] Edit for an index out of bounds

Error message for command "edit 17"should be "index provided is too big" instead of "at least one field must be provided". The error message only changes to "index provided is too big" when i add a field ("edit 17 n/test")

Labels: type.FeatureFlaw severity.Low
original: bryanongjx/ped#3

We personally find that the order of error message is valid as the format of the command is wrong in the first place


UX Network Account Zero-Available Quandry: Cannot buy RAM, Cannot Unstake NET/CPU

Using Anchor 1.1.1, cannot buy RAM or unstake resources, account is basically unusable:
0 UTX available (100% staked)
1+ million staked CPU
1+ million staked NET
11K+ UTXRAM
When attempting to purchase 1024 bytes of RAM:
"Insufficient available balance to complete transaction."
When attempting to unstake just a few thousand NET:
"account genesis111cm has insufficient ram; needs 4105 bytes has 4096 bytes"
In a Catch-22: not enough ram to unstake cpu/net, and not enough UTXRAM (although I have 11K+ in the account) to purchase a small amount of RAM.

Does the RAM purchasing screen show a balance? It's interesting that the UI is blocking the purchase despite you having the available UTXRAM balance.
One potential thing that may have happened is the configuration got screwed up somehow - which may be able to be resolved if you reset the application (via Tools), which will restore all the defaults, and then reimport your keys into a fresh wallet. Just be sure before you reset that you have a backup of all of your private keys to avoid erasing that data!

Not sure what screen that is, so attached 3 images and hopefully one of them is what you're referring to.
I have the keys safely archived elsewhere, so I will attempt the reset and re-import...

On the 3rd screenshot, this part leads me to believe the configuration may have gotten corrupted somewhere between 1.0.5 and 1.1.1.

That section should display UTXRAM Balance and then display how many tokens you have. I'd give the reset a try, and see if that fixes it. We'll dig on our end to see if we find anything wrong with that section as well.

The reset/reimport worked just fine.  Just purchased and doubled available RAM.  Thanks for your support!

Awesome, glad that worked! Hopefully this bug will only happen to the select few who went through and used 1.1.0 - and those who start using 1.1.1 and beyond won't experience this. Thanks for letting us know!


Angular 1.5 support

first. the question.
does this library run whit angular 1.5?

Yes.

It should work, if there is some error, please open an issue with a repro. Thanks!


Move static files from WebsiteEditor to WebsiteProvider

Steps to reproduce

Start KitchenSink (a0c8513), WebsiteEditor, WebsiteProvider (d7b875f)
Stop WebsiteEditor
Go to localhost:8080/kitchensink

Expected result
You should see KitchenSink wrapped in the DefaultSurface
Actual result
You get an exception because the static files are missing.
The static files should be moved from WebsiteEditor to WebsiteProvider.
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: Can not find referenced Html file: "/Websiteeditor/surfaces/DefaultSurface.html"
   at Starcounter.HtmlFromJsonProvider.ProvideFromFilePath[T](String filePath) in C:\TeamCity\TeamCity10\buildAgent\work\sc-6455\Level1\src\Starcounter\Middleware\HtmlFromJsonProvider.cs:line 58
   at Starcounter.HtmlFromJsonProvider.Invoke(MimeProviderContext context, Action next) in C:\TeamCity\TeamCity10\buildAgent\work\sc-6455\Level1\src\Starcounter\Middleware\HtmlFromJsonProvider.cs:line 52
   at Starcounter.Internal.JsonMimeConverter.Convert(Request request, IResource before, MimeType mimeType, MimeType& resultingMimeType) in C:\TeamCity\TeamCity10\buildAgent\work\sc-6455\Level1\src\Starcounter.Apps.JsonPatch\BuiltInRestHandlers\JsonMimeConverter.cs:line 18
   at Starcounter.Json.AsMimeType(MimeType mimeType, MimeType& resultingMimeType, Request request) in C:\TeamCity\TeamCity10\buildAgent\work\sc-6455\Level1\src\Starcounter.XSON\Class Json\Json.IResource.cs:line 45
   at Starcounter.Response.ConstructFromFields(Request req, Byte[] givenBuffer) in C:\TeamCity\TeamCity10\buildAgent\work\sc-6455\Level1\src\Starcounter.Internal\Http\Response.cs:line 809
   at Starcounter.Request.SendResponse(Response resp, Byte[] serializationBuf) in C:\TeamCity\TeamCity10\buildAgent\work\sc-6455\Level1\src\Starcounter.Internal\Http\Request.cs:line 1241
   at Starcounter.Internal.AppsBootstrapper.ProcessExternalRequest(Request req) in C:\TeamCity\TeamCity10\buildAgent\work\sc-6455\Level1\src\Starcounter.Apps.JsonPatch\AppsBootstrapper.cs:line 810
ParamName=Can not find referenced Html file: "/Websiteeditor/surfaces/DefaultSurface.html"
HResult=-2146233086

More information about this error may be available in the server error log.

Starcounter version <IP_ADDRESS>69
Technical information
Screenshot

Isn't this because SampleWebsieTheme changes values in the database?

It is reproducible without SampleWebsiteTheme. I have corrected the error and the screenshot.

Done in #145. Closing.

I still have the issue, any idea what am I doing wrong here?

@PatrykSzwer  @un-tone

That file is located in /websiteprovider/surfaces/DefaultSurface.html path. You have to update surfaces' URIs

@PatrykSzwer maybe you have ready steps how to do update the URIs fast?

We currently don't have any quicker way than just do /resetdata or manually changing that in DB.

Hi guys,
Sorry I totally forgot to follow up on this. Mujahid helped me fix this issue, we just had to copy paste a folder on the path \Website\src\WebsiteEditor\wwwroot\WebsiteEditor\surfaces with following html files.

@atifwaqar I'd just remind that in this case you should not forget to update these files from \Website\src\WebsiteProvider\wwwroot\WebsiteProvider\surfaces each time when you updating your Website* app instances.


chore: fix circle ci cache

This PR introduces fix for CI system that has been caused by recent release of circleci/node:8-browsers image, to unblock our pending CI builds.
This has resulted in policies around how cache is saved/restored being desynchronised, and the resolution strategy, essentially, is to "clear" the cache by bumping its key version, as it was suggested in the docs: https://circleci.com/docs/2.0/caching/#clearing-cache

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Installation issue with debian

I am getting an error while I am trying to install otcextensions on Debian 9
Installation procedure:
sudo apt update
sudo apt install gcc python3 python3-dev python3-pip libssl-dev
sudo pip3 install otcextensions python-openstackclient

Collecting otcextensions
  Using cached https://files.pythonhosted.org/packages/e8/e7/fbac77ea8ba410925a0f20483ff0a6b45fc191f7f82f177ce30395854fed/otcextensions-0.6.5.tar.gz
Requirement already satisfied: openstacksdk>=0.29.0 in /usr/local/lib/python3.5/dist-packages (from otcextensions)
Collecting oslo_i18n (from otcextensions)
  Using cached https://files.pythonhosted.org/packages/61/eb/4732a0f12850ef5ada812d4920c6801b7e394f14969864a91927ed853a2f/oslo.i18n-3.23.1-py2.py3-none-any.whl
Requirement already satisfied: netifaces>=0.10.4 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: os-service-types>=1.7.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: six>=1.10.0 in /usr/lib/python3/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: iso8601>=0.1.11 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: jmespath>=0.9.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: pbr!=2.1.0,>=2.0.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: munch>=2.1.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: decorator>=3.4.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: requestsexceptions>=1.2.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: keystoneauth1>=3.14.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: jsonpatch!=1.20,>=1.16 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: PyYAML>=3.12 in /usr/lib/python3/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: appdirs>=1.3.0 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: cryptography>=2.1 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: dogpile.cache>=0.6.2 in /usr/local/lib/python3.5/dist-packages (from openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: Babel!=2.4.0,>=2.3.4 in /usr/local/lib/python3.5/dist-packages (from oslo_i18n->otcextensions)
Requirement already satisfied: requests>=2.14.2 in /usr/local/lib/python3.5/dist-packages (from keystoneauth1>=3.14.0->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: stevedore>=1.20.0 in /usr/local/lib/python3.5/dist-packages (from keystoneauth1>=3.14.0->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: jsonpointer>=1.9 in /usr/lib/python3/dist-packages (from jsonpatch!=1.20,>=1.16->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: asn1crypto>=0.21.0 in /usr/local/lib/python3.5/dist-packages (from cryptography>=2.1->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: cffi!=1.11.3,>=1.8 in /usr/local/lib/python3.5/dist-packages (from cryptography>=2.1->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: pytz>=2015.7 in /usr/local/lib/python3.5/dist-packages (from Babel!=2.4.0,>=2.3.4->oslo_i18n->otcextensions)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.5/dist-packages (from requests>=2.14.2->keystoneauth1>=3.14.0->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.5/dist-packages (from requests>=2.14.2->keystoneauth1>=3.14.0->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: idna<2.9,>=2.5 in /usr/local/lib/python3.5/dist-packages (from requests>=2.14.2->keystoneauth1>=3.14.0->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /usr/local/lib/python3.5/dist-packages (from requests>=2.14.2->keystoneauth1>=3.14.0->openstacksdk>=0.29.0->otcextensions)
Requirement already satisfied: pycparser in /usr/local/lib/python3.5/dist-packages (from cffi!=1.11.3,>=1.8->cryptography>=2.1->openstacksdk>=0.29.0->otcextensions)
Building wheels for collected packages: otcextensions
  Running setup.py bdist_wheel for otcextensions ... error
  Complete output from command /usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-360opv2x/otcextensions/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmpodostwtbpip-wheel- --python-tag cp35:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for otcextensions
  Running setup.py clean for otcextensions
Failed to build otcextensions
Installing collected packages: oslo-i18n, otcextensions
  Running setup.py install for otcextensions ... done
Successfully installed oslo-i18n otcextensions-0.6.5

Please never ever ever ever use pip (or pip3) as root - see here why
The actual installation is done by wheel. As you want to use python3, please run apt install python3-wheel.

I'll tinker around a bit and add the information for python2 as well as soon as I found out how it works there ;)


Example Prediction Scoring

Task 1 Prediction - Density
Mean Absolute Error: 2.138
R2: -2.927
Normalised Mean Absolute Error (Assessed): 1.783
Points: 0
Task 2 Prediction - Adsorption Energy (Coordinate Data)
Mean Absolute Error: 2.138
R2: -2.927
Normalised Mean Absolute Error (Assessed): 1.783
Points: 0

Task 1 Prediction - Adsorption Energy (No Coordinate Data
Mean Absolute Error: 2.138
R2: -2.927
Normalised Mean Absolute Error (Assessed): 1.783
Points: 0
Task 2 Prediction - Adsorption Energy (Coordinate Data)
Mean Absolute Error: 2.138
R2: -2.927
Normalised Mean Absolute Error (Assessed): 1.783
Points: 0

Task 1 Prediction - Adsorption Energy (No Coordinate Data)
No results submitted for task 1 prediction
Task 2 Prediction - Adsorption Energy (Coordinate Data)
No results submitted for task 2 prediction


Document language extensions icons

While developing language extensions, I had the need to add a custom icon for my language's files. https://github.com/microsoft/vscode/pull/118846 implemented a way to do exactly that but it is not part of the documentation https://code.visualstudio.com/api/language-extensions/overview.

@jrieken, @mjbvz, could you help with routing this issue to the correct owner? Thanks!


directives in code

@lizmat @thoughtstream This concerns the following examples where a =config is used in a code block.
I opened an issue in Rakudo (#5723). However, now I think the current RakuAST parser is correct.
I am opening this issue here to verify.
Currently the following produces an expected AST and is rendered as expected, with =config being rendered as a string
=begin code
   =config item :bullet<->
   =item one
=end code
=item two

Here =item two is not affected by the config.
However, in the following, the =config line is missing from the rendered text, and is executed.
=for code
   =config item :bullet<->
   =item one

=item two

Here item two is affected by the config.
I thought at first this was a flaw in the parser. Now I am unsure. Consider the following top lines of a RakuDoc source:
=begin rakudoc
=TITLE Build a website from current directory
=SUBTITLE The Build component for the Elucid8 framework
=for AUTHOR :hidden
Richard Hainsworth, aka finanalyst
=for VERSION :hidden
v0.1.0
=config code :lang<text>
=begin SYNOPSIS
The component is part of the C<Elucid8> distribution and is installed
.. more lines from SYNOPSIS etc

Here TITLE is currently ended by SUBTITLE, =for AUTHOR is ended by =for VERSION and =for VERSION
is ended by =config code :lang<text>.
This seems reasonable. But it would not be possible if =config were a part of the =for VERSION block.
So the rule being followed by the RakuAST parser is: a =for block is ended by a blank line or a directive. I am not sure whether this was explicitly specified. But I think it is reasonable.
If a directive needs to be in a code block, then the block must have an explicit =begin/=end.
@thoughtstream Any thoughts. If you agree with the last assertion, then I will close the Rakudo-AST issue.

I concur with the last assertion (and with the entire analysis).
There is no bug here in the behaviour of the parser.
Every extended block and every abbreviated block always
terminates immediately at the next blank line or directive.
So a directive can only be placed as content inside a code block
when the code block is in the delimited form.

Closing as resolved


fix: missing blast key

Description

Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)
Fixes
Related pull request(s)

Closing this PR, as this change is stale and has timestamp clonficts


fix pthread_setaffinity_np error handling

Original issue: https://charm.cs.illinois.edu/redmine/issues/519

Since bug 501 is delayed to 6.0.1 I've broken out this fix to pthread_setaffinity_np() error handling.
The old code assumed that pthread_setaffinity_np() set errno and returned 0 or -1 like setaffinity, but it actually returns the full error code.  This patch (emailed to core) sets errno to the return value of pthread_setaffinity_np() so that perror() works.

Original date: 2014-06-17 17:34:44

Patch looks good, applying. Thanks

Original date: 2014-06-18 12:45:38

Jim: for future issues for which you have a patch prepared, feel free to submit them directly to Gerrit. We're not going to be strict about an open issue for every change to the codebase.


AV error after setting SVGText in TSVGIconImage

Got this even though icon was set ok (think I got it one or twice, not sure if IDE issue or not)

Btw, I was trying to set that image again (accidentally I was trying to set it at my base TStoryItem class instead of at the descendent TImageStoryItem, those are from https://github.com/zoomicon/READCOM_App). I noticed if I set the SVGText to the Glyph object I have there (of TSVGIconImage type) at a descendent frame (say in TAudioStoryItem) upon pressing Save it clears the SVG from the display (and loses it). Not sure if it's something I'm doing wrong in my base frame constructor, it was working till recently and think it broke (lost the SVG images at descendent frames) upon updating your library from GetIt.
So, have you tried if your TSVGIconImage stores its SVGText state ok when it is used with Frame inheritance (aka set at a descendent frame)?

so if I edit my .fmx of the inherited frame (TAudioStoryItem, descending from TStoryItem) by hand and open it, shows OK, but pressing save again it replaces SVGText with ''. The ancestor (the TStoryItem) has Glyph's SVGText as '' instead (the property editor doesn't seem to be able to set an empty string/file). So load when using frame inheritance works, but save somehow fails (instantly replaces SVGText with '')
inherited AudioStoryItem: TAudioStoryItem
Size.Width =<PHONE_NUMBER>00000000000
Size.Height =<PHONE_NUMBER>00000000000
OnClick = FrameClick
inherited Glyph: TSVGIconImage
Opacity = 0.300000011920929000
Size.Width =<PHONE_NUMBER>00000000000
Size.Height =<PHONE_NUMBER>00000000000
SVGText =
''#10'<svg xmln' +
's:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http:' +
'//www.w3.org/2000/svg" xmlns:cc="http://web.resource.org/cc/" xm' +
'lns:xlink="http://www.w3.org/1999/xlink" xmlns:dc="http://purl.o' +
'rg/dc/elements/1.1/" id="Layer_1" enable-background="new 0 0 100' +
' 100" xml:space="preserve" viewBox="0 0 100 100" version="1.1" y' +
'="0px" x="0px">'#10'    '#10''#10
end
inherited Border: TRectangle
Size.Width =<PHONE_NUMBER>00000000000
Size.Height =<PHONE_NUMBER>00000000000
end
object MediaPlayer: TMediaPlayerEx
FileName = ''
Muted = False
AutoPlaying = False
Looping = False
Left = 26
Top = 50
end
end

update: also just noticed that if I save an even deeper descendent frame than the one where I set the SVGText property of the TSVGIconImage that had been inherited from parent frame, it saves ok. It only fails (clears the SVGText) if I press Save in the frame that defined the SVGText (as I said that is a descendent frame of the one where TSVGIconImage component was defined)
If I add by hand in the .fmx file the SVGText it works ok.
Also note before I had that SVGText in the child Multires bitmap and it was saving ok, but after upgrade to new version it lost that data. You may be missing some call to "inherited" if you define persisted content programmatically / on-the-fly

Is this problem also present? I don't use Android apps as extensively as you do, so I can't reproduce the problem...

Not related to Android, but to frame inheritance. You may have forgotten to call inherited if you’ve overriden the persistence calls


Error: Too many open files - link-checker-crawled-pages.pstore

Love the gem!   But unfortunately, it's not working for me on my large site.
I end up with errors only a few thousand links into my several hundred thousand page site, http://www.thehollywoodgossip.com
Are there settings / tweaks I can make to make this work?

@ehoch, solution from @Paxa works. Please close the issue.


Use UIScreen.nativeScale instead of scale where available (iOS 8+)

Starting with iOS 8.0, UIScreen.nativeScale should be used to convert
from points to physical device pixels. In many cases, the "native scale"
and "scale" values match, but there are some exceptions:

Devices that perform hardware downsampling (iPhone 6+/6s+/7+/8+)
Devices supporting zoomed display mode (all iPhone 6/7/8 variants),
when display mode is enabled.

This fixes #78.

Awesome, thanks!


Foreign fields 5: Optimized multiplication of sums

This PR introduces a heavily optimized way to constrain foreign field expressions involving the product of two values or sums of values on the left side and a sum on the right side. Example:
(x - y) * z = a + b

A close analysis of the ffmul gate shows that for expressions like these, the ffmul gate is valid even without doing range checks or bounds checks on the sums x - y and a + b (assuming that the original values x, y, a, b are range-checked as usual).
Note that this is violating the assumptions that went into the original soundness proof of the ffmul gate, in multiple ways. At the bottom, we sketch an argument for why these assumptions can be weakened.
The API we introduce for adding these multiplication constraints uses a new "lazy sum" type, which allows optimal chaining and constraint-savings without leaking any of the involved complexity to the developer:
let xMinusY = ForeignField.Sum(x).sub(y); // create a lazy sum
let aPlusB = ForeignField.Sum(a).add(b); // another one

// assert that (x - y) * z === a + b
// `assertMul()` accepts either lazy sums or plain foreign field elements
ForeignField.assertMul(xMinusY, z, aPlusB, f);

What happens under the hood

Sums like a + b that go into the remainder are wired to the multiplication result directly, without any additional constraints. This has to do with the fact that the ffadd gate constrains its result a + b in compact limb form [r01, r2], and ffmul only uses the remainder in its compact form, so ffadd tells us enough about its output to be safely used in ffmul.

Note: To exploit this, we had to give the new API the form of an assertion (assertMul(x, y, z)) rather than a computation (mul(x, y) -> z).

For sums like x - y which become a multiplication input, ffmul uses the two lower limbs individually, which aren't constrained by ffadd. Therefore, we add additional generic gates which perform roughly the ffadd logic, just on the lowest limb. This is enough to guarantee that ffadd-equivalent equations hold on all 3 limbs. This is cheaper than ensuring limbwise constraints using a multi-range check on x - y.
For the left input sum, we ensure that ffadd is chained into the ffmul gate

Results
Empirically, using assertMul() for the example equation (x - y)(x + y) === x^2 - y^2 lowers the constraint count from 32 to 20 compared to a naive version with mul(), add() and sub(). Note that the naive version also suffers because it computes the left and right side separately, and so applies range-checks to the same result twice. This is another motivation for why an "assertion" API is better than a "computation" API.
These savings are crucial for EC addition, which essentially only consists of three calls to assertMul() with different types of sum.
Summary of changes

adds ForeignField.assertMul(), ForeignField.Sum()

including tests

new optimized gadget for constraining the carry to 0, 1 or -1 using generic gates

starting a new file of gadgets, basic.ts

new Unconstrained API. to facilitate the generic gate computation in Sum, I had to do computations on an auxiliary bigint that are interleaved with provable code. I added the Unconstrained class as a safe wrapper for auxiliary values like this, trying to realize some of @nholland94's ideas about boundaries between proof/auxiliary execution contexts

Sketch: Soundness of assertMul()

There are two high-level ingredients to the soundness proof for ffmul:

limb-wise equations mod n must actually hold over the integers. this is ensured with range-checking all participating terms
in the final equation, we must ensure bounds on the combined bigints to go from "mod 2^3l n" to "over the integers"

Re (1): The result of an ffadd chain, even without range check, is guaranteed to be a sum of small terms mod n. For a proof, see the PR description of #1220 (recommended read to understand the reasoning here)
To be precise, this is true for the combined lower two limbs r01, and for the high limb r2
If we add another equation that guarantees r0 = x0 + sign*y0 - overflow*f0 - carry*2^l, we can use that in the eq. for both lower limbs and conclude the same thing for r1 separately
If we replace "small value thanks to range-check" with "sum of small values" in the ffmul proof, the conclusions of the form |LHS - RHS| < n which guarantee non-overflow are still valid. We can even allow "small negative" values (close to the native modulus) which might be caused by an adversarial carry in ffadd, nothing breaks.
The limbwise equations that are being proved over the integers now prove ff addition and multiplication in one step, instead of only multiplication. this is fine
Re (2), additional bounds checks: We can understand bounds on the inputs of a sum as a weaker version of bounds on the result of a sum, e.g. |x - y| <= |x| + |y|. If x and y are small enough, the bound we need on |x - y| is still guaranteed. The assertMul() gadget enforces a rigorous version of this argument which takes into account the number of summands, see here. We maintain the same assumption used in other gadgets, that inputs are bounds-checked relative to f, i.e. x[2] <= f[2], but depending on the number of summands we enforce a stronger bound on f than elsewhere (other gadgets enforce f < 2^259, assertMul() enforces at least f < 2^258 because we can no longer assume that r is "positive". It doesn't matter because in reality, we're only interested in f < 2^256 and that's supported even for pretty long sums.

Before giving an actual code review, I will start by writing comments on the above explanation.

the ffadd gate constrains its result a + b in compact limb form [r01, r2]

This is true for FFMul, where the remainder is indeed given in compact form in the first 2 columns of the next row. But in the FFAdd gate, the result was given in 3-limb form, in the first 3 columns of the next row so it could chain easily with FFAdd and FFMul. Thus, what exactly are you referring to with the above sentence?

the naive version also suffers because it computes the left and right side separately, and so applies range-checks to the same result twice.

You mean one would naively range check x and y twice? Meaning, when computing $x^2$, once for "left" $x$ and again for "right" $x$? If this is what you meant then yes, this should be avoided and only range check it once to avoid duplicates.

You mean one would naively range check x and y twice? Meaning, when computing , once for "left" and again for "right" ?

I mean that you'd check x^2 - y^2 when calling sub(), and you'd also range-check (x - y)(x + y) when calling mul(), and then you assert they are equal. But if you already know they should be equal you could avoid one of the range checks. It's a minor point, of course we could add a flag to sub() or mul() that tells it to skip the range check. The nice thing about this API here is that it doesn't need any such flags

This is the full constraint system for the assertMul() example I use in the test. It does (x - y)(x + y) === x2 + y2, where x2 and y2 are just witnessed (not constrained)
0    Generic         [1 0 0 1 0] [-1 0 -1 1 0]      0->2, 1->3, 2->5, 3->4, 4->(1,3), 5->0
1    Generic         [1 1 -1 0 0] [2894.. 2894.. -1 0 0] 0->(2,3), 1->5, 2->(6,4), 3->(0,1), 4->(2,6), 5->1
2    ForeignFieldAdd [3094.. 3094.. 1208.. 1]       0->(6,3), 1->(9,1), 2->(9,2), 3->(8,3), 4->(9,4), 5->(9,5), 6->(1,4)
3    Zero                                           0->(6,5), 1->(10,4), 2->(10,5)
4    ForeignFieldAdd [3094.. 3094.. 1208.. -1]
5    Zero                                           0->(20,0), 1->(20,1), 2->(11,1)
6    Generic         [-1 0 -1 1 0] [1 1 -1 0 0]     0->1, 1->(7,0), 2->(7,3), 3->(8,0), 4->(1,2), 5->(10,3)
7    Generic         [2894.. 2894.. -1 0 0] [1 0 0 1 0] 0->4, 1->(9,6), 2->(8,4), 3->5, 4->(6,0), 5->(6,2)
8    Generic         [1 1 -1 0 0] [-1 1 -1 0 0]     0->(9,0), 1->5, 2->(10,0), 3->(9,3), 4->(7,2), 5->1
9    ForeignFieldAdd [3094.. 3094.. 1208.. -1]      0->(2,0), 1->(2,1), 2->(2,2), 3->(1,0), 4->(2,4), 5->(2,5), 6->(7,1)
10   ForeignFieldMul [1208.. 4294.. 0 3082..]       0->(8,2), 3->(3,0), 4->(3,1), 5->(3,2), 6->(12,0)
11   Zero                                           0->(20,2), 1->(5,2), 2->(16,0), 3->(17,0), 4->(18,0), 5->(14,0), 6->(13,0)
12   RangeCheck0     [0]                            0->(10,6), 1->(15,3), 2->(15,4)
13   RangeCheck0     [0]                            0->(11,6), 1->(15,5), 2->(15,6)
14   RangeCheck1                                    0->(11,5), 1->(18,1)
15   Zero                                           3->(12,1), 4->(12,2), 5->(13,1), 6->(13,2)
16   RangeCheck0     [0]                            0->(11,2), 1->(19,3), 2->(19,4)
17   RangeCheck0     [0]                            0->(11,3), 1->(19,5), 2->(19,6)
18   RangeCheck1                                    0->(11,4), 1->(20,3)
19   Zero                                           3->(16,1), 4->(16,2), 5->(17,1), 6->(17,2)
20   Generic         [1 3094.. -1 0 0] [1 0 0 0 0]  0->(5,0), 1->(5,1), 2->(11,0), 3->(14,1)


Update sql-database-service-tiers.md

Added P11 tier to section on Premium.

Hi @shontnew, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@shontnew @jeffgoll
I'll merge this PR when I see a comment here to do so. Thanks.

#sign-off


Fix locked page/snippet cannot proceed a GroupApprovalTask

Fixes #10173.
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Cherry-picked to 4.2.x in 99fc15835e64b4773e47ac21db956dac9f3c57ee.


Repository Mute Filters

This PR implements per-account per-repository mute filters (#10). This enables users to mute a repositories notifications by Subject Type and Reason. To create or edit a mute filter for a repository, you right click on the repo in the filter list and hit Edit Mute Filter.

Clicking Edit Mute Filter will take you to the following window where you can switch off, or on, certain Reasons or Subject Types. You can also delete the mute filter entirely using the X on the top right. Keep will show you notifications for that Reason or Subject Type, whereas Ignore will remove them from your view.

This PR also adds the following section to an accounts settings. Each button will take you to the page above, per repository.

Notifications that are muted are still ingested by Hawk Eye, but never shown to the user.   Sounds will not be raised for notifications that have been muted.
The Settings design for this isn't the best it could be, by a long shot, but I think we can put in a separate PR to alter the structure of that.

Looks like a great start, would definitely go through my repos and toggle a few of these!
Might be good to translate the reasons into more easily understandable scenarios. I don't know off hand what manual means, at least.

@bterlson Great point. I have changed Subscribed across the whole UI to "Watching", and Manual to "Watching Thread". I used https://developer.github.com/v3/activity/notifications/ to work out any changes here. I think the rest make sense?
I'm happy for this to go ahead and possibly release an initial version of this?

I guess "Authored" could be more clear as "My issue" or something similar? But Manual was definitely the most confusing one.
You either have to ship it or send me a build ;)

@bterlson The issue there is that we'd need to separate it out to My Issue, My Pull Request and My Commit for that to make sense. It also wouldn't fit the wording of the others? I'm sure this is something we can look at in the future, but I'm going to merge this PR and prep a build!


documentation on demo server outdated

The documentation on the demo server is outdated: http://demo.mazizone.eu:4567/index_documentation.
Perhaps create a script to keep the documentation up-to-date based on the github wiki, both on the demo server and on the raspberry Pi when a users does an update?

The documentation is updated based on the github wiki.
Please notice that one part of the info here is for the administrator and another part for the user. So the administrator tips are included in the documentation of the admin Portal.

Both in the demo server and version 1.6.5 the user documentation is not updated according the latest version of the github wiki here: https://github.com/mazi-project/guides/wiki/Applications (it would be great if the update is somehow automatic)


Dynamic Data: Not working on classic page

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
The below code should work fine on classic pages as well as modern
this.context.dynamicDataSourceManager.initializeSource(this);
Observed Behavior
When we add a webpart to a classic page that is a IDynamicDataController, the spinner stays there and a console error is thrown that says:
Uncaught Error: Source id contains invalid characters, like "_". Id: "WebPart.00000000-b799-43d5-8529-63f7caf2bd7c.g_cf8229db_8dfa_4a94_a622_ad12393f9c7d".
Steps to Reproduce
Build a SPFX webpart that implements IDynamicDataController and on Init calls "this.context.dynamicDataSourceManager.initializeSource(this);".
Once built deploy to a SharePoint and add to a classic page.
@VesaJuvonen
Thanks for your contribution! Sharing is caring.

What is your SPFx version and the library versions in package.json?

Dynamic Data is only available in the "1.5.1-plusbeta" packages

Lack of dynamic data support in the classic is by design and we are not currently planning to support this with the GA version of the dynamic data. Notice that there are also other ways to bypass the content between the components if needed for the classic experience.


[FEAT]: Gear added to the generation tool

Description
Would like to see this generate gear, weapons, armor, and coins into the NPC's inventory.
Additional Information
No response

Hi @valcoren, thank you for submitting a feature request. By any chance, is what you're referring to in the request the same as what's discussed here?

Hi @valcoren, thank you for submitting a feature request. By any chance, is what you're referring to in the request the same as what's discussed here?

It is, I noticed it was already out there after making the submissions. Feel free to disregard it as you are already on it. Thanks for responding to the request.  I currently use Chatgpt to generate all my NPC's I have a prompt that will build Stats, Backstory, Weapons, Armor, Gear, and Lootables. currently, it's a manual process to have to transfer that from Chatgpt to an NPCsheet in Foundry. I would love to have it automated. It seems based on this module you are already on this path.


fix for const-prop lint changes

Cc https://github.com/rust-lang/rust/issues/69331

@bors r+

:pushpin: Commit 627d7cba644575467eb276a853acc07f7fcf2b33 has been approved by RalfJung

:hourglass: Testing commit 627d7cba644575467eb276a853acc07f7fcf2b33 with merge 9e94ab640ac51c7277f4fffbf573bafb3940bab5...

:broken_heart: Test failed - checks-travis

@bors r+

:pushpin: Commit 3e2f29a0796af501485e13cfa06302aa6e479d6a has been approved by RalfJung

:hourglass: Testing commit 3e2f29a0796af501485e13cfa06302aa6e479d6a with merge 5b8462066d99511a5ca119cbd3a1443ccf675714...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing 5b8462066d99511a5ca119cbd3a1443ccf675714 to master...


Tracking multiple drugs in treatment types

E.g. at the moment for corticosteroids, we have treatment_corticosteroid as a boolean, but the only treatment we store information about is dexamethasone (treatment_dexamthasone). Suggest changing the boolean 'treatment_dexamethasone' to a combinedType list field similar to ethnicity, so we also track Methylprednisone, Prednisone and then have 'other' as a free text field within the combined type.
Repeat for similar fields - e.g. antiviral, experimental agents.

Good issue!. could we have it in the schema? then we can easily add it in
the parser ..
On Tue, Feb 28, 2023 at 11:42 AM Pip Liggins @.***>
wrote:

E.g. at the moment for corticosteroids, we have treatment_corticosteroid
as a boolean, but the only treatment we store information about is
dexamethasone (treatment_dexamthasone). Suggest changing the boolean
'treatment_dexamethasone' to a combinedType list field similar to
ethnicity, so we also track Methylprednisone, Prednisone and then have
'other' as a free text field within the combined type.
Repeat for similar fields - e.g. antiviral, experimental agents.
—
Reply to this email directly, view it on GitHub
https://github.com/globaldothealth/isaric/issues/86, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABW7SJFO4YLWQ5YFDZL6Y3LWZXQDNANCNFSM6AAAAAAVKTQ7MY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Make all C -> Lua calls protected and allow user error handlers in uv.run()

This task will fix #99.
The idea is to protect all calls into Lua from C using pcall.  If there is an error, it will be handled by the current global error handlers.  If there is no current error handler then we'll throw an unprotected lua error (most likely this will crash the process).
Since calls to uv.run() are blocking, then "nested" calls will be all "stacked" in the current C stack.  Therefore users can have nested error handlers.  A unit test framework may wish to handle all global errors, but only for the duration of it's test unit.  It can call and block on uv.run() with a custom error handlers that pertains to that one test.  When the test finishes and uv.run() returns, then the old error handler will be restored.
The new signature will be uv.run(mode, onError).

Perhaps make the errors a ring. Just to make sure it isn't unbounded.

That's not a problem, errors thrown by error handlers won't feed back into themselves.

My implementation idea is to add a couple global variables per luv instance.  One will hold a reference to the current error handler function.  The other will be a temporary place to hold the error value when an error happens.
The global error handler on the C side will simply store the error in the global place and unblock uv_run() with uv_stop().  Then the luv_run() wrapper will check the global error slot for a possible error.

WIP at #129

I decided this is a very deep rabbit-hole with little benifit.  I instead made a simple change to lua_pcall all callback event sources and hard-error if there is an uncaught exception.  All existing luv, luvi, and luvit unit tests still pass with this change since we almost always wrap our code in xpcall to get stack traces.
This change will simply enforce the current de-facto behavior and let you know if you forget to protect your event sources.

Implemented in https://github.com/luvit/luv/commit/7526c1d9955f085df9eb1c25fcc31c0cfe67e583

Probably should be reopened if you allow my humble five cents...
Catching runtime exceptions isn't the only reason why a C->Lua call should be protected. Studying your code, I can see that you pay no attention to the fact that many Lua C API functions may trigger out of memory exceptions. For example, lua_pushcfunction() that you use in luv_call_callback is prone to exceptions in Lua 5.1 due to the absence of light C functions (it always create a closure). In other words, any function that leads to memory allocation may fail (new strings, tables, string conversions, etc). One must pay attention to the types of exceptions a C API function generates as denoted in the Lua C API manual to the right of their names. What if one wants to confine memory usage of a Lua state and provides a custom lua_Alloc with some sort of accounting when luv is used as a library? Or is it impossible to create a custom Lua state?
Speaking more broadly, a pattern to reliably call a callback must be:

lua_cpcall() into a callback wrapper with an argument pointing to a structure on the C stack which you fill with the outer callback's arguments;
Inside the wrapper, it is safe to manipulate the stack, so fetch your Lua function, prepare its arguments and call it via lua_pcall() or  even lua_call() since you are already protected;

Another problem to this is that in your code, you mix malloc() and the allocator of the Lua state (indirectly). Moreover, many calls to malloc() don't even bother to check if the allocation succeeded or just assert it's successful. The assumption that if a memory block cannot be allocated, the process  must terminate is a brave one.:-) I'd recommend allocating internal structures via lua_newuserdata() for protection and consistency or at least use lua_getallocf() to fetch the current Lua state's allocator.
Loosely connected to the above, I can see that luv_alloc_cb() always allocates suggested_size which is always 64Kb by default. This is very slow and ineffective on most systems. I'd recommend buffer pooling.

The assumption that if a memory block cannot be allocated, the process must terminate is a brave one.

I think of it as a non-feature to keep things simpler and easier to maintain.  Is this constraint actually a problem for anyone?  Does it prevent you from doing something you want to do?
That said, you bring up good suggestions.  I'm just not sure who has the bandwidth to implement the change.

Well, I understand that this is fine grained approach and for most people it sounds like overkill, but in fact, it is the way to do things right as it is done in Lua itself. For example, check the source of standalone Lua to see that it first obtains protection via lua_cpcall (or lua_pcall for Lua 5.3) and only then manipulates the stack - loads chunks, pushes arguments, etc.
Based on years of direct experience with daemons running Lua code 24/7, we constantly run into situations when inadvertent Lua memory leaks happen (missing table clean ups, recursions, etc.). Lua itself is durable enough not to crash in such cases. Some measures are taken to ease things a bit internally like emergency garbage collection, gradual approach in allocation for LuaJIT, etc. But allocation related design flaws in the host code will definitely lead to a crash/termination of such a process which means it will be much harder to investigate what happened while it could have been possible to try to debug things live.
Another case is when a Lua state is sandboxed in terms of memory (may be not related to luv though if it's not possible by design to provide an already created Lua state to it). Imagine when a custom allocation function is provided to a Lua state upon creation and a memory exception happens (memory limit has been exceeded and the allocator deliberately returned NULL), the whole unprotected thing finds itself in the default panic function with a broken event loop because a long jump has just been made. Even if it's not a crash, it's unrepairable.
Hope this helps.

Another unrelated thing (which probably requires a separate issue to be opened) is that one must be very careful when converting stack values to strings via any of lua_tostring, luaL_checkstring, luaL_optstring and other functions that may cause coercion. For example, I can see that in your code when a table of strings is written to a stream, there is no protection that an element might in fact be a number. When a uv_buf_t vector is being initialized, the item is converted to a string on the stack and its pointer is saved in the vector. All seems good. However, after the conversion is made and before the actual string is written to a socket in a uv_write_t request, garbage collection may happen effectively invalidating the saved pointer because its source string existed briefly on the stack as a result of coercion (the item in the table is still a number, not a string). And that means in turn that undefined data will actually be written.
Btw, the table that is used to form a uv_buf_t vector may be altered even after the call directly in Lua which will lead to the same outcome. There is no protection against it.
I haven't checked through your code much, but there are many other caveats when using Lua C API that one must be aware of. They are all more or less mentioned in the manual though.


(WIP) Introducing new command New-ClusterAvailabilitySet

PR Summary
Add new command to the command reference.
PR Checklist

[X] Descriptive Title: This PR's title is a synopsis of the changes it proposes.
[X] Summary: This PR's summary describes the scope and intent of the change.
[ ] Contributor's Guide: I have read the contributors guide.
[ ] Style: This PR adheres to the style guide.

@scanum  Seems it is still draft


Requirements for qr_generator not found: ['pillow==9.5.0']

I'm receiving this error after updating Home Assistant.
Setup failed for custom integration qr_generator: Requirements for qr_generator not found: ['pillow==9.5.0'].
Home Assistant 2023.4.5
Supervisor 2023.04.0
Operating System 10.0
Frontend 20230411.1 - latest

You have to make sure that you install the version 1.0.4 (Beta) of this integration only when you have HA version 2023.5.0 or greater.


Revert "Upgrade Couchbase Server.app (Enterprise) to v3.0.4"

Reverts caskroom/homebrew-cask#11636

Thank you for the contribution. It was merged directly as dc5d03933fa29d57131dcde13edabc196badf8ac to keep commit history cleaner. Your contribution is still credited to you.


Add Q2 2020 canary

@j01tz sig checks out
$ gpg --verify canaries/canary-003-2020-q2.txt.asc.j01tz canaries/canary-003-2020-q2.txt
gpg: Signature made Wed  8 Apr 16:59:17 2020 -05
gpg:                using RSA key A70943BD109858B5034E23AC9969F570C2EF616F
gpg: Good signature from "John Woeltz<EMAIL_ADDRESS>[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: A709 43BD 1098 58B5 034E  23AC 9969 F570 C2EF 616F

Proof of freshness checks out

https://grinscan.net/block/644188
https://blockchair.com/bitcoin/block/000000000000000000020a911a9f9db2f1e12af1030cb7779e21c2f88d5d734a
https://etherchain.org/block/9834092
https://blockchair.com/litecoin/block/67aa7bfedac169a5f9a0c5c3a0bede88853fbf4c1bb4e92de94b1f2a954cc307


Accessing Controls open all visible Comboboxes

Expected Behavior
Access UIA Element without opening all visible Comboboxes.
Actual Behavior
All visible Comboboxes get opened while accessing any Control.
Steps to Reproduce the Problem

Open a UIA Application
Open a Dialog with different Controls inclusive some Comboboxes
Open any non Combobox Control; All visible Comboboxes get opened for a Second

Short Example of Code to Demonstrate the Problem
None
Specifications

Pywinauto version: 0.6.6
Python version and bitness: 3.7.2 64 bit
Platform and OS: Windows 10

You should try to access elements by child_window() instead of dialog['name']. For example, Access an Edit control by dialog.child_window(auto_id="1001", control_type="Edit") instead of dialog['Edit0']. If multiple elements match, you can feed another parameter to child_window, like child_window(auto_id="1001", control_type="Edit", found_index=1).


NIFI-5552 - Add option to normalize header column names in CSVRecordR…

…eader
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Hey @pvillard31 thanks for putting up a PR! I looked through it, and I do believe that it would resolve the issue that is being described in NIFI-5552. However, I'm not entirely sure that this is the best approach. This approach is adding property to the CSV Reader that are very much tailored toward Avro. I think the better approach would be to instead update the WriteAvroSchemaAttributeStrategy and AvroTypeUtil classes to normalize the names as necessary, so that Avro-related concerns are confined to the Avro-specific strategy.

Hey @markap14 - thanks for the review. You're right, it's much better to address it when creating the Avro schema. That would prevent this error to happen again if one day we add a Reader for a format that would accept non Avro compatible field names.
Just a quick remark. Initially in AvroTypeUtil I just wanted to change L123 from:
final Field field = new Field(recordField.getFieldName(), schema, null, recordField.getDefaultValue());

to
final Field field = new Field(normalizeNameForAvro(recordField.getFieldName()), schema, null, recordField.getDefaultValue());

But not sure changing the name just here is really a good idea and if it's not going to break some things in other places. In the end, I changed all the occurrences of recordField.getFieldName() to normalize the name. Thoughts?

@pvillard31 we don't want to change recordField.getFieldName() - that is the NiFi class and has nothing to do with Avro. We really want to avoid enforcing any Avro naming peculiarities on NiFi - we should only enforce them for Avro, so I think the AvroTypeUtil is the right place to put this. You should not need to worry about breaking backward compatibility, because the normalizeNameForAvro method should make no changes to the name unless the name is invalid - in which case it would have thrown an Exception previously.

we don't want to change recordField.getFieldName() - that is the NiFi class and has nothing to do with Avro. We really want to avoid enforcing any Avro naming peculiarities on NiFi - we should only enforce them for Avro, so I think the AvroTypeUtil is the right place to put this.

Yeah totally agree here.
I didn't change recordField.getFieldName(), I just wrapped it, in AvroTypeUtil, to ensure the name is normalized. My concern was more about methods like lookupField where we assign the field name to the record field object. Just want to ensure that this pair/map is not used outside of the AvroTypeUtil where we would try to access the record field object with a non-normalized field name. Does that make sense?

closing due to inactivity


Update NL COVID vaccination

25ca2057-978c-49b8-a9e6-1a1f70732659 is dead: add new dataset
Update historical data for administration/completion (if necessary)
Add data processing for new dataset

Fixed by f84d3df80bdf0fb1bbf5019f69489f17756f0cda.


technical replicates are wrongly handle.

The export to OpenMS with technical replicates is wrongly handled.

https://github.com/multiomics/multiomics-configs/blob/master/datasets/cancer-celllines-samples/sample-specific/PXD012255-Sample-1.tsv

Error in the pipeline:
File '/homes/yperez/.OpenMS/OpenMS.ini' is deprecated.
Updating missing/wrong entries in '/homes/yperez/.OpenMS/OpenMS.ini' with defaults!
Default-Parameter 'temp_dir' overridden: '' --> '/hps/nobackup2/proteomics/yperez_temp/temp/'!
 I think there was an error in the SDRF?


The generator_volto default shows last alpha

It should be aware that a stable version above it is available. npm does it.

I've been investigating, Volto npm registry API call returns:
    "dist-tags": {
        "latest": "16.2.0",
        "alpha": "16.0.0-alpha.53",
        "rc": "16.0.0-rc.3"
    },

and generator-volto returns:
    "dist-tags": {
        "alpha": "6.0.0-alpha.4",
        "latest": "6.1.1"
    },

Could be that the key order is not maintained...


[WIP] Adds a type-safe StateMachine builder to be used for life cycles.

Adds a declarative type-safe StateMachine immutable builder DSL to be used for life cycles. This is inspired by various frameworks I've used before in games and protocols (e.g. Fettle).
Each state may have onEntry, onExit, onError handlers attached, as well as  event->newstate transition mappings.
All legal states are defined, as well as event-driven transitions, with attached event and error handlers, in the DSL.
a PlantUML or GraphViz dump of the structure can be obtained.
The machine uses an internal queue to manage any events triggered by handlers. A sample implementation of AbstractArcHost.performParticleLifecycle() has been ported.
I'm still working on how the queue will be processed or drained, and whether I'll use another thread (e.g. like a browser microtasks queue). Additionally, its currently not thread safe (no mutexes around the mutate state field or eventQueue)
Comments welcome.

Added Mick as a replacement reviewer, since he's been working on the particle lifecycle a lot.
I like the idea of having a proper reusable state machine implementation, though to be honest I'm not completely sold on the DSL aspect of it, it seems like it might be harder to read and debug.

I'm still working on how the queue will be processed or drained, and whether I'll use another thread (e.g. like a browser microtasks queue). Additionally, its currently not thread safe (no mutexes around the mutate state field or eventQueue)

I think it's ok leaving this single threaded, without mutexes and without a separate processing thread. That seems simpler, and fits better with our proposed threading model going forward.

This seems very cool, I'm curious why so many of the methods are suspending functions though? What reason do they need to suspend? (KDoc explaining under what scenarios they suspend execution would be awesome)

I tend to agree with Cameron; not sure about the DSL approach. I'm also not sure about how the events fit in. For example: in ParticleStateMachine, a CreateEvent is triggered that doesn't appear to do anything and the process for MaxFailedEvent seems a little convoluted.

I like the idea of having a proper reusable state machine implementation, though to be honest I'm not completely sold on the DSL aspect of it, it seems like it might be harder to read and debug.

The DSL idiom is a standard Kotlin idiom for doing this (https://kotlinlang.org/docs/reference/type-safe-builders.html)
You can see Tinder is doing a similar technique here (https://github.com/Tinder/Scarlet/blob/5457f827884269a7e1a7c1c60d057d0ed5fa26b1/scarlet/src/main/java/com/tinder/scarlet/internal/connection/Connection.kt)
Or a similar pattern in Haskell (https://wickstrom.tech/finite-state-machines/2017/11/10/finite-state-machines-part-1-modeling-with-haskell.html)
The alternative is the boilerplatey Java approach used in Fettle, e.g.
val stateMachine.newBuilder().addState(Foo).onEntry(...).addTransition(...).build()

I'd argue laying out the states and events -> transitions helps readability once you get used to it.

I tend to agree with Cameron; not sure about the DSL approach. I'm also not sure about how the events fit in. For example: in ParticleStateMachine, a CreateEvent is triggered that doesn't appear to do anything and the process for MaxFailedEvent seems a little convoluted.

It's an omission. 'CreateEvent' is supposed to have a on(CreateEvent, Created) that creates a valid transition edge from Instantiated -> Created state, after onCreate() is called. 'Created'
The reason it uses an exception is because the current implementation is that onError() clears pending transition events. The exception could be removed just by adding a 'clearPendingEvents()' call and then transitioning to the MaxFailed state.
Basically, code needs to be able to short-circuit a sequence of transitions if an error occurs.

This seems very cool, I'm curious why so many of the methods are suspending functions though? What reason do they need to suspend? (KDoc explaining under what scenarios they suspend execution would be awesome)

Mostly laziness.

This seems very cool, I'm curious why so many of the methods are suspending functions though? What reason do they need to suspend? (KDoc explaining under what scenarios they suspend execution would be awesome)

Mostly laziness.

Actually, I believe if I use inline functions, I might be able to have my cake and eat it too, by letting you use either? (similar to the way many Kotlin stdlib inline functions on collections work?)

The DSL idiom is a standard Kotlin idiom for doing this (https://kotlinlang.org/docs/reference/type-safe-builders.html)

Fair enough. Definitely better than the boilerplate.

I'd argue laying out the states and events -> transitions helps readability once you get used to it.

Yes, that's probably true.

This seems very cool, I'm curious why so many of the methods are suspending functions though? What reason do they need to suspend? (KDoc explaining under what scenarios they suspend execution would be awesome)

Mostly laziness.

Actually, I believe if I use inline functions, I might be able to have my cake and eat it too, by letting you use either? (similar to the way many Kotlin stdlib inline functions on collections work?)

That could work!


Broken SVG link

Fixing broken SVG link

I signed it!

LGTM, thanks!

Yeah, this isn't rendered. It should point to the "normal" github URI
On Tue, Jun 19, 2018 at 5:21 AM Patrice Chalin<EMAIL_ADDRESS>wrote:

@chalin commented on this pull request.
In angular/README.md
https://github.com/dart-lang/angular/pull/1424#discussion_r196399646:

@@ -68,7 +68,7 @@ a set of [community contributed tutorials][comm].

Community/support:
mailing list,
Gitter chat room

Logo (SVG)

Actually, come to think of it, rather than a link to
raw.githubusercontent.com, this should probably link to the repo instead:
e.g., https://github.com/dart-lang/logos/tree/master/angular. In that
way, the developer will have the choice of format. @kevmoo
https://github.com/kevmoo - WDYT? /cc @kwalrath
https://github.com/kwalrath
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/angular/pull/1424#pullrequestreview-129942367,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCigbGTIyjddWnUG0QwL-TrKa8oXv4ks5t-OywgaJpZM4UtYdP
.

So should I point it to the repo as @chalin suggested?
https://github.com/dart-lang/logos/tree/master/angular/
or just the renderable version?
https://github.com/dart-lang/logos/blob/master/angular/logo/default.svg

The repo link looks good to me!
On Wed, Jun 20, 2018 at 4:08 AM Leonardo Lima<EMAIL_ADDRESS>wrote:

So should I point it to the repo as @chalin https://github.com/chalin
suggested?
https://github.com/dart-lang/logos/tree/master/angular/
or just the renderable version?
https://github.com/dart-lang/logos/blob/master/angular/logo/default.svg
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/angular/pull/1424#issuecomment-398712041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCijK_4F7M09lBVQ0sGwPVmIBDHQ0Sks5t-i0dgaJpZM4UtYdP
.

Thanks for the PR! I'm in the process of merging!


No throttling of message sending

Neither client nor server support flow control when sending messages (they do request
messages, so will interoperate with other servers and clients). This is because they
do not check call.isReady, or set the onReady handler.
Without this, the code which generates messages will not be throttled, and the code may
OOM in some situations.

Fixed by @timbertson in https://github.com/typelevel/fs2-grpc/pull/552 https://github.com/typelevel/fs2-grpc/pull/553


[Minimap Icon] Supernova Solrock has a massive mini-map icon

Describe the bug
Supernova Solrock has a massive mini-map icon that is many times larger than the icons for other mons.
To Reproduce
Steps to reproduce the behavior:

Find a Supernova Solrock
Look at the minimap

Expected behavior
Expected the icon to be normal size.
Scree

nshots
Username:
Dracten
Server name (all applicable):
Titan

An add-on to this. The sprite is off-center in the party roster

.

Updated to include Tidal Lunatone for same issue.

Since the original posting of this issue it has been resolved with the 1.1.1 resource pack. This issue can be closed at this time.


Shell test infrastructure

Description of changes:
Provides support for writing integration tests of predictors and estimators working within workflow of a SageMaker shell, as well as a test module that uses a dummy MeanPredictor in order to tests the shell itself.
I tried to split this readable commits, but the main point of the PR is the third one (i.e., the test_shell test module and the utility functions in the shell.testutil module).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-224/2 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/2/index.html

Job PR-224/3 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/3/index.html

Job PR-224/4 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/4/index.html

Job PR-224/5 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/5/index.html

Job PR-224/6 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/6/index.html

Codecov Report

Merging #224 into master will increase coverage by 1.6%.
The diff coverage is 84.82%.

@@            Coverage Diff            @@
##           master     #224     +/-   ##
=========================================
+ Coverage   79.77%   81.37%   +1.6%
=========================================
  Files         129      130      +1
  Lines        7277     7376     +99
=========================================
+ Hits         5805     6002    +197
+ Misses       1472     1374     -98

Impacted Files
Coverage Δ

src/gluonts/model/testutil.py
100% <100%> (ø)
:arrow_up:

src/gluonts/dataset/repository/datasets.py
75% <100%> (+17.85%)
:arrow_up:

src/gluonts/shell/__main__.py
47.16% <25%> (+1.01%)
:arrow_up:

src/gluonts/shell/serve.py
78.83% <79.48%> (+35.43%)
:arrow_up:

src/gluonts/shell/testutil.py
89.09% <89.09%> (ø)

src/gluonts/model/predictor.py
82.16% <0%> (+0.34%)
:arrow_up:

src/gluonts/transform.py
83.4% <0%> (+0.63%)
:arrow_up:

src/gluonts/core/component.py
88.27% <0%> (+0.68%)
:arrow_up:

... and 4 more

Job PR-224/7 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/7/index.html

Job PR-224/8 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/8/index.html

Job PR-224/10 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-224/10/index.html


Link styling in Contributor component

Problem to be solved
The embedded links in the Contributor component have missed out the hover state. Is this a new style, or has it been overlooked?
https://wellcomecollection.org/articles/W7TfGRAAAP5F0eKS

To do

[ ] Decide on link style to use
[ ] Add a sample link to contributor component in Cardigan

@jennpb This link style has been defined and is currently used in all components other than body content (e.g. breadcrumb, header in stories landing, info box). The link is displayed in black with underline then changes to teal with no underline on hover.
Default state

Hover state

Yes, but the hover state is not working on the contributor component.

The hover state colour is defined through #3634


include gcp-api tests in the pipeline

:nut_and_bolt: Description
trying this again 😺
i think this will work now. it works locally.
:+1: Definition of Done
gcp tests running in pipeline
:chains: Related Resources
https://github.com/chef/automate/issues/76

From the error it looks like the vault-secret isn't really base64-encoded, but plain JSON (with a space in it):

hab-studio: Running 'source scripts/verify_studio_init.sh &&
--
  | start_deployment_service &&
  | chef-automate dev deploy-some chef/compliance-service --with-deps &&
  | nodemanager_scans_integration' in Studio at /hab/studios/go--src--github.com--chef--automate (default)
  | /hab/pkgs/core/coreutils/8.30/20190115012313/bin/env: ‘"type":’: No such file or directory

i've reached out to releng to see about getting the google creds uploaded as base64 encoded, since this is the same workaround used in https://github.com/chef/automate/pull/1066

hmmm, so i heard back from releng: we can't base64 that value as it is dynamically generated by Vault on the fly
so back to the drawing board...maybe i can figure out how to grab that value once generated and base64 it before it gets to the studio entrypoint?

@vjeffrey Maybe in the job definition here, you could add a step that pre-processes whatever is stored in HAB_STUDIO_SECRET_GOOGLE_CREDS_JSON? Like,
export HAB_STUDIO_SECRET_GOOGLE_CREDS_JSON=$(base64 <<<"$HAB_STUDIO_SECRET_GOOGLE_CREDS_JSON")

⚠ Haven't tried this.

Chef Habitat is already up-to-date
--
  | panic: Error making API request.
  |
  | URL: GET https://vault.chef.co:8200/v1/account/dynamic/gcp/buildkite-ci/key/service-account
  | Code: 400. Errors:
  |
  | * googleapi: Error 429: Maximum number of keys on account reached., rateLimitExceeded
  |
  | goroutine 1 [running]:
  | github.com/chef/ci-studio-common/lib.Check(...)
  | /Users/tom/code/chef/ci-studio-common/lib/utils.go:11
  | github.com/chef/ci-studio-common/vault-util/cmd.fetchSecret(0xc0001226c0, 0xc00000e018, 0x982bfe)
  | /Users/tom/code/chef/ci-studio-common/vault-util/cmd/fetch-secret-env.go:87 +0x425
  | github.com/chef/ci-studio-common/vault-util/cmd.printSecrets(0xdc2680, 0xde8c00, 0x0, 0x0)
  | /Users/tom/code/chef/ci-studio-common/vault-util/cmd/fetch-secret-env.go:51 +0x177
  | github.com/spf13/cobra.(*Command).execute(0xdc2680, 0xde8c00, 0x0, 0x0, 0xdc2680, 0xde8c00)
  | /Users/tom/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:830 +0x2ae
  | github.com/spf13/cobra.(*Command).ExecuteC(0xdc2b80, 0x0, 0x0, 0x87f913)
  | /Users/tom/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914 +0x2fc
  | github.com/spf13/cobra.(*Command).Execute(...)
  | /Users/tom/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
  | github.com/chef/ci-studio-common/vault-util/cmd.Execute()
  | /Users/tom/code/chef/ci-studio-common/vault-util/cmd/root.go:27 +0x2e
  | main.main()
  | /Users/tom/code/chef/ci-studio-common/vault-util/main.go:8 +0x20

i'll give it a rerun later on

closing this til i get the account discrepancies figured out


Add docblocks on a few objects

Signed-off-by: Randy Barlow<EMAIL_ADDRESS>

I think #99 might replace this?


Add a new Location type

Just the data type, to/from Text functions and some tests.
! @jystic @nhibberd @olorin

LGTM. 👍

DItching this in favor of adding commands:
s3 download -r s3://path dir
s3 upload -r dir s3://path

as suggested by @jystic


Can't parse TIP v0.3

Apparently, the TIP language has incorporated SMT-LIB 2.6 changes (https://github.com/tip-org/tools/commit/2995668c6e0d3fb68ec71a494992f74f3c96b877) and is therefore no longer compatible with zipperposition's current parser:
$ zipperposition benchmarks/tip2015/list_elem_map.smt2
parse error at at file 'benchmarks/tip2015/list_elem_map.smt2': line 1, col 1 to 17:
expected statement

Since BNFC claims to be able to output Menhir files and the lbnf file is available, I suppose it would be little effort to update the parser, although I don't know anything about menhir and the way its output is used in zipperposition (otherwise I would've made a quick PR myself). Do you think this is feasible?
To give a little background: I'd like to add TIP support to Hets (https://github.com/spechub/Hets/issues/1502) to enable it to eventually talk to several induction-capable provers with relatively little translation effort of its own, using the TIP-provided tools instead. I plan on testing the implementation by connecting a prover that already talks TIP natively (e.g. zipperposition). Since the generated TIP should eventually be fed into TIP's (up-to-date) translator, I want to avoid implementing an old version of the language if possible.

Depending on how complicated the changes are, you might have an easier time just adapting the current parser to follow TIP 3. It's nice that they got closer to smtlib, I must say.
I don't have any time to work on this personally, though.

I've adapted the grammar and pushed it directly to master. I've tried a couple of problems from the TIP library and they can be parsed now. Let me know if you find any issues that I've missed.
The example list_elem_map.smt2 you mention above still throws an error, but at least it can be parsed now.

Thank you very much for the swift responses and the quick implementation!
Regarding issues, the following archive contains all the files from tip-benchmarks-0.3 that still throw parse errors, accompanied by zipperposition's respective outputs describing the error: parse_errors.tar.gz
In every single case, zipperposition's parser apparently expected term, while tip has no problems reading (and translating) them.
Furthermore, here is an archive of all the files that throw the same error you noticed with list_elem_map.smt2, again accompanied by the output:
ApplyError.tar.gz
Interestingly, tip has problems converting most of these to Isabelle format, except for list_elem_map.smt2 (and list_nat_elem_map.smt2).
Once again, thank you for your help!

I've fixed the parsing issue and pushed it to master.
The ApplyError is more difficult to fix. The issue is a clash of variable names in the induction module and I am not sure how the induction module works at all. It seems that all the variables of a form in Test_prop.ml are supposed to live in the same namespace. But then, via Libzipperposition.Cut_form.normalize_form, RW.Lit.normalize_clause is called, and it may rename variables in a single clause of a form, which can then cause variable name clashes.
A workaround would be to replace let cs = c |> rw_terms |> rw_clause |> rm_trivial in by let cs = c |> rw_terms |> (fun c -> [c]) |> rm_trivial in in Cut_form.ml. This prevents the error, but probably takes out some important functionality from the induction module.


How to use fake ban?

idk how to use fake ban, so i just changed name to fake name..
Or it's really fake name??

idk how to use fake ban, so i just changed name to fake name..
Or it's really fake name??

I'm not sure it actually works, haven't tried it since I got banned in like 5 minutes while only using walls and esp.

I am pretty sure you just press setup ban and then leave the match. and in chat instead of saying "xxx has disconnected" it will say "xxx has been permanently banned from Official CSGO Servers" or something like that. And it will also be red text, just like an actual perm ban.

i'll test it tomorrow, with my friend.
thx for help :)

i'll test it tomorrow, with my friend.
thx for help :)

Best of luck. 👍

How to restore my changed nickname?
my nickname is blank in game chat and it easily get overwatch ban, i think.

How to restore my changed nickname?
my nickname is blank in game chat and it easily get overwatch ban, i think.
Automatically restore after disconnected? or can I use some code?

I think it should change back when you join back to the game.
And no, I have completed over 400 overwatch cases and there's no indication of what anyone's name is. In overwatch we don't get any information about the suspect. So you're fine.

again, thanks for help.

When you disconnect writes Player xxx [fake ban] [reason of disconnecting]


pricecheck lets the bot die

hey
i updated the bot to the newest version, but somehow, if I start for example !jita Paladin the bot will die and be restarted.

Ok correction: It can also happen if other commands come up. I don't know where to look, the error Logfile doesn't show anything useful.

Not able to reproduce it (every once in awhile get an xml error but that's ccp issues). Can you double check the logs?
And also check your servers memory usage and let me know how much free memory you have.

i have more than 3.5GB mem available
it's a bit strange, that the pluginloading is running every like 10 seconds:

[2016-09-11 21:17:44] Dramiel.INFO: Checking authed users for changes.... [] []
[2016-09-11 21:17:45] Dramiel.INFO: Logger Initiated [] []
[2016-09-11 21:17:45] Dramiel.INFO: CCP Database already up to date [] []
[2016-09-11 21:17:45] Dramiel.INFO: Loading background plugins [] []
[2016-09-11 21:17:45] Dramiel.INFO: Loaded: 3 background plugins [] []
[2016-09-11 21:17:45] Dramiel.INFO: Loading in chat plugins [] []
[2016-09-11 21:17:45] Dramiel.INFO: Loaded: 10 chat plugins [] []
[2016-09-11 21:17:46] Dramiel.INFO: Discord WebSocket is ready!  [] []
[2016-09-11 21:17:51] Dramiel.INFO: Checking authed users for changes.... [] []
[2016-09-11 21:17:52] Dramiel.INFO: Logger Initiated [] []
[2016-09-11 21:17:52] Dramiel.INFO: CCP Database already up to date [] []
[2016-09-11 21:17:52] Dramiel.INFO: Loading background plugins [] []
[2016-09-11 21:17:52] Dramiel.INFO: Loaded: 3 background plugins [] []
[2016-09-11 21:17:52] Dramiel.INFO: Loading in chat plugins [] []
[2016-09-11 21:17:52] Dramiel.INFO: Loaded: 10 chat plugins [] []
[2016-09-11 21:17:53] Dramiel.INFO: Discord WebSocket is ready!  [] []
[2016-09-11 21:17:58] Dramiel.INFO: Checking authed users for changes.... [] []
[2016-09-11 21:17:59] Dramiel.INFO: Logger Initiated []

should this be normal?
ErrorLog just shows me some failures in the authCheck.php:

PHP Fatal error:  Call to a member function get() on null in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160
PHP Notice:  Trying to get property of non-object in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 125
PHP Warning:  Invalid argument supplied for foreach() in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 125
PHP Notice:  Trying to get property of non-object in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160
PHP Fatal error:  Call to a member function get() on null in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160
PHP Notice:  Trying to get property of non-object in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 125
PHP Warning:  Invalid argument supplied for foreach() in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 125
PHP Notice:  Trying to get property of non-object in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160
PHP Fatal error:  Call to a member function get() on null in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160
PHP Notice:  Trying to get property of non-object in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 125
PHP Warning:  Invalid argument supplied for foreach() in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 125
PHP Notice:  Trying to get property of non-object in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160
PHP Fatal error:  Call to a member function get() on null in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160

the "OtherLog" also did not show any suspicious behaviour...

The issue is
PHP Fatal error: Call to a member function get() on null in /var/discord/Dramiel/src/plugins/onTick/authCheck.php on line 160
fatal errors = a bot crash. I'll look into it and push out a fix, gimme a few minutes

It shouldn't crash if you do a pull now.. BUT it will probably throw an error in the log now. I'm guessing you have the wrong guildID in your config.. The first section of the config where it says guild, you need to put the ID of your guild (server) there.

works like a charm now, thx a lot


added prop rotateAngle to avoid the overlapping  x-axis tick values

Summary

What was changed:
added new prop called rotateAngle to avoid the x-axis overlapping tick values.
with prop rotateAngle: -45

with prop rotateAngle: 40

Why it was changed:
Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-XXXX

Thank you for contributing to Terra.
@cerner/terra

The tick values now overlap with the axis label. I think we'll need to dynamically adjust the padding of the axis label to account for the change in height.

Questions about cases:

What happens when the prop is not an integer (string, bool, float etc) ?
What happens when the values exceeds +/- 90º ?
Is unit of the angle only in degrees? What about radians?

We should add validation for the datatype in this function:
https://github.com/cerner/terra-graphs/blob/722464a8ce33888dcaeedf24a277c8f234230f76/packages/carbon-graphs/src/js/controls/Graph/Graph.js#L115

Worked with Uday to fine tune the padding between the tick labels and axis labels. Here is a screenshot of the result

We also ensured the legend still had appropriate padding. After these changes, this looks good to me!


use/reference official angular bootstrap bower dependency

Hi I had a problem since the anagular-advance-searchbox is referencing a pretty old version of angulat-bootstrap, which is anyway not referencing the official bower repository  (https://github.com/angular-ui/bootstrap-bower)
Instead of using the dependency "angular-bootstrap" it should be using angular-ui-bootstrap-bower"

Hi, it is using the correct repository, see here: https://github.com/angular-ui/bootstrap#install-with-bower
And yes i'll update to a newer version.

yeah you are right, now I know the reason: http://stackoverflow.com/a/22180864/4604872
I created the original project in January 2015 (at that time angular-ui-bootstrap-bower was the right dependency) , but Feb 2015 they did changes and some fix, and now its possible to use it like you mentioned.

Can we close this issue then? Currently i'm using a pre 0.14 version because they renamed all directives with a uib- prefix.
I think i'll update to 0.14+ in the beginning of the next year.

Lets just rename it ;)

+1


Header fixes, Title fixes, changes for md: to sm:

Summary
Fixed Header Part for mobile screen and other CSS changes
Description
CSS changes to fix Mobile and Tablet devices. Used Tailwind CSS to add mobile and tablet compatibility. Continued the changes for Issues #13
Creating a issue for refactoring of all the md: to sm:
Images

Issue(s) Addressed
Enter the issue number of the bug(s) that this PR fixes
Closes Issue #13
Prerequisites

[x] Have you followed all the CONTRIBUTING GUIDELINES?

@krishnaacharyaa apologies for the delay, I have addressed the PR comments. Please let me know if there's any other changes that needs to be taken care of!

@Deblin798, the skeleton for both cards looks out of sync to me, please look into that.

featured-post skeleton it should have only those many fields as the real post has. it currently has more than that
post-card it is not aligned in terms of height and width and also the no of components within the post card,

If you have any query regarding this, feel free to ask

Hi @krishnaacharyaa made the necessary changes and addressed the issues. Please have a look!

Hi @krishnaacharyaa made the necessary changes and addressed the issues. Please have a look!

Thank you for the changes @Deblin798, Please follow contributing guidelines as it helps us keep track of the project history, please change the PR title according to the 3rd guideline https://github.com/krishnaacharyaa/wanderlust/blob/c3b11e57fa35786358d6c373911109fe03116bbf/.github/CONTRIBUTING.md

@krishnaacharyaa made changes to a few titles, descriptions, padding, text sizes, which include a few specific to mobile devices and a few to desktop site as well. Please have a look!


Quick layout selection from keyboard

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
After using a hotkey to open the layout picker I would like to continue using the keyboard to select the new layout and confirm.
Level 1: Arrow keys
Directly use arrow keys to move the current selection.
I noticed there are some control you can do by keyboard but.

You must first tab to the right area
Using arrows not only jumps between selectable layouts but also other elements such as edit layout and add new layout, the jumps is also not consistent: (Right arrow select next layout, right arrow selects that layouts edit button, left button doesn't go back to that layout but instead the previous layout.

Level 2: Quick search
After pressing the hotkey for layout selection the next keypresses should be added to a quick search.

Press layout hotkey
Press the first letters in the layout name (the best match is highlighted)
Press enter to confirm and close.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

this is work we have to be extremely careful with since it becomes an accessibly issue for keyboard navigation
In 0.35, we did add in the hot swap layout feature so we do have some level of quick keyboard swapping

I see my level 1 suggestion would conflict with expectations of the current one.
Level 2 could work assuming keys a-z ans 0-9 is not planned for other navigation or operations(for example press e to edit selected layout).
The "hot swap"/"Quick layout switch" does most needs otherwise.

@hultqvist #11066 solves a lot of keyboard navigation issues. It's now inline with Windows keyboard navigation standards (using Tab to navigate between monitor - layouts - create new layout button, and arrow key navigation to navigate within the GridViews). Shift + F10 can be used to bring up the right-click context menu to e.g. delete an item.


LuaActor::new_with_vm and related changes

Alternative solution for https://github.com/poga/actix-lua/issues/18 discussed in the comments

I think github is half broken, I pushed the test commit 3 hours ago and the pull request hasn't updated (also the commit only appeared in github more than an hour after I pushed it)

I think github is half broken, I pushed the test commit 3 hours ago and the pull request hasn't updated (also the commit only appeared in github more than an hour after I pushed it)

I think github is half broken, I pushed the test commit 5 hours ago and the pull request hasn't updated (also the commit only appeared in github more than an hour after I pushed it)

merged and released 0.5.0 🎉
Also, please ignore my review. I completely misread the code (I blame the github preview :p ).


Create OBO file from ONS

Moved from:
ONS owl violates the OBO profile (multiple labels/comments etc):
OBO STRUCTURE ERROR Ontology does not conform to OBO structure rules:
multiple name tags not allowed. in frame:Frame(ONS:0000101 id( ONS:0000101)comment( Should break the definition down into separate terms, e.g. bioaccessable should be defined separately.)property_value( IAO:0000117 ENPADASI_WP4 xsd:string)name( food digestion)name( Food digestion)def( Digestion is the breakdown of large food molecules into small water-soluble food molecules. The breakdown is both mechanical and chemical (enzymatic digestion). During digestion, food components are released from the food matrix and may become bioaccessible.)def( Digestion is the breakdown of large insoluble food molecules into small water-soluble food molecules. The breakdown is both mechanical and chemical (enzymatic digestion). During digestion, food components are released from the food matrix and become bioaccessible. Bioaccessible molecules can be absorbed.)is_a( GO:0008150))

@FrancescoVit you can use
 robot convert -I https://raw.githubusercontent.com/enpadasi/Ontology-for-Nutritional-Studies/master/src/ontology/ons_release_v1.2.owl -f obo --check false -o ons_release_v1.2.obo

to circumvent the issue (--check false). This produces slightly dodgy OBO, but we all do it, all the time.
This particular error, by the way, should be fixed: you should never use multiple labels on a class. Use
 robot report -I https://raw.githubusercontent.com/enpadasi/Ontology-for-Nutritional-Studies/master/src/ontology/ons_release_v1.2.owl -o report.txt

To identify such issues!

I think related to this is that ONS needs a root ons.owl file.  Francesco, we could have a short call to finalize that. At moment OntoBee and OLS have old content for this ontology as a result of the current way of handling versions.

I am going over the multiple_definition and multiple_label ONS classes, and noted that in some cases the error raises from having specified a language tag, see example attached

Here we have two textual definition as one is "general" and implicitly in English language (defaultLanguage in ontology header section), while in an additional definition we specified the @en language tag. The same for the labels.
In this case I could easily remove the non langage tagged definition or label, but how to formally deal with it if I am to include other languages labels as well? All in all, I sort of think that this should not be a formal error

Indeed, take out the labels and definitions that don't have a language tag.
Now, as I recall some OBO validation tool may not accept multiple definitions that DO have other language tags besides english.  As a workaround until they do (they should at some point to get multilingual IMHO!) one could separate out the other language content into a separate import file, and just keep that disconnected and added by users when they want that multilingual capability for their applications.

Language tag removed, this specific issue is solved. Closing and referring to #15 for the new issue on general duplicated annotations


babeltrace: fix cross-compilation

Description of changes
Note: glib cross-compilation is at present broken on master. I've done my testing with e9c35f11 cherry-picked.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Thanks!


Enhance readability of URL parameters

Use params argument in requests.get() to provide parameters.
Improves readability.

Yeah, that does look better. Thanks!


kando: Add version 1.1.0

Closes #13365

[x] I have read the Contributing Guide.

/verify

Please fix validation issue(s) and follow the order of fields as per Contributing Guide.

Sorry for this newline stuff. VSCode keeps deleting it...

/verify

@aliesbelik Kando stores all data in the %APPDATA%\Kando folder. Should I add this information to notes like in Kanri?

/verify


Transfer ownership of repo

This repo appears to be unmaintained. Please transfer ownership to someone who will maintain it & accept pull requests: I'll volunteer @polleverywhere, but @cowboyd would be a good choice as well.

Alternately, you can transfer bazaar to me and I'll do the deprecation myself. I'm not interested in maintaining bazaar as-is, because I believe random_username is a superior project now.


rpi-clone stops working

I wanted to clone Ubuntu Mate x86 v. 20.04 LTS from SD card to USB SSD attached as sda.
Unfortunately, the cloning process freezes after second rsync.

Please help.

I've got the same issue here on ubuntu 22.04.1 on a Raspberry Pi 4.
I can let the clone running for 24h and it's still blocked with this message.
J've activated the verbose mode to check what was going one and it seems that the rsync is properly performed but then nothing more is happening.


Add SetGlossary event

Adds a new event that allows changing a glossary variable during the game. The only unfinished thing is that there is no event-icon!

This should fix #191


[AutoPR cognitiveservices/data-plane/Face] [FaceAPI] Update output folder of FaceAPI dotNet SDK

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6279

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/3618


Support multiple children props

There is currently no way to support multiple children, as in this example from the React docs: https://reactjs.org/docs/composition-vs-inheritance.html
function Dialog(props) {
  return (
    <FancyBorder color="blue">

        {props.title}

        {props.message}

    </FancyBorder>
  );
}

function WelcomeDialog() {
  return (
    <Dialog
      title="Welcome"
      message="Thank you for visiting our spacecraft!" />
  );
}

fiddle link
This fiddle does output the correct code for React, but almost all other frameworks need explicit new logic to handle multiple slots/pieces of content.

I think to support this we will need to have a first class feature in Mitosis around Slots. Since React is more flexible as to what you can do compared to other frameworks, we'll need to design an implementation in Mitosis that is easy to use and can support all of our output targets, even the most constraining of them. tmk slot, like used in most non-react frameworks, is the most common convention and is the most consistent across
may be a good one to do an RFC for


chore: fix warning on windows

This use was unused.

This patch has been manually integrated into mainline. Therefore, I am closing this PR.


Tasks that are waiting on locks are reporting as RUNNING

"status":"RUNNING"

If a task is waiting on a lock, it still reports as RUNNING. when querying the tasks /status endpoint.

This is "intended" in that tasks have a lifecycle that goes RUNNING -> SUCCESS/FAILED. There is no such thing as a "pending" or "waiting" status. We could change that if we want, but that is why things are the way they are.

@gianm I believe this has been greatly improved and is no longer and issue. I see pending tasks all the time now.

Can this be closed?

Ah yes. Now they are "WAITING" if they are waiting on locks.