stdlib - 4.1.0

I ran into an issue with 4.1.0. It appears no one ever updated stdlib here and it was on 4.2.2. With puppet-firewalld 4.1.0 I got the error below
Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Resource type not found: Stdlib::Ensure
::Service (file: /XXXXX/firewalld/manifests/init.pp, line: 36, column: 3)
Once I updated stdlib to the latest (6.1.0) it all ran fine.
Would it be possible to add a version check in puppet-firewalld or on the main page put the minimum stdlib required version?

The version requirement in the metadata.json looks correct to me.  That gets used on the puppet forge.
Maintaining it in the README as well isn't practical IMO.

Stdlib 4.2.2 is actually already over 5 years old.  I'm very surprised you were able to run such an old version without any other issues for so long.

I see it now. My bad

No worries.  Thanks for the interest.  We're always interested in PRs to improve docs.


Fix service connector creation in full stack endpoint

Describe changes
The dict.update(...) method returns None and was used incorrectly which means the service connector request was invalid due to a None config.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

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

Incorporated into https://github.com/zenml-io/zenml/pull/2887


[AMQ-9515] Redact JMSText in the HTTP params

As pointed out in https://issues.apache.org/jira/browse/AMQ-9515 message body is sensitive data and sending a text message using the web console shouldn't log the message content in the audit log.

I'm mostly -1 on this change.
I think this should be handled by configuring a filter at the logging framework level.
Some users may want body redacted, others certain header or properties fields.. or even just specific fields within the body.
Logging frameworks support configurable filters for this, I think this can be handled as a FAQ in ActiveMQ about how to add a logging filter.

I'm mostly -1 on this change.
I think this should be handled by configuring a filter at the logging framework level.
Some users may want body redacted, others certain header or properties fields.. or even just specific fields within the body.
Logging frameworks support configurable filters for this, I think this can be handled as a FAQ in ActiveMQ about how to add a logging filter.

Hi Matt, thanks for the feedback.
That's a good idea. Let me look into it today. Instead of making this change, we will ship a default configuration for audit log to mask that information and add a FAQ in ActiveMQ to instruct users on how to add their own or override the default. Does it sound good to you?

we will ship a default configuration for audit log ..

If by 'we' you mean your organization, good to go =)
If by 'we' you mean Apache, then I don't see us changing the default Apache distribution config for this.

we will ship a default configuration for audit log ..

If by 'we' you mean your organization, good to go =)
If by 'we' you mean Apache, then I don't see us changing the default Apache distribution config for this.

I can see your concern. By "we" I meant developers in this community :) When developers deploy ActiveMQ for their customers, their customers may want sensitive data to be redacted. For instance, in AuditLogEntry.java fields that are annotated by @Sensitive (such as password) are redacted in the audit.log. So in my opinion, it is probably better to have it default redacted (possibly other fields in the HTTP parameters as well) to avoid potential compliance issues. I will focus on documenting the instructions to configure the log filter nevertheless.


:bird: Please Tweet about v0.28.1 :pray:

So I can RT it when https://github.com/adriens/chocolatey-vendir/issues/19 is :ok:

@microwavables

:pray: :gift_heart: :rocket: :people_holding_hands:


Minor changes based on testing

Also changed the default quick bar, so it aligns with what I think most runs would see the most.

It looks fine


Dockerfile documentation on EXPOSE confusing

The Dockerfile documentation about the EXPOSE directive states it is used "to determine which ports to expose to the host when using the -P flag."
Then, it goes on to say:
"Note: EXPOSE doesn’t define which ports can be exposed to the host or make ports accessible from the host by default."
It seems to me the first statement is wrong and should be removed, because AFAIK EXPOSE does not determine which ports to expose to the host.  If I'm wrong about that, than the documentation should be updated with clarification.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Feel free to update, docs are located in this repo at /docs

#dibs

Nice work, thank you
On Tue, Oct 13, 2015 at 1:35 PM, moxiegirl<EMAIL_ADDRESS>wrote:

Closed #16634 https://github.com/docker/docker/issues/16634 via #16965
https://github.com/docker/docker/pull/16965.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16634#event-434367254.

--
Sincerely,
Colton Leekley-Winslow
651-242-9559
<EMAIL_ADDRESS>


Random starting points Using Strava data

Hi and thanks for making this tool available
I'm using Strava data with the latest version (v0.2.1)
About 98% of my runs start at home. However, the first frame of my .gif has the runs starting all over the route. See the attached pic for the first frame. On this pic you are able to make out the routes, so it is the timing or something that must be out. My expectation is that all the bright dots should start at the same place for the first frame. Any ideas?

How peculiar! Would you be willing to share your data with me somehow?

Yes, no problem. How should I send it to you?
On Fri, 18 Mar 2022, 04:49 Nathan Baulch, @.***> wrote:

How peculiar! Would you be willing to share your data with me somehow?
—
Reply to this email directly, view it on GitHub
https://github.com/NathanBaulch/rainbow-roads/issues/9#issuecomment-1071974359,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQQIEF5456LC4TVMBIFDICDVAPVLLANCNFSM5Q3KBZBQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Probably easiest if you send me a shared file link (Dropbox, GDrive, OneDrive, iCloud, etc) via Reddit DM. Alternatively you can email it to my username at gmail dot com.

Thanks. Just sent you a link on Reddit
On Fri, Mar 18, 2022 at 11:09 AM Nathan Baulch @.***>
wrote:

Probably easiest if you send me a shared file link (Dropbox, GDrive,
OneDrive, iCloud, etc) via Reddit DM. Alternatively you can email it to my
username at gmail dot com.
—
Reply to this email directly, view it on GitHub
https://github.com/NathanBaulch/rainbow-roads/issues/9#issuecomment-1072216435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQQIEF7UMMSOYUVGQJTF5ZDVARB6BANCNFSM5Q3KBZBQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Fixed. This is the first time I've seen laps used in TCX files so all your 1km segments were being animated in parallel. These are now stitched together as you'd expect.
I've just released v0.2.1 with this fix, thanks!

It works now. Thanks!!!


.matches method always send to OnDefault

Hi, I've got the feeling that I can't make the .matches method work well.
I have something like :
helloBot.add('/', new builder.CommandDialog()
    // .matches('^set name', builder.DialogAction.send('Hi !'))
    .matches('^name', function(session, results) {
        console.log("I'm in.");
        if (results && results.response) {
            session.send(results.response);
        } else {
            session.beginDialog('/profile');
        }
    })
    // .matches('^quit', builder.DialogAction.endDialog())
    // .matches('^what is the best IDE', builder.DialogAction.beginDialog('/sourcelair'))
    .onDefault([
        function (session, args, next) {
            console.log("In the default");
            if (!session.userData.name) {
                session.beginDialog('/profile');
            } else {
                session.endDialog("Je n'ai pas compris :/");
            }
        },
        function (session, results) {
            session.send('Hello %s!', session.userData.name);
        }
    ]));

I don't know if the problem is from my .matches method or the cycle of beginDialog / endDialog.
Thank you !

Maybe, it would be great, if you could describe your issue a little bit more? It would be great if you could upload your example output of what happens when you enter your desired input and what the expected output is.
Can you also check if this problem, that I described here #532 is the same as yours? If, so we should link it.

I'm sorry, that's just my bad, I'm making a bot in French and I had not to check the translate checkbox on the Microsoft website.
Thanks for your answer anyway.


Small corrections/clarifications in docs

peerjs not used anymore, and main readme details

ah and can we rename the wikitext task to gpt? (task is typically more informative. dataset often underspecified what's being done)


Ported some features over from 2020.3

Itemstacks:

Added support for itemstack variables
Added support for itemstack size procedure blocks
Added support for "Is item enchanted" and "Is item enchantable" procedure blocks
Itemstack procedure blocks should now work with custom dependencies

Entities:

Added support for "Get ridden entity" procedure block
Entity procedure blocks now work with custom dependencies

Other:

Added support for "Block offset type" and "AI path node type" for blocks and plants
Added support for "Get light level" and "Get block hardness" procedure blocks

Thank you for this contribution.
Reviewed & merging into master.


Redesign a index.html

i want to redesign the index.html and other pages too ...

Yes You can do it, once done please attach your screenshot and please join the onboarding group
Developers needs to onboard to opensource community for easy information flow along with admins, please join with this link  Curious Developers Community - Hacktoberfest
Standrad Website Design reference
1. https://dart-tutorial.com/
2. https://www.w3schools.com/html/
3. https://www.studytonight.com/html5-references/html-a-tag

Yes You can do it, once done please attach your screenshot and please join the onboarding group
Developers needs to onboard to opensource community for easy information flow along with admins, please join with this link Curious Developers Community - Hacktoberfest
Standrad Website Design reference 1. https://dart-tutorial.com/ 2. https://www.w3schools.com/html/ 3. https://www.studytonight.com/html5-references/html-a-tag

sure 👍

i think we need to move on javaScript framework?  (reactJs)

Yes
Thank You
Instructions

Yes you can start working on it by taking latest pull from main branch
Don't Forget to join onboarding group for knowledge flow and direct conversation and support from other developers link  Curious Developers Community - Hacktoberfest
Please attach the screenshots and video of the development work once it is done
Contributions more than 3 will be awarded a certificate of appreciation from curious ecosystem please mail to<EMAIL_ADDRESS>for claiming certificate and please attach your issue number
Respect Co Developers And Please Reach out to admins if any issues

Thanks & Regards
The Curious Team


Flashblocks BlockBuildingAlgorithm

A new BlockBuildingAlgorithm implementation is required for Flashblocks.
The idea is a timing config can be specified with the millis since last block it should "checkpoint". Checkpointing means to cache the orders at that point in time, and always use those orders as the head of the block when suggesting future blocks.
e.g. timings set to [250, 500, 750, 950] should result in:

While building block N

Between 0 - 250ms since block N-1, build_blocks produces and returns empty blocks
The first build_blocks call 250 - 500ms since block N-1 produces, caches, and returns f1 (Flashblock 1) using the existing simple gas price ordering algorithm.
Subsequent build_blocks calls 250 - 500ms since block N-1 returns f1.
The first build_blocks call 500 - 750ms since block N-1 produces, caches, and returns f2 (Flashblock 2) using the existing simple gas price ordering algorithm.
Subsequent build_blocks calls 500 - 750ms since block N-1 returns f2.
The first build_blocks call 750 - 900ms since block N-1 produces, caches, and returns f3 (Flashblock 3) using the existing simple gas price ordering algorithm.
Subsequent build_blocks calls 750 - 950ms since block N-1 returns f3.
The first build_blocks call 900 - ∞ms since block N-1 produces, caches, and returns f4 (Flashblock 4) using the existing simple gas price ordering algorithm.
Subsequent build_blocks calls 950 - ∞ms since block N-1 returns f4.

Notes

It should probably be a wrapper around an existing BlockBuildingAlgorithm implementation, like one that simply orders by gas price.
Flexible Flashblock counts and intervals per block

Hi had some questions about these steps, wanted to give some scenarios and clarify my undestanding.

Between 0 - 250ms since block N-1, build_blocks produces and returns empty blocks

So the very first time build_blocks is called will fall into this bucket?
Also does returns empty blocks refer to build_block, which returns Result<Box<dyn BlockBuildingHelper>>, instead of build_blocks, which has no return value?  Is the intention to eventually call input.sink.new_block?

The first build_blocks call 250 - 500ms since block N-1 produces, caches, and returns f1 (Flashblock 1) using the existing simple gas price ordering algorithm.

Say another call to build_blocks happens at 251 ms, so it falls into this bucket. We can call OrderingBuildingAlgorithm::build_blocks, which will end up calling input.sink.new_block?  We cache f1 by caching the BlockBuildingHelperFromProvider that was created.

Subsequent build_blocks calls 250 - 500ms since block N-1 returns f1.

Another call to build_blocks happens at 252 ms, so it falls into this bucket. It saves these SimulatedOrders for later. Not sure how to return f1 as noted earlier.

The first build_blocks call 500 - 750ms since block N-1 produces, caches, and returns f2 (Flashblock 2) using the existing simple gas price ordering algorithm.

Another call to build_blocks happens at 501 ms, so it falls into this bucket.  We add SimulatedOrders from the prior build_blocks call at 252ms to this current call's SimulatedOrders, and call OrderingBuildingAlgorithm::build_blocks.

Subsequent build_blocks calls 500 - 750ms since block N-1 returns f2.

Another call to build_blocks happens at 502 ms, so it falls into this bucket. It saves these SimulatedOrders for later. What happens if this is the last call to build_blocks, are these SimulatedOrders never submitted? Or are we guanteed a final build_blocks call post 950ms?
Thanks!


I am looking for a Stronger jsonPatch apply lib

usefor Kubernetes Dynamic Admission Controller
package main

import (
	"encoding/json"
	"fmt"

	jsonpatch "github.com/xxxx/json-patch"
	corev1 "k8s.io/api/core/v1"

)

func main()  {

	var pod = corev1.Pod{
		Spec:       corev1.PodSpec{
			Volumes: []corev1.Volume{
				{
					Name: "default-token-lsh6v",
					VolumeSource: corev1.VolumeSource{
						Secret: &corev1.SecretVolumeSource{
							SecretName: "default-token-lsh6v",
						},
					},
				},
			},

		},
	}

	podBytes, _ := json.Marshal(&pod)

	fmt.Printf("old document: %s\n", podBytes)

	patchJSON := []byte(`[
   {
      "op":"add",
      "path":"/spec",
      "value":{
         "dnsConfig":{
            "options":[
               {
                  "name":"single-request-reopen"
               }
            ]
         }
      }
   },
   {
      "op":"add",
      "path":"/spec/volumes/-",
      "value":{
         "name":"default-token-lsh6v1111",
         "secret":{
            "secretName":"default-token-lsh6v1111"
         }
      }
   }
]`)
	patch, err := jsonpatch.DecodePatch(patchJSON)
	if err != nil {
		panic(err)
	}
	modified, err := patch.Apply(podBytes)
	if err != nil {
		panic(err)
	}
	fmt.Printf("Modified document: %s\n", modified)

}

expect result json is:
{
   "metadata":{
      "creationTimestamp":null
   },
   "spec":{
      "dnsConfig":{
         "options":[
            {
               "name":"single-request-reopen"
            }
         ]
      },
      "containers":null,
      "volumes":[
         {
            "name":"default-token-lsh6v",
            "secret":{
               "secretName":"default-token-lsh6v"
            }
         },
         {
            "name":"default-token-lsh6v1111",
            "secret":{
               "secretName":"default-token-lsh6v1111"
            }
         }
      ]
   }
}

also, I expect:
   {
      "op":"append",
      "path":"/spec/containers/*/env",
      "value":{
         "name":"KEY",
         "value": "VALUE"
      }
   }

this will append a env to all containers ,not override

This package is for generating JSON Patches, not applying them, so I'm not sure what's your question. Moreover, the append OP isn't specified by the JSON Patch RFC, you should use an add operation with a path like /path/to/element/- to append a the end of an array.

the first op add will add a dnsConfig to override spec.

Sorry, is this related to this package ? I still can't tell from your question. Are you generating a patch with jsondiff ?

patch:
[
   {
      "op":"add",
      "path":"/bar",
      "value":{
         "test111111111":{
            "a":1,
            "b":2
         }
      }
   }
]

data:
{
  "bar" : {
    "test": 1
    }
}

result:
{
  "bar" : {
    "test111111111" : {
      "a" : 1,
      "b" : 2
    }
  }
}

I expect there has a stronger JsonPatch lib to get this result:
{
  "bar" : {
    "test": 1,
    "test111111111" : {
      "a" : 1,
      "b" : 2
    }
  }
}

Assuming that there is a super jsonPatch language, we can use it to change the json of the pod, and then use jsonDiff to generate a regular jsonPatch. The user only needs to write this super jsonPatch to change the properties of the pod in the access control of the pod.

Your patch is valid, see https://tools.ietf.org/html/rfc6902#section-4.1

If the target location specifies an object member that does exist, that member's value is replaced.

I still don't get what the link between your issue and this package.

I know this, I mean you can construct a middle-layer jsonPatch, and finally generate a standard jsonPatch

I still don't get what is your point. Are you reporting an issue with the package, or proposing a feature ? You are talking about a "super jsonPatch", but that seems hypothetical to me, there's no such thing that I'm aware of. This package follows the JSON Patch RFC.
Please provide a full explanation of what your trying to achieve, and why, so I can understand what we're talking about, otherwise I won't be able to provide a constructive answer.
Thanks


Create bioinformatics workflow

Create example workflow, e.g. assembly of covid data or variants calling.

Changed plan after discussion. Focus on one step/script example.


Using terraform workspace does not work as expected

Report from a user about bugs using Workspace: https://github.com/pwillis-els/terraformsh/issues/10

it seems terraformsh don't use workspaces and there is no way I found applicable to do the execution against some workspace
See in screenshot how it has ignore that we are in different workspace and tried to alter the current state of default workspace instead of use the current space?

@AMKamel I'm not sure what's going on here, I haven't used workspaces with the tool yet.
One thing to try would be to set environment variable TF_DATA_DIR to one directory, like:
export TF_DATA_DIR=".terraform"

This mimics the default behavior of Terraform to re-use the same local state directory for your Terraform runs.
You can also use the new option in the unreleased version of terraformsh, which does something similar, in that it doesn't delete the temporary TF_DATA_DIR that terraformsh creates and destroys on each run

Isn't using TF_DATA_DIR to something like /tmp/xyz.com.terraform.d that I have to take care or this dir as long as I want to keep track of the state, if so this is very hard as I am using terraform in automation and using a postgresql backend with spaces is safer, right?

A postgres backend with spaces I would think is safer, yes.
The temporary TF_DATA_DIR directory terraformsh creates (and destroys) is intended to draw attention to the fact that Terraform keeps local state (even if you're using a remote state backend like S3). A lot of users don't realize how much of using Terraform depends on this local state, which then causes problems when they use it in automation and it doesn't work the way it did on their laptop.
Basically, if you use Terraform the way it comes by default, there will be these .terraform directories littering your root modules, and if you try to use the same root module directory to apply Terraform to different environments, or with different configuration, you can end up "stepping on" the old .terraform directory from a previous run. I added some commands like terraformsh clean to try to work around that issue, but it just got so annoying that I added the automatic temp TF_DATA_DIR as a workaround. So probably this is what's causing the issue with your terraformsh workspaces commands.
I'm sorry I haven't gotten a chance to test workspaces out yet, hopefully this weekend I can take a look at it. Can you tell me more about your use of postgres backend with spaces?
Thanks

@AMKamel I've started working on some tests for postgres state backend, as well as some command-line parsing fixes, and I think I understand the issue better now.
So, it looks like what Terraform is trying to do with the workspace command is to keep both remote state and local state. Your backend state may be Postgres, but which workspace you're actively using is only stored in local state (which I guess makes sense). But since Terraformsh is creating and destroying local state each run, you lose which workspace is selected locally.
The previous way to solve this problem in Terraformsh 0.11 or earlier would be to set TF_DATA_DIR=.terraform, and then Terraformsh won't mess with it. The next way to solve it is with the code I committed a few weeks ago, where the  -n option also prevents destroying the temporary TF_DATA_DIR.
I've just pushed some new code which changes how command-line parsing works for Terraformsh. Now you can do this:
terraformsh workspace select abukamel.something plan

With dry-run mode, we can see it runs these commands:
+ terraform init -input=false -reconfigure -force-copy
+ terraform workspace select abukamel.something
+ terraform init -input=false -reconfigure -force-copy
+ terraform get -update=true
+ terraform validate
+ terraform plan -input=false -out=/home/psypete/git/PUBLIC/terraformsh/tests/foo/tf.a646d79d63.plan

Luckily running 'terraform init' twice is fine (in my testing, anyway). But if you wanted to avoid that, you can use the -D option to only run commands you specify on the command line, like this:
$ terraformsh -N -D init workspace select abukamel.something plan
+ terraform init -input=false -reconfigure -force-copy
+ terraform workspace select abukamel.something
+ terraform plan -input=false -out=/home/psypete/git/PUBLIC/terraformsh/tests/foo/tf.a646d79d63.plan

So, based on these options, will one of these methods work for you?

Great, thanks, to resolve the issues I was having I tried to reuse the commands outputs from terraformsh using python, I do use postgresql as a backend to creating terraform cloud workspaces, so pgsql is holding the state for terraform cloud workspace, and terraform cloud workspace which is the remote backend is holding the state for infrastructure code.
So when destroying, I destroy the state at terraform cloud workspace first then destroy the state at pgsql backend workspace which will delete the terraform cloud (now empty) workspace, then finally delete the pqsql workspace used as backend to terraform cloud workspace itself.
Snippet creating pgsql workspace
        shutil.copytree(f"{terraform_code_dir}/", f"{config_dir_location}/")
        zx.run_shell_print(
            f"cd {config_dir_location} && \
            terraform init -input=false -reconfigure -force-copy -backend-config {backend_config_file_location}")
        try:
            zx.run_shell_print(
                f"cd {config_dir_location} && \
                terraform workspace select {fqdn}")
        except:
            zx.run_shell_print(
                f"cd {config_dir_location} && \
                terraform workspace new {fqdn}")

        plan_file_location = f"{config_dir_location}/config.plan"

        if deployment_action == "apply":
            zx.run_shell_print(
                f"cd {config_dir_location} && \
                terraform plan -out {plan_file_location} -input=false -var-file {vars_file_location} && \
                terraform apply -input=false -auto-approve {plan_file_location}")
        elif deployment_action == "destroy":
            zx.run_shell_print(
                f"cd {config_dir_location} && \
                terraform plan -destroy -out {plan_file_location} -input=false -var-file {vars_file_location} && \
                terraform apply -input=false -auto-approve {plan_file_location} && \
                terraform workspace select default && \
                terraform workspace delete {fqdn}")

snippet creating infrastructure using terraform cloud
        os.environ["TF_REGISTRY_DISCOVERY_RETRY"] = "10"
        os.environ["TF_REGISTRY_CLIENT_TIMEOUT"] = "60"
        os.environ["TF_IN_AUTOMATION"] = "true"

        shutil.copytree(f"{terraform_code_dir}/", f"{config_dir_location}/")
        zx.run_shell_print(
            f"cd {config_dir_location} && \
            terraform init -input=false -reconfigure -force-copy \
            -backend-config {backend_config_file_location}"
        )
        if deployment_action == "apply":
            zx.run_shell_print(f"cd {config_dir_location} && \
            terraform apply -input=false -auto-approve")
        elif deployment_action == "destroy":
            zx.run_shell_print(f"cd {config_dir_location} && \
            terraform destroy -input=false -auto-approve")


IOSQE_IO_LINK - ECANCELED

For IOSQE_IO_LINK I don't get why "eg, a short read will also terminate the remainder of the chain." couldn't sqe.res just return the length read? even if its shorter then buffer specified, just like normal io_uring_prep_read*, why must this be an error?

Because if, for instance, you have "read(buf, N bytes) -> send(buf, N)",
and it's a short read, you'll be surprised sending garbage data. And that
garbage may even be confidential information.

It could be more less:
read(buf, ...)
send(buf[0:sqe.res])

Right, but not for IOSQE_IO_LINK, because linked requests are set upfront before you know cqe.res.

That is a good point, hmm... so there is no accountability internally to know how much was read before sending, eh...

Another concern i had was say if you are linking:

read(buf, 1024)
send(buf, 1024)

is the send guaranteed to send 1024 bytes? what if it only sends 512 bytes? socket send can fluctuate right.

Doesn't matter, since it's end of the chain. So you get to deal with it in the app, exactly how you would a standalone send/write/whatever that's short.

By that logic if i read(buff, 1024) and it reads 512 bytes it will raise ECANCELED at the same time if i send(buff, 1024) and it sends 512 bytes it doesn't raise ECANCELED? this isn't consistent.

Your example had read  send, so if the read is short, it fails dependent links - which is the send. The send doesn't have anything linked after it, so nothing to cancel. This is fully consistent with how links work. If you swapped the order of them, then a short send would of course cancel the read.

What would the short send cancel? Nothing. So the status of that is reported as expected.

If you swapped the order of them, then a short send would of course cancel the read.

ok, this is good to know... so pretty much any task that doesn't do exactly as specified will ECANCELED under IOSQE_IO_LINK.
Say if you link and submit 5 sqe using IOSQE_IO_LINK flag, is it guaranteed to return one after another when you io_uring_wait_cqe_nr(ring, cqes, 5) just as submitted? Since you "linked" it, can we asssume it return cqes in same order?
Its actually good to know such small details.

This isn't small details, this is the basic understanding of how links work. It is fully documented.


Upload of .csv file results in "experiment run fail" with Decimal symbol is set to ","

Upload of .csv file results in "experiment run fail" if windows symstem Decimal symbol is set to "," while the numbers in the .csv file is written with "."
It may be more specific than this, but it appears that not all numbers are interpreted as numbers even if the .csv file only contains number with "." decimal symbol.

The behaviour originated from a value in the input data that was not within the parameter space defined in the parameter table.
It could be very useful to have more clear error handling in the front-end. A good first step would be to pass on the error statement from the backend

Agreed - tracked in issue #122


Rename satisfaction score in CSV

What
Renamed satisfaction score to users who found page useful in CSV file.
Why
To better reflect the metric.

Review Checklist

[x] Changes in scope.
[x] Added/updated unit tests.
[x] Added/updated feature tests.
[x] Added/updated relevant documentation.
[ ] Added to Trello card.

 (3) Pain point - Rename 'user satisfaction score' metric in the frontend interface


QPS range bugfix

Re-apply the bugfix since it was undone in the previous commit.

sorry about that


Remove tinyint type

PostgreSQL don't support tinyint type.
Tinyint type in Accio came from Trino, we can remove it.

legacy issue.


SFTP connection not closed after upload

SFTP connections don't appear to be closed after uploading a file.
After a day's work, there are tons of sftp processes active on the server.

Hi guys,
Sorry for the long period of inactivity.
We are currently working on a new version : better code, more stable, and bug fixes.
This bug will be fixed at the next release.
Thank you for using our work ! :)

Hi guys,
A new version (1.0.0) was published tonight.
Feel free to reopen if the problem is still there.
Enjoy ! :D


Update to Laravel 5.6

- Installation request for barryvdh/laravel-cors ^0.9.2 -> satisfiable by barryvdh/laravel-cors[v0.9.2, v0.9.3].

Try this:
composer require barryvdh/laravel-cors
This will install latest version..
And run update again. After that, it should work.
Answer can be found from closed issue #286

I think this issue can be closed @barryvdh?


Encoders in arm don't work

The encoders weren't working as we wanted it to.

We used the RUN_TO_POSITION method to make the arm stay at the specified location for however long needed. We just found the target using telemetry and we set the motor to run till that spot.


Disable require branches to be up-to-date

As development under Kvrocks grows rapidly, it causes unnecessary reruns for patches due to we require branches to be up to date before merging.
We can disable the option and let the committers decide whether we should merge base branch before accepting the patch.
See also this discussion on general@: https://lists.apache.org/thread/w1tvjxzooyrjso80hdd7y04n2q6k7mxl
Signed-off-by: tison<EMAIL_ADDRESS>

@PragmaTwice we still run tests at least in latest commit so I don't think we should over optimize CI workflow. Another perspective is we may run kvrocks.yaml with a schedule trigger also.


it's time to rename the repo to azure-cosmosdb-rxjava

Because we had renamed documentDB to cosmosDB - it will be right if we will update the repo name as well.

Thanks for your comment. This repo provides a SDK for documentdb API aspect of cosmosdb. So "azure-documentdb-rxjava" is the correct name.


Feature Review: Fully automatic component dialogs

Required Information

[x] AEM Version, including Service Packs, Cumulative Fix Packs, etc: 6.4+

Feature Brief
Building on the synthetic form generation in MCP, expand to let developers create component dialogs using just the sling models.  Basically, no more need to hand-edit cq:dialog nodes.
How this would work

This requires the introduction of an OSGi service factory, DialogResourceProviderFactory, which binds to all declared sling models (via AdapterFactory registered instances.)  If an adapter factory is an exported class and is a subclass of GeneratedDialog, then it is considered a candidate for this feature.
Candidate sling models are then inspected for their provided resource type.  This can be provided in the class-level annotation which is part of sling models.   This can also be provided in a getter method or field annotated accordingly as the resource type.
The resource type is then pre-pended with "/apps/" and appended with "cq:dialog" to construct the target path of the resource provider root location.   A resource provider service is constructed and registered at runtime with this location, such that any requests to this resource are relative to the generated synthetic form resource.
An additional optional feature is to disable sling merger behaviors so that there are no additional form elements (to be decided on later) -- this is likely not a big deal for components but if using this feature on pages it will be necessary to prevent additional garbage from showing in the generated form.
The result is that a developer only need create a sling model with proper annotations and the dialog is then always correct and always relevant to the model.  There is no need to update a secondary location every time the component needs to be updated or revised.

@klcodanr, @HitmanInWis , @davidjgonzalez  this is the not-yet-added feature I was describing in the other recent PR's.  Those PR's do not include this feature but do support its eventual addition, but those PRs mostly just fix current bugs which would otherwise impede the success of a feature such as this.

Sounds good and definitely something we should add. Might not solve all issues with generating dialogs, but for the majority of the simple component dialogs it's probably sufficient.
Some questions:

you register a ResourceProvider for each of these models? Have you already tested if this has an performance impact on general resource lookup? Or would it be possible to register a single ResourceProvider to handle all of these models?
You use the @inject annotation to inject the properties from the Resource's ValueMap, but there are other ways to get them as well (e.g. @ValueMapValue), can you handle them as well?
What about Models which use other means than the Resource to get data from?

I think that this is a nice way to help reduce the boilerplate, but we should provide good documentation and include its limits.

@badvision is the intent to use this API in building-out custom AEM Components and replace (via auto-generation) dialogs defined via JCR nodes?
If so, does this have feature parity with the JCR node definition approach? How does this play with extending Core Components?
We shouldn't be replacing supported-by-Adobe AEM development best practices; this smells like it might be doing that? is it?

I love this idea, creating dialogs (and especially touch UI dialogs) is tedious and unfun.

So my concern is similar to @davidjgonzalez . While I think this is a problem that would be great to solve, providing another way to programmatically generating a dialog seems to be fraught with maintenance and upgrade issues.
IMO -- it would be cleaner to support the generation of the dialogs "offline" e.g. either through some sort of dialog builder or dialog / resource DSL which makes the process less "unfun"

Core components still work the same way they always work, this is really more for things like custom components that require a tedious amount of custom dialog generation.  I'm not trying to replace what the product is doing.  I'm actually just trying to do something better and more efficient.

I also love this idea, as dialog coding is super tedious and error prone.  However, I agree the more effective and flexible approach may instead be a way to generate the code offline to be put into a codebase, and then deploy to AEM.  This opens up opportunity for generating the simple 80% of a complex component, allowing the last 20% to be hand-baked, while also supporting 100% generation for simple components.  Supporting things like configs to extend an existing WCM Core component using the proxy extension method would be easy add-ons.
Bounteous is going to be open sourcing in the next day or so a generator we've built over the past month to do just this.  It takes in a JSON file of attributes and kicks out:

Full _cq_dialog, dialogshared, and dialogglobal dialogs (the latter two being for Shared Component Props)

Supports all basic field types
Supports image fields
Supports multifields

Clientlib at the correct /site folder path under the component
HTL file that pulls in the sling model and also displays the default WCM Core template if component is not configured
Fully coded sling model java classes (interface and impl)

One key difference in approach (which means both @badvision and Bounteous' approach may actually both be valid) is that Bounteous' approach supports a Front End Dev-first/only mentality, which has been a real challenge since the introduction of sling models.  @badvision's approach on the other hand can be valid for Back End-only Dev, where coding of sling models is a natural starting point.

Doesn't this design assume a 1:1 mapping between a Sling Model and a Component's Dialog?

Only for the things which you put a form field annotation on.   It's entirely possible to have other things in your sling model which are not present or visible in a form.

This approach is incremental, building on stuff that MCP was already doing basically.  The feature itself is just for the resource provider.  The hard part of generating dialogs is already in ACS Commons.

I'm on the side of: if we're got to generate a dialog, then it as part the build cycle is the appropriate approach.
Unless/until the Product team has stated that synthetic dialog generation is a supported feature/design paradigm, we should stick to what is supported. To me this means - repository nodes defining the structure.
Who knows what upgrade challenges this approach may lead to down the road.

Ok so let's break this down a little more: This is actually better than what the product does today.  Why?  Because it still uses only the supported granite components, just like your dialogs do, however if the product changes how those work then only this generator has to change.  Whereas if the product changes what components are allowed or how dialogs are structured, then you have to go rewrite all your dialogs by hand.  In this sense, my approach is far safer and is easier to update or future-proof.

however if the product changes how those work then only this generator has to change < this would also be true if it was a build-time generation, and not run-time.

@joerghoh the @inject stuff is because it's a sling model, not required for form generation.  It is, however, required for another framework feature that I'm not going to introduce into ACS Commons, but rather donate to Sling (if they'll have it) for JCR Transparent Persistence.

however if the product changes how those work then only this generator has to change < this would also be true if it was a build-time generation, and not run-time.

Have you been on an upgrade project that required recompiling code and what seemed it would be a simple 5-minute developer task?  Trust me, no, don't write things that require that.  It becomes an upgrade barrier, even if it seems like it shouldn't.

however if the product changes how those work then only this generator has to change < this would also be true if it was a build-time generation, and not run-time.

Have you been on an upgrade project that required recompiling code and what seemed it would be a simple 5-minute developer task? Trust me, no, don't write things that require that. It becomes an upgrade barrier, even if it seems like it shouldn't.

I don't see how this would be different - if build-time generation is a ridiculously costly upgrade task, then run-time generation is just as costly. The changes that need to be made would be the same LoE.
Run-Time (this) would require 2x effort to maintain for upgrade purposes - as when an update occurs, in this library, we would be required to maintain both versions of logic until we choose to deprecate and remove. A non-trivial amount of work, as when this library drops support for each legacy version of AEM.
Build-time generation is safer for upgrading because when I run a build, i can pick which version of the plugin/tool i want to use. This will directly target my AEM product version. The compatibility would be built into the release cycle. 1.x = AEM 6.x, 1.y=AEM6.y. When a new release for new AEM would be needed, you simply drop support for the prev version. The library only contains the support needed for the targeted platform, not every version of the product.

I can make the runtime aware of the installed product version and switch generators if needed.  Fortunately we're only worried about the current version of granite components.  Provided those don't change their interface (I'm basing all this on the public documentation for granite components) it should be pretty safe.  I'm going to disagree with you though, running a maven build might be simple enough for you or for me.  But there are times where administrator types try to do things like "no-touch" upgrades and anything requiring setting up maven blows the time estimates out of the water.  I'm trying to go for lowest common denominator and setting the stage for seamless updates to this stuff to avoid that kind of problem.  For example, if an admin installs a new version of ACS Commons in an upgraded environment in the future, having a custom package including an old version won't result in regressing ACS Commons to an old version.  Therefore, the old packages don't have to be rebuilt for this feature to keep working.

I'm sorry you guys have a preference for a different kind of feature.  Be my guest to write it however you see fit; I don't have time to and honestly I've already written it.  Happy to keep it in my private repo in case someone needs it.

If you do, however decide you would like this feature please feel free to re-open the issue and ping me.

Hey @badvision , did you ever have a look at http://code.digitalatolson.com/cq-component-maven-plugin/ ?

I think that's great, and I can see many places it would be really useful.  Thanks for contributing that to open source!  This dialog generator was more a natural extension of stuff I already wrote as part of MCP, so it was an evolutionary step, and honestly only a hundred or so lines of code.

@badvision I would love to have this feature as part of ACS AEM Commons; and even if there are cases when another approach (e.g. the generation of the dialog as part of the build) is more suitable, there is definitely value to have this on-the-fly generation of dialog structures at hand. I know that there are many Java Backend-Developers who are required to write component dialogs for their components as well, and this tool makes it definitely easier for them.
There is no single "one-size-fits-all" solution here, and if we wait for Adobe product engineering (or even the Core Components team) to approve this approach, we wait forever. I also consider this project as testing platform to see what features are useful and might make it into the product as well.
And: the overhead of having this feature is negligible. If it is turned off by default (which is/should be the default of the most of the features in here), it does not have an impact on performance and stability.
So as a question to all participants in this thread: What speaks against having this here as a pure optional-to-use feature, as all features in ACS AEM Commons are? Next to all the other ways to define and create dialog structures.

It's a three day weekend over here but you will have a feature branch before Monday.  Thanks  @joerghoh !

https://github.com/Adobe-Consulting-Services/acs-aem-commons/tree/feature/Dialog-Resource-Provider
The basic implementation is in the feature branch; still needs the OSGi kill switch and some unit tests.

Agreed with @joerghoh's post 100%.  No harm in having extra tools available, if they work and result in negligible overhead in being present.  Great innovation @badvision.

Thanks @HitmanInWis!  I have updated the service to be disabled by default and enabled via OSGi configuration.  This fits in line with what we do with other opt-in features.  Still needs some unit test coverage but it does work.

ACS Commons is not a framework and does not compete with AEM features (features/frameworks/APIs/etc). In fact, we deprecate our features when AEM introduces their own way to do the job. AFAICT this PR is a framework that directly competes with an established, supported, and more fully-featured approach to achieve the same.
Whether we like AEM's approach is moot. Open-source or not, relying on this framework is unnecessary lock-in, and risk: bugs/incompatibility w/ future versions/lack of feature parity/etc.
The difference between this and other ACS Commons features is: The alternative for other ACS Commons features is to "do it yourself". This alternative to this feature (framework) is to use the Adobe-supported, tried-and-true, fully-featured approach.
Perhaps this is better PR'd into Core Components (also OSS), at merge, it will be supported by Adobe and a viable framework to promote to AEM customers. Being in Core Components, you can actively engage in the work to ensure you don't "wait forever".
Hope this helps explain the concern -- it's a cool idea/innovation!

Core components is a separate concern though, this is more data focused whereas core components deal with actual base component implementation.  I think there could be room for both things, or folks can use this feature where needed.  It's an opt-in solution so it shouldn't mess up or step on other frameworks.

It's an opt-in solution so it shouldn't mess up or step on other frameworks.

ACS Commons is not a framework and does not compete with AEM features (features/frameworks/APIs/etc).

Sorry I'm not familiar with what framework you're suggesting this competes with.

This seems to have bubbled into a more heated discussion than usual and while disagreement can be healthy, it is also important that everyone be respectful. To be honest, I'm not totally following some of the disagreement here, but I'm going to try to summarize what I believe is really happening:

AEM developers need to create dialogs for "regular" components (by "regular" here I mean components which get dropped into a page via the page or template editors).
There are multiple approaches to building dialogs.
None of those approaches are perfect. We're talking about software here, so perfection is really out of the question :)

I hope the above is not particular controversial.
If I understand correctly, what @badvision is proposing here is a method for generating dialogs at runtime. Whether we want to call that a framework or a library or whatever seems unimportant to me.
Personally, I don't think #2 above is a problem. Do I think that the cq-component-maven-plugin or what's being proposed here will always produce the best dialogs? No, I do not. Do I think there is a class of dialogs where you can slap a few annotations on a class and get a reasonable authoring experience? Absolutely.
I see a number of what I think are off-topic issues being raised and I really think this needs to be brought back to the fundamental question... is there a place in ACS AEM Commons for runtime-generated component dialogs? Whether or not such a tool would be universally useful or replace other methods for building dialogs doesn't seem like a factor -- there's plenty in this project which is used in a relatively small minority of use cases. We as a community have never really established guidelines about what should be included and what shouldn't be included, but in general I think the primary factors should be:

Is this something which has practical application in real-world projects? i.e. this project shouldn't contain features which are uninformed by reality.
Is someone (to the best of their ability to agree to these things in the present) willing to participate in the maintenance of the feature?
Is the feature (to the best of the community's knowledge) unlikely to create problems for customers, especially related to product updates?

(And I'll acknowledge that I have personally violated some of this rubric. I'm looking at you Watson speech to text...)
I'm personally too far away from day-to-day AEM development to judge this on the first bullet. But the existence of the cq-component-maven-plugin suggests that there is real-world value to alternate approaches to dialog generation. On the second point, I think the answer is clear. On the third point, it is debatable, but arguably generating the dialogs at runtime is no riskier from an update perspective than doing it by hand (it may be less risky, but that's not important).
I would strongly caution everyone to steer clear from value judgements like "This is actually better than what the product does today." (sorry to pick on you @badvision). This isn't highly subjective and context-dependent. I think it would be more productive to judge features as purely on their merits as possible without contextualizing that judgement based on whether or not something works "better" in a particular workflow.
All of that said, I do have some practical concerns/suggestions:

Given that the direction from Adobe is to push towards extending the core components rather than creating components from scratch, it is not really clear to me how this works in the context where you don't control the base dialog or model class. If the answer is "that's not the use case -- this is for scratch-made components," I think that's an OK limitation, but would be worth calling out. If the answer is "totally works, you have to do XYZ," that's OK too. I'm just missing what the XYZ is.
I don't really love the need to extend a base class. I think this is OK in the context of MCP where the generated dialogs are specific to MCP, but in the "regular component" case, it seems heavy-handed. My default suggestion is "use an annotation" :) but perhaps an interface would be OK as well.
There's no support for design dialogs. Not a big deal IMO (presumably could always be added later), but worth noting in documentation.
One thing that might be nice (but see my comment above about needing 'practical application') is to be able to "export" a dialog definition. This is one thing in the demo I saw a few years ago of the cq-component-maven-plugin which I really liked -- if your needs grew beyond what the plugin could do, you could always take the generated xml, put it in source control and edit.

P.S. https://www.youtube.com/watch?v=rph_1DODXDU

Points well made, @justinedelson!
The interface vs. annotation vs. base class bit is understandable.  Let me see if there's anything in the framework that is actually mandating that or if I can make it smarter.  I don't want every subclass to have to add the same annotation if it's established in a base class, so maybe interface is the way to go.  I'll play with it.
I'm actually not sure if this plays well with core components or not.  I can say that I saw the sling resource merger trying (unsuccessfully) to inject tabs into the resulting markup, which is why I added the ability to pepper the components with disable flags to deactivate sling resource merger.  It might be very much the case that this initial version does not support inheritance/resource merger scenarios until I can find a suitable way to unit test against them.

Ah, I remember why I made it a subclass originally.  Before trying the resource provider route, I was trying to have all models extend a base model that provided dialogs using a more traditional resource inheritance route but it wasn't working too well.  Since the introduction of resource providers, I don't think I need that.

Ok, it was possible to switch to using an annotation OR a base class pretty easily.  Both now work.  The annotation might be useful for providing additional feature flags (such as experimental support for things like sling merging resource provider) in the future.


Keep newlines for better backtrace

Fixes #3

Coverage increased (+0.02%) to 99.3% when pulling 5f7f08a7c46cc95f18faa145e63955b077e154a7 on line-wise into 012757c88e8180386f3d95ea3ae334a3f8915874 on master.


Some adjustments to test new fonts

I only modified the font family names, there were no differences in the result, so you may not need to merge this.

well very strange. i installed git master on a remote server and fonts display perfectly fine on my browser.
it must be an issue with my local pc server side...
i will ignore it for now and stick with master..
thanks

From: Hung Tran<EMAIL_ADDRESS>Sent: Monday, February 27, 2017 6:04 AM
To: nommaz/hgngrav
Cc: Subscribed
Subject: [nommaz/hgngrav] Some adjustments to test new fonts (#3)
I only modified the font family names, there were no differences in the result, so you may not need to merge this.

You can view, comment on, or merge this pull request online at:
https://github.com/nommaz/hgngrav/pull/3
Some adjustments to test new fonts by tranduyhung · Pull Request #3 · nommaz/hgngrav · GitHubhttps://github.com/nommaz/hgngrav/pull/3
github.com
hgngrav - Project for hugin.com.tr
Commit Summary

Some adjustments to test new fonts

File Changes

M user/themes/woo/css/default.csshttps://github.com/nommaz/hgngrav/pull/3/files#diff-0 (42)
M user/themes/woo/css/fonts.csshttps://github.com/nommaz/hgngrav/pull/3/files#diff-1 (32)
M user/themes/woo/css/fonts/Lato/Lato-Black.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-2 (0)
M user/themes/woo/css/fonts/Lato/Lato-BlackItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-3 (0)
M user/themes/woo/css/fonts/Lato/Lato-Bold.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-4 (0)
M user/themes/woo/css/fonts/Lato/Lato-BoldItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-5 (0)
M user/themes/woo/css/fonts/Lato/Lato-Hairline.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-6 (0)
M user/themes/woo/css/fonts/Lato/Lato-HairlineItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-7 (0)
M user/themes/woo/css/fonts/Lato/Lato-Italic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-8 (0)
M user/themes/woo/css/fonts/Lato/Lato-Light.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-9 (0)
M user/themes/woo/css/fonts/Lato/Lato-LightItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-10 (0)
M user/themes/woo/css/fonts/Lato/Lato-Regular.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-11 (0)
M user/themes/woo/css/fonts/Lato/OFL.txthttps://github.com/nommaz/hgngrav/pull/3/files#diff-12 (0)
M user/themes/woo/css/fonts/Roboto/LICENSE.txthttps://github.com/nommaz/hgngrav/pull/3/files#diff-13 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-Black.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-14 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-BlackItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-15 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-Bold.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-16 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-BoldItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-17 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-Italic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-18 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-Light.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-19 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-LightItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-20 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-Medium.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-21 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-MediumItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-22 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-Regular.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-23 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-Thin.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-24 (0)
M user/themes/woo/css/fonts/Roboto/Roboto-ThinItalic.ttfhttps://github.com/nommaz/hgngrav/pull/3/files#diff-25 (0)

Patch Links:

https://github.com/nommaz/hgngrav/pull/3.patch
https://github.com/nommaz/hgngrav/pull/3.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/nommaz/hgngrav/pull/3, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJpdfhMxqI6itHkzIXUVMdzohCiyIuQVks5rgmdagaJpZM4MMual.


Can't takeoff on Nvidia Jetson Xavier NX

Hi,
I'm running my control program on a Nvidia Jetson Xavier NX with Ubuntu 20.04 as OS, to control a Pixhawk4 controller for a quadcopter. I'm running this program on python3.8 and the mavsdk server version is 1.4.13.
To connect the program to the drone I execute the command  sudo ~/.local/lib/python3.8/site-packages/mavsdk/bin/mavsdk_server -p 50051 serial:///dev/ttyACM0 on one terminal, and then run the main program on another terminal.
drone = System(port=50051)
await drone.connect()
print("Waiting for drone to connect...")
async for state in drone.core.connection_state():
    if state.is_connected:
        print(f"-- Connected to drone!")
print('--Arming')
await drone.action.arm()
print('--Taking off')

Just after arming succesfuly,  I execute the instructions to set the target altitude and the takeoff.
await drone.action.set_takeoff_altitude(aTargetAltitude)
await drone.action.takeoff()
await asyncio.sleep(10)

or this way,
await drone.param.set_param_float('MIS_TAKEOFF_ALT',aTargetAltitude)
await drone.action.takeoff()
await asyncio.sleep(10)

But none of this method works to takeoff.
The server terminal gave me this as output for both cases
[09:25:04|Warn ] sending again, retries to do: 3  (MIS_TAKEOFF_ALT). (mavlink_parameters.cpp:1340)
[09:25:04|Warn ] sending again, retries to do: 2  (MIS_TAKEOFF_ALT). (mavlink_parameters.cpp:1340)
[09:25:05|Warn ] sending again, retries to do: 1  (MIS_TAKEOFF_ALT). (mavlink_parameters.cpp:1340)
[09:25:05|Error] Error: Retrying failed get param busy timeout: MIS_TAKEOFF_ALT (mavlink_parameters.cpp:1358)

And the main program shows me this as error of the first method
--Arming
--Taking off
Traceback (most recent call last):
  File "wind_mav_v1.py", line 966, in <module>
    asyncio.run(main())
  File "/usr/lib/python3.8/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "wind_mav_v1.py", line 945, in main
    await arm_and_takeoff(2, drone)
  File "wind_mav_v1.py", line 923, in arm_and_takeoff
    await takeoff(aTargetAltitude, drone)
  File "wind_mav_v1.py", line 898, in takeoff
    await drone.action.set_takeoff_altitude(aTargetAltitude)
  File "/home/t2508/.local/lib/python3.8/site-packages/mavsdk/action.py", line 757, in set_takeoff_altitude
    raise ActionError(result, "set_takeoff_altitude()", altitude)
mavsdk.action.ActionError: PARAMETER_ERROR: 'Parameter Error'; origin: set_takeoff_altitude(); params: (2,)

and this as the second method
--Arming
--Taking off
Traceback (most recent call last):
  File "wind_mav_v1.py", line 966, in <module>
    asyncio.run(main())
  File "/usr/lib/python3.8/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "wind_mav_v1.py", line 945, in main
    await arm_and_takeoff(2, drone)
  File "wind_mav_v1.py", line 923, in arm_and_takeoff
    await takeoff(aTargetAltitude, drone)
  File "wind_mav_v1.py", line 897, in takeoff
    await drone.param.set_param_float('MIS_TAKEOFF_ALT',aTargetAltitude)
  File "/home/t2508/.local/lib/python3.8/site-packages/mavsdk/param.py", line 672, in set_param_float
    raise ParamError(result, "set_param_float()", name, value)
mavsdk.param.ParamError: TIMEOUT: 'Timeout'; origin: set_param_float(); params: ('MIS_TAKEOFF_ALT', 2)

does any body know how to solve this problem?

Are you using PX4 or ArduPilot?

Ardupilot.
I think I'm going to change it to PX4


Remove unused source controller configs

As per title.
Part of #1537

/test reconciler-tests_eventing-kafka-broker_main


I am having issues while playing the FW game as the account type is changed from Active to Owner

Hi Team,
Can you please help me resolve the issue? I had a wax wallet account sohail.gm which was an Active type of user, today morning somehow my app data was not there so I thought of restoring the account using the certificate and mnemonics which end up in creating an Owner type account. Can you guys please help me resolve the issue? How can I restore the active type user and how to get the game started again.
Thanks,
Sohail

Apologies for the late response on this - we don't actively monitor github for user support.
If you need assistance still, feel free to reach out to<EMAIL_ADDRESS>


deps: add secure.py

Uses secure.py to automatically add OWASP suggested security headers to all of our responses.
Something interesting to note is the results of this https://securityheaders.com/?q=itwewina.dev&followRedirects=on
Before secure headers:

After, we should get an "A" rating.

Codecov Report

Merging #526 into master will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #526      +/-   ##
==========================================
+ Coverage   88.82%   88.86%   +0.03%
==========================================
  Files          70       71       +1
  Lines        2613     2622       +9
==========================================
+ Hits         2321     2330       +9
  Misses        292      292

Impacted Files
Coverage Δ

CreeDictionary/securemiddleware.py
100.00% <100.00%> (ø)

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 d73ba0c...5a3f746. Read the comment docs.


How can we show left or right onOpen default in list view? Is it Possible ?

I want show button at least one like above screen.If it is possible how can i show this please make it an example.

you need to customize it, let's say for example :
var swipeoutBtns = [
{
text: Unread,
backgroundColor: '#2E86C1',
underlayColor: 'rgba(0, 0, 0, 1, 0.6)',
onPress:  props.onSend,
component:<View style={{flex:1,alignItems:'center',justifyContent:'center'}}>

<Text style={{color:'white'}}>Unread

}
]
and don't forget to add it to Swipeout :


Chapter 8 of BDA3

I would like to add this chapter to the main repository.
There is one example in this chapter:

Example. Stratified sampling in pre-election polling.

I have used pymc3 to reproduce the results. I must say that there are some problems with the hierarchical model, the figure 8.1 (b) is almost the same, except for a minus sign. After months of redoing that example, I don't know a good solution to that. I also used pystan to reproduce the problems with the hierarchical model, although the idea is to remove that part before merging. If anyone has suggestions (either code or English), I'd like to hear them!

I think I finally understood the hierarchical model, and the results are quite similar. I have to change some visualizations and explain more about the model.


Pointer to unmanaged function pointer in Bindings.

I noticed that in JPH_BroadPhaseQuery_CollideAABox , as opposed to the other similar functions there, we have a pointer type to the unmanaged function pointer:
https://github.com/amerkoleci/JoltPhysicsSharp/blob/bd2c1e2d4571a65779edc7f232a9fe8d79a4e0b2/src/JoltPhysicsSharp/JoltApi.cs#L1380
I think that star isn't supposed to be there? 😛

Hi Alan 👋
Can you submit PR with the fix please?
Thanks dude 😀

Was gonna do this now. Too late 🤦♂


Remove the JSON reserializers (except for AKB)

The AKB serializer is used in the tracelogging pipeline.
Chatted with @zadjii-msft about ganking the deserializers. The form they'll take in the future is probably very different from this.
We'll need to have some better tracking of the source or pass a setting was read during so that we can accurately construct an internal settings attribution model. Diffing was very extremely cool, but we didn't end up needing it.
This apparently drops our binary size by a whopping zero bytes because the optimizer was smarter than us and actually totally deleted it.

probably want

I imagine "each setting knows where it came from" might be more robust than diffing, but.. not sure and no design for that :smile:


Not working with Python 3

@Burnsedia Can you please provide more details on what does not works for you with Python 3 (Idealy PR with the failed TestCase)?
Thanks!

I need a tutorial on how to properly install Django-Classified, Every time I pip install and config all dependencies I get an error message, ps this is my first Django projects. I usually use Flask

I am getting an error with Django.core.exsecptions.Improperlyconfiged. Again this is my first Django project.  I am still learning Web development, coming from a C# Xamerin Native Stack.

Please take a look at the demo project https://github.com/inoks/django-classified-demo


[Issue 607]Validation for column group

1.Measure should not be part of column group
2.No dictionary column should not be part of column group
3.same columname should not be specified two different column group
4.complex dimension should not be part of column group
6.timestamp should not be part of column group
7.Added test cases

retest this please

retest this please

LGTM, Merged to master.


self referencing Parent relation has pagination if type has it

I have a category type:

@strawberry.django.type(models.Category, pagination=True)
class Category:
    id: auto
    name: auto
    slug: auto
    parent: "Category"
    children: List["Category"]

The graphql then adds pagination to the parent relation, which makes no sense, the children it does make sense for.

Describe the Bug

If the type is a single instance it should not have pagination by default.
System Information

Operating system: Mac
Strawberry version (if applicable): 0.176.0

Additional Context

I can fix it like this:

@strawberry.django.type(models.Category, pagination=True)
class Category:
    id: auto
    name: auto
    slug: auto
    parent: "Category" = strawberry.django.field(pagination=False)
    children: List["Category"]

but that shouldn't be needed imho.
Should also note that filters and order are not passed to the parent relation!

I am on 0.9.4 and yes, filters and order are not shown, pagination still is.

@hvdklauw oh, I see. You are probably right.
Do you want to try to open a PR for this? Otherwise I'll try to fix this in the weekend

I'll give it a go

Ok, was writing tests and was wondering if get_pagination should return None for fields like that.

def test_pagination_on_related_field_definition():
    from strawberry_django.fields.field import StrawberryDjangoField

    group_field = StrawberryDjangoField(type_annotation=StrawberryAnnotation(Group))
    assert group_field.get_pagination() is not None
    assert User._type_definition.get_field("group").get_pagination() is None

https://github.com/hvdklauw/strawberry-graphql-django/commit/125789984e2a23c643730c962aa774fd3126532c is what I made of it.
By returning UNSET in get_pagination it automatically won't add the arguments.
The thing is, now I think we also need to do this in filters and ordering to keep it consistent. Also couldn't find tests for those two in relation to not adding filters/order to those kind of fields.

@bellini666 What do you think? should get_pagination (and thus get_filters and get_order) return UNSET when self.is_list is False or should just the arguments function not add arguments in those cases?


Vai API Update koren Pls

Apnar API Expired Hoye gese. MSG send hoy na. Pls Update koren

Need to upgrade api

Need to upgrade api

Use this Tool If U are from BD:
https://github.com/zariradvance/SMS-Bomber-For-BD
I have updated API

thanks a lot bro

Need to upgrade api

Use this Tool If U are from BD:
https://github.com/zariradvance/SMS-Bomber-For-BD
I have updated API

not working bro

on online its running well ..but on my kali machine its showing error when i type '0' before the number

working bro..thanks a lot ...can i connect you with social media?

working bro..thanks a lot ...can i connect you with social media?

Why Not? Choose any Social Media From Here:
https://linktr.ee/zariradvance


[Feature Request]

Context

[X] This issue is not a bug report. (please use a different template for reporting a bug)
[X] This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description
Some language such as java, hcl ... not have format document option in context menu when click right mouse.
Bellow code is also not work
editor.getAction("editor.action.formatDocument").run().then(r => console.log('formatDocument'));
Please support format document feature for java, hcl ... like other languages
Thanks!

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


[BUG] files.slack.com not on the outgoing domains allow list

Writing a NextGen app, and I'm trying to download a file from Slack.  I get the following error when running the custom function:
error: Uncaught (in promise) PermissionDenied: Detected missing network permissions; add the domain to your manifest's `outgoingDomains`. Original message: Requires net access to "files.slack.com", run again with the --allow-net flag

I thought all the slack.com URLs were allowed?
I am using the latest CLI and SDK versions.

Do you see this when running locally and/or remotely post deploy? I have a feeling this is an oversight..

Indeed, locally running functions don't pre-approve files.slack.com - IIUC individual domains including subdomains need to be explicitly approved when running deno. Working on a fix here: https://github.com/slackapi/deno-slack-runtime/pull/66
I believe this will also be an issue once deployed to Slack hosting; we are also working on a fix on that end.

Yes, I just verified both  slack run and  slack deploy get the error.
In addition, I also noticed I need to provide the domain of my workspace...   XXXX.enterprise.slack.com   I would think that should be allowed, but I can understand why it isn't.

It seems initially we didn't want to pre-approve files.slack.com in order to ensure admins can gate access to file uploading features via domain approval, but given that file uploading requires its own specific scope (files:write), I think that's an acceptable path to ensure admins have control over apps with this feature.
Separate topic: @mcsescott what are you building such that you needed to access the X.enterprise.slack.com URL? I wonder if this falls into the same category.

👋 Hi @filmaj  You know I'm always trying to push the boundaries....
Use case:  Because the APIs aren't available to read a Canvas, the workaround we were given by the Canvas PM was to download the file and parse the contents.
I actually have it working now, but have added the domains to my manifest.

And we very much appreciate you boldly going where (clearly) no coded workflows have gone before. 👨🚀 ⭐
Just wanted to verify that the use case was one that would be more widely needed. I think we should consider adding some kind of blanket pre-approval for a bunch of Slack domains, including *.enterprise.slack.com. For example, if you decide to deploy your app to a different workspace with a different workspace URL, womp womp, you need to edit the manifest.
I will bring this up internally and see what we can do.

Hey @mcsescott , FYI if you update your deno-slack-hooks to 1.3.1 (should be referenced in your slack.json) local-running apps now automatically approve files.slack.com. We also just deployed changes to the run-on-slack environment to do the same.

Thank you sir!


How to add Swimm Verify to your Repo?

Link to swimms:
:link: doc: How to add Swimm Verify to your Repo?.

Have any questions? Check out Swimm docs and join our Slack Community.

@edenhermelin seems like a much needed doc, but do look at @noymaor's comments before merging 😄


Add help icon to nodes - Feature request

Add help icon to each node.
The user could access the text documentation of the node.
The node developer add description of the node: inputs, outputs, etc.

When you hover over the node with your mouse the node description should appear as tooltip (they need some improvement, the layouting doesn't work as it's supposed to), shouldn't this be sufficient? Also, in Ryven 3 there will be a collapse/expand node button at this position already


Customizing JWT claims

Currently SimpleJWT does not have a simple way of overriding the default TokenObtainPairSerializer in its app settings. This makes it somewhat difficult to customize the returned claims in dj-rest-auth without overriding LoginView and the jwt_encode function.
I believe a quick fix would be to allow for a new setting in dj-rest-auth, with the default set to 'rest_framework_simplejwt.serializers.TokenObtainPairSerializer':
REST_AUTH_SERIALIZERS = {
    ... ,
    'JWT_TOKEN_OBTAIN_PAIR_SERIALIZER' : 'someapp.serializers.MyTokenObtainPairSerializer',
    ... ,
}

with 'someapp.serializers.MyTokenObtainPairSerializer' defined as in https://django-rest-framework-simplejwt.readthedocs.io/en/latest/customizing_token_claims.html
I think this would then only require the jwt_encode function to be changed as such but I am unsure whether this action is better suited to within app_settings.py:
from app_settings import serializers as appserializers
def jwt_encode(user):
    try:
        from rest_framework_simplejwt.serializers import TokenObtainPairSerializer
        TOPS = import_callable(appserializers.get('JWT_TOKEN_OBTAIN_PAIR_SERIALIZER', TokenObtainPairSerializer))
    except ImportError:
        raise ImportError("rest-framework-simplejwt needs to be installed")

    refresh = TOPS.get_token(user)
    return refresh.access_token, refresh

Sounds reasonable to me. Pull requests are welcome 👍

This was merged. Closing now.


Prepare release 2.12.1

What does this PR do?
This PR prepares a hotfix 2.12.1 release.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.02%.

Additional details and impacted files
@@                                         Coverage Diff                                         @@
##           nogorodnikov/rum-5830/fix-classcastexception-in-datadoginterceptor    #2186   +/-   ##
===================================================================================================
  Coverage                                                               70.02%   70.02%
===================================================================================================
  Files                                                                     726      726
  Lines                                                                   26977    26977
  Branches                                                                 4522     4522
===================================================================================================
  Hits                                                                    18889    18889
  Misses                                                                   6821     6821
  Partials                                                                 1267     1267


Support go-containerregistry as a new image resolver

go-containerregistry is a golang library for working with container registries. By supporting this library as a new resolver, we don't need Docker dependency anymore (save & pull stuff in pipeline) since we are able to talk directly with registries. I'm not sure if this is a straightforward task to implement but all we need to do is write a simple converter to convert go-containerregistry models into dives'.
cc @developer-guy

We're willing to work on it, just assign it to us @wagoodman 😋🤞

Kind ping here 🎗 @wagoodman Does it make sense in overall?

actually, I'd like to rebase dive to use anchore/stereoscope instead, which uses google/go-containerregistry under the hood, but also has many of the filetree objects and layer reasoning needed to drive the analysis and UI.


raspotify title / name does not change

Hi, I tried to change the name of raspotify in the config but even after restarting (and saving, and yes, I've verified that the file was saved) my raspberry pi, the name of the device is still displayed as raspotify (hostname of my pi) in spotify.
Any ideas why this is?

Did you delete the # before DEVICE_NAME var?
e.g.
# Device name on Spotify Connect DEVICE_NAME="raspotify-this-works-trust-me"

God I feel dumb now. That's what you get when you just rush trough the config. I didn't expect raspotify to simply work without changing any configuration (since bitrate and options were commented out as well).
thanks & can be closed


doc: update release tagging procedures

Clean up and update release tagging procedures. Use new
document tabs to separate instructions for release
candidate and final releases.
Signed-off-by: David Leach<EMAIL_ADDRESS>

For convenience, my changes are localized here:
https://builds.zephyrproject.org/zephyrproject-rtos/zephyr/21284/docs/development_process/release_process.html#tagging

@dbkinder, I used the new tabs package you introduced to try to simplify the instructions by not mixing two paths in one instruction set.

Agree with @jhedberg's comments. We should also remove the old wiki page

Yes, we agreed to do that in the release meeting. I was planning on removing the wiki when this PR completes but I guess it doesn't really need to wait on this

random CI failure ?!?!


No fedora release?

Hello! Why is there no fedora RPM? I would like to install this program on my fedora computer
thank you rat
happy ratting

You can pretty easily build it using the makefile. I don't believe it has any required dependencies aside from a C compiler.

ngl I just think it'd be funny to have debs and RPMs with pre-built packages. It won't be difficult, afaik github has their own registry for apt/dnf

see: #19

Fixed!


[Dlight] LowBatchGemv rule only apply to function with spatial symbolic var

cc: @MasterJH5574

@tvm-bot rerun


Create examples and tests for environment.go

in examples update bin, cmd and Inspec

These got added at some point in the past.  Closing.


Loss of messages after disconnection

Is this a bug report?
Yes

Can you also reproduce the problem with the latest version?
Yes
Environment

Operating system: Any
Visual Studio version: Any
Dotnet version: .Net Core 3.1

Steps to Reproduce

Check reproducible demo
Expected Behavior

Batch consumer should be retried after a disconnection and no messages should be lost
Actual Behavior

After a disconection some messages are lost.
Reason is no clear.
One supposition is that if disconnection happens while the InMemoryOutbox is publishing/sending messages, they are acknowledged anyway.
Reproducible Demo

https://github.com/GuillermoGarces/MassTransitBatchTest.git
There are 2 .sh files.
start-rabbit.sh :: run it first to start a RabbitMQ docker container
test.sh :: it cleans rabbit queues, runs the test and simulates the disconnection
Steps:

Run test
Wait for it to finish.
Press a key and wait for results
Press another key to finish test

Result should return a " Missing xxx messages" list
If it returns "No missed messages". Run test again
If test always finishes with no messages lost.
There are some parameters that can be changed:
Program.cs file has these params:

ProcessesCount = 3;
WorkCountPerProcess = 100;
ExtraWorkCountPerProcess = 10;
ConsumersDelay = TimeSpan.FromMilliseconds(1);

test.sh file has a sleep command of 2 seconds
Try also with this set:

ProcessesCount = 2;
WorkCountPerProcess = 100;
ExtraWorkCountPerProcess = 100;
ConsumersDelay = TimeSpan.FromMilliseconds(100);
Sleep of 8 seconds

How to read result:
There are 3 levels of messages.
Each message from each level has a Key field which is composed with the previous level Key + "-" + "sequential number"
Therefore ... if message 2-3-64 is missing, it means that

it belongs to the third level
It was generated by message with key 2-3 of the second level

How test works:
Messages are sent in three levels in known amounts
Each message has a known key field
On every consumer, keys consumed are registered
Since amount of messages is known and messages keys are also known, at the end, records are analized for missing keys

It was not easy to reproduce this error. Please let us know if you had troubles trying to reproduce it with the test project.

I haven't had a chance to look at it yet, and it likely won't be until next week.

So, if the broker is stopped/disconnected when a batch is completing (either publishing outbox content, etc.) any acknowledged messages that were already acknowledged will no longer be available for the next batch. If you're expecting batches to match on disconnect, you'll likely never see that happen.

We do not expect batches to match, we just expect every message to be consumed at least once and that is not happening

I was able to reproduce using your test rig (thank you for that one) consistently.
I upgraded it to 7.0.7, which includes a0171c1c1a95318fb5daeaaa3b3840d631e6a60d, a change to how message NACK failures are handled, and have been unable to reproduce it since the change.
So this may be resolved.

Excellent! We will be testing the fix during the week. Thank you very much.

We just did some tests using 7.0.7 and noticed that the outbox is not working anymore for batch consumers... that's probabbly the reason why you weren't able to reproduce the issue anymore.
The problem seems to be the changes related to #2104 fix.
Let us know if you need a test scenario for this issue.

How could the Outbox not work? I don't see any changes related to the outbox in that commit.

I have also verified this one and I wasn't able to reproduce it anymore with the latest build.


API endpoints not returning issue tag/branch

Gitea version (or commit ref):  1.13.0
Git version: 2.20.1
Operating system: Debian 10

Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL)
[ ] No

Log gist:

Description
If I'm not blind, Gitea API not returning tag / branch assigned to the issue
I've tried:

https://try.gitea.io/api/swagger#/issue/issueListIssues
https://try.gitea.io/api/swagger#/issue/issueGetIssue

... And searching through whole page but not found
Screenshots

It's here, aren't them?

OK so this is partly because github does not have assigned tag/branch in its API - so we'd need to add it.


St. Peter Port, Guernsey, a City is classified as a State

In OSM it's a city: https://www.openstreetmap.org/node/116359720#map=13/49.4551/-2.5551
I looked around the source code but there doesn't seem to be anything special for Guernsey (iso: GG)
Some examples:
> Investec House La Plaiderie St Peter Port Guernsey

Result:

{
  "house": "investec house la plaiderie",
  "state": "st peter port",
  "country": "guernsey"
}

> Maison Trinity Trinity Square, St Peter Port Guernsey

Result:

{
  "house": "maison trinity",
  "road": "trinity square",
  "state": "st peter port",
  "country": "guernsey"
}

>  St Peter Port Guernsey

Result:

{
  "state": "st peter port",
  "country": "guernsey"
}

>  St Peter Port

Result:

{
  "state": " st peter port"
}

Hm, seeing a few training data issues on this one.
The first observation is the parser gets "Saint Peter Port" correct as a city.
> Investec House La Plaiderie Saint Peter Port Guernsey

Result:

{
  "house": "investec house la plaiderie",
  "city": "saint peter port",
  "country": "guernsey"
}

Likely because it occurs as such in a number of addr:city tags in OSM.
Secondly, and weirdly, GDAL returns that the point for Saint Peter Port is not contained within the Guernsey polygon. So that record becomes an "orphan point" without a country. It takes generous buffering to produce a polygon that contains that point. In previous versions we did use buffering but sometimes that would mean points along national borders could get mapped to the wrong country, which wasn't desirable. However, it might be useful to try a backoff approach w.r.t. identifying countries in the training data since they're so essential to determining the language/address format i.e. try the unbuffered polygon first, then with buffer(0), then try buffering by increasing amounts until a polygon is matched. This issue may affect the inclusion of some places very close to the coastline in our training data e.g. Juan Les Pins, France.
Lastly, the actual classification as "state" seems to come from the GeoPlanet postal code data. I had to do some manual reclassification of some of the place types in GeoPlanet in order to incorporate that data set. GeoPlanet had Guernsey and Isle of Mann as "counties" of the UK (yay marshaling everywhere into a single place hierarchy) whereas we classify anything with an ISO-3166 code as a country. Below that there are the parishes of Guernsey, which I assumed were parishes like Jamaica or Bermuda, but actually appear to be more like civil parishes in the UK, which would map more to "city" in our nomenclature. Same is true for Jersey.
Can be fixed for 1.1.

we classify anything with an ISO-3166 code as a country

This led me to wondering: So what does Guernsey, the non-sovereign city-state, get classified as? What about other city-states?
The answers are not particularly surprising, but they are interesting:
> 123 some street, saint peter port, Guernsey, UK

Result:

{
  "house_number": "123",
  "road": "some street",
  "city": "saint peter port",
  "state_district": "guernsey",
  "country": "uk"
}

> 123 some street, saint peter port, Guernsey

Result:

{
  "house_number": "123",
  "road": "some street",
  "city": "saint peter port",
  "country": "guernsey"
}

> 123 some street, saint peter port, Guernsey, Guernsey

Result:

{
  "house_number": "123",
  "road": "some street",
  "city": "saint peter port",
  "state": "guernsey",
  "country": "guernsey"
}

> 123 some street, saint peter port, Guernsey, Guernsey, UK

Result:

{
  "house_number": "123",
  "road": "some street",
  "city": "saint peter port",
  "state_district": "guernsey guernsey",
  "country": "uk"
}

> 123 some street, saint peter port, Guernsey, UK, Guernsey

Result:

{
  "house_number": "123",
  "road": "some street",
  "city": "saint peter port",
  "state_district": "guernsey",
  "country": "uk guernsey"
}

It would appear that Hong Kong cannot be classified as a State. But it is (currently) an ISO-recognised state of China.
> Hong Kong

Result:

{
  "country": "hong kong"
}

> Hong Kong, Hong Kong

Result:

{
  "city": "hong kong",
  "country": "hong kong"
}

> Hong Kong, Hong Kong, China

Result:

{
  "city": "hong kong",
  "country": "hong",
  "city": "kong",
  "country": "china"
}

> Central Hong Kong, Hong Kong, China

Result:

{
  "road": "central",
  "city": "hong kong",
  "country": "hong",
  "city": "kong",
  "country": "china"
}

Anything with its own ISO 3166-1 code is considered to be a country in our training data, whether it's a sovereign state of not. This is an opinion, but a documented one and shouldn't affect results that much. It also has the benefit of making the model smaller than having  a separate tag for "dependency" (I also generally dislike terms rooted in imperialism).
The above cases are conflating predictions of what an entity is with how it's actually classified in the training set. The parser is a machine learning model, and is imperfect. It predicts the best tag sequence it can given the words, their properties, and their word/tag contexts, but a parser result shouldn't be taken as evidence of what an entity is or can be, only what was predicted for that specific sequence. It's better to inspect the training data to look for inconsistencies or missing data/patterns.
Particularly for place names, we make a mostly-reasonable assumption that virtually every place name will be represented in the training data. This works pretty well in general because we don't want the parser to infer city names, etc. from the tag sequence (since we have so many different countries/formats represented, it's unreliable to have a model with high weights for "state" simply because the last word was "city" without knowing the words/phrase in question). However, if a place name like "Central Hong Kong" is not in OSM (it isn't) or one of our other data sets, it's likely that the parser will get it wrong at runtime. If there are place names you're interested in that are not getting parsed correctly, the best recourse is usually to add them to OSM.
Also, the breaking up of Hong Kong into "Hong" and "Kong" is related to #178 which should also be fixed with v1.1


yum helper failing in specs

  1) Chef::Provider::Package::Yum::PythonHelper propagates stacktraces on stderr from the forked subprocess

     Failure/Error: expect { helper.package_query(:whatprovides, "tcpdump") }.to raise_error(/your hands in the air/)

       expected /your hands in the air/, got #<RuntimeError: yum-helper.py had stderr/stdout output:

       Traceback (most recent call last):

         File "/opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-17.1.11/lib/chef/provider/package/yum/yum_helper.py", line 201, in <module>

           raise RuntimeError("bad command")

       RuntimeError: bad command

       > with backtrace:

         # ./lib/chef/provider/package/yum/python_helper.rb:227:in `rescue in with_helper'

         # ./lib/chef/provider/package/yum/python_helper.rb:204:in `with_helper'

         # ./lib/chef/provider/package/yum/python_helper.rb:162:in `query'

         # ./lib/chef/provider/package/yum/python_helper.rb:128:in `package_query'

         # ./spec/unit/provider/package/yum/python_helper_spec.rb:27:in `block (3 levels) in <top (required)>'

         # ./spec/unit/provider/package/yum/python_helper_spec.rb:27:in `block (2 levels) in <top (required)>'

         # ./spec/spec_helper.rb:306:in `block (2 levels) in <top (required)>'

     # ./spec/unit/provider/package/yum/python_helper_spec.rb:27:in `block (2 levels) in <top (required)>'

     # ./spec/spec_helper.rb:306:in `block (2 levels) in <top (required)>'

8hrs of time


ISSUE-1: set mode to 'OBJECT' before exporting any model.

Fixes #1
Exporting functions must expect that and only go to 'EDIT' when necessary

Coverage increased (+0.004%) to 93.308% when pulling 4de445b5c98b6fd555df7ffbedfa6c3276b6aabf on bugfix/ISSUE-1-exporting-in-edit-mode into 2c5d3230335d2794ad4705bf0f86ae36e61110cb on develop.


Configure prints "FreeImage not found" and "PVRTexLib not found" even though all git submodules are present

===>  Configuring for cuttlefish-texture-compressor-2.6.0
===>  Performing out-of-source build
/bin/mkdir -p /disk-samsung/freebsd-ports/misc/cuttlefish/work/.build
-- The C compiler identification is Clang 13.0.0
-- The CXX compiler identification is Clang 13.0.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Found Threads: TRUE
-- Looking for FreeImage
FreeImage not found
PVRTexLib not found
-- Configuring done
-- Generating done

FreeBSD 13.1

FreeImage first checks for a version on your system, and if not found it will build from the submodule. This message is a little confusing, though, and I can make it more descriptive.
PVRTexLib unfortunately is a closed source library, and is the only option for creating PVRTC textures. Since you are building on FreeBSD, it won't be able to use that library and PVRTC support will be disabled.
BTW, I noticed in your port you're manually setting compile flags for PPC. I patched the dependency that the flags were used for to automatically detect the CPU at compile time so that should no longer be necessary.

BTW, I noticed in your port you're manually setting compile flags for PPC. I patched the dependency that the flags were used for to automatically detect the CPU at compile time so that should no longer be necessary.

Someone else added the powerpc* check. I'll remove remove it then. Thanks for letting me know.


Not to understand syntax to remove 	-ExternalConnectionSettings

Not to understand syntax to remove 	-ExternalConnectionSettings
Thsi just doesn't telle me how to dio ths. Is this Microosft??

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

ID: 82e2b003-51ed-8624-07d8-e30d6ebc6c8e
Version Independent ID: 246383d8-41d0-1c15-0233-c10778e28dd5
Content: Set-ImapSettings (exchange)
Content Source: exchange/exchange-ps/exchange/client-access/Set-ImapSettings.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Hi @pear7777, thank you for your feedback.
For example, if you want to remove the following values: "ServerName1:993:TLS" and "ServerName2:443:SSL", you should run the following command:
Set-ImapSettings -ExternalConnectionSettings @{Remove="ServerName1:993:TLS","ServerName2:443:SSL"}
More information:
https://docs.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help

@dariomws  Thank you very much for the contribution and sharing this explanation. @pear7777
Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Revisit default colors of delta time

It's misleading rn (possibly brightness issue)

Hi there. I always use your plugin and when I want to highlight certain deltas I can't see the difference between them because of their colours. So I found a workaround. I use less thresholds, but I use an extra one to have the next brighter colour. That way it is easier to see the differences.
Then I thought of a way to use the brightness factor so that each of the 8 possible deltas can be more different.
By using a gradient, I sat the start brightness at a low level (dark) and the end brightness at a high level (light). Then I picked the colour from the gradient using eight squares and taking their centre as a reference point
I made three paletes

So every start squares start with a shade of dark red and then ends with a light yellow
For the #0 delta, It could be a purple. Or it can be hidden. Because most of the time I don't care what the delta is beyond the last one that I set.
If you need the exact HEX of the square I can share them xD

I tried 1st and 3rd pallets. Brightest looks a lot better imo, dark one is blending with dark background too much.

New color palette implemented in 0.4.3