Remove ImperativeString* Implementations.

Using Frovedis data structures instead of std::string provides a
significant performance boost.
A similar PR exists that does this plus, changes our varchar data structure. This should be merged first instead.

running tpc-h central now

@wmeddie  q10 & q12

Ah. I had that fixed in the original branch. Let me fix it.

Synchronized, and ran all the tests. This one stood out in particular though and it seems could be related to the String functionality.

[info] ArrowTransferCheck:
[info] Identify check: data that we put into the VE can be retrieved back out
[info] - for Float8Vector
[info] - for VarCharVector
[info] - for BigInt
[info] - for Int
[info] - Execute our function
[info] - Execute multi-function
[info] - Partition data by some means (simple Int partitioning in this case) (PIN) *** FAILED ***
[info]   Set((1.0,a,9.0), (2.0,b,8.0), (3.0,,7.0)) did not equal Set((1.0,a,9.0), (2.0,b,8.0), (3.0,cccc,7.0)) we verify that we get back the data we had put in (ArrowTransferCheck.scala:189)
[info]   Analysis:
[info]   Set(missingInLeft: [(3.0,cccc,7.0)], missingInRight: [(3.0,,7.0)])


add note for devtools configuration

Thanks, but personally I think it's too specific and unnecessary.

Thanks for the PR!
This is misleading as adding a store will not cause this to be true in all cases where one creates a store. If you want to resubmit with a more specific note, we'd be up for that, but the way it's worded right now is potentially confusing for people, which might be worse.


Update Editor section of blogpost

fix discussed on Discord

Actually, this won't work. You need to target bevy-engine/bevy-website/main

this is so sad, but already fixed by cart on bevy-website main https://github.com/bevyengine/bevy-website/commit/d785f6d0053f8868cd7cb4dd17a219d93f6b63a7


Data gatherers config

This offloads from #82 the formalization of the configuration for the datagatherers.
It also moves the responsibility of the validation to the data-gatherer package itself. If we finally end up refactoring the whole cmd/check config file parsing to rely on Viper's mapstructure annotations, we can make validation errors use the mapstructure tag (see example).
This is needed to unblock #95, although additional changes might be needed.

/approve
This looks good to me, pending AKS field name change.
I think this will make https://github.com/jetstack/preflight/pull/95 nicer.

I have renamed ClusterID -> ClusterName for aks and eks, since both seem to be using that terminology.

Sounds good.
/lgtm


Extended setvariable command description

Extended the task.setvariable command description to include special characters which can only be set via URL-encoding.

I'm still here ^^

@echalone thanks for contribution! Could it make sense also to add several examples of it?


looking for min and max date date lock

looking for min and max date date lock

Hi there! Thanks for reaching out, I've added min and max date attributes in the latest release :)
They are optional, but when set will prevent users from selecting dates outside the boundaries, see readme for how to use them.
v0.2.15

Thnx for support 👍


Fix the incorrect case #4 in k8s-src-ip.md

With cluster IP, traffic is masquraded only when --masquerade-all option is specified
or --cluster-cidr is specified and the source is not from the cluster CIDR range
https://github.com/kubernetes/kubernetes/blob/v1.14.2/pkg/proxy/iptables/proxier.go#L842

Is it worth being specific about those flags, where it says "default kubeadm options" ?


Explicit endpoint MAC address is not being set

Explicit endpoint MAC address is not being set.  This is same as the issue described in closed issue [#1009].
I am on unbuntu 16.04 LTS.  I am using the latest docker-ce version and I am using command like below to run docker:
“docker run –mac-address=”02:42:c0:a8:84:22″ –net=my_macvlan_network …”
Docker seems to ignore the –mac-address option and is still assigning its own MAC Address.

I'm seeing the same running libnetwork in 5.4.1 on Centos7:
Seems like we define a MAC addr and it's ignored as the driver automatically assigned a mac address:
docker run -d -it --name samiam --net MyNet --mac-address="02:42:ac:46:fc:ff" centos /bin/bash
4c2fb0fb8d46623dff8223c4afa6d36c5e40e7a169f75f5e5bf8588bfc7f660c
/usr/bin/docker-current: Error response from daemon: failed to create endpoint samiam on network MyNet: driver modified interface MAC address: endpoint interface MAC address present (02:42:ac:46:fc:ff). Cannot be modified with 76:a4:7a:19:c9:1f.; rolled back.

I've tried a few times with the same MAC addr, see the returned auto-generated mac below
02:42:ac:46:fc:ff
56:a4:7a:25:8b:c9

02:42:ac:46:fc:ff
0a:a4:7a:4f:50:3a

02:42:ac:46:fc:ff
5a:a4:7a:82:5c:ea

02:42:ac:46:fc:ff
76:a4:7a:19:c9:1f

02:42:ac:46:fc:ff
fe:a4:7a:56:1b:d6

I have debug logs for libnetwork if you think that could be beneficial,

@Char0772 @myobie what's the situation right now?

Tested with docker 19.03.7, seems to be fixed
docker network create -d macvlan mymacvlan
docker run --mac-address=02:42:c0:a8:84:22 --net=mymacvlan alpine ip l

... the chosen MAC address is correctly set

Problem is still reproducable for followoing mac addresses:

11:11:11:11:11:12
4b:b0:5f:a1:23:c2
bb:78:44:98:d8:e4
02:42:c0:a8:84:22

Env: macOS Version: 10.15.7 (19H15)

Docker:
Client: Docker Engine - Community
 Cloud integration: 1.0.2
 Version:           20.10.0-rc1
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        5cc2396
 Built:             Tue Nov 17 22:49:30 2020
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.0-rc1
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       131bf7e
  Built:            Tue Nov 17 22:52:57 2020
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          v1.4.1
  GitCommit:        c623d1b36f09f8ef6536a057bd658b3aa8632828
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0


Step not rendering in json due to usage of star notation

multiple-cucumber-html-reporter 1.13.1
webdriver 5.11.1
wdio-cucumberjs-json-reporter 1.1.1
NodeJS 10.16.0

In our feature files we are not using the traditional 'Given, When, Then' keywords at the beginning of our statements but using '*' (star) notation instead. After our tests run and the report is generated and below is a snippet from that code. In the name property we have the letter 'p' which is the last character of that step.
{
  "arguments": [],
  "keyword": "",
  "name": "p",
  "result": {
    "status": "passed",
    "duration": 10000000
  },
  "line": "",
  "match": {
    "location": "can not be determined with webdriver.io"
  }
}

Here is an example of using the traditional statements
{
  "arguments": [],
  "keyword": "Given",
  "name": "I am on a desktop",
  "result": {
    "status": "passed",
    "duration": 10000000
  },
  "line": 9,
  "match": {
    "location": "can not be determined with webdriver.io"
  }
}

We have written a large portion of our feature files in star notion which has proven popular amongst our developers. Is there a way of getting name value filed in with the entire step in the report?

Hi @terminalpassion
Thanks for filing an issue and provide all the needed info. This module works in such a way that it uses all the information that is provided by WebdriverIO itself. It will then match if a keyword (language independent) is used and adds that in the to be generated JSON. Because there is no matching keyword, there will be an empty string in the keyword output.
The report also doesn't have the context if the * is a Given|When|Then meaning it can't fill it in without any help from the outside, meaning the @wdio/cucumber-framework module.
Did it work with WebdriverIO V4?

Hi @wswebcreation,
Thanks for your reply which has given the team food for thought. We originally didn't have this in place for WebdriverIO v4. We are currently discussing moving back to Given, When, Then based on this information.
Thanks!

Ok, clear, for now I'm going to close it.


Changes

Add set filepath as URI & irrelevant files.

Looks great! I'll remove the extra files that got pulled in by git and merge after I've tested this on my mac.

I ran some tests and found a couple of odd problems, but nothing major. Looks good!


fix: #145 config files

Your Gemfile lists the gem html-pipeline (~> 3.2, >= 3.2.1) more than once.
You should probably keep only one of them.
Remove any duplicate entries and specify the gem only once.
While it's not a problem now, it could cause errors if you change the version of one of them later.
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies...
Could not find compatible versions
Because jekyll-mentions >= 1.0.1 depends on html-pipeline ~> 2.3
and Gemfile depends on html-pipeline >= 3.2.1, < 4.A,
jekyll-mentions >= 1.0.1 cannot be used.
So, because Gemfile depends on jekyll-mentions ~> 1.6,


Allow File summary AFTER namespace?

Hello all,
Running into the "No summary was found for this file" on Line 0 issue with files, and realized it was due to the fact I'm following the "Laravel way" of putting the class's namespace immediately after the opening <?php tags, example:
<?php namespace MyApp\Controllers;

/**
* This is supposed to be a file summary but won't be parsed as such due to the namespace
*/

If I change this to:
<?php
/**
* This will work just fine and I won't get the line 0 "No summary was found for this file" error
*/
namespace MyApp\Controllers;

I'm not sure if this is something we should fix with PHPDocs or if Laravel needs to change its suggestions, or if I'm just missing something obvious (the most likely).

They don't suggest a file comment, but it's pretty bothersome having phpdoc output an error per file because you're following the recommended convention. It's making catching any actual issues with the docblocks difficult.  Is there a way to cleanly disable that warning?

Seems not relevant anymore, laravel has changed.


[question] multi-contract support

Does ConFuzzius support multiple contracts? For example, https://github.com/crytic/echidna/tree/master/examples/solidity/basic_multicontract/contracts. The two contracts Foo and Bar are deployed at two addresses. echidna_test() in Foo defines the desired invariant, and it is only broken after calling Bar. Can ConFuzzius find such vulnerability?

Hi @jyao15, that's a good question. It depends. You can provide an initial state to ConFuzzius, thus a JSON file where both Foo and Bar are deployed and Foo got initialized with the address of Bar during deployment. Then ConFuzzius should be able to make a call to Bar's function test and return 1. If Bar is not deployed, and your are fuzzing Foo, then ConFuzzius will simulate the call to Bar's test function and return values generated by the symbolic execution, thus probably 0 or 1, since these are required in order to trigger both branches of enchidna_test().

@christoftorres Thanks for the answer. By JSON file do you mean something like https://github.com/christoftorres/ConFuzzius/blob/master/examples/RemiCoin/transactions.json? Is this file manually written or generated by some tool? Shall we use the "-b" argument?

@christoftorres That's very helpful. The last question: how can we generate transaction.json? I assume it is not written by hand.

@jyao15 Sorry for the late reply! I have been a bit busy the past few weeks. Well the transaction.json file is simply a list of transactions that you want to be executed in order to initialize the state of the smart contract. I can't find the script anymore, but we basically wrote a script that would get all the transactions that were performed on a local Ganache node and dump them into this JSON file. Thus, we would use web3 to get the transaction information for each transaction and dump it to a JSON file.


Update app-service-web-tutorial-java-mysql.md

fixed app env settings for password

@DariuszPorowski : Thanks for your contribution to the Azure documentation! The author, @bbenz, has been notified to review your proposed change.

@bbenz any news?

#sign-off

#sign-off

Thanks for this!  - bb


Expose isImmutable method

Why was with issue deleted without one comment?

It was closed without comment because it was opened without a description. The title was "Expose isImmutable method," which is not much to go on considering the method is already exposed. I didn't want any contributors to waste their time trying to guess what you wanted, so I closed it.
I don't know what "Was using the method on the wrong immutable library" means, but I opened https://github.com/rtfeldman/seamless-immutable/issues/192 about the missing documentation. 🙂


Set Helm as manager for managedFields

managedFields were a changed that landed in 1.18. This is an array
under metadata with managedFields. The kubernetes client pkgs that
Helm uses automatically add them.
This change added a manager for the managedFields. The flow for
deciding on the name to use is:

An explicit name if one is chosen
The base name of the first os.Arg (the binary name) if no name
explicitly set.
unknown if no name set and name cannot be detected

The name is at the package level as there is no other place to easily
set it for Helm v3. Since the name is for the binary or app it should
be ok to set app wide.
Signed-off-by: Matt Farina<EMAIL_ADDRESS>
What this PR does / why we need it:
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

To add extra detail for anyone who comes along to this in the future, unknown is what Kubernetes sets it to when it can't figure it out on its own. I discovered unknown as the phrasing during my testing. unknown is a common phrase for k8s when a state isn't known. For example, when Kubernetes can't figure out the User Agent for a request it's internal functions return unknown. This may be way unknown is set in my testing.


Chrome Native Client

Any plans to support Chrome Native Client? Or it's already supported?

Didn't google drop that?
I don't think we support that or that it's planned.

According to Wikipedia, "On October 12, 2016, a comment on the Chromium issue tracker indicated that Google's Pepper and Native Client teams had been destaffed."
We'll keep investing in HTML5, and keep our eyes on parallel technologies such as Emscripten (which are promising but result in worse performance than standard HTML5 builds for us) :smile:


100% test coverage in consensus package

Even 100% coverage doesn't guarantee your code is bug-free, but it's certainly a great first step. Let's try to reach 100% coverage in consensus, testing every single edge case. :)
Any increase in test coverage, even 1%, qualifies for our Hacktoberfest event, so don't be shy!

Hi @lukechampine i have raised a minor PR to increase coverage for update.go and validate.go, please review.

Here's a listing of the remaining uncovered code, with my suggestions on how to write a test for them:

[ ] storageProofRoot

this is used for v2 storage proofs, so validate a transaction that resolves a v2 contract with a storage proof.

[ ] (acc *ElementAccumulator) UnmarshalJSON

just need to add some test cases with invalid json

[ ] (acc *ElementAccumulator) containsChainIndex

this would also be covered by a v2 storage proof

[ ] (acc *ElementAccumulator) containsResolvedV2FileContractElement

ditto

[ ] (eau *elementApplyUpdate) updateElementProof

needs a test case for updating an ephemeral element

[ ] (eru *elementRevertUpdate) updateElementProof

apply a block, update a proof, revert the block, update the proof again, then check that the proof matches the original

[ ] (s State) MaxFutureTimestamp

no real behavior to test here, so just write a trivial comparison

[ ] (s State) BlockReward

need a test case with network parameters where InitialCoinbase != MinimumCoinbase

[ ] (s State) FoundationSubsidy

need a test case that fast-forwards to a regular subsidy block

[ ] (s State) FileContractTax

need a test case for a v1 contract below the tax hardfork height

[ ] (s State) StorageProofLeafIndex

this will be covered by a v2 contract test

[ ] (s State) StorageProofLeafHash

ditto

[ ] (s State) replayPrefix

a good test would be to calculate WholeSigHash at various heights and check that they do/do not match

[ ] (ms *MidState) siacoinElement (and similar)

these need tests cases involving ephemeral elements, i.e. a parent->child chain where the child spends an output created by the parent

[ ] (ts V1TransactionSupplement) storageProofWindowID

should be covered by a v1 contract storage proof?

[ ] updateOakTime

needs a test case at a specific height

[ ] updateOakTarget

needs a test case at a specific height

[ ] adjustTarget

the target isn't adjusted until block 1000, so we need a test that fast-forwards to that height

[ ] (ms *MidState) resolveFileContractElement

another v1 contract storage proof test

[ ] (ms *MidState) resolveV2FileContractElement

same but for v2

[ ] (ms *MidState) ApplyTransaction

more storage proof stuff, also foundation updates

[ ] (ms *MidState) ApplyV2Transaction

need to test all v2 contract resolution types; also attestations and foundation updates

[ ] (ms *MidState) ApplyBlock

need to test missed storage proofs

[ ] (ru RevertUpdate) UpdateElementProof

this would be covered by the revert test described above

[ ] (ru RevertUpdate) ForEachFileContractElement

revert a block with a contract in it and see that it's listed

[ ] (ru RevertUpdate) ForEachV2FileContractElement

ditto for v2

[ ] validateHeader

simple tests for insufficient work and bad nonce

[ ] ValidateOrphan

simple test for commitment hash

[ ] validateSiacoins

test for timelocks, double-spends, and a few other conditions

[ ] validateSiafunds

ditto

[ ] validateFileContracts

check for invalid revisions, multiple storage proofs, and storage proofs in general

[ ] validateArbitraryData

check foundation updates

[ ] validateV2CurrencyValues

missing some straightforward checks here

[ ] validateV2Siacoins

check for double-spends and ephemeral outputs

[ ] validateV2Siafunds

ditto

[ ] validateV2FileContracts

bunch of stuff here tbh, just start by testing anything involving a v2 contract resolution

I know this seems like a lot, but many of them just need a trivial test case, and many others have substantial overlap (e.g. two good tests for v1 and v2 contracts would add a ton of coverage).
For absolute beginners/newcomers, I recommend starting with validateHeader, ValidateOrphan, or MaxFutureTimestamp.


Inference CI from forks

Forks do not have access to secrets in github actions, so inference tests are rate-limited in the CI.
For now it's fine, but if the rate limit changes or we get more tests it's going to be problematic.

Possible solutions:

Use hard-coded access token from a dummy user for better rate limit, too bad if it's made public
Use vitest's --changed flag to only test what's necessary + split inference source files into many to accomodate it
?

Not urgent anyway

@coyotte508 I think you can close this one

Thanks!


Add overflow instrinsics support for souper2llvm

Google » souper #492 SUCCESS
This pull request looks good
(what's this?)

LGTM, please squash and merge

Google » souper #499 SUCCESS
This pull request looks good
(what's this?)


upgrade to v5.4

@plateaukao  :
looks like you made a release v5.4.0 BEFORE this PR get merged

hm...I will update the release binary then...


[Bug] app crashes while importing multiple photos

Tried  to import around 400 photos through files app (com.google.android.documents.ui). Imported first 40-60 but then it crashed after I retried to import again it force closed again.
And secret launch code doesn't work.
I have S10e, One UI 3.1 Android 11. I didn't try on AOSP ROM if anyone has Samsung can you try import multiple photos?

Unfortunately I am not able to test this atm.
Import has been tested with 2000 photos before. I beleve it belongs to an error with a specific photo.

@sivasren Since I am not able to reproduce this, I will close this for now.
Feel free to reopen tough.


TS-4470: ASAN stack-buffer-overflow when slow log is enabled

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/189/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/298/ for details.


Type-safe initial value skipping?

We've seen and heard struggles with the initial value behavior. Some observables emit it (property-based ones) and others do not (event-based ones).
It would be nice to encapsulate this in the type system for guarantees beyond just Javadoc.
public final class InitialValueObservable<T> extends Observable<T> {
  static <T> InitialValueObservable<T> create(InitialValueOnSubscribe<T> f) {
    return new InitialValueObservable<>(f);
  }

  private InitialValueObservable(InitialValueOnSubscribe<T> f) {
    super(f);
  }

  public Observable<T> skipInitialValue() {
    return skip(1);
  }
}

static abstract InitialValueOnSubscribe<T, V extends View> implements OnSubscribe<T> {
  private final V view;

  protected InitialValueOnSubscribe(V view) {
    this.view = view;
  }

  @Override public final void call(Subscriber<? super T> subscriber) {
    attachListener(view, subscriber);
    subscriber.onNext(initialValue(view));
  }

  protected abstract void attachListener(V view, Subscriber<? super T> subscriber);
  protected abstract T initialValue(V view);
}

Consumers could then rely on the type system for guaranteeing both that the observable would emit an initial value and that they could skip it.
RxTextView.textChanges(textView)
    .skipInitialValue()
    .switchMap(v -> suggestions(v))
    .subscribe(adapter);

I know we talked about this a long time ago. I've had a bit of a change of heart on it. It would be nice to indicate somehow that the Observable is expected to emit an initial value. I wonder how the folks at RxJava think about it...
My only concern is that this wouldn't be enough, since you can still use an InitialValueObservable while being completely ignorant of what it does. Just brainstorming - would it be a terrible idea to force the user to choose before using the Observable?

since you can still use an InitialValueObservable while being completely ignorant of what it does

I think this can be viewed as an advantage, but I understand the sentiment.

would it be a terrible idea to force the user to choose before using the Observable?

I believe my initial proposal was opting in to the initial emission. I don't necessarily think that is the right approach either, but it certainly would be explicit.

I think I'm going to make the above proposed change before 0.3 unless there's any compelling argument towards an opt-in approach.
In a casual glance through our codebase, we opt-out far less than we allow the initial value emission. That's just one example of tens of uses. I'm also not confident that I checked every operator that does have an initial value.

I think that the cleanest and the simplest way is to use naming conventions.
RxTextView.text should emit an initial value and updates to the value.
RxTextView.textChanges should emit only updates without initial values.
RxTextView.setText returns Action1 to chain it into Observable.subscribe. But we in fact don't need such method because we have TextView::setText shortcut from retrolambda.

Those overloads would just be implemented using a mechanism like what was
described above but hidden behind convention instead of being an explicit
API.
On Sat, Oct 17, 2015, 10:48 AM Konstantin Mikheev<EMAIL_ADDRESS>wrote:

I think that the cleanest and the simplest way is to use naming
conventions.
RxTextView.text should emit an initial value and updates to the value.
RxTextView.textChanges should emit only updates without initial values.
RxTextView.setText returns Action1 to chain it into Observable.subscribe.
But we in fact don't need such method because we have TextView::setText
shortcut from retrolambda.
—
Reply to this email directly or view it on GitHub
https://github.com/JakeWharton/RxBinding/issues/153#issuecomment-148921306
.

Punting on this to 2.0 after spending the night prototyping different approaches.

I just wonder: what do you think about BehaviorSubject as a representation of view property which can be both read from and written to?


is there a way to add the report as a comment to a pr?

I'd like to somehow receive the raw markdown of the report and post it as a comment to a pr. Is there something I missed or is it currently not possible?

Looks like it's not currrently possible
There's a (old) fork implementing it : https://github.com/n-ryu/test-reporter

Yes it would be REALLY useful to just give us a file of the markdown output so we can use as we wish (e.g. for a PR comment in a subsequent step, or saving it somewhere... anything really). The current implementation is great but it seems like an easy and obvious addition to output the actual markdown.


Use base image from donor booted ostree

Creating base system from donor booted ostree will preserve the same kernel and other possible changes commited to the donor OStree

/hold
rpm-ostreed.service failed to start ... investigating
Aug 21 08:53:42 sno rpm-ostree[1388387]: Reading config file '/etc/rpm-ostreed.conf'
Aug 21 08:53:42 sno rpm-ostree[1388387]: error: Couldn't start daemon: Error setting up sysroot: Reading deployment 0: No such metadata object d940cfc69b56b68676cfa9ec4269771c…8d4e9c78.commit

Finally resolved all the issues I found:

If the final commit has a basecommit, we need to create (and import) both commits in the recipient ostree
Starting from 4.13, we can use ostree container image deploy instead of importing + deploying
Handled kernel args


Update chunk format docs with native histograms and OOO

Part of https://github.com/prometheus/prometheus/issues/12005. Updating format/chunks.md and format/head_chunks.md with float native histograms and out of order changes.

Thank you very much. Will have a look ASAP.

I'm already working on the NHCB PR.

https://github.com/prometheus/prometheus/pull/15135


add Large Scale demo

ref: https://github.com/developmentseed/awspds-mosaic/blob/master/notebooks/LargeScaleMosaic.ipynb

I will have a look at https://github.com/developmentseed/titiler-pds/blob/master/demo/sentinel.ipynb in the interim - Idea being grab the data from the 10m bands - 2/3/4/8 (then do it again for the 20m) and save to geotiff/cog

I will have a look at https://github.com/developmentseed/titiler-pds/blob/master/demo/sentinel.ipynb in the interim - Idea being grab the data from the 10m bands - 2/3/4/8 (then do it again for the 20m) and save to geotiff/cog

A question on the read me... are the region statements meant to be environment variables...or can you deploy to a named --profile ...or it has to be the default?

A question on the read me... are the region statements meant to be environment variables...or can you deploy to a named --profile ...or it has to be the default?

I can expand that once I am clear on deploying to right region where the data is (windows client machine)

I can expand that once I am clear on deploying to right region where the data is (windows client machine)


Metrics name inconsistencies between Micrometer and Prometheus

I found inconsistencies in the metrics names between Micrometer and Prometheus, by using either PrometheusMetricsTrackerFactory or MicrometerMetricsTrackerFactory when configuring HikariConfig.
For exemple, using PrometheusMetricsTrackerFactory, we get these metrics :

hikaricp_active_connections
hikaricp_idle_connections

When using MicrometerMetricsTrackerFactory we get these ones :

hikaricp.connections.active
hikaricp.connections.idle

Which will be translated to Prometheus naming conventions if using io.micrometer:micrometer-registry-prometheus :

hikaricp_connections_active
hikaricp_connections_idle

It can be cumbersome when reusing or adapting dashboards like in Grafana.
But I don't know if it can be changed easily without breaking backwards compatibility...

@ghusta Yeah, that's rather unfortunate. Unfortunately, those two features were largely contributions, with some changes by me, and then even further pull requests over time from other developers, so I think there wasn't much consideration given to naming consistency between the two.
I do agree it seems difficult to change at this point without breaking existing dashboards.  But I am open to suggestions.
Just off of the top of my head, I could conceive of something like a system property, eg. hikaricp.metricsNaming2.0, that if defined as true (i.e., -Dhikaricp.metricsNaming2.0=true) would change the metrics naming in one direction or the other to be consistent.  Possibly over time, with enough notice to users, this could be changed to be the default, and the current behavior could be preserved by explicitly setting the property to false.
It is hard to say which naming is "correct", but subjectively my feeling is that hikaricp.connections.active is better than hikaricp.active.connections, because in a hierarchical key space hikaricp.connections.* is consistent (both active and idle pertaining to connections).  Obviously, in Prometheus, this would be "flattened" .
If this approach would be taken, then the system property would control the metric naming in the PrometheusMetricsTrackerFactory, toggling between hikaricp_active_connections and hikaricp_connections_active, for example.
If you think this is a good approach, could you submit a pull request?

@ghusta Yeah, that's rather unfortunate. Unfortunately, those two features were largely contributions, with some changes by me, and then even further pull requests over time from other developers, so I think there wasn't much consideration given to naming consistency between the two.
I do agree it seems difficult to change at this point without breaking existing dashboards.  But I am open to suggestions.
Just off of the top of my head, I could conceive of something like a system property, eg. hikaricp.metricsNaming2.0, that if defined as true (i.e., -Dhikaricp.metricsNaming2.0=true) would change the metrics naming in one direction or the other to be consistent.  Possibly over time, with enough notice to users, this could be changed to be the default, and the current behavior could be preserved by explicitly setting the property to false.
It is hard to say which naming is "correct", but subjectively my feeling is that hikaricp.connections.active is better than hikaricp.active.connections, because in a hierarchical key space hikaricp.connections.* is consistent (both active and idle pertaining to connections).  Obviously, in Prometheus, this would be "flattened" .
If this approach would be taken, then the system property would control the metric naming in the PrometheusMetricsTrackerFactory, toggling between hikaricp_active_connections and hikaricp_connections_active, for example.
If you think this is a good approach, could you submit a pull request?

Thanks for your reply.
I quite agree with you.
Concerning the metrics naming, I had a look at this pages :

https://micrometer.io/docs/concepts#_naming_meters
https://prometheus.io/docs/practices/naming/

But it almost give examples.
One another interesting example is org.hibernate:hibernate-micrometer.
So I think the best naming is going from more general to more specific, as you said.
I found your suggestion relevant, using a kind a feature flag with a system property.
I'll see if I have some time to work on this, but I can't promise anything yet !

Thanks for your reply.
I quite agree with you.
Concerning the metrics naming, I had a look at this pages :

https://micrometer.io/docs/concepts#_naming_meters
https://prometheus.io/docs/practices/naming/

But it almost give examples.
One another interesting example is org.hibernate:hibernate-micrometer.
So I think the best naming is going from more general to more specific, as you said.
I found your suggestion relevant, using a kind a feature flag with a system property.
I'll see if I have some time to work on this, but I can't promise anything yet !


Update requests dependency

Consider updating Requests dependency due to security issue which impacts versions <= 2.19.1.

Sure.


@import statement in Sass (*.scss) validation incorrectly flagged as error?

VSCode Version: 1.10.2
OS Version: 10.12.3

Steps to Reproduce:

Create a Sass file
Add an import statement to a file that exists
Editor incorrectly flags an error - [scss] { expected

This is the correct syntax - http://sass-lang.com/guide#topic-5

(Note if I edit settings.json and add "scss.validate": false the error goes away but that is because ALL validation is disabled.

@edhenderson The import statement as such is supported. What looks wrong are the --- above it. What are they for?

@aeschli You are quite correct, removing the Yaml front matter clears the error, BUT this is required for Jekyll to correctly use Sass.
Example below is from http://markdotto.com/2014/09/25/sass-and-jekyll/#using-sass-imports
---
# Front matter comment to ensure Jekyll properly reads file.
---

// Imports
@import "base";
@import "type";
@import "layout";

I'm not quite sure of the resolution here as of course this is an edge case on regular Sass. Happy to help diagnose and fix.

I'm testing this, and seems that the YAML front-matter is not a valid syntax for sass, and is not intended to validate as a pure sass or scss file:
https://github.com/jekyll/jekyll/issues/3408

OK, thats fair. Are we able to flag the --- as the error rather than the @import? Or add a caveat to ignore this potential problem?

I improved the parser to flag '---' as error

Thanks for the attention and fix on this, I appreciate it.


Concepts

Testing out some concepts

Use of YAML anchors for the initial job matrix appears to be out
The workflow is not valid. .github/workflows/ci.yml (Line: 12, Col: 1): Unexpected value '.matrix' .github/workflows/ci.yml: Anchors are not currently supported. Remove the anchor 'matrix'

Alright using hidden YAML keys is out:
Invalid workflow file: .github/workflows/ci.yml#L13
The workflow is not valid. .github/workflows/ci.yml (Line: 13, Col: 1): Unexpected value '.matrix'

Multiple YAML documents are also invalid. I had the workflow be the first document.
Invalid workflow file: .github/workflows/ci.yml#L1
The workflow is not valid. .github/workflows/ci.yml: Expected stream end parse event

Using a separate YAML file to store the matrix and then reading it in, converting it to JSON, and using ${{ fromJSON(...) }} to generate the matrix worked as expected (basically https://stackoverflow.com/questions/65384420/how-do-i-make-a-github-action-matrix-element-conditional).
I was hoping that the matrix could reside inside the workflow but the only way I see that working now is if I just include it has a string literal.

Gave a quick try to see if I could hide the matrix YAML in the header instead of document in a similar way to https://github.com/DanySK/true-yaml-actions/tree/master. No dice


Feat/range slider new props

Before submitting the PR:

[x] Does your PR reference an issue? If not, please chat to the team on Discord or GitHub before submission.
[x] Did you update and run tests before submission using npm run test?
[x] Does your branch follow our naming convention? If not, please amend the branch name using branch -m new-branch-name
[ ] Did you update documentation related to your new feature or changes?

What does your PR address?
Addressing #1066

Important notes:

As discussed, added the option to show number values, custom string values and to opt in for vertical labels (horizontal by default).
Apart from that, I also added labelsSteps to allow to don't show labels in every tick (as in the previous pic).
The logic has been manually tested a lot, but there are some issues with the styles:

I cannot add the styles as Tailwind classes because it doesn't work the same in my end.
Vertical labels are not 100% centered in the tick.
Similarly, when many ticks (not necessarily labels) are shown, labels are not centered in the ticks as shown below.

Need to create automatic tests for the new props.
I can update documentation if this is eventually merged.

@SebasF1349 I love the concept of this feature, but I think the way it's being implemented could use it a bit of adjustment. I won't have time to write a proper set of instructions here today, but just wanted to let you know where we are on this. I definitely thing this will be a valuable feature though.
We're juggling a few things right now, so expect this sometime early next week. Thanks!

No problem! Glad you liked the idea. My pr was definitely not production ready so I knew it will need some work. Also, too much work this last weeks, so completely understandable it gets pushed to after v1. Let me know if I can help in anything regarding this.

@SebasF1349 as discussed yesterday I'm closing this, but will refer to this in the ticket when I generate my iteration of this.


Geting error using Cysco Anyconnet

Hi, I'm taking this errors on log, when I connect to my corporate VPN using Cysco AnyConnect. Does anyone already faced the same problem?
check: ❌ nslookup fail for example.com AAAA using <IP_ADDRESS>
ping: bad address 'example.com'
check: ➖ ping fail to IPv6 external host (example.com)
ssl_client: example.com: certificate verification failed: unable to get local issuer certificate
wget: error getting response: Connection reset by peer
check: ❌ wget fail for https://example.com

When wsl-vpn-kit is activated:
instantly...

When wsl-vpn-kit is deactivated:
a few seconds without nothing and then...

I already deactivated the auto-generated resolv.conf. Now, its hard coded, with dns from google and the corporate dns I need for work.
WSL2 - Using Arch linux
Cysco Anyconnect  4.10.05095

Have you tried using the wsl-vpnkit with the auto-generated resolv.conf or <IP_ADDRESS>?

@sakai135 with or without wsl-vpnkit running?

VPN - ON
wsl-vpnkit - OFF

With wsl-vpnkit running. VPN on, wsl-vpnkit on.

@sakai135 however, I can't ping www.uol.com.br for instance.

@sakai135 however, I can't ping www.uol.com.br for instance.

did you ping www.uol.com.br or ping <IP_ADDRESS>
Also, is ICMP (reply) allowed from that host? does the ping work from the host using Powershell for example?

Closing due to inactivity


Achievements+

Feature
Achievements triggered by volumes, ship log facts, and dialogue conditions. Requested by Trifid.
Context
Repurpose the current fact reveal stuff to have an option to either reveal a fact, unlock an achievement, or set a condition.
For ship log facts and dialogue conditions, we'll need a mod config file where we'll set those.

Done in #199


Navigation to *.class file (jdt:// scheme) is missing

jdt.ls sends jdt:// uris for navigating to source code of classes in jar files. In vscode-java a provider is registered for the jdt scheme:
https://github.com/redhat-developer/vscode-java/blob/977973499608ccd5e64115876b250c5dae062023/src/extension.ts#L213-L221
https://github.com/redhat-developer/vscode-java/blob/56c5256f04b2d64208ff5346399cf2e1f94405aa/src/protocol.ts#L69-L71

why isn't the code embedded in this issue?

Implementation notes:

We'll need to add the JDT protocol via protocol.registerFileProtocol
Navigate through the JAR (ZIP) either using existing code or archive-view ?
Then open the file

@fbricon looks like we might just be able to wire the protocol handler up to the language server itself for obtaining the file contents?
Not sure what "code embedded in this issue" refers to.

Yes calling java/classFileContents with that jdt uri will return the source, you don't need to worry about opening/traversing the jar.
For the embedded code, I'm talking about https://github.com/blog/2415-introducing-embedded-code-snippets. It seems to only work for code from the same repo.

Read only text editor coming in https://github.com/atom/atom/pull/16294 which will unblock this

FYI, I plan on disabling sending those jdt:// uris unless clients advertise they support it (see https://github.com/eclipse/eclipse.jdt.ls/issues/649). @damieng you might want to keep an eye on that one.

With jdt.ls 0.20.0 (or more recent), clients need to declare their support for jdt:// urls by sending extendedClientCapabilities.classFileContentsSupport=true in initializationOptions. See   https://github.com/eclipse/eclipse.jdt.ls/issues/649#issuecomment-387775466


chore(deps): update common-dev-assets digest to 67d664c

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
452c37e -> 67d664c

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

GitHub release
v4.0.0

Your semantic-release bot :package::rocket:


Function get localtime in binary built by nix work incorrectly

Describe the bug
Function get localtime in binary built by nix work incorrectly
To Reproduce
Steps to reproduce the behavior:
I have written a simple project at https://github.com/thongpv87/nix-test . The code in main.cpp set the TZ environment variable then call function localtime and print the timezone. Compile this file with g++, nix-build, g++ in docker image by dockerfile, docker image from dockerTools and run these binary/image and compare the result.
My host system time zone is Singapore. The current time in Singapore when I run this is 23:48:40. The output when run with binary from nix-build is:
TZ=(null)
Current local time and date: Thu Jun  4 23:48:25 2020

TZ=America/New_York
Current local time and date: Thu Jun  4 15:48:25 2020

TZ=Asia/Tokyo
Current local time and date: Thu Jun  4 15:48:25 2020

TZ=Europe/London
Current local time and date: Thu Jun  4 15:48:25 2020

More output: https://pastebin.com/t8FAixyL
Expected behavior
TZ=(null)
Current local time and date: Thu Jun  4 23:48:40 2020

TZ=America/New_York
Current local time and date: Thu Jun  4 11:48:40 2020

TZ=Asia/Tokyo
Current local time and date: Fri Jun  5 00:48:40 2020

TZ=Europe/London
Current local time and date: Thu Jun  4 16:48:40 2020

Notify maintainers

Metadata

system: "x86_64-linux"
host os: Linux 4.15.0-70-generic, Ubuntu, 16.04.6 LTS (Xenial Xerus)
multi-user?: no
sandbox: yes
version: nix-env (Nix) 2.3.4
channels(gitlab-runner): "nixpkgs-20.09pre213040.f77e057cda6"
channels(root): "nixpkgs-20.09pre213040.f77e057cda6"
channels(tpham): "home-manager, nixpkgs-20.09pre228165.00df2371122"
nixpkgs: /home/tpham/.nix-defexpr/channels/nixpkgs

This looks like the same issue as https://github.com/NixOS/nixpkgs/issues/65415.

Any update on this?

Duplicate of #65415.


[TW#15836] Feature Request: Bluetooth RFCOMM/SPP as virtual uart in VFS

Is it on the ESP-IDF roadmap to provide a virtual uart integrated into the VFS that utilises RFCOMM/SPP over Bluetooth?
Looking at the example code under
esp-idf/examples/bluetooth/ble_spp_server/

I see a lot of boilerplate and complexity that I would prefer to avoid.

Hi @dmcnaugh , SPP for classic Bluetooth is under development, and we will deliver it in a month or a bit longer. The APIs are not decided yet and I don't know what they will be like. But we will try to make the APIs easy to use.

@dmcnaugh BTstack has full support for SPP. BTstack doesn't require a file system, so RFCOMM has a regular API. A simple SPP Server looks like this: https://github.com/bluekitchen/btstack/blob/master/example/spp_counter.c
Getting started with BTstack on ESP32: https://github.com/bluekitchen/btstack/tree/master/port/esp32


Can you deny specific metrics from specific versions?

Because of an older version are the metrics of my plugin completely messed up (see #80 for full context) and I now would like to deny those metrics from being displayed/rendered in some way, so that the metrics are fixed.
Is there a way to reset the metrics and make bstats not render/handle metrics from specific older versions?

Unfortunately that's not possible.
In your case, I would just recommend to delete the chart and create a new one with a different id.

In your case, I would just recommend to delete the chart and create a new one with a different id.

Would this cause any errors in the server/proxy console when the metrics are submitted?

No, the data will just be ignored by the backend.

Okay thanks for this info.
And while you're here would I like to ask a (hopefully easy to answer) question:
You may already know that I have a project that is split into three separate modules: Core, Velocity and BungeeCord.
I now use bstats-base in the Code module to have a getPie() method which returns a new DrilldownPie instance.
My question now is, should I relocate this base library or leave it as is? I'm not sure if relocating it would cause unwanted issues when compiling the plugin instances...

See https://github.com/Bastian/bStats-Metrics/issues/82#issuecomment-798879746 for why it isn't that simple.
I can't and won't have multiple BStats dependencies in my core as it would only make it bloated without reason, once I build the jar files.
And I do use org.bstats as pattern, so don't worry about this.
You can see my current setup of everything here, to get yourself a picture of my situation: https://github.com/Andre601/OneVersionRemake/tree/feature/move-drilldownpie-method


[NEW ICON]: Streamlit, Langchain, Seaborn, Gemini, PineconeVectorDB, Kaggle

Skill Name
Streamlit, Langchain, Seaborn, Gemini, Pinecone, Kaggle
Why?

Streamlit: Faster and interactive web app framework
Langchain: Framework to build applications using LLMs
Seaborn: Better version of Matplotlib
Gemini: A multimodal LLM developed by Google teams
Pinecone: A vector database widely used in building machine learning models
Kaggle:  An online community platform for data scientists and machine learning enthusiast. (Similar to github)

Reference Image

Code of Conduct Acknowledgment

[X] I have read and agree to the Code of Conduct.

I'm going to work on it, but I have a little problem with the lang chain icon, since it's just emojies, I d'ont really the idea to add it (at least not that version)

@LuluW8071 I found on their github, icons, that I just have and I'm going to post the result here so you can tell me what you think about.

@LuluW8071 what do you think about that ?

Looks great 😊

@LelouchFR if you have time could you check the issues from skill icons original repo! please!

@LuluW8071 what do you think about that ?

That's amazing!!!


[TaskManager DDS] Reorganize test file

This PR reorganizes the UT file. This is done is a separate PR to reduce the number of changes in https://github.com/microsoft/FluidFramework/pull/11649.

Rerunning failed jobs as they look unrelated.


Add New-GkeNodeConfig cmdlet

This cmdlet creates a Google Container NodeConfig object. This object will be used in the cmdlet New-GkeContainerCluster (to be created after this) to configure nodes in a container cluster.
Also enable New-GceServiceAccountConfig to use the project's default service account when service account email is not provided.

This change is

I refactored the code so they can be reused in Add-GkeCluster.
The List<Attribute> is actually not an instance of Collection<Attribute> (Collection here is System.ObjectModel.Collection).
@ILMTitan, @ahandley PTAL

Thanks!


[Live Avatar][Python, CSharp] Add logging for latency

Purpose
[Live Avatar][Python, CSharp] Add logging for latency
Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

/azp run


get feed stories

Hi
how I can get stories in main page feed ?
and another question is , is there any way to manually set page in feeds ?! for example getting posts?

Hi
how I can get stories in main page feed ?
Use ig.feed.reelsTray()

and another question is , is there any way to manually set page in feeds ?! for example getting posts?
Could you elaborate on that?

Hi
how I can get stories in main page feed ?
Use ig.feed.reelsTray()

and another question is , is there any way to manually set page in feeds ?! for example getting posts?
Could you elaborate on that?

thanks for your reply.
for the second question, for example we got this:
const userFeed = ig.feed.user(loggedInUser.pk);
const myPostsFirstPage = await userFeed.items();
const myPostsSecondPage = await userFeed.items();

as you know its auto-paginated, what Im trying to do is to determine offset , and some how handle the pagination manually.

This is difficult if not impossible because nextMaxId is given by the API.
So it is like a linked list where you 'jump' from item to item.

so no easy way ?

This thread has been inactive for a long time now, so it will be closed. If this is still an issue, reopen the it.

@Nerixyz Can you please me on https://github.com/dilame/instagram-private-api/issues/1308


Repo migration with a git:// URL does not require any authentication

I tried to migrate some repos into gogs 0.6.1. For that, I needed each time to clear user/password from the form, as I was using a git:// URL as source, which were automatically provided otherwise.

did you save password in your web browser?

Seems to. I retried after clearing firefox saved passord, and all went OK.

Hmm.. seems it's browser auto-save feature for the web form, close it now but open for continuing discussion. :dizzy:


INSTALL

from FS.pso import jfs
how to pip install this libray in colab .it shows no library found.could please give solution

ERROR: Could not find a version that satisfies the requirement FS.pso (from versions: none)
ERROR: No matching distribution found for FS.pso
while install "from FS.pso import jfs" this type error is display in colab.could you please give us solution


how to set align (left, ...) on cell or column...?

I want to set align in cell, column ... (not in view)?

@MaatwebsiteSupport Maybe you can help me. Look at this : https://stackoverflow.com/questions/51733202/how-can-i-set-text-align-right-in-the-column-on-the-laravel-excel-maatwebsite

works for me, thanks.

@MaatwebsiteSupport How to achieve this in version 3?


chore: release main

:robot: I have created a release beep boop
cli: 0.7.2
0.7.2 (2024-12-22)
Bug Fixes

incomplete string escaping or encoding (#1651) (870d2c2)

unplugin: 0.6.2
0.6.2 (2024-12-22)
Bug Fixes

incomplete string escaping or encoding (#1651) (870d2c2)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

cli0.7.2
unplugin0.6.2
:sunflower:


Adds 3.12 tests (#137)

Syncing the fix/project-type branch to have the latest changes.

Adds 3.12 tests

Adds 3.12 tests

@saketjajoo, could you kindly rebase instead of doing a merge?


fix NoSymbol keybinds

Describe your PR, what does it fix/add?
fixes #6721
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
this should still work for #6548
if you want we can @ the guy to test
Is it ready for merging, or does it need work?
yes

ye please @ em

@JaKooLit, sorry to ping but can you test this pr with plugging your charger to make sure this doesn't regress #6548

@JaKooLit, sorry to ping but can you test this pr with plugging your charger to make sure this doesn't regress #6548

I will try once Im off work... I will let you know


[DS-4126] 5x: Optimize docker builds

Port of #2307
Images have been built on DockerHub at terrywbrady/dspace.

verifyImages.sh has been run.
 ===== dspace-5_x-jdk8 =====
DSpace version:  5.11-SNAPSHOT
           JRE:  Oracle Corporation version 1.8.0_181
  ---> http://localhost:8080/xmlui
  ---> http://localhost:8080/oai/request
  ---> http://localhost:8080/solr
  ---> http://localhost:8080/rest
 ===== dspace-5_x-jdk7 =====
DSpace version:  5.11-SNAPSHOT
           JRE:  Oracle Corporation version 1.7.0_181
  ---> http://localhost:8080/xmlui
  ---> http://localhost:8080/oai/request
  ---> http://localhost:8080/solr
  ---> http://localhost:8080/rest
 ===== dspace-5_x-jdk8-test =====
DSpace version:  5.11-SNAPSHOT
           JRE:  Oracle Corporation version 1.8.0_181
  ---> http://localhost:8080/xmlui
  ---> http://localhost:8080/oai/request
  ---> http://localhost:8080/solr
  ---> http://localhost:8080/rest
 ===== dspace-5_x-jdk7-test =====
DSpace version:  5.11-SNAPSHOT
           JRE:  Oracle Corporation version 1.7.0_181
  ---> http://localhost:8080/xmlui
  ---> http://localhost:8080/oai/request
  ---> http://localhost:8080/solr
  ---> http://localhost:8080/rest

@PTrottier ,
Thanks for catching the typos.  I update the code.
I do not see the issue that you reported.  I created new volumes and I see that the content loaded.

I notice that your screenshot has Mirage rather than Mirage2.  Could you give it another test?

@terrywbrady Sure, I was testing /xmlui, what is the address for Mirage2?

@PTrottier , Mirage2 is an alternate theme for xmlui.  The following line of the docker-compose file will bring up Mirage2, so it makes me wonder how you initiated the dspace container.
https://github.com/DSpace-Labs/DSpace-Docker-Images/blob/master/docker-compose-files/dspace-compose/d5.override.yml#L7
If you did not use the docker-compose.yml + d5.override.yml file on startup, then the content will not autoload.

@terrywbrady I'll investigate things on my end in more detail and report back next week.

@terrywbrady Sorry, this works well for me, I can see Mirage2 as well.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1185 ms

Resolved: Bofrost.de performance has improved in 7d35621.


Add android storybook variant

Adds a build variant that just loads story book for the android app.
Does not load up the go engine.
Use by selecting the storyBook variant or running ./gradlew installStorybook
Don't forget to forward the ports you'll use: 8081 and 7007:
adb -d reverse tcp:8081 tcp:8081
adb -d reverse tcp:7007 tcp:7007

@keybase/react-hackers

yes


Full VM: Deployment Allowed with invalid inputs

Description
Deployments are allowed with invalid inputs in the full vm weblet.
TF Playground _ Full Virtual Machine (1).webm
and it then fails with the following error.

Cannot read properties of undefined (reading 'farmID')

Verified on devnet.
The deploy button is now disabled when an invalid input is entered in any of the fields.
Screencast from 11-06-23 16:46:35.webm


Pin Scotch version to 6.0.4 when building Nektar

Fixes Nektar's Scotch dependence to version 6.0.4.
With Scotch 7.0.1 (Spack's default), running with certain global solve modes, often the default, causes a segfault.
While this can be avoided by setting a suitable 'GlobalSysSoln' in the config file, I'd argue it's better to just rollback the version and not have to worry about it.
N.B.

6.0.4 is the version that Nektar itself builds if configured with -DBUILD_THIRDPARTY_SCOTCH

I'm currently on annual leave until the new year. Is it urgent that I
review this before then?
On Mon, Dec 19, 2022 at 4:01 PM oparry-ukaea @.***>
wrote:

@oparry-ukaea https://github.com/oparry-ukaea requested your review on:
#15 https://github.com/ExCALIBUR-NEPTUNE/NESO-Spack/pull/15 Pin Scotch
version to 6.0.4 when building Nektar.
—
Reply to this email directly, view it on GitHub
https://github.com/ExCALIBUR-NEPTUNE/NESO-Spack/pull/15#event-8070833302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6ESPPZU7ZYH7MXB2OQU53WOCBGPANCNFSM6AAAAAATDQSAQA
.
You are receiving this because your review was requested.Message ID:
@.***>

--
Chris MacMackin

Ah right, sorry, didn't realise - I'll assign to somebody else.
Have a good Christmas!

I'm never keen on fixing package versions. I'd propose that instead we fix it in the specs we put in our spack.yaml file.
You mention this can be fixed with the config file. Is this something that can be done simply when writing our program, or would it require manual intervention? If the former, I think it would be worth considering.

Btw, 6.0.4 doesn't fix the segfaults for me. https://github.com/ExCALIBUR-NEPTUNE/NESO/pull/116#issuecomment-1378869569

You mention this can be fixed with the config file. Is this something that can be done simply when writing our program, or would it require manual intervention? If the former, I think it would be worth considering.

Certain choices of 'GlobalSysSoln', including the default in some cases, seem to cause intermittent seg faults when using Scotch 7 but running in serial.  Setting a value that works is probably always possible, but it can take a while to diagnose the problem if you haven't seen it before / forget that you've seen it before...!


HTreeMap behaves different from java.util.HashMap

Running with Trove 3.0.3 and MapDb 1.0.6 when we insert records into the treemap and then recover them using the cache key the string values on the HTreeMap have been changed to a null.  Using a hashmap this is not occurring.
Could this be related to the handling of single quote, backslash, or utf-8 characters?

It looks like a bug. Would you have a code example?
Also a few common problems to diagnose/workaround:

are you values immutable?

is key hashing consistent?

try to disable cache (DBMaker.cacheDisable()) and do not enable async writer.

possibly transaction problem? commit have to be called to persist updates, or disable transactions.

Let me pull out a simplified dataset and code example that reproduces the issue.
The key hashing is consistent and the transaction is disabled.
I will also give it a try with the cacheDisabled and make the objects immutable.

Closing. Not enough information to reproduce


Enables utbot-analytics module in utbot-intellij module

Description
It returns the ML path selection on the table and gives an ability to mute it via addition/removal just dependency 'utbot-analytics' in the gradle file
Fixes #725
Type of Change

Refactoring (typos and non-functional changes)

How Has This Been Tested?
Manual Scenario
Just change the following line in UtBotSettings
var pathSelectorType: PathSelectorType by getEnumProperty(PathSelectorType.INHERITORS_SELECTOR)
to the following line:
var pathSelectorType: PathSelectorType by getEnumProperty(PathSelectorType.NN_REWARD_GUIDED_SELECTOR)
Checklist (remove irrelevant options):
This is the author self-check list

[x] The change followed the style guidelines of the UTBot project
[x] Self-review of the code is passed
[x] The change contains enough commentaries, particularly in hard-to-understand areas
[x] New documentation is provided or existed one is altered
[x] All tests pass locally with my changes

@denis-fokin please have a look

@denis-fokin I need your review


Add protocol to link in run.sh

This will make the link recognised as a URL in many terminal emulators.

I'm closing this because: 1. We are not forwarding a protocol. 2. The server already shows this link on startup.


Adding (Xt, yt) data during model creation versus model.fit()

What is the difference between adding (Xt, yt) data during model creation (model = FA(LinearRegression(), Xt=..., yt=...)) versus model.fit(Xs=..., ys=..., Xt=..., yt=...)? One observation is that during model creation, if Xt=None and yt=None, then it seems model.fit(...) will fail unless values for Xt and yt are provided (i.e. not None).

Hi @davidshumway,
Yes, it's a good observation, in fact it's almost the unique difference...
Setting Xt, yt at initialization is usefull when you want to use cross-validation objects from scikit-learn on an adapt algorithm.
Giving Xt, yt in the fit instead of initialization is usefull for memory reason, if your target dataset is huge and you don't want to save it with your adapt model, you give Xt, yt only in the fit method. Indeed, when setting at initialization, two attributes self.Xt and self.yt are created and are saved with the adapt model.
Note that you should give Xt, yt (or only Xt, depending of the adapt model you use) in at least one of the two: at initialization or in the fit. But you don't need to give it in both (in fact, the Xt, yt given in fit will overwrite the one given at initialization)


Java API Client

Since I can't open a PR for the Wiki, I just wanted to add to the "clients" section that I posted a basic Java client now that handles sending messages and raw messages - https://github.com/matthewmgamble/postal-java
I'll be updating it with the messages functions as well as I have time / need for them.

Thanks. I've updated the Wiki page.


Add managedResourcesPublicNetworkAccess property in 2021-12-01 API version

ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month. June 2023
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. June 2023
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Link to the approved PR: https://github.com/Azure/azure-rest-api-specs-pr/pull/8953

Link to the approved PR: Azure/azure-rest-api-specs-pr#8953

Add "Approved-BreakingChange" label, but @daminia-ms  you still need to ask to ArmReview Board to review

please fix Lintdiff and Modelvalidation error

Link to the approved PR: Azure/azure-rest-api-specs-pr#8953

@daminia-ms - the status of this PR is ARMChangesRequested, not ARMSignedoff.

Hi, @daminia-ms, For review efficiency consideration, when creating a new api version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Or you could onboard API spec pipeline

@daminia-ms - kindly follow this guidance to recreate the PR with an existing latest API as the first commit for new API version 2021-12-01. Then set WaitForARMFeedback(or remove ARMChangesRequested) label for review.

/azp run

Hi, @daminia-ms, For review efficiency consideration, when creating a new api version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Or you could onboard API spec pipeline

@daminia-ms - kindly follow this guidance to recreate the PR with an existing latest API as the first commit for new API version 2021-12-01. Then set WaitForARMFeedback(or remove ARMChangesRequested) label for review.

Hi @ms-zhenhua, as per the guidelines above, this requirement doesn't apply if we are trying to merge a PR that was previously in the private repository. Please confirm.

Hi, @daminia-ms, For review efficiency consideration, when creating a new api version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Or you could onboard API spec pipeline

@daminia-ms - kindly follow this guidance to recreate the PR with an existing latest API as the first commit for new API version 2021-12-01. Then set WaitForARMFeedback(or remove ARMChangesRequested) label for review.

Hi @ms-zhenhua, as per the guidelines above, this requirement doesn't apply if we are trying to merge a PR that was previously in the private repository. Please confirm.

@daminia-ms ,if you want to continue arm review, please remove ARMChangesRequested  labeland  add WaitForARMFeedback label

Hi, @daminia-ms, For review efficiency consideration, when creating a new api version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Or you could onboard API spec pipeline

@daminia-ms - kindly follow this guidance to recreate the PR with an existing latest API as the first commit for new API version 2021-12-01. Then set WaitForARMFeedback(or remove ARMChangesRequested) label for review.

Hi @ms-zhenhua, as per the guidelines above, this requirement doesn't apply if we are trying to merge a PR that was previously in the private repository. Please confirm.

@daminia-ms ,if you want to continue arm review, please remove ARMChangesRequested labeland add WaitForARMFeedback label and your private pr was not added "ArmSignOff" which means Arm Review was not finished.

@ms-zhenhua Made the suggested changes for the labels, let me know if any further actions are required for this review.

@kazrael2119
So, do we need to fix all Swagger LintDiff and model validation?

@shaileshsk94, Yes, you need to fix all LintDiff errors.
Once you have addressed all feedback provided OR provided a rationale on why the feedback was not addressed, please remove the "ARMChangesRequested" label from the PR.

Hi @daminia-ms , there're some LintDiff errors, please check and fix them as well.

Hi @daminia-ms , there're some LintDiff errors, please check and fix them as well.

Hi @ms-henglu, most of the errors are in the previous api versions and the description for 200 response code is consistent with all our api versions. Is there any specific error that you would suggest as blocking for this PR?

Hi @daminia-ms , there're some LintDiff errors, please check and fix them as well.

Hi @ms-henglu, most of the errors are in the previous api versions and the description for 200 response code is consistent with all our api versions. Is there any specific error that you would suggest as blocking for this PR?

Hi, please check this link: https://github.com/Azure/azure-rest-api-specs/pull/24299/checks?check_run_id=14491556376
There're 2 errors are introduced in this PR, and it's easy to fix, the description should be updated.

/azp run

@msyyc @tadelesh ,please help review sdk breaking change, thanks

@ms-henglu Please suggest the next steps for merging the PR.

Hi @daminia-ms , please ask the PR's assignee to merge it.

@rkmanda Could you please help us to merge the PR.

@rkmanda Could you please help us to merge the PR.

And please help guide on the next steps for generating sdk.


Adds support for assetFilter option

This pull request expands the options set of this plugin to support the assetFilter option, as defined here.

@passion4code I've verified that the changes matches the accepted options from the Universal Compact View. I don't have an active Bynder account, so i'm approving it under the assumption that you have tested these changes.

@passion4code Thanks for the PR, 2.1.0 is out now with the changes.


Change handjs link to https://github.com/deltakosh/handjs repo

The http://handjs.codeplex.com indicates the project has moved to github
so updating the link.
Note: that https://github.com/deltakosh/handjs is discontinued and
suggests using https://github.com/jquery/PEP until native support is
pervasive.
The PE W3C spec https://www.w3.org/TR/pointerevents/ was approved as a
recommendation 24 Feburary 2015. There are currently are three native
implementations IE v11, Edge v14 and Chrome v55 according to
https://www.w3.org/TR/pointerevents/.

What is the time frame for moving Babylon move to jquery/PEP or PE W3C, if ever?

There is no timeframe. You can keep using handjs

K, txs
On Tue, Dec 6, 2016, 1:37 PM David Catuhe<EMAIL_ADDRESS>wrote:

There is no timeframe. You can keep using handjs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BabylonJS/Babylon.js/pull/1561#issuecomment-265280418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-hHLO8D0ys9kgxKIYwArT-0Sh5OChJks5rFdWmgaJpZM4LF2nX
.


[Bug]<EMAIL_ADDRESS>download failed

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
nvcleanstall
Expected/Current Behaviour
As mentioned in https://github.com/ScoopInstaller/Extras/issues/12517#issuecomment-1867716510, the URL hardcoded in the package is no longer available, so the installation fails when trying to access. Doing from the browser you can see the following:

With an invalid certificate from the server. The software can be installed from multiple servers, not just one unique URL:

But the problem is that the available servers list is not always the same, it keeps changing frequently.
Steps to Reproduce
PS> scoop install extras/nvcleanstall
Installing 'nvcleanstall' (1.16.0) [64bit] from extras bucket
The remote certificate is invalid according to the validation procedure.
URL https://nl2-dl.techpowerup.com/files/NVCleanstall_1.16.0.exe#/NVCleanstall.exe is not valid

Possible Solution
Change the download URL to another one which is permanent or check multiple URLs (as the installer is available through multiple servers) during the installation. I don't know exactly how hard can it be to find a permanent link or to perform a discovery of the available URLs during the installation, but it seems to be the only feasible solution.
Scoop and Buckets Version
PS> scoop --version
Current Scoop version:
v0.3.1 - Released at 2022-11-15

'extras' bucket:
b2258212e (HEAD -> master, origin/master, origin/HEAD) spotify-qt: Update to version 3.11

'main' bucket:
4f7bcb890 (HEAD -> master, origin/master, origin/HEAD) trid: Update to version 2.24-23.12.31

'nirsoft' bucket:
b071ab2 (HEAD -> master, origin/master, origin/HEAD) Updated ShadowCopyView

'nonportable' bucket:
856625e (HEAD -> master, origin/master, origin/HEAD) goodsync-np: Update to version 12.5.2

Scoop Config
PS> scoop config

root_path    : C:\ProgramData\Scoop
global_path  : C:\ProgramData\Scoop\GlobalScoopApps
last_update  : 2023-12-31T18:47:25.3177561+01:00
scoop_branch : master
scoop_repo   : https://github.com/ScoopInstaller/Scoop

PowerShell Version
PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Additional Softwares
No response

Can this have some attention? I don't know why this is closed automatically saying that the Nvcleanstall package is not found...


BF: do not assume that expanduser would replace all ~

since it must not e.g. if there is ~ in some directory name along the path (awkward but possible/allowed).
Better to check either new path is absolute.  Removed 1 test which had no value

thanks!


Merge develop into master for release

:tada: This PR is included in version 1.1.4 :tada:
The release is available on:

v1.1.4
GitHub release

Your semantic-release bot :package::rocket:


Samples indexer

[ /] I incremented the version in the VERSION file
[ /] I updated CHANGELOG.md
[ /] I added test coverage for any changes

A few minor comments, otherwise looks aok


Update kernel.js

Fix for Misc syntax highlighting errors. #31

I do not have write access to the repo so I will not be able to merge the pull req.


Major Internal Changes

Changes:
- By far the biggest one: using a database instead of a text file. Up until now, text files were used for scoring, now we are using a database
- Cleaner code: Fixed up some bugs and removed verbose code
- Added some comments
- Added new "about" command
- Leaderboard now uses database for top 10

Merged into development. I'll test it and merge it into master once I'm able to migrate scores and such. Nice work!

Merged into development. I'll test it and merge it into master once I'm able to migrate scores and such. Nice work!

Thank you!


Make all classes final

I think haven't found classes designed to be extended, so I've added the final modifier to all of them. If someone come up with a valid use case we can always remove the modifier.

Codecov Report

Merging #290 (586111e) into master (94e1a66) will decrease coverage by 0.26%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #290      +/-   ##
============================================
- Coverage     91.44%   91.18%   -0.27%
+ Complexity      453      452       -1
============================================
  Files            57       57
  Lines          1484     1474      -10
============================================
- Hits           1357     1344      -13
- Misses          127      130       +3

Impacted Files
Coverage Δ

...tentSecurityPolicy/ContentSecurityPolicyParser.php
100.00% <ø> (ø)

src/ContentSecurityPolicy/DirectiveSet.php
97.77% <ø> (ø)

src/ContentSecurityPolicy/NonceGenerator.php
60.00% <ø> (ø)

src/ContentSecurityPolicy/PolicyManager.php
95.23% <ø> (ø)

src/ContentSecurityPolicy/ShaComputer.php
71.79% <ø> (ø)

src/ContentSecurityPolicy/Violation/Event.php
60.00% <ø> (ø)

...licy/Violation/Filter/BrowserBugsNoiseDetector.php
95.00% <ø> (ø)

...licy/Violation/Filter/CustomRulesNoiseDetector.php
0.00% <ø> (ø)

...tyPolicy/Violation/Filter/DomainsNoiseDetector.php
100.00% <ø> (ø)

...icy/Violation/Filter/DomainsRegexNoiseDetector.php
100.00% <ø> (ø)

... and 33 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 94e1a66...586111e. Read the comment docs.


Android version

Would be very glad to see an Android version of UnGoogledChromium!
Many thanks in advance!

#56


Upgrade readthedocs requirements.

Our older pins were no longer compatible with production RTD.
Fixes #2337

I tested this by replicating the RTD build commands locally, and it seems to work.
This stops the bleeding, but I will circle back to figure out if we can pare down/eliminate this requirements file. Since RTD is opinionated about what it supports, presumably it should be able to just work with those opinions.

Based on https://blog.readthedocs.com/defaulting-latest-build-tools/ RTD should now install the latest sphinx and sphinx_rtd_theme by default, and looking at the git history of our requirements.txt, I think those are all we care about. Looks like the other pins were to work around temporary compatibility issues, and then they started piling up on each other. So a followup PR will test that assumption (I'd like to merge this to get things working again before going down that path).


fixes #199 Bugfix/tclune/#199 hflux fix 3rd try

See PR #1202 for more details

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

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

Checklist:

[x] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

@mathomp4 @sdeastham
This is the new PR

Adding a blocker until I can test on Discover.

I have shown this is zero-diff. So I'll unblock. (Though @atrayano has questions, so it'll still block...)

I'm going to mark this longterm until @sdeastham can test and give a yea or nay.
Also, I think only @tclune can fix the conflict in base/MAPL_SphericalGeometry.F90 as it's beyond me!

Well, I can definitely say that if you don't enable this, the model is zero-diff. I did try to enable it but then history exploded which was its way of saying "You don't know what you are doing Matt". A consult with @bena-nasa confirmed that 😄

Sigh.  OK - hopefully I can work on this at some point this week.

@bena-nasa Please check my corrected logic for getting grid corners.  Thanks.

Due to traffic on #3093 I've updated this PR to develop in case @tclune decides it's time to pull it in.


Access key/ Help text is not defined for 'Open' menu item

Steps to Reproduce

Launch Xamarin Workbook application.
Navigate to File menu item present in menu bar and Expand it
Navigate to 'Open' menu item and Observe Inspect properties

Expected Behavior
Access key or Help text should be defined as 'CTRL+O' for 'Open' menu item
Actual Behavior
Access key or Help text is not defined for 'Open' menu item
Narrator Behavior: Narrator is announcing Open menu item as 'open, menu item'
NVDA Behavior: NVDA is announcing Open menu item as 'open'
Note: Same behavior is also observed for 'Run All, Save, New ' menu items
User Impact
Users who rely on screen reader will not be able to know the shortcut key for 'Open' menu item
Screenshots

Environment
Windows :Windows 10 Pro Version 1803 (OS Build : 17672.1000)
Xamarin Version : 1.4 (master/b3f92f9)
NVDA Version: 2018.1
Log File

Please add the following labels to the bug:
A11yMAS
Accessibility
Xamarin-Workbooks-Windows
Wipro
MAS4.2.1

Exemption Approved - 1813


Pickles/Data generation code

You mentioned you intend to commit the pickles containing the initial Norse data. Alternatively/additionally, you could also give the code to build them from source, to improve reproduceability.

I uploaded the language model pickles, to use directly with agents.py. Furthermore, all the resources and information are now available to generate the language model pickles from the corpus. Everything is described in the README.md file. Let me know if any issues arise!


fix: switch to the new jx gitops apply step

which is more optimised to be faster to deal with project imports etc

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
ab68a80bd52f1d0d016dc1c0db758ce19d214767
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
ab68a80bd52f1d0d016dc1c0db758ce19d214767
link
/test gsm

vault
ab68a80bd52f1d0d016dc1c0db758ce19d214767
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
ab68a80bd52f1d0d016dc1c0db758ce19d214767
link
/test vault

gsm
319ed600437152b85f56fa47c1f06cd94bd8a743
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
319ed600437152b85f56fa47c1f06cd94bd8a743
link
/test gsm

vault
319ed600437152b85f56fa47c1f06cd94bd8a743
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
319ed600437152b85f56fa47c1f06cd94bd8a743
link
/test vault

gsm
85209fcb0cb835c146236974b745ec1288528b42
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
85209fcb0cb835c146236974b745ec1288528b42
link
/test gsm

vault
85209fcb0cb835c146236974b745ec1288528b42
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
85209fcb0cb835c146236974b745ec1288528b42
link
/test vault

gsm
467369a612dcaded703af12bcb27ea85c9b3696c
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
467369a612dcaded703af12bcb27ea85c9b3696c
link
/test gsm

vault
467369a612dcaded703af12bcb27ea85c9b3696c
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
467369a612dcaded703af12bcb27ea85c9b3696c
link
/test gsm

vault
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test vault

gsm
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test gsm

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test vault

gsm
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test gsm

/test vault

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test vault

gsm
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test gsm

vault
e8c13ec52372a7db68a72ee3c301bfaf098e8122
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test vault

/test gsm


Add Tests

Add Unit Tests to ensure that Authentication is working as expected.

will require akavache/Akavache#375


Unhandled Exception in Client Dist

Failed to execute script 'jarbou3' due to unhandled exception: No module named 'Crypto'
Traceback (most recent call last):
File "jarbou3.py", line 13, in
ModuleNotFoundError: No module named 'Crypto'
This is on the compiled client executable.  Does one need to manage python module dependencies on the client end?

can you please run the installer.bat

The instructions says to use the latest Python so I have 3.12.


move bevy_core_pipeline to its own plugin

This decouples the opinionated "core pipeline" from the new (less opinionated) bevy_render crate. The "core pipeline" is intended to be used by crates like bevy_sprites, bevy_pbr, bevy_ui, and 3rd party crates that extends core rendering functionality.

bors r+

bors retry


[backport/2.16] ldap: fix GetUserByClaim for binary encoded UUIDs

GetUserByClaim didn't correctly work for claim "userid" when "idIsOctetString" is set to true. Because the LDAP filter was not correctly hex-escaped.
Fixes: https://github.com/owncloud/ocis/issues/7469 (cherry picked from commit 9b24c1780d57f98cad5fbcf982165fe47e47690b)

@micbar The codacy thing seem to not be enable of the 2.16 branch. Just ignore it? (IIRC that's what we did for 2.16.1)


Support multiple images upload on Flask-Admin interface

The user would like to see the Items pictures during the shopping. Current, Flask-Admin interface doesn't support multiple pictures upload, just one at time. We need to override the behaviour to support multiple pictures upload during Items creation (http://localhost:5000/admin/item/new/).

Hey @anapaulagomes I've started working on it.

Hello
I'd like to work too. But I'm not able to run it or the server.
I've not used Postgres earlier. Please help me to get started.
Till now I've fork the code. Downloaded & installed postgres (with password: postgres) and python libraries.
On running run.py
I'm getting the error: sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) fe_sendauth: no password supplied
Help me with this.

Hi @a-arpit94 ! I'm going to write a CONTRIBUTING file to help with this issues.
Are you using a virtual environment?

No.
Actually, I'm using Pycharm IDE, the project is saved in another folder. If the error would cause because of specific versions of libraries then I would have make a virtual environment. But it shows the error with database.
Please write CONTRIBUTION file or mail me at<EMAIL_ADDRESS>for specific answers to my queries

Hey @a-arpit94, don't forget to be polite. I'll write the guide as soon as I can. Regarding this issue, @ab-anand is already working on it.

Hello @anapaulagomes
I don't think I've said anything which could offend anyone. I was just pointing the issue I'm facing and asked for the solution to get it started so that I can contribute in this project. I am looking forward when you write CONTRIBUTION.MD file or @ab-anand  resolve this issue as early as possible.
Cheers