A few updates

A few minor tweaks, new() syntax, pattern matching, and minor optimization of filtering to attribute

I appreciate the help, but....these changes aren't what I'm looking for :). I'd rather not use new() and get rid of var in those cases.

I appreciate the help, but....these changes aren't what I'm looking for :). I'd rather not use new() and get rid of var in those cases.

No worries. There are a few other changes though that don't go against the rules you have in place.
For example:
public Destination MapUsingInline() => new Destination(); // this.source.MapToDestination();

vs the proposed:
public Destination MapUsingInline() => new(); // this.source.MapToDestination();

This
var candidateTypeSymbol = model.GetDeclaredSymbol(candidateTypeNode) as ITypeSymbol;
if (candidateTypeSymbol is not null)

vs the proposed:
if (model.GetDeclaredSymbol(candidateTypeNode) is ITypeSymbol candidateTypeSymbol)

Or
public List<TypeDeclarationSyntax> Candidates { get; } = new List<TypeDeclarationSyntax>();

vs
public List<TypeDeclarationSyntax> Candidates { get; } = new();

Also, some of the pattern matching stuff maps.Count == 0 vs maps is { Count: 0 }. Oh, and the filtering with LINQ is an improvement in that it's not a nested foreach loop and it doesn't call .ToString() twice. Take care

No worries. There are a few other changes though that don't go against the rules you have in place.
For example:
public Destination MapUsingInline() => new Destination(); // this.source.MapToDestination();

vs the proposed:
public Destination MapUsingInline() => new(); // this.source.MapToDestination();

This
var candidateTypeSymbol = model.GetDeclaredSymbol(candidateTypeNode) as ITypeSymbol;
if (candidateTypeSymbol is not null)

vs the proposed:
if (model.GetDeclaredSymbol(candidateTypeNode) is ITypeSymbol candidateTypeSymbol)

Or
public List<TypeDeclarationSyntax> Candidates { get; } = new List<TypeDeclarationSyntax>();

vs
public List<TypeDeclarationSyntax> Candidates { get; } = new();

Also, some of the pattern matching stuff maps.Count == 0 vs maps is { Count: 0 }. Oh, and the filtering with LINQ is an improvement in that it's not a nested foreach loop and it doesn't call .ToString() twice. Take care


Authik library is outdated or what?

I couldn't find anything about how to get the NEXT_PUBLIC_AUTHIK_PUBLIC_KEY and AUTHIK_SECRET_KEY. So it the library is outdated or what? I'm newbie here for NextJs

Hey, yeah the library doesn't exist anymore so auth doesn't work in this repo. Haven't had time to replace it with anything yet.

Got it! Thanks for your prompt reply!

@Nisarg1112 I have cloned this repo a fair amount of times or built out similar versions. There are always infinite libraries for this type of thing but staying close to Brian's implementation with GraphQL, one of the easiest ones I found to implement at the time was Supertokens.
Clerk is simple and has easy setup with apollo
I just found a library called Hanko that is also really simple for password and passkeys
Supabase is a there but a bit involved. Just alternatives. Kinda sad Authik never got to be used. Brian's setup with it seemd so simple

Hey @Benanna2019 do you have an example implementation setup with one of these auth providers?


LUN-xx: Add exported flag and remove --silence flag

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword LUN.

Fixed the pipeline, dev-delivery workflow is now working. Tested successfully on this branch, therefore version bump and moving of release notes happens here.


Health checks

Add the option for core containers to touch a file on a regular basis so we can see if they are frozen or deadlocked.

Codecov Report

Merging #21 into master will decrease coverage by 1.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   61.15%   60.13%   -1.03%
==========================================
  Files         115      115
  Lines        9829     9933     +104
==========================================
- Hits         6011     5973      -38
- Misses       3818     3960     +142

Impacted Files
Coverage Δ

assemblyline/odm/models/config.py
99.39% <100.00%> (+<0.01%)
:arrow_up:

assemblyline/common/backupmanager.py
60.16% <0.00%> (-16.19%)
:arrow_down:

assemblyline/odm/randomizer.py
95.16% <0.00%> (-0.49%)
:arrow_down:

assemblyline/common/identify.py
0.00% <0.00%> (ø)

assemblyline/common/constants.py
88.23% <0.00%> (+0.35%)
:arrow_up:

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 dcc8c50...57bdff4. Read the comment docs.

Codecov Report

Merging #21 into master will increase coverage by 0.14%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
+ Coverage   60.91%   61.06%   +0.14%
==========================================
  Files         115      115
  Lines        9858     9798      -60
==========================================
- Hits         6005     5983      -22
+ Misses       3853     3815      -38

Impacted Files
Coverage Δ

assemblyline/odm/models/config.py
99.39% <100.00%> (+<0.01%)
:arrow_up:

assemblyline/filestore/transport/sftp.py
26.60% <0.00%> (-5.02%)
:arrow_down:

assemblyline/filestore/transport/ftp.py
18.47% <0.00%> (-3.96%)
:arrow_down:

assemblyline/datasource/alert.py
88.46% <0.00%> (-3.85%)
:arrow_down:

assemblyline/datastore/__init__.py
59.20% <0.00%> (-1.56%)
:arrow_down:

assemblyline/datastore/helper.py
24.80% <0.00%> (-1.27%)
:arrow_down:

assemblyline/run/cli.py
23.24% <0.00%> (-1.27%)
:arrow_down:

assemblyline/datasource/common.py
70.37% <0.00%> (-1.06%)
:arrow_down:

assemblyline/odm/randomizer.py
93.86% <0.00%> (-0.95%)
:arrow_down:

assemblyline/filestore/transport/http.py
64.55% <0.00%> (-0.45%)
:arrow_down:

... and 6 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 f7f18c2...9343215. Read the comment docs.


Write tech.xing.com article

Let's write an article before we open source it. We can publish it together. Everyone who has a blog can then re-blog the tech.xing.com post to get more visibility.
I started a blog post here:
https://medium.com/p/97972d9ab161/edit
@iltempo can we change the author to XING instead of the one who created the draft?

please take a final look at the article. @BasThomas @iltempo @JoeSSS @dhartwich1991 @q231950

We should decide if we want to resurrect physical device functionality before we post the article, or just mention that it will be available there.

@danielknott I added some comments to the article right on Medium (as I don't have rights to change the original text).

the PR about physical devices is in review #109

@danielknott the article is great from my point of view 👍
I believe that we can publish it at Monday. #109 should be merged soon.

Why not writing two articles? :) For a long time I wanted to write something motivational for Calabash community. http://www.waysoftesting.com/?p=262&preview=true @danielknott do you think it is fine to publish it in the same day and reference to the tech.xing.com from there?

The link you provided gives a 404, but I don't see a reason why not. Would it make more sense to not post the two posts at the same time though? Not sure if that would be the best way to go. But definitely 2 > 1!


French translation for 1.1 Group management

Externalized some strings that were already translated but it was not referenced in html or yaml source files.

Thanks!


Warning spam in Compatibility renderer: Attempting to use a shader that requires tangents with a mesh that doesn't contain tangents.

Godot version
Godot v4.2.beta (5ee983188)
System information

Windows 10.0.22621 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 Ti (NVIDIA; <IP_ADDRESS>99) - 12th Gen Intel(R) Core(TM) i7-12700F (20 Threads)

Issue description
When create a new scene and add any mesh instance 3d to it, the following warning spams:
drivers\gles3\rasterizer_scene_gles3.cpp:265 - Attempting to use a shader that requires tangents with a mesh that doesn't contain tangents. Ensure that meshes are imported with the 'ensure_tangents' option. If creating your own meshes, add an `ARRAY_TANGENT` array (when using ArrayMesh) or call `generate_tangents()` (when using SurfaceTool). (User)

This doen't happen in forward plus or mobile.

Steps to reproduce

Create a new project with Compatibility renderer
create a new scene and add a mesh instance 3d to it
observe the warning spam

Minimal reproduction project
N/A

Just start an empty project in Compatibility mode in 4.2 Beta and this happens immediately without adding any meshes.

This warning appears to have been introduced by this commit:
https://github.com/godotengine/godot/commit/d1043a5f930513aa4b48b014ec7961cad48b0560

We uses the uses_tangent variable to track whether the shader uses tangents or not. The variable is set to true if certain shader built ins are used here: https://github.com/godotengine/godot/blob/3e7f638d7b574785f521beafaf52a6ad95be016f/drivers/gles3/storage/material_storage.cpp#L2925-L2928
However, mistakenly uses_tangent isn't initialized above (and a few others). So if it's not set to true it's used uninitialized and can be anything.
I'll bet that is what's causing this issue and the solution is to initialize it to false above with all the other variables.

I will take a look, thanks!

Confirmed with 4.2-beta5 official build. Can't reproduce with a local dev build of the master branch, probably because GCC initializes memory differently for unoptimized builds.

I'm definitely seeing it on my local build from master still, but I'm building on Windows so I'm not using gcc I guess.

This is marked as closed but in godot 4.2.beta6 the issue is still there. This screenshot is from a completely new project, no nodes or scripts at all. Windows 11.

@WalruswareGames This didn't make it into Beta 6, but it is in the master branch, so it will be in the next beta/rc release.

If it's not in beta6, why did it resolve this issue for me?
Godot v4.2.beta6 - Pop!_OS 20.04 LTS - X11 - GLES3 (Compatibility) - Mesa Intel(R) UHD Graphics 630 (CFL GT2) () - Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 Threads)

This didn't make it into Beta 6

If it's not in beta6, why did upgrading from beta5 to beta6 resolve this issue for me?
Godot v4.2.beta6 - Pop!_OS 20.04 LTS - X11 - GLES3 (Compatibility) - Mesa Intel(R) UHD Graphics 630 (CFL GT2) () - Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 Threads)

It's an uninitialized memory error. So it happens randomly. It's only working for you in beta 6 by chance.
The actual fix is coming in the next release

Thanks for clarifying and sorry for the bother. I didn't want to not
mention it in case it was still broken I didn't realise it hadn't been
included in beta 6.
On Wed, 15 Nov 2023, 20:12 Clay John, @.***> wrote:

This didn't make it into Beta 6
If it's not in beta6, why did upgrading from beta5 to beta6 resolve this
issue for me?
Godot v4.2.beta6 - Pop!_OS 20.04 LTS - X11 - GLES3 (Compatibility) - Mesa
Intel(R) UHD Graphics 630 (CFL GT2) () - Intel(R) Core(TM) i9-9900K CPU @
3.60GHz (16 Threads)
It's an uninitialized memory error. So it happens randomly. It's only
working for you in beta 6 by chance.
The actual fix is coming in the next release
—
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/84418#issuecomment-1813194173,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWQ3CSVT4N75TJNH2YTBEB3YEUO25AVCNFSM6AAAAAA64U2II6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGE4TIMJXGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fixed representative data tables in API-README file, removing unnecessary rows.

Description
**Invited Collaborator(s) to Review

Tara Timmerman
Nathan Hietala

What work was done?

On the preview of Github for this API-README.MD file, I noticed that the rows for the representative tables were not lining up correctly, so I went ahead and corrected those rows so the information doesn't fall onto an empty row.

Describe in detail what's been modified/created
Why was this work done?

This was done for better clarity of how the information of the data is presented.

Type of change

Correction

Completed, ready to review, and merge
Checklist
My code follows the style guidelines of this project
I have performed a self-review of my own code
My code has been reviewed by at least one peer
I have made corresponding changes to the documentation
My changes generate no new warnings

Super appreciate this, thanks, Jennifer!


Fix for<EMAIL_ADDRESS>

createJSModules() has been deprecated

Can this be merged please?

@DylanVann ping


Importance sampling env maps

Description

For #59
Known issues:

slightly low exposure when importance sampling is enabled as compared to current results with uniform sampling
slightly incorrect code for uniform sampling wrt MIS

Testing

TODO list:

looks good, could do with a bit of polish

Ok @achalpandeyy do the filter stuff at some point, watch out for when I'll finish the raytracing branch, then merge it into yourself and then we can merge ex 0 and ex42 together


Create proper m3u files.

Format is header, then a list of metadata and filepath pairs.
Fixes #2246.
Title

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate)
Types of Changes

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

Checklist

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

Related: #2256


HTTP error 500 context deadline exceeded when attempting to persist state to a MongoDB instance

Expected Behavior
To invoke the Dapr sidecar directly i.e. http://localhost:3500/v1.0/state/mongostore to store state against a MongoDB database instance and return HTTP 201 return code in that the payload has persisted in the database.
Actual Behavior
I continuously have a return code of HTTP 500 with a response text of:
{     "errorCode": "ERR_STATE_SAVE",     "message": "context deadline exceeded" }
Steps to Reproduce the Problem
Create a MongoDB yaml file that looks similar to this:
`
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mongostore
spec:
type: state.mongodb
metadata:

name: host
value: localhost:27017
name: username
value: root
name: password
value:
name: databaseName
value:
name: collectionName
value:
name: writeconcern
value:
name: readconcern
value:
name: operationTimeout
value:
`

Run an application using Dapr i.e. I am using a .NET core app here:
dapr run --app-id myapp --port 3500 --app-port 5000 --components-path ./components dotnet run
Then post the following:
POST http://localhost:3500/v1.0/state/mongostore [         {           "key": "2",           "value": "value2"           } ]
Other useful information about this bug
Redis state store works ok within the same application/instance of Dapr.
I can successfully communicate with the MongoDB instance using other applications outside of Dapr.
I have a user name and password configured in MongoDB because there is a bug in the C# SDK that requires it. I have not set the database collection or database name in the yaml for this component.

@simonrhart ,
Regarding - "I can successfully communicate with the MongoDB instance using other applications outside of Dapr."
What is the address that you are using in connecting the MongoDB instance?

@shalabhms
In my Dapr app I have written my own repository instead of using the Dapr one and this is the connection string/ctor code that works ok:
mongodb://root:<mypassword>@localhost:27017
Where  is my actual password of course.
The client code I am using this is:
  IMongoClient mongoClient = new MongoClient(connectionString);
In Robo 3T I am just using: localhost:27017

I believe I saw this issue when writing the conformance tests for mongo (https://github.com/dapr/components-contrib/pull/336/commits/4492d887ff2e4ff53fce92e798ce87b3e800fa2d) <- this has fixes in.

Firstly, there's an issue on this line where it is using defaultTimeout instead of the operationTimeout defined in metadata.
Secondly, and critically, all other operations use m.operationTimeout which is never set so immediately fails on any operation. We need to add: m.operationTimeout = meta.operationTimeout to actually set it.

Thanks @jjcollinge for bringing the issue details.
#370 has fixed the issue now.

Thanks for fixing chaps, will test when it has been merged


Is it possible to make lists final in the attributes?

I have noticed that even if you use private final for an attribute that is a list, that list would still be mutable!
Is there a way to make this list immutable or do we have to create an Imlist?

Although I think having a mutable list is very useful in most cases (outside the module ofcourse), I think that the idea of creating of creating new list and modifying that list, rather than modifying the previous list is sufficient for us.
Immutable is a concept for the user and as long as the user feels that it is immutable, then it should be good.


Initial Wasm runner implementation

Still untested, but I might have a very basic proof of concept ready. Currently it requires the user to define and export buffers to transfer tensors to/from wasm. The alternative is to pass pointers and lengths manually, which I think is more complicated, and doesn't allow for multiple returns. I used color_eyre temporarily for quick error handling, let me know what error handling system you are using and I can refactor to that. Also I'm not super sure how to test the runner, I have a half completed test written.

This is a good start. Here are a few high level comments:

Currently it requires the user to define and export buffers to transfer tensors to/from wasm. The alternative is to pass pointers and lengths manually, which I think is more complicated, and doesn't allow for multiple returns.

Unfortunately, the current approach is not particularly flexible as many things cannot be dynamic (e.g. number of return tensors, number of inputs, shapes of tensors, etc.).
I'd recommend reading about the WebAssembly Component Model and then take a look at wit-bindgen.
The component model allows you to define more sophisticated interface types and defines a canonical ABI so that Wasm modules implemented in several languages can communicate in a consistent way. This is somewhat similar to the interface definitions we were talking about in #164.
We generally want to support the same infer interface as the rest of Carton (the input is an arbitrary number of named Tensors and the output is an arbitrary number of named Tensors). This should be possible using WIT.
Can you try to get a prototype working using the component model/WIT? wasmtime has support for WIT so you shouldn't have to change runtimes.

@VivekPanyam What do you think of .wit for tensors I drafted up. And infer could just be:
infer func(in: list<tuple<string, tensor>>) -> list<tuple<string, tensor>>

or just a list of tensors.
I did consider using the component model initially, but I wasn't sure how developed tooling around it is yet.

That infer signature looks good to me and the .wit file looks good too!
One thing to note in the interface is that since you're using list<u8> or list<string>, we actually don't need strides.
In the future, ideally we'd return an address/pointer into Wasm memory for the buffer field (along with strides). That'll help avoid an extra copy in cases where the model's output isn't contiguous/doesn't have "standard" strides.
We could just make buffer a u64 or something and treat it as an offset into Wasm linear memory, but then we'd have to explicitly handle lifetimes. We can explore that as an optimization later and just stick with list for now.

@VivekPanyam What's the best way to create a Tensor from Vec<T>? Also I added 2 methods to TensorStorage, are those alright?

Finally got the runner working! Here is a recap of everything:
Summary
This PR adds 2 sub-modules, carton-runner-wasm and carton-wasm-interface.  The former implements the runner and specifies the components a model is required to implement. The latter is basically empty, but I'd like it to contain guest side implementations and conversions between Candle and Burn tensors. The motivation for this is that working with the raw component types is quite a rough experience.
Test Coverage
Host side conversions between carton and component tensors are covered for f32, u32, i32, string, and passing so I imagine they are working for all types. There is a a somewhat messy test for WASMModelInstance which is working for a basic model. The actual runner main.rs but I assume it's working since it's pretty simple.
Todo?

[ ] Guest side type conversions in  carton-wasm-interface
[ ] Reduce number of copies
[ ] Return pointer directly from wasm

Comments

Does the WIT interface require you to get a Vec as output or is there a way to get a slice? That would let you copy out of Wasm memory directly into a new Tensor.

Wasmtime will automatically copy the return into host memory via the Lift trait, vice versa with the Lower trait. Since list translates to vec you would get Vec<u8> back. So currently each infer call does 2 copies per variable: carton -> component -> wasm. As you mentioned, and I found out the hard way, there are some caveats to copyless construction of vecs, so this might be difficult.

In the future, ideally we'd return an address/pointer into Wasm memory for the buffer field (along with strides). That'll help avoid an extra copy in cases where the model's output isn't contiguous/doesn't have "standard" strides.

For handling the lifetime I think Rcing the previous output until the next infer call would probably suffice. That or introduce a callback to free it. The user has to implement the infer function though, so I'm not sure how that would work.
What are your thoughts? Is this mergeable yet?

Finally, we need to add a binary that builds a release (example), a complete test (example), and add it to CI

@VivekPanyam Done, and implemented most of the suggestions you made. Whats the best way to make it so the wasm runner is ignored when targeting wasm/wasi.

(Looks like the formatting check failed. You need to run cargo fmt)

Once you run cargo fmt and update the PR, can you

Change the PR title to remove the [WIP] and add a few words (e.g. "Initial implementation of Wasm runner")
Add a comment with what you want the commit message to be for the merged PR (normally, this is automatically set to original PR description, but that probably doesn't make sense in this case)
Mark the PR as "ready for review"

Thanks!

Appreciate the comments on using the macro. I couldn't figure it out initially, and I also didn't know you could match with macros like that. I don't want to restart CI so I can throw those changes in the next PR, or you could refactor them as well. I'll add a more detailed description in a bit.

Description
This PR adds a WASM runner, which can run WASM models compiled using the interface (subject to change #175) defined in ../carton-runner-wasm/wit/lib.wit. The existing implementation is still unoptimized, requiring 2 copies per Tensor moved to/from WASM. An example of compiling a compatible model can be found in carton-runner-wasm/tests/test_model.
Limitations

Only the wasm32-unknown-unknown target has been tested to be working.
Only infer is supported for now.
Packing only supports a single .wasm file and no other artifacts.
No WebGPU, and probably not for a while.

Test Coverage
All type conversions from Carton to WASM and vice versa and fully covered. Pack, Load, Infer are covered in pack.rs.
TODOs
Track in #164

Merged! Nice work :) :tada:


improve error messages from config validation

diff --git a/default.yaml b/default.yaml
index d101396b..812c3dd5 100644
--- a/default.yaml
+++ b/default.yaml
@@ -914,7 +914,7 @@ history:
         # you can control how they are stored here (same options as above).
         # if you enable this, strict nickname reservation is strongly recommended
         # as well.
-        direct-messages: "opt-out"
+        direct-messages: "opt-ot"

     # options to control how messages are stored and deleted:
     retention:

yields
2021/02/24 23:00:10 Config file did not load successfully: Invalid parameters

This is hard to debug!

The original case reported to us was a misspelled value of multiclient.always-on. These should get wrapped with an error that includes the bad value in its Error() string.


Latest blog articles

Use either RSS or the blog API to display the 5 latest articles on the main page of the website.

Issue closed by https://github.com/Jaedotmoe/go-jae.fi/commit/b2bdacb581087a3b8403291d99a3fc4d2fb88942.


add recyclerview support

+1

+1

Has anyone found a solution for recyclerview?

Here https://github.com/timehop/sticky-headers-recyclerview


manifest: hal_nordic: include lpcomp-int-dis-on-stop patch

Update hal_nordic manifest to include lpcomp-int-dis-on-stop patch

two sec, added reviewers to the wrong PR :)

ping @nordicjm


[7.x] Use BindingResolutionException to signal problem with container resolution

As part of static analysis sometimes abstracts get resolved which aren't
resolvable => that's totally fine but it would help to use a common
exception to signal this.
I figured BindingResolutionException would be the correct one. For example,
it's caught in cases like \Illuminate\Foundation\Exceptions\Handler::whoopsHandler
and IMHO this would also benefit from a streamlined exception.

Thanks for the PR. Please send this to 6.x. ;)

Failing GHA seems unrelated https://github.com/laravel/framework/pull/32348/checks?check_run_id=581130157#step:3:73
Error response from daemon: driver failed programming external connectivity on endpoint 3af20c2b87744521adcc4263fab1ca5f_mysql57_80d897 (478f563536e72ba97366dee1126af136172ff265b13dc5b36cc3b394dab95b82): Error starting userland proxy: listen tcp <IP_ADDRESS>:33306: bind: address already in use
Error: failed to start containers: c088a70988c15ccf147d9383148a5e68739e9d99ec3c6bb82236b826b1537ebd
##[error]Docker start fail with exit code 1


Push a new version to the forge

The latest version on the forge is adrien/network v0.4.1 from Aug 2013. There have been numerous patches since then. Can a new version be created and uploaded to the Forge? Thanks!

Dupe of #102, @igalic beat me by a few minutes cause I forgot to hit submit :(


.tech remaining items

[x] Differentiate between the before/after view when completing examples
[x] Explain significance of the action
[ ] Human-friendly URL in the tip example's URL bar

Message for self
Tip example loads indefinitely

@kauffj ^

@NetOperatorWibby it's true that you need an address or claim id when calling wallet_send (though maybe it should support full URLs cough @eukreign). But I don't understand why we can't show a more readable URL in the bar itself.

@kauffj Would it make sense to do that? Wouldn’t the end user expect to be able to use another human-readable name to tip?


XENized Jetson NANO

Curious if anyone has done XEN from meta-virtualization for the NANO. I added the package xen to my build along with virtualization. seems its built, i flash a device and ls -al /boot shows
ls -al /boot/
total 37240
drwxr-xr-x    3 root     root          4096 Mar  9  2018 .
drwxr-xr-x   19 root     root          4096 May 23 02:37 ..
lrwxrwxrwx    1 root     root            39 Mar  9  2018 Image -> Image-4.9.140-l4t-r32.3.1+g47e7e1cb0b49
-rw-r--r--    1 root     root      37257224 Mar  9  2018 Image-4.9.140-l4t-r32.3.1+g47e7e1cb0b49
drwxr-xr-x    2 root     root          4096 Mar  9  2018 extlinux
-rw-r--r--    1 root     root       2089938 Mar  9  2018 initrd
-rw-r--r--    1 root     root        214717 Mar  9  2018 tegra210-p3448-0000-p3449-0000-a02.dtb
-rw-r--r--    1 root     root        214717 Mar  9  2018 tegra210-p3448-0000-p3449-0000-b00.dtb
lrwxrwxrwx    1 root     root            63 Mar  9  2018 u-boot-dtb.bin -> u-boot-jetson-nano-qspi-sd-2016.07+gitAUTOINC+565a18c42c-r0.bin
-rw-r--r--    1 root     root        483328 Mar  9  2018 u-boot-jetson-nano-qspi-sd-2016.07+gitAUTOINC+565a18c42c-r0.bin
lrwxrwxrwx    1 root     root            10 Mar  9  2018 xen -> xen-4.12.2
lrwxrwxrwx    1 root     root            10 Mar  9  2018 xen-4 -> xen-4.12.2
lrwxrwxrwx    1 root     root            10 Mar  9  2018 xen-4.12 -> xen-4.12.2
-rw-r--r--    1 root     root        853328 Mar  9  2018 xen-4.12.2
-rw-r--r--    1 root     root          2213 Mar  9  2018 xen-4.12.2.config
So id guess the missing pieces are booting xen from u-boot ? feeling like i need a u-boot_append to write the proper config ??

Hey @outbackdingo
Did you successfully manage to resolve this issue ? if so, could please share here, I'm curious.
Thanks

while we can get xen to build for the jetson/xavier... i would need help with the u-boot booting xen piece

Hello @outbackdingo
I'm closing this issue because no updates.
I didn't have time to take a look on it.
If I will get some news about Xen with Jetson Nano I will create a discussion channel and I will tag you.


Predicate value is object doesn't work in Array.prototype.filter()

Bug Report

🔎 Search Terms

type narrowing, type predicate, value is object, filter(), lodash.isObject
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about type guards.

⏯ Playground Link

Playground link with relevant code
💻 Code

// isNumber and isObject are modeled after the functions by the same names in lodash.

function isNumber(value?: any): value is number {
  return typeof value === "number";
}

function isObject(value?: any): value is object {
  return typeof value === "object";
}

// Each element could be an object or a number, so we can't treat it as either.
const variousThings = [{ a: 1 }, 1, "abc"];
variousThings[0] + 1;
variousThings[0].a;

// Filtering for only numbers yields values we can add, but not get properties of.
const allNumbers = variousThings.filter(isNumber);
allNumbers[0] + 1;
allNumbers[0].a;

// But filtering for only object yields fails to remove number from the union type.
const allObjects = variousThings.filter(isObject);
allObjects[0] + 1;
allObjects[0].a;

// Yet isObject is able to narrow a single element in a simple conditional.
const value = variousThings[0];
if (isObject(value)) {
    value.a
}

🙁 Actual behavior
allObjects was typed as (string | number | { a: number })[], so both lines below const allObjects fail.
🙂 Expected behavior
allObjects should be typed as { a: number }[], so allObjects[0].a should pass the type checker. Notably, as seen above, isObject does manage to narrow the type of a single value with the union type to the only member of the union that's an object, it just can't narrow all of the elements using .filter() the way isNumber is able to.
I can't conceive of why they behave differently, but I also don't know the internals well. I think this difference is undesired, but I might be missing something deeper.

Ah! I understand now. The difference is that number is one of the types in the union and also the type that isNumber checks, but the object type in the union is { a: number }, while isObject checks for object in general. If you change isObject to return value is { a: number }, it works. (Though obviously that's not a reasonable definition of isObject.)
I think I have a solution, though: this alternate definition of filter (written here as filter2) should work with a predicate that checks a broader type than any elements in the union, and returns the intersection of the two broad types (the union and the type checked by the predicate).
interface Array<T> {
  filter2<S>(
    callbackfn: (value: T | S, index: number, array: (T | S)[]) => value is S,
    thisArg?: any
  ): (T & S)[];
}

(Playground)
The biggest downside I see at the moment is that the elements come out typed as { a: number; } & object. Maybe worse, the elements of allNumbers are typed as number | ({ a: number; } & number), which is rather absurd. I'm not sure why that doesn't reduce to number automatically. It's perfectly functional, though; you can still treat it as a number.
Would a PR with this as the new definition for .filter(), or something similar, be welcomed?

Your analysis is correct, and that definition for filter looks better in many ways. However, I’d be concerned that with the intersection, we’d be opening the doors for really explosive types (if your array element type is a union of 100 things, and your type predicate tells you that a type is a union of 100 other things, now you have a union of 100,000 things). I’m unsure whether there’s a good way forward with changing the lib typings. Semi-related is #36554, though that one actually doesn’t have any filter examples at the moment.

I've had the same problem with when filtering unknown[] with type guards, which current ts just ignores. Building on Peeja's solution, I arrived at a solution that also addresses an edge case that broke code reliant on inferred context, changing the src/lib/es5.d.ts override definition:
filter<S extends T>(predicate: (value: T, index: number, array: T[]) => value is S, thisArg?: any): T[]

…into two overrides that both produce (T & S)[] instead of T[]:
// make array.filter(isFoo).filter(isBar) produce Array<Foo & Bar>:

interface ReadonlyArray<T> {
    filter<S extends T>(predicate: (value: T, index: number, array: readonly T[]) => value is S, thisArg?: any): (T & S)[];
    filter<S>(predicate: (value: T | S, index: number, array: readonly (T | S)[]) => value is S, thisArg?: any): (T & S)[];
}
interface Array<T> {
    filter<S extends T>(predicate: (value: T, index: number, array: T[]) => value is S, thisArg?: any): (T & S)[];
    filter<S>(predicate: (value: T | S, index: number, array: (T | S)[]) => value is S, thisArg?: any): (T & S)[];
}

Updated version of the PR's example, re-calibrated for current typescript 5.2.2, and with another test case that broke with Peeja's first pitch: playgrounds
In other words: this problem can be addressed by this change, plus whatever test suite updates are needed.


[Spark] Add a Delta config to enable/disable the workaround of handling colons ':' in paths

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description
This PR follows https://github.com/delta-io/delta/pull/3153 and introduces a Delta config to enable or disable the workaround of handling colons ':' in paths. The value of this config is true by default.
How was this patch tested?
Existing tests.
Does this PR introduce any user-facing changes?
No, unless the user encountered any problem, which is very unlikely.

@bart-samwel could you check this one?


How to use?

How can i include this in my project? Do i need to use Node JS?

Yes, it's a node.js module

Okay thanks


How to parse dates of format DD/MM/YYYY?

In Hong Kong and Australia we do dates as 20/10/1984 meaning 20th October 1984.
How can I parse that date?

+1

Is there any update on this issue?


How to get window current status sub-seperators

In one of the screenshots on the readme there are black separators between the window number and title

i was wondering how this could be set in the .tmux.conf.local ?

Hello @dotpyfe 👋
This is an old screenshot and inserting these separators is no more automatic.
But you can still achieve the result by editing your ~/.tmux.conf.local copy:
tmux_conf_theme_window_status_format='#I \uE0B1 #W'
tmux_conf_theme_window_status_current_format='#I \uE0B1 #W'

got it - works great! thanks!


Reading from a DynamoDb index should be supported

The new dynamodb.read_items method is great, but as far as I can find, selecting an index other than the default isn't supported.  Scanning or querying an index is important functionality for DynamoDb utilization and it would be helpful if it were supported here.

Thanks @ddrinka, it's a fair ask so we will work on adding indexes


CF plugin leaves host name text field disabled in new server wizard

See the following STS JIRA for details: https://issuetracker.springsource.com/browse/STS-4024
The fix that worked for me:
if (curOldValue != curNewValue) {
   if (/NEW/ curNewValue == null /NEW/ || !!! curNewValue instanceof IServerType) {
       if (isSupportedServerType((IServerType)curNewValue)) {
						// Disable the host name field
						if (controlListener != null) {

Chunk of code between /NEW/ has been added to account for null values that can be selected (folders)

Fix pushed to master


Add ES7 class support

Hello,
I'm having some troubles in a project and decided to go on webpackbin.com to make a starter kit with es7 class support. But when I add this component I've got an unexpected token =. I can not modify the webpack configuration and I would like to use ES7.
Here a little more details :
import React from 'react';

class toto extends React.Component {
  myProp = 42;
  static myStaticProp = 21;

  constructor() {
    console.log(this.myProp); // Prints '42'
    console.log(toto.myStaticProp); // Prints '21'
  }
}
export default toto;

I found some hints here on the babel-preset-1 containing a reference to Class properties transform which is somehow related to my error :)

Ah, yes, now it uses "preset-0". I can add more presets in next release to allow you to add that stuff :)

Thanks a lot @christianalfoni let me know if you need help :)
Your webpackbin is the clearest of bins I've tryied ! great work !

Glad it has been helpful :-)

As of 13/10/2016, i'm still getting linting error with class properties and ... operator.
Would be nice to see these ES7 features added to this very nice online bin.
Keep up the good work ! Cheers.

As of 13/03/2017, i'm still getting linting error , trying to use static keyword.

Hi guys,
You can turn off linting in the settings on the profile menu on the right :)
Since it is not official stuff the linters have not implemented it, can not do anything about that, sorry :(


Support for ChromeOS

Having just discovered chromebrew, and even a prebuilt version of 'pass' for it, I thought it would be cool to add support.  Have everything needed, git, gpg, pass all tested working in a chromeOS developer shell.
I realise however that the pinentry program needed by gpg would only be able to support tty as GUI wouldn't work with chromeOS, or would it?  If not, then it would need unlocking beforehand, and maybe having the ttl cache set to last the whole session.

The honest answer is "I have no idea, maybe?..." 🙂
Would you be willing to investigate this? I can guide you as much as I can. I don't have chromeOS to test, so without you there isn't much we can do 🙂
The primary challenge I think is to find how to compile a Go binary for Chrome OS. In the makefile copy-paste the entry for browserpass-linux64, and adjust GOOS and GOARCH - we need to find the pair of values that works for ChromeOS.
https://github.com/dannyvankooten/browserpass/blob/d18ceff62f117d673cfcd96611aa26fde5f60d37/makefile#L34-L35
Once you change the values, save the file and run make browserpass-chromeos64, and test if the compiled binary works. I recommend to test using chrboe/native.pl.
The possible values for GOOS and GOARCH are listed here.

I've actually done all of this on a regular laptop with neverware cloudready on usb stick.  You can install it to hard drive or use live, I used live.  I do own Chromebook but it's been wiped and arch installed, but looking at getting another later.
Looking at the projects package list there is a Go pkg.  I will delve into it as you asked tomorrow, but if you wanna look into it, just boot usb, login as guest, ctrl alt t for terminal, type 'shell' and follow instructions on
https://github.com/skycocker/chromebrew
Really quite easy and simple.

Right, it seems to build, but I'm having trouble with native.pl
I added the 'go' package, did a go get -u 'url', edited makefile, copied the section and called it browserpass-cros64, did make browserpass-cros64 which said
'env GOOS=linux GOARCH=amd64 go build -o browserpass-cros64 ./cmd/browserpass'
I have a binary 'browserpass-cros64'.  I grabbed native.pl script, ran 'perl native.pl browserpass-cros64 {"test"}' which returned
open3: exec of browserpass-cros64 failed: No such file directory at native.pl line 95

Assuming both perl script and compiled browserpass are in the same folder, try providing relative path. I run it like this actually:
chmod +x native.pl
./native.pl ./browserpass-cros64 {"test"}

It would be very cool if GOOS=linux and GOARCH=amd64 are the values that actually work, it would mean you can just grab the release for Linux and it should work for chromeOS too, no extra effort required.

Must be a chromeos shell thing (it's bash tho), but it doesn't allow to run with "./", I have to use perl native.pl.  If I use perl native.pl ./browserpass-cros64 it givesopen3:
exec of ./browserpass-cros64 failed: Permission denied at native.pl line 95
I have permissions, it's set to +x, even sudo gives same error.  I'm about read to give up :)

I'll get back to you in an hour to try something else. In meanwhile, could you actually try to install the release for Linux and see if it works? Please take the file from #159.

AFAIK ChromeOS is based on Gentoo, so it should just work out of the box with GOOS=linux.
Regarding the native.pl thing, could you run which perl and give me the output please? @duffydack

Well, chromeOS is linux (gentoo), it's just stripped down of compiler and stuff, which chromebrew enables.
If git, gpg and pass all build and work then I can't see any reason for browserpass not to compile and work.
Tried the newer browserpass release, get "install.sh: 117: Bad substitution"

which perl = /usr/local/bin/perl
and ls -lah https://pastebin.com/Du35JLGu

which perl = /usr/local/bin/perl

That might be your issue, the script is trying to execute /usr/bin/perl. I'll try and fix that another day, but it should still work using perl native.pl.
The permission denied error is really weird, looking at your permissions it seems that everything should be good to go in that regard. Maybe something's wrong with the ChromeOS binary 🤔
Either way, it should still work with the Linux binary.
Ah, actually, I think I know what's wrong...  Can you post the output of uname -s?

uname is Linux
bash is bash 4.3.42(1)-release (x86_64-cros-linux-gnu_
I have to go for the day, I'll try more tonight if I can.  This isn't a must have feature, I don;t have another chromebook yet, hence I'm doing all this on cloudready, which is 99.999% chromeOS.
Later.

Huh, nevermind, I don't know what's wrong 😄
Alright, I'll try and investigate the install.sh issue in the meantime. Thanks for your cooperation so far 🙂

@duffydack Maybe this is related to your use case: https://stackoverflow.com/a/20616103/3691422 (even though we're using /usr/bin/env bash, but maybe ChromeOS is even mangling that).
Can you try running bash install.sh?

@duffydack another test to check that the host app works for you. Run this on a binary that you took from #159.
./browserpass-linux64 < ./request.hex.txt

request.hex.txt

Well I know that doesn't work, same as sh install.  Not near pc, can't remember what it was, something to do with HEAD, which I know it's git, but git works I know that much.

chronos@localhost ~/go/src/github.com/dannyvankooten/browserpass $ ./browserpass-cros64
bash: ./browserpass-cros64: Permission denied
chronos@localhost ~/go/src/github.com/dannyvankooten/browserpass $ sh browserpass-cros64
browserpass-cros64: 1: ELF: not found
browserpass-cros64: 5: Syntax error: "(" unexpected
chronos@localhost ~/go/src/github.com/dannyvankooten/browserpass $ go browserpass-cros64
go: unknown subcommand "browserpass-cros64"
Run 'go help' for usage.
chronos@localhost ~/go/src/github.com/dannyvankooten/browserpass $ bash browserpass-cros64
browserpass-cros64: browserpass-cros64: cannot execute binary file
chronos@localhost ~/go/src/github.com/dannyvankooten/browserpass $

Browserpass is an independent executable, it can only be executed a ./browserpass, not via sh/go/bash. I'm wondering if you are hosting this code on a partition that is mounted with noexec flag? Try running mount and check that there is no noexec flag.

Damnit, why didn't I think of that... I copied the native.pl and browserpass-linux64 to /usr/local/bin and ran...success
chronos@localhost /usr/local/bin $ perl native.pl browserpass-linux64 {"action": "search", "domain": "test"}
Request: |  {"action":"search","domain":"test"}
Result:  |  ["test","test.com"]
Errors:  |  -
chronos@localhost /usr/local/bin $ ./native.pl ./browserpass-linux64 {"action": "search", "domain": "test"}
bash: ./native.pl: /usr/bin/perl: bad interpreter: No such file or directory

Awesome! Now do you still have the issues with ./install.sh if you unpack the release archive for linux somewhere in /usr/local/bin and run ./install.sh there?

put in /usr/local/tmp and ran ./install.sh
chose chromium and chrome which made the files in /home/chronos/user/.config/NativeMessagingHosts but the extension fails to talk to host.  I don't know how chrome(ium) OS would identify the browser since it's an OS.  Getting somewhere now...

Do you have any other files in /home/chronos/user/.config/?

No, I don't think it's used the same as other Os's

So you need to find a correct folder now 🙂
Try this: locate QuotaManager-journal - it's just one of many files that I have in ~/.config/chromium/Default folder, if you find something, that is likely the correct path.

As i suspected, in $HOME (/home/chronos/user).  The partition layout and folder structure of cros is very different.  You can only see /home/chronos/user via terminal, things like Files app only show Google Drive and Downloads folder (in /home/chronos/user)

If you located the correct folder, try to put it in one of the two lines here (depends on what you select when you run the ./install.sh):
https://github.com/dannyvankooten/browserpass/blob/04199ddfd8bf6601101e252cd65ee9362d4c1e0b/install.sh#L23-L24
If that succeeds, we will add there just another entry called TARGET_DIR_CHROME_OS.

QuotaManager-journal is empty btw,     QuotaManager is a sqlite3 file

Already tried that, doesn't work..

https://stackoverflow.com/a/34462129

Chrome OS does not support third-party native messaging hosts

Disappointing... This answer is from 2015 though, maybe something changed since then...

Well that's that then!  Pity, so close.

Indeed, unfortunately! Maybe you can consider submitting a feature request for Chrome OS team?

If I can find such a page,  I'll try.  Thanks anyway


Update scenario.yaml results for nightly tests

This PR updates nightly test expected values.
It contains a subset of the changes in #669, and closes #671.
How to review

Try local execution

PR checklist

[x] Continuous integration checks all ✅

~- [ ] Add or expand tests; coverage checks both ✅~
~- [ ] Add, expand, or update documentation.~
~- [ ] Update release notes.~

Once this passes,

Sorry, didn't notice earlier: this can never pass. The "nightly" workflow uses a HTTPS username/password stored as GitHub "secrets" to download the input data for the nightly tests. This current PR is from a fork, and GHA runs from forks aren't given access to such secrets (for security reasons).
The PR should be made from a branch in the main repo → #689


Task: remove name field from systemuser v1 creation wizard

System user name sent to server in POST request should instead be set to name of chosen system name

Subtask of feature https://github.com/Altinn/altinn-studio/issues/12653


mitmproxy update breaks global state

I have an application where I need to count incoming requests, and I use global variables for that, like
myVariable=0

def responseheaders(flow):
    #do something asynchronously and update myVariable

Which stopped working when I updated to 0.18.x, because it initializes myVariable over and over for each request :(
In case this is not a bug, what would the new designated facility to keep global state instead of global variables be?

You don't give a complete example, so I can't quite tell where things are going wrong. The old, and awkward way to do this is like so:
var=0
def responseheaders(flow):
    global var
    var += 1
    print(var)

However, our addons mechanism has recently had a big facelift, and you can now do something much nicer by using an addon class:
class Addon:
    def __init__(self):
        self.count = 0

    def responseheaders(self, flow):
        self.count += 1
        print(self.count)

def start():
    # We boot into an addon returned from start
    return Addon()

In future, would you mind asking questions like this on our excellent forum so others can benefit from the answers, rather than having them disappear into the ether when we close the ticket:
https://discourse.mitmproxy.org/

Which stopped working when I updated to 0.18.x, because it initializes myVariable over and over for each request :(

If it actually re-initializes with myVariable=0 "all the time", that's a bug. In this case, we'd need a complete example to reproduce. :-)

Ok, I tried to create a minimal example, but it works as supposed. Probably it was a problem transitioning from python 2.7 to 3.


Lint raises max-len warnings.

The linter shows me max-len warnings (see below).
Should we disable that lint rule ?
$ yarn lint
yarn run v1.22.17
$ eslint --ext ts generators utils

generator-project/generators/root/index.ts
  64:1  warning  This line has a length of 131. Maximum allowed is 120  max-len
  67:1  warning  This line has a length of 156. Maximum allowed is 120  max-len

generator-project/generators/utils/database/index.ts
  45:1  warning  This line has a length of 127. Maximum allowed is 120  max-len

generator-project/utils/ansible/vault.ts
  60:10  warning  Prefer default export  import/prefer-default-export

generator-project/utils/circleci/Config.ts
  86:1  warning  This line has a length of 124. Maximum allowed is 120  max-len

generator-project/utils/circleci/Workflow.ts
  34:1  warning  This line has a length of 132. Maximum allowed is 120  max-len

generator-project/utils/circleci/mergeConfig.ts
   7:1  warning  This line has a length of 130. Maximum allowed is 120  max-len
  27:1  warning  This line has a length of 128. Maximum allowed is 120  max-len

generator-project/utils/validation/validateEmail.ts
  3:1  warning  This line has a length of 149. Maximum allowed is 120  max-len

generator-project/utils/validation/validateProjectName.test.ts
  4:1  warning  This line has a length of 134. Maximum allowed is 120  max-len
  8:1  warning  This line has a length of 126. Maximum allowed is 120  max-len

I think we should try to fix them when possible instead of disabling the rule.


Error running MSSQL image

/kind bug
Description
I needed to run this image to port this app to another DB.  Using officially provided docker command didn't work.

Click to expand

✗ podman run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=yourStrong(!)Password' -p 1433:1433 -it mcr.microsoft.com/mssql/server:2017-CU8-ubuntu
Trying to pull mcr.microsoft.com/mssql/server:2017-CU8-ubuntu...
Getting image source signatures
Copying blob 5594e4e5950b done
Copying blob b70745c852a2 done
Copying blob 4fa80d7b805d done
Copying blob 484dd0f2fbdc done
Copying blob 718060832ef2 done
Copying blob 47004b22ec62 done
Copying blob 7d648891de3f done
Copying blob 5b67719e2956 done
Copying blob e0d1b3db20c8 done
Copying blob ded313a21911 done
Copying config 229d30f7b4 done
Writing manifest to image destination
Storing signatures
^[	2020-01-13 14:08:10.45 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2020-01-13 14:08:10.55 Server      Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2020-01-13 14:08:10.55 Server      Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2020-01-13 14:08:10.56 Server      Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2020-01-13 14:08:10.59 Server      Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2020-01-13 14:08:10.61 Server      Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2020-01-13 14:08:10.65 Server      Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2020-01-13 14:08:10.80 Server      Microsoft SQL Server 2017 (RTM-CU8) (KB4338363) - 14.0.3029.16 (X64)
	Jun 13 2018 13:35:56
	Copyright (C) 2017 Microsoft Corporation
	Developer Edition (64-bit) on Linux (Ubuntu 16.04.4 LTS)
2020-01-13 14:08:10.80 Server      UTC adjustment: 0:00
2020-01-13 14:08:10.80 Server      (c) Microsoft Corporation.
2020-01-13 14:08:10.80 Server      All rights reserved.
2020-01-13 14:08:10.80 Server      Server process ID is 4124.
2020-01-13 14:08:10.80 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2020-01-13 14:08:10.80 Server      Registry startup parameters:
	 -d /var/opt/mssql/data/master.mdf
	 -l /var/opt/mssql/data/mastlog.ldf
	 -e /var/opt/mssql/log/errorlog
2020-01-13 14:08:10.81 Server      SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2020-01-13 14:08:10.81 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-01-13 14:08:10.81 Server      Detected 6129 MB of RAM. This is an informational message; no user action is required.
2020-01-13 14:08:10.81 Server      Using conventional memory in the memory manager.
2020-01-13 14:08:11.09 Server      Buffer pool extension is already disabled. No action is necessary.
2020-01-13 14:08:11.22 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2020-01-13 14:08:11.22 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
2020-01-13 14:08:11.22 Server      Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2020-01-13 14:08:11.26 Server      The maximum number of dedicated administrator connections for this instance is '1'
2020-01-13 14:08:11.26 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2020-01-13 14:08:11.27 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2020-01-13 14:08:11.28 Server      In-Memory OLTP initialized on lowend machine.
2020-01-13 14:08:11.35 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
ForceFlush is enabled for this instance.
2020-01-13 14:08:11.36 Server      Query Store settings initialized with enabled = 1,
2020-01-13 14:08:11.36 spid6s      Starting up database 'master'.
2020-01-13 14:08:11.37 Server      Software Usage Metrics is disabled.
ForceFlush feature is enabled for log durability.
2020-01-13 14:08:11.65 spid6s      The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
2020-01-13 14:08:11.65 spid6s      Error: 17053, Severity: 16, State: 1.
2020-01-13 14:08:11.65 spid6s      FCB::ZeroFile(), GetOverLappedResult(): Operating system error 997(Overlapped I/O operation is in progress.) encountered.
2020-01-13 14:08:11.65 spid6s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

I couldn't find any references of application error in image tracker https://github.com/microsoft/mssql-docker/search?q=Cannot+recover+the+master+database.+SQL+Server+is+unable+to+run.+&type=Issues and concluded that the error is caused by the podman itself.
Output of podman version:
Version:            1.7.0
RemoteAPI Version:  1
Go Version:         go1.13.5
OS/Arch:            linux/amd64

that error is coming from the container, so it can't be Podman.
Are you running as root or rootless?
In the second case it could be the interaction with fuse-overlayfs

in general I don't think you want your DB to use a FUSE file system or even overlay.  It is better to use a volume

Are you running as root or rootless?

Without sudo.


quorum wrapper

add wrappers to kvdb
add a log wrapper
add quorum wrapper.

allows setting/resetting quorum state.
in non-quorum state directly return kvdb_no_quorum error

Codecov Report

Merging #91 into master will increase coverage by 0.95%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #91      +/-   ##
==========================================
+ Coverage   68.59%   69.55%   +0.95%
==========================================
  Files           7        7
  Lines        3429     3432       +3
==========================================
+ Hits         2352     2387      +35
+ Misses        841      821      -20
+ Partials      236      224      -12

Impacted Files
Coverage Δ

common/common.go
15% <0%> (-0.59%)
:arrow_down:

etcd/v2/kv_etcd.go
68.45% <0%> (+0.32%)
:arrow_up:

etcd/v3/kv_etcd.go
67.91% <0%> (+1.51%)
:arrow_up:

consul/client.go
73.3% <0%> (+1.87%)
:arrow_up:

consul/kv_consul.go
73.03% <0%> (+1.89%)
:arrow_up:

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 3697f6c...15463a0. Read the comment docs.

Can we insert and remove a the no quorum filter in runtime - which will just unconditionally return ErrNoQuorum. The filter will be inserted when we lose quorum and removed when we regain quorum.

Can we insert and remove a the no quorum filter in runtime - which will just unconditionally return ErrNoQuorum. The filter will be inserted when we lose quorum and removed when we regain quorum.

ok, will do.


Put object failed when using IBM COS as the backend.

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug

What happened:
Put object failed when using IBM COS as the backend, and get error log like this:

What you expected to happen:
Put object succeed.
How to reproduce it (as minimally and precisely as possible):
Creat a backend using IBM Cos, and create related bucket and then upload object.
Anything else we need to know?:
Environment:

Gelato(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

It is fixed in PR#859


Keepalive pings are sent from C++ client even when keepalive is not configured

What version of gRPC and what language are you using?
client: C++
server: python/Java/C++
grpc version: 1.15.1
What operating system (Linux, Windows,...) and version?
Debian Stretch
What runtime / compiler are you using (e.g. python version or version of gcc)
g++
g++ (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
What did you do?
In the C++ grpc client there is no keepalive values configured.
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
What did you expect to see?
There should not be any keepalive pings sent from the C++ grpc client
What did you see instead?
The keepalive pings were sent every 5 minutes when the C++ gRPC client sends data or no data.
When I debugged the issue, the keepalive pings were sent based in the GRPC_ARG_HTTP2_MIN_SENT_PING_INTERVAL_WITHOUT_DATA_MS value.
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose()
problems better.
Anything else we should know about your project / environment?

The python/C++/Java gRPC servers does not have any keepalive settings configured.

client_ping_logs.txt
Note:
The attached log is taken from a python gRPC server. The server responds to the client ping for every 5 minutes (Search for logs WRITING [PING_RESPONSE]).

java_grpc_server_log.txt
The attached java server logs has the GO_AWAY error

Yes, C++ clients do send BDP pings to estimate what the flow control window should be. But, we can disable it

args->SetInt(GRPC_ARG_HTTP2_BDP_PROBE, 0);
By settings this channel argument, we would be disabling it.


Remove unused react variable in import statement

By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.
Description

Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.
Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, etc.
If the UI is being changed, please provide screenshots.

References

Include any links supporting this change such as a:

GitHub Issue/PR number addressed or fixed
Auth0 Community post
StackOverflow post
Support forum thread
Related pull requests/issues from other repos

If there are no references, simply delete this section.

Testing

Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.
Also include details of the environment this PR was developed in (language/platform/browser version).

[ ] This change adds test coverage for new/changed/fixed functionality

Checklist

[x] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[x] All active GitHub checks for tests, formatting, and security are passing
[x] The correct base branch is being used, if not the default branch

Can you elaborate? It gives me issues when checking out your changes:

Closing because lack of context and the fact that I get errors with this change.
If you believe we should merge this change, please fill in the template and provide context for the change.


Adding RowMergerTest.

A good portion of the tests in StreamingBigtableResultScannerTest were testing RowMerger functionality.  Copied those tests and translated them to be RowMerger specific.

Updated the tests.  PTAL.

LGTM


Update munit-cats-effect-3 to 1.0.7

Updates org.typelevel:munit-cats-effect-3 from 1.0.6 to 1.0.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "munit-cats-effect-3" } ]

labels: test-library-update, early-semver-patch, semver-spec-patch

Almost certainly the CI is failed because of https://github.com/typelevel/munit-cats-effect/pull/160.

It was fine on 0.3, but I'll leave this one open so we can address it here.

Sorry for the false alarm. It was a flaky test.


fix HasBoxedVariableError (warning/performance) + a few other warnings

Hi,
I made a few small fixes. Should not change the behavior, but avoid some warnings + maybe improve speed.

looks good, thanks


Added pester test guidelines for It and Context - Fixes #473

Pull Request (PR) description
Adds guidelines for It messages and Context messages to STYLEGUIDELINES.MD
Corrects Markdown rule violations in README.MD
This Pull Request (PR) fixes the following issues

Fixes #473
Fixes #511

Task list

[x] This PR changes documentation

@johlju , @mhendric, @gaelcolas - could you have a review?

This change is

@gaelcolas - can you merge this one when you get a moment? 😁


Consistentcy for Idefics

Fix message reading variable from 'x' to msg for consistency across repo
fix 'model_pth' variable to be consistent with Idefics2

With this modification, you also need to modify vlmeval/config.py

Thanks @kennymckormick for pointing out. I missed it completely.
I also saw, LlaVa has the same in-consistency so have updated the same in the PR


feat: add 'description-mentions-json' spectral rule and remove old rule

This commit adds support for a new spectral-style rule
with id 'description-mentions-json' and removes the old rule
'description_mentions_json'.
Also included are changes to tests in the validator package
to reflect the removal of the old rule.

:tada: This PR is included in version 0.4.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.56.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Fix overly strict lifetime requirements for deserialization helpers

And other improvements:

Don't deny clippy lints to avoid breakage when new lints are created
Add Key bound on Keyed::K so that we don't need to specify it on every usage

Happy to split this up into separate PRs if you prefer.

Codecov Report
Patch coverage: 66.66% and project coverage change: -0.09 :warning:

Comparison is base (3b4f224) 70.44% compared to head (48890c5) 70.36%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #291      +/-   ##
==========================================
- Coverage   70.44%   70.36%   -0.09%
==========================================
  Files         111      111
  Lines       20278    20261      -17
==========================================
- Hits        14285    14256      -29
- Misses       5993     6005      +12

Impacted Files
Coverage Δ

src/dds/key.rs
64.47% <ø> (ø)

src/dds/pubsub.rs
85.95% <ø> (-0.10%)
:arrow_down:

src/dds/with_key/datareader.rs
84.41% <ø> (ø)

src/dds/with_key/datasample.rs
40.35% <0.00%> (+2.01%)
:arrow_up:

src/dds/with_key/datasample_cache.rs
81.34% <ø> (ø)

src/dds/with_key/datawriter.rs
60.18% <ø> (ø)

src/dds/with_key/simpledatareader.rs
54.57% <ø> (ø)

src/lib.rs
100.00% <ø> (ø)

src/ros2/ros_node.rs
50.27% <ø> (+0.27%)
:arrow_up:

src/test/test_properties.rs
100.00% <ø> (ø)

... and 1 more

... and 4 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thanks. This is much appreciated. It seems that specifying trait bounds on an associated type works now better than it did ~3 years ago.

Yes, these seem to be good improvements. Thank you!


Organise problem-loading sessions

The context for this is massive and unwieldy so I've moved it into a discussion here 👉 https://github.com/CodeYourFuture/Programme/discussions/55
Acceptance criteria

[ ] Minimum of 3 problem-loading sessions are coordinated with a relevant target audience of stakeholders/key community figures before the given deadline
[ ] 2 different formats of problem-loading session are used - interactive session, panel format discussion, single expert interview
[ ] For each session, we collect relevant actionable feedback. See https://github.com/CodeYourFuture/Programme/issues/56

Owner
@Dedekind561
Stakeholders
@SallyMcGrath @kfklein15
Approvers
@MarianaVazquezCYF

@MarianaVazquezCYF We should arrange for you to observe these sessions as part of the approval of this issue

I'm taking the priority down as there is no deadline and there's been no activity for 3 weeks

Closing this since it will be picked up with other team


Docker client cannot connect after Kitematic installation (mac)

I had an older docker installation. I upgraded it via boot2docker upgrade.
I then installed Kitematic. I could run the Kitematic nginx-hello-world example. However, when I do "docker ps" I get the error:

An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.19/version: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>

I tried to regenerate config via:
boot2docker shellinit
boot2docker restart

But still the same error. What has happened and how should I correct?
Thanks!
EDIT: the docker cli installed by kitematic in

/Volumes/Macintosh_HD/Users/shauncutts/Downloads/Kitematic (Beta) 2.app/Contents/Resources/resources

works... however the one in /usr/local/bin/docker doesn't work. However, they both list the same build (0baf609) and seem to have same environment - vis:
bash-3.2$ env | grep DOCKER
DOCKER_HOST=tcp://<IP_ADDRESS>:2376
DOCKER_TLS_VERIFY=1
DOCKER_CERT_PATH=/Users/shauncutts/.docker/machine/machines/dev
(NB -- in fact, "usr/local version" had

DOCKER_CERT_PATH=/Users/shauncutts/.boot2docker/certs/boot2docker-vm

but changing didn't effect error.)
Is there some other config I'm missing? Also, why didn't "global"  boot2docker shellinit rewrite the certificates so that then the Kitematic version would break not the /usr/local version?

This is a boot2docker issue. It usually occurs whenever the boot2docker VM is restarted. There's no official fix for it yet, but you can work around the issue by adding the following file to your boot2docker VM:
/var/lib/boot2docker/profile
waitForEth1() {
  COUNT=0
  until ip a show eth1 | grep -q UP
  do
    [ $((COUNT++)) -gt 60 ] && break || sleep 1
  done
  sleep 1
}
waitForEth1

@Chekote -- thanks! -- that sounds promising... only, /var/lib/boot2docker does not exist. (checked e.g. /usr/local/var/lib as well...) Is there an alternate location? ... or if I create it there with just that in it, will it work? In general, what rule(s) does boot2docker use to find this profile?
If this is useful:
bash-3.2$ boot2docker info
{
"Name": "boot2docker-vm",
"UUID": "632dc5f1-5d05-4f0c-9605-ddf4c5973bc1",
"Iso": "/Users/shauncutts/.boot2docker/boot2docker.iso",
"State": "running",
"CPUs": 8,
"Memory": 2048,
"VRAM": 8,
"CfgFile": "/Users/shauncutts/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vbox",
"BaseFolder": "/Users/shauncutts/VirtualBox VMs/boot2docker-vm",
"OSType": "",
"Flag": 0,
"BootOrder": null,
"DockerPort": 0,
"SSHPort": 2022,
"SerialFile": "/Users/shauncutts/.boot2docker/boot2docker-vm.sock"

Another related fact:
sudo DOCKER_HOST=tcp://<IP_ADDRESS>:2376 DOCKER_TLS_VERIFY=1 DOCKER_CERT_PATH=/Users/shauncutts/.docker/machine/machines/dev docker info
works... perhaps there is something in my ~/.boot2docker or ~/.docker directories that conflicts, which is somehow overridden by the Kitematic resource files? I don't have global docker_machine installed.

I only just started messing with kitematic, and I'm also not using docker machine. I've just experienced this same issue with boot2docker before.
I've had trouble with the boot2docker instance starting up with the .100 IP address too. Whenever that happens I just stop and start it and it typically picks up the expected .103 address.
In regards to the missing directory, I'm not sure why it's not on your system. /var/lib/boot2docker is a symbolic link. This is what /var/lib looks like on my boot2docker VM:
docker@boot2docker:~$ ls -lah /var/lib/
total 0
drwxrwxr-x    3 root     staff        100 Jun 29 13:39 ./
drwxrwxr-x    9 root     staff        200 Jun 29 13:39 ../
lrwxrwxrwx    1 root     root          29 Jun 29 13:39 boot2docker -> /mnt/sda1/var/lib/boot2docker/
lrwxrwxrwx    1 root     root          24 Jun 29 13:39 docker -> /mnt/sda1/var/lib/docker/
drwxr-xr-x    4 root     root         160 Jun 29 13:39 nfs/

@shaunc it sounds like you have both boot2docker and the kitematic VM setup - You're probably looking at the previous .bashrc setup which conflicts with your current VM setup.
Here are a couple of tips to get you back on your feet:

Edit your local .bashrc or .zshrc and comment out (add #) for each DOCKER env variable
Confirm that your shell no longer has DOCKER like env via:
env | grep "DOCKER"
If any DOCKER variable exist, you can remove them via unset, like so:

$ env | grep "DOCKER"                                                                                DOCKER_HOST=tcp://<IP_ADDRESS>:2376
$ unset DOCKER_HOST
$ env | grep "DOCKER"

Now to user docker with your boot2docker vm, do the following:
$ eval "$(docker-machine env boot2docker)"

If you wanted to use the 'dev' VM as created by Kitematic:
$ eval "$(docker-machine env dev)"

The issue with shared Volumes, is that by default the VM created will mount the /Users directory - You can modify this with the VirtualBox app to point to any folder you like.

@TeckniX Thanks .. this looks promising. On first attempt:

Shauns-MacBook-Pro:xquery-rest shauncutts$ env | grep "DOCKER"
DOCKER_HOST=tcp://<IP_ADDRESS>:2376
DOCKER_TLS_VERIFY=1
DOCKER_CERT_PATH=/Users/shauncutts/.docker/machine/machines/dev
Shauns-MacBook-Pro:xquery-rest shauncutts$ unset DOCKER_HOST
Shauns-MacBook-Pro:xquery-rest shauncutts$ unset DOCKER_TLS_VERIFY
Shauns-MacBook-Pro:xquery-rest shauncutts$ unset DOCKER_CERT_PATH
Shauns-MacBook-Pro:xquery-rest shauncutts$ env | grep "DOCKER"
Shauns-MacBook-Pro:xquery-rest shauncutts$ eval "$(boot2docker shellinit)"
Writing /Users/shauncutts/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Users/shauncutts/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Users/shauncutts/.boot2docker/certs/boot2docker-vm/key.pem
Shauns-MacBook-Pro:xquery-rest shauncutts$ docker info
An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.19/info: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>

However, the other suggestion works:

Shauns-MacBook-Pro:xquery-rest shauncutts$ unset DOCKER_HOST
Shauns-MacBook-Pro:xquery-rest shauncutts$ unset DOCKER_TLS_VERIFY
Shauns-MacBook-Pro:xquery-rest shauncutts$ unset DOCKER_CERT_PATH
Shauns-MacBook-Pro:xquery-rest shauncutts$ eval "$(docker-machine env dev)"
-bash: docker-machine: command not found
Shauns-MacBook-Pro:xquery-rest shauncutts$ eval "$(/Volumes/Macintosh_HD/Users/shauncutts/Downloads/Kitematic\ (Beta)\ 2.app/Contents/Resources/resources/docker-machine env dev)"
Shauns-MacBook-Pro:xquery-rest shauncutts$ docker info
{works}

I am still confused why the first way doesn't work. Perhaps a conflict in ~/.boot2docker ?

Nope what you see there is a version issue - If you look at the version of docker within the boot2docker, I'm guessing it's different than the one on your Mac.
Getting them both to the latest version should fix this issue.

To install the global command line binaries that Kitematic uses do the following:

After this, calling eval "$(docker-machine env dev)" should work for the dev VM.
As @TeckniX mentioned, updating should fix this - the same menu command in the above image will also update your docker CLI version.


Fix signatures

<!-- Make sure you have read http://napalm.readthedocs.io/en/latest/contributing/index.html --!>

Coverage decreased (-0.3%) to 86.047% when pulling 2d8fb23bf9ce3d084c9a93ee803335d80e602831 on mirceaulinic:FIX-SIGNATURES into bf5ed178d2468d96d5bfeab0bc91aedad9310df1 on napalm-automation:develop.

+1

Coverage increased (+0.02%) to 86.357% when pulling b3e86fba3e2efbc8824e9630650c5cbcc94bd5c3 on mirceaulinic:FIX-SIGNATURES into bf5ed178d2468d96d5bfeab0bc91aedad9310df1 on napalm-automation:develop.


View templates: fix form.select syntax (with class)

To reproduce: go to your account preferences, select the Amanita theme, and reload the page. Preference selects are not really very legible; insufficient contrast.
Diagnosis:
In the view templates, form selects (in user prefs and elsewhere) correctly specify the Bootstrap class: "form-control", but the class attribute is not created in the HTML, due to incorrect syntax in the erb tag. Result: the select options are not very legible; the text color is incorrectly inherited from the parent element.
Fix: The form.select helper requires two options hashes. The class has to be in the second hash, rather unintuitively. (Someone seems to have discovered this already, because views/name/form_name.html.erb already had the correct syntax.)

Coverage remained the same at 92.633% when pulling 55215ec1c7b9e3d68f191002da7fdbfb7c44342e on nimmo-form-selects into 462bf35db7b30b48d3c6fe845a13c4774ec7fec0 on master.

This is preliminary to the other SCSS consolidation PR. Will merge today, if no objections
Let me know if your select elements appear wacky, wonky, or otherwise. They shouldn't be.
Note: if you don't feel comfortable reviewing SCSS, the easy way to review these PRs is to simply navigate to the page affected and note any front-end changes vs master. The change here just fixes a long-term legibility bug in the Amanita theme, which apparently nobody noticed until now because i'm the only one using Amanita. (Blame "Amanita Rita" aka MO user Debbie Viess!)


[DAO] Combining Consensus Parameters for cfund % and rewards

The current setup has these two parameters set separately. But since these two parameters are coupled, it is suggested that we somehow combine these two parameters into 1 consensus item that has two parameters so they can be changed at the same time.
For example, in the current setup, if we want to increase cfund distribution to 1 NAV per block while keeping the reward of 2 NAV per block, we will have to change the reward to 3 NAV per block at the same time increasing the percentage to 33%. In this scenario, there is no guarantee that the two consensus changes will be both approved. If only one is approved, the result would be less than ideal.

this is an interesting upgrade, which would require a bit of reengineering of how things work internally. adding a bounty and will add later some ideas on how it could be implemented

How about this is defined by JSON and parsed at startup
{"reward":[{"block":0,"CFUND":0.5,"STAKE":2}]}
The above would be the initial definition based on the new scheme.  The 0 would just mean from when current staking rewards started.
It would allow a reward scheme to be built such as the below example in JSON and a maximum supply hard limit set
{"reward":[{"block":0,"CFUND":0.5,"STAKE":2},{"block":6000000,"CFUND":0.25,"STAKE":1},{"block":7000000,"CFUND":0.125,"STAKE":0.5},{"block":8000000,"CFUND":0.1,"STAKE":0.4}],"max_supply":170000000}
This would change the reward at block 6 million, 7 million and 8 million after that the reward would remain the same until the maximum supply limit of 170000000 was reached.  Obviously as that limit approached the scheme would need to be updated.  This is not how I expect the initial definition to be defined it will just be 2 stake and 0.5 community fund like it is now.
Obviously not as easy to parse JSON in C++ but can be done.  Probably some sort of web interface to parse the JSON and generate the CLI command required should be developed at the same time.
This would be a good but challenging first change for me!

first of all, what you propose is out of the topic of this issue. here OP proposed to combine two consensus parameters into one, which makes sense, as currently the approval of one of the inflation related parameters does not imply the approval of the other while both affect the inflation and normally people would vote with both on mind.
for what you propose, id suggest to gather enough support from the rest of the community before starting the work. once you think the network would approve the fork, then the change is very easy.
see GetFundContributionPerBlock and GetStakingRewardPerBlock in main.cpp. they would look like something like this:
uint64_t GetStakingRewardPerBlock(const CStateViewCache& view)
{
    if (!forkActive)
    {
        return GetConsensusParameter(Consensus::CONSENSUS_PARAM_GENERATION_PER_BLOCK, view) - GetFundContributionPerBlock(view);
    }
    else
    {
         if (mapBlockIndex.count(view.GetBestBlock()){
             CBlockIndex* pindex = mapBlockIndex[view.GetBestBlock()];
             if (pindex->nHeight < 1000000)
                return 2*COIN;
             else if (pindex->nHeight < 2000000)
                return 1.5*COIN;
         }
    }
}

Something similar for GetFundContributionPerBlock would be necessary.

There is no fork here.  The change combines community fund and staking rewards into a single JSON defined parameter and staking reward and community fund amounts remain unchanged.
The example of the possibility that using JSON allows offering tiered reward and community fund amounts based on block is an example of what this change facilitates.  Such a change would as a minimum require a consultation before making such a change to the JSON and would result in a fork when the values change from current and not before.  But the code change to support it does not change consensus unless the JSON defining it changes.
The intention is to develop the JSON defined community fund and staking reward of {"reward":[{"block":0,"CFUND":0.5,"STAKE":2}]} which requires no fork and does not change consensus in any way.  Update code for the change of the new combined consensus parameter via DAO and update or have updated the block explorer to support it.


sql_dialect / dialect/ target?

Previously our header used dialect, like:
prql dialect:postgres

Now we use sql_dialect
prql sql_dialect:postgres

I was thinking through the semantics of how something like https://github.com/PRQL/prql/issues/1369 would work.
It could be prql python_dialect:xarray. But then we have two parameters that can't be used together, rather than just one parameter. Should it instead be more general, something like:
prql target:sql.postgres

and then #1369 would use
prql target:python.xarray

While I don't expect we'll have any target apart from SQL soon (#1369 is highly speculative!), 0.4 is a breaking change, so if we want to change it, doing so now would avoid another breaking change later.

Good idea, I concur.


Installing ESP-IDF extension python packages fails through the vscode extension if windows user has space in name (IDFGH-8259)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v4.4.2
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
No response
What is the expected behavior?
Install completely using the express instalation.
What is the actual behavior?
It fails to install due to space being present in user path
Steps to reproduce.
Install express via vscode extension on a windows machine and on a user with space in name
Build or installation Logs.
No response
More Information.
No response

You should probably open the issue in the vscode extension repository instead.
The ESP-IDF has of yet to support spaces in PATH as mentioned in the documentation.


Backbone 1.1.2 is available, please update

Hello
Could you please update to 1.1.2?
https://github.com/jashkenas/backbone/commit/53f77901a4ea9c7cf75d3db93ddddf491998d90f
Thanks!

See #12.


Prometheus metric for prover errors

This needs more discussion, and protocol to help with it

Since we are not running any block producers or snark workers, we'd have to add this to node-status(telemetry). The daemon could keep track of any blockchain snark errors and include that in the node-status output.
For snark work failures, we currently crash when prover errors occur. We'll have to change that to return the error to the daemon, keep track of it and include it in the node-status output.
Are we ok taking these changes as hotfix?
There is an alternative to observe transaction snark failures and that is to run snark workers with a new key and fee < account-creation-fee so that snarks are generated but don't get broadcasted. I can add snark-worker container crashes to the existing alerts


Azure SQL Code Modifications and Integration Tests Added

update setup.py to include dependencies

@mpurusottamc made necessary changes. lemme know


BuildCraft machines not connecting

BuildCraft machines don't connect to Universal Cable, Forestry machines do.
Forestry build 30, Mekanism build 75, BuildCraft 6.0.17

Cable still doesn't connect to BuildCraft machines.
Minecraft: 1.7.10
Mekanism: 8.1.5 (All addons have the same version)
BuildCraft: <IP_ADDRESS>
Forge: <IP_ADDRESS>2-1.7.10


Share data directly between Fragment and Service

Instead of subscribing to every detailed update, the fragment now
shares data directly with the service and receives notices when
any data has changed.  This simplifies the interactions between the
two, paving the way for a shared Collection (when we integrate the
collections library).
One aspect of this change is that it replaces the fragments
mPwoMetadataQueue with an mUrlQueue.  This is simplier for checking
whether new urls are already stored in the queue, but it also will
allow us to access the most appropriate metadata at the time of
display, as opposed to at the time of placing the data into the
queue.

lgtm


Update third_party/go/src/github.com/golang/protobuf to commit dda510ac0fd43b39770f22ac6260eb91d377bce3 [phab:D802]

Created by schroederc at 2016-03-30 22:25:11:

zarko accepted this revision at 2016-03-30 22:29:40

schroederc closed via commit e481d6977777d04016cc767318054211b2d5435e at 2016-03-30 22:30:07


Queue unresolved contracts past their proof deadline

Changes PruneStaleStorageObligation to also queue action items for any unresolved contracts past their proof deadline when starting the host.
Works around #6. The host from the issue has 487 unresolved contracts past their proof deadline. This will trigger data cleanup and mark those contracts as failed.

nice!

nice! Is this sufficient to close #6, or is there more work to be done?

Yeah, this should be enough to close #6, but it won't fix the underlying issue with the contracts not resolving. I'm not sure how long that would take to find and fix. It might be a good idea to open a tracking issue for all the little Host bugs.

Contracts not being resolved
Lockups
Financial tracking


Add topology cluster yaml to create a vanilla cluster for BYOH using cluster class

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Related to #487
Anything else you would like to add:
[Miscellaneous information that will assist in implementing the feature.]
Environment:

Cluster-api-provider-bringyourownhost version:
Kubernetes version: (use kubectl version --short):
OS (e.g. from /etc/os-release):

/assign @shivi28


⚠ Mobitopup has degraded performance

In bec4fbd, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 5508 ms

Resolved: Mobitopup performance has improved in edbecfb after 415 days, 9 hours, 53 minutes.


Formatting differences between copy cell/selection

In response to some customer confusion, we thought it would be prudent to record this design decision.
Copy value will copy an unformatted value such that it can be formatted however the user wishes in a different program.
Copy selection will copy values based on the column's formatter to ensure that it matches the designed output when pasted into another program.
(internal tracking ICM 238532161)

@yelper : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add Travis CI

For each commit CI should build the project and run unit tests, and eventually do linting and other things.

Based on offline discussion, it seems like GitHub Actions might be an easier option, if we switch to Conan.


"Scan a shared QR code" text consistency and add? help text?

For the "Scan a shared QR code" function from the Bottom Nav Share screen, text should be consistent between the Share screen and QR code Scanner screens. Not sure which is better.
Also, recommend adding a one sentence help text as to what this is / how it's supposed to be used.
Bottom Nav Share Screen (left) and QR code Scanner Screen (right)

Why is the scan function apart of the "share" menu if the purpose of the scan is to view or import a credential (not share one from the users perspective).


ValueError: Exception while processing img1_path

Before You Report a Bug, Please Confirm You Have Done The Following...

[X] I have updated to the latest version of the packages.
[X] I have searched for both existing issues and closed issues and found none that matched my issue.

DeepFace's version
0.0.92
Python version
3.8
Operating System
No response
Dependencies
Package                      Version     Editable project location

absl-py                      2.1.0
asttokens                    2.0.5
astunparse                   1.6.3
backcall                     0.2.0
beautifulsoup4               4.12.3
blinker                      1.8.2
cachetools                   5.3.3
certifi                      2024.6.2
charset-normalizer           3.3.2
click                        8.1.7
comm                         0.2.1
debugpy                      1.6.7
decorator                    5.1.1
deepface                     0.0.92      /nfs1/56dev/root/dxj/jike/deepface
executing                    0.8.3
filelock                     3.14.0
fire                         0.6.0
Flask                        3.0.3
flatbuffers                  24.3.25
gast                         0.4.0
gdown                        5.2.0
google-auth                  2.30.0
google-auth-oauthlib         1.0.0
google-pasta                 0.2.0
grpcio                       1.64.1
gunicorn                     22.0.0
h5py                         3.11.0
idna                         3.7
importlib-metadata           7.0.1
ipykernel                    6.28.0
ipython                      8.12.2
itsdangerous                 2.2.0
jedi                         0.18.1
Jinja2                       3.1.4
jupyter_client               8.6.0
jupyter_core                 5.5.0
keras                        2.13.1
libclang                     18.1.1
Markdown                     3.6
MarkupSafe                   2.1.5
matplotlib-inline            0.1.6
mtcnn                        0.1.1
nest-asyncio                 1.6.0
numpy                        1.24.3
oauthlib                     3.2.2
opencv-python                <IP_ADDRESS>
opt-einsum                   3.3.0
packaging                    23.2
pandas                       2.0.3
parso                        0.8.3
pexpect                      4.8.0
pickleshare                  0.7.5
pillow                       10.3.0
pip                          24.0
platformdirs                 3.10.0
prompt-toolkit               3.0.43
protobuf                     4.25.3
psutil                       5.9.0
ptyprocess                   0.7.0
pure-eval                    0.2.2
pyasn1                       0.6.0
pyasn1_modules               0.4.0
Pygments                     2.15.1
PySocks                      1.7.1
python-dateutil              2.9.0.post0
pytz                         2024.1
pyzmq                        25.1.2
requests                     2.32.3
requests-oauthlib            2.0.0
retina-face                  0.0.17
rsa                          4.9
setuptools                   69.5.1
six                          1.16.0
soupsieve                    2.5
stack-data                   0.2.0
tensorboard                  2.13.0
tensorboard-data-server      0.7.2
tensorflow                   2.13.1
tensorflow-estimator         2.13.0
tensorflow-io-gcs-filesystem 0.34.0
termcolor                    2.4.0
tornado                      6.3.3
tqdm                         4.66.4
traitlets                    5.7.1
typing_extensions            4.5.0
tzdata                       2024.1
urllib3                      2.2.1
wcwidth                      0.2.5
Werkzeug                     3.0.3
wheel                        0.43.0
wrapt                        1.16.0
zipp                         3.17.0
Reproducible example
result = DeepFace.verify(
  model_name = "Facenet512",
  img1_path = "/nfs1/56dev/root/dxj/jike/data/tom/tom_3.jpg",
  img2_path = "/nfs1/56dev/root/dxj/jike/data/tom/tom_5.jpg",
)

Relevant Log Output
(face_test) (base) root@bigdata-gpu01:/nfs1/56dev/root/dxj# /root/anaconda3/envs/face_test/bin/python /nfs1/56dev/root/dxj/jike/test.py
2024-06-11 04:15:42.308968: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-06-11 04:15:44.082942: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2024-06-11 04:15:48.289210: W tensorflow/core/common_runtime/gpu/gpu_bfc_allocator.cc:47] Overriding orig_value setting because the TF_FORCE_GPU_ALLOW_GROWTH environment variable is set. Original config value was 0.
2024-06-11 04:15:48.289269: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1639] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 18011 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 3090, pci bus id: 0000:03:00.0, compute capability: 8.6
2024-06-11 04:15:48.289831: W tensorflow/core/common_runtime/gpu/gpu_bfc_allocator.cc:47] Overriding orig_value setting because the TF_FORCE_GPU_ALLOW_GROWTH environment variable is set. Original config value was 0.
2024-06-11 04:15:48.289882: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1639] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 21883 MB memory:  -> device: 1, name: NVIDIA GeForce RTX 3090, pci bus id: 0000:04:00.0, compute capability: 8.6
2024-06-11 04:15:49.511652: W tensorflow/tsl/framework/cpu_allocator_impl.cc:83] Allocation of 411041792 exceeds 10% of free system memory.
2024-06-11 04:15:50.053616: W tensorflow/tsl/framework/cpu_allocator_impl.cc:83] Allocation of 67108864 exceeds 10% of free system memory.
2024-06-11 04:15:50.167234: W tensorflow/tsl/framework/cpu_allocator_impl.cc:83] Allocation of 42958848 exceeds 10% of free system memory.
Traceback (most recent call last):
File "/nfs1/56dev/root/dxj/jike/deepface/deepface/modules/verification.py", line 130, in verify
img1_embeddings, img1_facial_areas = __extract_faces_and_embeddings(
File "/nfs1/56dev/root/dxj/jike/deepface/deepface/modules/verification.py", line 239, in __extract_faces_and_embeddings
img_objs = detection.extract_faces(
File "/nfs1/56dev/root/dxj/jike/deepface/deepface/modules/detection.py", line 96, in extract_faces
raise ValueError(
ValueError: Face could not be detected in /nfs1/56dev/root/dxj/jike/data/tom/tom_0.jpg.Please confirm that the picture is a face photo or consider to set enforce_detection param to False.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/nfs1/56dev/root/dxj/jike/test.py", line 4, in
result = DeepFace.verify(
File "/nfs1/56dev/root/dxj/jike/deepface/deepface/DeepFace.py", line 144, in verify
return verification.verify(
File "/nfs1/56dev/root/dxj/jike/deepface/deepface/modules/verification.py", line 141, in verify
raise ValueError("Exception while processing img1_path") from err
ValueError: Exception while processing img1_path
Expected Result
in verification.py, line 239 ~247
img_objs = detection.extract_faces(
img_path=img_path,
detector_backend=detector_backend,
grayscale=False,
enforce_detection=enforce_detection,
align=align,
expand_percentage=expand_percentage,
anti_spoofing=anti_spoofing,
)
in process of  debug, find the variable img_objs = [].   my pictures is :

How to solve it?
What happened instead?
get correct verity result
Additional Info
I have used vgg, facenet512

Exception message is clear, this is not a bug.


add BurntSushi/cargo-benchcmp

utility to compare Rust micro-benchmarks

Happily accepting any project by BurntSushi. ;) Thank you.


secretary segfaults on macOS 10.13 Beta (17A352a)

on macOS 10.13 Beta (17A352a) the latest secretary binary is segfaulting:
salimane at Salimanes-MacBook-Pro (git:salimane.com)  in ~/src/project
± echo -n "my_lovely_password" | ../../secretary encrypt
zsh: done                echo -n "my_lovely_password" |
zsh: segmentation fault  ../../secretary encrypt

With go 1.9 build , the issue is gone, hence #21

now using 1.9.2 of golang in travis builds