Slack Notification Error

[x] Which version of Forseti Security you're using: 2.19.1
[x] Which module(s) (inventory, scanner, enforcer, explain) you're having trouble with: Notifier
[x] Include errors, log output, and host operating system, including installed packages.
[x] Note how you deployed (via Deployment Manager, Terraform, local system, etc.): Terraform

Several customers have reported an issue with the Slack notifier. Violations are being discovered and notifications are sent via email, but Slack has an error. This violation then does not make it's way into GCS. When Slack is disabled, no errors are encountered.
Error message
  "serverMessage": "Error occurred during the notification process: 'Traceback (most recent call last):\n  File \"/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.1-py3.6.egg/google/cloud/forseti/services/notifier/service.py\", line 129, in _run_notifier\n    self.service_config)\n  File \"/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.1-py3.6.egg/google/cloud/forseti/notifier/notifier.py\", line 173, in run\n    notifier.run()\n  File \"/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.1-py3.6.egg/google/cloud/forseti/notifier/notifiers/slack_webhook.py\", line 84, in run\n    webhook_payload = self._compose(violation=violation)\n  File \"/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.1-py3.6.egg/google/cloud/forseti/notifier/notifiers/slack_webhook.py\", line 64, in _compose\n    self._dump_slack_output(violation.get('violation_data'), 1))\n  File \"/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.1-py3.6.egg/google/cloud/forseti/notifier/notifiers/slack_webhook.py\", line 41, in _dump_slack_output\n    for key, value in sorted(data.items()):\nAttributeError: 'str' object has no attribute 'items'\n'"
Sample rules:
`
rules:

name: All buckets in project must be in the US.
mode: whitelist
resource:

type: project
resource_ids:

applies_to:

type: 'bucket'
resource_ids:

'*'
locations:

'us*'

name: All buckets in project must not be in EU.
mode: blacklist
resource:

type: project
resource_ids:

applies_to:

type: 'bucket'
resource_ids:

'*'
locations:

'eu*'
`

This has been released as part of Forseti Release v2.22.0.


Sqlite error when running inside ubuntu docker container

Hi, I've tried running twscrape in dockerized FastAPI project, but getting this exception
when trying to get user by login:
  File "/usr/local/lib/python3.11/site-packages/huntersdao/twitter_scraper/core.py", line 112, in get_user_by_login     user = await self.api.user_by_login(user_login)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/twscrape/api.py", line 118, in user_by_login     rep = await self.user_by_login_raw(login, kv=kv)           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/twscrape/api.py", line 115, in user_by_login_raw     return await self._gql_item(op, kv)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/twscrape/api.py", line 62, in _gql_item     async with QueueClient(self.pool, queue, self.debug) as client:   File "/usr/local/lib/python3.11/site-packages/twscrape/queue_client.py", line 37, in __aenter__     await self._get_ctx()   File "/usr/local/lib/python3.11/site-packages/twscrape/queue_client.py", line 56, in _get_ctx     acc = await self.pool.get_for_queue_or_wait(self.queue)           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/twscrape/accounts_pool.py", line 162, in get_for_queue_or_wait     account = await self.get_for_queue(queue)               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/twscrape/accounts_pool.py", line 157, in get_for_queue     rs = await fetchone(self._db_file, q2)          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/twscrape/db.py", line 20, in wrapper     raise e   File "/usr/local/lib/python3.11/site-packages/twscrape/db.py", line 17, in wrapper     return await func(*args, **kwargs)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/twscrape/db.py", line 126, in fetchone     async with db.execute(qs, params) as cur:   File "/usr/local/lib/python3.11/site-packages/aiosqlite/context.py", line 41, in __aenter__     self._obj = await self._coro                 ^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 184, in execute     cursor = await self._execute(self._conn.execute, sql, parameters)              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 129, in _execute     return await future            ^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/aiosqlite/core.py", line 102, in run     result = function()              ^^^^^^^^^^ sqlite3.OperationalError: near "RETURNING": syntax error
Any ideas? I am using latest 0.2.1 version from PyPI.

Hi, @0xGhostCasper.
Probably something wrong sqlite version. Can you check versions with:
docker exec -d CONTAINER_NAME twscrape versrion

I build my containers like this:
FROM python:3.11-alpine
RUN apk update && apk upgrade
RUN apk add --no-cache build-base libffi-dev git sqlite

In any case, I will try to make some hack to be able to work on older versions of SQLite

Hi again, @0xGhostCasper.
SQLite 3.34 support fixed in 0.2.2. Try with new version please: pip install twscrape --upgrade

@vladkens works now, thanks, may I also ask if accounts are automatically
rotated when one of them hits RateLimit for specific queue? Because as I can see it keeps
waiting when hits RateLimit and not rotate to check whether other acc in pool has relaxed limits.


garage: 0.7.0 -> 0.7.2

Description of changes
https://git.deuxfleurs.fr/Deuxfleurs/garage/compare/v0.7.0...v0.7.2
Added checkFeatures and checkInputs, required to pass integration tests.
Upstream's shell.nix helped me figure out why tests suddenly started failing while doing a minor version bump. For future reference, failures looked like this:
---- k2v::item::test_item_return_format stdout ----
thread 'k2v::item::test_item_return_format' panicked at 'called `Result::unwrap()` on an `Err` value: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, me>
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I also tried to address this in a comment.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

kubernetes-discovery should be added to buildFeatures.

Thank you for your review, I addressed your suggestions in 047b6dd. I had to add k2v to checkFeatures to make the integration tests pass.

There's a new tag that should address the missing version bump on their side. I'm testing it

Result of nixpkgs-review pr 185770 run on x86_64-darwin 1

1 package built:

garage

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1088

Result of nixpkgs-review pr 185770 run on x86_64-linux 1

1 package built:

garage


script doesn't find anything under 30€

hi,
the script doesn't find anything under 30€
im looking for something cheap.
my command is:
hah.py --price 30 --disk-size 2000 --ram 16 --cpu-score 2000
i get results but only up from 30€, but on the site are a few listed for 24/25 €

Ah, I see what may be the issue - it's tax rate which I assumed is 19% for Germany.
It's selectable in top left corner. Can you verify that you see the same results if you choose Germany? If so I'll add tax rate as command line parameter.

its the tax.
price for US is set to 0% on the website,
when entering my country, its all working good.
thx for the fast reply


Training unconditional model for image and video generation

Hi Author,
Thanks for your excellent work. If I would like to train an unconditional image and video generation model, how should I modify the code? Thanks

can you further explain that what do you mean exactly of unconditional generation

No text input, thanks

hi @oahzxl , thanks for your reply.
Unconditional model means the there is no text input for the model.
Based on the original DiT, which supports both unconditional and conditional training.
Thx

hi @oahzxl , thanks for your reply.
Unconditional model means the there is no text input for the model.
Based on the original DiT, which supports both unconditional and conditional training.
Thx

do you mean label input as origin DiT

Hi @oahzxl , thanks for your reply.
Yes it is about label input of original DiT. But I think this repo is about txt-based video/image generation, it should be no text input, no label input, just input image/video for image/video generation.
The following link includes the reply of the author of original DiT about unconditional training, thanks
https://github.com/facebookresearch/DiT/issues/18#issuecomment-1427265881

we use label generation by default in our example scripts

Thanks


Add a JSON schema for strategies.yaml

Adds a JSON schema file for next hop strategies for use in validating strategies.yaml

The schema is invalid. Here's a modified version that is syntactically valid (just the initial part)
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://github.com/apache/trafficserver/tree/master/configs/strategies.schema.json",
  "title": "Trafficserver next hop strategies Configuration",
  "description": "NextHop Strategies configuration file structure.  Licensed under Apache V2 https://www.apache.org/licenses/LICENSE-2.0",
  "type": "object",
  "properties": {
    "version": {
      "type": "string",
      "description": "Configuration format version."
    },
    "strategies": {
      "description": "Root tag for next hop strategies configuration",
      "type": "array",
      "items": {
        "$ref": "#/$defs/strategydef"
      }
    }
  },
  "required": [ "strategies" ],

All of the properties must be keys of the "properties" tag.
The path is "#/blah/blah" not "#blah/blah".

There are a number of JSON schema validators online, use them to validate both the syntax of the schema and whether it matches example strategy files.

Cherry-picked to v9.1.x branch.


Painter Partition problem

💥 Proposal
You have to paint N boards of length {A0, A1, A2, A3 … AN-1}. There are K painters available and you are also given how much time a painter takes to paint 1 unit of board. You have to get this job done as soon as possible under the constraints that any painter will only paint contiguous sections of board. Return the ans % 10000003
Input Format
First line contains three space seperated integers N,K and T ,where
N = Size of array,
K = No of painters available ,
T = Time taken to print each board by one painter
Next line contains N space seperated positive integers denoting size of N boards.
Constraints
1<=N<=100000
1<=K<=100000
1<=T<=1000000
1<=Li<=100000
Output Format
Return minimum time required to paint all boards % 10000003.
Sample Input
2 2 5
1 10
Sample Output
50
Explanation
The first painter can paint the first board in 5 units of time and the second painter will take 50 units of time to paint the second board. Since both can paint simultaneously , the total time required to paint both the boards is 50.
**It is a really hard and good problem was asked in google
It really helps in understanding binary search **
Have you read the Contributing Guidelines on Pull Requests?
yes

i would like to work on this issue in cpp as part of hakin codes
kindly add ch20 tag and assign this issue to me

I would like to take up this issue in python

I would like to take this in Java  for CH20

I would like to do this in C

We are logging the scores for the Contributor's Hack 2020. If you have one or more than one PR merged during the program, make sure to fill this form

I would like to contribute in this issue in C++

I would like to contribute in this issue in C++


converged_if_changed triggered on empty property

working_dir says it is being set to an empty string, though it is not defined as a property, causing converge_if_changed to run and updating the container. interesting bit is docker inspect shows the working_dir was not actually set to an empty string. expected result is docker run to immediately return with no action needed after the redeploy.
docker_image 'uchiwa/uchiwa' do
  notifies :redeploy, 'docker_container[uchiwa]', :immediately
end

docker_container 'uchiwa' do
  repo 'uchiwa/uchiwa'
  tag 'latest'
  port '3000:3000'
end

  * docker_image[uchiwa/uchiwa] action pull
    - Pull image uchiwa/uchiwa:latest
  * docker_container[uchiwa] action redeploy
    - create uchiwa
    -   set container_name              to "uchiwa" (default value)
    -   set repo                        to "uchiwa/uchiwa"
    -   set tag                         to "latest"
    -   set command                     to nil (default value)
    -   set cap_add                     to nil (default value)
    -   set cap_drop                    to nil (default value)
    -   set cgroup_parent               to "" (default value)
    -   set cpu_shares                  to 0 (default value)
    -   set cpuset_cpus                 to "" (default value)
    -   set devices                     to [] (default value)
    -   set dns                         to [] (default value)
    -   set dns_search                  to [] (default value)
    -   set domain_name                 to "" (default value)
    -   set entrypoint                  to nil (default value)
    -   set env                         to [] (default value)
    -   set extra_hosts                 to nil (default value)
    -   set exposed_ports               to {"3000/tcp"=>{}}
    -   set hostname                    to nil (default value)
    -   set ipc_mode                    to "" (default value)
    -   set labels                      to {} (default value)
    -   set links                       to nil (default value)
    -   set ip_address                  to nil (default value)
    -   set mac_address                 to nil (default value)
    -   set memory                      to 0 (default value)
    -   set memory_swap                 to 0 (default value)
    -   set network_disabled            to false (default value)
    -   set network_mode                to "bridge"
    -   set outfile                     to nil (default value)
    -   set port_bindings               to {"3000/tcp"=>[{"HostIp"=>"<IP_ADDRESS>", "HostPort"=>"3000"}]}
    -   set pid_mode                    to "" (default value)
    -   set privileged                  to false (default value)
    -   set publish_all_ports           to false (default value)
    -   set remove_volumes              to false (default value)
    -   set restart_maximum_retry_count to 0 (default value)
    -   set restart_policy              to nil (default value)
    -   set ro_rootfs                   to false (default value)
    -   set security_opts               to nil (default value)
    -   set signal                      to "SIGTERM" (default value)
    -   set sysctls                     to {} (default value)
    -   set tty                         to false (default value)
    -   set ulimits                     to nil (default value)
    -   set user                        to "" (default value)
    -   set userns_mode                 to "" (default value)
    -   set uts_mode                    to "" (default value)
    -   set volumes                     to {} (default value)
    -   set volumes_from                to nil (default value)
    -   set volume_driver               to nil (default value)
    -   set working_dir                 to "" (default value)
    -   set volumes_binds               to nil (default value)
    - starting uchiwa
  * docker_container[uchiwa] action run
    - deleting uchiwa
    - update uchiwa
    -   set working_dir to "" (was "/go/src/github.com/sensu/uchiwa")
    - starting uchiwa

Can confirm this for the case that an ip_address is set.
In the recipe docker_container.rb there is already a workaround mentioned in line 151:
# these are a special case for us because our names differ from theirs
We fixed it by adding the following lines after 155:
        container.info['NetworkSettings'] &&
        container.info['NetworkSettings']['Networks'] &&
        container.info['NetworkSettings']['Networks'][network_mode] &&
        container.info['NetworkSettings']['Networks'][network_mode]['IPAMConfig']  &&
        container.info['NetworkSettings']['Networks'][network_mode]['IPAMConfig']['IPv4Address']

I confirm the ip_address bug which is very annoying.

ip_address bug should be resolved in v2.16.2

This also affects memory_swap and user when using chef-client v16. Interestingly it worked with chef 14 for unknown reasons (no re-creation of containers on each converge).


Issue with valibotResolver causing unexpected form submission behavior

I am using react-hook-form with valibotResolver to validate my form data. I have noticed an issue where only the lastName field is included in the form data when the form is submitted, even though I have firstName and age fields in my form.
Link to CodeSandbox Project: https://codesandbox.io/p/devbox/fkzp9q?file=%2Fmyapp%2Fvite-project%2Fsrc%2FApp.tsx%3A1%2C1-79%2C1
this is my code  import React from "react";
import { useForm, Controller } from "react-hook-form";
import { valibotResolver } from "@hookform/resolvers/valibot";
import {
coerce,
maxLength,
maxValue,
minLength,
minValue,
number,
object,
Output,
safeInteger,
string,
} from "valibot";
//   import { formSchema } from './schema';
export const formSchema = object({
lastName: string([
minLength(1, "This field is required."),
maxLength(5, "Please enter within 2 characters."),
]),
});
const App = () => {
const { handleSubmit, control, formState } = useForm({
mode: "onChange",
defaultValues: {
lastName: "fds",
firstName: "sdf",
age: "2",
},
resolver: valibotResolver(formSchema),
});
const handleOnSubmit = handleSubmit((formType) => {
alert(JSON.stringify(formType));
});
console.log("errors", formState.errors);
return (

Last Name
<Controller
name="lastName"
control={control}
render={({ field }) => <input {...field} />}
/>
{formState.errors?.lastName?.message?.toString() || ""}
    First Name
    <Controller
      name="firstName"
      control={control}
      render={({ field }) => <input {...field} />}
    />
    {formState.errors?.firstName?.message?.toString() || ""}

    Age
    <Controller
      name="age"
      control={control}
      render={({ field }) => <input type="text" {...field} />}
    />
    {formState.errors?.age?.message?.toString() || ""}

    <button
      type="submit"
      disabled={!formState.isDirty || !formState.isValid}
    >
      execute
    </button>
  </form>

);
};
export default App;
And here's the output I get when I submit the form:
{
"lastName": "fds"
}

Hi @JolianGof,
Your form should be
ruby <form onSubmit={handleSubmit(handleOnSubmit)}>
And your handleOnSubmit should be
const handleOnSubmit = (formType) => {
    alert(JSON.stringify(formType));
  };

Hi @JolianGof,
You are missing firstName and age in your schema, add these to your schema and try again
export const formSchema = object({
  lastName: string([
    minLength(1, "This field is required."),
    maxLength(5, "Please enter within 2 characters."),
  ]),
firstName: string(),
age: string()
});

Hi,
Thank you for the response. I understand that the valibotResolver requires all fields in the form to be defined in the validation schema. However, in my case, I have a large form and I only want to validate some of the fields.
For instance, if I have a form with fields firstName, lastName, age, and many others, and I only want to validate firstName and age, how would I go about doing that?
Should I include all fields in the schema and provide simple validation rules like string() or number() for the fields I don't want to validate? Or is there a better way to handle this scenario?
Thank you for your guidance.

@JolianGof,
I understand what you want, so you can try to use yupResolver
Check this one: https://codesandbox.io/p/sandbox/react-hook-form-yup-resolver-forked-4k44jg?file=%2Fsrc%2FcolorScheme.js%3A11%2C4


Titlebar Conflicts Tracker

🔝 Titlebar Conflicts Tracker
The point of this issue is to discuss and track progress on resolving conflicts with General Updates 11 / Adding link parsing
Info & Documentation
Files

Seemingly, the Files app uses the Click event.
This code also seems to be vaguely mentioned in Files' MainPage.xaml and MainPage.xaml.cs
Docs

TextBox
ClickMode

Personally, ClickMode seems like a good option
Completion

[ ] Decide what event or method of obtaining focus status should be used
[ ] Develop

@onein528 @BobbyESP I'll see if I can start deving on GU11


Unable to install helm - Azure

Output of helm version:
$ helm version
version.BuildInfo{Version:"v3.4.0", GitCommit:"7090a89efc8a18f3d8178bf47d2462450349a004", GitTreeState:"clean", GoVersion:"go1.14.10"}
Output of kubectl version:
$sudo kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Trying to connect kubernetes cluster to Azure-Arc
LOGS:
$sudo az connectedk8s connect --name 'MyK8SCluster' --resource-group 'MyArc-k8s-Clusters' --location 'eastus'
Command group 'connectedk8s' is in preview. It may be changed/removed in a future release.
Ensure that you have the latest helm version installed before proceeding.
This operation might take a while...
Please check if the azure-arc namespace was deployed and run 'kubectl get pods -n azure-arc' to check if all the pods are in running state. A possible cause for pods stuck in pending state could be insufficient resources on the kubernetes cluster to onboard to arc.
Unable to install helm release: W1110 10:30:02.197250   21584 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
Azure part maybe irrelevant as issue is seen on Edge device (on k8s custer master node)

The error suggests that the chart you are attempting to install a chart that utilizes a deprecated API. However, Helm only reports it as a warning message. It is not treated as an error condition.
Based on the error message it would seem that this is caused by the CI pipeline you are utilizing to install the Helm chart. We've had issues in the past where Azure Pipelines would fail if helm reported any warning messages (see https://github.com/microsoft/azure-pipelines-tasks/issues/13594).
Can you please check with the azure Arc team and see if this is a result of an issue on their end?

Thanks @bacongobbler  for quick reply.
Yes - here is the azure-arc issue tracker https://github.com/microsoft/azure_arc/issues/152
But not update since few days on that..
QQ: Does this " apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition" Error indicates that Azure-arc pipeline trying to use v1beta1 CustomResoruceDefinition unsupproted version to install helm? and hence the reason for error?  If so, how I can make the pipeline to use V1 CRD instead of v1beta1.. Sorry, I am beginner in kubernetes--tried to set APIVersion to V1 - But, not sure how to set that...

I cannot tell nor know how one would go about fixing that. Sorry.


Added Ruby

Fixes #645
I have added a free ruby course
Kindly merge it

please add in json file also


Support optional createCanvas factory

This adds no additional dependencies and doesn't break anything but instead adds an optional createCanvas factory function on the params which a caller can use to inject their own canvas.
I plan to implement a hashicon-cli library which will inject the node-canvas in to enable server side image rendering.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

I believe this addresses the concerns in #24 while enabling the core features of the branch.

thank you!

@justinmchase Thanks.   Originally I thought it'd be better to allow bypassing the createCanvas()  completely, so one will not go through our HiDPR scaling, or allow other modifications on the canvas on creation.     But, honestly I don't see any real-world requirement, so I'm cool with your solution. Thanks.
Could you please just update the README as well (params and node-canvas example sections).

Ok will do.


feat: Add root service feature

Hi, I have found your tool very useful, but graphs for very large yamls (which I unfortunately use) can get quit messy.
So I have decided to add this little feature that lets you render just a subset of the whole service dependencies net.

Fixed ci issues

Thanks for your awesome contribution! This new feature will be release in the next version :)

Hi @josef-v, I found some possible conditions that may cause exceptions, such as KeyError, so I fixed it in the later commits and added tests, please take look at #43


Inf. Stamina not working

When sprinting, it seems like the cheat works but the stamina wheel is actually just invisible, the stamina still runs out and you need to wait for it to fill up again. When climbing, the stamina wheel does appear but it decreases like usual. Other cheat options work fine

I'm not sure what codes you are using, but the code works fine, and has been tested by others including myself..
https://youtu.be/maXhUgjIFbA

Oh, do you have an idea as to why mine isn't working? Are there any variables that might effect it?

I've just now noticed, there are some error codes upon game start up on ryujinx that weren't there before I applied the new updated cheats, is it possible for you to check them out and see if they are linked to your cheats?
00:00:02.091 |E| TamperMachine Compile: System.NullReferenceException: Object reference not set to an instance of an object.
at Ryujinx.HLE.HOS.Tamper.InstructionHelper.GetCodeType(Byte[] instruction) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\InstructionHelper.cs:line 80
at Ryujinx.HLE.HOS.Tamper.CodeEmitters.EndConditionalBlock.Emit(Byte[] instruction, CompilationContext context, IEnumerable1 operationsElse) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\CodeEmitters\EndConditionalBlock.cs:line 44    at Ryujinx.HLE.HOS.Tamper.CodeEmitters.EndConditionalBlock.Emit(Byte[] instruction, CompilationContext context) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\CodeEmitters\EndConditionalBlock.cs:line 20    at Ryujinx.HLE.HOS.Tamper.AtmosphereCompiler.CompileImpl(String name, IEnumerable1 rawInstructions) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\AtmosphereCompiler.cs:line 81
at Ryujinx.HLE.HOS.Tamper.AtmosphereCompiler.Compile(String name, IEnumerable1 rawInstructions) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\AtmosphereCompiler.cs:line 41 00:00:02.091 |E| TamperMachine Compile: There was a problem while compiling the Atmosphere cheat 00:00:02.092 |E| TamperMachine Compile: System.NullReferenceException: Object reference not set to an instance of an object.    at Ryujinx.HLE.HOS.Tamper.InstructionHelper.GetCodeType(Byte[] instruction) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\InstructionHelper.cs:line 80    at Ryujinx.HLE.HOS.Tamper.CodeEmitters.EndConditionalBlock.Emit(Byte[] instruction, CompilationContext context, IEnumerable1 operationsElse) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\CodeEmitters\EndConditionalBlock.cs:line 44
at Ryujinx.HLE.HOS.Tamper.CodeEmitters.EndConditionalBlock.Emit(Byte[] instruction, CompilationContext context) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\CodeEmitters\EndConditionalBlock.cs:line 20
at Ryujinx.HLE.HOS.Tamper.AtmosphereCompiler.CompileImpl(String name, IEnumerable1 rawInstructions) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\AtmosphereCompiler.cs:line 81    at Ryujinx.HLE.HOS.Tamper.AtmosphereCompiler.Compile(String name, IEnumerable1 rawInstructions) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.HLE\HOS\Tamper\AtmosphereCompiler.cs:line 41
00:00:02.092 |E| TamperMachine Compile: There was a problem while compiling the Atmosphere cheat

Paste your RYU File.

I'm so sorry to waste your time, I've just done a complete reinstall of everything and the problem is now gone, so it was obviously some mistake on my part. Thanks for your time.


releases: Add manifest for ESECIOTDM RC based on i.MX8MM Release PD21.1.0

Add Manifest for ESECIOTDM release canditate based on the final PHYTEC release PD-BSP-Yocto-FSL-i.MX8MM-PD21.1.0
meta-esec-iotdm is not fixed in this pre-version

Closing, as the manifest is created in phy2octo.


Using function local variables inside an anonymous function causes segmentation fault

example:
(import stdlib)

(using-namespace std

(def main (fn extern-c void (void)
  (def var (var intern int 0)) ;if this is a global variable, it works
  (let ((fun \ (fn void (void)
          (incv var)
          (return))))
    (fun)
    (fun))))
)

This is now fixed.  Anonymous functions should not have access to any variables outside their own scope, including variables defined within the function in which the anonymous function is defined.


Add support for variables substituion similar to I18n.

Hey!
I thought it would be nice to have variable substitution, just like I18n does it, since YAML does not allow string concatenation and partial existing parameter substitution.
So, assuming we have the following YAML-file:
defaults: &defaults
  name: 'Defaults'
  mailer:
   host: 'localhost'
  email<EMAIL_ADDRESS>
email will be equal to Defaults@localost.
Local settings and nested keys are supported too, see tests for more.

@mislav please, answer something here. If you don't want any pull requests here, just close it, so I won't wait anymore.


Refactor Util

Our Util class in lib contained a wide variety of util functions. We also already had a separate FileNameUtils class in lib which only contained one function. I added a new util package under lib and refactored our util classes as follows:

FileNameUtils -> FileUtils, and it now also contains recursivelyClearDirectory (previously in Util)
new class JarUtils which contains all jar-related helpers
new class ProjectLoadUtils which contains our helpers used in loading projects (find the main method and throw the correct exception in the case of an unallowed class)

As part of this work I also made all the util classes final and gave them private constructors that throw an exception if they are used.

LGTM!
Side note -- is this a pattern we should use in other packages too (eg, protocol)?
And if we had a util sub-package elsewhere, would is be parallel to support where we've added that? Maybe support makes more sense as a sub-package in the context of a student-facing package.

@bencodeorg good questions. I mostly made this a subpackage so that all the util classes were in one place and easily findable. If there's only one util class it feels less necessary but if we want to adopt that pattern we can. As to your second question, it would probably make sense to make it parallel, although if the util functions were only used in the support code then it would make sense for the package to be inside support.


mysql version support

this solution only support mysql5.7.
do not support latest mysql8.
https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/#starting-replication

Since this page for example of replicated Stateful application in K8s, So need to mention/investigate more on other softwares.

/retitle "Run a Replicated Stateful Application" task example limited to MySQL 5.7, no MySQL 8 support


installing missing dbus-x11

fix https://github.com/scylladb/scylla-operator-images/issues/57

(would be good to update the commit message and PR title)

tagging to unblock other PRs
/lgtm


Code Quality Analysis

Hello there!
I did a quality code analysis for your project and I would like to share the results of this analysis here. The analysis was mainly done using the SonarCube tool which is responsible for locating code smells and measuring other  metrics for quality in the project. I also used the monkey tool in Android Studio to find errors that could occur when the user interacts with the application, but the test did not detect problems.
I attach two PDF files: the first includes an overview of the analysis and the second a report with more detailed information. These files were created by a trial version of a SonarQube plugin (sending results to GitHub is not included in the free version of SonarQube).
I know time is limited and valuable to developers, so  if you don't have time and you want to improve reliability level of the project  , I would recommend correcting errors that fall into the category of Blocker and Critical. They are the most important for the application. (For more information on how  SonarQube classificates the bugs, visit this page).
If these errors are corrected, the reliability level will increase significantly.
Screen snapshot of errors are attached .

Project's security is at a very good level.
In addition, there are 346 code smells. Code smells are very important in open source projects because maintainability is directly related to them.
For a detailed analysis and to be able to see code smells, please install SonarQube locally and let me know if I can help.
A very good tutorial on the installation and use of SonarQube at Android Studio which I followed can be found here.
Thanks for your time!
Analysis Overview.pdf
Report for Quality Analysis.pdf

This is not relevant anymore as the app was converted to Kotlin.


Enable OSX on Travis

And upgrade travis settings.
Finally no deprecation warnings when loading PyPlot on master.... (after clearing the cache...)

Hmmm, seems that Travis is not enabled for this repo?

Seems that the deprecation warnings are fixed in #5 so the only thing left in this PR now is enabling travis on OSX......

Doesn't hurt, I guess, although this particular package is pure Julia so I'm not worried too much about platform variations.

Agree. Only adding it because it was part of the original PR (and the .travis.yml was copied from Compat.jl...)


Dealing with bounding boxes outside of the image issues

Hello! first of all thank you for your amazing works!
I've implemented YOLOv1 in PyTorch and applied imgaug for augmentation.
I have some questions about cut_out_of_image() function.
(I saw the example Dealing with bounding boxes outside of the image )
i used quokka image where size is 256 x 256
and i run this code
bbs_aug.remove_out_of_image().cut_out_of_image()
and result is
1. BoundingBox(x1=145.0000, y1=25.0000, x2=195.0000, y2=75.0000, label=None)
2. BoundingBox(x1=220.0000, y1=25.0000, x2=256.0000, y2=75.0000, label=None)
shape=(256, 256, 3))

and image is below

I wonder why second bounding box's x2 is 256.

BoundingBox(x1=220.0000, y1=25.0000, x2=256.0000, y2=75.0000, label=None)

I think x2 should be 255 not 256
because image is 256 x 256 , i guess all coords should be within [0-255].

I wonder, what happens if one bounding box is completely outside?

I wonder, what happens if one bounding box is completely outside?

This is discussed in some detail here:
https://imgaug.readthedocs.io/en/latest/source/examples_bounding_boxes.html#shifting-moving-bounding-boxes


Feature Request: Add a flag for --force-parent-span-id

Hey there 👋
Similar to how there's currently functionality for --force-trace-id and --force-span-id, i'd like to request a feature for --force-parent-span-id. The use case here would be useful for folks such as myself that are interested in creating traces with child spans across different languages.
For example, starting a trace w/ parent spans in Ruby OpenTelemetry and passing those parent span ids down into a Bash script with otel-cli so there's a complete trace.
Any input/thoughts would be appreciated, Thanks!

I'm happy to add the feature, makes sense.
Also, did you try setting a TRACEPARENT environment variable before calling otel-cli? otel-cli allows propagating traceparent over envvar and files and that should get your parent trace set automatically.

@tolbert yeah, unfortunately it looked like TRACEPARENT allowed me to overwrite the trace-id and span-id itself, but not trace-id + parent-span-id like I required for making all otel-cli's spans be child spans.
I may have missed something though, so feel free to let me know if that's not the case 😄

If you set TRACEPARENT, usually otel-cli will set your parent span id to the span in the traceparent. It's very similar to how things work over http/grpc headers with the traceparent header.

PR merged, thank you! I'll close this once I release.

@tobert sounds great, thanks! any idea roughly what the ETA of the next release is?

@domofactor apologies, I disappeared into a huge project for a bit. I think the new OTLP work is settled enough to release. I'll do it in the next week or so.

I released v0.4.0 yesterday. Please open more issues if you run into trouble!


[BUG] dash daq.gauge color scale can't take same color in multiple regions

Sorry to be a bother. I've noticed that dash daq.gauge 's color scales do not work if parsed the same color for more than one region. For example, if i have two "warning" regions which i want to be read. I've also notice that, as a workaround, if the colors are given slightly different hex codes, then it works fine.
I've attached examples below - where dial 1 is fine, dial 2 doesnt work due to the above issue and dial 3 works due to the workaround.
Thanks very much!
Harry
import dash
import dash_daq as daq
import dash_core_components as dcc
import dash_html_components as html
from dash.dependencies import Input, Output, State

random_temperature = 18

app = dash.Dash(__name__,)

app.layout = html.Div([
    daq.Gauge(
        id='test-1',
        label="Test 1",
        value=random_temperature,
        min=0,
        max=35,
        color={"gradient":False,"ranges":{"green":[0,10],"yellow":[10,20],"red":[20,35]}},
        units="Celsius",
        showCurrentValue=True,
    ),
    daq.Gauge(
        id='test-2',
        label="Test 2",
        value=random_temperature,
        min=0,
        max=35,
        color={"gradient":False,"ranges":{"red":[0,10],"yellow":[10,20],"red":[20,35]}},
        units="Celsius",
        showCurrentValue=True,
    ),
    daq.Gauge(
        id='test-3',
        label="Test 3",
        value=random_temperature,
        min=0,
        max=35,
        color={"gradient":False,"ranges":{"#ff0001":[0,10],"yellow":[10,20],"#FF0000":[20,35]}},
        units="Celsius",
        showCurrentValue=True,
    ),
])

if __name__ == '__main__':
    app.run_server(debug=True)

Thanks @henrykeithturner - moved to the dash-daq repo where this would be addressed.
You're absolutely right, this is a limitation of the current API using a dict with the colors as keys - one of the values will overwrite that other.
I can see two ways to handle this:

Allow a value of this dict to be a list of lists. Advantage is this can be backward-compatible, disadvantage is you can't keep the ranges in order, you must put all the reds together:

"ranges": {"red": [[0, 10], [20, 35]], yellow: [10, 20]}

turn the whole thing into an ordered structure, perhaps a list of [color, range]. This isn't as self-documenting, and has a lot of nesting that would be easy to get wrong. Also not backward-compatible unless we continue accepting both forms. But it's compact and easy to read, and inherently ordered:

"ranges": [["red", [0, 10]], ["yellow", [10, 20]], ["red", [20, 35]]]
# or, less nested but possibly more confusing
"ranges": [["red", 0, 10], ["yellow", 10, 20], ["red", 20, 35]]

Colors also don't align with the range-values if min is not equal to zero


Log problematic sentences

Automatically log problematic sentences as pending for the trainer web interface, PR on rasa-nlu-trainer to import those pending strings
Proposed changes:

Added a processor on the response
Based on a config file, compares the threshold defined with the response confidence and if needed log the string to a JSON file defined in the config file
The extracted strings can be imported in the Rasa-nlu-trainer

Status:

[x] ready for code review
[ ] there are tests for the functionality
[ ] documentation updated
[ ] changelog updated

Tests to be added.
Needs https://github.com/RasaHQ/rasa-nlu-trainer/pull/27 for the import part.
Which section in the documentation should I add this to ?

I would add the docs here: https://rasa-nlu.readthedocs.io/en/latest/closeloop.html

thanks for your work. I am not sure we need this logging, as every request is logged anyways. Basically, you can extract the problematic sentences from the logging file by going through them and filtering them according to the logged confidence.
Maybe we could add a threshold to the logging that we already do?


Update circe-core, circe-jawn, circe-parser to 0.14.0

Updates

io.circe:circe-core
io.circe:circe-jawn
io.circe:circe-parser

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

Files still referring to the old version number
The following files still refer to the old version number (0.13.0).
You might want to review and update them manually.
COMPATIBILITY.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

labels: library-update, semver-minor, old-version-remains

Superseded by #1118.


container.exec fails with dockerode 2.5.0 but worked fine with dockerode 2.4.3

I run the following code in my app:
    const command = 'sudo chown user:user /home/user/.ssh/authorized_keys';
    const container = docker.getContainer(containerId);
    const options = {
      Cmd: [ '/bin/bash', '-c', command ],
      AttachStdout: true,
      AttachStderr: true
    };

    container.exec(options, (error, exec) => {
      if (error) {
        callback(error);
        return;
      }

      exec.start((error, stream) => {
        callback(error, stream);
      });
    });

With dockerode v2.4.3 it works fine, but with dockerode 2.5.0 my callback receives this error:
{ Error: (HTTP code 500) container not running - {"message":"EOF"}

    at /home/janx/janitor/node_modules/docker-modem/lib/modem.js:243:17
    at IncomingMessage.<anonymous> (/home/janx/janitor/node_modules/docker-modem/lib/modem.js:270:9)
    at emitNone (events.js:110:20)
    at IncomingMessage.emit (events.js:207:7)
    at endReadableNT (_stream_readable.js:1047:12)
    at _combinedTickCallback (internal/process/next_tick.js:102:11)
    at process._tickCallback (internal/process/next_tick.js:161:9) reason: 'container not running', statusCode: 500, json: null }

Note, this happens with two Docker instances running versions 17.05.0-ce and 1.12.6.
Edit: With 2.4.3, the chown user:user is successfully applied, but with 2.5.0 the targeted file remains root:root.

A workaround is attaching to stdin and the error will go away, check the issue bellow there is an example there.
It was caused by:
https://github.com/apocas/docker-modem/issues/81
We are still trying to find why dockers behaves like that when you don't attach to stdin.

Same problem here back to v2.4.3 and work fine :)

We're still pinned on v2.4.3 because of this issue :) not a huge problem though

Just published v2.5.1 that should fix this.

I confirm that v2.5.1 doesn't seem to have this problem anymore. Thanks a lot for the fix!


md-icon is not rendered correctly in md-button

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The Icon in md-icon should be aligned horizontally centered when it is used in a md-raised-button.
What is the current behavior?
When I have a md-icon in a md-raised-button the icon is rendered at the top of the button and not in the center like the normal text is.
What are the steps to reproduce?
<button md-raised-button">Last<md-icon>navigate_before</md-icon></button>

Like you can see the icon is rendered very weird.
Which versions of Angular, Material, OS, browsers are affected?
Angular: 2.0.1
Angular Material: 2.0.0-alpha.9-3
Angular-CLI: 1.0.0-beta.15
Tested in Chrome and Firefox on Ubuntu 16.04

I found this as well. I made due in the mean time by setting vertical-align to [md-raised-button] md-icon

I have the same problem with version "v2.0.0-alpha.8-2". Could you put an example of your workaround @emilio-martinez? Thanks

I found a workaround for this issue in my case (row with "center center" alignmen):

          <button md-raised-button color="primary" type="button" (click)="addPoint()">

              <md-icon md-list-avatar>note_add</md-icon>
              {{ 'ADD_POINT' | oTranslate }}

          </button>

An easier option (adding style="vertical-align:middle;")
<button md-raised-button color="primary" type="button" (click)="addPoint()"><md-icon md-list-avatar style="vertical-align:middle;">note_add</md-icon> {{ 'ADD_POINT' | oTranslate }}</button>

@denislamela exactly. Vertical align does the trick. That said, some icons shift a bit, so vertical-align: middle will not necessarily work exactly right all the time.

The question here is "which is the right component for a button containing both text and an icon?", and then we need to make sure that it behaves as expected.

I actually figured out a way (especially for md-raised-button, since for an non md-raised-button the icon and the text alignments are OK). All you have to do is to wrap the md-icon and the text part under another div - where the div is a flex and has a the following properties:
.your-flex-container {
    display: flex;
    flex-direction: row;
    align-items: center;
    align-contents: center;
}

Also to provide a bit of distance between the text and the icon, I added 8px margin-left to the text element.
Note: For convenience, I have used the same CSS layout styles as in Angular material v1.x.x.
[layout="row"] {
    -webkit-flex-direction: row;
    -ms-flex-direction: row;
    flex-direction: row;
}

[layout-align="center center"]{
    align-items: center;
    -webkit-align-content: center;
    -ms-flex-line-pack: center;
    align-content: center;
    max-width: 100%;
}

And the button HTML markup looks like the following:
<button md-button md-raised-button>

        <md-icon> settings</md-icon>

Settings

</button>


Unable to verify integrity of package

Hi @kei6u , we tried out this package and it works very well. Thanks for putting it together.
When we install it via krew it states the following in bright red

WARNING: You installed plugin "secretdata" from the krew-index plugin repository.
These plugins are not audited for security by the Krew maintainers.
Run them at your own risk.

This is a problem for us. I wonder if there is any way to begin performing security auditing on the plugin? This way more people may have confidence in using it...
Again, thanks for putting the project together. Please don't take this as a criticism. It is just a concern when we are dealing with sensitive data.

@lewismc
Thank you for reporting!
I will look into it to solve the warning.

@lewismc
Investigation:
The warning when installing this plugin via krew also occur in other plugin installation due to https://github.com/kubernetes-sigs/krew/issues/576.

The reason we added this is because users must understand that they are downloading potentially unvetted binaries.

This pr added the feature to output the warning message.
Conclusion:
Every plugin installation via krew outputs the warning and there is no way to prevent it currently.

Thank you for doing the investigation @kei6u and apologies for my late response.


CUDA 12.0

Comment:
CUDA 12.0 has been released (https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#cuda-12-0-release-notes).
When can we expect a corresponding cudatoolkit package?

It's still WIP: https://github.com/conda-forge/staged-recipes/issues/21382

Yeah we are taking this opportunity to restructure how the packages work actually. Part of this is including the compiler as its own package. Another part of this is providing finer grain division of the libraries themselves so packages using them don't need to bring in as much stuff. This means it will take a bit longer. It also means we may not have a cudatoolkit package per-se as new packages supersede it.

This is out and packages are being rebuilt for CUDA 12. More details in issue ( https://github.com/conda-forge/conda-forge.github.io/issues/1963 )


The SD-JWT DC does not CONTAIN the Key Binding JWT

Section 3.2 states:

SD-JWT VCs MUST be encoded using the SD-JWT format defined in Section 5 of [I-D.ietf-oauth-selective-disclosure-jwt].  A presentation of an SD-JWT VC MAY contain a Key Binding JWT.
Note that in some cases, an SD-JWT VC MAY have no selectively disclosable claims, and therefore the encoded SD-JWT will not contain any Disclosures.

The SD-JWT DC does not CONTAIN the Key Binding JWT. See the revised Figure 1. See #285.
However, a SD-JWT VC CAN be ASSOCIATED with a Key Binding JWT
The following changes are proposed:

A presentation of an SD-JWT DC CAN be associated with a Key Binding JWT.
Note that in some cases, an SD-JWT DC MAY have no selectively disclosable claims, and therefore the encoded SD-JWT will not be associated with any Disclosures.

Although, I agree with the proposed idea (I also think that SD-JWT doesn't contain a KB-JWT, rather a KB-JWT may be associated to an SD-JWT presentation), yet I feel that this proposal should target SD-JWT and not SD-JWT-VC.


operator mariadb-operator (0.12.0)

Add operator mariadb-operator (0.12.0) to community operators

/merge possible

/retest-required

/merge possible

/retest-required


Improved code coverage of nspmessage app

Also new_message view doesn't create message object unless the following statements are true:
    if Follow.objects.filter(follower=sender, following=receiver):
        if Follow.objects.filter(follower=receiver, following=sender):

Pull Request Test Coverage Report for Build 32

34 of 35 (97.14%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+3.5%) to 77.185%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

nspmessage/views.py
4
5
80.0%

Totals

Change from base Build 30:
3.5%

Covered Lines:
998

Relevant Lines:
1293

💛  - Coveralls


Update README.md

Adding example to the doc: custom stream
Description
Adding example to the doc: custom stream
Reference issue
No issue

thanks!


[Epic] Tasks related to version 4.1.0 sample

Context
This is an Epic to track all sample tasks with the GitHub task feature. Here is the task list:

[ ] #40
[x] #43
[ ] Make sure all code snippets in doc(not sample) have imports.
[ ] Check and fix Out-of-date samples.

[x] EventHubs-Kafka: Example is out of date (dependencies versions are old)
[x] azure-spring-cloud-sample-servicebus-topic-binder: example is out of date
[ ] Storage queue: Queue name is not in the config, not clear where to change or if it will be created.

[ ] Make azure-spring-boot-sample-keyvault-secrets consistant with configure-spring-boot-starter-java-app-with-azure-key-vault
[x] #26
[x] #30
[x] #35
[ ] A wiki page to list all samples and analyze samples
- there are features sdk support but not covered in this repo.
[ ] Rename artifactId
[x] #42

@fangjian0423  please take a look of this issue, and provide priorities, anything urgent and have more impact should be done and those only, we already have lots of things to do


Update websites-dotnet-webjobs-sdk-service-bus.md

Fix documentation - introduction was slightly incorrect, and a couple of minor spelling/capitalisation errors

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

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@johndowns I think that typo was fixed in a previous PR, so now there is a merge conflict. If you can fix the conflict, I will get someone to review the rest of your submission. Thanks for helping out!


Update oci-cn-auth

Message from Arnaud
OCI is rolling out a new firmware update for Mellanox CX5 NICs. The firmware gets applied on the host machine through internal OCI process and customers don’t have to install firmware. However on the GPU nodes, there is a Mellanox config change which is required (documented below) for optimal RDMA performance. The same config change also works on existing firmware, hence OCI recommendation is to apply the change on all GPU nodes with RDMA cluster network to ensure all nodes have same configuration.
Who should update
The change impacts customers running multi-node cluster network / RDMA jobs.  It doesn’t impact single node customers, not using RDMA.
Steps to update
Given below are various scenarios and steps to update.
Scenario-1: Existing GPU cluster with RDMA
The change can be applied without disrupting the jobs using the steps below.  We have a bash script which will do the below steps.

  Update the roce_tx_window_en setting. This will not impact running jobs, this update the config without any service restart, but to persist the change across reboot, do step2.

  Install oci-cn-auth-2.1.4 rpm/deb package , which has the above fix to make the change permanent (survive node reboot or NIC restart). Our bash script will install the package.

Scenario-2: Adding/replacing nodes of existing GPU cluster with RDMA
We will modify the RDMA ansible role to make sure the oci-cn-auth-2.1.4 rpm package is installed before configuring the interface.
Scenario-3: Provisioning a new GPU cluster with RDMA
Ask OCI team to provide you the new OCI GPU custom image which has the fix.
How do I know if I am running new Mellanox firmware
New firmware version is:  16.34.1002.  You can check for it on a GPU node using command: ibstat | grep "Firmware version” .  We have a script you can run to check for it.

@steven-basart
Can this be closed?

We need to rerun the cais-all playbook. This was a reminder to myself to do that. So I'll do it now.

 So good to close.


ValidationPipe ignores empty body

class RegisterDTO {
  @IsEmail()
  email: string;

  @IsNotEmpty()
  @IsString()
  @Length(6, 64)
  password: string;
}

class AuthController{
  @Post("/register")
  @HttpCode(201)
    public register(@Body(ValidationPipe) body: RegisterDTO) {
      return AuthService.register(body);
    }
}

When I'm hitting POST /register endpoint with Postman (empty body) validation doesn't run and I get 200. If I declare something like {} validation works just fine and it requires mentioned values like email and password. Am I missing something?

Hi @impez
Thanks for the report. A fix has been released.


Modularize simBEV

simBEV works ok when running completely from input data to results. But it is lacking a structure that allows to run single parts, e.g. generating load timeseries from standing times created before.

closes #10


SCRIPT1002: Syntax error after ng build --prod and run it on VM with IE10

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request

Versions.
node: 6.9.2
os: win32 x64
@angular/common: 4.0.1
@angular/compiler: 4.0.1
@angular/core: 4.0.1
@angular/forms: 4.0.1
@angular/http: 4.0.1
@angular/platform-browser: 4.0.1
@angular/platform-browser-dynamic: 4.0.1
@angular/router: 4.0.1
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.1
Repro steps.
I did ng build --prod on my local machine and copy the dist folder into my VM which has IE10, when trying to load the page console.log error says SCRIPT1002: Syntax error
I also enabled Polyfills for IE10, IE11
/** IE9, IE10 and IE11 requires all of the following polyfills. **/
import 'core-js/es6/symbol';
import 'core-js/es6/object';
import 'core-js/es6/function';
import 'core-js/es6/parse-int';
import 'core-js/es6/parse-float';
import 'core-js/es6/number';
import 'core-js/es6/math';
import 'core-js/es6/string';
import 'core-js/es6/date';
import 'core-js/es6/array';
import 'core-js/es6/regexp';
import 'core-js/es6/map';
import 'core-js/es6/set';

The log given by the failure.

SCRIPT1002: Syntax error  when loading the page on VM IE10

Desired functionality.

Mention any other details that might be useful.

Looks like it was my base href="/appsrc/" to base href="/" however nothing is being loaded just loading...

Fixed my issue, just wrong base href!

Can you talk to how to fixed?


Code and changelog for v3?

On npm ts-force and ts-force-gen are on v3.0.0-rc.8 (published 10 days ago), but the latest version in this repo is 2.7.0 on master and 3.0.0-rc.3 on the 3.0 branch.
Where can I find the updated code for 3.0.0-rc.4 through 3.0.0-rc.8? Also, where can I find a changelog, if one exists, for those versions.

the rc versions should not have technically been marked as latest on npm.  Even though 3.x is probably better and more stable, I haven't had a chance to finish documenting and testing.
I just pushed my recent local commits, including a change log of everything since 2.7.
3.x got sidetracked by 'grand visions' of fixing all the less than ideal design decisions... However, I've recently been working through some of the remaining items and do actually plan on releasing it soon.  Strict support (including your PR) is part of that.


Feature request: UI testing environment

Working on Wagtail’s admin UI, I find it unnecessarily hard to make sure that I take all of the variations in UI components into account. It's a problem with all projects that have fairly big UIs, but is compounded in Wagtail by the fact that so much of the UI is dependent on what content has been created in the CMS, and on how the site has been set up. It also doesn't help that Wagtail's default dev environment is first meant to be a good demo of how Wagtail would be used on a small-scale website, rather than a dev playground (https://github.com/wagtail/bakerydemo/issues/175).
Having a more comprehensive UI "test" environment would help in a number of scenarios:

Reviewing the existing UI, for example as part of a UX review, accessibility testing, compliance, or just when testing the impact of a specific change.
Changing existing UI components, and reviewing changes. It's really hard to know what impact a UI change might have, if you have to know how to use the CMS for bits of its UI to appear. This is particularly problematic when multiple people work on the same feature, and they all have to do the same error-prone setup on their local copies of Wagtail for them to test their changes meaningfully
Setting up automated UI testing in continuous integration – accessibility testing (https://github.com/wagtail/wagtail/issues/4871#issuecomment-486648541), visual regression testing. These are impossible to set up if we don't have a standardised test environment to build the test suites for.

Related: #3804, https://github.com/wagtail/bakerydemo/issues/175, https://github.com/wagtail/wagtail/issues/4871#issuecomment-486648541, https://github.com/wagtail/rfcs/pull/37

This was previously discussed at a Wagtail team meeting, and the conclusion there was that it should be done as a separate environment / project, rather than extending bakerydemo. It's not entirely clear how this project could then be used in the Wagtail CI builds. Thoughts welcome!

I'm super keen for this too. Working on refactoring some of our older JS, and some of it really could use with some tests.
I'm keen to take a stab at this as part of that refactor as now really is the right time for me to be writing tests whilst I know about the edge cases. Rough thoughts on a path forward:

Take bakerydemo as a starting point
Remove vagrant but keeping the docker setup with the intention of running our tests inside docker
Keep the models as a starting point, but implement testdata in a way that can easily be modified (probably by creating some JSON of just the data, and the importing the models and programatically creating them)

Yep, I’ve also struggled with turning this into an achievable task. My WIP has been to at least tweak the settings to make it easier to automate browsing on the bakery demo: https://github.com/thibaudcolas/bakerydemo/pull/2.
Then my plan was to start making test content for all of the scenarios to support, defined here https://github.com/thibaudcolas/wagtail-tooling/blob/master/ui/scenarios.js (not just individual items within the "scenarios" array, but also all of the states in each of those items).
Once that’s done, all of the cases listed in https://docs.google.com/spreadsheets/d/1rTMilzKhcb43Y3fZKGJJeoKWLCR00bfgwVB9f6OaC2U/edit#gid=0 should be testable.

Yeah sure. The hurdle I've hit with bakerydemo is adding lots of additional
data (without doing it by hand) is hard. There are a few pagination states
that don't get hit with the current data. (Although there may well be an
easy way to do this that I don't know about...)
On Thu., 6 Jun. 2019, 3:12 am Thibaud Colas<EMAIL_ADDRESS>wrote:

Yep, I’ve also struggled with turning this into an achievable task. My WIP
has been to at least tweak the settings to make it easier to automate
browsing on the bakery demo: thibaudcolas/bakerydemo#2
https://github.com/thibaudcolas/bakerydemo/pull/2.
Then my plan was to start making test content for all of the scenarios to
support, defined here
https://github.com/thibaudcolas/wagtail-tooling/blob/master/ui/scenarios.js
(not just individual items within the "scenarios" array, but also all of
the states in each of those items).
Once that’s done, all of the cases listed in
https://docs.google.com/spreadsheets/d/1rTMilzKhcb43Y3fZKGJJeoKWLCR00bfgwVB9f6OaC2U/edit#gid=0
should be testable.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/wagtail/wagtail/issues/5271?email_source=notifications&email_token=AAJTOZ2PC2XIVJCECPUVU2LPY7XYNA5CNFSM4HJTSNA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXAMRSA#issuecomment-499173576,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJTOZ3VHWW2NHW5KJYXUTDPY7XYNANCNFSM4HJTSNAQ
.

I've put up a proof of concept wagtail environment  thats designed to be used by Wagtail developers and our CI. Yet to see how Travis goes with it, but you can run docker inside Travis so hopefully should be smooth sailing. Not completely happy with how we run the tests, but It Works™.
Also verrrrry roughly mocked up using Pa11y's actions along side one of your scenarios and that works really well! Loads more to do but it's a start.
Be interested to get your thoughts on this @thibaudcolas given right now it would probably be mostly you and I using it, if we think it's on the right track I'll look into proposing how we could integrate it with our build pipeline (and start writing some tests for my JS refactoring 🎉).

@marteki interested in this

FYI we briefly discussed this today. I’ve kept https://github.com/thibaudcolas/wagtail-tooling maintained, especially to help with the accessibility work in https://github.com/wagtail/wagtail/projects/5.
At the moment it contains a test suite of a 100+ cases, based on content from the bakerydemo. I regularly use this to review pull requests that change a lot of parts of the UI.
I don’t have much time to spend on this currently but if anyone is interested in using this / picking it up, the tooling is available in the repository. @allcaps was working on a UI testing environment directly within the Wagtail repository during the last sprint in Bristol, which would greatly simplify integrating this into our development workflow (and in CI).

I believe this has been addressed in #7751 so will close this now.


Update Composer dependencies (2023-05-18-00-08)

Visual regression test passed!
View the visual regression test report


Uploading Image MicrosoftDocs/azure-docs#42903

Uploading the image of Performance Counters Metric option sitting under Monitoring Blade. MicrosoftDocs/azure-docs#42903

#sign-off

@mrbullwinkle: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Hi @MonikaReddy-MSFT - thanks, we'll merge this.
As a reminder, can you use the private repo for such PRs in the future? Thanks.


Add documentation for running docker-compose without gitlab

Add docker-compose.no-gitlab.yml that can be added to
docker-compose.yml making it possible to skip gitlab in houston.
Add documentation in deploy/codex/README.md for how to use
docker-compose.no-gitlab.yml.

/rebase


The word secondary indexes suites better than the word secondary indices

The word secondary indexes suites better than the word secondary indices. And users can connect with Index word than Indices

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8d56f28171a3ed1aa1837574ffac4235df48314c/
Edited pages:

v19.1/interleave-in-parent.md


Support for DateTimeOffset

I think a support for DateTimeOffset would be nice complement to the existing DateTime helpers in Humanizer. DateTimeOffset works better in most cases than DateTime, since it represents a very specific moment in time and has better timezone support than the oversimplified DateTimeKind enum in DateTime type.
Please consider.

:+1:

Completely agreed. This has been in my mind since V1.
So you're volunteering to do it? ;)


Unable to run chapter05 (and probably others) as unable to download pdbbind_v2015.tar.gz

Running deepchem 2.3.0 in a conda environment on ubuntu.
From looking at the error by hand, it seems the url http://deepchem.io.s3-website-us-west-1.amazonaws.com/datasets/pdbbind_v2015.tar.gz is 403ing.
Stack Trace
$ python3 pdbbind_nn.py
Traceback (most recent call last):
  File "pdbbind_nn.py", line 4, in <module>
    pdbbind_tasks, pdbbind_datasets, transformers = dc.molnet.load_pdbbind(featurizer="grid", split="random", subset="core")
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/site-packages/deepchem/molnet/load_function/pdbbind_datasets.py", line 230, in load_pdbbind
    dest_dir=data_dir)
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/site-packages/deepchem/utils/__init__.py", line 83, in download_url
    urlretrieve(url, os.path.join(dest_dir, name))
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/urllib/request.py", line 247, in urlretrieve
    with contextlib.closing(urlopen(url, data)) as fp:
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/urllib/request.py", line 222, in urlopen
    return opener.open(url, data, timeout)
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/urllib/request.py", line 641, in http_response
    'http', request, response, code, msg, hdrs)
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/urllib/request.py", line 503, in _call_chain
    result = func(*args)
  File "/home/ella/anaconda3/envs/deepchem/lib/python3.7/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 403: Forbidden

I attempted this both from my home PC and routed via my university VPN, so I don't think it is my connection.

Ah our apologies! This is because we had to switch AWS backends (our support from Stanford ran out so we swapped to our own backend). The old URLs are no longer accessible
Easiest fix here is probably to upgrade to the nightly deepchem build which points to the correct new S3 buckets with
pip install --pre deepchem

As a warning, the rest of the book code hasn't been converted to the nightly build, so there may be different errors, but we plan to make this conversion over the coming weeks as part of our upcoming release


Add Aaron Johnson

Additional comment:
No response

@conda-forge-admin, please add user @AaronDJohnson


Document React + Event handling

Event's foo["bar"] usage, and some practical examples with onClick, onChange (form events) etc.

Done in #882


maybe harden the rewardcontroller against hostile tokens

Currently, the rewardcontrolelr is attackable by a malicious token, that can take the entire balance of the rewardtoken from the contract by misreporting the balances and totalbalance.
A malicious token would have to be onboarded by the rewardcontroller.owner, and can be removed if discovered in time.
The attack would work by for example returning 1 for the totalBalance and 100 (or any suitable value) for an account balance.
Now in updateVault, vault.rewardPerShare would be set to the total amount of rewards.
Then, in commituserbalance, the user would be awarded 100 * the total allocation of the vault. Which the user can then claim.
(It seems to me this can work but I have not reproduced this in a test)
One possible way to avoid this attack is to make sure that the token cannot access rewards that are not allocated to that vault in the first place.  One way is to keep counters for the total amount allocated to the vault (in updateVault) and the total amount claimed (in claimReward), and then revert in claimReward if the vault pays out more than its allocation.

Well this will work only if a malicious token is registered directly right, but if the contract is an actual vault, even if a vault with malicious token, it won't work right?
We could ensure in the setAllocPoint that the vault added comes from the factory, which would mean this attack won't be possible anymore.

But we might also want to make sure a vault only has access to its own reward in any case

sorry false alarm, the balances do not come from the token, but from the (shares in) the vault


NNAPI Support?

Hello,
I see examples using the Android GPU delegate and CPU for tflite, but no examples or mention of using the NNAPI for Android. Is this supported and will examples be made available?
Thanks!

@jessedaniels NNAPI is lower level API on android than TFlite. We do not have plans to support NNAPI inference for Android. What is the use case for this? If you like to support NNAPI in MediaPipe, we welcome contribution on this. You will have to do something similar to TFLiteinference calculator

TFLite provides a UseNNAPI(bool enable)  option on the interpreter class to use NNAPI from TFLite. From my understanding it can provide further optimized operator placement on the compute devices, e.g., use the DSP on a Qualcomm chip. It seems like this capability is getting more attention with the Android 10 release to optimize network performance. Android 10 is also supposed to provide additional control over operator placement.
Just curious if this TFLite feature was on a support roadmap as an execution option in addition to GPU/CPU. We've seen performance improvements using the NNAPI interface on some of the newer phones/tablets.
Thanks


Support ECMAScript private fields added from TS 3.8

ECMAScript private fields spec was implemented in TypeScript and released at v3.8 beta.
https://github.com/microsoft/TypeScript/issues/33925
class C {
    #foo = 10;
    bar = true;

    piyo() {
        return this.#foo;
    }
}

Previously the private name field declaration #foo in #foo = 10 was not highlighted. This PR adds highlight to it
Now '#' is part of identifiers in TypeScript. So this PR adds it to iskeyword option. Vim can recognize #foo as one identifier by it.

Thanks!

are private methods a thing?

I did not care methods.

I checked TypeScript 3.8 RC, but it does not support private methods. It's private 'fields' so it does not include methods.
I tried:
class Foo {
    #foo() {
        console.log('hi');
    }
    show() {
        this.#foo();
    }
}

and I got:
foo.ts:2:5 - error TS18022: A method cannot be named with a private identifier.

2     #foo() {
      ~~~~

Found 1 error.

Hi @NullVoxPopuli, it won't be hard to add private method support once it is available in TypeScript.
Let's wait for its adoption.


I can't get sample Rule to work

Hello, thanks for your plugin.
I'm trying to define a rule for a specific filetype but the sample code doesn't work
npairs.add_rules({
  Rule("$", "$",{"tex", "latex"})
    -- don't add a pair if  the previous character is xxx
    :with_pair(cond.not_before_regex_check("xxx", 3))
     }
)

The only way I can get it to work is to leave off the filetype.
Here is my full configuration
require('nvim-autopairs').setup()
local Rule = require('nvim-autopairs.rule')
local remap = vim.api.nvim_set_keymap
local npairs = require('nvim-autopairs')

-- skip it, if you use another global object
_G.MUtils= {}

vim.g.completion_confirm_key = ""
MUtils.completion_confirm=function()
  if vim.fn.pumvisible() ~= 0  then
    if vim.fn.complete_info()["selected"] ~= -1 then
      return vim.fn["compe#confirm"](npairs.esc("<cr>"))
    else
      return npairs.esc("<cr>")
    end
  else
    return npairs.autopairs_cr()
  end
end

remap('i' , '<CR>','v:lua.MUtils.completion_confirm()', {expr = true , noremap = true})

-- you can use some builtin condition
local cond = require('nvim-autopairs.conds')
require('nvim-autopairs').clear_rules()  -- <=== I clear the default rules on purpose.  This is the only way my defined rule works

npairs.add_rules({
  Rule("(", ")")
    :with_pair(cond.not_before_regex_check("\\", 1))  -- <== I only want this rule to apply on latex files; adding {"tex","latex","plaintex"}  to the argument list had no effect.  It just made the rule not apply.
  }
)

My neovim version:
NVIM v0.5.0-dev+1285-g0150cc416
Build type: Release
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -O2 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/nelson/builds/neovim/build/config -I/home/nelson/builds/neovim/src -I/home/nelson/builds/neovim/.deps/usr/include -I/usr/include -I/home/nelson/builds/neovim/build/src/nvim/auto -I/home/nelson/builds/neovim/build/include
Compiled by root@anarchy

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/share/nvim"

Run :checkhealth for more info

This rule is work.
npairs.add_rules({
  Rule("$", "$",{"tex", "latex"})
    -- don't add a pair if  the previous character is xxx
    :with_pair(cond.not_before_regex_check("xxx", 3))
     }
)

you define wrong It is use lua regex not vim \
In lua you need use % before special character double slash because it use on string .
1 is a length of text for to check with that regex.
If you don't want a regex you can write a function to check text.
npairs.add_rules({
  Rule("(", ")")
    :with_pair(cond.not_before_regex_check("%\\", 1))
  }
)

I update docs with new condition to check text
https://github.com/windwp/nvim-autopairs/blob/master/doc/rules.md

Maybe I'm doing something wrong with my setup?
You can see from the gif that when I try to use the rule with filetypes, it doesn't work.  The first half of the gif shows the rule with no filetype defined.  The last half shows the rule with filetype defined but not triggering.

https://imgur.com/wrOnRGu

Sorry i can reproduce it .I use the same rule and it work on plaintex file.
you can run :imap ( and check is that have a mapping.
if it doesn't have mapping. so i don't have any idea about it :). or you can test to change filetype to lua and test.

There's an incompatibility between autopairs and nvim-tree
I don't think it's the fault of autopairs.  I don't even think it's the fault of nvim-tree.  But it's weird behavior when using packer to install the two.  Changing the way i installed the two together in packer fixed the problem.
I changed
# This breaks autopairs.  Autopairs will only work if I manually launch nvim-tree.
use "kyazdani42/nvim-tree.lua"

to
# This code makes autopairs rules work
use {"kyazdani42/nvim-tree.lua", opt = true }

Hmm. it is very strange
if your mapping with filetype is not working then the only way to do that is break  that autocommand.
https://github.com/windwp/nvim-autopairs/blob/master/lua/nvim-autopairs.lua#L56-L57
but I check nvimtree  source code and don't see any problem. :cry:

Maybe it's more of a packer problem?  Changing this setting moves the directory where the plugin is stored.  Maybe they both have to be in the same directory to work well together?   Or maybe it's the order in which packer loads optional plugins vs autostart ones.  I'm not sure.  Both plugins are optional and that works.


Create infrastructure for system-tests

Unfortunately our current unit tests can't simulate all the weird nuget responses. I would like to build a integration test suite which actually runs the whole paket process. We need infrastructure for this.
Current idea:

create a new folder "integration-tests"
create subfolders for every integration test
in testxxc subfolder create a "initial" subfolder and "expected" folder
in "initial" add a "scenario.txt" file

first line contains command line call.
other lines are comments

running test

copy initial folder to temp dir
run specified command from  scenario.txt
compare temp folder with "expected" folder and report differences

Is this a good idea? Is there a tool that works on mono and .NET which works like this?

Any news on this?

Sorry for the delay, but I hope to send something this week or so for review.

Was the system-tests folder moved or deleted? After fetching latest, I can't seem to find it anymore.

I think @forki removed them so that they didn't pollute the codebase

I deleted it. Since tests were too old. We need to create new ones.
On Feb 2, 2015 4:43 PM, "Jon"<EMAIL_ADDRESS>wrote:

Was the system-tests folder moved or deleted? After fetching latest, I
can't seem to find it anymore.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/153#issuecomment-72478456.


Crash

Waybar crashes frequently with the following error:
malloc(): unaligned tcache chunk detected
[1]    39455 IOT instruction (core dumped)  waybar

If  you need more information, please let me know how to provide it and I will try to do so.
Also note the following info:
λ ~/ waybar --version
Waybar v0.9.10

λ ~/ screenfetch
                   -`
                  .o+`                 patrick@plato
                 `ooo/                 OS: Arch Linux
                `+oooo:                Kernel: x86_64 Linux 5.16.12-zen1-1-zen
               `+oooooo:               Uptime: 7h 27m
               -+oooooo+:              Packages: 1525
             `/:-:++oooo+:             Shell: zsh 5.8.1
            `/++++/+++++++:            Resolution: 1745x981
           `/++++++++++++++:           WM: sway
          `/+++ooooooooooooo/`         GTK Theme: WhiteSur-light [GTK2/3]
         ./ooosssso++osssssso+`        Icon Theme: WhiteSur
        .oossssso-````/ossssss+`       Font: Noto Sans,  10
       -osssssso.      :ssssssso.      Disk: 3.9T / 4.1T (94%)
      :osssssss/        osssso+++.     CPU: AMD Ryzen 7 PRO 4750U with Radeon Graphics @ 16x 1.7GHz
     /ossssssss/        +ssssooo/-     GPU: AMD/ATI
   `/ossssso+/:-        -:/+osssso+-   RAM: 3678MiB / 31383MiB
  `+sso+:-`                 `.-/+oso:
 `++:.                           `-/+/
 .`                                 `/

I am willing to help, but I am not sure how to start. Can you give some quick pointers?
Like; should I build in debug mode... and how... are there other important pointers?

How did you generate that core dump?
I would like to know the exact error for my issue (as well).

I also run Arch Linux which uses systemd. You can use coredumpctl and coredumpctl debug $PID to list coredumps and start gdb on the coredump. The command bt shows the backtrace in gdb. I think the systemd-coredump.socket is enable per default, so you should have some coredumps too.

This is my coredump:
Core was generated by `./waybar'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f417f82cd24 in ?? () from /usr/lib/libgtk-3.so.0
[Current thread is 1 (Thread 0x7f417b151240 (LWP 28399))]
(gdb) bt
#0  0x00007f417f82cd24 in  () at /usr/lib/libgtk-3.so.0
#1  0x00007f417f240ef2 in  () at /usr/lib/libglib-2.0.so.0
#2  0x00007f417f245074 in g_hash_table_unref () at /usr/lib/libglib-2.0.so.0
#3  0x00007f417f82fa69 in  () at /usr/lib/libgtk-3.so.0
#4  0x00007f417f827b76 in  () at /usr/lib/libgtk-3.so.0
#5  0x00007f417f81bd98 in  () at /usr/lib/libgtk-3.so.0
#6  0x00007f417f7c2aca in  () at /usr/lib/libgtk-3.so.0
#7  0x00007f417f992fae in  () at /usr/lib/libgtk-3.so.0
#8  0x00007f417f993c6d in gtk_widget_get_preferred_height_and_baseline_for_width () at /usr/lib/libgtk-3.so.0
#9  0x00007f417f7ca3d3 in  () at /usr/lib/libgtk-3.so.0
#10 0x00007f417f814fe7 in  () at /usr/lib/libgtk-3.so.0
#11 0x00007f417f81bf5d in  () at /usr/lib/libgtk-3.so.0
#12 0x00007f417f7c2aca in  () at /usr/lib/libgtk-3.so.0
#13 0x00007f417f992fae in  () at /usr/lib/libgtk-3.so.0
#14 0x00007f417f993a09 in gtk_widget_get_preferred_height () at /usr/lib/libgtk-3.so.0
#15 0x00007f417fa619cb in  () at /usr/lib/libgtk-3.so.0
#16 0x00007f417f992fae in  () at /usr/lib/libgtk-3.so.0
#17 0x00007f417f993c6d in gtk_widget_get_preferred_height_and_baseline_for_width () at /usr/lib/libgtk-3.so.0
#18 0x00007f417fb0a094 in  () at /usr/lib/libgtk-3.so.0
#19 0x00007f417fa5e852 in  () at /usr/lib/libgtk-3.so.0
#20 0x00007f417fa631ac in  () at /usr/lib/libgtk-3.so.0
#21 0x00007f417f36fc96 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#22 0x00007f417f36fe04 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#23 0x00007f417f810f79 in  () at /usr/lib/libgtk-3.so.0
#24 0x00007f417f36fc96 in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#25 0x00007f417f36fe04 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#26 0x00007f417f655850 in  () at /usr/lib/libgdk-3.so.0
#27 0x00007f417f6426b0 in  () at /usr/lib/libgdk-3.so.0
#28 0x00007f417f2576d8 in  () at /usr/lib/libglib-2.0.so.0
#29 0x00007f417f256ee3 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#30 0x00007f417f2ad0f9 in  () at /usr/lib/libglib-2.0.so.0
#31 0x00007f417f254455 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#32 0x00007f417f5266ee in g_application_run () at /usr/lib/libgio-2.0.so.0
#33 0x000055eef828cf55 in waybar::Client::main(int, char**) ()
#34 0x000055eef828be7d in main ()

This is a little over my head (I have zero experience with gtk programming).
The main change I see is the new window icon support. So, I will first move forward and disable that and see if waybar becomes (more) stable:
    "sway/window": {
        "icon": false,
    },

I have been having the same problems on the latest version of waybar (Waybar v0.9.10).
I disabled window icon support as suggested and have had no issues.
(Working 5+ hours without a crash)

Same problem but different "solution".
I'm on Waybar v0.9.9
I did use the default config as a starting point and everything worked perfectly and looked good except for the backlight icons.
OTF icons are installed and displayed correctly for anything else.

Removing the icons from the backlight module "fixed" it for me.
Core dumb:
Core was generated by `waybar -b bar-0'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0  0x00007fc094338ccf in g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[Current thread is 1 (Thread 0x7fc090911ac0 (LWP 28121))]
(gdb) bt
#0  0x00007fc094338ccf in g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fc094338f99 in g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc09433a3fa in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc09433a6e3 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fc0944e39e2 in ?? () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
#5  0x00007fc0944e3bd4 in ?? () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
#6  0x00007fc0944feb40 in Glib::IOSource::dispatch(sigc::slot_base*) () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
#7  0x00007fc0944f7ba7 in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
#8  0x00007fc094331c24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007fc0943866f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007fc09432f3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007fc09460cc85 in g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
#12 0x000056028336f413 in ?? ()
#13 0x000056028336dfdd in main ()

Well, never mind.
Just build from scratch and it is not reproducible anymore.
❯ waybar --version
Waybar v0.9.12-88-gcaee2e6 (branch 'master')


Support features in test cases

Currently all test cases are only built with the default feature set.

I believe this works on Linux but not Windows. src/features.rs probably needs a line to deal with the ".exe" extension.