Add Translations

I am unfortunately only a native speaker of English. Anybody who wishes to may step in and provide a translation for their language of choice.
For the prologue and all of the other cutscenes you may notice the chaotic formatting of the text. This was an attempt by me to re-create left aligned text so that the style of the original app could be replicated. When translating you're going to have to use the editor to add newlines and spaces to manually create the appearance of top-left aligned text. Hopefully a feature could be added to Valkyrie in the near future to eliminate the need to do this, but for now it is necessary to keep consistency between the translated version and the original version.

Hello, is this project still alive? I see it's not on Valkyrie right now, any reason?
I could translate it in Spanish, but first I would like to play it.

Hello, @EwenDC . Did you read my message?

Yes sorry life was quite busy so I never got a chance to reply. It's not on Valkyrie because I never submitted it. Due to the very dynamic nature of the scenario, I wanted to get it tested more thoroughly before releasing it for general consumption, but I only ended up getting like 2 play-tests. It took me like a solid month or two of free time around my full time job to make this scenario in the first place, so I got quite burned out from working on it and stopped.
I've tried to revisit it a few times but honestly Valkyrie's editor makes things take ten times longer to do than it should, so I haven't had the motivation to try and make some of the changes I want to. If I were to get back into Mansions of Madness in any serious way I'd probably look into contributing to Valkyrie itself to make it a more friendly experience to create for.

Yes sorry life was quite busy so I never got a chance to reply. It's not on Valkyrie because I never submitted it. Due to the very dynamic nature of the scenario, I wanted to get it tested more thoroughly before releasing it for general consumption, but I only ended up getting like 2 play-tests. It took me like a solid month or two of free time around my full time job to make this scenario in the first place, so I got quite burned out from working on it and stopped.
I've tried to revisit it a few times but honestly Valkyrie's editor makes things take ten times longer to do than it should, so I haven't had the motivation to try and make some of the changes I want to. If I were to get back into Mansions of Madness in any serious way I'd probably look into contributing to Valkyrie itself to make it a more friendly experience to create for.

Hello, @EwenDC
I see your point, but if this helps somehow, I think you made a great scenario that it's a real pity to left it unpublished. One friend of mine (who is cretating a quite ambitious scenario and he has programming skills) and I would make the playtesting you needed. I have some experience with the editor and the game itself since I have translated (and fully tested) over 50 scenarios so far. So, please, could you rethink it?

@EwenDC, does your last update mean you retake this project? Are you still interested on having some feedback from betatesters?

Hi @vidimus, Yes sorry I had another look at it and ended up catching the Mansions of Madness bug again 😀. I worked on it for a bit and pushed that update, but then life got really busy. I would definitely appreciate the play-testing, preferably after I get my next update out (hopefully in a day or two). I'll be adding a custom soundtrack and possibility of expansion content showing up (just items and monsters for now).

@EwenDC, great news! In that case, I will wait for the next update to play the scenario.

New update is out! The scenario is at a stage where I'm happy for a 1.0 release. I'll hang around for any required bugfixing or rebalancing but I won't add any more content for now to prevent burnout.

New update is out! The scenario is at a stage where I'm happy for a 1.0 release. I'll hang around for any required bugfixing or rebalancing but I won't add any more content for now to prevent burnout.

Hello, @EwenDC
I played yesterday your scenario. Great scenario! I have some feedback for you. Do you want to get it here? Or better in a private message (to avoid spoilers)?
I saw no glitches or bugs, luckily. From the technical part, the scenario works fine.

Hi @vidimus, feel free to DM me here or on Discord.

Hi @vidimus, feel free to DM me here or on Discord.

OK, I will contact you using Discord

@EwenDC is there any new about this project?

@EwenDC, is the project still alive?

Hi @vidimus. Thank you for your passion on this project and apologies for the radio silence. Unfortunately my life has gotten quite busy entering 2022 and I didn't get the chance I thought I'd have to work on this over the Christmas/New Year period. I must admit to focusing on a different project in my spare time. I'm looking to leave my current job for various reasons, so I have been working on a project that I am passionate about, while also being a good (and much needed) portfolio piece for the kind of job I wish to move into.
I do apologise as I did say that I would only do some minor bug-fixing before considering this a 1.0 release, but your excellent feedback echoed sentiments I myself had about the shortcomings of the scenario. It's probably me being overly perfectionist but I really wished to address these before release, as they felt like changes that should happen now rather than post 1.0

[Scenario Spoilers] Changes I wished to make

Add more questions to the final ritual, so it's not quite so easy to get the good ending. I'm envisioning three questions, two minor (what is their colour, what is their aspect) and one major (what is their name). Answering would have three possible outcomes:

Success: Same as current success; you'll banish the god and fight the priests, leading to a good ending if you win or slightly less good if not. Would require you answer the major question correctly and one of the minor ones.
Soft Failure: Same as current failure; you'll fight the avatar of the invading god, being an extremely difficult fight with a chance pull off a clutch win and receive a not-as-good ending. Would require you answer at least one question correctly. I originally had this as the only failure state because the question outcome was binary and I didn't want a wrong answer to just end the scenario anticlimactically. But since we now have multiple outcomes I can add...
Hard Failure: Immediate game over with a bad ending. Would require answering no questions correctly. I don't feel so bad about this being anticlimactic as it would be hard to not get at least one question right even if you guessed entirely randomly. Would serve as a good motivation for a group to try the scenario again if they managed to completely botch the investigation, rather than just accepting the soft failure as their ending.

Adjust the house so that the bad hostage outcomes are less random. Right now they're a random chance that's weighted to be higher the later you visit the house. During your play test it was a 50% chance on each hostage, but you got (un)lucky and had a good outcome on all three. This clearly made the house a quite boring location so I'd like to change it to a system where the weighted random is instead just a flat number of hostages with a bad outcome. Something along the lines of:

House visited first: 0-1 bad outcomes
House visited second: 1-2 bad outcomes
House visited third: 2-3 bad outcomes

Make some changes to the dock to make it more interesting. These are more band-aid fixes but better fixes would require major reworking and simply too much time. For now I can think of the following more easy-to-implement changes:

Add one or more roaming monsters. Honestly pretty lame because it makes all 3 locations mostly involve fighting monsters, but it is also perfectly valid to have a MoM scenario where the main focus is combat. Since the story of the scenario is quite light we probably mostly fall into that camp anyway. May be unnecessary with this change...
Remove the colour hints from the keys. There is actually no danger in opening a room containing a box of the wrong colour, but I should've foreseen people avoiding the incorrectly coloured rooms since I so strongly hinted at their colour (it wasn't just you vidimus, I also play-tested with some IRL friends who had the same assumption). This doubly hurt the enjoyment of this location because all of the randomly spawned monsters are inside the box rooms, where it was easy to never encounter them. If we make the players have to open the rooms to check the boxes, they can actually encounter the monsters and we might not need to add roaming ones.
Remove the colours from boxes entirely. Make the player have to find hints that tell them which colour each box is associated with. Make the hints a little subtle so that it feels more satisfying to deduce them (i.e. instead of saying "the company logo prominently features red" say "the company logo prominently features a colour illustration of a man holding out a tomato")

Honestly writing this list did give me a bit of motivation to boot Valkyrie back up and work on the scenario, but I've used up my evening just writing this post.... If I get a free day on a weekend I might be able to knock out some or all of these changes, but sadly this coming weekend is already booked out for me, so we'll have to see if the following weekends are any better.

Hello, @EwenDC
First, thanks a lot for such a extensive reply, with all your planned improvements for the scenario. They seem great to me, specially the ones about the ritual and the bad outcomes.
I hope you find the time needed for this, but obviously, life come first. I will be more than pleased to help you play-testing the new version, and translating it into Spanish when the final version is ready.
Best regards.

Hello, @EwenDC . How are you?
Any news about this project?
Cheers.

Hi @vidimus, thank you for your continued passion on this project. It had been both a great motivator and reminder for me to work on it. I finished work on my other project a few months ago, around the same time I started my new job. Which means now I have had time to look at this.
I have managed to implement all of the changes I wanted to make. I considered doing another round of play-testing, but at this point I think it's far better for me to just release it and stop holding up your translation. As of this moment v1.0 is officially out, and I have submitted a request to get it added to the official scenario roster.
https://github.com/NPBruce/valkyrie/issues/1581

Hi @vidimus, thank you for your continued passion on this project. It had been both a great motivator and reminder for me to work on it. I finished work on my other project a few months ago, around the same time I started my new job. Which means now I have had time to look at this.
I have managed to implement all of the changes I wanted to make. I considered doing another round of play-testing, but at this point I think it's far better for me to just release it and stop holding up your translation. As of this moment v1.0 is officially out, and I have submitted a request to get it added to the official scenario roster.
 Glad to finally see this project  ended. I will wait until you get some feedback, in case you need to improve, change or add anything to the scenario.

Hello, @EwenDC
Here is the file with the Spanish translation. Could you please add it to your scenario?
Localization.Spanish.txt


[ExaModelsJuMP] Wrapper is broken if JuMP's objective sense is set to Max

Please find attached a MWE:
using Test
using JuMP
using ExaModels
using MadNLP

model = Model()
@variable(model, 0 <= x <= 1)
@objective(model, Max, x^2)

# Optimize with JuMP
JuMP.set_optimizer(model, MadNLP.Optimizer)
JuMP.optimize!(model)
@test JuMP.objective_value(model) ≈ 1.0 rtol=1e-7

# Optimize with ExaModels
exam = ExaModels.ExaModel(model)
results = madnlp(exam)
@test results.objective ≈ 1.0 rtol=1e-7 #broken!

Addressed in #66


chore(falcosidekick): upgrade redis-stack image to 7.2.0-v11

What type of PR is this?
/kind chart-release

Any specific area of the project related to this PR?
/area falcosidekick-chart

What this PR does / why we need it:
The default image of redis-stack has been released in February 2023 and is outdated.
This should be updated to a more recent tag (see https://hub.docker.com/r/redis/redis-stack/tags).
Which issue(s) this PR fixes:

-/-
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: tberreis
Once this PR has been reviewed and has the lgtm label, please assign cpanato for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Did you test the new image?

Yes, I'm already using it and everything's working as expected.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, tberreis
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

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


Would this work with some training

1st, thank you for your great work. This is awesome.
I have a question. I am making some interesting #devart using Google neural experiment (https://pbs.twimg.com/media/CVHNNKvUYAAVCxA.jpg). My issue is that I can only produce small images of 512px-600px due to GFX memory limits. The usual process to create the art image is that I use a group of source images and apply them as style to a destination image. So the number of sources is very small (like 4 to 6) but usually of good quality and resolution (at least 2 - 3 times the resolution of the resulting image).
I wanted to use those to train a model that could be used to scale the small image. My thinking is that since the small picture is made of elements found in the larger resolution sources they should scale quite well from a model learned from them... Even if there is only a few sources. Am I right?
I tried to create a new learning model but I keep getting no resulting models when following the instructions on the site. I use an Amazon EC2 GPU vm... could this be the issue?
Let me know what you thing. While it is running:
th train.lua -method scale -model_dir models/my_model -test ../neural-style/out/beachhousev2.png -style photo

I get:
{
  random_overlay_rate : 0
  images : "./data/images.t7"
  active_cropping_rate : 0.5
  batch_size : 32
  model_file : "models/my_model/scale2.0x_model.t7"
  scale : 2
  learning_rate : 0.001
  nr_rate : 0.75
  random_unsharp_mask_rate : 0
  max_size : 256
  validation_crops : 80
  thread : -1
  patches : 16
  method : "scale"
  noise_level : 1
  style : "photo"
  gpu : -1
  data_dir : "./data"
  test : "../neural-style/out/beachhousev2.png"
  random_half_rate : 0
  validation_rate : 0.05
  jpeg_chroma_subsampling_rate : 0
  image_list : "./data/image_list.txt"
  model_dir : "models/my_model"
  active_cropping_tries : 10
  crop_size : 46
  inner_epoch : 4
  color : "rgb"
  random_color_noise_rate : 0
  backend : "cunn"
  seed : 11
  epoch : 30
}
# make validation-set
load .. 6
# 1
## resampling
 [==================================== 6/6 ======================================>] ETA: 0ms | Step: 62ms
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.029155457838594
}
.
.
.
# validation
current: nan, best: 100000
# 29
## resampling
 [==================================== 6/6 ======================================>] ETA: 0ms | Step: 63ms
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.001971720239251
}
# validation
current: nan, best: 100000
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.0019699730134259
}
# validation
current: nan, best: 100000
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.0019685453993993
}
# validation
current: nan, best: 100000
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.0019674577827876
}
# validation
current: nan, best: 100000
# 30
## resampling
 [==================================== 6/6 ======================================>] ETA: 0ms | Step: 58ms
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.0019724147989311
}
# validation
current: nan, best: 100000
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.0019706121464777
}
# validation
current: nan, best: 100000
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.0019693580947609
}
# validation
current: nan, best: 100000
## update
 [==================================== 96/96 ====================================>] ETA: 0ms | Step: 7ms
{
  loss : 0.0019682200185748
}
# validation
current: nan, best: 100000
ubuntu@ip-10-144-123-177:~/waifu2x-photo$ ls

The validation always look like:
# validation
current: nan, best: 100000

This look strange somehow. Is this what it should look like?

Use --validation_rate 0.17 option.
number of validation images = validation_rate * number_training_images.
validation_rate is 0.05 by default. (int(0.05 * 6) = 0, no validation image)
I think training on 6 images is unreasonable.
If you want to use photo model, you can use models/ukbench or models/photo.
th waifu2x.lua -model_dir models/ukbench -m scale -i input_image.png -o output.png

when you use photo branch,
th waifu2x.lua -model_dir models/photo -m scale -i input_image.png -o output.png

models/ukbench was trained on the ukbench dataset (It contains 10000 small photo).  models/photo was  trained on 5000 high-resolution raw photograph. Denoising is not supported (work in progress).

Cool, thank you!

I did a test run from 19 source pictures I use on and off as texture using a scale of 4 and I am amazed at how good the scaling work. I think running it on a small set work well as long as the same source of info was used to create the original that need scaling.
Can I keep adding pictures to the model or is it that once you are done making it you have to start from scratch? For example, if I add a new picture to my set, do I need to run learning against the 20 images or can I only run it against the 1 new to add the data to the model?

I think self-similarity based approach(e.g. SelfExSR) is better for your use case.
And single image super-resolution has its limit.

Interesting. I will have to get a matlab trial to give it a try. Too bad there is no free matlab starter version for testing purpose. I don't feel like buying the software just to play around and figure out if it work.

Also, how should I set the following values since I use hi-res input images:
-max_size
-crop_size

If your dataset is very small (less than 100), I recommend following option,
-random_half_rate 0.5 -random_color_noise_rate 0.5 -patches 1024 -epoch 200

But maybe it  will overfit.


Activate subscription confirmation fit text

Description:
FI text doesn't completely fit in 100% zoom level Chrome Mac
Maybe these kind of confirmation popups should also use styling we use for popups elsewhere?

QA passed


[http2] Stats and logging for H2 goaway error codes

It would be good to have stat counters for H2 goaway error codes so we can better understand reasons why H2 connections are forced closed by the local or remote endpoint.  Requests that failed due to immediate local or remote goaway should goaway error code and debug data in their request logs.  It would also be nice to have a config option to enable sending additional debug data in goaway messages to aid debugging.
After doing some code inspection, I think that most of the interesting goaway reasons like flow control errors and compression problems are generated inside the nghttp2 library and there may not be an existing debug hook that we could hook into for stats.

IIRC the GOAWAY reason is in the frame data here: https://github.com/envoyproxy/envoy/blob/5d8f7d785b59d1450b67f3279706b787c5641a66/source/common/http/http2/codec_impl.cc#L582 (it's possible that not all of the error reasons are as detailed as we want).

IIRC the GOAWAY reason is in the frame data here:
https://github.com/envoyproxy/envoy/blob/5d8f7d785b59d1450b67f3279706b787c5641a66/source/common/http/http2/codec_impl.cc#L582
(it's possible that not all of the error reasons are as detailed as we want).

I was mostly interested in goaway sent by Envoy.  Tracking received goaway by hooking into that code seems useful.


(GH-1995) Log where projects are loaded from

This will now log the path that a project is loaded from at info
level. This also moves the message listing loaded config files to
debug. Lastly this adds a message when Bolt is searching for a project
and doesn't find one at the path stating that the path won't be loaded
as a project.
This also does some restructuring of how logs are gathered from project
and config loading and passed back to the CLI to be logged. Because the
project and config are loaded before the logger is configured (because
log configuration is in the config), we need to store up those logs and
pass them back to the CLI so they can be logged once everything is set
up. Previously we just had a warnings instance variable on the config
class that inherited from the project class, got read and logged. The
same flow is true, but now instead of an array of messages to log at
warn level there's a new instance variable logs which stores an
ordered array of hashes, where each hash is a log level and it's
message. This lets us print the logs in order at the correct log level
in the CLI.
Closes #1995
!no-release-note

CLA signed by all contributors.


Unable to load the best accuracy model for prediction

Trained the model with custom dataset and when trying to test it with demo.py file, It gives an the below error
#Error
['model input parameters 32 100 20 1 512 256 38 25 TPS ResNet BiLSTM Attn',
'loading pretrained model from /content/deep-text-recognition-benchmark/best_accuracy.pth',
'Traceback (most recent call last):',
'  File "/content/deep-text-recognition-benchmark/demo.py", line 129, in ',
'    demo(opt)',
'  File "/content/deep-text-recognition-benchmark/demo.py", line 33, in demo',
'    model.load_state_dict(torch.load(opt.saved_model, map_location=device))',
'  File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1407, in load_state_dict',
'    self.class.name, "\n\t".join(error_msgs)))',
'RuntimeError: Error(s) in loading state_dict for DataParallel:',
'\tMissing key(s) in state_dict: "module.Transformation.LocalizationNetwork.conv.0.weight", "module.Transformation.LocalizationNetwork.conv.1.weight", "module.Transformation.LocalizationNetwork.conv.1.bias", "module.Transformation.LocalizationNetwork.conv.1.running_mean", "module.Transformation.LocalizationNetwork.conv.1.running_var", "module.Transformation.LocalizationNetwork.conv.4.weight", "module.Transformation.LocalizationNetwork.conv.5.weight", "module.Transformation.LocalizationNetwork.conv.5.bias", "module.Transformation.LocalizationNetwork.conv.5.running_mean", "module.Transformation.LocalizationNetwork.conv.5.running_var", "module.Transformation.LocalizationNetwork.conv.8.weight", "module.Transformation.LocalizationNetwork.conv.9.weight", "module.Transformation.LocalizationNetwork.conv.9.bias", "module.Transformation.LocalizationNetwork.conv.9.running_mean", "module.Transformation.LocalizationNetwork.conv.9.running_var", "module.Transformation.LocalizationNetwork.conv.12.weight", "module.Transformation.LocalizationNetwork.conv.13.weight", "module.Transformation.LocalizationNetwork.conv.13.bias", "module.Transformation.LocalizationNetwork.conv.13.running_mean", "module.Transformation.LocalizationNetwork.conv.13.running_var", "module.Transformation.LocalizationNetwork.localization_fc1.0.weight", "module.Transformation.LocalizationNetwork.localization_fc1.0.bias", "module.Transformation.LocalizationNetwork.localization_fc2.weight", "module.Transformation.LocalizationNetwork.localization_fc2.bias", "module.Transformation.GridGenerator.inv_delta_C", "module.Transformation.GridGenerator.P_hat", "module.FeatureExtraction.ConvNet.conv0_1.weight", "module.FeatureExtraction.ConvNet.bn0_1.weight", "module.FeatureExtraction.ConvNet.bn0_1.bias", "module.FeatureExtraction.ConvNet.bn0_1.running_mean", "module.FeatureExtraction.ConvNet.bn0_1.running_var", "module.FeatureExtraction.ConvNet.conv0_2.weight", "module.FeatureExtraction.ConvNet.bn0_2.weight", "module.FeatureExtraction.ConvNet.bn0_2.bias", "module.FeatureExtraction.ConvNet.bn0_2.running_mean", "module.FeatureExtraction.ConvNet.bn0_2.running_var", "module.FeatureExtraction.ConvNet.layer1.0.conv1.weight", "module.FeatureExtraction.ConvNet.layer1.0.bn1.weight", "module.FeatureExtraction.ConvNet.layer1.0.bn1.bias", "module.FeatureExtraction.ConvNet.layer1.0.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer1.0.bn1.running_var", "module.FeatureExtraction.ConvNet.layer1.0.conv2.weight", "module.FeatureExtraction.ConvNet.layer1.0.bn2.weight", "module.FeatureExtraction.ConvNet.layer1.0.bn2.bias", "module.FeatureExtraction.ConvNet.layer1.0.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer1.0.bn2.running_var", "module.FeatureExtraction.ConvNet.layer1.0.downsample.0.weight", "module.FeatureExtraction.ConvNet.layer1.0.downsample.1.weight", "module.FeatureExtraction.ConvNet.layer1.0.downsample.1.bias", "module.FeatureExtraction.ConvNet.layer1.0.downsample.1.running_mean", "module.FeatureExtraction.ConvNet.layer1.0.downsample.1.running_var", "module.FeatureExtraction.ConvNet.conv1.weight", "module.FeatureExtraction.ConvNet.bn1.weight", "module.FeatureExtraction.ConvNet.bn1.bias", "module.FeatureExtraction.ConvNet.bn1.running_mean", "module.FeatureExtraction.ConvNet.bn1.running_var", "module.FeatureExtraction.ConvNet.layer2.0.conv1.weight", "module.FeatureExtraction.ConvNet.layer2.0.bn1.weight", "module.FeatureExtraction.ConvNet.layer2.0.bn1.bias", "module.FeatureExtraction.ConvNet.layer2.0.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer2.0.bn1.running_var", "module.FeatureExtraction.ConvNet.layer2.0.conv2.weight", "module.FeatureExtraction.ConvNet.layer2.0.bn2.weight", "module.FeatureExtraction.ConvNet.layer2.0.bn2.bias", "module.FeatureExtraction.ConvNet.layer2.0.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer2.0.bn2.running_var", "module.FeatureExtraction.ConvNet.layer2.0.downsample.0.weight", "module.FeatureExtraction.ConvNet.layer2.0.downsample.1.weight", "module.FeatureExtraction.ConvNet.layer2.0.downsample.1.bias", "module.FeatureExtraction.ConvNet.layer2.0.downsample.1.running_mean", "module.FeatureExtraction.ConvNet.layer2.0.downsample.1.running_var", "module.FeatureExtraction.ConvNet.layer2.1.conv1.weight", "module.FeatureExtraction.ConvNet.layer2.1.bn1.weight", "module.FeatureExtraction.ConvNet.layer2.1.bn1.bias", "module.FeatureExtraction.ConvNet.layer2.1.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer2.1.bn1.running_var", "module.FeatureExtraction.ConvNet.layer2.1.conv2.weight", "module.FeatureExtraction.ConvNet.layer2.1.bn2.weight", "module.FeatureExtraction.ConvNet.layer2.1.bn2.bias", "module.FeatureExtraction.ConvNet.layer2.1.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer2.1.bn2.running_var", "module.FeatureExtraction.ConvNet.conv2.weight", "module.FeatureExtraction.ConvNet.bn2.weight", "module.FeatureExtraction.ConvNet.bn2.bias", "module.FeatureExtraction.ConvNet.bn2.running_mean", "module.FeatureExtraction.ConvNet.bn2.running_var", "module.FeatureExtraction.ConvNet.layer3.0.conv1.weight", "module.FeatureExtraction.ConvNet.layer3.0.bn1.weight", "module.FeatureExtraction.ConvNet.layer3.0.bn1.bias", "module.FeatureExtraction.ConvNet.layer3.0.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer3.0.bn1.running_var", "module.FeatureExtraction.ConvNet.layer3.0.conv2.weight", "module.FeatureExtraction.ConvNet.layer3.0.bn2.weight", "module.FeatureExtraction.ConvNet.layer3.0.bn2.bias", "module.FeatureExtraction.ConvNet.layer3.0.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer3.0.bn2.running_var", "module.FeatureExtraction.ConvNet.layer3.0.downsample.0.weight", "module.FeatureExtraction.ConvNet.layer3.0.downsample.1.weight", "module.FeatureExtraction.ConvNet.layer3.0.downsample.1.bias", "module.FeatureExtraction.ConvNet.layer3.0.downsample.1.running_mean", "module.FeatureExtraction.ConvNet.layer3.0.downsample.1.running_var", "module.FeatureExtraction.ConvNet.layer3.1.conv1.weight", "module.FeatureExtraction.ConvNet.layer3.1.bn1.weight", "module.FeatureExtraction.ConvNet.layer3.1.bn1.bias", "module.FeatureExtraction.ConvNet.layer3.1.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer3.1.bn1.running_var", "module.FeatureExtraction.ConvNet.layer3.1.conv2.weight", "module.FeatureExtraction.ConvNet.layer3.1.bn2.weight", "module.FeatureExtraction.ConvNet.layer3.1.bn2.bias", "module.FeatureExtraction.ConvNet.layer3.1.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer3.1.bn2.running_var", "module.FeatureExtraction.ConvNet.layer3.2.conv1.weight", "module.FeatureExtraction.ConvNet.layer3.2.bn1.weight", "module.FeatureExtraction.ConvNet.layer3.2.bn1.bias", "module.FeatureExtraction.ConvNet.layer3.2.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer3.2.bn1.running_var", "module.FeatureExtraction.ConvNet.layer3.2.conv2.weight", "module.FeatureExtraction.ConvNet.layer3.2.bn2.weight", "module.FeatureExtraction.ConvNet.layer3.2.bn2.bias", "module.FeatureExtraction.ConvNet.layer3.2.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer3.2.bn2.running_var", "module.FeatureExtraction.ConvNet.layer3.3.conv1.weight", "module.FeatureExtraction.ConvNet.layer3.3.bn1.weight", "module.FeatureExtraction.ConvNet.layer3.3.bn1.bias", "module.FeatureExtraction.ConvNet.layer3.3.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer3.3.bn1.running_var", "module.FeatureExtraction.ConvNet.layer3.3.conv2.weight", "module.FeatureExtraction.ConvNet.layer3.3.bn2.weight", "module.FeatureExtraction.ConvNet.layer3.3.bn2.bias", "module.FeatureExtraction.ConvNet.layer3.3.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer3.3.bn2.running_var", "module.FeatureExtraction.ConvNet.layer3.4.conv1.weight", "module.FeatureExtraction.ConvNet.layer3.4.bn1.weight", "module.FeatureExtraction.ConvNet.layer3.4.bn1.bias", "module.FeatureExtraction.ConvNet.layer3.4.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer3.4.bn1.running_var", "module.FeatureExtraction.ConvNet.layer3.4.conv2.weight", "module.FeatureExtraction.ConvNet.layer3.4.bn2.weight", "module.FeatureExtraction.ConvNet.layer3.4.bn2.bias", "module.FeatureExtraction.ConvNet.layer3.4.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer3.4.bn2.running_var", "module.FeatureExtraction.ConvNet.conv3.weight", "module.FeatureExtraction.ConvNet.bn3.weight", "module.FeatureExtraction.ConvNet.bn3.bias", "module.FeatureExtraction.ConvNet.bn3.running_mean", "module.FeatureExtraction.ConvNet.bn3.running_var", "module.FeatureExtraction.ConvNet.layer4.0.conv1.weight", "module.FeatureExtraction.ConvNet.layer4.0.bn1.weight", "module.FeatureExtraction.ConvNet.layer4.0.bn1.bias", "module.FeatureExtraction.ConvNet.layer4.0.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer4.0.bn1.running_var", "module.FeatureExtraction.ConvNet.layer4.0.conv2.weight", "module.FeatureExtraction.ConvNet.layer4.0.bn2.weight", "module.FeatureExtraction.ConvNet.layer4.0.bn2.bias", "module.FeatureExtraction.ConvNet.layer4.0.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer4.0.bn2.running_var", "module.FeatureExtraction.ConvNet.layer4.1.conv1.weight", "module.FeatureExtraction.ConvNet.layer4.1.bn1.weight", "module.FeatureExtraction.ConvNet.layer4.1.bn1.bias", "module.FeatureExtraction.ConvNet.layer4.1.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer4.1.bn1.running_var", "module.FeatureExtraction.ConvNet.layer4.1.conv2.weight", "module.FeatureExtraction.ConvNet.layer4.1.bn2.weight", "module.FeatureExtraction.ConvNet.layer4.1.bn2.bias", "module.FeatureExtraction.ConvNet.layer4.1.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer4.1.bn2.running_var", "module.FeatureExtraction.ConvNet.layer4.2.conv1.weight", "module.FeatureExtraction.ConvNet.layer4.2.bn1.weight", "module.FeatureExtraction.ConvNet.layer4.2.bn1.bias", "module.FeatureExtraction.ConvNet.layer4.2.bn1.running_mean", "module.FeatureExtraction.ConvNet.layer4.2.bn1.running_var", "module.FeatureExtraction.ConvNet.layer4.2.conv2.weight", "module.FeatureExtraction.ConvNet.layer4.2.bn2.weight", "module.FeatureExtraction.ConvNet.layer4.2.bn2.bias", "module.FeatureExtraction.ConvNet.layer4.2.bn2.running_mean", "module.FeatureExtraction.ConvNet.layer4.2.bn2.running_var", "module.FeatureExtraction.ConvNet.conv4_1.weight", "module.FeatureExtraction.ConvNet.bn4_1.weight", "module.FeatureExtraction.ConvNet.bn4_1.bias", "module.FeatureExtraction.ConvNet.bn4_1.running_mean", "module.FeatureExtraction.ConvNet.bn4_1.running_var", "module.FeatureExtraction.ConvNet.conv4_2.weight", "module.FeatureExtraction.ConvNet.bn4_2.weight", "module.FeatureExtraction.ConvNet.bn4_2.bias", "module.FeatureExtraction.ConvNet.bn4_2.running_mean", "module.FeatureExtraction.ConvNet.bn4_2.running_var", "module.Prediction.attention_cell.i2h.weight", "module.Prediction.attention_cell.h2h.weight", "module.Prediction.attention_cell.h2h.bias", "module.Prediction.attention_cell.score.weight", "module.Prediction.attention_cell.rnn.weight_ih", "module.Prediction.attention_cell.rnn.weight_hh", "module.Prediction.attention_cell.rnn.bias_ih", "module.Prediction.attention_cell.rnn.bias_hh", "module.Prediction.generator.weight", "module.Prediction.generator.bias". ',
'\tUnexpected key(s) in state_dict: "module.FeatureExtraction.ConvNet.0.weight", "module.FeatureExtraction.ConvNet.0.bias", "module.FeatureExtraction.ConvNet.3.weight", "module.FeatureExtraction.ConvNet.3.bias", "module.FeatureExtraction.ConvNet.6.weight", "module.FeatureExtraction.ConvNet.6.bias", "module.FeatureExtraction.ConvNet.8.weight", "module.FeatureExtraction.ConvNet.8.bias", "module.FeatureExtraction.ConvNet.11.weight", "module.FeatureExtraction.ConvNet.12.weight", "module.FeatureExtraction.ConvNet.12.bias", "module.FeatureExtraction.ConvNet.12.running_mean", "module.FeatureExtraction.ConvNet.12.running_var", "module.FeatureExtraction.ConvNet.12.num_batches_tracked", "module.FeatureExtraction.ConvNet.14.weight", "module.FeatureExtraction.ConvNet.15.weight", "module.FeatureExtraction.ConvNet.15.bias", "module.FeatureExtraction.ConvNet.15.running_mean", "module.FeatureExtraction.ConvNet.15.running_var", "module.FeatureExtraction.ConvNet.15.num_batches_tracked", "module.FeatureExtraction.ConvNet.18.weight", "module.FeatureExtraction.ConvNet.18.bias", "module.Prediction.weight", "module.Prediction.bias". ']
I am able to solve the loading problem by changing the demo.py file with below code
 print('loading pretrained model from %s' % opt.saved_model)
 checkpoint = torch.load(opt.saved_model, map_location=device) # Load the model file, pt, pth file can be;

 if torch.cuda.device_count() > 1:
    model = nn.DataParallel(model)
    model.load_state_dict(checkpoint)

However the predictions are going wrong/throwing garbage value after that.
Please help

I have exactly the same problem!!

The problem was solved. We need to train the custom model by keeping argument --sensitive false.
ie, parser.add_argument('--sensitive', default=False , action='store_true', help='for sensitive character mode')
also change the above line in demo.py as well.

The problem was solved. We need to train the custom model by keeping argument --sensitive false.
ie, parser.add_argument('--sensitive', default=False , action='store_true', help='for sensitive character mode')
also change the above line in demo.py as well.

I just want to do inference with the pretrained weight. But I am unable to get any sensible predicted labels at all. I manage to load the models after a while.

This issue occurs only when I run on Mac M1 chip. Otherwise it is running perfectly.


feat: SAST, Versioning & Fuzzing tests

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

GitHub release
v1.4.0

Your semantic-release bot :package::rocket:


fix: fixed the Responsiveness issue on Github button

Description
This PR addresses the inconsistency of the button at '/tools/generator' route.
Screenshot

Fixes #3008

It has been updated in this PR

It has been updated in this PR

Just confirming, are you talking about my PR? If not, can you please mention the PR in which it is updated

Mybad wrote a wrong comment
The preview is not working properly the button is still not aligned properly

Mybad wrote a wrong comment
The preview is not working properly the button is still not aligned properly

Do you want margin between the 2 buttons?

I have tried to fix it by giving it proper width.
You can look at this PR 058cf59

closing this as duplicate PR


Linting not working with Python

This issue has been moved from a ticket on Developer Community.

[severity:It's more difficult to complete my work]
I am intentionally writing errors and linting does not appear to be working at all in this build of VS 2022.

Original Comments
Feedback Bot on 7/26/2021, 00:15 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions
(no solutions)

Dupe of #6607


RDF namespaces and prefixes

A bit of a disconnect here...
Right now you can instantiate a repository instance with different prefixes.  These go from repo.context into available namespaces when parsing a resource's RDF into foo.rdf.prefixes.
However, if you PATCH a resource from the GUI (as not yet implemented), and create a new prefix like gn with the uri http://geonames.org/ontology#, add a triple, then retrieve that resource, that new prefix doesn't come along as you're stuck with the hardcoded prefixes (and mixins) that came with the repository instance.
Likely need a combination of the two.  It would be nice if you know what prefixes you'll be using to instantiate a repository handle with those in hand.  But, when you retrieve resources, it seems necessary to also parse those namespaces and include them in resource.rdf.prefixes.
Furthermore, if you use a prefix that was defined in the repository instance, but did not yet exist in the resource's RDF record with Fedora, and add a triple, Fedora doesn't pick up that prefix.  That namespace is given a prefix like ns1 in Fedora.
And that kind of makes sense... as submitting a new graph through .update() doesn't send a PATCH with prefixes defined (which does appear to include that prefix in Fedora thereafter).
Need to look into this.

A couple updates:

If you retrieve a resource with text/turtle, the prefixes found in Fedora are translated to graph.namespaces() for that resource, but not the case with at least json-ld

So far, even sending the rdf graph serialized as turtle -- which includes the prefixes -- with Content-Type text/turtle does not include the prefixes.

But might this be related to some kind of namespace pollution?

Probably have to do some more savvy binding of namespaces with things found in repo.context, convenience methods at foo.rdf for including namespaces, and then whatever comes back from get_resource, which should perhaps be locked down to text/turtle so we know we're getting namespaces?

Confirmed: binding namespace before updating propagates prefix to repository (not eventual workflow, just a hack to test):
from rdflib.namespace import Namespace, NamespaceManager
namespace_manager = NamespaceManager(foo.rdf.graph)
namespace_manager.bind('goober', Namespace('http://goober.com/'), override=True)
foo.add_triple(rdflib.term.URIRef('http://goober.com/likes'),'oysters')
foo.update()

results in front-end showing:
goober: likes
    oysters

and double confirmed:
foo = repo.get_resource('foo',response_format='text/turtle')
In [53]: list(foo.rdf.graph.namespaces())
Out[53]:
[('dc', rdflib.term.URIRef('http://purl.org/dc/elements/1.1/')),
 ('ldp', rdflib.term.URIRef('http://www.w3.org/ns/ldp#')),
...
 ('goober', rdflib.term.URIRef('http://goober.com/'))]

More fuel for fire:
Looks like if we parse the document with application/rdf+xml or text/turtle we get the following triple for a dc:title set:
(rdflib.term.URIRef('http://localhost:8080/rest/testing/foo'),
  rdflib.term.URIRef('http://purl.org/dc/elements/1.1/title'),
  rdflib.term.Literal('one hit wonder', datatype=rdflib.term.URIRef('http://www.w3.org/2001/XMLSchema#string')))

But if we parse with application/ld+json, we only get:
(rdflib.term.URIRef('http://localhost:8080/rest/foo'),
  rdflib.term.URIRef('http://purl.org/dc/elements/1.1/title'),
  rdflib.term.Literal('testing'))

The moral of this story is increasingly looking like **do not use application/ld+json for parsing resources, or updating, as it drops information.

Platypus had some of this functionality already:
https://github.com/platypus-ldp/platypus/blob/master/platypus/platypus.py

Big changes in rdfparsing branch, going with PATCH for RDF updates.  Uses new SparqlUpdate class to build query.
Only problem now is with datatype attribute for RDF terms.
The SparlqUpdate query builder is using .serialize(format='nt').decode('utf-8') to build the INSERT and DELETE portions, but this introduces the following artifacts in the query:
DELETE {
<http://localhost:8080/rest/foo/bar> <info:fedora/test/goober> "troozles"^^<http://www.w3.org/2001/XMLSchema#string> .
}

INSERT {
<http://localhost:8080/rest/foo/bar> <info:fedora/test/goober> "trockles" .
}

The answer seems to get a handle on the datatypes before moving forward.  However, closing this issue and creating a new one, as the namespaces and prefixes are enduring and parsed in a rational manner.


[go-rancher] Rancher Client example for creating a cluster

What kind of request is this (question/bug/enhancement/feature request):
Question
I am trying to use go-rancher v3 API to create cluster. I didn't see any examples wrt to go-rancher API. I am writing provisioning layer using go-rancher API's. Basically my use case is to create/delete cluster in rancher. I was able to create a cluster using  REST end point, but didn't any info how to use go-rancher api to create/delete cluster.
It would be helpful if any point out for existing go-rancher document demonstrating simple example.

Hi @rohithsharmaks, rancher/go-rancher repo is just for use with rancher v1.6.
For rancher v2.x you should use go client from rancher/types . On rancher v2.x, go client has 3 parts:

management to do tasks at global level.
cluster to do tasks at cluster level.
project to do tasks at projects level.

To create a cluster,  you need basically to:

connect to API using generated client functions.
use generated cluster functions to set cluster data and create it.

For some examples, you could take a look at rancher/cli cluster cmd and at rancher/terraform-provider-rancher2 cluster resource.

Thanks @rawmind0  for your inputs! I will try these API's and get back to you with updates.

I could able to make use of pointed reference. Closing the issue.

Could you give a Rancher Client example for creating a cluster?
I met the same error "x509: certificate signed by unknown authority"


Chapter for Docker and Java 9

@arun-gupta will help review and iterate on this. This is a rough first draft in preparation for dockercon eu 17 next week.

LGTM @spara @ManoMarks can merge it!


[ServiceBus] Add support to operation timeout

Problem:
ServiceBus is missing operation timeout support for most service operation except max_wait_time in pull receive and push receive.
According to the guideline:
https://azure.github.io/azure-sdk/python_design.html#python-client-service-args
DO support the common arguments for service operations:
---
timeout | Timeout in seconds | All service methods

and in the azure-core: https://github.com/Azure/azure-sdk-for-python/blob/35f880c37e81d9708f8571c23174aaac643543d5/sdk/core/azure-core/azure/core/pipeline/policies/_retry.py#L85
we need to add support to operation timeout for other service methods like send/schedule, etc.
The design/implementation problem here would be:

where shall we put the timeout parameter

client level config (naming could be a problem, operation_timeout)
method level parameter
both

if method level parameter, then what methods does it apply to?

how it interact with message settlement via receiver link which doesn't seem to support timeout

Echoing our OOB discussion:  My head with this is entirely in a "let's make sure we align this with our retry policy strategy" mode, so client-level seems a given.  Method level is largely a question of consistency, broad guidelines from the architects, and if there's a demand from the users. (I have an inclination on the third part that it's premature in absence of evidence, and since additive, would probably start with just class, but that's just me)
Need to think more on question 2.  That's kinda the ambiguity with retry policy as a whole, since we straddle amqp and http transactions.

PR merged: https://github.com/Azure/azure-sdk-for-python/pull/13854


Incorrect "verified" label

It seems the UI is displaying the Verified badge incorrectly on unverified groups?

Fixed in #386


[New game]: Guess The Weapon

🎮 Game Request
A Weapon Image Guessing Game From Call Of Duty, PUBG or similar sort of games. Some Portion of the image will be shown first from that you have to guess correct name of the weapon.
Point down the features
User Will get 3 chance to identify an image. In each chance bigger portion of the images will be shown. According to the number of chance for the correct guess point will be given.
Select program in which you are contributing
hacktoberfest
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @psykat1116 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @psykat1116 👋!
@kunjgit here,
Hope you are enjoying this hacktober 😀
We are excited to share that we are opening issue from our side where you will be going to add games on our website 🚀
Work on this issue 🔥
and help us building GameZone 💗
if you still haven't joined us join us on Discord
See you soon 😊

Hey @psykat1116 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


[Release] sdk/resourcemanager/timeseriesinsights/armtimeseriesinsights/1.0.0

/azp run prepare-pipelines

/azp run go - armtimeseriesinsights - ci


Support for additional "switchport default phone" commands

Enhancement summary
We would like support for the following commands natively in AVD:
(config)#switchport default phone qos trust ?
  cos   Set trust mode to CoS
  dscp  Set trust mode to DSCP

(config)#switchport default phone cos ?
  <0-7>  COS range

(config)#switchport default phone trunk untagged phone ?
  <cr>

(config)#switchport default phone vlan ?
  <1-4094>  Identifier for a Virtual LAN

(config)#switchport default phone access-list bypass ?
  <cr>

These commands are not supported todavia eos_cli_config_gen:
https://avd.arista.com/4.10/roles/eos_cli_config_gen/docs/input-variables.html#switchport-default
Note: we support "switchport default phone trunk untagged" but not "switchport default phone trunk untagged phone".
Some related TOIs:
https://www.arista.com/en/support/toi/eos-4-28-2f/15899-phone-qos-trust-mode
https://www.arista.com/en/support/toi/eos-4-24-2f/14567-802-1x-on-arista-switches
Which component of AVD is impacted
eos_cli_config_gen
Use case example
Set phone defaults globally via AVD natively.
Describe the solution you would like
Support via eos_cli_config_gen for those commands.
Describe alternatives you have considered
Raw cli.
Additional context
No response
Contributing Guide

[X] I agree to follow this project's Code of Conduct

In the realm of automation, do we really want to promote the use of these "convenience" type commands?  Is it a better practice to fully specify the interface details in a port profile?  The schema validation should probably warn about the use of this family of commands.

I'd say thats up to the user to specify this as part of the port-profile or globally. In some cases setting this up globally as a default, may benefit users missing to apply the correct port-profile, misconfigurations etc.

Also please note:
Phone configurations in the dot1x TOI are using these global commands (check dot1x interaction with phone vlan feature).
https://www.arista.com/en/support/toi/eos-4-24-2f/14567-802-1x-on-arista-switches


Update CONTRIBUTING.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@warmachine0609 Thank you for submitting a pull request (PR). I have closed the PR because the changes you have made is either inconsistent with the style the rest of the articles in the guide repository and/or do not improve the article.

Note for collaborators: this PR was not reviewed in order because it was not labelled by the bot.


frontend: make table sortable

use api endpoint to not reload data when sorting the table.

new base structure following in the next days so this is not needed atm.


FR: Reducing the amount of options in the right click menu

Would it be possible to add a setting so we can choose which options to show in the right click menu?
I'd like to reduce the right click options to only those I actually use, namely changing a yaml field from true to false or inserting dates with the calendar, I know there's the "Display field options in context menu" toggle but that removes all of the options except one.
Thank you

This would increase the complexity of the settings imho.
I've planned to bind some field actions with commands (and from there you can bind them to hotkeys) see #163 .
So you could toggle off "Display field options in context menu" and set a hotkey for your favorite fields

If I could toggle between true and false for a specific field with a hotkey then that would be a great solution as well, I'll look forward to that.
Thank you

I see that the hotkey has been added and together with the commander plugin I now have 1 "Manage field at cursor" button in my right click menu which is exactly what I was hoping for, thank you for the addition.
I'm going to mark this issue as closed since the hotkey solution works great.


How to disable pagination

I dont want pagination. I want unlimited  scroll down how can i do that

yes, that would be great!

Sorry but that's something that I won't implement, that would require a lot of changes and not everyone needs/wants it, I also believe that behavior plays against usability and SEO.


GraalVM - Unable to load PublicSuffixDatabase.gz resource from the classpath

I'm using com.squareup.okhttp3:okhttp:5.0.0-alpha.4 and graalvm-ee-java11-<IP_ADDRESS>
When using native-image I encounter this error:
Exception in thread "OkHttp Dispjava.lang.IllegalStateException: Unable to load PublicSuffixDatabase.gz resource from the classpath.
        at okhttp3.internal.publicsuffix.PublicSuffixDatabase.findMatchingRule(PublicSuffixDatabase.kt:109)
        at okhttp3.internal.publicsuffix.PublicSuffixDatabase.getEffectiveTldPlusOne(PublicSuffixDatabase.kt:71)

My project is console kotlin app and there's no proguard or r8. I actually checked any that file PublicSuffixDatabase.gz is indeed inside my jar file but after creating native executable this happens.

I think I forgot to add them to the automatic registration.
            ResourcesRegistry resourcesRegistry = ImageSingletons.lookup(ResourcesRegistry.class);
                    resourcesRegistry.addResources("...");

But until then you will need to manually register it
https://www.graalvm.org/22.0/reference-manual/native-image/Resources/

I think I forgot to add them to the automatic registration.
            ResourcesRegistry resourcesRegistry = ImageSingletons.lookup(ResourcesRegistry.class);
                    resourcesRegistry.addResources("...");

But until then you will need to manually register it
https://www.graalvm.org/22.0/reference-manual/native-image/Resources/

Thanks, I was able to generate required configs for creating a native-image using link you provided and also this one.
{
  "resources":{
    "includes":[
      {
        "pattern":"\\Qokhttp3/internal/publicsuffix/PublicSuffixDatabase.gz\\E"
      }
    ]}
}

I think I forgot to add them to the automatic registration.
            ResourcesRegistry resourcesRegistry = ImageSingletons.lookup(ResourcesRegistry.class);
                    resourcesRegistry.addResources("...");

But until then you will need to manually register it
https://www.graalvm.org/22.0/reference-manual/native-image/Resources/

Thanks, I was able to generate required configs for creating a native-image using link you provided and also this one.
{
  "resources":{
    "includes":[
      {
        "pattern":"\\Qokhttp3/internal/publicsuffix/PublicSuffixDatabase.gz\\E"
      }
    ]}
}

what does the \\Q \\E mean?
thx


Distance Question

I've just got a question on how I would make it so I can go further out from my character, in 1.14.4 which I've been using for a while I am able to go nearly as far out as I want but I can't seem to get the same with 1.16.5. Im probably just reading the config file wrong honestly.

You need to adjust the following settings in shouldersurfing.toml:
You can specify a custom min or max value for the camera offset:
[perspective.offset.min]
	#If x-offset is limited this is the minimum amount
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	min_offset_x = -3.0
	#If z-offset is limited this is the minimum amount
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	min_offset_z = -3.0
	#If y-offset is limited this is the minimum amount
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	min_offset_y = -1.0

[perspective.offset.max]
	#If z-offset is limited this is the maximum amount
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	max_offset_z = 5.0
	#If y-offset is limited this is the maximum amount
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	max_offset_y = 1.5
	#If x-offset is limited this is the maximum amount
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	max_offset_x = 3.0

Or you can disable limit alltogether:
[perspective.offset.limits]
	#Whether or not z-offset adjustment has limits
	unlimited_offset_z = false
	#Whether or not y-offset adjustment has limits
	unlimited_offset_y = false
	#Whether or not x-offset adjustment has limits
	unlimited_offset_x = false

Note that you need to edit the lines without the preceeding #

[perspective]
#Whether or not to replace the default third person perspective
replace_default_perspective = false
#Size of the camera adjustment per step
#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
camera_step_size = 0.05
#Whether or not to hide the player model if the camera gets too close to it
keep_camera_out_of_head = true
#Whether or not to limit the player reach depending on the crosshair location (perspective offset)
limit_player_reach = true
#The default perspective when you load the game
#Allowed Values: FIRST_PERSON, THIRD_PERSON_BACK, THIRD_PERSON_FRONT, SHOULDER_SURFING
default_perspective = "FIRST_PERSON"
#Whether or not to remember the last perspective used
remember_last_perspective = true
[perspective.offset]
	#Third person camera x-offset
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	offset_x = -3.8163916471489756E-16
	#Third person camera y-offset
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	offset_y = 0.0
	#Third person camera z-offset
	#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
	offset_z = 5.0

	[perspective.offset.min]
		#If x-offset is limited this is the minimum amount
		#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
		min_offset_x = -3.0
		#If z-offset is limited this is the minimum amount
		#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
		min_offset_z = -3.0
		#If y-offset is limited this is the minimum amount
		#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
		min_offset_y = -1.0

	[perspective.offset.max]
		#If z-offset is limited this is the maximum amount
		#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
		max_offset_z = 5.0
		#If y-offset is limited this is the maximum amount
		#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
		max_offset_y = 1.5
		#If x-offset is limited this is the maximum amount
		#Range: -1.7976931348623157E308 ~ 1.7976931348623157E308
		max_offset_x = 3.0

	[perspective.offset.limits]
		#Whether or not z-offset adjustment has limits
		unlimited_offset_z = false
		#Whether or not y-offset adjustment has limits
		unlimited_offset_y = false
		#Whether or not x-offset adjustment has limits
		unlimited_offset_x = false

[crosshair]
#Whether or not to show the crosshairs farther than normal
show_crosshair_farther = true
#Crosshair type to use for shoulder surfing
#Allowed Values: ADAPTIVE, DYNAMIC, STATIC, STATIC_WITH_1PP
crosshair_type = "ADAPTIVE"
[crosshair.visibility]
	#Crosshair visibility for first_person
	#Allowed Values: ALWAYS, NEVER, WHEN_AIMING, WHEN_IN_RANGE, WHEN_AIMING_OR_IN_RANGE
	first_person = "ALWAYS"
	#Crosshair visibility for shoulder_surfing
	#Allowed Values: ALWAYS, NEVER, WHEN_AIMING, WHEN_IN_RANGE, WHEN_AIMING_OR_IN_RANGE
	shoulder_surfing = "ALWAYS"
	#Crosshair visibility for third_person_back
	#Allowed Values: ALWAYS, NEVER, WHEN_AIMING, WHEN_IN_RANGE, WHEN_AIMING_OR_IN_RANGE
	third_person_back = "NEVER"
	#Crosshair visibility for third_person_front
	#Allowed Values: ALWAYS, NEVER, WHEN_AIMING, WHEN_IN_RANGE, WHEN_AIMING_OR_IN_RANGE
	third_person_front = "NEVER"

This is what I've got for my config but this is as far as I can get it to go

This is the section to disable offset limits for the respective dimensions
[perspective.offset.limits]
		#Whether or not z-offset adjustment has limits
		unlimited_offset_z = false
		#Whether or not y-offset adjustment has limits
		unlimited_offset_y = false
		#Whether or not x-offset adjustment has limits
		unlimited_offset_x = false

For example if you set unlimited_offset_z = false to unlimited_offset_z = true you can set the camera as far back as you want.
If you set unlimited_offset_y = false to unlimited_offset_y = true you can set the camera as high as you want. (unlimited_offset_x for left/right).
You can also specify a limit for each offset as i said in the first block in my first comment. Just set i.e. max_offset_z = 5.0 to max_offset_z = 10.0. This allows you to set the camera back 10 blocks instead of just 5.

Ahhh I gotcha! Problem solved :)


Login screen glitches when window is at minimum size

I think #153 will fix this but I'll just put it up nontheless

Is it still broken? I thought the minimum app size of 1280x720 fixed it

Maybe it must be bigger than that?

Leave this to me. I think it has to do with the SecurityBoxDisplay so ps ill take this

Fixed it in the latest PR


Brainstorming

@AbdelStark
I have a few questions/thoughts about the different features and possibilities of the Global Proving System:
Marketplace/Matching engine between Users, Prover provider:
Questions:
a. Provider/Business can deploy their program into:

Backend endpoint, like the Bonsai API (NIP-94 and NIP-96)
Compiled program deployed with NIP-94/96 or somewhere else: how can we serve it generically and call it in our matching engine or create a load and call program?
Maybe another way to deploy it?

In Askeladd, we can implement enum attributes to identify the way developers launch their programs:
Can be a URI for the backend post endpoint with the params required, or a program compiled and deployed on Nostr/Ipfs with the params required.
b. NIP-89:
If I understand it well, it's mainly used to send applications that can handle a specific kind of event.
We can create an Event kind of DVM (NIP-90) to verify and prove the Event.
To send Application information:
maybe we can also use the NIP-78/NIP-94/NIP-96 to send application info and metadata (URI, endpoint, download_url, params of request, payment config)
TODO and WIP:

Business

a. Send NIP-89 (maybe others) event for Application handler: (content + tags)

Program reachability: Backend, Compiled program uploaded, other way...
Create their request_id to be reachable by anyone.
Parameters of the request_json to prove/verify
Program reachability:
It can be served as a backend, or uploaded as a binary with NIP-94 and loaded and called by a Matching engine or SDK.
Payment config: Amount of Zap for Bitcoin or Tip of Joyboy/AFK for Starknet.
Difference between the Verify/Proof function of the program.

b. Subscription to request_id of the prover

Check if the user wants a prove/verify
Do a matching engine for the payment to occur if needed
Send a job result with the StarkProof and data

User

User can:

Send a request to a specific request_id, with the request_json as job_request. Use a specific event kind of the DVM maybe to differentiate proving/verifying.
Select between the Proof and Verify functions of a specific program.
Pay if needed
Get the result after paying in ZAP or Tip Starknet Nostr (not required, depends on config of the program provider)

Thanks for sharing those ideas. Will have a look and get back to you.

Closing, please move in Discussions


More content pack fixes

WIP. Adding other fixes here.
Changes:

Propagate total_files to the parent. No need to record files_complete.

TODO:

investigate why videos are being duplicated.

Tests pass @rtibbles.


It doesn't show the the trade pop-up in POE2

The app says it's already 1.36 and the taskbar is shown in game, open test is fine, but the real trade message doesn't make the pop-up shown
I also enabled POE2 support, and locate the right folder, but it resets to uncheck and located to my POE1 folder after restart app.
Do I need to download the file and run it in a seperated folder? I had no problem when using is in POE1, and java already installed.
Thanks for updating this app

Update:
I delete the folder in appdata, did a clean install, it's working for trade messages now. But there's another issue, I lowered the notification volume, it also reset after restart the app. And poe 2 support tick box also reset.
Another question is what if I want to play poe 1 for next league,  do I just change folder selection or it will automatically recognize?

You need to press save after changing things inside settings for it to be saved, that's why after restart your checkbox did uncheck and slider moved back.
Location of tab name which is shown after clicking is tied to grid location when you do set it up (grid icon on taskbar, need to save after changing it too) it cannot be moved in any other way.
If you want to use it for Poe 1 again you will need to change Poe folder location and Poe 2 support to disabled and save settings for it to work there

I did save before close settings, here is what's happening now: the item grid position, panels position all saved. Only things that reset every time are something like poe2 support check, sound levels, and Hotkeys for response buttons.

@bleeblee666 issue with saving settings will be resolved in today's release but it will come later.
For now you can follow this steps for it to be fixed for you

Close MercuryTrade if it's already running
Start it again and wait for load to finish
Go to settings
Click on choose language input
From dropdown list chose the one that you are using already or select any other one then select yours
Press Save


Paragraph name not accurate: Create Meraki Dashboard test user

[Enter feedback here]
The paragraph name "Create Meraki Dashboard test user" is not accurate. The reader is instructed to create a Dashboard role, not a user. More accurate would be the heading: "Create Meraki Dashboard Admin Roles"

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

ID: e25502b7-432c-e8ff-2dde-f21e8ba6b4db
Version Independent ID: ab9b51a1-d5c9-050b-ef67-0f1820eaf910
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Meraki Dashboard
Content Source: articles/active-directory/saas-apps/meraki-dashboard-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@JohnMoor Thank you for pointing it out. We will have this reviewed and update the documentation as required.

@JohnMoor Thank you for pointing it out. We will have this reviewed and update the documentation as required.

@v-hagamp Can you please update this article?
@chetansriv for tracking this item.

@v-hagamp Can you please update this article?
@chetansriv for tracking this item.

@v-hagamp @chetansriv  This issue is a duplicate of MicrosoftDocs/azure-docs#69420 and will get closed automatically once that is closed.

@v-rant for tracking

The issue got resolved as suggested.
#please-close


Two ideas for verifying authenticity of downloaded files

I would like to share two ideas:

Looking at the code I can see we check the consensus library file hash against the correct ones that are hardcoded, that is the correct thing to do. However, if we upload new versions of the consensus library, every time you upload a new version you have to modify the code (i know that that is something that doesn't change often). I think a better approach would be that we digitally sign the files and validate it with Nicolas's public key in the code. In that way we don't need to hardcode the hashes and change them when new versions are uploaded

The NodeBuilder downloads the bitcoin core node zip file and doesn't perform any authenticity verification, that means developers could download and run fake bitcoin core nodes. This is not very crazy IMO. We could verify the authenticity of the files here too.

What do you think?

I saw your approach in the other PR of just using the SHASUM256 file hashes of the packages. This is just perfect!


Specify agent version for lodestar

Is your feature request related to a problem? Please describe.
Right now lodestar is always identified as the default agent version of libp2p, for example js-libp2p/0.36.2, see https://github.com/libp2p/js-libp2p/blob/1f38ab7ac8380c9501b252d076bb356662978882/src/identify/consts.ts#L5
Describe the solution you'd like

We should be able to provide our own version, for example lodestar/0.41.0 using identify option https://github.com/libp2p/js-libp2p/blob/1f38ab7ac8380c9501b252d076bb356662978882/src/index.ts#L112
Inform other clients to identify lodestar using this new agent version

We can switch to js-libp2p/lodestar/1.0.0 or similar to not break crawler regex and communicate with community about the change

Imo we should change the agent version to what we want eg: lodestar/${version}.
This is something we would have wanted to do for a 1.0 release if we would have followed our original timeline.

The only two active crawlers I'm aware of is the one from Miga Labs and Blockprint. Are there any others you may know of? If it's just two, maybe we can just relay the info for them to update.

Imo we should change the agent version to what we want eg: lodestar/${version}. This is something we would have wanted to do for a 1.0 release if we would have followed our original timeline.

@wemeetagain the issue is that now everyone else in the network won't be able to detect us. It doesn't matter when we change it, it matter when others change it

Lets make issues with all clients announcing our intention. Ideally clients can have similar logic as this: https://github.com/ChainSafe/eth2-crawler/blob/d5da38aaecdc36b7d852a8ce60be68156c6a8dc0/models/peer.go#L49
agentString.startsWith('lodestar') || agentString.startsWith('js-libp2p')
This issue isn't urgent and its better to take the right steps than do something halfway.

@dapplion @wemeetagain Most have either implemented or will implement in their next releases. We should be good to go forward for a PR here.


ex1

Do you really need 25 files? Can you add a readme on how to compile?

Hello,
I have optimized and removed the unwanted files. So for ex2 I need
approximately 7 files and 1 file for ex1.
On Wed, May 17, 2017 at 10:36 PM, dRehfeldt<EMAIL_ADDRESS>wrote:

Do you really need 25 files? Can you add a readme on how to compile?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/appfs/appfs/pull/99#issuecomment-302224041, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aa6-tSHNxzI8JYz4Z6M4Blb7B3lNgiHsks5r61o0gaJpZM4Nd6J6
.


Consistent Invalid grant, aprox every week

Have the module installed and configured, works as it should for about a week, after which it shows invalid grant, the only fix i have found so far is to stop MM, delete tocken, run auth script, start MM back up.
Because this is running on an older Pi2 this process can take upwards of 10min each time as i have to wait for the google auth pages to load.
Is this an issue with the module or something in my settings?

Hi @SupaCoder ,
It sounds like you've done everything correctly with setting up the module. The issue with the expired token is a common one in projects that utilize Google authentication. Typically, when your app is in "test" mode in the Google Cloud Platform, tokens have a limited lifespan and tend to expire every seven days or so.
To mitigate this problem, you need to change the status of your app from "testing" to "production" by publishing it. Here's how you can do that:

Go to your Google Cloud Project console.
Click on the "OAuth consent screen" tab.
Scroll down to the "Publishing Status" section.
There should be an option to "Publish App." Click this button.
A prompt will appear, asking you to review the permissions and other necessary details. Make sure everything is correct and submit for publishing.

Once your app is published, the token's lifespan should be significantly extended, which will lessen the frequency of these disruptions needing a new authorization.
Best regards,
Ivan

Doesn't this make your calendar public and accessible to anyone with a Google account?

Hi @unknownuser17769, "Pubishing App" should only affect your google engine app, not your calendar. Since you're the only one authenticating to your CGP app from the MMM-GooogleCalendar instance, you're calendar info stays private, and visible only throuhg your MagicMirror instance. If anybody else were to attempt to authenticate within your app, they would need access to your cgp app, MagicMirror instance, and calendar settings. However, in this case, your data remains private since you're the only one authenticating against your own app, and the OAuth credentials are used solely within your instance of the plugin. As a result, there's no public exposure to worry about.


Update active-directory-accessmanagement-simplerulegroup.md

Added link to advanced rules

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

It looks like you're working at Microsoft (rodejo). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


feat: add ja Base README

Refs #149
Add Japanese translation of the base README.

Thank you for your review!
I reffered the README of Web-Dev-For-Beginners, but it seems to work only in GitHub, so I have fixed as you said.
@kenya-sk , since you seem to have committed the most lines of Japanese translations in this repo, could you please review this?

Of course. I will do a linguistic review.

I checked the contents. There was no linguistic problem.
Thank you for your hard work!


[FEATURE] Remove app alert for new icons

Description
We currently have a homepage alert, but this can now be removed

[!NOTE]
this can be done in the GitHub UI if you prefer

Steps:

Delete these lines of json
https://github.com/EddieHubCommunity/BioDrop/blob/040ab1e5145351a2937e9cde764b6c5a2ef77ac1/config/app.json#L4-L7

Create a pull request from your fork to our repo BioDrop

Screenshot before

Screenshot after

Screenshots
No response
Do you want to work on this issue?
None
Additional information
No response

Can I take this one please?

Sure Sara I have assigned it to you 👍

I can take this if no one is up for.

Pls assign to me.


Suggestions for tagging releases, etc.

Since apparently LESbrary.jl will depend on Oceanostics.jl, I'm thinking it would be good to have some sort of version tagging or something to help maintain both packages and its dependencies properly, no? Maybe even one of automatic tools that github provides.
I've maintained packages before (including version tagging) but they were always for personal use. @ali-ramadhan @glwagner
Since you guys have experience with that, do you have any tips?

I think it makes sense to liberally bump the release number often. You could tag a minor version every time a diagnostic is added, perhaps.
Could also make sense to register with the julia package registry so you can use the julia registrator bot:
https://github.com/JuliaRegistries/Registrator.jl

I agree it would make sense to register Oceanostics.jl as a Julia package.
I had some issues setting up multiple environments in https://github.com/CliMA/LESbrary.jl/pull/93 I think because Oceanostics.jl wasn't a registered package.
I think having CI is a requirement for registering a Julia package but I can help with setting up a GitHub Actions CI pipeline if needed.

I actually tried registering it last week. The two limiting factors were:

I need to provide and upper bound to [compat]. This is easily doable but I decided not to do it in the case of Oceananigans the versions change so quickly. I'd need to update the upper bound weekly. (Unless maybe I just set it to 1.0? Not sure if that would work and it's probably not recommended)
Adding tests (which I have no idea how to do for the time being)

I didn't do much effort back then because I thought it would mostly impact me. But since you guys are having issues because of it, it might make sense to make an effort.

Ah should I open a PR to start adding tests?
I think for package registeration a very simple runtests.jl file with using Oceanostics should suffice (and would at least make sure the package is usable).

Ah should I open a PR to start adding tests?

Sure! And I truly appreciate it. Should I make you a collaborator to make things easier?

Ah that might help just for this PR since I don't think GitHub Actions will run on PRs from forks?

Very true! Just sent you an invitation :)

Done! I think everything worked out:. Thanks for the help!
https://github.com/JuliaRegistries/General/pull/31318


Mismatch in throwing direction and the final direction of the thrown item

Description

Final direction of thrown items seems to be independent from the direction they were thrown at.
Reproduction

Walk along a straight line and throw items to left and right. Then repeat the same procedure but this time walk in the opposite way and throw items to left and right. Items thrown will face around the same direction.
Screenshots

Two blue gloves at the upper side were thrown while walking down, while the two down were thrown walking upwards.

https://github.com/space-wizards/space-station-14/pull/18578 should fix it

Tested it, this is fixed now.


Composite Type should disallow null on a required contains one

Bug description
We currently defer to a runtime error, when we can catch it at compile time.
How to reproduce
Given the following Schema
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["mongoDb"]
}

datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

model Order {
  id              String   @id @default(auto()) @map("_id") @db.ObjectId
  shippingAddress Address
}

type Address {
  street String
  city   String
  zip    String
}

It's currently possible to write:
 const order = await prisma.order.create({
    data: {
      shippingAddress: null,
    },
  })

And pass typescript's type-check.
However if you run it, you get the following error
Argument shippingAddress: Got invalid value null on prisma.createOneOrder. Provided null, expected AddressCreateEnvelopeInput or AddressCreateInput

Expected behavior
It should show a red squiggly line for null values as well
Environment & setup

OS: OSX
Database: MongoDB
Node.js version: v14.18.1

Prisma Version
Environment variables loaded from .env
prisma                  : 3.10.0-integration-composites.1
@prisma/client          : 3.10.0-integration-composites.1
Current platform        : darwin
Query Engine (Node-API) : libquery-engine ddc7068ea0a6b8c1ac10c85e13e5e396421b5c6a (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli ddc7068ea0a6b8c1ac10c85e13e5e396421b5c6a (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core ddc7068ea0a6b8c1ac10c85e13e5e396421b5c6a (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt ddc7068ea0a6b8c1ac10c85e13e5e396421b5c6a (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : query-engine-composite-basic-api-ddc7068ea0a6b8c1ac10c85e13e5e396421b5c6a
Studio                  : 0.458.0
Preview Features        : mongoDb

Next step, retest this on the latest version.

Tested in 3.12.0-dev.9 and it's fixed now!


Replaced smtp image to work on arm64

The currently used smtp image does not run on arm64. The replaced one does run on amd64 as well as arm64. This is a fairly random repo and as such a potential security risk but i couldn't find a better one. I would fork it myself but that would not be much better
See https://github.com/BytemarkHosting/docker-smtp/issues/10
Link to the repo: https://github.com/sverzegnassi/docker-smtp

@Nereuxofficial 👋
Thank you for the PR. But I think the plan is to remove mail container completely in the next version.

@Nereuxofficial 👋
Thank you for the PR. But I think the plan is to remove mail container completely in the next version.

That sounds like the better solution! Thanks for the swift reply. One less dependency to potentially break


Localisation

I updatet the current resx files in the repository to make them useable.
The problem was, that the Name property in the resx was  equal to the value that can't work because the name field is the idenifier and can inherit some special characters. I also escaped the special charakters in the Value property.
I added also a German localisation for test usage. However, it would be helpful overall if partial translations are not inserted into other messages. This makes translation into other languages difficult.
I added also an localisaation Example to show how the localization currently works. The Example inherits two language examples en-GB and de-DE yuu can switch the culture in the appesettings.json.

Hi @poison2k.  Thanks for taking the time to contribute german translations and to create an example app.
First of all, please forgive any brevity or criticism that feels pointed.  It's not intended that way.  I'm on holidays and trying to be thorough but also quick so I fear some of my questions and suggestions may be less thoughtful than I'd like.
re: resx translations
I remember now there were some issues with the resx format but I didn't follow up on it at the time because I thought there would be more interest in the new IStringLocalizer pattern using json and not much for resx.  I'm sure this is due to my not working directly with localization for quite a while.
I see that you created the CoreResources override for to use keys resx supports.  I'm currently using a test class to auto-generate both the resx and the json files from the resources classes.  It was quick and dirty because I didn't have time to make it more elegant and as I mentioned above, I didn't think there would be much desire for resx so I didn't want to put time into it.  I think we need to find a more sustainable approach that will ensure new resource strings will be included in the resx files and in the CoreResources class and we need to find a way to make CoreResources part of the core.  I don't want to be responsible for ensuring these are manually added every time.  I'm sure I will forget.  Any thoughts?
re: example app
One of the things I've realized with this framework is that a lot of the people who find it are hobbyists or relatively new to programming.  This is why I spent a lot of time rewriting the help and adding the getting started docs.  These users don't have the experience to know what is required for the example and what is extra, so it's important for the examples to be as bare bones as possible.  Users will more easily understand it this way.  I've had to spend a fair amount of time groking the many parts of this example and I'm familiar with CommandDotNet.
I'm wondering if we can simplify this example app and remove stuff that's not needed and follow patterns common in the rest of the examples and docs.
Examples:

the command classes don't need interfaces.  It looks like you're using them for DI but that's not required. Have you found a need to define interfaces for the command classes?  I've never seen a need to mock them or have multiple implementations.
are appsettings needed? It seems to me it's easier to test culture changes with the culture directive, but maybe I'm missing something.
Program.GetService is an anti-pattern
App class has always defined commands and/or hosted subcommands and the Program class handled all configuration.  This example mixes configuration across both classes, although I can see that you're doing that to take advantage of the DI to populate the IStringLocalizer.  You could get that directly from the _serviceProvider during configuration.

I wonder if it's necessary to show logging stuff here.  It would simplify the example to exclude it and users advanced enough care enough for logging could probably figure it out themselves.  Alternatively, move the registration to its own section or class and call it in a way to make it obvious it's optional.
Not adding Resources? resourcesOverride to AppRunner<T> ctor was an oversight on my part.  If you updated that, we could change the example to use new AppRunner<Menu> instead of new AppRunner(typeof(Menu), ...
In Summary
This looks promising. Let me know if anything I mentioned wasn't clear or if you have other questions.  My availability will be spotty over the next few weeks.  I'll respond and availability allows.
Cheers...

Hi @poison2k.  Thanks for taking the time to contribute german translations and to create an example app.
First of all, please forgive any brevity or criticism that feels pointed.  It's not intended that way.  I'm on holidays and trying to be thorough but also quick so I fear some of my questions and suggestions may be less thoughtful than I'd like.
re: resx translations
I remember now there were some issues with the resx format but I didn't follow up on it at the time because I thought there would be more interest in the new IStringLocalizer pattern using json and not much for resx.  I'm sure this is due to my not working directly with localization for quite a while.
I see that you created the CoreResources override for to use keys resx supports.  I'm currently using a test class to auto-generate both the resx and the json files from the resources classes.  It was quick and dirty because I didn't have time to make it more elegant and as I mentioned above, I didn't think there would be much desire for resx so I didn't want to put time into it.  I think we need to find a more sustainable approach that will ensure new resource strings will be included in the resx files and in the CoreResources class and we need to find a way to make CoreResources part of the core.  I don't want to be responsible for ensuring these are manually added every time.  I'm sure I will forget.  Any thoughts?
re: example app
One of the things I've realized with this framework is that a lot of the people who find it are hobbyists or relatively new to programming.  This is why I spent a lot of time rewriting the help and adding the getting started docs.  These users don't have the experience to know what is required for the example and what is extra, so it's important for the examples to be as bare bones as possible.  Users will more easily understand it this way.  I've had to spend a fair amount of time groking the many parts of this example and I'm familiar with CommandDotNet.
I'm wondering if we can simplify this example app and remove stuff that's not needed and follow patterns common in the rest of the examples and docs.
Examples:

the command classes don't need interfaces.  It looks like you're using them for DI but that's not required. Have you found a need to define interfaces for the command classes?  I've never seen a need to mock them or have multiple implementations.
are appsettings needed? It seems to me it's easier to test culture changes with the culture directive, but maybe I'm missing something.
Program.GetService is an anti-pattern
App class has always defined commands and/or hosted subcommands and the Program class handled all configuration.  This example mixes configuration across both classes, although I can see that you're doing that to take advantage of the DI to populate the IStringLocalizer.  You could get that directly from the _serviceProvider during configuration.

I wonder if it's necessary to show logging stuff here.  It would simplify the example to exclude it and users advanced enough care enough for logging could probably figure it out themselves.  Alternatively, move the registration to its own section or class and call it in a way to make it obvious it's optional.
Not adding Resources? resourcesOverride to AppRunner<T> ctor was an oversight on my part.  If you updated that, we could change the example to use new AppRunner<Menu> instead of new AppRunner(typeof(Menu), ...
In Summary
This looks promising. Let me know if anything I mentioned wasn't clear or if you have other questions.  My availability will be spotty over the next few weeks.  I'll respond and availability allows.
Cheers...

Hi @poison2k, I created #439 as a way to include support for resx into CommandDotNet.  This way the english resx file will be updated as new resources are added.  It also uses the member name as a key instead of the value and escapes the xml.  Can you look it over and see if it fits with how you'd use it?
To use the resx file with the ResourceProxy class, it should be instantiated with memberNameAsKey=true.  This does not seem terribly obvious so I'll need to call it out in the docs.  I'm open to better naming or another more clear approach.  It may be better to allow this as an AppSettings property so devs don't have to instantiate an instance of each ResourceProxy.

Hi Drew,
first of all thanks for your work and sorry for not responding as fast as I would like to at the moment.  But I am currently a bit overloaded with work.
I will look at your changes as soon as I can and it is still important to me to support you here.
What I have seen in the skim looks good for now.
The resx support is also essential for me. Our doc and localaization teams use only xml content. Therefore I can't switch to json.
I made the example application a bit more complex to show the problems I had with the framework and to present my solutions.
But you are right, as a simple example it is not good. But I am bound to certain designs e.g. Domain driven design in the use of Enterprise Business Applications. So I always have to be able to inject all dependencies and not use any static code.
Thanks again and I will look at everything in detail as soon as possible.

Hi @poison2k,
I went ahead and merged the other branch.  I still like the idea of your sample app.  I think if you merge in master it will make the PR much smaller.  I'll go ahead and close it for now and you can take your time getting the next iteration up.


"Broscăuți" and "Slobozia" are listed in the drop-down menu

Description:
"Broscăuți" and "Slobozia" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Broscăuți" in the search bar.

Expected results
The location is listed in the drop-down menu as "Broscăuți, Botoșani".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Broscăuți" in the search bar.

Expected results
The location is listed in the drop-down menu as "Broscăuți, Botoșani (Broscăuți)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 1
Type "Slobozia" in the search bar.

Expected results
The location is listed in the drop-down menu as "Slobozia, Botoșani (Broscăuți)".

ATTENTION:
STEP1:
Request - "Broscăuți, Botoșani"
In dropbox, the request is displayed correctly. - "Broscăuți, Botoșani"
After you click on the text, what is displayed in the window this is different - "Broscăuți, BOTOȘANI"
STEP3:
Request - "Broscăuți, Botoșani (Broscăuți)"
In dropbox, the request is displayed correctly. - "Broscăuți, Botoșani (Broscăuți)"
After you click on the text, what is displayed in the window this is different - "Broscăuți, BOTOȘANI (Broscăuți)"
STEP5:
Request - "Slobozia, Botoșani (Broscăuți)"
In dropbox, the request is displayed correctly. - ""Slobozia, Botoșani (Broscăuți)"
After you click on the text, what is displayed in the window this is different - "Slobozia, BOTOȘANI (Broscăuți)"


Fix AutoTile z-index not persisting correctly

z-index with value 1 and negative values was being ignored.

Thanks!


Document Deployment Fails

Summary
Deploying Documents via the CLI fails with the message The DocumentFolder named Folder_Name/Document_Name was not found in the workspace.
Steps To Reproduce:

Ensure a Document Folder named MyFolder exists in the source environment, with a Document named MyDocument.txt inside.
Using the following package.xml, perform a force:source:retrieve

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
  <types>
    <name>Document</name>
    <members>MyFolder</members>
    <members>MyFolder/MyDocument.txt</members>
  </types>
  <version>46.0</version>
</Package>

Using the same manifest, attempt to deploy the Document and Folder.

Expected result
The Document and Folder were deployed.
Actual result
You receive the error message The DocumentFolder named MyFolder/MyDocument.txt was not found in the workspace.
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): 7.15.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core): 46.6.0
OS and version: Windows 10 Pro

Clarification for step 3: Attempt to deploy the metadata to a sandbox using force:source:deploy

If you remove the file extension (.txt) it should work. Deploy does not take the file extension

Hi Claire! I appreciate your response. I did try both ways (with and without the file extension), although I wasn't 100% on which was the supported path, and was having trouble finding documentation.
I re-attempted deploying using the following command:
sfdx force:source:deploy -c -u myAlias -x path/to/package.xml

With the following package.xml (no file extension on file name):
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
  <types>
    <name>Document</name>
    <members>MyFolder</members>
    <members>MyFolder/MyDocument</members>
  </types>
  <version>46.0</version>
</Package>

And received the following error: The DocumentFolder named MyFolder/MyDocument was not found in the workspace.
Can you re-open this issue, or can I provide more information/open a new issue to assist?

@kristen-j-owens, I am sorry about that. I have added the bug to our backlog and hope to have the issue picked up by the team in August.

Great, thanks for the update!

@clairebianchi Any updates on this? August has come and gone and so has most of September :-P

After some hacking, we were able to get the Documents to deploy by adding the file extension to the document-meta.xml
For example, for this:
    <types>
        <members>PatronTicket_Application_Components</members>
        <members>PatronTicket_Application_Components/PatronTicketLogo.gif</members>
        <name>Document</name>
    </types>

Our source tree contains:
force-app\
  main\
    default\
      documents\
        PatronTicket_Application_Components.documentFolder-meta.xml
        PatronTicket_Application_Components\
          PatronTicketLogo.gif.document-meta.xml
          PatronTicketLogo.gif  (the actual binary)

@daveespo , I believe this had been fixed a while back and was specific to windows OS.Are you still facing any issues during deployment using package.xml? If yes, could you please provide the CLI version and the OS you are using  and the error message you get during deploy? Thank you.

@nramyasri-sf  I don't think this is fixed. We're seeing different behavior between force:source:deploy using a manifest (package.xml) and force:source:push to a scratch org.
For force:source:deploy, we need the document-meta.xml to also contain the file extension as part of its filename (as I show above in my example)
For force:source:push, the push will fail with:
     [java]     "name": "Missing Metadata File",
     [java]     "message": "Expected metadata file with '-meta.xml' extension at path: C:\\Users\\x\\y\\z\\q\\force-app\\main\\default\\documents\\PatronTicket_Application_Components\\BoxOfficeReportsIcon.document-meta.xml",

So, which is it? Should the meta.xml file have the file extension for the document in its filename or not?

@daveespo , source:deploy using -x references the package.xml and a format shown below should suffice :

Document
foldername/filename

46.0

source:push does not reference to any package.xml within the project folder. I am unsure as to where you had removed the file extensions. You need not make any changes to document-meta.xml while using source:deploy or source:push. Let me know if that answered your question. Thanks.

@nramyasri-sf  -- our project still needs to serve two masters. It is a 1GP managed package and thus we need to be able to use BOTH force:source:deploy (to push into our packager org) while being able to use force:source:push into scratch orgs.
This is apparently where the breakdown occurs. The CLI builds the deployment differently (push vs. deploy) and one requires the file extension while the other doesnt.

is fixed.


Use standard-version for releases

These changes update the existing publish workflow to instead run when tags are pushed after running the standard-version script. A sample run of these workflows is viewable on my fork here.
The scripts I've written include support for prerelease tags. If there's no intent to make prereleases after the initial 2.0 release, I can probably simplify them a bit.

Maybe there will be pre-releases even after 2.0.0. Maybe we make a 2.1.0 and need to pre-test stuff. I have seen other projects doing that, why not? Depends on the future changes...

@pamapa is there anything else I should include here? I was thinking that a workflow trigger for creating a release could be useful.

Yes something i really like in lerna (https://github.com/lerna/lerna) is semi-automatic releasing. you can interactive choose the version, it adapts files and makes a commit and pushes. Just for the record lerna is for multi-project, which this project is not :-)
Currently i coupled the publish with the github publish, which is also quiet nice, as we can make a tag, control the tag and then manually create a npm registry release by creating a github release.

Yeah Lerna is definitely intended for multi project setups. I think this project can operate just fine with automatic version tagging implemented here, so I wouldn't recommend it. Maybe a pull_request action enforcing commit message formats with commitlint would be good?

lets keep things simple, other developer shall have it easy to provide features/fixes...

i guess this MR can be closed, the CI workflows have been renamed and updated. For the release making i am researching a helper library see #272