cargo-binstall feature did not work for me on Codespaces

This is my devcontainer.json:
{
	"name": "Rust",
	"image": "mcr.microsoft.com/devcontainers/rust:1-1-bullseye",

	// Features to add to the dev container. More info: https://containers.dev/features.
	"features": {
		"ghcr.io/lee-orr/rusty-dev-containers/cargo-binstall:0": {}
	},
}

When  I try to use cargo binstall in a Github Codespace built with that config, it doesn't work:
$ RUST_LOG=debug cargo-binstall nextest
ERROR Fatal error:
binstall::io

   × I/O Error: Permission denied (os error 13)

Update: I'm starting to realize that it's meant to be used with the "packages" option to get packages while the container being built. I haven't tested whether that works. However, this isn't documented anywhere, and in any case I wish it would also work from the command line.
For now, as a workaround to this and #15, I add the following line to devcontainer.json based on cargo-binstall's README:
"postCreateCommand": "curl -L --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/cargo-bins/cargo-binstall/main/install-from-binstall-release.sh | bash",

I will also probably add  && cargo binstall cargo-insta cargo-nextest to that line.

Thanks for posting this! I will be able to look at it tomorrow.

Just released a new version that should resolve this - but please let me know if there's still issues.


Migrate from snarkyjs to o1js

Hi @maht0rz ,
Are these issues available to work on by anyone ?
If yes, can you please share more detail on what needs to be done?
I would like to understand the project better and contribute from my end.
Thank You


Stack overflow when injecting content into SystemTextJsonOutputFormatter in preview8 (used to be ok in preview6)

Describe the bug
Getting a StackoverflowException when injecting content into the output formatter
To Reproduce
Steps to reproduce the behavior:

Using ASP.NET Core 3.0-preview8
Create a middleware as follows:

public async Task InvokeAsync(HttpContext context,
  OutputFormatterSelector selector,
  IHttpResponseStreamWriterFactory writerFactory) {
  ...
  context.Response.StatusCode = (int)statusCode;
  var response = new ErrorResponse { ... };
  var formatterContext = new OutputFormatterWriteContext(
    context, writerFactory.CreateWriter, typeof(ErrorResponse), response);

  var selectedFormatter = selector.SelectFormatter(formatterContext, Array.Empty<IOutputFormatter>(), new MediaTypeCollection());
  await selectedFormatter.WriteAsync(formatterContext);
}

Add the middleware to the pipeline
When running a request through, I get Stack overflow. in the console and the server crashes.

Expected behavior
Response reaches the client and server continues to run.
Additional context
.NET Core SDK (reflecting any global.json):
Version:   3.0.100-preview8-013656
Commit:    8bf06ffc8d
Runtime Environment:
OS Name:     ubuntu
OS Version:  18.04
OS Platform: Linux
RID:         ubuntu.18.04-x64
Base Path:   /usr/share/dotnet/sdk/3.0.100-preview8-013656/
Host (useful for support):
Version: 3.0.0-preview8-28405-07
Commit:  d01b2fb7bc
.NET Core SDKs installed:
2.2.300 [/usr/share/dotnet/sdk]
3.0.100-preview6-012264 [/usr/share/dotnet/sdk]
3.0.100-preview8-013656 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.2.5 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.5 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0-preview6.19307.2 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0-preview8.19405.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.5 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview6-27804-01 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview8-28405-07 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
This used to work in preview6.

Thanks for contacting us, @marono
@pranavkm can you please look into this? Thanks!

@marono do you have a stack trace?

@pranavkm unfortunately not. That's literally all I get in the console before crashing (Stack overflow.). Tried various ways of catching the exception but none worked (debugger attached and stepping through, handling first chance exception on the AppDomain).
If you can't reproduce it quickly, I could try and provide a sample.

A sample sounds great. When debugging, if you get as far as selectedFormatter.WriteAsync, it's fairly likely that the stack overflow comes from the serializer. In which case,
a) could you include the model type (ErrorType)
b) the data in ErrorType. Try using Newtonsoft.Json to serialize the model.

Hey, I can confirm that in debug mode, WriteAsync is the last line I can reach.
Here's my ErrorResponse model, there's recursion in it:
public class ErrorResponse {
    public IEnumerable<Error>? Errors { get; set; } = null;
  }

  public class Error {
    public string Code { get; set; } = string.Empty;
    public string Description { get; set; } = string.Empty;
    public IEnumerable<Error>? InnerErrors { get; set; } = null;
    public Dictionary<string, object> Meta { get; set; } = new Dictionary<string, object>();
  }

If this is still not enough to investigate, I will spend some time tomorrow providing a sample.

Could you provide the data? I'm unable to reproduce a stackoverflow with the model, I suspect something the data might be the source of the issue.
/cc @ahsonkhan @steveharter

This look like a duplicate from https://github.com/dotnet/corefx/pull/39936 which was recently fixed. That issue related to cycles\recursion in a model that uses collections, like the model in this issue (ErrorResponse.Errors->Errors.InnerErrors->ErrorResponse)

Thanks @steveharter, in that case, it will be available in preview 9.

Try this https://github.com/marono/aspnet-stack-overflow. Didn't get to test it with preview9 yet, will do so next ...

Preview9 is working fine https://github.com/marono/aspnet-stack-overflow/tree/preview9 .
I'm closing the issue now, thanks for the help and quick replies


Fix: avoid casting Locator's to strings, use ->toAttribute instead.

(Directly casting to string gives garbled attributes like "LaTeXML::Common::Locator=HASH(...)")

This needs an extra sanity check that the result of ->getProperty is defined before calling ->toAttribute, or it would incur a Fatal error in the cases where no locator is available. You could for example write that as:
  if ($trailer) {
    if (my $locator = $trailer->getLocator) {
      $trailer = $locator->toAttribute; } }

I've been away from the project space for quite some time, and was just doing quick reviews, but since you made two PRs I tried to investigate why the Travis CI builds now fail, which lead me down a rather deep rabbit hole...
Long-story short, some dust had settled w.r.t to the Travis deploys, which I just cleaned up in #122 . I incorporated your upgrades from this PR (and extended them to another routine of interest), so I will close this PR and merge there. I recommend rebasing your master to upstream, and we can continue removing what's rest of the cruft.
Since I recall some contributors may be new to GH, what you'd like to do from a terminal is:
git checkout master
git pull --rebase
git checkout your-local-dev-branch
git rebase master

to sync any local feature branches with master updates.


Extract production consumption metrics per-app to support chargeback modelling

Is your feature request related to a problem? Please describe.
We want to provide enough snapshot metrics to allow a chargeback model to be built/derived. The first phase will break down per-topic-partition snapshot of the number of 'records' at the current offset.
Describe the solution you'd like
the ability to one-shot execute the code to extract current topic-partition-offset starts at time 't'.
Further augmentation will capture per-topic-bytes (similar to kafka.admin.LogDirsCommand) - from which the average record size can be calculated. Compacted topics are problematic and
Additional context
We need a simple method that captured sufficient cluster/topic/consumer metrics to build chargeback modeling. The first phase is to calculate topic-partition level records, and derive record size. From this - throughput and volume can be derived. Compacted topics are problematic and may require segment investigation
@big-andy-coates  - wdyt?

Arguably many more important things to work on first.
That aside, like good.
The admin api provides some info on log dirs on each broker. Might be enough to build a picture of disk utilisation and message rates.
Message rates and data sizes would allow for basic charge back model.
However... This is moving more into cluster monitoring, which is far away from SpecMesh core value IMHO.

As discussed - we want to be aligned with a data-product product (primarily around public topics) and their utlisation, so it sits on the specmesh modeling semantic, along with topological views, and observability... ;)

Left open until the doc task is complete


make cargo espflash work by adding a partition.csv

For running the examples we are using cargo espflash. By default cargo espflash will be using the partition.bin created inside esp-idf-sys ( espflash by default will use its own. The problem is that the default esp-idf-sys partition has only a 1MB big AppPartition size. All sdkconfig options for using different sized partitions only lead to a max AppPartition to 1.5MB and this is still to less for an wifi example with debug infos. So the simplest / cleanest solution is to simply provide one with the configuration file-

I think we need this for esp-idf-hal as well, no? And for esp-idf-sys?

i

I think we need this for esp-idf-hal as well, no? And for esp-idf-sys?

yeah already pushed

Thanks!


portico: Fix multiple landing pages broken.

Since postcss tries to preserve specificity of selectors which are defined in in a group, a :not(#does-not-exist) selector was added to the non ID selectors (solutions-page and case-study-page).
This caused the CSS styles to override other styles due to unexpectedly increased specificity.
To fix it, we remove the ID selector #why-zulip-page from the group.

Merged, thanks @amanagr!


Add support for tmpfs mounts on Docker runtime

As opposed to volumes and bind mounts, a tmpfs mount is temporary, and only persisted in the host memory. When the container stops, the tmpfs mount is removed, and files written there won't be persisted.
This is useful to temporarily store sensitive files that you don't want to persist in either the host or the container writable layer.
Limitations:

Unlike volumes and bind mounts, you can't share tmpfs mounts between containers.
This functionality is only available if you're running Docker on Linux.

The goal of this issue is to add support for a tmpfs mount.
Rough outline of the implementation:

Add an tmpfs.go file to the docker packge.
Implement the Mounter interface.
Register the new mounter implementation when wiring in the Docker runtime.
Add tests.

https://github.com/runabol/tork/pull/211


[DOC] Update docs for 24.04.0 release [skip ci]

This PR updates download docs for 24.04.0 release.
Signed-off-by: Suraj Aralihalli<EMAIL_ADDRESS>

build


Implement 2D instance shader parameters

Rebased from @KoBeWi 's PR #77594
I also fixed it, so it actually works, although I am not entirely sure the code I wrote is fine, if someone from rendering could comb over it I'd be thankful.
Original PR text:
Closes #62943
I wrote this a while ago and decided to rebase and test it again now. This seems to work the same as in 3D (no wonder, since it's a 1:1 copy-paste), i.e. the parameters appear in the inspector, they have correct default value etc.
The only problem is that changing the parameter has no effect. It always uses the default for the given type (not even the defined default). But it's probably the only missing bit, so if anyone can help, the feature would be finished.

Okay, I just realised I didn't actually get it to work, I think a redesign of canvas.glsl is needed because there's no space in the push constant to fit an instance ID, if it's fine i'll take a look at making it work like scene.glsl does.

there's no space in the push constant to fit an instance ID

I dont know much about rendering, but you are talking about this https://github.com/godotengine/godot/pull/80458, right?

there's no space in the push constant to fit an instance ID

I dont know much about rendering, but you are talking about this #80458, right?

Yes, exactly, lol, i'll just wait for that to get merged then

This is a great first step towards adding support for instance shader parameters.
The missing piece is mapping the instance id to the global array. Here is what that looks like in the Forward+ renderer:
https://github.com/godotengine/godot/blob/a9bb8509f2faac81bdb995c6c89a5347372f3498/servers/rendering/renderer_rd/forward_clustered/scene_shader_forward_clustered.cpp#L728
As you pointed out, there isn't room for that extra parameter in the current approach because push constants have such a limited size. That being said https://github.com/godotengine/godot/pull/80458 isn't really a full solution either as we will run into cache alignment issues if we start using a SSBO but then use 132 bytes for each instance

As you pointed out, there isn't room for that extra parameter in the current approach because push constants have such a limited size. That being said #80458 isn't really a full solution either as we will run into cache alignment issues if we start using a SSBO but then use 132 bytes for each instance

What about moving something less important from the push constant to the instance buffers?
In the case of canvas items, does specular_shininess need to be there? That feels like something that should be part of shaders that have specular enabled, creating a shininess per-instance variable. (and can't imagine many people are using specular on their canvases in the first place...)
With that removed, there'd be room for the instance index, keeping the struct 128 bytes.
But I don't have much of a grasp on how this part of the engine works, just wondering!

Hello, any news about that ? Instance uniforms are a must for anyone making a vampire survivor's like game.


menus-section popup window leaves traces of itself on second click

Clicking twice on the 3 vertical dots in the example page leaves traces of the popup window with Firefox 47 on Linux. See screenshot:

Distribution is Ubuntu 14.04, if that matters.

This bug also occurs in the elm clone, see: https://github.com/debois/elm-mdl/issues/83

Created bug for Mozilla Firefox, see https://bugzilla.mozilla.org/show_bug.cgi?id=1288059

This bug is still present for me in Firefox 47.0.1 on Linux x86_64.

I can confirm this. Firefox 47.0 on Ubuntu 15.10. Even if this is a bug in Firefox, we should find a solution for this issue.

I can also confirm this for Firefox 48.0 on Windows 10 (1607) and Windows 8.1

This has worked previously and we haven't changed the functionality of the menu. Therefore this is a regression in Firefox. Please file a bug with them so they can address this internally.
If they WONTFIX a report about the root cause of this, then we can assess at that time whether we should work to address this internally. At which point we can re-open this issue if we will handle patching it in v1.
Thank you.


chore: Update copyright year

In the CommonAssemblyInfo.

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

v1.8.1
GitHub release

Your semantic-release bot :package::rocket:

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

v1.8.1
GitHub release

Your semantic-release bot :package::rocket:


Register to Login on Successful Registration

Once a user registers successfuly, Go to Login after displaying message

Finished adding changes


Fix patch generation script

Relates to #1030.

Let me do some more tests before merging it. ;)

Suuuuure. Is this PR closes issue completely which includes injecting comments also?

@kwonoj Not yet. I'll add some commits injecting the comments.

@kwonoj Now it's complete. ;)

@kwonoj Just updated the PR addressing you comments.

I think change's good, thinking which changes should be checked in first between https://github.com/ReactiveX/RxJS/pull/1077 and this. Still need some comment update from those PR regarding patch operators.

I think it doesn't make a difference which one gets merged first. If it is necessary to keep the change regarding the patch operators on #1077, it will require a separate PR to change the generator script.
What do you think?

I think it doesn't make a difference which one gets merged first.

: Yes I agree, just work order in my preferences :)

Given the size of #1077, maybe it would be better to merge it first as is. Then I can rebase and update this PR.

I'll update this PR as soon as #1091 gets merged.

@luisgabriel , PR #1091 's checked in to allow this PR can be updated. Thanks for take care of those. Let me mark as blocked for now to avoid possible confusions.

Thanks, @kwonoj! I'll rebase and update this PR tomorrow.

Just updated this PR. Now it includes also pairwise, race and let that were recently checked in.

Merged with 5e43f14, appreciate for effort @luisgabriel :)


why does this code is required?

if task in ["track", "vos"]:
         # build dummy dataset for purpose of dataset setup (e.g. caching path list)
         logger.info("Build dummy AdaptorDataset")
         dummy_py_dataset = AdaptorDataset(
            task,
            cfg,
            num_epochs=cfg.num_epochs,
            nr_image_per_epoch=cfg.nr_image_per_epoch,
            seed=seed,
        )
        logger.info("Read dummy training sample")
        dummy_sample = dummy_py_dataset[0]  # read dummy sample
        del dummy_py_dataset, dummy_sample

Hi, i read your code, but i can't understand the code here, Isn't it redundant here?

Hope you can reply me,  thank you!~~ :-)

@lzx1413

@zxyyxzz  Please paste the link to starting line here so that I can trace to the context of this block easily.
From this stage, I can only guess that some static class members will be initialized when the first object is instantiated, and this is required before the instantiation of the first real dataset. So a dummy object is built here just for initialization.
Specifically, the following comment line in the code explains the using purpose:
build dummy dataset for purpose of dataset setup (e.g. caching path list)

Closed as no further discussion. Feel free to reopen it again.


[perf]: initial load testing fiindings

During first load tests we had some first findings we need to investigate. The results of the tests can be found in the comments below.
The tests first create a user per VU (virtual user) and then sign in using username and password. The trends ending with *_duration measure the request duration.
Testing setup was localhost mac book pro with M1.
Executed load tests: https://github.com/zitadel/zitadel/pull/7635
Most affecting were the so called "trigger" functions on query side.
During this spike we will investigate clean implementations to deprecate the triggers so that query side does no longer rely on the current_states-table.
### Tasks
- [ ] Document investigation outcome of load tests
- [ ] Describe possible solutions for the documented problems
- [ ] Try possible solutions
- [ ] Create issues for remaining tasks

Estimation: 10 days
Internal information:
Traces can be found here:

200 parallel users:
INFO[0002] admin signed in                               source=console
INFO[0002] org<PHONE_NUMBER>57111614) created              source=console
INFO[0044] 200 users created                             source=console

     ✓ user defined
     ✓ authorize status ok
     ✓ login name status ok
     ✓ login shows password page
     ✓ login has no error
     ✓ password status ok
     ✓ password callback
     ✓ code set
     ✓ token status ok
     ✓ access token created
     ✓ openid configuration
     ✓ userinfo status ok

     █ setup

       ✓ user defined
       ✓ authorize status ok
       ✓ login name status ok
       ✓ login shows password page
       ✓ login has no error
       ✓ password status ok
       ✓ password callback
       ✓ code set
       ✓ token status ok
       ✓ access token created
       ✓ org created
       ✓ create user is status ok

     █ teardown

       ✓ org removed

     checks...............................: 100.00% ✓ 13788     ✗ 0
     data_received........................: 24 MB   94 kB/s
     data_sent............................: 4.4 MB  17 kB/s
     http_req_blocked.....................: avg=7.5ms    min=0s       med=1µs      max=1.1s     p(90)=1µs      p(95)=2µs
     http_req_connecting..................: avg=4.53ms   min=0s       med=0s       max=1.01s    p(90)=0s       p(95)=0s
     http_req_duration....................: avg=4.03s    min=6.89ms   med=1.05s    max=33.28s   p(90)=14.58s   p(95)=17.91s
       { expected_response:true }.........: avg=4.03s    min=6.89ms   med=1.05s    max=33.28s   p(90)=14.58s   p(95)=17.91s
     http_req_failed......................: 0.00%   ✓ 0         ✗ 10738
     http_req_receiving...................: avg=1.03ms   min=12µs     med=140µs    max=764.87ms p(90)=1.27ms   p(95)=2.3ms
     http_req_sending.....................: avg=109.54µs min=7µs      med=93µs     max=8.86ms   p(90)=172µs    p(95)=206µs
     http_req_tls_handshaking.............: avg=2.95ms   min=0s       med=0s       max=483.6ms  p(90)=0s       p(95)=0s
     http_req_waiting.....................: avg=4.03s    min=5.34ms   med=1.05s    max=33.28s   p(90)=14.58s   p(95)=17.91s
     http_reqs............................: 10738   42.302557/s
     iteration_duration...................: avg=34.01s   min=530.93ms med=31.34s   max=1m33s    p(90)=56.53s   p(95)=1m6s
     iterations...........................: 1216    4.790455/s
     login_password_login_duration........: avg=34.03s   min=6.16s    med=31.34s   max=1m33s    p(90)=56.54s   p(95)=1m6s
     login_ui_enter_login_name_duration...: avg=7.12s    min=273.27ms med=3.27s    max=20.95s   p(90)=17.76s   p(95)=18.77s
     login_ui_enter_password_duration.....: avg=955.11ms min=6.89ms   med=9.82ms   max=14.76s   p(90)=4.03s    p(95)=8.41s
     login_ui_init_login_duration.........: avg=1.89s    min=168.51ms med=714.05ms max=21.87s   p(90)=5.97s    p(95)=8.02s
     login_ui_token_duration..............: avg=7.06s    min=190.71ms med=3.14s    max=20.52s   p(90)=17.42s   p(95)=18.54s
     oidc_user_info_duration..............: avg=11.27s   min=256.08ms med=9.18s    max=33.28s   p(90)=22.65s   p(95)=24.69s
     setup_create_org_duration............: avg=100.79ms min=100.79ms med=100.79ms max=100.79ms p(90)=100.79ms p(95)=100.79ms
     setup_create_user_duration...........: avg=10.21s   min=807.44ms med=9.06s    max=22.89s   p(90)=19.87s   p(95)=21.59s
     vus..................................: 24      min=0       max=200
     vus_max..............................: 200     min=200     max=200

running (4m13.8s), 000/200 VUs, 1216 complete and 0 interrupted iterations
default ✓ [======================================] 200 VUs  3m20s

150 parallel users:
INFO[0002] admin signed in                               source=console
INFO[0002] org<PHONE_NUMBER>30844734) created              source=console
INFO[0044] 150 users created                             source=console

     ✓ user defined
     ✓ authorize status ok
     ✓ login name status ok
     ✓ login shows password page
     ✓ login has no error
     ✓ password status ok
     ✓ password callback
     ✓ code set
     ✓ token status ok
     ✓ access token created
     ✓ openid configuration
     ✓ userinfo status ok

     █ setup

       ✓ user defined
       ✓ authorize status ok
       ✓ login name status ok
       ✓ login shows password page
       ✓ login has no error
       ✓ password status ok
       ✓ password callback
       ✓ code set
       ✓ token status ok
       ✓ access token created
       ✓ org created
       ✓ create user is status ok

     █ teardown

       ✓ org removed

     checks...............................: 100.00% ✓ 11246     ✗ 0
     data_received........................: 19 MB   76 kB/s
     data_sent............................: 3.6 MB  14 kB/s
     http_req_blocked.....................: avg=5.59ms   min=0s       med=1µs      max=1.06s    p(90)=2µs     p(95)=2µs
     http_req_connecting..................: avg=2.83ms   min=0s       med=0s       max=1.01s    p(90)=0s      p(95)=0s
     http_req_duration....................: avg=3.75s    min=6.32ms   med=1.51s    max=27.11s   p(90)=10.95s  p(95)=14.29s
       { expected_response:true }.........: avg=3.75s    min=6.32ms   med=1.51s    max=27.11s   p(90)=10.95s  p(95)=14.29s
     http_req_failed......................: 0.00%   ✓ 0         ✗ 8712
     http_req_receiving...................: avg=1.58ms   min=12µs     med=140µs    max=1.71s    p(90)=1.34ms  p(95)=3.02ms
     http_req_sending.....................: avg=116.74µs min=13µs     med=87µs     max=26.95ms  p(90)=175µs   p(95)=215µs
     http_req_tls_handshaking.............: avg=2.75ms   min=0s       med=0s       max=497.64ms p(90)=0s      p(95)=0s
     http_req_waiting.....................: avg=3.75s    min=0s       med=1.51s    max=27.11s   p(90)=10.92s  p(95)=14.29s
     http_reqs............................: 8712    34.594902/s
     iteration_duration...................: avg=30.94s   min=348.97ms med=25.36s   max=1m38s    p(90)=1m6s    p(95)=1m19s
     iterations...........................: 994     3.947123/s
     login_password_login_duration........: avg=30.96s   min=6.76s    med=25.36s   max=1m38s    p(90)=1m6s    p(95)=1m19s
     login_ui_enter_login_name_duration...: avg=5.65s    min=393.77ms med=4.21s    max=23.74s   p(90)=9.77s   p(95)=11.71s
     login_ui_enter_password_duration.....: avg=1.89s    min=6.32ms   med=9.6ms    max=22.31s   p(90)=10.69s  p(95)=14.42s
     login_ui_init_login_duration.........: avg=2.67s    min=176.03ms med=986.29ms max=27.11s   p(90)=6.48s   p(95)=15.31s
     login_ui_token_duration..............: avg=4.41s    min=189.69ms med=3.42s    max=13.89s   p(90)=8.56s   p(95)=9.02s
     oidc_user_info_duration..............: avg=9.49s    min=141.91ms med=9.31s    max=25.23s   p(90)=16.2s   p(95)=17.49s
     setup_create_org_duration............: avg=96.89ms  min=96.89ms  med=96.89ms  max=96.89ms  p(90)=96.89ms p(95)=96.89ms
     setup_create_user_duration...........: avg=13.01s   min=1.58s    med=12.93s   max=24.34s   p(90)=22.37s  p(95)=23.29s
     vus..................................: 33      min=0       max=150
     vus_max..............................: 150     min=150     max=150

running (4m11.8s), 000/150 VUs, 994 complete and 0 interrupted iterations

350 parallel users
INFO[0002] admin signed in                               source=console
INFO[0002] org<PHONE_NUMBER>91554955) created              source=console
INFO[0091] 350 users created                             source=console

     ✓ user defined
     ✗ authorize status ok
      ↳  99% — ✓ 1041 / ✗ 4
     ✓ login name status ok
     ✓ login shows password page
     ✓ login has no error
     ✓ password status ok
     ✓ password callback
     ✓ code set
     ✓ token status ok
     ✓ access token created
     ✓ openid configuration
     ✓ userinfo status ok

     █ setup

       ✓ user defined
       ✓ authorize status ok
       ✓ login name status ok
       ✓ login shows password page
       ✓ login has no error
       ✓ password status ok
       ✓ password callback
       ✓ code set
       ✓ token status ok
       ✓ access token created
       ✓ org created
       ✓ create user is status ok

     █ teardown

       ✓ org removed

     checks...............................: 99.96% ✓ 12167     ✗ 4
     data_received........................: 25 MB  77 kB/s
     data_sent............................: 4.3 MB 14 kB/s
     http_req_blocked.....................: avg=22.94ms  min=0s       med=1µs     max=1.48s    p(90)=2µs     p(95)=2µs
     http_req_connecting..................: avg=15.05ms  min=0s       med=0s      max=1.35s    p(90)=0s      p(95)=0s
     http_req_duration....................: avg=8.31s    min=6.55ms   med=1.95s   max=57.5s    p(90)=27.66s  p(95)=35.44s
       { expected_response:true }.........: avg=8.3s     min=6.55ms   med=1.94s   max=57.5s    p(90)=27.65s  p(95)=35.44s
     http_req_failed......................: 0.03%  ✓ 4         ✗ 10092
     http_req_receiving...................: avg=1.46ms   min=0s       med=153µs   max=773.01ms p(90)=1.57ms  p(95)=4ms
     http_req_sending.....................: avg=132.86µs min=10µs     med=97µs    max=13.31ms  p(90)=192µs   p(95)=243µs
     http_req_tls_handshaking.............: avg=7.87ms   min=0s       med=0s      max=868.13ms p(90)=0s      p(95)=0s
     http_req_waiting.....................: avg=8.3s     min=5.8ms    med=1.95s   max=57.5s    p(90)=27.66s  p(95)=35.44s
     http_reqs............................: 10096  31.727135/s
     iteration_duration...................: avg=1m13s    min=478.87ms med=1m10s   max=2m38s    p(90)=1m57s   p(95)=2m12s
     iterations...........................: 1045   3.28396/s
     login_password_login_duration........: avg=1m13s    min=5.84s    med=1m10s   max=2m38s    p(90)=1m57s   p(95)=2m12s
     login_ui_enter_login_name_duration...: avg=16.38s   min=430.65ms med=12.78s  max=38.92s   p(90)=35.05s  p(95)=36.44s
     login_ui_enter_password_duration.....: avg=2.5s     min=6.55ms   med=10.26ms max=17.19s   p(90)=8.76s   p(95)=9.81s
     login_ui_init_login_duration.........: avg=4.33s    min=181.27ms med=1.25s   max=27.3s    p(90)=13.8s   p(95)=15.73s
     login_ui_token_duration..............: avg=15.43s   min=199.12ms med=12.08s  max=38.45s   p(90)=34.44s  p(95)=36.27s
     oidc_user_info_duration..............: avg=20.35s   min=233.88ms med=18.17s  max=57.5s    p(90)=40.82s  p(95)=42.83s
     setup_create_org_duration............: avg=82.85ms  min=82.85ms  med=82.85ms max=82.85ms  p(90)=82.85ms p(95)=82.85ms
     setup_create_user_duration...........: avg=21.26s   min=1.32s    med=19.72s  max=46.92s   p(90)=41.6s   p(95)=44.43s
     vus..................................: 0      min=0       max=350
     vus_max..............................: 350    min=350     max=350

running (5m18.2s), 000/350 VUs, 1045 complete and 0 interrupted iterations
default ✓ [======================================] 350 VUs  3m20s

machine pat login:
INFO[0002] setup: admin signed in                        source=console
INFO[0002] setup: org<PHONE_NUMBER>39985562) created       source=console
INFO[0052] setup: 400 machines created                   source=console
INFO[0060] setup: Pats added                             source=console
INFO[0274] teardown: org removed                         source=console

     ✓ openid configuration
     ✓ userinfo status ok

     █ setup

       ✓ user defined
       ✓ authorize status ok
       ✓ login name status ok
       ✓ login shows password page
       ✓ login has no error
       ✓ password status ok
       ✓ password callback
       ✓ code set
       ✓ token status ok
       ✓ access token created
       ✓ org created
       ✓ create user is status ok
       ✓ add pat status ok

     █ teardown

       ✓ org removed

     checks...............................: 100.00% ✓ 6253      ✗ 0
     data_received........................: 9.6 MB  35 kB/s
     data_sent............................: 1.1 MB  3.8 kB/s
     http_req_blocked.....................: avg=51.6ms   min=0s       med=1µs      max=2.33s    p(90)=2µs      p(95)=316.23ms
     http_req_connecting..................: avg=34.53ms  min=0s       med=0s       max=2.02s    p(90)=0s       p(95)=70.87ms
     http_req_duration....................: avg=12.92s   min=10.03ms  med=13.58s   max=43.38s   p(90)=22.69s   p(95)=25.93s
       { expected_response:true }.........: avg=12.92s   min=10.03ms  med=13.58s   max=43.38s   p(90)=22.69s   p(95)=25.93s
     http_req_failed......................: 0.00%   ✓ 0         ✗ 6651
     http_req_receiving...................: avg=207.19µs min=13µs     med=124µs    max=17.93ms  p(90)=205µs    p(95)=285.49µs
     http_req_sending.....................: avg=111.81µs min=8µs      med=63µs     max=7.64ms   p(90)=145µs    p(95)=273.49µs
     http_req_tls_handshaking.............: avg=17.05ms  min=0s       med=0s       max=2.24s    p(90)=0s       p(95)=50.83ms
     http_req_waiting.....................: avg=12.92s   min=9.79ms   med=13.58s   max=43.38s   p(90)=22.69s   p(95)=25.93s
     http_reqs............................: 6651    24.31244/s
     iteration_duration...................: avg=16.35s   min=500.07ms med=16.58s   max=59.23s   p(90)=24.25s   p(95)=26.95s
     iterations...........................: 5041    18.427155/s
     login_ui_enter_login_name_duration...: avg=324.56ms min=324.56ms med=324.56ms max=324.56ms p(90)=324.56ms p(95)=324.56ms
     login_ui_enter_password_duration.....: avg=10.03ms  min=10.03ms  med=10.03ms  max=10.03ms  p(90)=10.03ms  p(95)=10.03ms
     login_ui_init_login_duration.........: avg=245.39ms min=245.39ms med=245.39ms max=245.39ms p(90)=245.39ms p(95)=245.39ms
     login_ui_token_duration..............: avg=201.38ms min=201.38ms med=201.38ms max=201.38ms p(90)=201.38ms p(95)=201.38ms
     oidc_user_info_duration..............: avg=16.27s   min=277.16ms med=16.55s   max=43.38s   p(90)=24.14s   p(95)=26.92s
     setup_create_human_duration..........: avg=5.03s    min=536.22ms med=5.2s     max=8.89s    p(90)=8.21s    p(95)=8.54s
     setup_create_org_duration............: avg=98.49ms  min=98.49ms  med=98.49ms  max=98.49ms  p(90)=98.49ms  p(95)=98.49ms
     vus..................................: 3       min=0       max=400
     vus_max..............................: 400     min=400     max=400

running (4m33.6s), 000/400 VUs, 5041 complete and 0 interrupted iterations
default ✓ [======================================] 400 VUs  3m20s

Query triggers
The load tests show that so called triggers in the query package and getLatestState are blocking. If multiple execution paths call the same method of queries which does a trigger first they are blocking.
Options
Possible mitigation of the problem are the following.
Move triggers to command side (API)
As the data can only change during a command in CQRS it would be feasible to move the calls of the triggers of the projections to the command side and call them during or after a command.
Pros

low hanging because the changes on the code are little
fast everything already exists, its just moving code

Cons

root cause is not solved
problem could reoccur including even more parts of the system
quality is hard to achieve because changes on projections include possible extension of the trigger list of commands

Remove triggers
Instead of ensuring that the data are up-to-date on the list projections we call the eventstore directly or first query the current data and afterwards the eventstore to reduce the not yet reduced events.
To fulfill the requirements of the queries the event store interface need to be extended that multiple questions can be answered in a single query.
The change also includes in memory processing of the events which is currently solved by database DML-queries. This change can reduce times to left fold an object drastically because there are no round trips to the database for each event.
Pros

solves the actual root cause
possible performance improvement of reduce
allows future optimizations if needed

Cons

time to implement, however small changes can easily be shipped and hidden behind a feature flag
many code changes

Outcome
The issues to improve the oidc server side improve the speed of the oidc endpoints, these optimizations should be prioritized.
As Option 1 does not solve the root cause we focus on Option 2 verify this approach. If the outcome is as expected create issues for each query method which uses triggers and prioritize them as high.
Additional work
As the session-resource gets more important we need additional load tests for this part of zitadel. This could result in additional issues including the auth middleware of zitadel.

Improvement of app and project queries
Test
Mac M1
VUS=100 ADMIN_PASSWORD=Test111$ DURATION=300s make machine_pat_login
Before
Branch: main

Percentile
Latency

25%
64 ms

50%
1485 ms

75%
1924 ms

90%
2233 ms

95%
2361 ms

After
PR: https://github.com/zitadel/zitadel/pull/7817

Percentile
Latency

25%
16 ms

50%
49 ms

75%
501 ms

90%
1335 ms

95%
1426 ms

latency of token endpoint
Test
Mac M1
VUS=100 ADMIN_PASSWORD=Test111$ DURATION=300s make human_password_login
Limit db connections to 100
Before
Branch: main

Percentile
Latency

25%
7 ms

50%
21 ms

90%
3565 ms

95%
3796 ms

99%
4120 ms

99.5%
4409 ms

After
PR: https://github.com/zitadel/zitadel/pull/7817

Percentile
Latency

25%
18 ms

50%
48 ms

90%
1641 ms

95%
2000 ms

99%
3266 ms

99.5%
5023 ms


Testing cmake builds

the CMake has been writtern, debugged tested and now all is left is to test it's output;the projects to check that it works with all operating systems and IDE's cmake is compatible with along with how it fares in it's project creation.
I need help with more people testing the builds as 1 person does not represent the whole of the world(what might work for me might not for you)

Tested with:

Windows:

[ ] CLion

OS X

[ ] CLion

Linux

[ ] CLion


Unsafety in conditional rules and fixing them

Hello there.
Not sure if this is the right place to ask for usage tips, but I have a bit of
a conundrum and the user manual only has one instance of the word unsafe in
it, in chapter 6.1. I am trying to declare a conditional or dynamically
expanded rule of the form
p(X) :- q(X, A) : r(A).

but Clingo is reporting the variable X as "unsafe":
Reading from test.lp
test.lp:31:1-52: error: unsafe variables in:
  p(X):-[#inc_base];q(X, A):r(A).
test.lp:31:3-4: note: 'X' is unsafe

*** ERROR: (clingo): grounding stopped because of errors
UNKNOWN

Why is this? One source by Lifschitz claims that

Some error messages say that the program has “unsafe variables.” Such a
message usually indicates that the head of one of the rules includes a
variable that does not occur in its body; …

However, this does not seem to be the case here. How might I fix a problem like
this?

Never mind. Adding an unconditionally grounded rule s(X) after the conditional worked:
p(X) :- q(X, A) : r(A); s(X).

I guess ambiguities are bad?

It is important to provide a binding for X. Consider the program
d(f(1)).
p(X) :- q(X) : #false.

The conditional literal is true for all values of X. We obtain an infinite answer set:
d(f(1)), p(1), p(f(1)), p(f(f(1))), ...


[DOCFIX] - Small updates

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15827/
Test PASSed.


add unit test for YAML anchors

Just a quick test to demo and doc how YAML anchors are and are not supported by libyaml.
Closes #535

Love it.  Merging.


[Support] Code cleanup and refactor how b-panel animation occurs [#157398629]

Overview
This is just some cleanup to facilitate this story
How to test
See impact app PR

@jonpitch I'm a little curious about the observer -> computedProperty change.  observer seems to make sense, because it's there to perform side-effects on the DOM.  A computedProperty that is impure + performs side-effects seems counter intuitive, and I'd be surprised if there are any guarantees around the min/max number of times computedProperty gets evaluated under any condition.  Is a computedProperty better here for some reason?

@thematthopkins in my opinion, the majority of the time observer is used in our Ember apps, it has unintended side effects and the same functionality can be achieved simpler. In this particular case, observer probably makes more sense, but I'd rather have the rule to not use them globally thinking it'll have more benefits even if it makes this one instance a little more difficult.


A OIDC provider can access custom userdata types

Closes #350

Coverage decreased (-0.1%) to 88.578% when pulling f10161b70db66ddc88c4d5208295e130fec18d36 on feature/custom-attributes-by-app into b16ef5fce9d147722524ccd6bb94d5f95a3a7d45 on main.


chore(graph): jermaine review

Closed. All reviewed changes have either been implemented or a task has been created for them. Please see comments on code if you wish to know the status of changes at the time of closure.


Where is epel-6?

https://repos.fedorapeople.org/repos/peter/erlang/
no epel-6
http://repos.fedorapeople.org/repos/peter/erlang/epel-6/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"

I have a PR into to use the official erlang-solutions repo, this might be helpful for you.
https://github.com/garethr/garethr-erlang/pull/21


Fix TO CRConfig tm.url to be FQDN, not URI

What does this PR do?
Fix TO CRConfig tm.url to be fdqn, not uri.
This fixes a regression introduced by https://github.com/apache/trafficcontrol/pull/3069 which itself fixes a bug from the CRConfig tm_host coming from the request Host header, not from TO.
The regression is that the tm.url is typically a URI, not an FQDN.
This fixes the CRConfig generation to work with either. If the tm.url parameter is an FQDN, it's returned as-is. If it's a URI, the Host part is returned.
Includes unit tests. Updates existing API Tests.
Which TC components are affected by this PR?

[ ] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[x] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] Other _________

What is the best way to verify this PR?
Snapshot the CRConfig with a global tm.url Parameter which is a URI, e.g. https://example.invalid, verify the CRConfig stats tm_host field is the FQDN of the URI, e.g. example.invalid.
Check all that apply

[x] This PR includes tests
[ ] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2955/
Test PASSed.


[Bug] stack traces sent from uploading crashes API cannot be shown on AppCenter portal

Hi,
I used the API Upload custom crashes via API, with optional parameter stackTrace in exception.
The payload is like:
{     "logs": [         {             "type": "managedError",             "timestamp": "2019-11-25T04:22:23.516Z",             "appLaunchTimestamp": "2019-11-24T04:22:23.516Z",             "processId": "123",             "id": "bca65f46-46ee-451b-83bb-2e358c3f45bf",             "fatal": true,             "processName": "com.abc",             "device": {                 "appVersion": "13.0",                 "appBuild": "1",                 "sdkName": "custom.android",                 "sdkVersion": "1.0.0",                 "osName": "android",                 "osVersion": "9.3",                 "model": "Pixel",                 "locale": "en-US",                 "appNamespace": "com.abc"             },             "userId": "TestID",             "exception": {                 "type": "java.lang.RuntimeException",                 "stackTrace": "at com.google.gson.internal.LinkedTreeMap$LinkedTreeMapIterator.nextNode(LinkedTreeMap.java:544)"             }         }     ] }
And I got successful response from API, on App Center portal,  I can find that crash record, but CAN NOT see the detail crash trace:

I assume this's a bug? @winnie

Hi @msdof - please start a support ticket (blue chat bubble in App Center) so our team can better investigate. Thanks!

Hi @msdof, This issue has been fixed.
Now you should be able to provide the stack trace and can be seen in AppCenter portal like below


Document IfNode fields

Adds documentation for the fields of the IfNode. Also updates the overall description to mention ternary expressions.
Part of #2123

Open to feedback on level of detail or any stylistic changes. I just opened this one node to see if it was approximately what you were looking for but happy to open others as a follow-up.
I also wasn't exactly sure how to indicate multiple lines for something like:
              if foo
                bar
              elsif baz
              ^^^^^^^^^
                qux
                ^^^
              end
              ^^^

so let me know if you have an opinion on that. Are the contents of this file used to generate documentation somewhere that I can see? I wasn't sure how to preview my changes outside of the YAML.


Potential Security Vulnerability Found - Requesting Secure Contact Method

Hello,
I've discovered a potential security issue in your project. Could you please provide a secure method of contact to discuss it privately?
Thank you!

As this is an open source project no need to be discussed in private.
Please create an issue here or start a discussion or raise a pr with the issue you found and suggested fix.


Research superior LiDAR Sensor for Obstacle Avoidance

Rationale
In the 2024 competition, URC has decided to raise the budget cap for the rover, allowing us to upgrade various hardware components.
One of the issues with the existing LiDAR sensor on the rover is that it only supports scanning in the X and Z axis. This means that the rover is incapable of distinguishing between a slight bump on the surface, a rock, or a wall. With the new budget cap, we aim to upgrade the LiDAR sensor to one that supports Y axis scanning as well.
Required Actions

[ ] Research and investigation replacement LiDAR Sensor
[ ] Update existing code for compatibility with new sensor

 Research LIDAR sensors for obstacle avoidance


Add resending of emails in listview, with attachments

This PR adds a button to the list view action column to resend emails with attachments. Displays growl messages on success or error.

Thanks ❤ . I have left one suggestion. Could you apply that?

Thanks ❤ . I have left one suggestion. Could you apply that?

Ok, PR is updated with "clone" as suggested, I've also changed the Ajax call to POST and removed a log entry

Ok, PR is updated with "clone" as suggested, I've also changed the Ajax call to POST and removed a log entry

I am closing this as it's stale for a very long time. Let us know when you want to work on it :)


Failure downloading artifacts during Release on Linux agent

Environment

VSTS - rcss-willistowerswatson - PPM
Agent - Private: 2.139.1
OS: Red Hat Enterprise Linux 7.4

Issue Description
1. Set up a build that publishes 2 artifacts using "Publish Build Artifacts" task.
One task should publish to a file share, the other task should publish to VSTS.

2. Set up a VSTS agent on a Linux VM.
See above for agent and OS details.
3. Set up release definition to download artifacts only from VSTS.

The release will attempt to download (or at least look at) artifacts on a share.
Error: ENOENT: no such file or directory, scandir '\\e20-ix-file001p\drop$\vsts-issue\49497'
While the Linux VM is on the same network as the share, is domain-joined, and is running as a domain account, it cannot resolve a UNC path. Regardless, it should not even care about the share artifact, because it was deselected.
Task logs
tasklog_2.log
Error logs
Error: ENOENT: no such file or directory, scandir '\\e20-ix-file001p\drop$\vsts-issue\49497'

Hi @xenalite ,
Can you please check if you are still able to repro this issue?

@gykuma I cannot reproduce the issue anymore.
Tried on the same agent version and OS like in the OP.
Same set up as before for artifacts download:

It only attempts to download the vsts artifact:

@xenalite Thanks for the update. The issue should have got fixed with the new DownloadFileshareArtifacts task roll out.


docs: complete example with options object

Why this PR?
Right now, we are forced to read further and manually configure the options and throw it in the object. No need: this PR makes it very clear what is required.

@benkoshy  Thanks for your contribution.
I agree with you suggestion, however I will close this MR , as we are planning to make a major update to our js docs


Noticed Deadlock? Sometimes buntdb gets stuck by a deadlock

Hi. Today, I decided to integrate buntdb via interfaces ( alongside boltdb ) as both libraries are very similar. When running the same code using buntdb, sometimes it generates a deadlock and gets stuck (probably the locking mechanism of buntdb). I want to say that I am running the same exact code using boltdb and I never noticed any deadlock using boltdb.
You can check both databases integrations via an interface https://github.com/PandoraPay/go-pandora-pay/tree/main/store/store-db
LE: Could it be because the string -> []byte cast? As keys and values are binary data casted as strings?
LE2: Tested it again. Buntdb generates deadlock. Same code running with boltdb no deadlock spotted.

Hi. I would like to reproduce this issue. Could you provide the steps to cause the deadlock?

Hi @tidwall ! Thanks for the response. I will make you a tutorial tomorrow to reproduce it after I will test it again. Thanks again!

Today I also noticed a deadlock.
The reason was that I started a read / write transaction (update) enclosed within a read-only transaction (view). Silly me running untested code.
Strumbled across this issue and thought this info might be interesting for other users.
cheers


[SPARK-48682][SQL] Use ICU in InitCap expression for UTF8_BINARY strings

What changes were proposed in this pull request?
Update InitCap Spark expressions to use ICU case mappings for UTF8_BINARY collation, instead of the currently used JVM case mappings. This behaviour is put under the ICU_CASE_MAPPINGS_ENABLED flag in SQLConf, which is true by default. Note: the same flag is used for Lower & Upper expressions, with changes introduced in: https://github.com/apache/spark/pull/47043.
Why are the changes needed?
To keep the consistency between collations - all collations shouls use ICU-based case mappings, including the UTF8_BINARY collation.
Does this PR introduce any user-facing change?
Yes, the behaviour of initcap string function for UTF8_BINARY will now rely on ICU-based case mappings. However, by turning the ICU_CASE_MAPPINGS_ENABLED flag off, users can get the old JVM-based case mappings. Note that the difference between the two is really subtle.
How was this patch tested?
Existing tests, with extended CollationSupport unit tests for InitCap to verify both ICU and JVM behaviour.
Was this patch authored or co-authored using generative AI tooling?
No.

@mkaravel ready for review

@mkaravel please review

@cloud-fan ready to merge

thanks, merging to master!


Fix "Symbol is undefined" error

We faced with issue, that in old browsers Symbol is not supported.
As I see, in the code, Symbol is used as unique value (not as unique key in an object).
So I added the check if Symbol exists and use an Object if not.

I switched away from Symbol entirely, the typeof Symbol === "function" check just adds unnecessary complexity. Good PR, thanks!!


Added Rasa Entities Role and Groups

As discussed in https://github.com/SimGus/Chatette/issues/48
List of added functionalities:

Entities Roles and Groups with chatette annotation format. For example

I want to go from @[place]("role": "departure", "group": "airport") to @[place]("role": "arrival")

Added Rasa YAML adapter format which can be called with argument -a rasayml or -a rasayaml
added inline entity support for markdown and yaml adapter as requested here: https://github.com/SimGus/Chatette/issues/46

Any chance for a Yml adapter soon. It would be a great feature!!

Hello @tomgun123, thanks a lot for your changes!
I'll review them as soon as I can and let you know if any changes are required

Hi @Bohemus307!
Since yaml is a superset of json, the json adapter can actually be considered a yaml adapter (which is the reason I never made a "proper" one). However, if you think it would make sense to create a proper one and want to discuss it further, you can open an issue about this :)
Cheers!

I wasnt aware of that thank you SimGus. I haven't tried to use the JSON in rasa yet do I just add it to the nlu directory or do I need to add it to the config as a custom directory?

It's been a while I haven't used Rasa, but unless they changed something you should be able to simply add the generated file to the nlu directory

Hi @Bohemus307 @SimGus
Yaml adapter should've been implemented if this PR is approved.
Meanwhile, you can try it from my forked repository first and if you find some bugs or suggestion, please report it here :)
And also, yeah, you can put JSON file inside the NLU folder in your rasa training data directory and when you train, Rasa can detect whether the JSON format is the correct training data format or not. Though, it's easier to for human to read a yaml file than a json file.

hi @SimGus, do you have any update on this?
Sorry to interrupt if you're currently busy with your main work.

Hi @Atorpat
Roles and groups can already be used from my forked master branch with:
I want to go from @[place]("role": "departure", "group": "airport") to @[place]("role": "arrival")

It will generate something like:
- I want to go from [Berlin]{"entity": "place", "role": "departure", "group": "airport"} to [San Francisco]{"entity": "place", "role": "arrival"}.

I haven't used Rasa in a while since my project has changed but I think the format hasn't changed that much so you can still use it as it is.

@tomgun132
Thanks a lot, Tom. yes, the format is still the same.
I will try the branch. It's a shame we don't have it on the main project.


Bsky app doesnt send referrer

You can't track traffic to your website from Bluesky app because of this. In Matomo or Google Analytics you only see visitors who use Bluesky in browser.
Matomo dev team wrote:
_Our development confirmed the app does not send a referrer, so it is only possible to populate as direct entry unfortunately.
As BS is still in beta development, maybe they will add the information in the future.
Let me know if you have any questions please.
Regards,
--
Ralph Conti
<EMAIL_ADDRESS>Matomo Support Team_

Can you please fix this. It hard to show how important Bluesky is, if you cant track traffic to your site.

This feels like it is massively in Bluesky's interests to fix.

I agree. Although fixing this isn't free - to do it properly you'd need to host a proxy to add the header. There's got to be a strong commercial case for showing downstream sites that Bluesky is driving their traffic, but...

it's not obvious to me that fixing this in the app is sufficient in the long run, if the network becomes properly federated people may click on a link you posted on the Bluesky app in a different client altogether, so we'd still be undercounting, or at least disaggregating, the impact of Bluesky on traffic
whoever pays for the proxy would need to decide there's a business case and that this is a priority

I think the business case for the proxy is that this will drive more users to the platform. People who monetise substacks and the like will be more active on bsky if they see more of their traffic coming from there

Sorry but this is not a bug - if you want to track visitors from Bluesky to your site put the appropriate information in the URL you post...

Sorry but this is not a bug the lack of referrer information is a plus for an awful lot of people
And there is a simple workaround if you want to track visitors from Bluesky to your site put the appropriate information in the URL you post - in the same way you would when sending an email out..

No, you are wrong. Its totally differend thing put tracker urls to post you personally share.

Sorry but this is not a bug the lack of referrer information is a plus for an awful lot of people
And there is a simple workaround if you want to track visitors from Bluesky to your site put the appropriate information in the URL you post - in the same way you would when sending an email out..

I agree that it isn't a "bug" per-se, but it is still Bsky's problem - asking everyone else to change the way they work to fit in with Bsky just isn't going to cut it. For example, people running hosted Wordpress or Substack literally can't change the way they work to fit in with this, even if they had the technical acumen to do so. They will simply look at their stats, see that Bsky is way, way below Facebook and Twitter and Wikipedia (sic - in my case!) and shug and say "Well... Bsky isn't really getting any traction - I'll focus elsewhere."

I've looked at this today. So far it doesn't seem to be possible to add a Referer header on iOS (without dropping down from SFSafariViewController to WKWebView which I'd rather not do) or on Android (where CustomTabsIntent only takes CORS-safelisted headers, which Referer is not).
This means, unless I'm wrong, that we're only left with these options:

Do nothing (status quo)
Set up a redirect service like https://bsky.app/redirect/... (which would rely on the browser to fill inReferer)
Or hijack the link to add utm_source=bluesky or something to the links (if missing)

I lean towards (2) with an opt-out in Settings for people who'd rather skip this step. But curious if y'all have other ideas.

How other apps do this? X, Threads, Facebook?

Hijacking the links is going to cause weird bugs in systems which don't use "standard" url parameters. I've literally done this in the past - I added an ID to people's Return URLs in a payment system - and had people get cross with me for messing with their inputs.
Setting up a redirect service is definitely the better solution; but I appreciate it won't be a cheap - hence I'd understand doing nothing.

I think X uses their t.co link shortening service, which I'm guessing sends a Referer.
No idea about Threads or Facebook.

How other apps do this? X, Threads, Facebook?

They embed a webview in their app, rather than passing out to Safari/ Chrome to handle it.


2d pose mapping

Hi,
I'm trying to integrate @mediapipe/pose in my react project for 2d mapping with COCO key points.
but as I see I can only use @mediapipe/pose for 3d mapping.
so is there any way I can use it for 2d mapping?

Hi @ashisharorambdev,
Could you elaborate your query with more details to understand the issue better from our end. Thank you!

hi @kuaashish sorry for the delayed response
I have some COCO key points for the 2d model which I want to map using @mediapipe/pose but from what I saw in the examples I can only map the 3d model using this library.
So is there any way I can use this library of 2d mapping?
below I have listed 17 key points I want to map
0: 'nose',
1: 'left_eye',
2: 'right_eye',
3: 'left_ear',
4: 'right_ear',
5: 'left_shoulder',
6: 'right_shoulder',
7: 'left_elbow',
8: 'right_elbow',
9: 'left_wrist',
10: 'right_wrist',
11: 'left_hip',
12: 'right_hip',
13: 'left_knee',
14: 'right_knee',
15: 'left_ankle',
16: 'right_ankle'

hi, @kuaashish any update regarding my query?

Hi @ashisharorambdev,
Can you please let us know the following:

What does the mean by "mapping"?  Does mean "rendering"?
We believe you would like to convert MediaPipe landmarks to/from COCO key-points?

Mediapipe does include several 2d models and 2d renderers.  2d landmarks are common inside MediaPipe. Thank you!


tests fail with openssl 1.1.0e because of extra spaces in DN output

OpenSSL 1.1.0e  16 Feb 2017 possible new format introduced in OpenSSL
tape test/openssl-cmd.js
TAP version 13
# openssl version
# make temp dir
ok 1 null
# pkcs8 rsa public key parses
ok 2 should be equal
ok 3 should be equal
ok 4 should be equal
ok 5 should be truthy
# pkcs8 rsa private key parses
ok 6 should be equal
ok 7 should be equal
ok 8 should be equal
ok 9 should be truthy
# pkcs8 rsa public key output
ok 10 output produced
ok 11 should be equal
ok 12 should be equal
# pkcs8 rsa private key output
ok 13 output produced
ok 14 should be equal
ok 15 should be equal
# sign with sshpk, openssl dgst verify
ok 16 should be equal
ok 17 should be equal
# sign with openssl, verify with sshpk
ok 18 should be equal
ok 19 should be truthy
ok 20 should be truthy
# make a self-signed cert, parse with openssh
ok 21 should be equal
not ok 22 should be equal
  ---
    operator: equal
    expected: 'CN=rsa, C=US'
    actual:   'CN = rsa, C = US'
    at: ChildProcess.<anonymous> (/home/pravi/forge/debian/git/pkg-javascript/node-sshpk/test/openssl-cmd.js:225:6)
  ...
not ok 23 should be equal
  ---
    operator: equal
    expected: 'CN=rsa, C=US'
    actual:   'CN = rsa, C = US'
    at: ChildProcess.<anonymous> (/home/pravi/forge/debian/git/pkg-javascript/node-sshpk/test/openssl-cmd.js:228:6)
  ...
ok 24 should be equal
ok 25 should be equal
# make a self-signed cert, verify with openssh
ok 26 should be equal
ok 27 should be equal
# make a self-signed cert with utf8 chars
ok 28 should be equal
ok 29 should be equal
# verify a self-signed cert with utf8 chars
ok 30 should be equal
ok 31 should be equal
ok 32 should be equal
ok 33 should not be equal
ok 34 should be equal
ok 35 should be equal
ok 36 should not be equal
ok 37 should be truthy
# make a self-signed cert with non-printable chars
ok 38 should be equal
ok 39 should be equal
ok 40 should be equal
ok 41 should not be equal
ok 42 should be equal
ok 43 should be equal
ok 44 should not be equal
ok 45 should be truthy
# make a self-signed cert with generated key
# make temp dir
ok 46 null
# pkcs8 dsa public key parses
ok 47 should be equal
ok 48 should be equal
ok 49 should be equal
ok 50 should be truthy
# pkcs8 dsa private key parses
ok 51 should be equal
ok 52 should be equal
ok 53 should be equal
ok 54 should be truthy
# pkcs8 dsa public key output
ok 55 output produced
ok 56 should be equal
ok 57 should be equal
# pkcs8 dsa private key output
ok 58 output produced
ok 59 should be equal
ok 60 should be equal
# sign with sshpk, openssl dgst verify
ok 61 should be equal
ok 62 should be equal
# sign with openssl, verify with sshpk
ok 63 should be equal
ok 64 should be truthy
ok 65 should be truthy
# make a self-signed cert, parse with openssh
ok 66 should be equal
not ok 67 should be equal
  ---
    operator: equal
    expected: 'CN=dsa, C=US'
    actual:   'CN = dsa, C = US'
    at: ChildProcess.<anonymous> (/home/pravi/forge/debian/git/pkg-javascript/node-sshpk/test/openssl-cmd.js:225:6)
  ...
not ok 68 should be equal
  ---
    operator: equal
    expected: 'CN=dsa, C=US'
    actual:   'CN = dsa, C = US'
    at: ChildProcess.<anonymous> (/home/pravi/forge/debian/git/pkg-javascript/node-sshpk/test/openssl-cmd.js:228:6)
  ...
ok 69 should be equal
ok 70 should be equal
# make a self-signed cert, verify with openssh
ok 71 should be equal
ok 72 should be equal
# make a self-signed cert with utf8 chars
ok 73 should be equal
ok 74 should be equal
# verify a self-signed cert with utf8 chars
ok 75 should be equal
ok 76 should be equal
ok 77 should be equal
ok 78 should not be equal
ok 79 should be equal
ok 80 should be equal
ok 81 should not be equal
ok 82 should be truthy
# make a self-signed cert with non-printable chars
ok 83 should be equal
ok 84 should be equal
ok 85 should be equal
ok 86 should not be equal
ok 87 should be equal
ok 88 should be equal
ok 89 should not be equal
ok 90 should be truthy
# make a self-signed cert with generated key
# make temp dir
ok 91 null
# pkcs8 ecdsa public key parses
ok 92 should be equal
ok 93 should be equal
ok 94 should be equal
ok 95 should be truthy
# pkcs8 ecdsa private key parses
ok 96 should be equal
ok 97 should be equal
ok 98 should be equal
ok 99 should be truthy
# pkcs8 ecdsa public key output
ok 100 output produced
ok 101 should be equal
ok 102 should be equal
# pkcs8 ecdsa private key output
ok 103 output produced
ok 104 should be equal
ok 105 should be equal
# sign with sshpk, openssl dgst verify
ok 106 should be equal
ok 107 should be equal
# sign with openssl, verify with sshpk
ok 108 should be equal
ok 109 should be truthy
ok 110 should be truthy
# make a self-signed cert, parse with openssh
ok 111 should be equal
not ok 112 should be equal
  ---
    operator: equal
    expected: 'CN=ecdsa, C=US'
    actual:   'CN = ecdsa, C = US'
    at: ChildProcess.<anonymous> (/home/pravi/forge/debian/git/pkg-javascript/node-sshpk/test/openssl-cmd.js:225:6)
  ...
not ok 113 should be equal
  ---
    operator: equal
    expected: 'CN=ecdsa, C=US'
    actual:   'CN = ecdsa, C = US'
    at: ChildProcess.<anonymous> (/home/pravi/forge/debian/git/pkg-javascript/node-sshpk/test/openssl-cmd.js:228:6)
  ...
ok 114 should be equal
ok 115 should be equal
# make a self-signed cert, verify with openssh
ok 116 should be equal
ok 117 should be equal
# make a self-signed cert with utf8 chars
ok 118 should be equal
ok 119 should be equal
# verify a self-signed cert with utf8 chars
ok 120 should be equal
ok 121 should be equal
ok 122 should be equal
ok 123 should not be equal
ok 124 should be equal
ok 125 should be equal
ok 126 should not be equal
ok 127 should be truthy
# make a self-signed cert with non-printable chars
ok 128 should be equal
ok 129 should be equal
ok 130 should be equal
ok 131 should not be equal
ok 132 should be equal
ok 133 should be equal
ok 134 should not be equal
ok 135 should be truthy
# make a self-signed cert with generated key
ok 136 should be equal
ok 137 should be equal
# teardown

1..137
# tests 137
# pass  131
# fail  6

Thanks for reporting this!
Patch review: https://cr.joyent.us/#/c/2005/


feat(parseEditorState): adding support for parsed JSON in addition to stringified JSON

Fixes #2052

Mind adding a simple test?

@fantactuka Thanks for the help. A simple test has been added but I'm not sure if it is enough. Let me know.


[Epic] - Make it easier to start developing with miranum connect

[x] Description created
[ ] Reviewed by peer:
[ ] Prioritised

Description
We should simplify it to start with the development of Miranum Connect.
Getting Started examples are needed for this -> like this: https://docs.camunda.org/get-started/quick-start/
Moreover we should think about creating a initializer similar to https://github.com/spring-io/initializr
-> Please refer: https://docs.spring.io/initializr/docs/current/reference/html/#create-instance
Sub-Tasks

### Tasks
- [ ] <your-issue-here>

Stakeholder
@dominikhorn93
Acceptance

Getting Started Landing Page in Docs with chapter per case
Each Getting Started has its own git repository
The Getting Started can be used as a seed project
Following Getting Started are created

Simple C7/C8 Worker created
Hexagonal Architecture Style
Process Start
Message Correlation

Hi @Hafflgav,
I've forked your repo and added it as one of our consulting projects: https://github.com/FlowSquad/miranum-consulting/tree/feat/pizza-e-vino

Hi @Hafflgav,
I've forked your repo and added it as one of our consulting projects: https://github.com/FlowSquad/miranum-consulting/tree/feat/pizza-e-vino

Hey @DaAnda97!
Isn't this part of this story: https://github.com/orgs/FlowSquad/projects/9/views/1?filterQuery=label%3Aconsulting&pane=issue&itemId=23820378


IAM onboarding resiliency

Based on the discussion on PR - https://github.com/IBM/ibm-iam-operator/pull/488
This new PR has been raised with removal of capture the iam-onboarding logs
https://github.ibm.com/IBMPrivateCloud/roadmap/issues/53620
Change in brief -> Add init container to check two crucial endpoints before starting the actual job. The script to check endpoints is available in iam-onboarding job.

Regression result -
summOutputLog_CD_08-30-2022_16-10-20.txt

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/53620


Kubernetes Core bundle does not start on localhost

Using Juju 2.1.2, 0/lxd/0 won't come up:
Model    Controller  Cloud/Region         Version
default  lxd         localhost/localhost  2.1.2

App                Version  Status       Scale  Charm              Store       Rev  OS      Notes
easyrsa                     waiting        0/1  easyrsa            jujucharms    7  ubuntu
etcd               2.2.5    blocked          1  etcd               jujucharms   24  ubuntu
flannel            0.7.0    blocked          2  flannel            jujucharms   11  ubuntu
kubernetes-master  1.5.3    maintenance      1  kubernetes-master  jujucharms   12  ubuntu  exposed
kubernetes-worker  1.5.3    waiting          1  kubernetes-worker  jujucharms   14  ubuntu  exposed

Unit                  Workload     Agent       Machine  Public address  Ports  Message
easyrsa/0             waiting      allocating  0/lxd/0                         waiting for machine
etcd/0*               blocked      idle        0        <IP_ADDRESS>         Missing relation to certificate authority.
kubernetes-master/0*  maintenance  idle        0        <IP_ADDRESS>         Rendering authentication templates.
  flannel/0*          blocked      idle                 <IP_ADDRESS>         Waiting for etcd relation.
kubernetes-worker/0*  waiting      idle        1        <IP_ADDRESS>           Waiting for kubelet to start.
  flannel/1           blocked      idle                 <IP_ADDRESS>           Waiting for etcd relation.

Machine  State    DNS             Inst id        Series  AZ
0        started  <IP_ADDRESS>  juju-917855-0  xenial
0/lxd/0  down                     pending        xenial
1        started  <IP_ADDRESS>    juju-917855-1  xenial

Relation      Provides           Consumes           Type
certificates  easyrsa            etcd               regular
certificates  easyrsa            kubernetes-master  regular
certificates  easyrsa            kubernetes-worker  regular
cluster       etcd               etcd               peer
etcd          etcd               flannel            regular
etcd          etcd               kubernetes-master  regular
cni           flannel            kubernetes-master  regular
cni           flannel            kubernetes-worker  regular
cni           kubernetes-master  flannel            subordinate
kube-dns      kubernetes-master  kubernetes-worker  regular
cni           kubernetes-worker  flannel            subordinate

And output from lxc list
+---------------+---------+--------------------------------+------+------------+-----------+
|     NAME      |  STATE  |              IPV4              | IPV6 |    TYPE    | SNAPSHOTS |
+---------------+---------+--------------------------------+------+------------+-----------+
| juju-44d73a-0 | RUNNING | <IP_ADDRESS> (eth0)          |      | PERSISTENT | 0         |
|               |         | <IP_ADDRESS> (lxdbr0)              |      |            |           |
+---------------+---------+--------------------------------+------+------------+-----------+
| juju-44d73a-1 | RUNNING | <IP_ADDRESS> (docker0)           |      | PERSISTENT | 0         |
|               |         | <IP_ADDRESS> (eth0)          |      |            |           |
+---------------+---------+--------------------------------+------+------------+-----------+
| juju-894d8f-0 | RUNNING | <IP_ADDRESS> (eth0)          |      | PERSISTENT | 0         |
+---------------+---------+--------------------------------+------+------------+-----------+

How did launch this cluster? Can you also juju status --format yaml easyrsa for additional output?

Hey Marco,
Launch wise, just
juju bootstrap localhost lxd
juju deploy kubernetes-core

And the output of status
model:
  name: default
  controller: lxd
  cloud: localhost
  region: localhost
  version: 2.2-beta2
  model-status:
    current: available
    since: 04 Apr 2017 15:06:01+01:00
machines:
  "0":
    juju-status:
      current: started
      since: 04 Apr 2017 15:07:35+01:00
      version: 2.2-beta2
    dns-name: <IP_ADDRESS>
    ip-addresses:
    - <IP_ADDRESS>
    instance-id: juju-19d03f-0
    machine-status:
      current: running
      message: Running
      since: 04 Apr 2017 15:07:01+01:00
    series: xenial
    network-interfaces:
      eth0:
        ip-addresses:
        - <IP_ADDRESS>
        mac-address: 00:16:3e:6a:8f:c4
        is-up: true
      lxdbr0:
        ip-addresses:
        - <IP_ADDRESS>
        mac-address: 5e:ea:ac:dd:2b:a8
        is-up: true
    containers:
      0/lxd/0:
        juju-status:
          current: down
          message: agent is not communicating with the server
          since: 04 Apr 2017 15:11:49+01:00
        instance-id: pending
        machine-status:
          current: provisioning error
          message: 'Failed to change ownership of: /var/lib/lxd/containers/juju-19d03f-0-lxd-0/rootfs'
          since: 04 Apr 2017 15:11:49+01:00
        series: xenial
    hardware: arch=amd64 cores=0 mem=0M
applications:
  easyrsa:
    charm: cs:~containers/easyrsa-7
    series: xenial
    os: ubuntu
    charm-origin: jujucharms
    charm-name: easyrsa
    charm-rev: 7
    exposed: false
    application-status:
      current: waiting
      message: waiting for machine
      since: 04 Apr 2017 15:06:47+01:00
    relations:
      client:
      - etcd
      - kubernetes-master
      - kubernetes-worker
    units:
      easyrsa/0:
        workload-status:
          current: waiting
          message: waiting for machine
          since: 04 Apr 2017 15:06:47+01:00
        juju-status:
          current: allocating
          since: 04 Apr 2017 15:06:47+01:00
        machine: 0/lxd/0

I guess
'Failed to change ownership of: /var/lib/lxd/containers/juju-19d03f-0-lxd-0/rootfs'
is the key error here, so could well be an issue on my box, rather than the bundle.  AWS deployment works fine.

Right, LXD deployments dont work ootb with K8s-core. We instead recommend the use of conjure-up.
Try instaling conjure-up and giving that a go
snap install conjure-up
conjure-up kubernetes-core

This should tweak and tune the lxd profiles and the bundle appropriately to accomodate a lxd deployment.

Hey Chuck!
Yeah, I tried that as well.  C-U bootstraps the the LXD juju controller fine, but doesn't seem to launch any of the LXD containers for the rest of the machines; just sits in "waiting for machine"
And juju status:
0        down        pending  xenial      not found
1        down        pending  xenial      not found
2        down        pending  xenial      not found
3        down        pending  xenial      not found

So, that's interesting, and problematic. Could you do the following:
juju status --format yaml

Could you also do:
lxc profile show juju-$(juju switch | awk -F/ '{print $2}')

Finally,
lxc launch ubuntu:x -p  juju-$(juju switch | awk -F/ '{print $2}')

The output of each of these as well as:
conjure-up --version
lxc version

Hey Marco,
I have the issue on both my desktop and laptop - my desktop has Juju and LXD from PPAs and my laptop from snap packages.  Both have conjure up from snaps.  I'll paste from my desktop for now (can do the same from laptop if you think there'd be any difference).
juju status --format yaml
model:
  name: conjure-up-kubernetes-core-0b1
  controller: conjure-up-localhost-5ee
  cloud: localhost
  region: localhost
  version: 2.1.2
machines:
  "0":
    juju-status:
      current: down
      message: agent is not communicating with the server
      since: 06 Apr 2017 09:36:58+01:00
    instance-id: pending
    machine-status:
      current: provisioning error
      message: not found
      since: 06 Apr 2017 09:36:58+01:00
    series: xenial
  "1":
    juju-status:
      current: down
      message: agent is not communicating with the server
      since: 06 Apr 2017 09:37:31+01:00
    instance-id: pending
    machine-status:
      current: provisioning error
      message: not found
      since: 06 Apr 2017 09:37:31+01:00
    series: xenial
  "2":
    juju-status:
      current: down
      message: agent is not communicating with the server
      since: 06 Apr 2017 09:38:05+01:00
    instance-id: pending
    machine-status:
      current: provisioning error
      message: not found
      since: 06 Apr 2017 09:38:05+01:00
    series: xenial
  "3":
    juju-status:
      current: down
      message: agent is not communicating with the server
      since: 06 Apr 2017 09:38:39+01:00
    instance-id: pending
    machine-status:
      current: provisioning error
      message: not found
      since: 06 Apr 2017 09:38:39+01:00
    series: xenial
applications:
  easyrsa:
    charm: cs:~containers/xenial/easyrsa-7
    series: xenial
    os: ubuntu
    charm-origin: jujucharms
    charm-name: easyrsa
    charm-rev: 7
    exposed: false
    application-status:
      current: waiting
      message: waiting for machine
      since: 06 Apr 2017 09:36:22+01:00
    relations:
      client:
      - etcd
      - kubernetes-master
      - kubernetes-worker
    units:
      easyrsa/0:
        workload-status:
          current: waiting
          message: waiting for machine
          since: 06 Apr 2017 09:36:22+01:00
        juju-status:
          current: allocating
          since: 06 Apr 2017 09:36:22+01:00
        machine: "0"
  etcd:
    charm: cs:~containers/xenial/etcd-24
    series: xenial
    os: ubuntu
    charm-origin: jujucharms
    charm-name: etcd
    charm-rev: 24
    exposed: false
    application-status:
      current: waiting
      message: waiting for machine
      since: 06 Apr 2017 09:36:26+01:00
    relations:
      certificates:
      - easyrsa
      cluster:
      - etcd
      db:
      - flannel
      - kubernetes-master
    units:
      etcd/0:
        workload-status:
          current: waiting
          message: waiting for machine
          since: 06 Apr 2017 09:36:26+01:00
        juju-status:
          current: allocating
          since: 06 Apr 2017 09:36:26+01:00
        machine: "1"
  flannel:
    charm: cs:~containers/xenial/flannel-11
    series: xenial
    os: ubuntu
    charm-origin: jujucharms
    charm-name: flannel
    charm-rev: 11
    exposed: false
    application-status:
      current: waiting
      message: waiting for machine
      since: 06 Apr 2017 09:36:28+01:00
    relations:
      cni:
      - kubernetes-master
      - kubernetes-worker
      etcd:
      - etcd
    subordinate-to:
    - kubernetes-master
    - kubernetes-worker
  kubernetes-master:
    charm: cs:~containers/xenial/kubernetes-master-12
    series: xenial
    os: ubuntu
    charm-origin: jujucharms
    charm-name: kubernetes-master
    charm-rev: 12
    exposed: true
    application-status:
      current: waiting
      message: waiting for machine
      since: 06 Apr 2017 09:36:31+01:00
    relations:
      certificates:
      - easyrsa
      cluster-dns:
      - kubernetes-worker
      cni:
      - flannel
      etcd:
      - etcd
      kube-api-endpoint:
      - kubernetes-worker
    units:
      kubernetes-master/0:
        workload-status:
          current: waiting
          message: waiting for machine
          since: 06 Apr 2017 09:36:31+01:00
        juju-status:
          current: allocating
          since: 06 Apr 2017 09:36:31+01:00
        machine: "2"
  kubernetes-worker:
    charm: cs:~containers/xenial/kubernetes-worker-14
    series: xenial
    os: ubuntu
    charm-origin: jujucharms
    charm-name: kubernetes-worker
    charm-rev: 14
    exposed: true
    application-status:
      current: waiting
      message: waiting for machine
      since: 06 Apr 2017 09:36:34+01:00
    relations:
      certificates:
      - easyrsa
      cni:
      - flannel
      kube-api-endpoint:
      - kubernetes-master
      kube-dns:
      - kubernetes-master
    units:
      kubernetes-worker/0:
        workload-status:
          current: waiting
          message: waiting for machine
          since: 06 Apr 2017 09:36:34+01:00
        juju-status:
          current: allocating
          since: 06 Apr 2017 09:36:34+01:00
        machine: "3"

lxc profile show juju-$(juju switch | awk -F/ '{print $2}')
config:
  boot.autostart: "true"
  linux.kernel_modules: ip_tables,ip6_tables,netlink_diag,nf_nat,overlay
  raw.lxc: |
    lxc.aa_profile=unconfined
    lxc.mount.auto=proc:rw sys:rw
  security.nesting: "true"
  security.privileged: "true"
description: ""
devices:
  aadisable:
    path: /sys/module/nf_conntrack/parameters/hashsize
    source: /dev/null
    type: disk
  aadisable1:
    path: /sys/module/apparmor/parameters/enabled
    source: /dev/null
    type: disk
  root:
    path: /
    pool: default
    type: disk
name: juju-conjure-up-kubernetes-core-0b1
used_by: []

lxc launch ubuntu:x -p  juju-$(juju switch | awk -F/ '{print $2}')
Creating darling-barnacle
error: not found

conjure-up 2.1.2
lxc 2.12
Thanks!

@joedborg Curious if you tried with the latest conjure-up (2.2.1)?

Hey @tvansteenburgh,
If I try with 2.2.2 I get:
2017-06-29 11:45:47,615 [DEBUG] conjure-up/_unspecified_spell - app.py:258 - LXD version: 2.14, Juju version: 2.2.1-zesty-amd64, conjure-up version: 2.2.2
2017-06-29 11:45:47,651 [INFO] conjure-up/_unspecified_spell - events.py:178 - Watching for shutdown
2017-06-29 11:45:47,730 [DEBUG] conjure-up/_unspecified_spell - events.py:55 - Awaiting Shutdown at conjureup/events.py:180
2017-06-29 11:45:50,536 [DEBUG] conjure-up/canonical-kubernetes - download.py:60 - Path is local filesystem, copying /snap/conjure-up/527/spells/canonical-kubernetes to /home/joe/.cache/conjure-up/canonical-kubernetes
2017-06-29 11:45:50,549 [DEBUG] conjure-up/canonical-kubernetes - utils.py:392 - Pulling bundle for canonical-kubernetes from channel: stable
2017-06-29 11:45:58,176 [INFO] conjure-up/canonical-kubernetes - common.py:77 - Bootstrapping Juju controller.
2017-06-29 11:45:58,176 [DEBUG] conjure-up/canonical-kubernetes - juju.py:139 - Bootstrapping to set region: {}
2017-06-29 11:45:58,182 [DEBUG] conjure-up/canonical-kubernetes - juju.py:170 - bootstrap cmd: ['juju', 'bootstrap', 'joyent/eu-ams-1', 'conjure-up-joyent-554', '--default-model', 'conjure-canonical-kubern-be1', '--config', 'image-stream=daily', '--config', 'enable-os-upgrade=false', '--bootstrap-series', 'xenial', '--credential', 'myjoyent']
2017-06-29 11:45:58,205 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting ModelConnected at conjureup/controllers/deploy/common.py:23
2017-06-29 11:45:58,224 [DEBUG] conjure-up/canonical-kubernetes - juju.py:179 - waiting for proc
2017-06-29 11:46:03,737 [DEBUG] conjure-up/canonical-kubernetes - juju.py:181 - proc done
2017-06-29 11:46:03,738 [ERROR] conjure-up/canonical-kubernetes - common.py:36 - Error bootstrapping controller: ['Creating Juju controller "conjure-up-joyent-554" on joyent/eu-ams-1', 'ERROR failed to bootstrap model: no image metadata found']
2017-06-29 11:46:03,740 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Setting Error at conjureup/events.py:147
2017-06-29 11:46:03,820 [ERROR] conjure-up/canonical-kubernetes - events.py:166 - Unhandled exception
Traceback (most recent call last):
  File "/snap/conjure-up/527/lib/python3.6/site-packages/conjureup/controllers/bootstrap/common.py", line 39, in do_bootstrap
    app.current_cloud_type))
Exception: Unable to bootstrap (cloud type: joyent)
2017-06-29 11:46:03,826 [DEBUG] conjure-up/canonical-kubernetes - __init__.py:21 - Showing dialog for exception: Unable to bootstrap (cloud type: joyent)
2017-06-29 11:46:05,426 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Setting Shutdown at conjureup/events.py:143
2017-06-29 11:46:05,428 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Received Shutdown at conjureup/events.py:180
2017-06-29 11:46:05,429 [INFO] conjure-up/canonical-kubernetes - events.py:184 - Shutting down
2017-06-29 11:46:07,797 [DEBUG] conjure-up/_unspecified_spell - app.py:258 - LXD version: 2.14, Juju version: 2.2.1-zesty-amd64, conjure-up version: 2.2.2
2017-06-29 11:46:07,832 [INFO] conjure-up/_unspecified_spell - events.py:178 - Watching for shutdown
2017-06-29 11:46:07,912 [DEBUG] conjure-up/_unspecified_spell - events.py:55 - Awaiting Shutdown at conjureup/events.py:180
2017-06-29 11:46:13,814 [DEBUG] conjure-up/canonical-kubernetes - download.py:60 - Path is local filesystem, copying /snap/conjure-up/527/spells/canonical-kubernetes to /home/joe/.cache/conjure-up/canonical-kubernetes
2017-06-29 11:46:13,822 [DEBUG] conjure-up/canonical-kubernetes - utils.py:392 - Pulling bundle for canonical-kubernetes from channel: stable
2017-06-29 11:46:19,987 [INFO] conjure-up/canonical-kubernetes - common.py:77 - Bootstrapping Juju controller.
2017-06-29 11:46:19,988 [DEBUG] conjure-up/canonical-kubernetes - juju.py:139 - Bootstrapping to set region: {}
2017-06-29 11:46:19,994 [DEBUG] conjure-up/canonical-kubernetes - juju.py:170 - bootstrap cmd: ['juju', 'bootstrap', 'joyent/eu-ams-1', 'conjure-up-joyent-91a', '--default-model', 'conjure-canonical-kubern-6fc', '--config', 'image-stream=daily', '--config', 'enable-os-upgrade=false', '--bootstrap-series', 'xenial', '--credential', 'myjoyent']
2017-06-29 11:46:20,020 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting ModelConnected at conjureup/controllers/deploy/common.py:23
2017-06-29 11:46:20,039 [DEBUG] conjure-up/canonical-kubernetes - juju.py:179 - waiting for proc
2017-06-29 11:46:22,031 [DEBUG] conjure-up/canonical-kubernetes - gui.py:13 - Rendering bootstrap wait
2017-06-29 11:46:22,164 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting PreDeployComplete at conjureup/juju.py:517 in task _do_deploy at conjureup/controllers/deploy/gui.py:239
2017-06-29 11:46:22,301 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting PreDeployComplete at conjureup/juju.py:517 in task _do_deploy at conjureup/controllers/deploy/gui.py:239
2017-06-29 11:46:22,416 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting PreDeployComplete at conjureup/juju.py:517 in task _do_deploy at conjureup/controllers/deploy/gui.py:239
2017-06-29 11:46:22,530 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting PreDeployComplete at conjureup/juju.py:517 in task _do_deploy at conjureup/controllers/deploy/gui.py:239
2017-06-29 11:46:22,643 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting PreDeployComplete at conjureup/juju.py:517 in task _do_deploy at conjureup/controllers/deploy/gui.py:239
2017-06-29 11:46:22,761 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting PreDeployComplete at conjureup/juju.py:517 in task _do_deploy at conjureup/controllers/deploy/gui.py:239
2017-06-29 11:46:22,771 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting Bootstrapped at conjureup/controllers/bootstrapwait/gui.py:37
2017-06-29 11:46:22,773 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting RelationsAdded:flannel at /snap/conjure-up/527/usr/lib/python3.6/asyncio/events.py:127 in task wait at conjureup/events.py:95
2017-06-29 11:46:22,775 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting RelationsAdded:easyrsa at /snap/conjure-up/527/usr/lib/python3.6/asyncio/events.py:127 in task wait at conjureup/events.py:95
2017-06-29 11:46:22,777 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting RelationsAdded:etcd at /snap/conjure-up/527/usr/lib/python3.6/asyncio/events.py:127 in task wait at conjureup/events.py:95
2017-06-29 11:46:22,779 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting RelationsAdded:kubernetes-worker at /snap/conjure-up/527/usr/lib/python3.6/asyncio/events.py:127 in task wait at conjureup/events.py:95
2017-06-29 11:46:22,781 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting RelationsAdded:kubernetes-master at /snap/conjure-up/527/usr/lib/python3.6/asyncio/events.py:127 in task wait at conjureup/events.py:95
2017-06-29 11:46:22,783 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Awaiting RelationsAdded:kubeapi-load-balancer at /snap/conjure-up/527/usr/lib/python3.6/asyncio/events.py:127 in task wait at conjureup/events.py:95
2017-06-29 11:46:26,017 [DEBUG] conjure-up/canonical-kubernetes - juju.py:181 - proc done
2017-06-29 11:46:26,018 [ERROR] conjure-up/canonical-kubernetes - common.py:36 - Error bootstrapping controller: ['Creating Juju controller "conjure-up-joyent-91a" on joyent/eu-ams-1', 'ERROR failed to bootstrap model: no image metadata found']
2017-06-29 11:46:26,020 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Setting Error at conjureup/events.py:147
2017-06-29 11:46:26,104 [ERROR] conjure-up/canonical-kubernetes - events.py:166 - Unhandled exception
Traceback (most recent call last):
  File "/snap/conjure-up/527/lib/python3.6/site-packages/conjureup/controllers/bootstrap/common.py", line 39, in do_bootstrap
    app.current_cloud_type))
Exception: Unable to bootstrap (cloud type: joyent)
2017-06-29 11:46:26,110 [DEBUG] conjure-up/canonical-kubernetes - __init__.py:21 - Showing dialog for exception: Unable to bootstrap (cloud type: joyent)
2017-06-29 11:46:32,972 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Setting Shutdown at conjureup/events.py:143
2017-06-29 11:46:32,974 [DEBUG] conjure-up/canonical-kubernetes - events.py:55 - Received Shutdown at conjureup/events.py:180
2017-06-29 11:46:32,974 [INFO] conjure-up/canonical-kubernetes - events.py:184 - Shutting down

@joedborg Okay, but that's on joyent, what about lxd?

Sorry @tvansteenburgh, I got confused with another bug I raised earlier.  It does build with conjure-up now.  The only issue is this when I try and kill the controller:
ERROR getting controller environ: getting environ using bootstrap config from client store: validating cloud spec: non-empty endpoint "<IP_ADDRESS>:58313" not valid

But this issue is resolved in conjure up

Hello,
I'm having an issue that I think is related to this. The kubernetes spell doesn't seem to finish. Attached is my log dump. I initially had the storage pool as zfs, but changed it to dir after reading this thread.  Any ideas?

[results-2018-12-09-20-03-34.tar.gz](https://github.com/juju-solutions/bundle-canonical-kubernetes/files/2661407/results-2018-12-09-20-03-34.tar.gz)

Hi @shortwavedave
I see you are deploying kubernetes on localhost on a system with nvidia hardware. And the nvidia-docker daemon fails to start. You should request for the docker runtime to be the one you get from the apt repository.
Here is how to do that, in conjure-up on the "Configure Applications" screen, before you select "Deploy", select "Configure" the kubernetes-worker, then "Show Advance Configuration" and there for "docker_runtime" select "apt".
As you can find be searching past issues, special hardware available through the lxc layer on localhost has always been giving us trouble. We are in the process of improving our docs and that will hopefully address this kind of annoyances https://github.com/juju-solutions/kubernetes-docs/issues/59 .
Thank you for using CDK

@ktsakalozos Wow, that worked. Thank you so much!

@ktsakalozos Wow, that worked. Thank you so much!

I had the same problem. Setting "docker_runtime" to "apt" solved it as well. I might not be the only one, so should it be documented somewhere ?


Quick homepage fixes

📝 Changed routes:

/

(view full size)

Commit d7820f7c7f0d6e933ff9223949924ba12949753a (https://thirdweb-9da8evz40.thirdweb-preview.com).


Allow bloom filter for no dictionary SV columns

Instructions:

The PR has to be tagged with at least one of the following labels (*):

feature
bugfix
performance
ui
backward-incompat
release-notes (**)

Remove these instructions before publishing the PR.

(*) Other labels to consider:

testing
dependencies
docker
kubernetes
observability
security
code-style
extension-point
refactor
cleanup

(**) Use release-notes label for scenarios like:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

Codecov Report

Merging #8961 (b62eb58) into master (47c637c) will decrease coverage by 44.61%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #8961       +/-   ##
=============================================
- Coverage     69.71%   25.09%   -44.62%
+ Complexity     4710       47     -4663
=============================================
  Files          1817     1805       -12
  Lines         94789    94522      -267
  Branches      14178    14163       -15
=============================================
- Hits          66083    23724    -42359
- Misses        24065    68493    +44428
+ Partials       4641     2305     -2336

Flag
Coverage Δ

integration1
?

integration2
25.09% <0.00%> (+0.16%)
:arrow_up:

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Suggest adding following tests -- Can be combined together where you generate some random data into a segment and then run queries on it or may be change any of the existing tests

Segment generation with one or more raw SV columns with bloom filter
Query execution tests on one or more raw SV columns with bloom filter.

After further testing and discussions, came to realise that people generally move to no dictionary columns if they see high dictionary sizes. Introducing a hasSet to store unique values even for non dictionary columns, just to be able to support bloom filter (This PR was using the set just to provide the cardinality value when creating bloom filter) will be counterproductive. I'm closing this PR. Will rethink and raise a new one.


fix(ios): replace deprecated statusBarOrientation

This PR fixes https://github.com/capawesome-team/capacitor-screen-orientation/issues/23:

updates convertOrientationValueToType for iOS to use the interfaceOrientation of the window scene instead of statusBarOrientation as that is deprecated from iOS 13.0 and above.
allows for backwards compatibility by leaving the original functionality in for <13.0

NOTE: I am not a Swift developer so please feel free to pull my solution apart!

Thanks @robingenz! Wondering when I can expect this to be released for use?

Thanks @robingenz! Wondering when I can expect this to be released for use?

Thank you so much!


Update the tar-rs dependency

Fixes some extraction bugs when unpacking archives.

@bors: r+ c111410

:hourglass: Testing commit c111410 with merge 708a89f...

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

:broken_heart: Test failed - cargo-win-gnu-64

@bors: retry

:hourglass: Testing commit c111410 with merge 25033b7...

:broken_heart: Test failed - cargo-linux-64

@bors: retry
On Wed, May 27, 2015 at 12:27 PM bors<EMAIL_ADDRESS>wrote:

[image: :hourglass:] Testing commit c111410
https://github.com/rust-lang/cargo/commit/c1114107919114ed36ee7e4567e2c7a5dd8ffcd4
with merge 25033b7
https://github.com/rust-lang/cargo/commit/25033b7561d7d12d5d103d8bbd0320e3ea02e312
...
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/cargo/pull/1653#issuecomment-106042537.

:hourglass: Testing commit c111410 with merge de903c7...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64


Serialize patch

[x] As a start, don't catch all exceptions, and don't fail silently if a field is missing.
[x] Tolerate string inputs in set_properties_from_json
[x] There's a monstrous list of string-to-type mappings in dace.properties.known_types. This seems brittle and hideous. We can replace this by calling an optionally implemented method.
[x] Naming scheme is off (should be to_json, not toJSON
[x] Move set_properties_from_json out of Property class
[x] Right now every implementation of toJSON/fromJSON needs to call json.dumps and json.loads. Reduce this to receive the JSON objece.

Jenkins, do your thing.

Jenkins, do your thing. Again.

Jenkins, do your thing.

Jenkins, do your thing.

Jenkins, do your thing.

@tbennun The test now fails because dace.types.struct is constructed with mix of types and typeclass fields. Unfortunately this does not seem to happen only in the initializer, so we have to track down where this happens. I assume we want it to only contain typeclasses?

Turns out the problem is that json_to_typeclass in dtypes is doing two different things at the same time (converting from string to type, and from json to object), and was failing at one of them. I've fixed the branch that was failing, but eventually we want to split this into two different functions (or refactor entirely).


Support git publishing via new prepare script

So it seems that since npm 5 you can now install dependencies via Github and it'll install devDependencies and run a prepare script.
This would mean we don't need to publish packages via npm and it makes it easier to fork and install from forks etc.
So then you can do:
npm i https://github.com/filipesilva/angular-quickstart-lib

And it'll work out of the box without a publish

The path changes in package.json are problematic, since the published directory structure needs to be as is at the moment per the packaging spec.
Plus I don't think npm5 should be a hard requirement. For those two reasons, I'm not sure we should make these changes.

alright sounds cool to me. Will use the change and enforce the team to use NPM 5 >:)
One thing I saw though is that the umd had the wrong path

Oh that's a mistake, thanks for letting me know!


linux_5_17: add hardened kernel

Description of changes
Add linux 5.17 hardened kernel.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

already done in https://github.com/NixOS/nixpkgs/commit/b79d9a846b51933229e0b9bfd625b1bb4324cc66

In master branch it gives me an error:
error: attribute 'linux_5_17_hardened' in selection path 'linux_5_17_hardened' not found
       Did you mean one of linux_5_10_hardened, linux_5_15_hardened, linux_4_14_hardened, linux_4_19_hardened or linux_5_4_hardened?

cc @Ma27 @SuperSandro2000

yeah looking this afternoon.

Going to merge now and add a backport label because it's a valid fix (and sorry for missing the relevant parts the first time)!
Though I'm wondering why  we still expose hardened in all-packages.nix (I'm actually in favor of it because I really dislike the new structure inside linuxKernels, but we should do it for non-hardened kernels as well IMHO).