Initial support for Microsoft.Data.Sqlite

see issue #359

Looks ok. Were you able to run the full test suite against it?

I haven't tried to run the test suite yet. But I will try that...

I couldn't get the tests to run..... I compiled the whole solution but I didn't find a way to run the tests...

The tests run as a console application. You just need to adjust the config.

howd u go with this?

I'm very busy with getting out a first version of our product for market trial. We discarded SqLite support for this first version. I will look into this once I have some more resources available...

--- "a/NPoco\\src\\NPoco\\MappingFactory.cs"
+++ "b/NPoco\\src\\NPoco\\MappingFactory.cs"
@@ -28,11 +28,13 @@ public MappingFactory(PocoData pocoData, DbDataReader dataReader)
         {
             _pocoData = pocoData;
             _rowMapper = RowMappers.Select(mapper => mapper()).First(x => x.ShouldMap(pocoData));
-            _rowMapper.Init(dataReader, pocoData);
         }

         public object Map(DbDataReader dataReader, object instance)
         {
+            //re-init mapper for every row https://github.com/aspnet/Microsoft.Data.Sqlite/issues/300
+            //null gets mapped to Int32, in a later row it receives Int64 (INTEGER) and can't convert
+            _rowMapper.Init(dataReader, _pocoData);
             return _rowMapper.Map(dataReader, new RowMapperContext()
             {
                 Instance = instance,

This patch should allow the tests to run (I haven't tried, because I haven't found the time yet to rewrite the SQL). I don't know how this would affect performance.

Any update on this?

Actually I recently made an attempt to make the test suite work for my pull request. I expected that I only need to slightly modify the tests for the existing System.Data.Sqlite provider.
But I realized that the test suite is far from being usable with the existing System.Data.Sqlite either - looks like there is quite some work to be done for both System.Data.Sqlite and Microsoft.Data.Sqlite (regarding testing). I'll absolutely need Sqlite support in the longer term, so at some point I'll be forced to look into this in more detail. But I'm too busy with other stuff at the moment.

Updating to Microsoft.Data.Sqlite version 2.0.0 fixed the "The IsolationLevel 'ReadCommitted' is invalid." error for me.

This really needs to be rebased before review.


“createdTime” Is Returned Null When Using Publisher Rest API

Description:
When using the publisher Rest API to get API information, using the following Rest API call, the createdTime attribute is returned null, and lastUpdatedTime gets returned successfully.
https://<IP_ADDRESS>:9443/api/am/publisher/v1/apis?expand=true
Steps to reproduce:

Deploy a sample API.
Use the Publisher API [1] to retrieve API details.
Use the https://<IP_ADDRESS>:9443/api/am/publisher/v1/apis?expand=true operation with the 'expand' attribute set to 'true'.
Check for the 'createdTime' attribute in the response.

[1] https://apim.docs.wso2.com/en/3.2.0/develop/product-apis/publisher-apis/publisher-v1/publisher-v1/#tag/APIs/paths/~1apis/get
Affected Product Version:
WSO2AM-<IP_ADDRESS>

According to [1], the expand in Publisher V2 GET APIs resource has been deprecated from APIM 4.0.0 onwards. Hence, no need for the master fix.
https://apim.docs.wso2.com/en/latest/reference/product-apis/publisher-apis/publisher-v2/publisher-v2/#operation/getAllAPIs


Handle cell vars in closures and update m{in,ax} impls

This adds a patch to closure inlining that ostensibly handles
cell variables. This allows for inlining more arbitrary closures
during IR manipulations in the pipeline.
It also rewrites the argm{in,ax} and m{in,ax} to use this
functionality.

@ehsantn I'm not 100% sure of the validity of this change. I suspect more may need to be done as there's ir.Const containing builtins now, however, this seems to work but quite possibly for the wrong reasons!

Thanks for the PR. It looks plausible, but I wonder in what context does this tuple and cell_contents arise as closure environment? Why did Python behave like this when it already had a way using build_tuple?

@ninegua This is what I was puzzled over too and it was the root of my noted uncertainty, I also was wondering why this didn't go via the path you describe. I think it can be summarised as the difference between asking the inliner to inline an enclosing function and asking it to inline and instance of the enclosed function.
The reason I attempted this was to allow the type based specialisation of function to be determined at runtime and that specialised instance to be inlined thus avoiding using llvmlite and IR* etc. This patch basically patches the inliner to inline such a function, which in this case happens to be an instance of the inner most enclosed function, hence has cellvars for the freevars in __closure__. Whilst this is probably (almost definitely) an abuse of the inliner it makes me wonder if with a little more the inliner could be extended to inline pretty much anything (I actually played with this idea a while back during the time of the closures PR)? Would such a capacity make it possible to write functionality at a higher level with all the benefits associated with such implementations? Essentially, is this a good idea/would it be useful?!

@stuartarchibald Sorry for not getting back to this PR in time. It becomes outdated compared to current numba master. If you would still like to push this forward, please rebase and re-submit the PR, maybe against the core-pa branch, where our new code are going in. It would also be helpful to give a test case that this PR enables.


Anybody having luck fine tuning?

I'm using a clean 40hr dataset, female American, that I used on tacotron with good results. I've trained on VITS twice now and it starts over fitting around 70K. It's definitely intelligible and in the correct tone but the prosody is way off. First run had default configs. Second run I tried decreasing learning rate and lr decay. It helped some with overall loss, but still started overfitting around 70K.

When you say fine tuning, do you mean you're initializing the weights from the pretrained LJSpeech model, as opposed to training from scratch? I've trained on a ~15 hour single-speaker dataset from scratch and gotten good results 🙂 .
When you say it's overfitting, what do you mean exactly? That it's able to generate sentences in your training set well, but can't generate novel sentences with correct prosody? Or are you referring to the learning curves you're seeing?

I am using '!python train.py -c configs/ljs_base.json -m ljs_base' with a config file that points to my own datasets. So I assumed that was using the pretrained weights. How would I start from complete scratch?
To be clear, I'm getting decent results. But my model isn't nearly as natural as the examples, and that is the only thing I'm looking for right now. The total loss starts to level out and even increase after around 70k and the examples in the tensorboard start to sound slightly worse. I decided to just keep training and it does seem to oscillate from increasing slightly to decreasing, increasing slightly then decreasing. Overall I think it's decreasing very slowly still and I'm at 104k. I'll just keep running and see what happens.

Ah in that case what you're doing is training from scratch, rather than fine tuning. You'd have to download the pretrained models, but in fact I think only the generator is provided not the discriminator? So I'm not sure if the pretrained models linked are suitable for fine tuning?
Yes I think it's definitely worth continuing training, even if the loss seems to be plateauing. I believe the paper says the LJSpeech model was trained to 800k steps.

@alexpeattie  Could you share your tensorboard show loss images？After how many steps (G_*.pth) of training, the synthesized wavs is understandable  or of decent quality?
I tried to train the model using my own chinese datasets, but the training seems abnormal， and the synthesized wavs are bad.

Here you go:

It seems that the discriminator loss is improving steadily, while the mel loss is improving on the generator while other losses are climbing. However, generated samples seem to be getter slightly better.
The synthesized sound very good in terms of spectrogram inversion from only a few 10k steps (e.g. no tininess/reverb/warbling). And the prosody seems to be getting better as the training goes on. But for me by 180k it was already sounding better than Tacotron, so I suspect something might have gone wrong with your training.

@alexpeattie Thank you very much for you reply. I also guess maybe I make mistake in some steps. I will try to figure it out. Your tensorboard are very good references!

Can someone explain why all these losses are going up? My graphs look similar.

Here you go:

It seems that the discriminator loss is improving steadily, while the mel loss is improving on the generator while other losses are climbing. However, generated samples seem to be getting slightly better.
The synthesized sound very good in terms of spectrogram inversion from only a few 10k steps (e.g. no tininess/reverb/warbling). And the prosody seems to be getting better as the training goes on. But for me by 180k it was already sounding better than Tacotron, so I suspect something might have gone wrong with your training.

The discriminator becomes better through training. In other words, the discriminator can correctly classify generated samples as false, so the g_losss increase and these losses is backforward to force generator to generate more realistic samples.

I understand what you're saying in theory, but wouldn't the generator then become better in generating with the improvement of the discriminator, resulting in smaller generation loss?
This is my first time training a GAN. I'm not saying I'm right, I'm just saying t seems counterintuitive that the losses are designed in a way that total loss is going up but the model is continuing to improve.
I'm at 180K now and I guess it sounds a bit better than 80K, but probably not by much. Total loss has been increasing slightly or remaining constant since about 80K. But mel and dur and d_total losses are still decreasing. Maybe these are a better indicator of improvement. I'm just going to keep going.

@TaoTeCha
https://github.com/jaywalnut310/vits/blob/2e561ba58618d021b5b8323d3765880f7e0ecfdb/losses.py#L25-L26
The GAN losses are MSE, so the total loss goes up when one is doing better than the other, despite the fact that their relative performance doesn't mean anything about the performance of the overall model.
I guess I'm just saying, ignore generation and discriminator losses. As long as they both are above 0 the model should still be improving.

@alexpeattie
Did you get an improvement from g/fm loss?

Hey @CookiePPP, sorry, I'm not 100% sure what you're asking? Do you mean did the g/fm loss improve as I continued training?

@alexpeattie
Ah sorry, ignore that

Well I ran to 300K and it sounds great. Definitely better in audio quality, prosody, and pronunciation than Tacotron2. Some issues with pronunciation or speed come up in some of the samples but overall it sounds awesome. I think part of the problem was that I was only listening to the example from the tensorboard for the higher checkpoints, which sounded a lot worse than anything I am hearing on inference. Don't base the model quality off of what you hear in the tensorboard.
And thanks @CookiePPP for the detailed response. You always show up out of nowhere to help those in need.

@alexpeattie  After I found and fixed mistakes in my code, trainning works fine, and the synthesized wavs are excellent!
Could you please help me figure out this problem?
https://github.com/jaywalnut310/vits/issues/13

@alexpeattie what hardware did you use? am trying to squeeze the model into 8GiB GPU, reduced some model parameters. but get negative loss value for duration predictor, tried to train as long as 200K,500K steps.

@CookiePPP I strongly agree with you on "I believe the other loss values are ones that matter e.g: dur, kl and mel should be going down in an improving model".
However, the training curves show that these discriminator independent losses (say kl  and fm) do not decrease along the training process. For me, it is indeed quite counter intuitive. Any deeper understanding for this? Thanks ahead

@Teddy-QU
loss/fm can be ignored as it's numerical value doesn't actually mean anything on it's own.
loss/kl is linked to loss/mel. Search up Autoencoders and VAEs if you're not familiar on the concept, but basically the model can trade between kl and mel loss as it trains (e.g: model can get better mel loss by increasing it's kl loss. The model has a natural balancing point but that might shift over training).
loss/kl going up isn't automatically bad, it's only bad if loss/mel increases at the same time.

So uh, summary of how to read the loss terms is as follows;

loss/g/mel and loss/kl should trend down. The model can trade between mel and kl so sometimes one will go up while the other goes down but overall they should be decreasing.
loss/g/dur should always go down.
any loss/d_g/{number} or loss/d_r/{number} should never hit 0.0 or get close to it (anything under 0.05 is probably a dead generator network). The actual value is not important.
any loss/g/{number} should never hit 0.0 or get close to it (anything under 0.05 is probably a dead discriminator network) The actual value is not important.
loss/fm doesn't really matter. In fact I'm not actually sure if it makes the finished model sound better 😅

@CookiePPP
Thanks for the awesome sharing.
I understand that the loss/kl and loss/mel contribute together to the evidence lower bound of VAE. The loss plot below indeed aligns with the trend.

Although loss/fm is designed to represent the reconstruction loss that
is measured in the hidden layers of the discriminator, given the adversarial training style, its value indeed lose its prectical meaning.

Hi everybody !
I have trained a Vietnamese female voice model in 500k steps. and I found the voice quite clear. I want to train another male Vietnamese voice.
I learned there is a training method based on a previously trained model, which will shorten the training time.
Can someone help me with that method.
Thank you !

I've created a repo to finetune VITS (and MMS, the multilingual Meta version of VITS) using Hugging Face implementation, feel free to take a look: https://github.com/ylacombe/finetune-hf-vits
You can try some finetuned models in this demo and in that one.


Expose demultiplexed boolean properties for DIO registers

[x] Proposed
[ ] Prototype: Not Started
[ ] Implementation: Not Started
[ ] Specification: Not Started

Summary
Use payloadSpec to represent DIO inputs. This would allow much easier selection of boolean flags directly as fields using a member selector, and also improve property grid experience when creating command message payloads.
Motivation
The current standard for representing DIO registers in the device.yml file is to define a custom bitmask enum type over the register number. For example:
  DigitalInputState:
    address: 32
    access: Event
    type: U8
    maskType: DigitalInputs
    description: Reflects the state of DI digital lines of each Port
...
  DigitalInputs:
    description: Specifies the state of port digital input lines.
    bits:
      DIPort0: 0x1
      DIPort1: 0x2
      DIPort2: 0x4
      DI3: 0x8

The above will be represented at the level of the high-level interface as a C# enum type with the [Flags] attribute. Values from flags can be hard to manipulate, requiring specialized operators to decode or encode the values (HasFlag). Even when using such operators, the chain of processing can be complex for something as simple as retrieving the timestamped events of when a single DI port changes value:

The ConvertTimestamped node is required in this case to make sure the timestamp is carried through the conversion operator with HasFlag which will be inside the group node to extract the single bit from the DIO bitmask state.
Detailed Design
In this proposal, representation of the same DIO register in the device.yml file would be:
  DigitalInputState:
    address: 32
    access: Event
    type: U8
    payloadSpec:
      DIPort0:
        mask: 0x1
        interfaceType: bool
      DIPort1:
        mask: 0x2
        interfaceType: bool
      DIPort2:
        mask: 0x4
        interfaceType: bool
      DI3:
        mask: 0x8
        interfaceType: bool
    description: Reflects the state of DI digital lines of each Port

With this specification for the register, the generator would create a DigitalInputStatePayload type with the following layout:
public struct DigitalInputStatePayload
{
    public bool DIPort0;
    public bool DIPort1;
    public bool DIPort2;
    public bool DI3;
}

This then becomes the output type of the Parse node, which means that individual bit flags can be selected with the right-click context menu. It also means that the CreateMessage operator for this register will expose these properties directly as fields in the grid, where it becomes easy to see and change which bits are being set or cleared.
The proposal requires no change in the current implementation of the standard, in so much as it is only a change in the way the existing standard is used to model specific types of registers.
Drawbacks
There are a few important reasons why we might not want to do this:

Several published devices exist which do not follow this proposal, which would mean either creating conflicting and possibly confusing ways of using different devices, or breaking the published interfaces of existing devices to conform to this proposal.
At the level of firmware generation, it is easy to see how simple bitmask types might be leveraged to automatically generate C/C++ enum types. It is not clear whether/how we want to support automatic generation of payloadSpec types in C/C++ firmware code.

Alternatives
Manipulating DIO registers is a fundamental part of many boards, and the existing approaches for manipulating bitmasks seem too confusing for such a basic recurrent feature. The impact of not doing anything to improve the situation will cause significant friction in the learning curve of Harp high-level interfaces.
There might be another alternative to work around the problem without breaking current device compatibility and keeping the default register types as they are. This should be explored in detail elsewhere, but briefly we could mark specific bitmasks as "demux types" and have the generator automatically create conversion operators that convert to/from bitmask type to a demux payload type.
New virtual register types could be added to the drop-down of Parse so that the return type is a demuxed structure. For the CreateMessage operator we could also create a new type converter that exposes bit flags as nested properties so it becomes easier to toggle individual bits HIGH or LOW.
Marking of bitmasks as demux types could be done either at the level of the bitmask type itself, or at the level of the register, for example by specifying simultaneously the maskType and the payloadSpec attributes.
Unresolved Questions
Whether this will replace the existing specification, or be included as an addition to the existing specification remains to be seen, depending on the discussion of the alternatives presented above.
Design Meetings

TBD

If it is worth it, I don't mind implementing this change as a breaking change. I think it's currently a very core and annoying pattern that takes too many operators to get right.
Regarding the yml spec, I would suggest that rather than re-defining the schema, we could have an additional property in each register: bitmask_compiler that toggles between these two modes: "FlagEnum" (default) or "PayloadSpec" (new proposal). As you pointed out, some registers still make more sense to be Flag Enums. In both situations they should be coded as bitmasks in the yml file since they share the same firmware implementation.
We should keep in mind that the yml file should also serve as a blueprint that people can use to generate firmware and, worst case scenario, as a lookup table to interact with the device via the generic bonsai interface when needed.

Consider:

This is a subset of the struct-like payloads:
Allow users to define multiple operators per register (might allow back-compatibility)


Caffe: different data type for Convolution between caffemodel and prototxt

Hello, I found that when I opened my caffemodel using Netron, the numerical values of all convolutional layers were displayed as '?'. However, when I opened any caffemodel downloaded(such as bvlc_googlenet.caffemodel) from the official Caffe website using Netron, the numerical values of all convolutional layers were normally displayed as float32.

So I compared the corresponding information of the convolutional layers in the prototxt file of these two models and found that the bias_term parameter in my prototxt was set to false, but in the official prototxt file, the bias_term parameter was set to true and the bias_filler parameter had a value.

Is this the specific reason for this issue?

@lbq779660843 please share sample files to reproduce the issue.


openbazaar.com is unreachable

https://www.openbazaar.com and https://openbazaar.com gives me (Sweden) and my friend (Malaysia) the following;

Doing http://openbazaar.com gives perhaps some more information.

This was on Firefox on Debian. Similar (less informative) on Chrome and Chromium browsers.
Can't report to openbazaar.com (obviously), and hope it is Ok to do so here...

"Openbazaar.com" is the search engine of OB1, which is now closed. But you can use https://market.mobazha.com/

I have recently installed OpenBazaar desktop and OB1, obviously, didn't work. However, as someone just trying I had no way (until looking here at issues) to find a new search engine. Shouldn't this be displayed more prominently somewhere? How would newcomers to the platform learn about working search engines?


is MAPI legacy authentication?

The document lists MAPI in the first portion as a legacy protocol that can't enforce MFA. However in the articles linked from this page MAPI is mentioned as the preferred option for Outlook that can do MFA and modern authentication.
I don't think MAPI is part of the "CA Legacy protocol block" so this is incorrect information?
In this linked article one can read:
Outlook Anywhere (formerly known as RPC over HTTP) has been deprecated in Exchange Online in favor of MAPI over HTTP. Outlook for Windows uses MAPI over HTTP, EWS, and OAB to access mail, set free/busy and out of office, and download the Offline Address Book. All of these protocols support Modern authentication.

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

ID: ad5f26dc-2f8f-ef76-3d20-a0a42d2bbada
Version Independent ID: a0e971d1-05f2-2c21-06d4-60c087d45c0a
Content: Block legacy authentication - Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/conditional-access/block-legacy-authentication.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@wUEZRs
Thanks for your feedback! We will investigate and update as appropriate.

There is a legacy and modern option for MAPI as mentioned in the article you linked to... https://docs.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online#pop-imap-and-smtp-auth
#please-close


updated readme and added docs

Updated ReadMe to have users use 3.0.3 instead of 3.0.1 to avoid #86


Feature request: allow to retrieve RPM package list

Would be great to be able to get more information related to RPM packages (Fedora, CentOS, RHEL, etc).
Will have a look at this and might come up with a PR.

I had a look at this today and wrote a proposal in #146.

@nkubala @gbraad #146 has been merged, so this issue can be closed.

sorry, completely missed this... Great!


Opportunities list page

[x] Change two columns to a single column
[ ] Default sort for cards should be: open at top, nearest closing deadline at top.
[ ] Can we restore the interaction so that the entire card is clickable/active (in addition to title) to go to opportunity detail page?
[ ] Increase size of text for "Closing in..." to match the $Price text
[x] Comment out the checkmark (Publish) button
[x] In admin view on this page, for any opportunities that appear to the admin, but are not published, can the whole card be faded?

[ ] when an opportunity is 'Not Published', the 'APPLY' button should not appear

I would like the Opportunity list page to display a panel like in this mockup when the user is not logged in

I think this would be ideal:

When user is not logged in, the panel appears and the '+ Post an Opportunity' button is hidden
When user is logged in, the panel disappears and the '+ Post an Opportunity' button is visible.

Done


cannot drag non-browser text into a angular typeahead

I have an office app and I would like to drag text items from the office app into angular uib typeahead.
I have followed the getting-started steps and my html looks like:
<input type="text" ... ui-on-Drop="onDrop($event, $data)" ... >
I have a corresponding method in my controller and nothing gets logged.
$scope.onDrop = function($even, $data){
console.log("event is: " + JSON.stringify($event));
}

Is that even possible?

Thanks,
Radu

You dont need angular dragdrop to accept text into a text field. Text Inputs should take text dragged into them even without using any library.

Ganaraj,
You are right that by default any html input text accepts drag and drop of text.  However my requirements are more demanding:

Be able to clear the contents of the input text when drag text enters.  onDragEnter - i believe you don't have such an event yet, right?

Can you please re-open my question?
Thanks,
Radu

Also i can clear the text with JQuery - but it is a hack - would really want to stay pure angular code.
My hack:
`

...

`


Initialise model in main for greater flexibility

Intention is to make it easier to modify the inital config for the application.

I like this :+1:

Thanks @jdhodges431  :)


mxnet read jpeg images give different values compared with other libs

Description
Hi, guys! I am a student and recently when my colleagues and I use imread in mxnet, version 1.3.1, we found a very strange phenomena. For some jpeg images, the RGB values mxnet read may possibly differ from the values read by other libraries, e.g. skimage, scipy, matplotlib. However, on mxnet, version 1.2.1, everything is fine.
Environment info (Required)
Ubuntu 18.04, Python 3.6.6, Anaconda(conda version 4.5.12), NumPy 1.14.6, skimage 0.14.1
mxnet 1.3.1 was installed by pip
Reproducible example

Here is our result on mxnet=1.3.1. mxnet and skimage give different result!

However, skimage, scipy and matplotlib all give the same value!

Steps to reproduce
(Paste the commands you ran that produced the error.)

This is our test image

here's the code

import mxnet
import skimage.io as io
import numpy as np
filename = "test.jpeg"  # this image lead to value inconsistent!
img_sk = io.imread(filename)
img_mx = mxnet.image.imread(filename).asnumpy()
np.where(img_sk != img_mx)  # should be empty!
# from here you can peek some values using the indices above

import matplotlib
import skimage.io as io
filename = "test.jpeg"
img_sk = io.imread(filename)
img_mp = matplotlib.image.imread(filename)
import numpy as np
np.where(img_sk != img_mp)
import scipy
img_sci = scipy.misc.imread(filename)
np.where(img_mp != img_sci)

What have you tried to solve it?

The only way to solve this is to use version 1.2.1 instead.

Hi @2void mxnet.image.imread() uses opencv imread under the hood. Using the snippet below we can check that the results from both are identical. (I am using mxnet 1.4.0)
import mxnet
import numpy as np
import cv2
filename = "test.jpeg"
img_cv = cv2.cvtColor(cv2.imread(filename), cv2.COLOR_BGR2RGB) #need to convert as default is BGR for opencv
img_mx = mxnet.image.imread(filename).asnumpy()
print(np.where(img_cv != img_mx))

The difference in output between opencv and skimage, from what I could gather, is due to different techniques of decoding the jpeg image (source: https://github.com/scikit-image/scikit-image/issues/2293). However, the output from both cannot be differentiated by human eye.
If you want to ensure you have the exact same output as mxnet.image.imread, I would suggest using opencv.

@abhinavs95 Thank you very much!👍. Looks like opencv and skimage use different algorithms to deal with compressed JPEG data.

Thanks. Glad to hear your issue got resolved.
@Roshrini Can you close this issue ?
@2void Please feel free to re-open the issue if closed in error.

@2void Could you close the issue since your problem has been resolved?

@abhinavs95 Sorry, this is my first time open an issue 😅


Added some new words

Added new words to superb

Coverage remained the same at 100.0% when pulling aba4f85e75297e99726bd881382a4eb7ae5dad39 on soyjuanmacias:master into 36c052cbbac6e54bff874f336e0a2241991b25d5 on Kikobeats:master.

Coverage remained the same at 100.0% when pulling aba4f85e75297e99726bd881382a4eb7ae5dad39 on soyjuanmacias:master into 36c052cbbac6e54bff874f336e0a2241991b25d5 on Kikobeats:master.

The thing I like from the current word set is that all of the words are unisex.
I'm going to add figura manually because I added plural support as well 😄


Tyle8552/local server services

updated local server services sample:

removed ui and logic for starting/stopping local server (felt it went beyond sample's scope)
updated ui
updated file dialog to remember last directory and added extension filters

@john0005 Can you review please?

Will need to update the gif as well.

Everything else looks good.

@john0005 I've decided to remove the gif and just use the png. I think it should be enough to convey what it's for.


Consider removing the CMD + Shift +P shortcut for start/stop pomo.

The CMD + Shift + P keyboard shortcut is a common binding for developer tools, such as VS Code, to bring up the command palette.
After installing your program, which I love btw, it highjacked my ability to open the command palette in VS Code using the default shortcut.  Also, now I will have to remember to remove the shortcut in TickTick's helper app anytime I setup a new machine.
Or, if possible, maybe detect if the window is on VS code and don't hijack there?  idk.  This really messed me up for about a week.  Glad I finally figured it out and thought I'd share the frustration.  Hopefully you guys can figure out an elegant fix to this.

Sorry wrong repo, lol.


Add licenses.db; fix packaging; recognize more file patterns

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Fixes https://github.com/conda-forge/staged-recipes/pull/12558#issuecomment-693380650 :
This now includes the licenses.db which wasn't added to the Conda package.

Addresses https://github.com/conda-forge/staged-recipes/pull/12558#issuecomment-693155109 :
We shouldn't write to the recipe folder during build. Including files via the recipe folder works, but that's an implicit behavior and not an explicit one we should depend on (conda-build could be changed to, e.g., package these files before the actual build; and if someone built with conda-build --no-include-recipe the licenses wouldn't be included.).
The way it currently is, is not optimal, but I opened https://github.com/conda/conda-build/issues/4121 to track this use case.
I'm using the gather_licenses function included in this PR in other recipes that I'm about to submit to staged-recipes.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Windows build fails because of https://github.com/google/licenseclassifier/blob/842c0d70d7027215932deb13801890992c9ba364/file_system_resources.go#L49 which assumes absolutes path to start with / ... which of course does not recognize the D:/... on Windows...

I'm going ahead with the merge (to put this one to use for the https://github.com/containers packages I've worked on).
I'll clean up the patching once everything is upstreamed.

Thanks for picking this up @mbargull! I got it to a point but found it didn't actually work in practice and as I have literally zero go knowledge I didn't know how to fix it myself.
I think it will be very useful for go recipes so I'm glad you took up the challenge and sorted it out! :+1:

I have literally zero go knowledge

Same here :D.
I guess we just have to add it to the build of some feedstocks and hope an eager Go developer then notices it and adds themselves as a maintainer here to improves things if I messed something up ;P.


Upgrading migration task tries to recreate the tag table

I upgraded our gem from 3.0.2 to 3.5.0 and ran the migration installation script listed in the upgrade instructions. The migrations that were generated include one to create the tags table, which we already have, and thus fail when I try to run rake db:migrate. Do I need to do something different?

+1
I removed the following auto-generated migrations to make it work for me:
db/migrate/20151203165736_acts_as_taggable_on_migration.acts_as_taggable_on_engine.rb
db/migrate/20151203165737_add_missing_unique_indices.acts_as_taggable_on_engine.rb
db/migrate/20151203165738_add_taggings_counter_cache_to_tags.acts_as_taggable_on_engine.rb


Add refresh_token to RKOAuthClient

When RKOAuthClient receives a new access token, its delegate should also get the refresh token.
I've added:
- (void)OAuthClient:(RKOAuthClient *)client didAcquireAccessToken:(NSString *)token refreshToken:(NSString *)refreshToken;

Ok, so I added some test coverage here, as you suggested.
I don't want to break any existing code, so I added a new server endpoint (/refresh), to get the refresh_token (and then test its presence).
The next step would be to add a new method to the RKOAuthClient, similar to - (void)validateAuthorizationCode, but to refresh the access token. Should be pretty straightforward, as long as you're committed to stick with the latest draft for OAuth 2.0 (http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-1.5).


Use AMD

I'm looking to move everything over to a more modular aproach. CodeMirror, video.js and Draggabilly support RequireJS for lazy-loading, and I can finally start to split up the huge client.js.
The long term would be to transition to ES6 modules, but that's at least a year off until browser support.

I've decided against this for the time being.

I've been playing with Webpack recently, and it supports bundling several different modularization libraries, and ES6. It might have a good fit in the droppy project

Yes, it look suitable with my requirements (primarily async on-demand loading), but my ultimate decision against a module system was the added overhead from the module loaders, which was at least 20kB minified for the ones that support async loading, last I checked. Do you have a estimate on how much Webpack would add?

I'm probably not grasping how Webpack works yet, so I might be wrong about added overhead on the client. Got some reading up to do. This looks interesting.

I don't have a good estimate, but webpack tends to become extremely tiny after proper deadcode removal and minification. We are just now separating our code out into separate modules on the project I'm working on, so after that I can contribute the knowledge I will have ascertained.
I believe Webpack reduces module loading code in production mode to bear minimums.


ASAN build fails unit tests on Ubuntu 16.04

https://github.com/ripple/rippled/issues/1668 is already closed, but the issue still persists - when running the build_all.sh script on Ubuntu 16.04, the very first build (which in my case is --static --assert --sanitize=address gcc.debug) already fails.
 I am not 100% sure if the issue is with ASAN, boost-coroutine or rippled's use of these - maybe it is even already fixed upstream, but Ubuntu 16.04 still ships with Clang 3.8 by default.

Issue still persists in 17.04, the currently latest Ubuntu release (well, soon to be release).
 I'm inclined to close this, unless you are concerned about the clang versions that ship by default with the distro (we install compilers from apt.llvm.org). TSAN is still a problem and I'm not sure we can fix those easily. UBSAN is TBD, but seems like we should be able to make it pass.

...the build you linked shows a warning from ASAN on line 1161. I'm not sure if it is actually working as expected.

that warning talks about false positives, of which there are none currently. That said, it would be best to eliminate the warning (I'm thinking boost related possibly), so it warrants more investigation.

@ximinez can you check if this is still an issue?

This appears to still be an issue in rippled 1.6.0 with Pop OS / Ubuntu 20.04.

Given the obsolete title of this issue, let's continue tracking in #4661


Master

Add San Jose CA

This PR appears to be spam or junk like https://github.com/openaddresses/openaddresses/pull/1631.


Feature/sg 195 bbox formats

As a part of SG-195 and also related to @Louis-Dupont's work on dataset targets format, this PR adds explicit Bbox formats specs to be used in both datasets & output adapter.

@shaydeci agree on pre-defined bboxes to check for regression. Added them in the recent commit.


Fix unread timestamps changing when hiding a post

Builds on #185. Removes :read_at from the timestamps to be set on create, so it will be nil if the person has never read the post (e.g. they hide it without opening it).
The change to the query may not be necessary, but I thought it best to hard-code it rather than assuming date_trunc on nil would produce nil and that nil < date would be true?

The @unread_ids and @opened_ids in posts_from_relation would likely have been broken with this change, but I fixed that and added tests to specifically ensure they still worked. Marking a post unread no longer destroys its post view, as if a post is ignored and is then marked unread, this would mark it unignored.


Compatibility of io.helidon.microprofile.cdi.Main with Gradle

When simple hello world JAX-RS project is stated from Idea or using Gradle application plugin (gradlew run), it fails to find @Path annotated classes.
It is caused by Gradle application plugin and Idea providing application classpath in two entries

build\resources\main that contains META-INF directory
and build\classes\java\main that contains compiled classes

org.jboss.weld.environment.deployment.discovery.FileSystemBeanArchiveHandler#handle and org.jboss.weld.environment.deployment.discovery.FileSystemBeanArchiveHandler#handleDirectory however expect that directory structure that contains META-INF/beans.xml also contains annotated classes.
As result the initialization console output sequence contains
WARNING: There are no JAX-RS applications or resources. Maybe you forgot META-INF/beans.xml file?

and the handler is not found.
When application is started from final jar file (that contains both META-INF/beans.xml and annotated classes), it runs fine.
Related issue Simple weld-se bootstrap example fails to find class when using gradle
Environment Details

Helidon Version: 2.3.4
Helidon MP
JDK version: java version "17" 2021-09-14 LTS
OS: Win 10
Gradle Version: 7.2

Steps to reproduce

Extract attached delidon-demo.zip project
Run gradlew run
Access http://localhost:7001/hello in a browser

Expected result
hello world response
Actual result
No handler found for path: /hello response
helidon-demo.zip

Updated example build.gradle files to make this work. See PR #3612


Create ex1_24.cpp

C++ Primer 第五版练习 1.24的一种可能的答案。

@boytom  Hi~
Thank you for the contribution. And It seem that you have a lot of experience on c++ from the codes.

Test the previous program by giving multiple transactions representing multiple ISBNs. The records for each ISBN should be grouped together.

The question(ex 1.24) ask us about testing, rather than writing the code. so I suppose that you want to rewrite the "ex 1_23" ? right?
I can't sure that the solution is appropriate. cause you are using std::map and std::iterator to solve it. They will appear later (in the chapter 10). Thus, we should solve the problem without to use them as far as possible. right?
Or, if you find any bugs in "ex1_23", I'm very glad you can point it out. thanks. :smile:

Agree @pezy

是的，ex1_24要求测试前面的程序，但是很明显前面没有程序可以正确实现分组功能。第一章最后的书店程序是要求输入数是按ISBN分组的。如果输入数据没有按ISBN分组，那个程序不会有正确的运行结果。再说了，Sales_item.h 里的知识也是要到后面的章节讲解，所以，在第一章用 std::map和std::iterator是让新手更早了解它们，这是可以的。


Philips Azurion compliance

It seems as if, at the moment, there is a problem with the Philips Azurion systems RDSR-fiels not giving the table position in relation to the beam. This makes it impossible to perform a correct PySkinDose calculation based on the RDSR data as the table and beam have two separate and unrelated coordinate systems.
Let's try and keep an eye on the RDSR-file in upcoming software updates of the Philips Asurion system to see if this is fixed.


HBASE-28832 Upgrade from bootstrap 3.4.1 to non vulnerable version 5.3.3

This is the backport of https://github.com/apache/hbase/pull/6490/ for branch-2.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 15s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
jshint
0m  0s

jshint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 31s

branch-2 passed

+1 :green_heart:
compile
7m 57s

branch-2 passed

+1 :green_heart:
checkstyle
1m 20s

branch-2 passed

+1 :green_heart:
spotbugs
14m 39s

branch-2 passed

+1 :green_heart:
spotless
1m  2s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 32s

the patch passed

+1 :green_heart:
compile
8m 23s

the patch passed

+1 :green_heart:
javac
8m 23s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  8s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
spotbugs
15m 55s

the patch passed

+1 :green_heart:
hadoopcheck
23m  7s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m 18s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
1m 24s

The patch does not generate ASF License warnings.

89m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless jshint shellcheck shelldocs

uname
Linux a0bf2099b396 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / b568f7abc40c3a12f063a8dac2c21fd3283b7692

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
180 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3 shellcheck=0.8.0

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 15s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 57s

branch-2 passed

+1 :green_heart:
compile
2m 29s

branch-2 passed

+1 :green_heart:
javadoc
3m 35s

branch-2 passed

+1 :green_heart:
shadedjars
7m 20s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 55s

the patch passed

+1 :green_heart:
compile
2m 34s

the patch passed

+1 :green_heart:
javac
2m 34s

the patch passed

-0 :warning:
javadoc
2m 22s
/results-javadoc-javadoc-root.txt
root generated 10 new + 94 unchanged - 10 fixed = 104 total (was 104)

+1 :green_heart:
shadedjars
6m 36s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
435m  6s

root in the patch passed.

479m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 491fcf740e28 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / b568f7abc40c3a12f063a8dac2c21fd3283b7692

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/1/testReport/

Max. process+thread count
7993 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  6s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
jshint
0m  0s

jshint was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 44s

branch-2 passed

+1 :green_heart:
compile
8m 12s

branch-2 passed

+1 :green_heart:
checkstyle
1m 23s

branch-2 passed

+1 :green_heart:
spotbugs
14m 50s

branch-2 passed

+1 :green_heart:
spotless
1m 17s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 45s

the patch passed

+1 :green_heart:
compile
8m 14s

the patch passed

+1 :green_heart:
javac
8m 14s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 11s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
spotbugs
15m 21s

the patch passed

+1 :green_heart:
hadoopcheck
24m 35s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 48s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 56s

The patch does not generate ASF License warnings.

91m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless jshint shellcheck shelldocs

uname
Linux 3af4818e0499 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 09512e80934e23e09b6a00e7409a81f194dcd38d

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
179 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3 shellcheck=0.8.0

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  0s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  4s

branch-2 passed

+1 :green_heart:
compile
2m  3s

branch-2 passed

+1 :green_heart:
javadoc
2m 59s

branch-2 passed

+1 :green_heart:
shadedjars
5m 47s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 54s

the patch passed

+1 :green_heart:
compile
2m  5s

the patch passed

+1 :green_heart:
javac
2m  5s

the patch passed

+1 :green_heart:
javadoc
2m 59s

the patch passed

+1 :green_heart:
shadedjars
5m 46s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
460m 50s
/patch-unit-root.txt
root in the patch failed.

495m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux f9d4b320e9d1 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 09512e80934e23e09b6a00e7409a81f194dcd38d

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/testReport/

Max. process+thread count
5226 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 20s

branch-2 passed

+1 :green_heart:
compile
2m  7s

branch-2 passed

+1 :green_heart:
javadoc
2m 59s

branch-2 passed

+1 :green_heart:
shadedjars
6m 21s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  9s

the patch passed

+1 :green_heart:
compile
2m  6s

the patch passed

+1 :green_heart:
javac
2m  6s

the patch passed

+1 :green_heart:
javadoc
2m 58s

the patch passed

+1 :green_heart:
shadedjars
6m 16s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
469m 57s
/patch-unit-root.txt
root in the patch failed.

506m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 8c6fbfb9b2a6 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 09512e80934e23e09b6a00e7409a81f194dcd38d

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/testReport/

Max. process+thread count
5284 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 16s

branch-2 passed

+1 :green_heart:
compile
1m 33s

branch-2 passed

+1 :green_heart:
javadoc
2m 50s

branch-2 passed

+1 :green_heart:
shadedjars
4m 21s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  6s

the patch passed

+1 :green_heart:
compile
1m 34s

the patch passed

+1 :green_heart:
javac
1m 34s

the patch passed

+1 :green_heart:
javadoc
2m 58s

the patch passed

+1 :green_heart:
shadedjars
4m 22s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
526m 36s
/patch-unit-root.txt
root in the patch failed.

556m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux dc680b96fc43 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 09512e80934e23e09b6a00e7409a81f194dcd38d

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/testReport/

Max. process+thread count
5300 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 17s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
jshint
0m  0s

jshint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 44s

branch-2 passed

+1 :green_heart:
compile
6m 11s

branch-2 passed

+1 :green_heart:
checkstyle
1m 16s

branch-2 passed

+1 :green_heart:
spotbugs
12m 34s

branch-2 passed

+1 :green_heart:
spotless
0m 52s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 28s

the patch passed

+1 :green_heart:
compile
6m 13s

the patch passed

+1 :green_heart:
javac
6m 13s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 15s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
spotbugs
14m 16s

the patch passed

+1 :green_heart:
hadoopcheck
24m 19s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m 17s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
1m  4s

The patch does not generate ASF License warnings.

81m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless jshint shellcheck shelldocs

uname
Linux a5c4b8a9e2bb 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 1c6f572ce874271cfcc267379404f96ba124b622

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
178 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3 shellcheck=0.8.0

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 19s

branch-2 passed

+1 :green_heart:
compile
2m 51s

branch-2 passed

+1 :green_heart:
javadoc
4m 27s

branch-2 passed

+1 :green_heart:
shadedjars
6m 14s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 41s

the patch passed

+1 :green_heart:
compile
3m  5s

the patch passed

+1 :green_heart:
javac
3m  5s

the patch passed

+1 :green_heart:
javadoc
3m 50s

the patch passed

+1 :green_heart:
shadedjars
7m 27s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
503m 54s
/patch-unit-root.txt
root in the patch failed.

550m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 0c1fad7f7fa4 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 1c6f572ce874271cfcc267379404f96ba124b622

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/testReport/

Max. process+thread count
5459 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 51s

Docker mode activated.

-0 :warning:
yetus
0m  8s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 19s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 40s

branch-2 passed

+1 :green_heart:
compile
2m 57s

branch-2 passed

+1 :green_heart:
javadoc
3m 36s

branch-2 passed

+1 :green_heart:
shadedjars
9m 20s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 50s

the patch passed

+1 :green_heart:
compile
2m 58s

the patch passed

+1 :green_heart:
javac
2m 58s

the patch passed

+1 :green_heart:
javadoc
4m 12s

the patch passed

+1 :green_heart:
shadedjars
6m 37s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
524m 12s
/patch-unit-root.txt
root in the patch failed.

575m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6524

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 6580495f72b8 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 1c6f572ce874271cfcc267379404f96ba124b622

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/testReport/

Max. process+thread count
5594 (vs. ulimit of 30000)

modules
C: hbase-resource-bundle hbase-http hbase-server hbase-thrift hbase-rest . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6524/3/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Hi @PDavid this needs rebase since now dependent PR #6551 is merged!


add content-length to header

https://github.com/laravel/framework/issues/29227
I added the content length to the header, cause on head request it can not be identified by the web server.

Heya,
Thanks for your PR. You've submitted this on the Illuminate organization which is a read-only sub split of laravel/framework. Please submit your PR on the https://github.com/laravel/framework repository.
Thanks!


Could not connect servers on launch time with denops 7.x

Describe the bug
Using denops 7.0.x, denops attempts to connect to the server several times on the editor startup, but it seems to be failed due to the following errors.
[denops] Server stopped (1). Restarting...
[denops] Failed to connect channel ``: Vim(let):connection failed: tcp address must be host:port
[denops] error: Could not find constraint in the list of versions<EMAIL_ADDRESS>[denops]   Specifier: jsr<EMAIL_ADDRESS>[denops]     at file:///Users/giginet/.local/share/nvim/lazy/denops.vim/denops/@denops-private/cli.ts:5
:26

As I tried, this error is not reproduced using denops 6.0.11.
Provide a minimal vimrc with less than 50 lines to reproduce
Just install denops with lazy.nvim without any settings.
How to reproduce the problem from Vim startup
Start Neovim
Expected behavior
Any errors are not occur
Actual behavior
Failed to connect to the server
Screenshots (if need)
Your environment

OS: uname -a (macOS/Linux) or ver (Windows) Darwin
Deno version: deno --version  1.45.5
Vim/Neovim version: vim --version or nvim --version Neovim 0.10.1
Denops version: git log -1 (run in the denops.vim repository) 7.0.2

Additional context

Could you try call denops#cache#update(#{reload: v:true})?
https://github.com/vim-denops/denops.vim/blob/fcc579be1f11d24b56d4d0180bd6ca8a8b919cdb/doc/denops.txt#L252-L260

This suggestion seems to be working fine 🎉
Thank you!

Hm...  I think the error check is needed for it.
Current implementation just checks for external denops modules.


How to remove punctuation ?

Hello,
How can i receive recognized result without punctuation ?
E.g. Instead of "What is the weather today ?", i'm expecting "What is the weather today" without question mark.
Thank you.

The "Lexical" field in the detailed recognized text does not contain punctuation.
For speech to text, you can turn on detailed format by speechConfig->SetProperty(PropertyId::SpeechServiceResponse_OutputFormatOption, "detailed") before creating the recognizer.
The Lexical field can be retrieved as follows:
auto result = recognizer->RecognizeOnceAsync().get();
string jsonResult = result->Properties.GetProperty(PropertyId::SpeechServiceResponse_JsonResult);

Here is an example of the jsonResult:

Closing the issue as the question was answered.

I am having same issue in javascript sdk and I am using startContinuousRecognitionAsync function. I have added speechConfig.setProperty("SpeechServiceResponse_OutputFormatOption", "detailed") before creating the recognizer object but it's not returning Lexical field in :
recognizer.recognized = function (s, e) {
 console.log('recognized text', e.result.properties.getProperty("SpeechServiceResponse_JsonResult"));
};

Am I missing something ? Thank You.

To set the output format use:
speechConfig.outputFormat = sdk.OutputFormat.Detailed;
The property you found about it is an internal one that isn't used by all recognizer types, the config option should work for all types.

@rhurey Thanks it helped. But we need to enable speechConfig.enableDictation(); so, this Lexical field is not useful. Is there any way to stop auto punctuation please ? Thank You.

Just to make sure I get the right information...

but if the user spoke "Call my wife" you'd get "Call my wife"
?

@rhurey yes. That's exactly we want. Thanks

@rhurey Is there any way to fix my issue please ?

Add this:
speechConfig.setServiceProperty('punctuation', 'explicit', SpeechSDK.ServicePropertyChannel.UriQueryParameter);
To where you initialize your config object.

@rhurey Thanks, this does the trick. But your solution is incredibly hard to find.
For SpeechConfig.SetProperty() there's a PropertyId enumeration, at least, where you can browse the possible values in the online documentation.
But I failed to find any documentation on the different property names and values for SpeechConfig.SetServiceProperty.
Do you have any idea where to look?
TIA


Adding support for Cilium Network Policy

Supporting Cilium network policy in AKS
cilium data plane requires cilium network policy. when specifying azure policy for cilium we get an error - CiliumDataplaneRequiresNetworkPolicyCilium
Configuration
networkPolicy: 'azure'
networkPlugin: 'azure'
networkDataplane: 'cilium'
Detailed Error
"message":"{\r\n "code": "BadRequest",\r\n "details": null,\r\n "message": "Cilium dataplane requires network policy cilium.",\r\n "subcode": "CiliumDataplaneRequiresNetworkPolicyCilium",\r\n "target": "networkProfile.networkPolicy"\r\n}"}]}]

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[ ] Azure Verified Module updates:

[ x] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[ x] I'm sure there are no other open Pull Requests for the same update/change
[ x] I have run Set-AVMModule locally to generate the supporting module files.
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings

@cv-gh
We have added examples for Bicep parameter files to the Readme. This has been applied to all published modules but needs to be done for PRs as well. Can you please run the Set-AVMModule utility as detailed here. It is required for the validation pipeline to succeed and the contribution to be published.
Please reach out if any support is needed.

Hi @ReneHezser set-avmmodule PowerShell was executed and readme and main.json are included in the change. static code validation is passing but build issue is due to some other issues unrelated to this PR. Issue is about AKS Schedule update configuration, and I think there is another PR #3228

Hi @cv-gh
You need to update your branch first. Only then will the new script version update the Readme.

Looks like https://github.com/Azure/bicep-registry-modules/pull/3228 has merged. @cv-gh can you please merge main into your branch and re-run tests?

Looks like #3228 has merged. @cv-gh can you please merge main into your branch and re-run tests?

Hi @cv-gh,
Echoing @ilhaan, please merge latest from upstream.
The PR shows you currently have conflicts to be solved in main.json, hence it cannot be approved and merged.
Please reach out if you need any support.
Let's drive this useful contribution to closure 💪


[NEW ICON] Appium

Skill Name
Appuim
Why?
It is popular for mobile testing.
Reference Image

I created a new project since this project is no longer updating & the author left it, appium is available skills-icons
https://skills-icons.vercel.app/api/icons?i=appium


[5.2] Large payload in database cache table causes corrupt data with decryptor

Using the database as a caching mechanism will crash when trying to store large objects in the cache, the framework will throw a decrypt error when trying to receive from the cache (because the original payload was cut off by MySQL because the datatype used is too small to store the cache object). This causes weird behavior when using Cache::remember(), the first lookup will succeed because it will write to the DB without error, and it will return the original object, however on following lookups it will throw the error seen in the attached image.
Not that much of a bug but maybe there should be some sort of checking mechanism before trying to decrypt data from the database? Or maybe a system which won't write to the cache if the object is to big to fit.
Thanks in advance for looking into this.
-- Edit
This error actually occurred on Laravel 5.1 I was thinking of the wrong project. :sweat_smile:

How large? What PHP version?

Not a bug. MySQL is just crap, and truncates data without warning. I'd recommend using Postgresql instead. There's nothing we can really do about MySQL.

Using PHP version PHP 7.0.3-5
Longer than the column datatype in the cache database table (default in doc is TEXT which would be 65,535 (216−1) bytes = 64 KiB but this could differ per implementation).
Even though "MySQL is just crap", and people should probably not be using MySQL cache in production, it's useful for development/testing.
That being said, the MySQL driver could probably add a checksum or at least the object length to the table (extra column, or maybe fixed length prepended to the object blob?), then verify when looking up. This will be slow, but this should probably not be used in production anyways, (for obvious reasons, as well as being prone to this bug).
This should be fixed due to the face that Laravel does support MySQL for caching, if not it should probably drop support for MySQL caching. (and add a warning to the docs).
Thanks again for looking into this.


Input/TextField API disambiguation/consistency

Closes #9326
There is discussion/examples in the linked issue.
Alter the TextField/Input api by:

Remove TextField.inputProps, since it can be accessed via InputProps.
Remove TextField.InputClassName - confusing with inputClassName and redundant with InputProps.className

Other than the convenience props, access any prop from Input necessary via TextField.InputProps.

@oliviertassinari - You want to keep Input.inputComponent so you can possibly pass component to configure the outer div instead?

@rosskevin Yes, exactly.

Spurious codecov error that I am going to force through once everyone has done their review.

Why keep inputClassName since it can be accomplished by other means? It seems to create opportunities for confusion like:
<TextField inputClassName="foo" type="number" InputProps={{ inputProps: { min: '0', max: '10', step: '1' } }} />

You might not expect that your inputClassName="foo" is going to have no effect because it's being overwritten by what you provided for InputProps.

Spurious codecov error

Hmm. Thought we'd fixed that... (#9323 / #9355)

I thought so too 😕

I am game for removing more props here, but if we remove inputClassname, do we do the same for label, helper etc?

I am game for removing more props here, but if we remove inputClassname, do we do the same for label, helper etc?

Personally I'm in favor of fewer redundant ways to do things, because it simplifies and clarifies the API.

The problem being that TextField exists as a convenience. If we go extreme and remove all flattened props, does TextField have any value?

The problem being that TextField exists as a convenience. If we go extreme and remove all flattened props, does TextField have any value?

Yeah I'm not sure 🤷♂ I guess it's a bit of a slippery slope.


[storage-blob-preview] Support blob immutability policy and legal hold

Add support for blob immutability policy and legal hold with

az storage blob immutability-policy set/delete
az storage blob set-legal-hold

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

storage-blob-preview


Redfish: systest migration to redfish Power on /off

Deprecate legacy REST usage in systest and use Redfish power on / off

https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-test-automation/+/20377


research-maps.html depends on openlayers via http

I made a gh-pages branch to get the io pages working and it looks like https://gios-asu.github.io/gios-research-maps/html/research-maps.html isn't working because its asking for openlayers over http. Could we find an https source to use instead?

Openlayers doens't provide https so we might need to download their library from github.

What about https://cdnjs.com/libraries/ol3 ?

It worked..thanks

sure thing, if you could merge your changes into the gh-pages branch and the github io pages will auto update with the latest code.


Basic configuration type and schema validation.

Is your feature request related to a problem? Please describe.
Currently there are almost not schema validations inside Epicli using jsonschema version 7.
Describe the solution you'd like
Add basic type and schema validation for the following folders containing jsonschema  validation documents:

/workspaces/epiphany/core/src/epicli/data/azure/validation/infrastructure
/workspaces/epiphany/core/src/epicli/data/aws/validation/infrastructure
/workspaces/epiphany/core/src/epicli/data/azure/validation/infrastructure

Describe alternatives you've considered
*
Additional context
The following websites can be used to setup the basic structure and validation documents from the default documents.
1: https://www.json2yaml.com/convert-yaml-to-json - To convert YAML default to JSON
2: https://www.liquid-technologies.com/online-json-to-schema-converter - To convert the JSON defaults to JSON schema
3: https://www.json2yaml.com/ To convert JSON schema to YAML schema.

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license
[ ] Backport tasks created / doesn't need to be backported

Hi there! :+1::innocent:
Here's my research about validation, a proof-of-concept very simple functional-style DSL https://github.com/sk4zuzu/RESEARCH/blob/master/jsonschema%2Bjmespath/main.py#L431-L448 that could be added to our schema documents and provide declarative dynamic validation of Epiphany's manfest (it's a working prototype).
You can see here that on top of the normal jsonchema validation we would add some more dynamic checking using an functonal (expression-only) DSL. :heart_eyes:
A working example (it validates the schema first and then runs "dynamic" checks):
type: object
required:
  - "cluster"
  - "infra/vm"
properties:
  "cluster":
    type: object
    patternProperties:
      "^[a-z0-9]+$":
        required:
          - spec
---
all:
  - eq:
      - jmespath: >-
          "infra/vm".{{ cluster.* | [0].spec.app1.vm }}.spec.os
      - jmespath: >-
          "infra/vm".{{ cluster.* | [0].spec.app2.vm }}.spec.os

Why additional DSL? That's because jsonschema does not support such functionality and it seems it's unlikely it will. Also I was unable to find anything like this... :'C
So idea would be (thank you @seriva!) to make it a small separate stalically-linked binary/command in golang or rust (using musl toolchain), make it public and then reuse it in Epiphany or wherever we would need. :)
WDYT? :thinking:

Hi there! 👍😇
Here's my research about validation, a proof-of-concept very simple functional-style DSL https://github.com/sk4zuzu/RESEARCH/blob/master/jsonschema%2Bjmespath/main.py#L431-L448 that could be added to our schema documents and provide declarative dynamic validation of Epiphany's manfest (it's a working prototype).
You can see here that on top of the normal jsonchema validation we would add some more dynamic checking using a functonal (expression-only) DSL. 😍
A working example (it validates the schema first and then runs "dynamic" checks):
type: object
required:
  - "cluster"
  - "infra/vm"
properties:
  "cluster":
    type: object
    patternProperties:
      "^[a-z0-9]+$":
        required:
          - spec
---
all:
  - eq:
      - jmespath: >-
          "infra/vm".{{ cluster.* | [0].spec.app1.vm }}.spec.os
      - jmespath: >-
          "infra/vm".{{ cluster.* | [0].spec.app2.vm }}.spec.os

Why additional DSL? That's because jsonschema does not support such functionality and it seems it's unlikely it will. Also I was unable to find anything like this... :'C
So idea would be (thank you @seriva!) to make it a small separate stalically-linked binary/command in golang or rust (using musl toolchain), make it public and then reuse it in Epiphany or wherever we would need. :)
WDYT? 🤔

Not relevant for this issue, but ill link it to the one that might deal with this eventually:)

Validation works fine with the fixes made in #2474.


With reference #79 issue, I am getting type '_Map<dynamic, dynamic>' is not a subtype of type 'Map<String, Object?>?' this error

Dear,
I am getting type '_Map<dynamic, dynamic>' is not a subtype of type 'Map<String, Object?>?' while sending answer. with the reference of #79 issue.

Please follow the Bug report template to create bug issues.
And the answer accepts Map<String, Object?> not  _Map<dynamic, dynamic>. You should check your parameter type.
see https://stackoverflow.com/questions/31257735/what-is-the-difference-between-dynamic-and-object-in-dart

But I am sending the same response data only what I am getting from Submit function.

@Vpdwivedi
Please provide more information as the Bug report template says.
Can not help you without steps to reproduce

Thank you fixed in #91


test: create load test for exposure key ingest

We now have some headcount for load test scenarios

/assign

/reopen

/reopen

/assign @chaodaiG

This was fixed in https://github.com/google/exposure-notifications-server/pull/764


Implement cleanup task

Current coverage is 100.00%

Merging #44 into master will not affect coverage as of 31b2538

@@            master     #44   diff @@
======================================
  Files           16      16
  Stmts         1788    1829    +41
  Branches       174     173     -1
  Methods          0       0
======================================
+ Hit           1788    1829    +41
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 31b2538

Powered by Codecov. Updated on successful CI builds.


Can't send 2d array over network

Godot version:

3.1
OS/device including version:

Windows 10 64-Bit
Issue description:

When sending a 2d array with an rpc call, the receiving function seems to interpret it as a 1d
array.
Example Code:
func _ready():
	var networkArray = [ [1,2], [3,4], [5,6] ]
	rpc("doSomething", networkArray)

remote func doSomething(networkArray):
	var localArray = [ [1,2], [3,4], [5,6] ]
	print(localArray[2][0]) #prints 5
	print(networkArray[2][0]) #prints "Invalid get index '[]' (on base: 'Array')"

CC @godotengine/network

@derderder77 I'm unable to reproduce, and the error seems like what you get if you do: networkArray[[]].
Are you sure that is the exact code that gives you that error? Can you provide a minimum reproduction project?

It seems that it was some bug on my side, now that I implemented it again it works


Update C++ OpenMP offload readme

Existing Sample Changes
Description
Restructured to match new template. Updated branding. Fixed formatting. Rewrote for clarity.
Fixes Issue#
External Dependencies
N/A
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[x] Documentation

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Command Line
[x] VSCode

@ishaghosh27 please review.
@IgorOchocki  and @jimmytwei added for notifications.


Questions about Lab7

I'm trying to modify the NRQL to pull information from the OrderDetails table and having issues displaying it.
What I'm trying to do is a Year over Year revenue comparison and what happens is that nothing displays in the graph...just a line at the bottom.  We have this working in insights but would like to see a breakdown in NR1 for each application.
The NRQL I'm trying is: query={SELECT sum(orderTotal - tax) FROM OrderDetails  WHERE appName = '${entity.name.replace("'", "\\'")}' TIMESERIES SINCE ${durationInMinutes} MINUTES AGO COMPARE WITH ${durationInMinutes*2} MINUTES AGO}>
but nothing is being graphed.  Is this possible and I'm just missing something?  Also, not sure if this is the right place to ask for help.

Hi @cmnorman, I'm making the assumption that your 'OrderDetails' is something you've custom instrumented into Insights and would get better support visiting Programmability Office Hours. Details about offer hours can be found here: https://discuss.newrelic.com/t/programmability-office-hours-update/94062
I'd also check the account you selected when making your API key is correct and has the OrderDetail data you're trying to add to your New Relic Application.


Subspaces checks in x/posts

Description
This PR add the checks for subspace inside x/posts module.
Closes #464.
Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Wrote integration tests (simulation & CLI).
[ ] Updated the documentation.
[ ] Added an entry to the CHANGELOG.md file.
[ ] Re-reviewed Files changed in the Github PR explorer.

@RiccardoM I did not implement the first method of the expected keeper you proposed in the issue because it wasn't used anywhere. Tell me what do you think about this and after it I will make some tests.


Leaves infesting themselves

Hi Team,
Not sure if this is just me, but my leaves seems to be infesting themselves.
Is this a bug?
Regards,

Should be fixed in e27bf664921f7761f81ac5bce80fbc7d0747d43d and version 0.1.10.


2.2 crash broked

Describe the Bug:
crash on world load. both new and old world
How to Reproduce:
load into the world
Expected Behavior:
no crash
Version Information:

Operating System: windows
Mod Version: 2.2
Minecraft Version: 1.16.5
Forge Version: 36.2.0
Other mods that were running when the crash happened:

crash-2021-08-11_01.09.18-client.txt

Did you enable the replaceNetherBiomeProvider config?

nope, i didnt touch the configs. just updated and it crashed when i tried to join any world.

same bug here, I am using ATM 6 with added infernal expansion, switching back to 2.1.1 seems to help

I am also having same bug as well in 2.2

Mentioned Users

@amoooooo
@gtokarz
@Klouver0X
@Phweeeee

Please let me know if using this version of the mod doesn't fix your issue: infernalstudios.org/etc/infernal-expansion-2.2.0+20210829.1.jar


Manual approval required for workflow run<PHONE_NUMBER>: Release t0rn refs/tags/v1.10.4-rc.0

Please approve runtime upgrade with github release t0rn v1.10.4-rc.0
Runtime upgrade dry run output:
💈 Script started at 1787595 block in t0rn chain

🐡 Running with dryrun flag!

🐙 checking out v1.10.4-rc.0...
✅ tag checked out

🔎 making sure runtime version got updated...
✅ runtime versions updated

🫧 check WASM artifact...
🔢 WASM blake2_256 hash: 0xa6bc1fbb1d48a3c0e1c8d4a2a65467f624a68da63fc08f049dc264721b7fee73
🔢 WASM blake2_256 hash fetched from release: 0xa6bc1fbb1d48a3c0e1c8d4a2a65467f624a68da63fc08f049dc264721b7fee73
✅ WASM blake2_256 hash is matching
⚙ set_code runtime upgrade... dry
✅ runtime upgrade executed... dry

Workflow is pending manual review.
URL: https://github.com/t3rn/t3rn/actions/runs/4753733473
Required approvers: [AwesomeIbex MaciejBaj]
Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

Workflow cancelled, closing issue.


chore: Update PR template to ensure issue is linked and clarify when examples/docs should be added

What does this PR do?

Add a templated line for Resolves #<xxx> to help guide users to autolink issues to PRs
Add clarifying note on using existing examples to demonstrate addon usage and add a docs page when adding an addon

Motivation

Updating project general practices

More

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
[ ] Yes, I have updated the docs for this feature
[ ] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

/lgtm

we're not that fancy (*yet) 😅


NativeControlHost doesn't work properly with most native control when UseWindowsUIComposition enabled

Describe the bug
Native control is embed but not rendered on the window. It still possible to interact with mouse, but visual any visual response.
To Reproduce
Steps to reproduce the behavior:

Clone latest master
Change NativeEmbedSample config to include lines

.With(new Win32PlatformOptions
{
    UseWindowsUIComposition = true
})

Run this sample on windows
See error

Expected behavior
Control is rendered.
Screenshots

Desktop (please complete the following information):

OS: Windows
Version 0.10.x

Additional information
This issue is not reproducible with newer native controls such as WebView2

Not sure if it's even supposed to work with this combination. It's hard to imagine combination of winui compositor and old native controls. It easily could be windows bug and not avalonia bug.


Condition actions for #show/#hide not working

Which version of the plugin are you using?
[ ] Data Populator for Sketch v3.6.2
Describe the bug
I'm trying to show/hide a layer in Sketch using Data Populator but it doesn't work. I've tried naming the layer to #show["{user.for_hire}"] as the docs suggest but not having any luck. I've also tried making it a symbol but nothing works. These are the different names I've tried calling the layers:
#show["{user.for_hire}"]
#show["{for_hire}"]
#show["{for_hire}" == true]
#show["{user.for_hire == true}"]
#show["{user.for_hire}" == true]
{#show["{user.for_hire}" == true]}
[#show["{user.for_hire}" == true]]
No matter what, the layer is always showing even if the boolean value is set to false in the data. I tried manually hiding the layer to see if it would then show once set to true but it just remains hidden — nothing I've tried works, have spent hours on this now.
I'm using the test datapopulator-demo.sketch template provided by Data Populator and I'm loading the data from this URL:
https://api.unsplash.com/search/photos?client_id=80d96f3329e4b8a67d17ccec7571fef9b606b6d21f0fcd5f2191f84cc5cbf933&page=1&per_page=100&order_by=popular&query=sunset
Environment:

macOS Version: macOS Big Sur v11.2.3
Sketch Version: 72.1 (124357)
Plugin Version: 3.6.2

I've experienced this as well, though specifically it doesn't work in symbol instances. I can get it working if I've named the layer appropriately and directly "Populate Again" on the layer to test it out. But the moment I make the layer into a symbol and attempt to "Populate Again" an instance of the symbol, it doesn't work.

Dirty fixed it with Detach from Symbol before populating with data. 🩹

sorry for the hassle, there are issues with conditional actions at the moment – especially with symbols.


Strange wrapping on heavily indented text

The following (with the text being all on the same line):
\begin{definition}
  \begin{definition}
    \begin{definition}
      Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
    \end{definition}
  \end{definition}
\end{definition}

is formatted to:
\begin{definition}
  \begin{definition}
    \begin{definition}
      Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
      tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim
      veniam,
      quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
      consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
      cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat
      non
      proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
    \end{definition}
  \end{definition}
\end{definition}

I think the formatter is doing a wrapping pass followed by an indentation pass followed by another wrapping pass?

Yes, this is expected behaviour at the moment, as the formatter alternates between wrapping and indenting as you suggest. I am hoping to restructure this to remove the multiple passes framework at some point.

A potential band-aid fix to this could be for line wrapping to not count the initial indent as characters, this would mean that the text starts going past 80 characters but the line width should be bounded by your indent level

Yes this is possible but I would really like the formatter to adhere to 80 characters whenever it can. I'll think about this more.

I am working on a solution as part of a refactor in the one-pass branch, which does the following:

If a line is less than WRAP_MAX = 80 characters, it is kept.
Otherwise, it is wrapped to be at most WRAP_MIN = 70 characters.
This way, after the line is re-indented, it will most likely not need wrapping again.

Implemented in<PHONE_NUMBER>51a61fa4b3c9fa92e9fea8fe577509. Let me know if this is still not desirable and I can reopen the issue.


Mem fast path optimization

Removes one addition from the memory access fast path by including the offset to the memory::mem8 array directly in the page entry data stored in tlb_data. This improves performance.

hi! @copy , how can I download the image for this test ? --> Test failed: Tiny Core 11 CD.
Also, on my machine some tests are segfaulting (for instance: linux reboot). Any suggestions for a proper setup for debugging the tests ?

@copy, the tiny core test failed because the test agent took a bit longer to execute it (in previous runs it was at 288s and the limit is at 300s). Other then that I fixed the expect tests. Any feedback from your side ?

What is the percent of speed optimisation?

Very small. I estimate from benchmarks between 0.5 to 1% on general code. I need to estimate because at this level the noise in the benchmarks is relevant. Anyway, I did a couple of runs with the patch and selected the best one. After that I did run the old code about 10 times and it always had a bit lower score but with a small margin.
The patch does remove an addition but that is probably just one register operation on the host and it is only for the memory fast path which is probably more than 10 - 20 instructions  in native code.
Overall ... I am not sure if the more convoluted code (baking in an offset in some values) is worth the gain ...

the tiny core test failed because the test agent took a bit longer to execute it (in previous runs it was at 288s and the limit is at 300s).

No worries. CI speed isn't very stable so I wouldn't put that on this PR. I'll bump the limit on that test.

Overall ... I am not sure if the more convoluted code (baking in an offset in some values) is worth the gain ...

I think this is a worthwhile optimisation. Memory reads or writes often make up 50% of the executed instructions (and even more of the code size), and this is an obvious win.

@viorelcanja Thanks for the contribution.
FYI, I had to revert the eqz optimisation I suggested earlier — my bad. I thought we were returning mem8 + phys, which can't be zero, but we're actually returning (mem8 + phys) ^ virt. There's another optimisation I'm planning to implement that will further reduce the number of operations of memory accesses (at the cost of increasing the tlb size), which will bring back the eqz part. But this PR is good progress, squashed and merged.


YQ-2068 cache lookup results

This likely belongs to some follow-up patch: TUnboxedKeyValueLruCacheWithTtl relies on garbage collection by periodic calls to .Tick() method, it looks like not called anywhere currently.