[feature] Prebundle workspace dependencies

Is your feature request related to a problem? Please describe.
The biggest problem in vite performace is the number of files served to the browser, this becomes very big in case most of your code is placed in workspaces (which are not prebundled by vite)
To decrease the number of es modules served in big monorepos Vite could prebundle workspaces dependencies to signle files (still with node modules externalized, to prevent duplication of dependencies)
Describe the solution you'd like
Bundle workspaces in single files bundles
On workspace files change, rebundle the files again
React refresh and other plugins would still be applied, this means that workspaces would need to be bundled with rollup instead of esbuild
Describe alternatives you've considered
Additional context
This would allow to set typescript or vue files as main for internal packages, which would remove a lot of tooling in a typical private monorepo

Any progress in the feature?


ERROR in training

Traceback (most recent call last):
File "train.py", line 175, in
main()
File "train.py", line 49, in main
tb_logger = SummaryWriter(log_dir='../tb_logger/' + opt['name'])
File "C:\Program Files\Python36\lib\site-packages\tensorboardX\writer.py", line 254, in init
self._get_file_writer()
File "C:\Program Files\Python36\lib\site-packages\tensorboardX\writer.py", line 310, in _get_file_writer
self.file_writer = FileWriter(logdir=self.logdir, **self.kwargs)
TypeError: init() got an unexpected keyword argument 'log_dir'
i try to find the solution but failed.

I have not encountered this problem in my environment.
You may try to replace 'log_dir' with logdir, as the demo shows:
https://github.com/lanpa/tensorboardX/blob/bf8c6795779fbf225a6bbfefb5a53f9191e7440e/examples/demo_purge.py#L4-L6

I have not encountered this problem in my environment.
You may try to replace 'log_dir' with logdir, as the demo shows:
https://github.com/lanpa/tensorboardX/blob/bf8c6795779fbf225a6bbfefb5a53f9191e7440e/examples/demo_purge.py#L4-L6

thank you for your reply!  thank you very much!
now i want to use gray image to train not RGB image. How can i change the parameter?
And i want to generate X2 image not X4, how can i get the pretrain_model_G? without pretrain_model_G is ok?
thank you very much!!!

add an extra config to dataset color: gray.
You can train from scratch or initialize it from the X4 model.

add an extra config to dataset color: gray.
You can train from scratch or initialize it from the X4 model.

Dear xintao:
thank you for you reply!
when i want to train X2 module, i meet the problem which is
UserWarning: Using a target size (torch.Size([16, 3, 128, 128])) that is different to the input size (torch.Size([16, 3, 256, 256])). This will likely lead to incorrect results due to broadcasting. Please ensure they have the same size.
when i modify the GT_size: 256 instead of 128 in train_ESRGAN.yml , another problem
RuntimeError: CUDA out of memory. Tried to allocate 64.00 MiB (GPU 0; 22.41 GiB total capacity; 21.34 GiB already allocated; 10.38 MiB free; 21.20 MiB cached)
i'm a newer in this field, thank you for your Excellent work.thank you!

You also need to modify scale: 4, upscale: 4 for the X2 model.

You also need to modify scale: 4, upscale: 4 for the X2 model.

hi,xintao:
i have modify scale:4 into scale:2 , upscale:4 into upscale:2 ; but it still wrong:
UserWarning: Using a target size (torch.Size([16, 3, 128, 128])) that is different to the input size (torch.Size([16, 3, 256, 256])). This will likely lead to incorrect results due to broadcasting. Please ensure they have the same size.
can you tell me Where do I need to make detailed changes?
thank you very much!!!

Make sure that your output size is the same as your target.

Check your input size.
Check the upsample scale factor of your network.

Make sure that your output size is the same as your target.

Check your input size.
Check the upsample scale factor of your network.

thanks for your reply!!!
best wishes for you.

@xinntao 您好我现在特别需要训练自己的模型，应为直接用作者的模型测试效果实在不好，但是我不知道该如何做，您能教我一下吗，任何提示将不盛感激，如果可以也可以加我微信love_qinging

@1810325
Prepare your data and finetune the pre-trained model.


Bump cgroups dep to 38a61430f7ceb01581fba6dd7ead48

This allows the build to to build the release binaries and hash the resulting tar and include the hash in the release notes.
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

Codecov Report

Merging #1636 into master will decrease coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #1636     +/-   ##
=========================================
- Coverage   48.87%   48.67%   -0.2%
=========================================
  Files          27       27
  Lines        4074     4074
=========================================
- Hits         1991     1983      -8
- Misses       1668     1672      +4
- Partials      415      419      +4

Impacted Files
Coverage Δ

metadata/db.go
64.43% <0%> (-1.55%)
:arrow_down:

metadata/snapshot.go
49.34% <0%> (-0.94%)
:arrow_down:

Continue to review full report at Codecov.

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


px to em

set font-size to container for resize counter

@fenyagg the entire CSS has been rewritten in the ES6 branch, which is also scalable. Take a look at that and see if it resolves your issues.


Broken in angular6?

Upgraded from angular5 to angular6 and this package stopped working
Getting the following warnings
<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>You must install peer dependencies yourself.

It might have something to do with "Anywhere you use Renderer, now use Renderer2"

Thanks for the notify, I think I will fix very soon :)

@LastRose Fix in new version just published. (1.2.0)


[Accessibility] "document" role is needed for "monaco-hover" class div

CC @isidorn
Similar to #132275. When Ctrl+K, Ctrl+I is pressed, the focus  moves to mouse hover content where screen readers' browse mode is used. As this is a read-only area, please consider adding "document" role.

I have a better idea. Please use role = "textbox" and readonly = "true" instead of role = "document"`.
I am suggesting this because Focus on Output View(Ctrl+Shift+U) uses this technique, which offers screen readers very satisfactory accessibility.
I can share my test results using insider build once this patch is made.

This makes good sense, thanks a lot for the suggestion.
@jooyoungseo what's the benefit of using a readonly textbox instead of a role = "document" on the user side?
role="document" sounds a bit more precise, since the hover is not actually a textbox.
@alexdima do you mind if I add this role to the editor hover? I will also do it for the debug hover.

@isidorn -- We may want to test role = "document" first. If that gives us satisfactory usability, I don't think we need to switch to "textbox". I wish I could build the dev version of VSCode on my end to experiment around.

@jooyoungseo here are the steps for getting VS Code built on your machine
https://github.com/microsoft/vscode/wiki/How-to-Contribute
It should just work. So if you have time give it a try, if you hit some issue feel free to ping me.
I think this might be a good place for a code change
https://github.com/microsoft/vscode/blob/main/src/vs/editor/contrib/hover/hoverWidgets.ts#L27
Also the current role is tooltip which seems fitting to me. Maybe a better approach would be if we go to NVDA and suggest to them that if the tooltip has focus that they auto switch to browse mode?

@isidorn I am open to tweaking the role to anything that works. But I agree with you that the current tooltip role seems appropriate.

Since the tooltip aria spec doesn't require screen readers to switch to browse mode, the browse-mode activation against tooltip focus goes beyond the scope of a certain screen reader's behavior (e.g., NVDA).
Because tooltip is likely used when a temporary information pops up for a short period of time, screen readers would deliver a new tooltip info via passing-by speech against "tooltip" role. Hence, I would be reluctant to suggest changing the default behavior of screen readers for tooltip role. Instead, I would suggest VSCode takes either "document" or "textbox" role for this area. As you know, accessibility markup should contextually be utilized depending on its use case. I think this area better fits with "document" or "textbox" instead of "tooltip".

Makes sense. We could tweak the role start of October and see how it feels.
@MarcoZehe @jvesouza @zersiax for potential feedback

@isidorn -- The suggested path is not found.

I think this might be a good place for a code change https://github.com/microsoft/vscode/blob/main/src/vs/editor/contrib/hover/hoverWidgets.ts#L27

@jooyoungseo sorry about that, here's a good link
https://github.com/microsoft/vscode/blob/c9e8266ee24f34107ff52d836a4e8f533afb93c5/src/vs/base/browser/ui/hover/hoverWidget.ts#L29

Thanks @isidorn. I was able to build my demo version, but I need your help. In order to test the hover tooltip, I need to trigger an error. However, I was not able to find a way to easily create a detectable syntax error within the demo VSCode since it is a vanilla version without any languageserver extensions.

@jooyoungseo even in vanilla VS Code we have simple language server support. Here's a simple error, save the following content as test.json and open it in vanilla VS Code. This file will produce 2 errors since it does not comply with json syntax.
{
    a
}

Hope that helps!

After more thinking I have decided to open an issue on the NVDA side https://github.com/nvaccess/nvda/issues/13047
Let's see what they say, but I think we are using the correct role and we should not change anything here. Thus closing this for now and we can reopen if we decide to change the role in the end.


UserService that manages users in Horreum DB - Fixes #1260

Depends on #1304

@luis please can you rebase this PR.  I saw it depends on https://github.com/Hyperfoil/Horreum/pull/1304  I merged that PR first, now we have conflicts

@johnaohara rebased

@barreiro did you test this with a recent backup of prod db?


feat: port MeasureTheory.Measure.Regular

[x] depends on: #4018

This PR/issue depends on:

leanprover-community/mathlib4#4018
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#4018
By Dependent Issues (🤖). Happy coding!

bors merge

There are going to be merge conflicts in Mathlib.lean with all the MeasureTheory files
bors r-
bors d+

bors merge

bors merge


[PE-D][Tester A] Phone numbers can be less than 8 digits

While it is stated than phone numbers must be exactly 8 digits. Users can add 123456 for example.

Labels: type.FunctionalityBug severity.Low
original: RoeReRe/ped#2

This seems to be more of a UG bug. The UG specifies that phone numbers should be exactly 8 digits long, but our isValidPhoneNumber method checks that it is at least 3 digits long, and the error message thrown also seems to match that. Will need to update UG accordingly.

As discussed, we will change the UG to update the restrictions for phone numbers to be 3 digits instead.


[Question] How can I get the CustomAttributes for a method?

Sorry about this silly questions.
Assuming we have a method defined as below.
public class SomeClass
{
    [My("beautifulName")]
    public void DoSomeThing()
    {
         // whatever.
    }
}

public MyAttribute : Attribute
{
    public string Name { get; init; }
    public MyAttribute(string name) => Name = name;
}

Now we got a memory dump of this application, we can use ClrMD to find the SomeClass type easily, then we can easily find the DoSomeThing ClrMethod. Now, how can I find the corresponding MyAttribute instance and get the beautifulName value?
Thanks for any helping!

 Ideally you could use System.Reflection.Metadata or System.Reflection.MetadataLoadContext for this. In the simplest case, if the assembly is available as file under the same location as in the dumped process and you can afford to load it for execution, standard reflection also does it:
    static void PrintName(ClrMethod m)
    {
        ClrType t = m.Type;
        ClrModule module = t.Module;
        string path = module.Name;
        Assembly moduleAssembly = Assembly.LoadFrom(path);
        MethodBase mi = moduleAssembly.ManifestModule.ResolveMethod(m.MetadataToken);
        string attrName = mi.GetCustomAttribute<MyAttribute>().Name;
        Console.WriteLine(attrName);
    }

Thank you for your help! @MSDN-WhiteKnight
Can we load Assembly from some segment of the dump itself? It would be great if the tool doesn't have to depend on the location of the assembly dlls.
I will figure out how to inspect the metadata in the dump,  hopefully I can start from MetadataLoadContext. The information about this part is rare.

You can use DataTarget.DataReader.Read to get assembly image as byte array. I have example here: https://github.com/MSDN-WhiteKnight/CilTools/blob/e1d48edf8013cb21ac6b5be9a794301fd55b3147/CilTools.Runtime/ClrAssemblyReader.cs#L559 , but it uses ClrMD 1.1 which had DataTarget.ReadProcessMemory instead.
Not sure whether MetadataLoadContext would be able to handle assembly image loaded this way, as it has different layout than assembly file. System.Reflection.Metadata will handle it if you pass it into PEReader with PEStreamOptions.IsLoadedImage set to true.

Thank you @MSDN-WhiteKnight for your awesome example and explanation.
Actually I am not very familiar with these concepts here. I will follow your example carefully to see if I can complete this task.
Will post the result here if I can achieve it.
Thank you again!

Looks like this question was answered, thanks!


MQTT server authentication even with invalid credentials

I passed MQTT_ADMIN, MQTT_PASS and MQTT_SERVER env variables to my docker container. Yet, I AM ABLE TO connect to the MQTT server, publish and subscribe using any arbitrary credentials.

Should I add quotes in the values for my env variables MQTT_ADMIN and MQTT_PASS? The example MQTT_SERVER='localhost:1883' has quotes around the value. Basically, should it be MQTT_ADMIN='test' or MQTT_ADMIN=test? I tried both and in both cases, I was able to authenticate with the MQTT server even with wrong credentials.

Is this intended behavior? Is it possible to restrict only the admin to connect, publish and subscribe?

Which credentials does find3 use for its MQTT client? The one provided via env variables?

mosquitto_config/passwd and mosquitto_config/acl are empty. Is this intended behavior?

Sounds like somethings wrong. Did you find anything else?

@abhilash1in @fermuch this should be fixed now

I'll try again some day this week and report back.


Didn't get the purpose of the method

Hey guys, I need a clarification about situations, which this method must be applied to.
Am I right, that this method is best to use when our teacher model is much more complex than the student model? In this case we could get comparable accuracy with lower params for the student model.
Or we must use the same student and the teacher model architecture? But in this case I do not understand, why just not to perform fine-tuning using the pre-trained teacher network directly?

mark

We only experimented with student models that have the same number of parameters as the teacher model. The method should also work for scenarios with different teacher and student architectures.
The baseline right directly uses the pre-trained teacher model. We showed that perform fine-tuning using the student model works much better.

@ancientmooner Hi small question regrad to ur answer.
If the output feature map size between teacher and student is not the same, how can the feature
map distilled in your method?


Materials do not apply correctly to plane actor

Looks like the color of a single pixel is applied to the entire plane.
original texture:
https://altspacevr-demo.herokuapp.com/beach-ball.png

plane-material.ts.txt

Whoops, my bad. Fixed, going into next release.

https://github.com/Microsoft/mixed-reality-extension-unity/pull/23

verified fixed


Uploading metadata for remote SP/IDP not working

If deployer prefer to use 'upload' option than using static path or metadata URL, then there is actually no option to do that. "Upload" metadata option for IDP or SP is not working.

Fixed. @mzico - check, please.

@dmogn : I'll test and inform you the status.

"Certiiificates" page do not shows the certificate too?

root@ce:/opt/gluu-server-2.4.3/etc/certs# keytool -list -v -keystore asimbaIDP.jks
Enter keystore password:
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 7 entries
...

Alias name: https://test.gluu.info/idp/shibboleth3
Creation date: Jun 6, 2016
Entry type: trustedCertEntry
Owner: CN=ce.test.gluu.info
Issuer: CN=ce.test.gluu.info
Serial number: c709546f3fe6682b
Valid from: Mon Jun 06 13:13:35 UYT 2016 until: Tue Jun 07 13:13:35 UYT 2016
Certificate fingerprints:
MD5:  D9:AA:66:34:3E:6A:62:65:EF:65:94:DA:CE:DF:1B:06
SHA1: FE:13:65:17:0A:97:F8:FF:AF:D9:7B:EC:04:86:AD:F8:56:66:07:F7
SHA256: 59:82:E5:B7:C4:85:4F:10:38:AA:8E:EB:24:1B:24:4D:29:77:F5:B1:52:8D:B3:E4:71:30:77:36:3A:FB:9D:80
Signature algorithm name: SHA256withRSA
Version: 3
.....

Yeh, I found the problem.
Fixed. @mzico - check, please.

@dmogn : Huge improvement!! Now oxTrust can grab the cert and metadata and insert them properly. However, I still need to restart tomcat to grab the changes.
oxTrust version:
Manifest-Version: 1.0
Implementation-Title: oxTrust Server
Implementation-Version: 2.4.4-SNAPSHOT
Implementation-Vendor-Id: org.xdi
Built-By: tomcat
Build-Jdk: 1.7.0_79
Created-By: Apache Maven 3.3.9
Implementation-Build: 45de1
Archiver-Version: Plexus Archiver

Nice! I close this issue.

@dmogn : We still need to restart tomcat to apply changes....

@mzico  We have separate issue for this: https://github.com/GluuFederation/oxAsimba/issues/4
It's new functionality, I cannot add it in 2.4.4.

ah..ok... thanks!


Broken on Julia v1.8

The minimal example code from the documentation returns a 404 error when running on Julia v1.8. The /docs endpoint works. Running on Julia v1.6 works.
code:
using Oxygen
using HTTP

@get "/greet" function(req::HTTP.Request)
    return "hello world!"
end

# start the web server
serve()

server output:
[ Info: ✅ Started server: http://<IP_ADDRESS>:8080
[ Info: 📖 Documentation: http://<IP_ADDRESS>:8080/docs
[ Info: Listening on: <IP_ADDRESS>:8080, thread id: 1
[ Info: 2022-12-21T19:41:35-0500 - <IP_ADDRESS>:59706 - "GET /greet HTTP/1.1" 404

Request from Firefox:
GEThttp://<IP_ADDRESS>:8080/greet
[HTTP/1.1 404 Not Found 1413ms]

GET
	http://<IP_ADDRESS>:8080/greet
Status
404
Not Found
VersionHTTP/1.1
Transferred54 B (0 B size)
Request PriorityHighest

    Transfer-Encoding
    	chunked

    Accept
    	text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
    Accept-Encoding
    	gzip, deflate, br
    Accept-Language
    	en-US,en;q=0.5
    Connection
    	keep-alive
    DNT
    	1
    Host
    	<IP_ADDRESS>:8080
    Sec-Fetch-Dest
    	document
    Sec-Fetch-Mode
    	navigate
    Sec-Fetch-Site
    	none
    Sec-Fetch-User
    	?1
    Upgrade-Insecure-Requests
    	1
    User-Agent
    	Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0

I'm running Julia 1.8 with and your code works for me.
Have you tried to update you packages before?

Have you tried to update you packages before?

This happens even in a clean environment. Running v1.1.3.

@Octogonapus
Could you give me more details around your setup? I was able to run this example without any problems with 1.8.4 from my laptop (m1 mac)

The example code is working now for whatever reason :shrug:
Not sure why it wasn't working in the first place.


Minimum stake schedule starts at the moment of deploying KEEP token

We are deploying a new staking contract version but we want to maintain the same minimum KEEP stake schedule. To make it happen, instead of using staking contract deployment time as a schedule start, we now define a constant in MinimumStakeSchedule with a value equal to the time of deploying KEEP token. On the other hand, we want the slashing schedule (1% for the first 3 month and 50% for the next 3 months) start with the time of deploying the new TokenStaking contract. I renamed TokenStaking.minimumStakeScheduleStart to TokenStaking.deployedAt and updated Groups.sol to use the new name.
The most problematic part were unit tests. Since we now use a fixed point in the past as a minimum stake schedule start, I had to introduce TokenStakingStub for some tests with a fixed minimum stake of 100k KEEP.

I went through the code, no more comments


Notebook fixes to work in Workbench

Fixes #126

The JSON diff just shows everything changed but I assume you just changed the part about display_name -> resource_name


Timber skill doesn't work with cherry trees

I'm setting up a server, and i saw that FreeRPG got forked, and i thank you for that cause it is one of the plugins i always use.
Recently one of my friend realized that the skill doesn't work with cherry trees (i believe it also don't increase the woodcutting exp too).
edit:
I wonder if can be a good idea to turn the events into a config file, so between minecraft versions will not be that hard to workaround/update since the plugin is already well developed.

I am not using it anymore. I fixed it for myself when I ported it to 1.18.0. The issue why newer versions are not supported out of the box is that you need the class namings of the new blocks and so on. Most of it is already configured in the config files. But for some stuff to work, you need to update it in the source files as well.
To do this. You basically need to just look into my recent changes here on Github. And just need to put the stuff from the new versions in. And test it, if it works as intended.
If you are still playing and want to do it. I am happy to merge your pull request and create a release.


⚠ Bofrost.de has degraded performance

In 95f72a6, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1539 ms

Resolved: Bofrost.de performance has improved in 98e497e after 6 minutes.


Update servers.json

addition of roflmining.com for garlicoin mining

roflmining.com also shows a quick guide on setting up full garlicoin node


pool incentives needs to support multiple denoms

Currently, pool incentives module supports single denom for distribution

fixed by lockdrop module


Attached Storage Account Error

My storage accounts are not loading. Msg received is Unable to load attached Storage Account. Error: Cannot read properties of undefined (reading 'version')

Closing due to lack of response. If you're still running into this problem we recommend opening an Azure support ticket via the Azure Portal. Alternatively you can open a new issue here.


fix(README) correct lerna version

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>

Coverage remained the same at 88.538% when pulling eb2ee43dd753e39f653b23690e42ed9ecabd25a6 on jeromesimeon:js-fix-readme into 56014faa25d6e750f4f58ab45b9f5464db87f189 on accordproject:master.


Add function of list all volumes an remove inactive volumes

bash-my-aws is a great project and save me a lot of typing and time during my daily routine job, but I think there could be more enhancements, for ex, the function to list all volumes, search volume and delete volum.
sometimes, there would be a case a lot of volumes got created and but not deleted on time, so you would see something like this:

and this:

most of volumes are at a 'available' status rather than 'in-use' status. those volumes could be safely removed.
So  I want to add some functionality as below:

Add a function to list all volumes, and could also sort volumes by category.
remove all volums

I will fork you project and send a pull request later. thanks a lot.

Thanks for the kind words.
By all means go ahead and create volume functions. Just so you know, yesterday I had a discussion with some colleagues and we've come up with an improved convention for functions that list and act on resources. I wouldn't wait though as it will be easy to refactor if you keep the functions simple.


moving anonymous validation function outside of validation class

Given,
import {MinLength, MaxLength, ValidationArguments} from "class-validator";
export class Post {
    @MinLength(10, {
        message: (args: ValidationArguments) => {
            if (args.value.length === 1) {
                return "Too short, minimum length is 1 character";
            } else {
                return "Too short, minimum length is " + args.constraints[0] + " characters";
            }
        }
    })
    title: string;
}

... how can I move the anonymous function (args: ValidationArguments) outside of the class?
Form example, something similar to the below (DOES NOT WORK):
export class Post {
    @MinLength(10, {
        message: minLengthFn(args: ValidationArguments)
    })
    title: string;
}

function minLengthFn(args: ValidationArguments){
 if (args.value.length === 1) {
                return "Too short, minimum length is 1 character";
            } else {
                return "Too short, minimum length is " + args.constraints[0] + " characters";
            }
}

Is this possible? I cannot get mine to work.

You were close 😉
export function minLengthFn(args: ValidationArguments) => {
    if (args.value.length === 1) {
        return "Too short, minimum length is 1 character";
    } else {
        return "Too short, minimum length is " + args.constraints[0] + " characters";
    }
}

export class Post {
    @MinLength(10, {
        message: minLengthFn,
    })
    title: string;
}

@19majkel94 Could you please check your answer above for me. args.value.length is always zero. Thanks


Add Travis build setup

This task includes multiple things

[x] add linux + GCC 7
[x] add linux + Clang 8
[x] add OSX with latest stable clang
[ ] add Windows with VS Studio latest

In order to support windows:

https://docs.travis-ci.com/user/reference/windows/
https://chocolatey.org/packages/conan

Take note that our Windows environment is in early stages and a minimal subset of what’s available on Linux or macOS is currently supported.

You could also use GitHub actions, which supports Windows, Linux and OSX out of the box just fine. See https://help.github.com/en/articles/virtual-environments-for-github-actions

This will be replaced with Github actions.


Add describe command-line

Add $ py-ntfy describe command-line option
Improve getting started example
Fix init not storing the new topic

🎉 Configuration file: /Users/.../vict0rsch/ntfy-wrapper/.ntfy.conf
   Topics: huff-prone-dreary-mutiny
   Emails:
   Defaults:
   • title = Yo!
   • attach = hello


Add new algorithm for cycle detection

We should provide an algorithm for cycle detection that works for both directed and undirected (and mixed) graphs.
Consider basing it on #8.
Besides merely detecting cycles, it would be nice to also return Cycle instances, similar to how DetectNegativeCycle works.
http://en.wikipedia.org/wiki/Cycle_(graph_theory)#Cycle_detection

See #119.

Algorithms will be split off via #119, issue migrated to graphp/algorithms#2


Parser/Classifier for yara-matching session data

Wishlist item -- extend yara scan beyond a single packet as discussed in Slack.
"do it as a parser/classifier that just watched everything" [that] would probably be easier, compared to my suggestion of a plugin similar to parsers/http.c

Here are some pcaps and yara rules for testing:
yara-eicar-{http,netcat}.pcap should hit on "eicar".  This was just "grab a file over an easy network protocol"
yara-execs-ftp.pcap should hit on just about everything.  I transferred many files over ftp.
yara-examples.zip

These seem to already work with the current yara implementation

@jpvlsmv do you have examples that don't work?

Closing for now, feel free to reopen with more info


Refactor App.js for Better Component Structure and Performance Optimization

GSSoC Contributor
Close Issue #98
Description:
This pull request includes the following key changes and improvements to the App.js file:

Component Decomposition:

The App.js file has been broken down into smaller, reusable components (MovieList, SeatSelection, BookingForm, and ConfirmationModal) to enhance code readability and maintainability.

State Management:

Refactored state logic using useState and useEffect hooks to ensure proper handling of loading states, errors, and data fetching (movies and seat availability).

Loading and Error Handling:

Introduced loading indicators while fetching data (movies and seats).
Added user-friendly error messages to handle API failures or booking errors.

Performance Optimization:

Implemented memoization using React.memo, useMemo, and useCallback to minimize unnecessary re-renders.
Integrated lazy loading for certain components using React.lazy and Suspense to improve initial load performance.
Added debouncing logic to the search input to avoid excessive API calls.

UI/UX Enhancements:

Improved seat selection UI by color-coding available/occupied seats and adding animations for selected seats.
Included a confirmation modal to display final booking details before submission.

These changes significantly enhance the performance, structure, and user experience of the movie ticket booking app.

Please kindly consider this pull request.

@chikatlarakesh there is some error in your code.

@chikatlarakesh I'm closing this PR as I don't see any progress. Please let me know if anything has been addressed or fixed.


Not able to run child workflow from master workflow

I am running a child workflow run_cmd_ssh via another workflow invoke_item.
But it is not getting executed saying
"Failed to run task [error=Failed to find workflow [name=run_cmd_ssh] [namespace=], wf=.invoke_item, task=execute_workflow]:
Traceback (most recent call last):
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/mistral/engine/task_handler.py\", line 63, in run_task
    task.run()
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/osprofiler/profiler.py\", line 158, in wrapper
    result = f(*args, **kwargs)
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/mistral/engine/tasks.py\", line 374, in run
    self._run_new()
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/osprofiler/profiler.py\", line 158, in wrapper
    result = f(*args, **kwargs)
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/mistral/engine/tasks.py\", line 403, in _run_new
    self._schedule_actions()
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/mistral/engine/tasks.py\", line 481, in _schedule_actions
    timeout=self._get_timeout()
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/osprofiler/profiler.py\", line 158, in wrapper
    result = f(*args, **kwargs)
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/mistral/engine/actions.py\", line 538, in schedule
    wf_spec_name=self.wf_name
  File \"/opt/stackstorm/mistral/lib/python2.7/site-packages/mistral/engine/utils.py\", line 91, in resolve_workflow_definition
    (wf_spec_name, namespace)
WorkflowException: Failed to find workflow [name=run_cmd_ssh] [namespace=]",

So i debugged and found out that in mistral database in table:-workflow_definitions_v2 .
SELECT name FROM workflow_definitions_v2;
               name
----------------------------------
 std.create_instance
 std.delete_instance
invoke_item

run_cmd_ssh was not present but when i ran run_cmd_ssh separately it got added to the table
SELECT name FROM workflow_definitions_v2;
               name
----------------------------------
 std.create_instance
 std.delete_instance
invoke_item
 run_cmd_ssh

and it started working from master workflow also.
Is this expected behavior?
Also st2ctl reload should add the workflows entry into the workflow_definitions_v2 table? or do we have any separate command to handle this?

Thanks for the report. What does your workflow definition look like?

I am unable to reproduce this.
These are the steps I tried:
vagrant@st2vagrant:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.4 LTS
Release:	16.04
Codename:	xenial
vagrant@st2vagrant:~$ st2 --version
st2 2.7.1, on Python 2.7
vagrant@st2vagrant:~$

I first created these workflows:
/opt/stackstorm/packs/default/actions/parent.yaml:
---
description: Parent Mistral Action
enabled: true
runner_type: mistral-v2
entry_point: workflows/parent.yaml
name: parent
parameters:
  cmd:
    required: true
    type: string
  timeout:
    type: integer
    default: 60

/opt/stackstorm/packs/default/actions/workflows/parent.yaml:
version: '2.0'

default.parent:
    description: Parent workflow that calls child
    type: direct
    input:
        - cmd
        - timeout
    output:
        stdout: <% $.stdout %>
    tasks:
        task1:
            action: default.child cmd=<% $.cmd %> timeout=<% $.timeout %>
            publish:
                stdout: <% task(task1).result.stdout %>
                stderr: <% task(task1).result.stderr %>

/opt/stackstorm/packs/default/actions/child.yaml:
---
description: Child Mistral Action
enabled: true
runner_type: mistral-v2
entry_point: workflows/child.yaml
name: child
parameters:
  cmd:
    required: true
    type: string
  timeout:
    type: integer
    default: 60

/opt/stackstorm/packs/default/actions/workflows/child.yaml:
version: '2.0'

default.child:
    description: Child workflow to run arbitrary command
    type: direct
    input:
        - cmd
        - timeout
    output:
        stdout: <% $.stdout %>
    tasks:
        task1:
            action: core.local cmd=<% $.cmd %> timeout=<% $.timeout %>
            publish:
                stdout: <% task(task1).result.stdout %>
                stderr: <% task(task1).result.stderr %>

I then registered all actions and workflows with sudo st2ctl reload --register-all. This completed without errors.
I then ran the parent workflow:
vagrant@st2vagrant:~$ st2 run default.parent cmd=id
..
id: 5ae33cdfc4da5f06a163e0cf
action.ref: default.parent
parameters:
  cmd: id
status: failed
result_task: task1
result:
  extra:
    state: SUCCESS
    state_info: null
  stdout: uid=1002(stanley) gid=1003(stanley) groups=1003(stanley)
  tasks:
  - created_at: '2018-04-27 15:08:16'
    id: e0f580a8-3608-44ad-9b3a-a68de8702957
    input: null
    name: task1
    published:
      stderr: ''
      stdout: uid=1002(stanley) gid=1003(stanley) groups=1003(stanley)
    result:
      failed: false
      return_code: 0
      stderr: ''
      stdout: uid=1002(stanley) gid=1003(stanley) groups=1003(stanley)
      succeeded: true
    state: SUCCESS
    state_info: null
    updated_at: '2018-04-27 15:08:17'
    workflow_execution_id: 2cdf0f1e-35d6-4889-a730-ac5717a9e0cd
    workflow_name: default.child
start_timestamp: Fri, 27 Apr 2018 15:08:15 UTC
end_timestamp: Fri, 27 Apr 2018 15:08:18 UTC
+-----------------------------+------------------------+-------+---------------+----------------------------+
| id                          | status                 | task  | action        | start_timestamp            |
+-----------------------------+------------------------+-------+---------------+----------------------------+
| + 5ae33ce0c4da5f06a163e0d2  | succeeded (2s elapsed) | task1 | default.child | Fri, 27 Apr 2018 15:08:16  |
|                             |                        |       |               | UTC                        |
|    5ae33ce0c4da5f06a163e0d4 | succeeded (1s elapsed) | task1 | core.local    | Fri, 27 Apr 2018 15:08:16  |
|                             |                        |       |               | UTC                        |
+-----------------------------+------------------------+-------+---------------+----------------------------+
vagrant@st2vagrant:~$ st2 --version

This all appears to be working as expected.
Please provide a minimal set of workflows and the exact steps you go through to reproduce this problem.

There are few differences in our workflows,

You have called your child workflow with tag action: default.child cmd=<% $.cmd %> timeout=<% $.timeout %> but we are calling child workflow by tag workflow: <% $.workflowname %>, also our workflow names are dynamic.Is that the issue?

`version: '2.0'
default.parent:
description: Parent workflow that calls child
type: direct
input:
- cmd
- timeout
output:
stdout: <% $.stdout %>
tasks:
task1:
workflow: default.child cmd=<% $.cmd %> timeout=<% $.timeout %>
publish:
stdout: <% task(task1).result.stdout %>
stderr: <% task(task1).result.stderr %>`
I reloaded by st2ctl reload and ran the command st2 run default.parent cmd=hostname got the following error:
`
id: 5aec00c57052cf06e90df902
action.ref: default.parent
parameters:
cmd: hostname
status: failed
start_timestamp: Fri, 04 May 2018 06:42:13 UTC
end_timestamp: Fri, 04 May 2018 06:42:14 UTC
result:
extra:
state: ERROR
state_info: "Failed to run task [error=Failed to find workflow [name=default.child] [namespace=], wf=default.parent, task=task1]:
Traceback (most recent call last):
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/task_handler.py", line 63, in run_task
task.run()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 374, in run
self._run_new()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 403, in _run_new
self._schedule_actions()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 481, in _schedule_actions
timeout=self._get_timeout()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/actions.py", line 538, in schedule
wf_spec_name=self.wf_name
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/utils.py", line 91, in resolve_workflow_definition
(wf_spec_name, namespace)
WorkflowException: Failed to find workflow [name=default.child] [namespace=]
"
result: "Failed to run task [error=Failed to find workflow [name=default.child] [namespace=], wf=default.parent, task=task1]:
Traceback (most recent call last):
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/task_handler.py", line 63, in run_task
task.run()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 374, in run
self._run_new()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 403, in _run_new
self._schedule_actions()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 481, in _schedule_actions
timeout=self._get_timeout()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/actions.py", line 538, in schedule
wf_spec_name=self.wf_name
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/utils.py", line 91, in resolve_workflow_definition
(wf_spec_name, namespace)
WorkflowException: Failed to find workflow [name=default.child] [namespace=]
"
tasks:

created_at: '2018-05-04 06:42:14'
id: 252c02f9-c559-4f0c-9591-c3d10736b164
input: null
name: task1
published: {}
result: []
state: ERROR
state_info: "Failed to run task [error=Failed to find workflow [name=default.child] [namespace=], wf=default.parent, task=task1]:
Traceback (most recent call last):
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/task_handler.py", line 63, in run_task
task.run()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 374, in run
self._run_new()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 403, in _run_new
self._schedule_actions()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/tasks.py", line 481, in _schedule_actions
timeout=self._get_timeout()
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/osprofiler/profiler.py", line 158, in wrapper
result = f(*args, **kwargs)
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/actions.py", line 538, in schedule
wf_spec_name=self.wf_name
File "/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/engine/utils.py", line 91, in resolve_workflow_definition
(wf_spec_name, namespace)
WorkflowException: Failed to find workflow [name=default.child] [namespace=]
"
updated_at: '2018-05-04 06:42:14'
workflow_execution_id: 8d0ec7bd-18f3-4395-a787-5bae82dee713
workflow_name: default.parent

`

@nkv16786 Instead of using workflow: default.child you need to use action: default.child
The workflow keyword is used to call sub-workflows within a workbook (a workflow file that contains multiple workflows in it). https://docs.openstack.org/mistral/latest/user/wf_lang_v2.html#workflow
For more examples of workbooks, see the examples:

https://github.com/StackStorm/st2/blob/master/contrib/examples/actions/workflows/mistral-jinja-workbook-complex.yaml
https://github.com/StackStorm/st2/blob/master/contrib/examples/actions/workflows/mistral-workbook-basic.yaml
https://github.com/StackStorm/st2/blob/master/contrib/examples/actions/workflows/mistral-workbook-complex.yaml
https://github.com/StackStorm/st2/blob/master/contrib/examples/actions/workflows/mistral-workbook-multiple-subflows.yaml
https://github.com/StackStorm/st2/blob/master/contrib/examples/actions/workflows/mistral-workbook-subflows.yaml

To reiterate. The workflow keyword is used to invoke other workflows with in the same workbook, NOT StackStorm actions (what you're trying to execute).
The action keyword is used to invoke StackStorm actions. So, if default.child is a StackStorm action then you need to use the action keyword. This action can use any runner, including the mistral-v2 runner.
For an example of how to do this, see @LindsayHill 's workflow example above.

So it is not possible to invoke a child workflow of another pack? Also we can invoke workflow dynamically which is not possible with actions.
Also our scenario is working as expected if the child workflow is executed before invoking it from master workflow.

@sumeetisp Yes,  you can absolutely invoke another workflow from another pack. Simply use the action keyword: action: otherpack.other_action

But when we use action: otherpack.other_action , it doesnt accept dynamic name of the workflow.

action: dynamic_name

action: <% $.workflow_name %>

@sumeetisp Correct, rendering variables is not supported in the action stanza. There is an existing feature request out there for this behavior: https://github.com/StackStorm/st2/issues/3798

Understood.
But how does it work when the child workflow is execute first and then the master?

I just posted to #3798 with the workaround we use and are calling the dispatch pattern.
Hopefully that fits your immediate need until #3798 can be implemented.


Shortened URLs pointing to old README

Describe the bug
There are three shortened URLs throughout the project which take you to the old README.md. Shortened goo.gl urls need updating to the new README.md in cra-template.
Outdated URLs:

https://goo.gl/9VhYWB
https://goo.gl/LeUzfb
https://goo.gl/MMTaZt

Did you try recovering your dependencies?
N/A
Which terms did you search for in User Guide?
N/A
Environment
N/A
Steps to reproduce
N/A
Expected behavior
N/A
Actual behavior
N/A
Reproducible demo
N/A

We can't actually edit the shortlinks, that's why there are placeholder files there that link to the new location.


[BUG] iOS hero back when using full screen preview?

Android can using back button, iOS how to solve it??

See the issue template.


GPM Installer unZip() returning unexpected package folder name

I encountered the following issue trying to use the Direct Upload interface in the Grav Admin plugin (Grav v1.6.16 - Admin v1.9.10 with PHP 7.2.19).  On line 191 of Installer.php, $zip->getNameIndex(0) is returning the first subfolder of the theme (quark/assets) rather than the theme folder. This causes the the upload to fail because GravGPM::getPackageType() can't locate the blueprints.yaml in the given folder (line 228 in Grav\Plugin\Admin\Gpm). This seems to be unexpected behavior from getNameIndex(), not sure if something changed recently with the PHP 7.2.x. I've also encountered this with PHP 7.3.9 running on Ubuntu 18.04.

What file are you trying to direct install?

I just ran into this issue today with PHP 8.0.20 and Grav 1.7.34.  In this case, the intention was to build a ZIP of a custom theme in our CI and use the direct-install command to update that when necessary (just a simple zip -r ../../theme.zip . from inside the user/themes/custom directory after our NPM scripts run).
It fails because Grav\Common\GPM\GPM::getPackageType() is called with the path /home/<site>/public_html/tmp/Grav-62b0b1b6c75ce/blueprints/, it needs to be one level higher for the command to work.


Local fs backend should have an option to flush data to disk after write/create

There will be a risk of losing some data without f.flush():
https://github.com/datafuselabs/opendal/blob/9fdd2d6eecc4b927a489803f5728970543b50d1f/src/services/fs/backend.rs#L271-L285

A file will not be closed immediately when it goes out of scope if there are any IO operations that have not yet completed. To ensure that a file is closed immediately when it is dropped, you should call flush before dropping it. Note that this does not ensure that the file has been fully written to disk; the operating system might keep the changes around in an in-memory buffer. See the sync_all method for telling the OS to write the data to disk.

Right it should be sync_all()! I must have been thinking about sled API:(


Author pages are getting incorrectly prefixed with /blog

Getting a 404 page when I try visiting the author pages by clicking on them.

Hosted version: https://next-cms-ghost-j2jwkzzdp.vercel.app/blog/author/criodo
When I remove the /blog prefix and visit the link, it seems to work.
https://next-cms-ghost-j2jwkzzdp.vercel.app/author/criodo

Currently this project assumes that you host your Ghost CMS under a (sub-)domain, such as https://blog.crio.do instead of https://www.crio.do/blog. The automatic link substitution does not yet work, if the CMS can only be reached under a subpath. I will fix it in the next release.

Currently this project assumes that you host your Ghost CMS under a (sub-)domain, such as https://blog.crio.do instead of https://www.crio.do/blog. The automatic link substitution does not yet work, if the CMS can only be reached under a subpath. I will fix it in the next release.

Please verify if latest release fixes this problem for you too.

Please verify if latest release fixes this problem for you too.

Closing as solved.

Closing as solved.


[DOCS] Zustand create implementation marked as deprecated

Describe the Bug
https://reactflow.dev/learn/advanced-use/state-management
the zustand store init is marked as deprecated.
https://github.com/pmndrs/zustand/discussions/1937
for me the zustand docs worked as expected:
import { createWithEqualityFn } from 'zustand/traditional'
import { shallow } from 'zustand/shallow';
...
export const useFlowStore = createWithEqualityFn<RFState>((set, get) => ({
...
}), shallow);

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
used the docs to create a zustand backed RF instance
Expected behavior
no deprecation warning on the store function
Screenshots or Videos
No response
Platform

OS: macOs
Browser: Chrome

Additional context
No response

thanks! For stuff like this you can also use the https://github.com/xyflow/web repo

The guide now uses the latest API.


Change CONTRIBUTING.md to prefer single quotes

Single quotes seem to be more popular in the Python community
e.g. https://www.kennethreitz.org/essays/if-i-could-amend-pep-8)
There is automated tooling for single quotes, but not double quotes

Codecov Report

Merging #12 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   71.59%   71.59%
=======================================
  Files          17       17
  Lines         352      352
=======================================
  Hits          252      252
  Misses        100      100

Continue to review full report at Codecov.

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


ADBDEV-3247-2 Fix gpstop error when the locale is not English

Geenplum python scrips try to parse system command’s STDOUT and STDERR in english and fails if locale is different from en_US
For example, /usr/lib/gpdb/lib/python/gppylib/commands/pg.py contains class ReadPostmasterTempFile with method getResults, which try to find message "No such file or directory" and fails when locale non english. This method used in gpstop in _stop_master function and on Alt and Astra gpstop prints this error:
20221129:16:38:21:003241 gpstop:oan-astra1:gpadmin-[INFO]:-Attempting forceful termination of any leftover master process
20221129:16:38:21:003241 gpstop:oan-astra1:gpadmin-[INFO]:-Terminating processes for segment /data1/master/gpseg-1
20221129:16:38:21:003241 gpstop:oan-astra1:gpadmin-[ERROR]:-Failed to kill processes for segment /data1/master/gpseg-1: ([Errno 3] No such process)
20221129:16:38:21:003305 gpstop:oan-astra1:gpadmin-[INFO]:-Starting gpstop with args: -a -m -f -d /data1/master/gpseg-1 -B 64 -l /home/gpadmin/gpAdminLogs

On Centos with locale en_US there is no error in gpstop invocation:
20221128:12:19:07:016251 gpstop:oan-adb-pg-hba:gpadmin-[INFO]:-Attempting forceful termination of any leftover master process
20221128:12:19:07:016251 gpstop:oan-adb-pg-hba:gpadmin-[INFO]:-Terminating processes for segment /data1/master/gpseg-1
20221128:12:19:07:016318 gpstop:oan-adb-pg-hba:gpadmin-[INFO]:-Starting gpstop with args: -a -m -f -d /data1/master/gpseg-1 -B 64 -l /home/gpadmin/gpAdminLogs

This patch is a backport of 909c7f7e4f0d76151ab846ee73210efb57efb769
Also, this patch reinstalls glibc-common in docker container. This is necessary to get langpacks in docker because docker images don't contain them.

why new pr?
why not simply backport without test?


Board page is broken with Kanboard 1.2.10

Hello,
when I try to open the board page with the customizor plugin installed on Kanboard version 1.2.10 I simply get a blank screen.
I have attached the log below:
graylog-search-result-relative-172800.csv.zip

https://github.com/creecros/Customizer/blob/69a4e61b1879ffd329c0e2b4f8c1cf191ea68ebc/Plugin.php#L109
Something changed in 1.2.10, and the version compare now thinks 1.2.10 is less than 1.2.4, and its pulling the old pre 1.2.4 template. Can you confirm your version is reporting correct in your admin panel, "settings>about"
I'll take a look tonight. I just noticed the new KB version, so haven't had  the time to play with it.

that should fix it, let me know, just in case.

Thank you very much 🙌🙌


Add separate element for the Github Link.

The GitHub link is not visible to the public. Hence a separate element like :

in the top-right area would be really beneficial and readable.

sorry to bother you @matteobruni, but can you hacktoberfest label?

@Blurry-Brush yeah, but remember that only PR counts, assigning or labelling issues is not necessary for the hacktoberfest.

Oh, I didn't know that, thank you!

Hello @matteobruni, I have implemented the feature but when creating the pull request, I am getting 'can't merge automatically'. What should I do?

Hello @matteobruni, I have implemented the feature but when creating the pull request, I am getting 'can't merge automatically'. What should I do?

You have to merge from this repository main branch to yours

@matteobruni please review the PR.


Make the router example more extensive

Make the router example more extensive. It now shows an example using a config that caps all model spend, and another that has an uncapped fallback with unlimited spend.

Looks great!


“MaxCoin-QT” is damaged and can’t be opened. on Mac

I downloaded the latest release v<IP_ADDRESS>, on Mac OS X 10.13.6.
“MaxCoin-QT” is damaged and can’t be opened. You should move it to the Trash.
Can you provide an updated build please?

I have the same OS and it works fine on mine.  Someone else on the maxcoin telegram chat mentioned the same thing on 10.13.6 .. the download may be currupt, can you try downloading again and seeing if you have the same problem?  I have not been able to replicate this issue.

inactive, closing


Multiple Deployment Errors

Description
I have multiple problems when deploying after following the instructions found on the wiki (and elsewhere).
Using the exact steps in the wiki I get the following error message in the heapster log (along with a similar one for *v1.Node)
k8s.io/heapster/metrics/heapster.go:328: Failed to list *v1.Pod: Get https://kubernetes.default/api/v1/pods?resourceVersion=0: dial tcp: lookup kubernetes.default on <IP_ADDRESS>:53: no such host

According to my understanding of kubernetes, looking up kubernetes.default from inside a pod should be working but it isn't. When I replace the --source argument with the fully qualified domain name https://kubernetes.default.svc.cluster.local then lookup succeeds.
After making this change and redeploying, however, I get the following error
Error in scraping containers from kubelet:<IP_ADDRESS>:10255: failed to get all container stats from Kubelet URL "http://<IP_ADDRESS>:10255/stats/container/": Post http://<IP_ADDRESS>:10255/stats/container/: dial tcp <IP_ADDRESS>:10255: getsockopt: connection refused

I have deployed the RBAC configuration for heapster, my setup commands were:
kubectl apply -f https://raw.githubusercontent.com/kubernetes/heapster/v1.5.3/deploy/kube-config/influxdb/influxdb.yaml
kubectl apply -f https://raw.githubusercontent.com/kubernetes/heapster/v1.5.3/deploy/kube-config/rbac/heapster-rbac.yaml
kubectl apply -f https://raw.githubusercontent.com/kubernetes/heapster/v1.5.3/deploy/kube-config/influxdb/heapster.yaml

The cluster was deployed with kubeadm, the coredns configuration is
:53 {
    errors
    health
    kubernetes cluster.local in-addr.arpa ip6.arpa {
       pods insecure
       upstream
       fallthrough in-addr.arpa ip6.arpa
    }
    prometheus :9153
    proxy . /etc/resolv.conf
    cache 30
    reload
}

The network uses kube-router with cni config
{
  "name":"kubernetes",
  "type":"bridge",
  "bridge":"kube-bridge",
  "isDefaultGateway":true,
  "ipam": {
    "type":"host-local"
  }
}

Please let me know if I can provide any more information to diagnose
Output of heapster --version:
Not sure how to do this, the heapster container doesn't provide a shell that I know of. The image version pulled in the yaml file is v1.5.3
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:53:20Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:43:26Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Generally, when Heapster can't connect to your nodes, it's a problem with your networking set.  More specifically, certain networking vendors don't allow pods to connect to node IPs by default, and you have to manually allow it.  Unfortunately, there's not much advice I can provide here, since it's highly specific to your networking setup.

Sorry I'm not sure what you mean by networking vendor, I'm not doing anything non-standard here it's a bare metal install on a VM running on my laptop for evaluation purposes.

I should also point out that its a single-node cluster in theory packets shouldnt even be leaving the machine, I'm not sure how a network vendor would be relevant

So there were actually a couple of things going wrong but it is worth pointing out that heapster requires kubelet to have its readOnlyPort set to 10255. Kubeadm does not provide an easy way to do this with its config file, but you can instead update /etc/default/kubelet to set KUBELET_EXTRA_ARGS=--read-only-port 10255

So there were actually a couple of things going wrong but it is worth pointing out that heapster requires kubelet to have its readOnlyPort set to 10255

Alternatively, you can just tell Heapster not to use the read-only port.  There's flags on the source to do this -- see https://github.com/kubernetes/kubernetes/pull/65102.
Sorry for the initially terse response -- we end up getting a lot of issues that boil down to "My CNI plugin/overlay network blocks pod<->communication out of the box".

Yeah that looks perfect, it's too bad it requires a source change to work. Probably the default should be to use the secure port for everything right?

It's been the default in at least a couple of distros for a while now, but hasn't been in kubernetes for various reasons.  It'll be the default in metrics-server soon.


Replace reference to registry with local lookup

Description
Update a reference to this module in the tests to be a local lookup rather than a potentially old version from the terraform module registry.
Release required?

[x] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
This is an example update, not part of the main module, so no release is required.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.20.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Configuration.browserSize setting is ignored with custom WebDriver

When using customize WebDriver creation by:  "Extend WebDriver implementation, override public XxxDriver(Capabilities capabilities) constructor and pass this class name as browser system variable value" - Configuration.browserSize not overriding default ChromeDriver value and ignored.  Worked fine with Selenide 5
public class ChromeDriverProvider implements WebDriverProvider {
    @Nonnull
    @Override
    public WebDriver createDriver(@Nonnull Capabilities capabilities) {
        WebDriverManager.chromedriver().setup();
        ChromeOptions options = new ChromeOptions();
        options.addArguments("--no-sandbox", "--disable-gpu", "--ignore-certificate-errors", "--disable-extensions",
                "--disable-dev-shm-usage", "clickViaJs");
return new ChromeDriver(options);
    }

 @Test
    public void openGoogle() {
        Configuration.browser = ChromeDriverProvider.class.getName();
        Configuration.browserSize = "800x600";
        Configuration.headless = false;

        open("https://google.com/");
        System.out.println("Real size: " + WebDriverRunner.getWebDriver().manage().window().getSize());

    }

Output:
Real size: (1200, 921)
Environment:
Selenide version 6.11.0
Chrome version 109
MacOs 13.1

@Zaykona Works as expected :)
That's the point of custom webdriver provider: when you decide to implement it, you fully control the creation of the webdriver. You need to set all the properties by yourself.
Yes, before Selenide 6.10.0, setting Configuration.browserSize affected also webdrivers created by custom WebDriverProviders - but it was a bug. :)
The fix is very easy for you: just add --window-size=1800x1400 to your chrome options.

Yes, I have already added the fix. But it was interesting to understand the flow in general. Thank you for details. Got it;)


Problem about running gunicorn_thrift

I'v installed gunicorn_thrift， but can't find the command gunicorn_thrift？

This needs a lot more information before anyone can be helpful. How did you install it? What platform? Did you install it globally, or in a virtualenv? What version of Python?

@preytaren  this issue is more related to your python setup rather than gunicorn_thrift itself.
Please create a new virtualenv and install gunicorn_thrift in it to check if it's gunicorn_thrift's problem, meanwhile I'll close this issue.  Feel free to reopen it.

I met the same issue.
After cloning repo, i just run "python setup.py install" in a virtualenv. It's werid that log does not show gunicorn_thrift script was installed.
`
(.venv) ➜  gunicorn_thrift git:(master) ✗ python setup.py install
running install
running bdist_egg
running egg_info
creating gunicorn_thrift.egg-info
writing requirements to gunicorn_thrift.egg-info/requires.txt
writing gunicorn_thrift.egg-info/PKG-INFO
writing top-level names to gunicorn_thrift.egg-info/top_level.txt
writing dependency_links to gunicorn_thrift.egg-info/dependency_links.txt
writing entry points to gunicorn_thrift.egg-info/entry_points.txt
writing manifest file 'gunicorn_thrift.egg-info/SOURCES.txt'
reading manifest file 'gunicorn_thrift.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '..swp' found under directory '.'
warning: no previously-included files matching '..swo' found under directory '.'
warning: no previously-included files matching '' found under directory 'venv'
warning: no previously-included files matching '' found under directory 'dist'
warning: no previously-included files matching '*' found under directory 'build'
writing manifest file 'gunicorn_thrift.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.12-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
creating build/lib/gunicorn_thrift
copying gunicorn_thrift/init.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/config.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/gevent_worker.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/six.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/sync_worker.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/thriftapp.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/thriftpy_gevent_worker.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/thriftpy_sync_worker.py -> build/lib/gunicorn_thrift
copying gunicorn_thrift/utils.py -> build/lib/gunicorn_thrift
creating build/bdist.macosx-10.12-x86_64
creating build/bdist.macosx-10.12-x86_64/egg
creating build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/init.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/config.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/gevent_worker.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/six.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/sync_worker.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/thriftapp.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/thriftpy_gevent_worker.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/thriftpy_sync_worker.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
copying build/lib/gunicorn_thrift/utils.py -> build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/init.py to init.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/config.py to config.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/gevent_worker.py to gevent_worker.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/six.py to six.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/sync_worker.py to sync_worker.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/thriftapp.py to thriftapp.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/thriftpy_gevent_worker.py to thriftpy_gevent_worker.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/thriftpy_sync_worker.py to thriftpy_sync_worker.pyc
byte-compiling build/bdist.macosx-10.12-x86_64/egg/gunicorn_thrift/utils.py to utils.pyc
creating build/bdist.macosx-10.12-x86_64/egg/EGG-INFO
creating dist
creating 'dist/gunicorn_thrift-0.2.21-py2.7.egg' and adding 'build/bdist.macosx-10.12-x86_64/egg' to it
removing 'build/bdist.macosx-10.12-x86_64/egg' (and everything under it)
Processing gunicorn_thrift-0.2.21-py2.7.egg
creating /Users/zifeng.huang/Desktop/study/test/gunicorn_thrift/.venv/lib/python2.7/site-packages/gunicorn_thrift-0.2.21-py2.7.egg
Extracting gunicorn_thrift-0.2.21-py2.7.egg to /Users/zifeng.huang/Desktop/study/test/gunicorn_thrift/.venv/lib/python2.7/site-packages
Adding gunicorn-thrift 0.2.21 to easy-install.pth file
Installed /Users/zifeng.huang/Desktop/study/test/gunicorn_thrift/.venv/lib/python2.7/site-packages/gunicorn_thrift-0.2.21-py2.7.egg
Processing dependencies for gunicorn-thrift==0.2.21
Finished processing dependencies for gunicorn-thrift==0.2.21
`
My platform is Darwin appledeMacBook-Pro-2.local 16.3.0 Darwin Kernel Version 16.3.0: Thu Nov 17 20:23:58 PST 2016; root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64.
But if i use "python setup.py develop", the gunicorn_thrift script will be installed.


V0.4 update docs

@CS2103JUN2017-T2/developers
Let's use this branch to collate all our documentation updates in one place.
The format expected for AboutUs.adoc for V0.4 is different from what we have previously, reference my portion for the new format.
Also, if you're doing the implementation for a feature/command I think you should also take over the documentation for that feature/command, to ensure consistency.

Coverage remained the same at 81.706% when pulling e1f00769772f22e1d8556758028f754e9726c6ab on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage increased (+0.4%) to 82.07% when pulling 14f9db1b3f158734a2dd841e64cbb95f20097c8a on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-2.05%) to 79.656% when pulling 5f0d62d96019d00f37631871b785fd71927e36d7 on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-2.2%) to 79.526% when pulling 5f0d62d96019d00f37631871b785fd71927e36d7 on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-2.05%) to 79.656% when pulling b95be0ffa6ed2e8770e87987aecc2b6ee30dd09d on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-2.05%) to 79.656% when pulling c0feee86030b97c4f998a56516af41a45d9ef564 on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-1.5%) to 80.16% when pulling 633e431b248aca72e57668d68e69ee8d1d8129d6 on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-1.5%) to 80.16% when pulling 633e431b248aca72e57668d68e69ee8d1d8129d6 on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-1.5%) to 80.16% when pulling 633e431b248aca72e57668d68e69ee8d1d8129d6 on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-1.7%) to 80.0% when pulling 98ddb323ceecfd39a288ebeb60cac861a55a93bb on V0.4_update_docs into db56b96647b73835b184e20b8dcbe916a35c58ea on V0.4.

Coverage decreased (-0.1%) to 80.0% when pulling eb05c67b14e983318e85980277718e9d5023e975 on V0.4_update_docs into 308632baa2d11825a0aea1cce0e0e704e0785ef0 on V0.4.

Coverage remained the same at 80.12% when pulling c91dfdaf1405e22a036b3272f9e8c66253687111 on V0.4_update_docs into 308632baa2d11825a0aea1cce0e0e704e0785ef0 on V0.4.

Coverage remained the same at 80.12% when pulling c91dfdaf1405e22a036b3272f9e8c66253687111 on V0.4_update_docs into 308632baa2d11825a0aea1cce0e0e704e0785ef0 on V0.4.


Time functionality added

@Laxmankohar, one can see only own message timing but not others. Try to fix it. Also, swap the place of the message and its time.

ok

Is it ok?

@Laxmankohar, yeah now it's kinda perfect.... do create a PR...will merge it


Bump Dependencies #5771342267

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/5771342267

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update permissions so that an org admin can S&R and edit all projects in their org (add members etc)

[ ] Org admins can view project page for all projects owned by their org, whether confidential or not
[ ] Org admins can edit project details (add members, etc.) for all projects owned by their org, whether confidential or not

[ ] They are not required to be project managers (or even members) in order to do this: org admin status conveys this permission

[ ] Org admins can Send/Receive all projects owned by their org, whether confidential or not

[ ] They are not required to be project managers (or even members) in order to do this: org admin status conveys this permission

Just discovered something while working on this, which I'll record here for now but might move into its own issue later.
The orgs list in the JWT currently just lets .NET serialize it, resulting an orgs list that looks like this:
"orgs": [
  {
    "Role": 1,
    "OrgId": "a748bd8b-6348-4980-8dee-6de8b63e4a39"
  }
]

But if you write code like this in Svelte:
$: orgsManagedByUser = user.orgs.filter(o => o.role === OrgRole.Admin).map(o => o.orgId);

Then it's comparing the number 1 to the string "ADMIN" and coming up false.
We need to tweak the serialization of the JWT in .NET to use a string rather than an int for the role in the Orgs object.

Need a copy of FieldWorks to test the Send/Receive scenarios, as Language Forge will refuse to do a clone via S/R because "you're not a project manager". To change that would require either editing the Language Forge project-creation login in LF, or else editing the API that LF queries and telling it "if the user is an org manager, then list all the projects in the org as being "managed" by that user when LF asks".


Added example for getProfile

If merging into master, have to also merge into develop after, may be easier to just merge into develop

Oh, yes this should be merged into develop. My bad!


upgrade to kustomize 5

What this PR does / why we need it:
Updates Kustomize from v4.5.7 to v5.0.1 which resolves CVE-2022-27664, CVE-2022-41723, CVE-2022-41723, and CVE-2022-28948 with high severity and CVE-2022-41717 with medium severity
Which issue(s) this PR fixes:

Fixes SC-69470
Special notes for your reviewer:

Added a pod to the pkg/tests/pull/cases/subchart-crds test case chart at templates/my-chart-pod.yaml with the following contents:
apiVersion: v1
kind: Pod
metadata:
  name: my-chart-pod
spec:
  containers:
  - name: my-chart-container
    image: nginx
    ports:
    - containerPort: 80
  initContainers: null

Steps to reproduce

Run the updated unit test with and without the code changes.  Without, it will fail with the following:
Error: updating name reference in 'spec/initContainers/env/valueFrom/configMapKeyRef/name' field of 'Pod.v1.[noGrp]/my-chart-pod.[noNs]': considering field 'spec/initContainers/env/valueFrom/configMapKeyRef/name' of object Pod.v1.[noGrp]/my-chart-pod.[noNs]: expected sequence or mapping node\n

Does this PR introduce a user-facing change?

Updates Kustomize from v4.5.7 to v5.0.1 which resolves CVE-2022-27664, CVE-2022-41723, CVE-2022-41723, and CVE-2022-28948 with high severity and CVE-2022-41717 with medium severity.

Does this PR require documentation?

NONE

Copying PR feedback: We need to run this logic for non-helm charts when creating the rendered directory: https://github.com/replicatedhq/kots/blob/6e358766c5c424a757ff1361bb87191438c95ad8/pkg/kustomize/app.go#L34-L54

Is there a way to run and detect nil fields in a single pass before calling kotsutil.RemoveEmptyMappingFields ?

We can maybe try to do a text search first, but that also could fail to detect if spacing/indentations are different.  I cannot think about a great way to handle it without unmarshalling the yaml.


[BUG] dashboard object cannot be created when index doesn't exist

What is the bug?
A new dashboard object cannot be created if the assigned index doesn't exist. The terraform apply will fail saying plugin crash. However, if you check the indices in Opensearch, the given index actually got created from the failed deployment. If I rerun the Terraform plan and apply again, things would work as expected.
How can one reproduce the bug?

make sure Opensearch does not have a test index for a tenant, say .kibana_<hash>_<tenant_name>
use this provider to create an index pattern and assign this test index to that index pattern
the deployment will fail with the following stack trace
If we rerun terraform plan and apply again, we won't see the error, as the .kibana_<hash>_<tenant_name> index already got created from the first failed deployment.

│   61: resource "opensearch_dashboard_object" "index_patterns" {
│
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
Stack trace from the terraform-provider-opensearch_v1.0.0 plugin:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xef475a]
goroutine 147 [running]:
github.com/opensearch-project/terraform-provider-opensearch/provider.elastic7CreateIndexIfNotExists(0xc00052ee00, {0xc00076f980, 0x15}, {0xc00076f980, 0x15})
github.com/opensearch-project/terraform-provider-opensearch/provider/resource_opensearch_dashboard_object.go:141 +0x21a
github.com/opensearch-project/terraform-provider-opensearch/provider.resourceOpensearchDashboardObjectCreate(0xc0003fe600, {0xf84780?, 0xc000507400})
github.com/opensearch-project/terraform-provider-opensearch/provider/resource_opensearch_dashboard_object.go:100 +0x10f
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).create(0x14565e8?, {0x14565e8?, 0xc0005366c0?}, 0xd?, {0xf84780?, 0xc000507400?})
github.com/hashicorp/terraform-plugin-sdk/v2@v2.12.0/helper/schema/resource.go:330 +0x178
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc00018b340, {0x14565e8, 0xc0005366c0}, 0xc00062b790, 0xc0003fe480, {0xf84780, 0xc000507400})
github.com/hashicorp/terraform-plugin-sdk/v2@v2.12.0/helper/schema/resource.go:472 +0x83a
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc000438798, {0x1456540?, 0xc0004eb000?}, 0xc00040d2c0)
github.com/hashicorp/terraform-plugin-sdk/v2@v2.12.0/helper/schema/grpc_provider.go:1021 +0xdaa
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0xc0003f5c20, {0x14565e8?, 0xc000525ec0?}, 0xc0001f60e0)
github.com/hashicorp/terraform-plugin-go@v0.8.0/tfprotov5/tf5server/server.go:812 +0x515
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0x111a540?, 0xc0003f5c20}, {0x14565e8, 0xc000525ec0}, 0xc000467a40, 0x0)
github.com/hashicorp/terraform-plugin-go@v0.8.0/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:385 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc000170a80, {0x1459308, 0xc000445a00}, 0xc0008b70e0, 0xc00043b290, 0x1bdfee0, 0x0)
google.golang.org/grpc@v1.45.0/server.go:1282 +0xccf
google.golang.org/grpc.(*Server).handleStream(0xc000170a80, {0x1459308, 0xc000445a00}, 0xc0008b70e0, 0x0)
google.golang.org/grpc@v1.45.0/server.go:1619 +0xa1b
google.golang.org/grpc.(*Server).serveStreams.func1.2()
google.golang.org/grpc@v1.45.0/server.go:921 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
google.golang.org/grpc@v1.45.0/server.go:919 +0x28a
Error: The terraform-provider-opensearch_v1.0.0 plugin crashed!
This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.
What is the expected behavior?
It seems like the provider is trying to support creating an index pattern with a nonexistent index but it crashes after the index got created. If that is the case, the expected behavior should be the index patterns will be created successfully with a new index.
What is your host/environment?
Operating system, version.
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

@opensearch-project/opensearch-dashboards-core Could you please advise if this is a known issue from dashboards side?

Yes, a index pattern cannot be created before an index with that pattern exists. Why are we trying to create an index pattern before the index itself?

Maybe the title of this bug is not clear. The point here is when we try to create an index pattern before the index, the index gets created but the index pattern creation fails. It seems like this use case, creating index pattern for a nonexistent index, is supposed to work but fails actually, otherwise the index won't be created at all, since I didn't explicitly create it.


Write a more approachable release-tagging script

The current version of the script has a few issues:

Because it uses command-line flags to bump version numbers, it's
possible to bump multiple parts of the version number at once.
The version-number logic was, at one point, capable of generating and
pushing invalid tags (for instance, v0.5.1-rc0.5.0). This has
probably been fixed, but it's hard to be sure because...
Bash being bash, it's not always easy to tell what the code is doing.
Given the script has the potential to kick off and publish a new
release of our product, it's worth building up our collective
confidence in what the code is doing.

I've taken a first stab at a version that addresses these issues, trying
to build up a release tagging script as I might like to see it. I've
documented everything I can think of documenting, and used a combination
of named and positional arguments to mean it's only possible to call for
one type of release (as it's a single named argument).
I decided to test the Weaveworks waters with a spot of Python, partly to
see what a Python-based deploy script could look like, and partly
because I got fed up bashing my head against bash. I've made sure to
keep to the dependencies in Python's standard library, because Python's
package management is a whole other nest of complexity I don't want to
get into.
At least partially related to #1478.

This might absolutely be me not understanding how the old script worked, but… If the current version is 0.6.1, and I want to start the release process for 0.7.0, then I want to "bump, and make that an RC", yet I think the way you modelled the "state machine of release transitions" means I can only go from 0.6.1 to 0.7.0 directly, or to 0.6.2-rc1? My intuition about release numbers suggest that "rc" on top of stable shouldn't exist, instead "minor" and "patch" should both return rc1.
I also suspect throwing when you run minor on a rc isn't the best behaviour either - I've found myself going "hang on, I already have 0.6.2-rc1 but it turns out we've done non-patch changes, let's re-version this 0.7.0-rc1" more than once when working on other projects in the past.
I do think that not using bash is an excellent proposal, and python should be universal enough to not cause a problem.

Ok, here’s what I’m thinking for a potential flow (and the flags to go with it).
Some principles I’ve tried to follow here:

Fail safe. As this is kicking off a potential release, the script should abort with an error rather than do anything unexpected.
RCs by default. Release candidates are good, we want to use them pretty much all the time, but let’s provide a get-out for situations we might not have thought about.

I’ve drawn up a map of input versions to output versions, as much for my own clarity as anything.

Command
v1.1.1
v1.1.1-rc1

tag-release minor
v1.2.0-rc1
❌

tag-release patch
v1.1.2-rc1
❌

tag-release minor --no-rc
v1.2.0
❌

tag-release patch --no-rc
v1.1.2
❌

tag-release minor --abandon
❌
v1.2.0-rc1

tag-release patch --abandon
❌
v1.1.2-rc1

tag-release minor --abandon --no-rc
❌
v1.2.0

tag-release patch --abandon --no-rc
❌
v1.1.2

tag-release bump
❌
v1.1.1-rc2

tag-release promote
❌
v1.1.1

How does that look to people? Does that make sense from your perspective as potential users?
Side-note: at this point, it’s possible that it makes more sense to build a new branch-based release process rather than spend more time replacing this script, although either way we go about it we’re probably going to:

Need at least some of the same logic in place
End up with one less Bash script

I'm not 100% sure what the --abandon flag is doing here?
Other than that though I think the flows look reasonable.

So I went outside. We should ignore all the things I wrote before, and do exactly what you propose for a branch based release process.
I believe that as more conservative organisations starts to rely on gitops core we'll want longer-lived stable branches, and as more developers start to work on it we'll want an easier-to-separate release process. But my workings out above has convinced me that we can add that when we get there, from what you've proposed for a branch based release process.

Thumbs-up for a branch-based release process :+1:   One of the pain points of the current approach is that it's difficult to test changes to the release process. You either have to "test it live" with the real environment or dummy up a separate fork or standalone repo that can stand in for the real one. Neither option is great.
Also, I have high hopes that we can now make the process much simpler and less error-prone because much of the complexity in the original process derived from managing the documents as a separate repo. :crossed_fingers:


Bump BLST to 0.3.12 and remove patch

We will need to ideally update clvmr to use the new chia-bls version, then bump clvmr in chia_rs.
But I think in the lockfile, it's already replaced it since it's a semver compatible version.

Rebased against main


Naming conflict between models and GraphQL types

When working on GraphQL types, we often end up in a situation where we have naming conflicts between the GraphQL types and the models. An example to illustrate:
server/graphql/v2/mutation/TierMutations.ts
import Tier from '../../../models/Tier';
import Tier from '../object/Tier'; // Error: Tier is already defined

const tierMutations {
  createTier: {
    type: new GraphQLNonNull(Tier),
    resolve: (args) => Tier.create(args);
  }
}

The way we usually work around this issue is by aliasing one of the two variables:
// Aliasing the model
import { Tier as TierModel } from '../../../models/Tier';
import Tier from '../object/Tier';

// Or the GraphQL import
import Tier from '../../../models/Tier';
import { Tier as GraphQLTier } from '../object/Tier';

This practice, however:

Is another thing that you need to think about when working on GraphQL operations
Is not consistent across files
Because of the above, is potentially error-prone

Proposed solution
Standardize all our exported GraphQL objects with the GraphQL prefix:

GraphQLTier
GraphQLExpense
GraphQLPaymentMethod
...etc

I tend to prefer this approach because it is consistent with all the other GraphQL types that are imported in these files: GraphQLString, GraphQLBoolean, GraphQLInt, etc.
To make it clear: I'm only proposing the rename the exported variable, not the type in GraphQL itself:
- export const Tier = new GraphQLObjectType({
+ export const GraphQLTier = new GraphQLObjectType({
  name: 'Tier',
  description: 'Tier model',

A bit verbose but make sense.


Bluetooth LESC debug keys support (BT_USE_DEBUG_KEYS) is broken

Configuring CONFIG_BT_USE_DEBUG_KEYS=y will lead to failure during pairing.

d_00: @00:00:00.000000  ***** Booting Zephyr OS v1.9.0-7108-g19845a7 *****
d_01: @00:00:00.000000  ***** Booting Zephyr OS v1.9.0-7108-g19845a7 *****
d_01: @00:00:00.000000  [bt] [INF] hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
d_01: @00:00:00.000000  [bt] [INF] hci_vs_init: HW Variant: nRF52x (0x0002)
d_01: @00:00:00.000000  [bt] [INF] hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.13 Build 0
d_01: @00:00:00.000000  [bt] [WRN] bt_setup_id_addr: No static addresses stored in controller
d_00: @00:00:00.000000  [bt] [INF] hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
d_00: @00:00:00.000000  [bt] [INF] hci_vs_init: HW Variant: nRF52x (0x0002)
d_00: @00:00:00.000000  [bt] [INF] hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.13 Build 0
d_00: @00:00:00.000000  [bt] [WRN] bt_setup_id_addr: No static addresses stored in controller
d_01: @00:00:00.002528  [bt] [INF] bt_dev_show_info: Identity: f7:38:e5:75:02:d8 (random)
d_01: @00:00:00.002528  [bt] [INF] bt_dev_show_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0x05f1
d_01: @00:00:00.002528  [bt] [INF] bt_dev_show_info: LMP: version 5.0 (0x09) subver 0xffff
d_01: @00:00:00.002528  [bt] [DBG] bt_smp_init: (0x080af060) LE SC enabled
d_01: @00:00:00.002528  [bt] [DBG] bt_smp_pkey_ready: (0x080aff40)
d_00: @00:00:00.002528  [bt] [INF] bt_dev_show_info: Identity: fa:dd:f6:49:f2:51 (random)
d_00: @00:00:00.002528  [bt] [INF] bt_dev_show_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0x05f1
d_00: @00:00:00.002528  [bt] [INF] bt_dev_show_info: LMP: version 5.0 (0x09) subver 0xffff
d_00: @00:00:00.002528  [bt] [DBG] bt_smp_init: (0x080af3b0) LE SC enabled
d_00: @00:00:00.002528  [bt] [DBG] bt_smp_pkey_ready: (0x080a7720)
d_01: @00:00:00.004448  [bt] [WRN] irk_init: Using temporary IRK
d_01: @00:00:00.004448  Bluetooth initialized
d_00: @00:00:00.004448  [bt] [WRN] irk_init: Using temporary IRK
d_00: @00:00:00.004448  Bluetooth initialized
d_01: @00:00:00.005048  Scanning successfully started
d_00: @00:00:00.005048  Advertising successfully started
d_01: @00:00:00.007010  [bt] [DBG] bt_keys_find_irk: (0x080b7b80) 78:18:63:8a:e4:cc (random)
d_01: @00:00:00.007010  [bt] [DBG] bt_keys_find_irk: (0x080b7b80) No IRK for 78:18:63:8a:e4:cc (random)
d_01: @00:00:00.007010  [DEVICE]: 78:18:63:8a:e4:cc (random), AD evt type 0, AD data len 29, RSSI -35
d_01: @00:00:00.007010  [AD]: 1 data_len 1
d_01: @00:00:00.007010  [AD]: 3 data_len 6
d_01: @00:00:00.116389  [bt] [DBG] bt_smp_accept: (0x080b7b80) conn 0x080b00c0 handle 0
d_01: @00:00:00.116389  [bt] [DBG] bt_smp_connected: (0x080b7b80) chan 0x080b03e0 cid 0x0006
d_01: @00:00:00.116389  Connected: 78:18:63:8a:e4:cc (random)
d_00: @00:00:00.116891  [bt] [DBG] bt_smp_accept: (0x080af240) conn 0x080a78a0 handle 0
d_00: @00:00:00.116891  [bt] [DBG] bt_smp_connected: (0x080af240) chan 0x080a7b80 cid 0x0006
d_00: @00:00:00.116891  Connected
d_01: @00:00:00.618713  [bt] [DBG] bt_keys_find: (0x080b7b80) type 32 78:18:63:8a:e4:cc (random)
d_01: @00:00:00.618713  [bt] [DBG] bt_keys_find: (0x080b7b80) type 4 78:18:63:8a:e4:cc (random)
d_01: @00:00:00.618713  [bt] [DBG] bt_smp_send_pairing_req: (0x080b7b80)
d_01: @00:00:00.620281  [bt] [DBG] smp_init: (0x080b7b80) prnd 68c662a92d46b300fc6122061aaeb841
d_00: @00:00:00.668932  [bt] [DBG] bt_smp_recv: (0x080af240) Received SMP code 0x01 len 7
d_00: @00:00:00.668932  [bt] [DBG] smp_pairing_req: (0x080af240)
d_00: @00:00:00.670500  [bt] [DBG] smp_init: (0x080af240) prnd 8bfc7e952bc1ddee0e489e57afb492ce
d_01: @00:00:00.718630  [bt] [DBG] bt_smp_recv: (0x080b7b80) Received SMP code 0x02 len 7
d_01: @00:00:00.718630  [bt] [DBG] smp_pairing_rsp: (0x080b7b80)
d_01: @00:00:00.719910  [ATTRIBUTE] handle 10
d_00: @00:00:00.768360  [bt] [DBG] bt_smp_recv: (0x080af240) Received SMP code 0x0c len 65
d_00: @00:00:00.768360  [bt] [DBG] smp_public_key: (0x080af240)
d_00: @00:00:00.768360  [bt] [DBG] smp_f4: (0x080af240) u 20b003d2f297be2c5e2c83a7e9f9a5b9eff49111acf4fddbcc0301480e359de6
d_00: @00:00:00.768360  [bt] [DBG] smp_f4: (0x080af240) v 20b003d2f297be2c5e2c83a7e9f9a5b9eff49111acf4fddbcc0301480e359de6
d_00: @00:00:00.768360  [bt] [DBG] smp_f4: (0x080af240) x 8bfc7e952bc1ddee0e489e57afb492ce z 0x0
d_00: @00:00:00.768360  [bt] [DBG] smp_f4: (0x080af240) res<PHONE_NUMBER>9abac6ac131a8700d165ca
d_00: @00:00:00.768360  [bt] [ERR] emulate_le_generate_dhkey: public key is not valid (ret -3)
d_00: @00:00:00.768360  [bt] [DBG] bt_smp_dhkey_ready: (0x080a7720) 0x00000000
d_00: @00:00:00.768360  [bt] [DBG] smp_pairing_complete: (0x080a7720) status 0xb
d_01: @00:00:00.868590  [bt] [DBG] bt_smp_recv: (0x080b7b80) Received SMP code 0x0c len 65
d_01: @00:00:00.868590  [bt] [DBG] smp_public_key: (0x080b7b80)
d_01: @00:00:00.868590  [bt] [ERR] emulate_le_generate_dhkey: public key is not valid (ret -3)
d_01: @00:00:00.868590  [bt] [DBG] bt_smp_dhkey_ready: (0x080aff40) 0x00000000
d_01: @00:00:00.868590  [bt] [DBG] smp_pairing_complete: (0x080aff40) status 0xb
d_00: @00:00:00.918288  [bt] [DBG] bt_smp_recv: (0x080af240) Received SMP code 0x05 len 2
d_00: @00:00:00.918288  [bt] [WRN] bt_smp_recv: Unexpected SMP code 0x05
d_01: @00:00:00.918686  [bt] [DBG] bt_smp_recv: (0x080b7b80) Received SMP code 0x03 len 17
d_01: @00:00:00.918686  [bt] [WRN] bt_smp_recv: Unexpected SMP code 0x03
d_01: @00:00:00.918686  [bt] [DBG] smp_pairing_complete: (0x080b7b80) status 0x8
d_00: @00:00:00.968288  [bt] [DBG] bt_smp_recv: (0x080af240) Received SMP code 0x05 len 2
d_00: @00:00:00.968288  [bt] [WRN] bt_smp_recv: Unexpected SMP code 0x05
d_01: @00:00:00.968566  [bt] [DBG] bt_smp_recv: (0x080b7b80) Received SMP code 0x05 len 2
d_01: @00:00:00.968566  [bt] [WRN] bt_smp_recv: Unexpected SMP code 0x05

How to reproduce:
Modify the central_hr as follows:
@@ static void connected(struct bt_conn *conn, u8_t conn_err)
        printk("Connected: %s\n", addr);

        if (conn == default_conn) {
+               k_sleep(500);
+               bt_conn_auth_cb_register(NULL);
+               err = bt_conn_security(conn, BT_SECURITY_MEDIUM);
+               if (err) {
+                       printk("bt_conn_security failed (err %d)\n", err);
+                       return;
+               }
                memcpy(&uuid, BT_UUID_HRS, sizeof(uuid));
                discover_params.uuid = &uuid.uuid;

Set in the central_hr and peripheral_hr project files CONFIG_BT_USE_DEBUG_KEYS=y
Run in one device this central_hr app, against another with this peripheral_hr app.

From a quick look it seems likely that the hci_ecc.c values are in the correct byte order (little endian instead of big endian). E.g. smp.c has the same public key value, but that's compared against little endian data, whereas the hci_ecc.c values are passed to the crypto API which expects big endian.


Respect embed image aspect ratio

Is there some CSS trick available that could make these prettier by respecting their aspect ratio instead of defaulting to being square?

.wc:has(.e > .em > a.c[href*="github"]) {
    .em {
        height: 160px;
    }
    width: 320px;
    height: 160px;
}

There's no way you can get the embeds to auto-respect aspect ratio using just CSS (the plugin nests divs strangely). So I made this CSS snippet that'll just work on GitHub embeds.

CC: @s1avash26 (you thumbs-up reacted the issue)

Thanks for your snippet.
I'm not good at CSS. I was planning to rewrite the whole CSS part with GPT. But GPT can not handle this. So I gave up.
Maybe you can create a pull request for this

Thanks, but if I were to PR this repo I'd want to actually solve the issue for all thumbnails, not just GitHub ones.
Sometime in the future when I have free time, I can look into fixing this entirely.