Deletion in a linked list

Would like to contribute in the C++ codebase by adding an algorithm for deletion in a singly linked list under GSSOC2021.
Please assign me.

i like to contribute to this project ...my code will be in java with proper comments and test cases

Hello.....I would like to contribute to this issue as a part of GSSoC 2021. Could you please assign this to me? I would implement this in C++ and will cover all the Cases.

Hello.....I would like to contribute to this issue as a part of GSSoC 2021. Could you please assign this to me? I would do this in C++ and fulfill all the necessary requirements.

I would like to work on this issue as a part of GSSoC 2021 and would like to contribute to this issue using C++.

I would like to solve this issue as a part of GSSoC 2021 in python. I would be thankful to you if you please assign me this issue.

I am a GSSOC'2021 participant. Please assign me this work.I am good at C++,C,Java and python.Also good at algorithm and data structures.I will write programmes with detailed explanation and proper commenting.


(question) can i use physic or js engine (physic but no botplay lag) charts?

pls answer

yes but some older version of psych engine might make it crash (idk about js engine)

and ye. what the frick admin mode doing?

It allows you to use botplay and practice mode on any song and other stuff (btw botplay and practice mode won't be in the admin menu next update)


⚠ Bofrost.lu has degraded performance

In ea38383, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1191 ms

Resolved: Bofrost.lu performance has improved in d548690 after 14 minutes.


Contrast Security Solution

Solution including workbook, data connector and analytics rules for review.

Requires further logo changes.


Rename OIIO_NAMESPACE_ENTER/EXIT -> BEGIN/END, and roll the braces into it

I've wanted this for a while, finally got around to it.
It was awkward, before you needed
OIIO_NAMESPACE_ENTER
{
   ....
}  // what's that extra brace all about?
OIIO_NAMESPACE_EXIT

now it's the cleaner
OIIO_NAMESPACE_BEGIN
...
OIIO_NAMESPACE_END

LGTM, I agree its much cleaner this way.


Feature/update prettier

Update prettier to latest mainly because of https://github.com/prettier/prettier/issues/7428 , then manually ran prettier on all relevenant files.
The new trailing comma looks weird to me but...it is what it is.

Adding --trailing-comma none to the command does work but...
https://prettier.io/blog/2020/03/21/2.0.0.html first paragraph says they deliberately chose to do that.  As weird as it looks to me, the point of prettier is that it's opinionated so we don't debate on which style to use https://prettier.io/docs/en/option-philosophy.html

The new trailing comma looks weird to me but...it is what it is.

Fun fact: IE6 did not allow trailing commas.


RFC: Flutter types that would be useful in Jaspr

Description
This is a request for comments on https://flutter.dev/go/move-flutter-agnostic-types, which proposes that certain Flutter types are moved out of Flutter's namespaces so they can be used in contexts other than Flutter. We'd like to hear from the Jaspr maintainers and community on what Flutter types would be useful in the Jaspr framework and/or applications.

Yes, please!

Also commented on the doc, but to summarize:

Generally very welcome, would be a huge benefit for Jaspr
Especially ChangeNotifier, ValueNotifier, Listenable would be very welcome as those are duplicated right now.
Some common (kIsWeb, debug/release mode constants) would also be welcome.
dart:ui types are not useful at all for Jaspr, as it has css based styling (e.g. it has a Color class but this works different to Flutters Color)


Update cargo lock

Cargo.lock of kimchi was breaking nix develop mina so the file was updated using cargo update

!ci-build-me


Incorrect confirm password validation text

Bug Report
What is the current behavior?
The second password field on the signup form (for confirmation) says "Must be 6 characters long and include a capitalized letter" when its validation fails
What is the expected behavior?
When the two passwords don't match, the confirm password field should instead say something like "Passwords must match"
What steps did you take to get this behavior?
Enter two different passwords into the signup form fields (which each meet the 6 characters & capital letter criteria)
Additional Info
Operating System
Browser
Screenshots

@matthewzurek you mentioned that you wanted this issue, correct?

Yep! Just finished working on it

Don't forget to submit the PR when you're finished @matthewzurek


Long reads are not detected in nanopolish eventlalign

Hi,
I am trying to useevent-align scale-events with RNAs of 100,150,1500 and 5000 bps. (contigs corresponding to 5S,5.8S,18S and 28S).
I use minimap2 for alignment and the bam file has quite big amount of all these contigs.
However, the event-align output only have 18S... None of the other contigs are there..
Can you elaborate on how to overcome this issue please?
Thank you very much.

Could you paste the "post-run summary" message?
Jared

Sure:
[post-run summary] total reads: 8383375, unparseable: 0, qc fail: 34730, could not calibrate: 1461914, no alignment: 179382, bad fast5: 0

That is an incredible amount of data in IVT_repeat, perhaps you ran out of disk space in the first run? In any case, I'm glad you have a result now, can I close this issue?


Create initial metadata for the repo

Motivation
Necessary for new pipeline

LGTM, let's do this :)


feat(otelcol/exporter/splunkhec) Add Splunk HTTP Event Collector (HEC) Exporter

PR Description
Adds functionality described in https://github.com/grafana/alloy/pull/1645 and the proposal at https://github.com/grafana/alloy/issues/1646
Pinging @PatMis16
Which issue(s) this PR fixes
Fixes #1646
Notes to the Reviewer
PR Checklist

[x] CHANGELOG.md updated
[x] Documentation added
[x] Tests updated
[x] Config converters updated

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

I assume the failed ci is due to me forgetting to re-run go generate ./internal/tools/docs_generator/ after updating the docs?

Thanks for your contributions, it looks great already :)

Puh i pretty much just copied (or tried to copy) what was done in the datadog PR . I will address your comments as soon as i manage to also work on them. Thanks a lot for the kind words!

The config converter is missing (this is used to convert an otel config to an alloy config automatically). Here is the converter folder: https://github.com/grafana/alloy/tree/main/internal/converter/internal/otelcolconvert and here is a PR that adds a new converter: https://github.com/grafana/alloy/pull/739/files

I dont know how i missed this - but i will add the converter when addressing the remaining, open comments.

Else, are you ok to become a maintainer of this component?

I will come back to you on this

All good from my POV, please ignore the flaky test. One last thing before we merge: I see that you added yourself and @PatMis16 as maintainers. We update our Otel dependencies ~every 6 weeks (before every release). A few days before we cut the release candidate, we will ping you on the community slack and on github to give you the opportunity to sync the hec exporter with upstream.
But no pressure:

it's okay to miss some updates
it's okay if the component does not have all upstream's features
you can step out at any time from being a maintainer
If there are breaking changes in the component that are blocking our release and that no maintainers are available we can step in and help. If there is no easy way for us to solve them we may temporarily disable the component.
The way we update the otel dependencies is not ideal but it's something that we are working on improving.

@adlotsof @PatMis16 if you are ok with this, please thumbs up this message and I will proceed to merge the PR.
If you need to reach out to the team you can message us on slack directly or ping us in the #alloy slack channel

Guess it's ok.


Suggestions for improving your paper

Hello,
I read your paper. I hope it will be accepted. I have some suggestions to improve your paper or give you some ideas for future work.

You had faced with imbalanced datasets and used undersampling. One way to deal with this problem is to use an unbiased metric such as  Matthews Correlation Coefficient (MCC). In software defect prediction we face the same issue. MCC is widely used in software defect prediction.
Using relative process metrics might help to improve the results. Again, in software defect prediction relative process metrics improve the results (e.g., see the paper).
"We use the Min-Max scaler provided by ..." --> It would be better to consider distribution and then apply the scaler (Standard or Min-Max).
"Logistic Regression: C (page 5) --> There are two regularization types (norm 1 and norm 2). Which one do you use?

Thanks for your great paper. Good Luck!

Thanks for the suggestions! @jan-gerling will look at it!


Added catalog-webhook plugin & image for the plugin directory

Hopefully this is an easy PR. Added a new public plugin that provides the ability to push catalog changes to a remote URL.

Two quick improvements to consider to make sure this is more broadly usable:

https://github.com/ForgedApps/backstage-catalog-webhook-plugin/blob/61a1afe16b917a5d186305f20bdbcc02e37552b8/src/webhookProcessor.ts#L42-L45: could this use the task scheduler instead? It lets it scale across multiple instances and is gonna be more robust than setInterval
https://github.com/ForgedApps/backstage-catalog-webhook-plugin/blob/61a1afe16b917a5d186305f20bdbcc02e37552b8/src/cache.ts#L4: could this use the cache service instead? same thing here - helps it scale across instances and avoids local filesystem access

Two quick improvements to consider to make sure this is more broadly usable:

https://github.com/ForgedApps/backstage-catalog-webhook-plugin/blob/61a1afe16b917a5d186305f20bdbcc02e37552b8/src/webhookProcessor.ts#L42-L45: could this use the task scheduler instead? It lets it scale across multiple instances and is gonna be more robust than setInterval
https://github.com/ForgedApps/backstage-catalog-webhook-plugin/blob/61a1afe16b917a5d186305f20bdbcc02e37552b8/src/cache.ts#L4: could this use the cache service instead? same thing here - helps it scale across instances and avoids local filesystem access

Thanks @Rugvip these are good suggestions, I wasn't aware of those - I'll do a quick refactor!

Hi @Rugvip, I made both changes. Felt good to get rid of the node-persist dependency. Thanks for the smart suggestions, feels better now :)

Hi folks, let me know if there are any enxt steps I need to take to add my plugin to the directory, thanks!


fixing blob path regex

Fixing the regex so that it accept the following inputs, Fixing regex for storage bindings, opening a new issue to review all other regexs
con/a
{container}/{a}
%abc%/{a}/{ab}/a
%abc%/%a%/{abc}/a
{Container}/{first}
con/{a}

Also for blob trigger it accept the following as well
con
{Container}
{container}
%abc%

#409


fix(export): export selenium-webdriver

rename to ProtractorBrowser to be able to export selenium-webdriver Browser as Browser
export all selenium-webdriver items in ptor
update dependency tests for selenium

closes #3427

Needs testing.

ensure globals are exported from the namespace https://github.com/angular/protractor/issues/3437

One more thing, then LGTM


Update to gfx-rs v0.17 and glutin v0.12

gfx-rs v0.16 -> v0.17 upgrade didn't go quite smooth :-( Something seems to be wrong with the alpha channel

Mipmaps were the problem.
You should either use gfx::texture::Mipmap::Provided (old behaviour) or call Ecoder::generate_mipmap later.


RFC: Checkbox

Which scope/s are relevant/related to the feature request?
checkbox
Information
Checkbox
Assesment

Time
Complexity
Risk
Description

3
2
0
Mostly styles

Dependencies
None
brn

API (proposed)
The brnCheckbox directive would set the inputs type to checkbox & control the aria-checked attribute based on the inputs value & indeterminate state.
Toggling the indeterminate state would not change the inputs value, just the aria-checked attribute.
The directive also adds a readonly input that intercepts the click & change events
<input name="test" brnCheckbox />Test

Alternatively it could apply only to inputs of type checkbox, but that seems like a bit of repetition.
<input name="test" type="checkbox" brnCheckbox />Test

Another alternative would be to create a checkbox component that handles the label, this would also allow us to bind aria-labeledBy to the inputs id & toggle the checkbox when the user clicks the label. This would however require us to either create a brnLabel directive or use something else for the checkbox, & does not sync with the current implementations of hlmInput & hlmLabel.
<brn-checkbox name="test">Test</brn-checkbox>

Proposed inputs

Input
Type
Default
Description

readonly
BooleanInput
false
toggles the readonly state of the checkbox

hlm

The hlmCheckbox directive would be composed with the brnCheckbox & apply the appropriate styles.
Aria

Roles, States & Properties
aria-checked should be true or false based on the inputs value or mixed if indeterminate
when focused space should be able to toggle the checkbox (this is a html default, so it only applies if we go the custom component route)
checkbox
Radix

API
const CheckboxDemo = () => (
      <Checkbox.Root
        defaultChecked
        id="c1"
      >
        <Checkbox.Indicator>
          <CheckIcon />
        </Checkbox.Indicator>
      </Checkbox.Root>

        Accept terms and conditions.

);

Source
https://www.radix-ui.com/docs/primitives/components/checkbox
shadcn

API
export function CheckboxWithText() {
  return (
      <Checkbox id="terms2" />

        Accept terms and conditions

  )
}

Source
https://ui.shadcn.com/docs/components/checkbox
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue

[X] Yes
[ ] No

I think we should actually follow the radix api and not use a directive here.
The implementation would become similar to our Switch.
Let me explain why:
If we use a directive there is no way to easily style the indicator in the template (with CSS or tailwind classes).
One of the strengths of radix is that everything is right there in the template. I want to keep that (as good as possible)
for the brn primitives too. I do think we can use a directive as the indicator, which would leave us with an API like below:
<brn-checkbox [(ngModel)]="acceptedTermsAndConditions">
  <hlm-icon brnCheckboxIndicator name="check" />
</brn-checkbox>

brnCheckboxIndicator makes sure it is rendered when state is checked or indeterminate.
That way we have complete control over the styling while all the aria management is taken care off by brn.
Label interaction would stay as you suggested
<brn-checkbox name="termsAndConditionsCb" [(ngModel)]="acceptedTermsAndConditions">
  <hlm-icon class="h-4 w-4" brnCheckboxIndicator name="check" />
</brn-checkbox>
  I accept the terms and conditions.

@elite-benni I remember you mentioning that you had some POC working for this. Do you want me to assign you this issue?

Yes you can assign me.
I have it working in my Checkbox branch already.
The only thing missing is indeterminate / mixed Checkbox.
I have planned to provide a PR today. ;)


change room admin failing on prod.

Describe the bug
Make room admin failing on prod.
To Reproduce
Steps to reproduce the behavior:

Create room
Try to transfer ownership

Expected behavior
Transfer ownership
If someone wants to assign it to me ill be working on it tonight or tomorrow morning I'll figure it out.
Probably has something failing in the validation for the Kousa.Room.change_room_creator function

i'll fix it

it works, may be @benawad didn't deploy elixir API? 🤔

hmmm, maybe, do error messages not appear on front-end on prod?
it was working fine for me too

it just works, but it has a logical error, the former creator gets made a listener

I didn't realize there was a backend change, my bad, let me review next time before merging backend changes

@benawad gotcha, the changes were made to fix #1097

All good haha

its pushed now


Scrollable menu

I guess this doesn't work with current implementation, so would be a feature request. I tried to create a scrollable page selection menu for pagination using mdl-menu with max-height and overflow-y: auto. I have hundreds of pages on my data-table and the menu goes blank when scrolling. The items appear again on hover. I guess this is due to animations:

UPDATE: It works ok if I use scrollwheel, this happens only with scrollbar. When scrolled to bottom using wheel first, then the items stay visible. So I think a solution would be to animate only the items initially visible, then reveal the rest which don't fit in the menu.
UPDATE2: This doesn't happen on a menu with class mdl-menu--top-right. Only if menu opens down.

This has come up before. Nothing can be done in 1.x about it. Should be fixed in 2.x updates.

I am facing the same problem.
Can anybody help please.

@charanjit-singh It can be solved by using two CSS properties in ul tag.

         <input type="text" value="" class="mdl-textfield__input" id="sample11" readonly>         <input type="hidden" value="" name="sample11">         Select Doctor

Doctor 1

Doctor 2

Doctor 3

Doctor 4

Doctor 5

Doctor 6

Doctor 7

Doctor 8

Doctor 9

Last Doctor

You can change the max-height of ul to change the no. of items shown in the drop-down.


Accept non null terminated string on unpacking

This is a bug-fix for #378 and fixes #373.

I thought that was already merged...


Annotation config.kubernetes.io/depends-on not registered / documented

This is a Bug Report

Problem: https://github.com/kubernetes-sigs/cli-utils/blob/master/README.md mentions an annotation, config.kubernetes.io/depends-on. We haven't documented this in https://kubernetes.io/docs/reference/labels-annotations-taints/ (which means it's not registered).
Proposed Solution:
Document that annotation.
Page to Update:
https://kubernetes.io/docs/reference/labels-annotations-taints/

Additional Information:
/language en
/sig docs

/assign

/triage accepted

(anyone is welcome to work on this - we have a “no cookie licking” policy in SIG Docs)
If someone has said they plan to work on an issue, and you're also considering that work, it's polite - but not mandatory - to try to co-ordinate.

I did spend time reading materials about this annotation and the PR proposed.
However, I don't think we should add this as a "well-known labels, annotations or taints".
There are a million of annotations/labels used by external tools, but we are not supposed to document them all.

A counter-point to @tengqm is that this annotation is in an official-looking domain, config.kubernetes.io.

There are a million of annotations/labels used by external tools, but we are not supposed to document them all.

The library that uses this annotation is part of the Kubernetes project.

Hi, as there was still discussion on whether this annotation should be registered earlier, can we get a final note on whether working on this Issue and raising PR is required or we can close this issue?

Maybe we can remove triage till the total consensus on this.
If we are open for PR , i can add this one.

Let's treat this as accepted (which is how things stand) until there's consensus to change it.


feature: add healthcheck policy for workload and trait by cue template

[x] Support Custom Health Check Logic for Appliction by Cue Template

Vela is used for application release, and how to evaluate the success of an application release? Not only Vela creates workloads and traits, but more importantly, Vela should check the health of workloads and traits. HealthScope is hardcoded for the health check logic of various resources. Here providers a custom health check plan.
Health Check Policy
After the K8s resource is created, the relevant data will be written back to the status of CR. Whether the release is successful is actually a series of judgments and filter conditions combination, called health policy. Vela should combine with the data in CR and the policy to determine whether a resource object meets the conditions. For example, when the values of replicas and readyReplicas in the status of Deployment CR are equal, the release is successful.
Developers could customize the health check policy in the definition, which has high scalability.
apiVersion: core.oam.dev/v1alpha2
kind: WorkloadDefinition
metadata:
  name: worker
  annotations:
    definition.oam.dev/description: "Long-running scalable backend worker without network endpoint"
spec:
  definitionRef:
    name: deployments.apps
  extension:
    healthPolicy: |
      isHealth: output.status.replicas == output.status.readyReplicas
    template
      ...

healthPolicy is the customized policy by developer
output represents the CR

Example

Workload(deployment) health policy

apiVersion: core.oam.dev/v1alpha2
kind: WorkloadDefinition
metadata:
  name: worker
  annotations:
    definition.oam.dev/description: "Long-running scalable backend worker without network endpoint"
spec:
  definitionRef:
    name: deployments.apps
  extension:
    healthPolicy: |
      isHealth: output.status.replicas == output.status.readyReplicas
    template: |
      output: {
      	apiVersion: "apps/v1"
      	kind:       "Deployment"
      	spec: {
      		selector: matchLabels: {
      			"app.oam.dev/component": context.name
      		}
      		template: {
      			metadata: labels: {
      				"app.oam.dev/component": context.name
      			}
      			spec: {
      				containers: [{
      					name:  context.name
      					image: parameter.image

      					if parameter["cmd"] != _|_ {
      						command: parameter.cmd
      					}
      				}]
      			}
      		}

      		selector:
      			matchLabels:
      				"app.oam.dev/component": context.name
      	}
      }

      parameter: {
      	// +usage=Which image would you like to use for your service
      	// +short=i
      	image: string

      	cmd?: [...string]
      }`

Trait(ManualScalerTrait) health policy
It is assumed that the trait will return whether the release is successful through the phase of status

apiVersion: core.oam.dev/v1alpha2
kind: TraitDefinition
metadata:
  annotations:
    definition.oam.dev/description: "Manually scale the app"
  name: scaler
spec:
  appliesToWorkloads:
    - webservice
    - worker
  definitionRef:
    name: manualscalertraits.core.oam.dev
  workloadRefPath: spec.workloadRef
  extension:
    healthPolicy: |
      isHealth: output.status.phase == "ready"
    template: |-
      output: {
      	apiVersion: "core.oam.dev/v1alpha2"
      	kind:       "ManualScalerTrait"
      	spec: {
      		replicaCount: parameter.replicas
      	}
      }
      parameter: {
      	//+short=r
      	replicas: *1 | int
      }

Good idea overall. I wonder what type of health check does this support? There must be a limit.

Good idea overall. I wonder what type of health check does this support? There must be a limit.

Good idea overall. I wonder what type of health check does this support? There must be a limit.

I wonder how can the "health" expression work when the fields are in a YAML/Json format instead of cue?

Good idea overall. I wonder what type of health check does this support? There must be a limit.

I wonder how can the "health" expression work when the fields are in a YAML/Json format instead of cue?

Good idea overall. I wonder what type of health check does this support? There must be a limit.

I wonder how can the "health" expression work when the K8s CR output are in a YAML/JSON format instead of cue?
The "health" expression is cue template, but data(k8s CR output) is JSON used to combine with "health" expression.

Good idea overall. I wonder what type of health check does this support? There must be a limit.

I wonder how can the "health" expression work when the K8s CR output are in a YAML/JSON format instead of cue?
The "health" expression is cue template, but data(k8s CR output) is JSON used to combine with "health" expression.

Good idea overall. I wonder what type of health check does this support? There must be a limit.

Thanks, the "health" check just is used for the output of CR, which could be any kind of CR as long as you can write relevant expressions correctly with powerful cue expression.

I wonder how can the "health" expression work when the K8s CR output are in a YAML/JSON format instead of cue?

The "health" expression is cue expression, but data(k8s CR output) is JSON used to combine with "health" expression.

I like the idea that we can add "health check"  CUE formula to the template. This is useful for the health scope.
However, the application controller shouldn't care about each workload/trait's health. We have a healthScope that handles that.
I wonder if you can make the UT test work and then integrate this formula with the healthScope implementation instead (in a separate PR)?

Good idea overall. I wonder what type of health check does this support? There must be a limit.

Thanks, the "health" check just is used for the output of CR, which could be any kind of CR as long as you can write relevant expressions correctly with powerful cue expression.

I wonder how can the "health" expression work when the K8s CR output are in a YAML/JSON format instead of cue?

The "health" expression is cue expression, but data(k8s CR output) is JSON used to combine with "health" expression.

I like the idea that we can add "health check"  CUE formula to the template. This is useful for the health scope.
However, the application controller shouldn't care about each workload/trait's health. We have a healthScope that handles that.
I wonder if you can make the UT test work and then integrate this formula with the healthScope implementation instead (in a separate PR)?


Internal error while getting Lets Encrypt certificate / SQlite database

When trying to get a new certificate from Let's Encrypt, I get an "Internal Error" message.
Using latest docker image (2.4.0).
By looking at the /var/log/letsencrypt/letsencrypt.log file, I can see that the challenges has been successfully completed :
2020-08-26 21:54:18,911:DEBUG:certbot._internal.storage:Creating directory /etc/letsencrypt/archive.
2020-08-26 21:54:18,912:DEBUG:certbot._internal.storage:Creating directory /etc/letsencrypt/live.
2020-08-26 21:54:18,912:DEBUG:certbot._internal.storage:Writing README to /etc/letsencrypt/live/README.
2020-08-26 21:54:18,913:DEBUG:certbot._internal.storage:Archive directory /etc/letsencrypt/archive/npm-2 and live directory /etc/letsencrypt/live/npm-2 created.
2020-08-26 21:54:18,913:DEBUG:certbot._internal.storage:Writing certificate to /etc/letsencrypt/live/npm-2/cert.pem.
2020-08-26 21:54:18,914:DEBUG:certbot._internal.storage:Writing private key to /etc/letsencrypt/live/npm-2/privkey.pem.
2020-08-26 21:54:18,914:DEBUG:certbot._internal.storage:Writing chain to /etc/letsencrypt/live/npm-2/chain.pem.
2020-08-26 21:54:18,914:DEBUG:certbot._internal.storage:Writing full chain to /etc/letsencrypt/live/npm-2/fullchain.pem.
2020-08-26 21:54:18,914:DEBUG:certbot._internal.storage:Writing README to /etc/letsencrypt/live/npm-2/README.
2020-08-26 21:54:19,032:DEBUG:certbot._internal.plugins.selection:Requested authenticator webroot and installer <certbot._internal.cli.cli_utils._Default object at 0x7fc1461d4190>
2020-08-26 21:54:19,033:DEBUG:certbot._internal.cli:Var pref_challs=dns,http (set by user).
2020-08-26 21:54:19,033:DEBUG:certbot._internal.cli:Var authenticator=webroot (set by user).
2020-08-26 21:54:19,033:DEBUG:certbot._internal.cli:Var webroot_path=/data/letsencrypt-acme-challenge (set by user).
2020-08-26 21:54:19,034:DEBUG:certbot._internal.cli:Var webroot_path=/data/letsencrypt-acme-challenge (set by user).
2020-08-26 21:54:19,034:DEBUG:certbot._internal.cli:Var webroot_map={'webroot_path'} (set by user).
2020-08-26 21:54:19,034:DEBUG:certbot._internal.storage:Writing new config /etc/letsencrypt/renewal/npm-2.conf.
2020-08-26 21:54:19,079:DEBUG:certbot._internal.reporter:Reporting to user: Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/npm-2/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/npm-2/privkey.pem
Your cert will expire on 2020-11-24. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot renew"

The certificate is then displayed on the certificates list as expired with an expiration date being the current day.

By looking at the certificate file on /etc/letsencrypt/live/..., I can see the certificate being valid :
[root@docker-nginx:/etc/letsencrypt/live/npm-2]# openssl x509 -in cert.pem -text Certificate:     Data:         Version: 3 (0x2)         Serial Number: <removed>         Signature Algorithm: sha256WithRSAEncryption         Issuer: C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3         Validity             Not Before: Aug 26 20:54:16 2020 GMT             Not After : Nov 24 20:54:16 2020 GMT

More information :
After manually editing the expiration date of the generated certificate on my SQlite database file, everything goes well.

Apparently, it's caused by FROM_UNIXTIME:
[8/29/2020] [10:22:15 PM] [Express  ] › ⚠  warning   update `certificate` set `modified_on` = date('now'), `expires_on` = FROM_UNIXTIME(1606511988) where `certificate`.`id` = 3 - SQLITE_ERROR: no such function: FROM_UNIXTIME

I can confirm, that I also have the problem with 3 - SQLITE_ERROR: no such function: FROM_UNIXTIME and somehow it makes the domain to reach the letsencrypt rate-limit (so in my case until the next week I won't be able to get a new SSL certificate).
It worked properly before start using SQLITE.

I can confirm as well showing the same error caused by FROM_UNIXTIME

Same Problem for me.

Same here.
@tg44 Did you also face this issue when implementing SQLite?

It looks like this may be fixed in #560

I can confirm this is fixed in v2.5.0 🚀

I dont use certs, probably this is the reason why I didn't catch that...
Yes the problem is the sql function (sqlite is really limited and sonetimes dumb), and the linked PR is the fix for this (I did the same with the current time function anno).

@jc21 i think we can close this 👍

also have the same issue

@docfactory37  The issue was fixed in v2.5.0
Make sure you're updated to that version. If you're still having the issue, you may want to open a different issue and include some logs for further troubleshooting.

I confirm, it's now working properly :-)
Thanks for your help !


Flex spec v2

Checklist

[x] Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
[x] Any modified or new methods or classes have helpful JavaDoc and code is thoroughly commented
[x] The description lists all applicable issues this PR seeks to resolve
[x] The description lists any configuration setting(s) that differ from the default settings
[x] All tests and CI builds passing

Description
Changes to migrate the dev-flex branch from flex version 1 to version 2.

Death, where is thy Sting? Last edit looks good.


Add "target_for" edges from loadPHAROS.py

hey @beasleyjonm , @EvanDietzMorris sorry this item got lost in the move. I took a look post-merge and I agree with this change. It looks good.


[0.45.0] new app setup fails "bundling: Error at DependencyGraph._getAbsolutePath"

react-native init testApp
cd testApp
react-native run-ios
yields:
error: bundling: Error     at DependencyGraph._getAbsolutePath (/Users/nilspoltoraczyk/Desktop/temp/testApp/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:280:11)     at DependencyGraph.getDependencies (/Users/nilspoltoraczyk/Desktop/temp/testApp/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:218:26)     at Resolver.getDependencies (/Users/nilspoltoraczyk/Desktop/temp/testApp/node_modules/react-native/packager/src/Resolver/index.js:107:27)     at /Users/nilspoltoraczyk/Desktop/temp/testApp/node_modules/react-native/packager/src/Bundler/index.js:591:37     at Generator.next (<anonymous>)     at step (/Users/nilspoltoraczyk/Desktop/temp/testApp/node_modules/react-native/packager/src/Bundler/index.js:12:445)     at /Users/nilspoltoraczyk/Desktop/temp/testApp/node_modules/react-native/packager/src/Bundler/index.js:12:605     at <anonymous>     at process._tickCallback (internal/process/next_tick.js:169:7) Bundling index.ios.js  0.0% (0/1), failed.
OSX 10.11.6

I got it to work by starting the packager with npm run start -- --reset-cache.
But you have to reset the cache each time you close it.

Getting the same error here after the last Xcode update.

Also getting the same error with Android.
react-native init Project
cd Project
react-native run-android
Android: 7.0 and 6.0 (real devices)
Mac: OS 10.12.5
"react": "16.0.0-alpha.12",
"react-native": "0.45.0"

Getting the same error for run-ios and run-android.
Looking for JS files in /node_modules/react-native/packager
instead of
npm start works ok

Cannot run on-device debug. Getting this error. Trying to look files from '/node_modules/react-native/packager'

I am seeing the same problem after upgrading to react-native 0.45. But my error message is slightly different:
NotFoundError: Cannot find entry file build/app/app.ios.js in any of the roots: ["<omitted>/client/node_modules/react-native"]
That might be the reason why @aparedes's npm run start -- --reset-cache didn't work for me. Using --root as suggested here did work, though:
npm run start -- --root <directory_with_your_react_component_js_sources>

I'm having this issue as well. @aparedes's advice is getting me by for now, but it's annoying having to run that command every time I want to launch my app.
macOS: 10.12.5 (16F73)

Same problem as @br4nnigan but with Android, @aparedes's solution seems to be working.
Windows 10
react-native 0.45.0
react 16.0.0-alpha.12
Android

I ended up using rninit to initialize the project with the previous release.

I met a problem, also hope to get some help, thank you very much:
Error message:
<
Loading dependency graph, done.
error: bundling: Error
at DependencyGraph._getAbsolutePath (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:280:11)
at DependencyGraph.getDependencies (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:218:26)
at Resolver.getDependencies (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Resolver/index.js:107:27)
at /Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Bundler/index.js:591:37
at Generator.next ()
at step (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Bundler/index.js:12:445)
at /Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Bundler/index.js:12:605
at
at process._tickCallback (internal/process/next_tick.js:169:7)
Bundling index.ios.js  0.0% (0/1), failed.
error: bundling: Error
at DependencyGraph._getAbsolutePath (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:280:11)
at DependencyGraph.getDependencies (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:218:26)
at Resolver.getDependencies (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Resolver/index.js:107:27)
at /Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Bundler/index.js:591:37
at Generator.next ()
at step (/Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Bundler/index.js:12:445)
at /Users/xinghao/Desktop/RNNewsCar/node_modules/react-native/packager/src/Bundler/index.js:12:605
at
at process._tickCallback (internal/process/next_tick.js:169:7)
Bundling index.ios.js  0.0% (0/1), failed.

I don't know how this is a mistake
I NPM is 5.0
node is 8.0
10.12.5 is OS
Hope to get answer Thank you very much

I'm having the same problems after upgrade from react native 0.36.0 to 0.45.0 and running npm run start -- --root starts      from console starts the app. Running latest xcode update

I am also facing similar error.
Loading dependency graph, done.
error: bundling: Error
at DependencyGraph._getAbsolutePath (/Users/ashiqm/Ashiq/Learning/React-native/kasave/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:280:11)
at DependencyGraph.getDependencies (/Users/ashiqm/Ashiq/Learning/React-native/kasave/node_modules/react-native/packager/src/node-haste/DependencyGraph.js:218:26)
at Resolver.getDependencies (/Users/ashiqm/Ashiq/Learning/React-native/kasave/node_modules/react-native/packager/src/Resolver/index.js:107:27)
at /Users/ashiqm/Ashiq/Learning/React-native/kasave/node_modules/react-native/packager/src/Bundler/index.js:591:37
at Generator.next ()
at step (/Users/ashiqm/Ashiq/Learning/React-native/kasave/node_modules/react-native/packager/src/Bundler/index.js:12:445)
at /Users/ashiqm/Ashiq/Learning/React-native/kasave/node_modules/react-native/packager/src/Bundler/index.js:12:605
at
at process._tickCallback (internal/process/next_tick.js:169:7)
Bundling index.android.js  0.0(0/1), failed.

Me too

+1

Doesn't anyone test these releases?

Issue resolved for me.
The react-native launched new release 0.45 a few days back. So, the commands to create a react-native application and running locally have many differences.
npm install -g create-react-native-app
Then run the following commands to create a new React Native project called "AwesomeProject":
the new way of creating a react-native application as follows
create-react-native-app AwesomeProject
cd AwesomeProject
npm start

Please follow the official documentation for creating an application and running the application on locally. hope the below link will help you.
https://facebook.github.io/react-native/docs/getting-started.html
Enjoy, Happy coding :)

Applications created using create-react-native-app are set up in a different manner. Projects created using react-native init, e.g. "Projects Built with Native Code", are still supported and should work. The workaround is not to switch to CRNA, but rather to kill and restart the packager directly using npm start. At this point you can reconnect your app to the packager by reloading.
Closing as duplicate of #14246.

+1 - this happens on an upgraded application as well.

Brothers, ladies I found the solution:0.45.0 seems to be a beta and formal version of the mixtureWhen we are creating a new project to knock this command react - native init XXX - versoin 0.44.3Then you can I've tried no problem is not in use 0.45.0 version created

$ react-native init ProjectName --version 0.42.0


[Optimize](inverted index) optimize inverted index bitmap copy

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


print: fix urls for uglyURLs=true

Enabling "ugly URLs" does not seem to be compatible with the new print support feature: All subpages are displayed in print mode.
MWE: Checkout the Hugo Relearn theme version 5.2.1 and add uglyurls = true to config.toml. The homepage is displayed normally, all subpages will be displayed only in print mode. However, the URLs point to the normal subpages, i.e. something like ...exampleSite/public/basics.html.

Once you deactivate the new print feature (remove the "PRINT" entries in [outputs]), the subpages are also displayed normally again.
Tested with Hugo 0.101.0 and Hugo Relearn theme 5.2.1.

Thanks for reporting!

Thanks for the clarification.
So the takeaway message is that uglyURLs and print just won't work together? Is there any way to get both options working? You wrote, that one could change the definition of outputformats.PRINT. Any advise how to do so?

No no. You can use uglyURLs, but they will only be used for the usual HTML page. For the print-preview it falls back to "prettyURLs".
Eg. if I apply uglyURLs to the theme's exampleSite you would have a URL .../basic.html for the page of the first chapter but still .../basic/_index.print.html for its print preview.
The patch for this is pushed and I've released a new version specifically for this bug fix yesterday.

Oh, my bad. I only noticed commit 0fb76d2 listed in the timeline, which seems to contain just a note/clarification (_index.en.md) and a new toggle in config.toml.

Yeah, the additional option in config.toml is the fix. Please note, that this is the config.toml that comes with the theme (and not with the exampleSite). Besides updating your installation, you don't need to change anything to make it work!

Ah, I see :)  Thank you again very much for your work on this beautiful theme!


When using an ALPHA-type hardware keyboard, display of the the special-character selector box is unreadable.

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.801
Where did you get the app from?
F-Droid
Android version
Lineage 16, Lineage 20
Device model
No response
Steps to reproduce

Connect an ALPHA-type hardware keyboard.
In K9-Mail, compose a new e-mail and select the message body for editing.
On the hardware keyboard, long-press any character that exists in accented variants (e.g. 'A').
An on-screen selector box appears, that should allow one to pick the desired accented variant of the character. However, in K9-Mail, the selector box is displayed in an unreadable and distorted way. See first screenshot attached.
Note that, despite the distorted graphics, the selector does actually allow one to pick an accented character at random: Tap any of the blank "character" boxes and the respective letter indeed appears in the message body. It is only the unreadable display that makes the character selector box useless.

Expected behavior
The accented character selector box should be displayed in a readable way. The second screenshot shows a different app (QKSMS) properly supporting the feature on the same device.
Actual behavior

Logs
No response

This UI is rendered by the OS, not the app. This is most likely a bug in Android that only affects some apps. Please report this in the Lineage bug tracker.


LayoutXLM - pretrained model for FUNSD

Describe
Model I am using (UniLM, MiniLM, LayoutLM ...): LayoutXLM
I cannot find pretrained LayoutXLM Relation Extraction model for FUNSD dataset. It is only available for XFUN

The pre-trained LayoutXLM model can be used for both entity recognition and relation extraction. You may just fine-tuned the LayoutXLM on FUNSD.


Loading data on Lazyloading

I would like to know is there a possibility to save data on lazyloading mode, since I will be able to show also the data for more last days without any difficulties.

Can you please provide a bit more information regard your issue? Maybe provide some examples, screenshots, etc...

Hello,
According to the meaning of lazyloading ( Lazyloading is a way in which, the content of the web page is loaded as and when the user scrolls down the page. It is a popular technique being used by various websites. Advantages of Lazy loading: On-demand loading reduces time consumption and memory usage thereby optimizing content delivery) we wanted to know if there is any possibility or way to make this technique done on our chart and when a user see our chart after entering our website just face with a small part of database which is provided by our API and seeing the rest of information when zooming or scrolling on the chart by his default.

Yeah, I've knew about lazyloading, but what's problem you faced with that? It shouldn't be hard to implement it with lightweight-charts. You can 1) load the code of the library async when an user scrolls to the chart and/or 2) load your data async to insert them to the chart.

I'm going to close the issue. If you'll have any question or updates - feel free to re-open it.

@kirchet That can easily be dealt with by using a timer, some delay after scrolling with the mouse, so that not every single scroll pings the API, for side drag, I like that usage of only loading after the click has ended.

@timothymarois now there is a possibility to implement lazy loading, look at barsInLogicalRange
function onVisibleLogicalRangeChanged(newVisibleLogicalRange) {
    const barsInfo = series.barsInLogicalRange(newVisibleLogicalRange);
    // if there less than 50 bars to the left of the visible area
    if (barsInfo !== null && barsInfo.barsBefore < 50) {
        // try to load additional historical data and prepend it to the series data
    }
}

chart.timeScale().subscribeVisibleLogicalRangeChange(onVisibleLogicalRangeChanged);

That can easily be dealt with by using a timer, some delay after scrolling with the mouse, so that not every single scroll pings the API, for side drag, I like that usage of only loading after the click has ended.

You can do this right now on your side inside onVisibleLogicalRangeChanged.

@kirchet Did you scuueed in your code? I can not update historical data with series.update method.

I can not update historical data with series.update method

You should replace all data if you want to add more history bars, you need to use setData

@kirchet OK ,thank you very much


can i get the most recent template for vs2017?

hi... can i get the most recent template for vs 2017 directly from file > new > project?

nope - you have to use the dotnet sdk v2 command line as far as I understand.

@mpalmer-sps  thanks


Vector Warning in Windows Python build

Description

Compiling ITK Python wrappings on Windows produces a warning about unsigned vector operations. It is unclear what change introduced this warning.
Steps to Reproduce

Compile ITKCommon Python wrappings on Windows.
Expected behavior

No warnings
Actual behavior

...
[2018/3230] Building CXX object Wrapping\Modules\ITKCommon\CMakeFiles\ITKCommonPython.dir\itkVectorPython.cpp.obj
D:\a\1\s\Modules\Core\Common\include\itkVector.hxx(71): warning C4146: unary minus operator applied to unsigned type, result still unsigned
D:\a\1\s\Modules\Core\Common\include\itkVector.hxx(66): note: while compiling class template member function 'itk::Vector<unsigned long,1> itk::Vector<unsigned long,1>::operator -(void) const'
D:\a\1\s-build\Wrapping\Modules\ITKCommon\itkVectorPython.cpp(36974): note: see reference to function template instantiation 'itk::Vector<unsigned long,1> itk::Vector<unsigned long,1>::operator -(void) const' being compiled
D:\a\1\s-build\Wrapping\Modules\ITKCommon\itkVectorPython.cpp(3776): note: see reference to class template instantiation 'itk::Vector<unsigned long,1>' being compiled
[2019/3230] Building CXX object Wrapping\Modules\ITKCommon\CMakeFiles\ITKCommonPython.dir\vnl_c_vectorPython.cpp.obj
...

Reproducibility

100%
Versions

Environment

Windows 10
Additional Information

CDash results

It looks like the warning was first picked up on March 16th
https://open.cdash.org/index.php?project=Insight&begin=2021-09-23&end=2022-03-21&filtercount=3&showfilters=1&filtercombine=and&field1=buildwarnings&compare1=43&value1=0&field2=buildname&compare2=63&value2=python&field3=buildname&compare3=63&value3=windows

Yes, I added new Python wrapping for Vector for UL and ULL in the mesh serialization change.
Checking if it can be avoided.
Mesh Serialization
UNIQUE(vector_types "UC;F;D;UL;ULL;${WRAP_ITK_SCALAR}")

Strange that the unsigned types warning did not appear for the unsigned char type. When I rebuild without UL and ULL I do not see the warnings, though.
I think I would be in favor of suppressing and ignoring this warning. Users are already expected to be responsible for avoiding overflow with unsigned types such as itk.UL and the same responsibility should apply when working with vectors. However I would appreciate an additional perspective from @dzenanz or @thewtex .
If we go this route we can suppress the warning by adding a regex string to CTEST_CUSTOM_WARNING_EXCEPTION in CTestCustom.cmake. We currently do this to suppress a similar warning that appears from VNL vector wrappings.

I am building it without those additional wrappings however, it failed previously.
If we can't do without those wrappings then yes we have to do something similar to what you are suggesting.

Thank you @PranjalSahu !


WebExtension module

Not sure how this'll work in terms of webextension-polyfill-ts. Don't want to include a dependency like that for anyone not using it.

Similar to date-fns, this probably belongs in a separate bindings package.


Fix TestConcurrentBindUnbind error

An exception was being thrown when running the TestConcurrentBindUnbind method because DS was in the middle of binding to a service reference while another thread was unregistering the service. The sObjs.GetService call in ComponentContextImpl::AddToBoundServicesCache was throwing the exception because the ServiceReferenceBasePrivate object had been cleared out by the unregister operation and was returning an empty InterfaceMap. Changed ServiceObjects.cpp to check for the return of an empty map and handle the condition. Signed-off-by: The MathWorks, Inc<EMAIL_ADDRESS>

Codecov Report

Merging #562 (61f8a8a) into development (6f27dcc) will increase coverage by 0.37%.
The diff coverage is 46.66%.

@@               Coverage Diff               @@
##           development     #562      +/-   ##
===============================================
+ Coverage        89.82%   90.19%   +0.37%
===============================================
  Files              234      236       +2
  Lines             9480     9682     +202
===============================================
+ Hits              8515     8733     +218
+ Misses             965      949      -16

Impacted Files
Coverage Δ

...m/DeclarativeServices/src/ComponentContextImpl.hpp
0.00% <ø> (ø)

...anager/BundleOrPrototypeComponentConfiguration.cpp
84.72% <28.57%> (-6.33%)
:arrow_down:

...es/src/manager/SingletonComponentConfiguration.cpp
93.05% <28.57%> (-6.95%)
:arrow_down:

...m/DeclarativeServices/src/ComponentContextImpl.cpp
90.84% <58.33%> (-2.44%)
:arrow_down:

framework/src/service/ServiceObjects.cpp
94.11% <75.00%> (-1.07%)
:arrow_down:

...ork/include/cppmicroservices/detail/CounterLatch.h
94.44% <0.00%> (ø)

...ework/include/cppmicroservices/detail/ScopeGuard.h
100.00% <0.00%> (ø)

...ompendium/DeclarativeServices/src/SCRActivator.cpp
84.09% <0.00%> (+2.03%)
:arrow_up:

...ativeServices/src/manager/states/CCActiveState.cpp
79.24% <0.00%> (+8.19%)
:arrow_up:

.../cppmicroservices/detail/BundleAbstractTracked.tpp
83.56% <0.00%> (+9.58%)
:arrow_up:

... and 4 more


Documentation on email: defaultFrom, defaultReplyTo, testAddress

The README documentation of this package documents the following keys under exported email.settings:

from
replyTo

These values are not recognized by strapi v3 and v4, causing the default<EMAIL_ADDRESS>being used as the email FROM.
I would suggest updating the README... (or would you like a PR instead?)

hello , is this solved or not yet , if not , do we have any work around to use smtp ?

@benedictjohannes Thank you, the documentation has been updated.
@SAVE-POlNT There is no problem, only an issue with the documentation, just use defaultFrom and defaultReplyTo when configuring the provider. If you have other problems, please create a new issue detailing your case, I would be happy to help.

There is an error in the documentation for Strapi 4.
The settings object should be inside config:
module.exports = ({ env }) => ({
  email: {
    config: {
      provider: 'strapi-provider-email-smtp',
      providerOptions: {
        host: 'smtp.gmail.com', //SMTP Host
        port: 465   , //SMTP Port
        secure: true,
        username<EMAIL_ADDRESS>        password: 'my.password',
        rejectUnauthorized: true,
        requireTLS: true,
        connectionTimeout: 1,
      },
      settings: {
        defaultFrom<EMAIL_ADDRESS>        defaultReplyTo<EMAIL_ADDRESS>      },
    },
  },
});


Pass class:method to router

Is it possible to have something like:
$app->get('/', '\HomeController:home');
instead of closure function? If yes, I have not found such info in documentations, please give link or hint or sample code.

https://silex.symfony.com/doc/2.0/usage.html#controllers-as-classes

Thanks. As mentioned on docs, Silex doesn't support ORM. but here https://silex.symfony.com/doc/2.0/usage.html#route-variable-converters it seems orm is available in class. Is there any tricky way to have entity manager in controller classes?
@srsbiz

Silex does not come with ORM, but you can use one as ServiceProvider https://github.com/silexphp/Silex/wiki/Third-Party-ServiceProviders-for-Silex-2.x#database
Most service providers registers itself inside $app, so if you make your controller to accept Silex\Application  as one of the arguments, you can access its services:
$app->get('/', 'Acme\\Foo::bar');

use Silex\Application;
use Symfony\Component\HttpFoundation\Request;

namespace Acme
{
    class Foo
    {
        public function bar(Request $request, Application $app)
        {
            // for https://github.com/dflydev/dflydev-doctrine-orm-service-provider
            $em = $app['orm.em'];
        }
    }
}

Thanks for all kind helps. It works now.
May I ask please kindly help for this too? https://github.com/silexphp/Silex/issues/1562#issuecomment-341503361 I see no cookie. What is wrong in my code?

With your help, I am almost getting it. Any help about this one too please?
https://stackoverflow.com/questions/47127830/how-to-get-redirected-to-correct-page-with-silex
@srsbiz

When I use bind() like
$controllers->get('/', 'Controllers\\Login::index')->bind('login'); I get "No route found for "GET /login":" but without bind() it works fine. What is wrong?

well, this route is using / as URL, not /login

Thanks, bind() naming must be unique for each post and get? I mean
$controllers->get('/login', 'Controllers\Login::index')->bind('login');
$controllers->post('/login', 'Controllers\Login::index')->bind('login');
Is something invalid to use the same name for post and get?
@stof

Yes it does. The argument given to bind() is the route name. Reusing the same name would replace the route definition.

@stof If I have like /login/{id} then what should be the second parameter of path() as I get
exception ("Some mandatory parameters are missing ("id") to generate a URL for route "login"."). ?

Closing as support should probably be done in StackOverflow instead of here. Thanks.


can company-dict integrated to company-complete?

now i should type company-dict to popup words listed from my custom dict( or bind with keys)
is there a way that i just type company-complete instead of typing company-dict?

Whoa, so sorry for the really late reply. Yes, you can do this by adding company-dict to company-backends, like so:
(add-to-list 'company-backends 'company-dict)


Azure Cognitive Search Retrieval Example

Firstly, thank you for the amazing project. It's nice to see the prompting paradigm going away.
I wanted to check if there is an example demonstrating ACS as a retriever model?
I looked up in the docs and it has a TODO marked in there. Thank you for your time.

Few months back I had a PR for this.
Pls check below.
https://github.com/hasalams/dsp/blob/azure_cognitive_search/dsp/modules/azurecognitivesearch.py


auditd not capturing administrator actions

The bosh_audit stage adds a rule to record system administrator actions. The current configuration attempts to log actions that modify /var/log/sudo.log (https://github.com/cloudfoundry/bosh-linux-stemcell-builder/blob/master/stemcell_builder/stages/bosh_audit/shared_functions.bash#L65)
This rule is ineffective because /var/log/sudo.log does not exist.
sudoer actions are being captured, but commands entered in a root shell are not.

@xtreme-conor-nosal is this causing any issues that you are aware of?  I'm assuming that this is a suggestion to remove the line you called out here; please let me know if my interpretation is incorrect. Thanks!

This is a CIS Stemcell Hardening failure (non-repudiation of logs). The corresponding test (https://github.com/cloudfoundry/bosh-linux-stemcell-builder/blob/master/bosh-stemcell/spec/support/os_image_shared_examples.rb#L660) references CIS 8.1.16 Collect System Administrator Actions (sudolog).
The CIS remediation does call for the current configuration (-w /var/log/sudo.log -p wa -k actions), but also calls out a precondition on 9.5 Restrict Access to the su Command that isn't currently met in the stemcell:
"If the system has been properly configured to disable the use of
the su command and force all administrators to have to log in first and then use sudo to
execute privileged commands, then all administrator commands will be logged to
/var/log/sudo.log"
I believe the current sudoer configuration is logging to syslog directly, not /var/log/sudo.log, and access to su is not restricted.
Regarding CIS 8.1.16, 2 options are:

reconfigure to log to /var/log/sudo.log (following CIS's documented remediation)
verify sudo logs to syslog, remove the ineffective auditd rule, and document that CIS 8.1.16 is being met via an alternate remediation

Regarding CIS 9.5, 2 options are:

restrict su
if that's not feasible, consider remediation via additional audit rules to capture root actions, for example -a exit,always -F euid=0 -F auid>1000 -S execve -k actions to capture programs launched by a bosh_ssh user in a su shell

How about something like this:
-a always,exit -F arch=b64 -S execve -F euid=0 -F auid>=1000 -F auid!=-1 -F key=sudo_log
-a always,exit -F arch=b32 -S execve -F euid=0 -F auid>=1000 -F auid!=-1 -F key=sudo_log

It captures "root" activity of real users and you can inspect the audit log with:
sudo ausearch -k sudo_log -i
Very good article describing this problem:
https://sudoedit.com/log-sudo-with-auditd/

closing as fixed in #167


Cluster Definitions Excel Export Sheet is outdated

this sheet is outdated and needs to be replaced.  waiting on updated sheet!

Talked to Christian, an updated sheet is not required until next year.


Add road points reducing algorithm

This PR aims to do the following:

Reduce the number of sampled road points based on input threshold.
Export the road points vector for easy debugging.

This is not final PR. Some changes maybe made as per preferences -

I have added the speedup script with hardcoded path for dataset. This is because the previous configs style folder has been removed. The script can be moved and/or modified as per the project style.
Adding a flag for initializing graphics to check which road points to use for rendering is pending.

Hi Aarav,
Thanks for doing this, really excited to try this out!
I have two questions:

Have you tested whether it works correctly? Are there additional tests I can run on this end?
Is there a way to turn the road point reduction algorithm off completely? If there are bugs in it, we don't want it to influence my experiments. If so, can you add documentation/briefly explain it?
It looks like this feature speeds up the simulator speed but does not reduce the observation space. Would it be possible to decrease the size of the observations through this as well? Now the observation probably contains more zeros.

Have you tested whether it works correctly? Are there additional tests I can run on this end?
So I have tested it by running rendering. You can run it from here - https://github.com/facebookresearch/nocturne/blob/main/examples/rendering.py
However, I am going to take another look because I am not convinced that it is entirely correct.

Is there a way to turn the road point reduction algorithm off completely? If there are bugs in it, we don't want it to influence my experiments. If so, can you add documentation/briefly explain it?
Yes. You can set the reducing_threshold in the config to 0. Note the condition in the code to skip a point is using strictly less than  (<) operator. Since area can never be < 0, it will include all the points.

It looks like this feature speeds up the simulator speed but does not reduce the observation space. Would it be possible to decrease the size of the observations through this as well? Now the observations probably just contain more zeros. Tagging in @eugenevinitsky
I can take a look at how the observations are formed.

Yeah, this won't change the observation size. We'd need to change the values of num_road_points in the observation config for that. We can pick a good value for that by looking at the renderings of the agent view once we pick a threshold


s3fs fails build because of no matching fsspec

Steps To Reproduce
Steps to reproduce the behavior:

Install dvc with aws integration

Build log
ERROR: Could not find a version that satisfies the requirement fsspec==2022.8.2 (from s3fs) (from versions: none)
       > ERROR: No matching distribution found for fsspec==2022.8.2

Additional context
I am running nixos on the unstable branch.
Notify maintainers
@costrouc
@teh
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.68, NixOS, 22.11 (Raccoon), 22.11.20220926.62228cc`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.0`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Probably fsspec needs an update to 2022.8.2

Will be fixed with #195701.

Oh sorry for the noise, did not search the PRs.


Saner NSURL value mapping by default

In e798444e6e0b0f2bfe3e479d69ef7d96cedee719, the default NSURL transformer was changed to percent-escaping by default. Not only is it a bad idea in general (see this document for details), but it also means that if the JSON API you're consuming is sane and emits properly encoded URLs, which is most likely the case for most APIs, the NSURLs you get from the decoded models will be broken, with every %20 replaced with %2520 and so on. Please consider disabling the behavior by default, or at least adding a setting to opt out of it.

You're correct - this should not have happened and conflicts with #119 where I fixed it initially. Need to prevent this from being changed again.

Corrected in b5f0b466cbf83511b4c104d0f6e0e27812525626 & a75e750a3bdb308347e1629a59a09c477c4289a8. Hopefully will prevent this from happening again.


[Feature Request] disallow using deprecated angular features

I would love the linter to complain when I use anything listed on this page
https://angular.io/api?status=deprecated
adding a warning for this lot would be useful as well: https://angular.io/api?status=experimental
Any implementation of this would have to be tied into the version of angular installed in the project, but perhaps this could be done by accessing the comment defined on item. e.g: https://github.com/angular/angular/blob/master/packages/http/src/http.ts#L101

Hi @stocksr ,
Tslint offers the rule deprecated  currently.
 "deprecation": {
      "severity": "warn"
    },

We can extend this rule to handle the @experimental tag.
Thanks

Many thanks - I guess I was looking in the wrong place.


Fix clippy unused import

Trivial clean up before tackling #626

And... I didn't run fmt.
It looks like @ctron  is doing things. I'm just going to close this and wait for the dust to settle.

Just merged a few things. What I noticed is that Rust Rover indeed flags this import, but clippy does not. If that's ok with you, I'll just push the change too.

Yes, please do!


Windows.Data.Html.HtmlUtilities.ConvertToText(inputString);  tags are not supported in UWP app

[Enter feedback here]

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

ID: 26202847-c423-8281-763b-140244a9d5ee
Version Independent ID: 867bc5f0-487f-1b0c-bf01-1ec01e676048
Content: HtmlUtilities.ConvertToText(String) Method (Windows.Data.Html) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.Data.Html/HtmlUtilities.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @mcleanbyron
Microsoft Alias: mcleans

Thanks for submitting this feedback. Can you please provide more information about how you learned this information? Did a member of a Microsoft product team pass this information to you, is this something that you discovered via testing, or something else?

Thanks for taking the time to let us know about this and we sincerely apologize for the delayed response. Due to the sheer volume of feedback in our repo, we are currently prioritizing new Issues. If you believe your feedback is still actionable, let us know either directly in this thread or by filing a new Issue and we’ll work to incorporate the suggestions into the documentation. Though the Issue will be marked as Closed, we will monitor any replies that come afterwards so feel free to treat this like an open Issue. Many thanks!


Make it easier to use samples in this repo as a base for custom application

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Try extracting parts of this samples structure and build your own application.
This process is not documented, and trying to do so results in many jumps and still a lot of failures.

Any log messages given by the failure

Expected/desired behavior

Steps to do so should be clear and easy to follow.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Please add documentation showing how to get the components of these samples and build your own application, not tied to the unified cmake structure implemented here.

We will keep the design of the samples repo as is for now. Further documentation will be added as needed.


Update dependencies

I updated dependencies and devDependencies.
I replaced built-in fs with graceful-fs.
I updated .travis.yml.

Coverage remained the same at 100.0% when pulling 583678866d0a82b763de018d258e269d143dca8f on shinnn:patch into 2a0f222295eb0d2d8ce755ca0652eade7f9af90c on floridoo:master.

Thanks @shinnn!  @floridoo care to push an update? The convert-source-map dependency had some important errors fixed for IO.js.  I was just going to make a pull myself.

Created a new issue. #94

A little bit too many changes to be merged like this. I cherrypicked the important ones.
Published as v1.4.0


JS/CSS files for Latest Version

Good day,
Thank you for sharing this awesome project.
I am doing some tests with this library and I am sure this is very useful and helpful.
Just, could you do me a favor?

Could you share the js/css of the latest version files without minimization? min.js and min.css are difficult to read for me.
Hope you can help me... Thank you so much.

Oh, I'm sorry. There are not js/css of the latest release version in my PC. If you need js/css file without minimization, you can use some tools (such as jsbeautifier to convert min.js file to js file.

Yeah, but all the variable names are replaced in min.js.
So even I use jsbeautifier, it won't get enough source which is readable.
I tried to build the project in debug mode but couldn't maybe cause of the different version of npm or node.
Would you build the project in debug mode and get js files? Don't you have the environment for it on your machine?

This is js/css file build in my machine. It maybe a little difference from the release version.
interactive-graph.zip
And this is the environment, it might help you.

nodejs: 11.15.0
npm: 6.7.0

Thank you !!!


Laravel Linter

This pull request includes changes and recommendations for crafting your application "The Laravel Way". Feel free to commit any additional changes to the shift-59491 branch.
Before merging, you need to:

Checkout the shift-59491 branch
Review all pull request comments for additional changes
Thoroughly test your application

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

:warning: The following classes do not extend the standard Laravel Model and Controller class. This may add complexity which makes your application harder to upgrade. Often a trait can be used instead of inheritance. You should review the following classes:

[ ] app/Models/Address/MiningAddress.php
[ ] app/Models/Address/WitnessAddress.php

:warning: The following controllers contain actions outside of the 7 resource actions (index, create, store, show, edit, update, destroy). For more details, review the docs or watch Cruddy by Design to see if you can rework these into resource controllers.

[ ] app/Http/Controllers/AverageBlocktimeController.php
[ ] app/Http/Controllers/DifficultyHashrateController.php

:warning: Shift found inline validation in the following controllers. Unless you require this level of control, you should use a Form Request to encapsulate this validation logic and keep your controller clean. You may automate this conversion with the Laravel Fixer.

[ ] app/Http/Controllers/Auth/ConfirmablePasswordController.php
[ ] app/Http/Controllers/Auth/NewPasswordController.php
[ ] app/Http/Controllers/Auth/PasswordResetLinkController.php
[ ] app/Http/Controllers/Auth/RegisteredUserController.php
[ ] app/Http/Controllers/DifficultyHashrateController.php

:information_source: Shift detected controller namespaces being set in your RouteServiceProvider. Laravel 8 began registering controllers using static class references instead of namespace prefixes and controller names.
You may automate this conversion using the Laravel Fixer or tasks within the Shift Workbench.

:warning: Shift found the following config files differ from the defaults. While you are welcome to customize your configuration, you should leverage ENV variables rather than hardcode values. If you find you're adding a lot of configuration options, consider creating a domain specific config file, such as core.php. Both will make app upgrades and deployments easier.

[ ] config/app.php
[ ] config/auth.php
[ ] config/cache.php
[ ] config/queue.php

:information_source: As noted, much of the lint detected above can be automatically fixed using the Laravel Fixer. Save yourself time and clean up your codebase quickly with this new Shift.

:warning: Laravel uses PSR-4 autoloading for the app/ folder. While you can configure your application to load these files within composer.json, all files under the app folder should be classes with a PSR-4 compliant namespace.
The following PHP files are missing a namespace:

[ ] app/helpers.php


Add createOrUpdateFromArray method to RLMObject

That might not be the exact naming, but the idea would be to do upserts given an array of objects
Currently there is an addOrUpdateFromArray http://realm.io/docs/cocoa/0.90.6/api/Classes/RLMRealm.html#//api/name/addOrUpdateObjectsFromArray:
This was brought up here https://github.com/realm/realm-cocoa/issues/1573

It's trivial to loop over an array and call this on its members so I really don't think we should do this. This is also why we have -[RLMObject initWithObject:] but not initWithObjects:.

I think this will make more sense when done on the Realm, that example does make it look a bit weird


Adding --testCA for testing on Let's Encrypt staging API

with --testCA parameter, you can use staging API with all commands without moving any files or changing configuration.
Solves #92 with minimal changes to code and configuration.

I'm not entirely sure if this option makes sense... It adds a lot of code that could just be replaced by a few lines of config... And I don't find this very practical either since it may resign perfectly fine valid certificates with staging ones if used incorrectly.


docs: Add removal of dryRun to migration guide

Fixes https://github.com/getsentry/sentry-javascript-bundler-plugins/issues/396

@lforst @Lms24 Is there an alternative to dryRun that is supported now?


Changelog needed

Gonna need to add a changelog and kick it off with the changes from #16 and #24

I like to stick a list of changes here when making a new relase:

So not creating a changelog? just documenting it in the latest release?

In the past, I've maintained a CHANGELOG.MD and copied into the latest release, but I'm not sure you need to do both anymore. I know I check releases first. It's come a long way and it's a clean way to do it.

Makes my life easier 😜  Releases it is!


case agreement

verb should be plural like the subject (contents).
describe your changes...

[x] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[x] Make sure your PR complies with the writer's guide.
[x] Review the diff carefully as sometimes this can reveal issues.
Remove these instructions from your PR as they are for your eyes only.

Thanks!


Remove CopyFromUri

I'll remove this API from current release as it hasn't been approved by Arch Board. I'll add it back in next release.
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/azp run cpp - storage


messages: specify a response for each request

Getting closer to JSONRPC and have a proper Request / Response flow makes it easier for us to know if the Coordinator actually stored our stuff (in the "Coordinator isn't evil" case).
Based on #89

ACK c73af1e


v1.2.0 planning

We have lot of content for 1.2.0, anything missing for a new release?
https://github.com/lima-vm/socket_vmnet/milestone/8?closed=1
I think the most important for the release is improved logging:
https://github.com/lima-vm/socket_vmnet/pull/46

Sure, after merging:

https://github.com/lima-vm/socket_vmnet/pull/94

https://github.com/lima-vm/socket_vmnet/releases/tag/v1.2.0


Can you add a LICENSE file?

Please add a license file so that people know if they can use or contribute.

Definitely, thanks for opening the issue. I'll get one in shortly. I'd be thrilled to have people using this and contributing!

Done. I'm happy to take any PR's, and feel free to open up issues for discussion

Will do. Thanks.
On Mon, May 29, 2017 at 12:24 PM, aviaviavi<EMAIL_ADDRESS>wrote:

Done. I'm happy to take any PR's, and feel free to open up issues for
discussion
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aviaviavi/legion/issues/1#issuecomment-304569567, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ASyuUetLFp8VhzEjgavMsfGAmBaJuRbEks5r-kh_gaJpZM4No4UQ
.


Wipe wallet causes crash

If the user has a wallet and wants to import a new one they must fill in the seed again to delete the datastore.
When they are successful entering the seed and alertview shows that asks the user to  "Wipe Wallet?"
When done the app crashes to a black screen

This has been fixed in the lates releases AFAIK.

Closing due to duplicate issue (#41)

It doesn’t crash to black screen now, it seems to lock up at the “wiping” screen and does not ask for seed or passcode to wipe wallet. v2.3.5


⚠ Bofrost.nl has degraded performance

In 0354ccf, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 850 ms

Resolved: Bofrost.nl performance has improved in 1baf10a.


Fixup tests for OSX

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

@ocefpaf can we merge this one too? it just fixes the downstream tests for OSX that were failing before.
Thanks @isuruf for finding the source of the problem.

Downstream tests should use https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#downstream-tests to avoid cycles.

will that simply run the downstream test section? I should remove the custom commands and file I added right?

yes to both

Does opencv need to be rerendered?https://github.com/conda-forge/opencv-feedstock/issues/220

Yes. Looks like it. There's also an issue with conda-build at https://github.com/conda/conda-build/issues/3908

yeah, this isn't really that good, it defaulted to a really old version of opencv 3.4 (3.4.2) which I don't think you or I maintain.

Lets try again when: https://github.com/conda-forge/opencv-feedstock/pull/221
merges

opencv was merged, but no job is running on master?

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@isuruf I really can't understand the conflict, but maybe i'm missing something.
What is the way forward? Do I comment out the opencv test and rebuild opencv when this is pulled in?

@hmaarrfk sorry, I let slip through the cracks. Do you still want to rebase it? If not I can try to fix this PR so we can work on the latest version.

honestly, i'm really not sure what the current status of the feedstock is.
Would have to redo this work. Maybe lets leave it open until one of us has a chance to do it.?

Maybe lets leave it open until one of us has a chance to do it.?

Tried and failed miserably :smile:
I'll try to find more time and tackle this again later this week. Thanks!

I just manually copied over the idea of the changes.


zookeeper situation and multi-node

Hi there,
1).Who can tell me the situation about zookeeper version and deployment?
2).It's happy to see that the streaming-benchmark had been upgraded to the latest version, and shown
the test result, but could anybody give more details about the operations for multi nodes?
Thanks a ton!

I have tried to run the benchmark in the zookeeper 3.4.10 and it works fine. But it runs in a single-node environment.


ESP32 - Windows Setup Issue (IDFGH-10375)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hi there,
  I am trying to setup the Espressif on Windows laptop. I am getting following error when I run the install.bat command:

I have made the following edit in the requirements.txt file:

After following these steps, I am still getting the same error.
For convenience, Here is what in my requirements file:

Can anyone please assist with this issue?

Probably this is what you are looking for: https://github.com/espressif/esp-idf/blob/release/v4.4/requirements.txt
But be aware, v4.3 is in maintenance period, that means it is not recommended for new designs. If you can then consider using a newer version which is still in service period.

I have double-checked that the fix has been backported to v4.3 as well: https://github.com/espressif/esp-idf/blob/release/v4.3/requirements.txt, here: https://github.com/espressif/esp-idf/commit/f9e52727279180f5f5ec4acb7996f01e92b40e06.


Project Documentation

Create docs folder with Markdown files. Markdown can then be exported to readthedocs. Documentation should make it easy for sysadmins and designers to get started quickly.
Because the project consists of stitching software together, this puzzle needs to be explained.
Experiences and project management and thesis related thing should not belong to the project documentation.

I want to keep the documentation on our own http://osm2vectortiles.org page where we also provide download links, introduction etc. We can still write Markdown like before and just use Github Pages. That's the easiest way to do it where we have the most control.
Read the docs gives better options (with Sphinx and restructured text) for generating documentation but by controlling the page ourselves we can make it look better and more uniform and can also build our own custom stuff into the page (like Mapbox GL samples or data comparisons).
Changes on http://osm2vectortiles.org/ are online (not looking good on mobile though).

I don't know where to best put this but a few things I noticed when we talked with people about the project

People care about labels and label ranks -> new idea there was using Wikipedia links of OSM data to determine importance (but that's a topic for itself)
People don't like that data in the vector tiles might be missing because it is not considered important by us
People do like that there is an open alternative to the all mighty Mapbox
It was asked pretty quickly, how the MBTiles would get updated
Disputed borders really are kind of a undecided problem. People map the border and set disputed=yes. And borders are the relations that are updated the most.
People are also interested in rendering MBTiles themselves (so making our PostGIS / export stack approachable would make also sense - it is not just for us)
Documentation will be absolutely crucial - explaining the project on the site and helping as fast as possible to get to the goal of MBTiles is important
Packaging tessera/Mapbox GL locally makes for an extrem good demo use case even though it is perhaps of limited use. One can just give the people an executable (on a branded stick?), they click on it and choose an MBTiles and voilà - a nice map rendered from own data from OpenStreetMap. This will get people talking. Docker while very powerful and actually the end goal is an additional obstacle when just trying to get started as fast as quickly (My guess is especially for Windows people)

Improved documentation for usage on a small OSM planet dumps (cities extracts, etc) without the cluster is necessary... ensure and test the main export docker runs directly - without access to cloud buckets and queues - if the AWS variables are not set by the user...

We decided to take a question based approach with the documentation. We write down the most common questions which will probably be asked, and answer them with tutorials and text. The separation between user and dev documentation will stay.
User Documentation
The user documentation describes how to get started with OSM Vector Tiles and how to create a custom style.
Dev Documentation
Whereas the dev documentation focuses on which data is included, how to host them, creating own extract, adding own data.


fix: Ensure that outstanding workflows are only run once

Fixes: https://github.com/argoproj/argo/issues/4392
This reverts #4294 and adds additional fixes.

Lets chat about the correct solution to this at stand-up.

Let me get this right:

The fix of the locking contention + patch fix introduced a race condition between Run and runOutstandingWorkflows that can result in race?

Could we fix that race using KeyLock like we do in the normal controller?

Not exactly sure, I actually have more curiosity about the CronWorkflow informer... I'm thinking we should add the write-back and the 1 second sleep fall-back that we have in the Workflow informer.
Regardless of this, there was an issue with runOutstandingWorkflows calling Run, but not returning from the current context, which it should do because after it calls Run, the CronWorkflow object will be persisted, and the current context will now be invalid.

Closing in favor of https://github.com/argoproj/argo/pull/4440

Not exactly sure, I actually have more curiosity about the CronWorkflow informer... I'm thinking we should add the write-back and the 1 second sleep fall-back that we have in the Workflow informer.
Regardless of this, there was an issue with runOutstandingWorkflows calling Run, but not returning from the current context, which it should do because after it calls Run, the CronWorkflow object will be persisted, and the current context will now be invalid.

I encountered similar problem that cron sometimes executes 2 workflows when parallelism is replace. So, how did you solve this problem?


Add sendMessage Method

Added a sendMessage method for sending Messages across the Network.

This doesn't compile

What?


Add relative position, remove poise

This is a major rewrite of the firewall cookbook, however tests were only slightly adjusted to regex matches. The major changes in this version include:

Breaking change: chef actions have been split out from firewall rule actions (e.g. a rule now always runs action :create, but uses command :drop or :accept)
Breaking change: :save action has been removed from firewall. All providers except firewalld are persistent by default.
Remove poise dependency. Providers and resources now extend LWRP base classes.
Ubuntu support for iptables has been split out into a separate provider to make it cleaner.
Mixlib:ShellOut and most non-chef firewall logic has been placed in helper libraries that don't depend on Chef. Providers and resources are the only things that depend on Chef. This should aid in further testing.

@someara @coderanger @rdoorn @bison I'd love to get any feedback on this if you have a spare moment. Thank you!

Nice! A quick skim makes it looks like each provider work a lot more like the iptables cookbook, which is a big plus :)
I likely won't have time to evaluate before you'd want to merge, but I'll check it out when i have time for a rewrite of our firewall stuff

Hi @martinb3 nice work on the cookbook!
could it be that it uses some chef 12 features that don't work in chef 11 clients?
I've loaded the cookbook in a chef 11 environment, and am getting a compile error
Chef::Exceptions::InvalidResourceSpecification
----------------------------------------------
You must specify `resource_name'!

Cookbook Trace:
---------------
  /var/chef/cache/cookbooks/firewall/recipes/default.rb:20:in `from_file'
  /var/chef/cache/cookbooks/idb_firewall_wrapper/recipes/default.rb:11:in `from_file'

Relevant File Content:
----------------------
/var/chef/cache/cookbooks/firewall/recipes/default.rb:

 19:
 20>> firewall 'default' do
 21:    action :install
 22:  end
 23:

in my wrapper i call it like this:
include_recipe 'firewall::default'

just incase you wonder ;-)
If this is not a chef 11 thing i'll see if i can dig in to this deeper once i have some time...
Thanks for the efforts!

@rdoorn I've pushed a new commit that should resolve the chef 11 compatibility issue. Can you give it a try again? Thank you!!

Ok, haven't read through completely, but one thought, perhaps for later (as this seems fine). It seems that right now, we're building the whole ruleset internally, and hiding our positioning logic. So the position information isn't clearly on the node's filesystem post-converge. Assuming rules are spread across quite a few cookbooks, it might be a bit of indirection to track down the positions of other rules to know how to get yours in the right place. (ie. oh, I want mine in front of the rule that sets port x, so what cookbook manages something that wants that port? Ok, figured that out, now search and find out what position it sets.)
An alternative might be to do what the iptables cookbook does, which seems very transparent: it creates a /etc/iptables.d/ directory and drops each rule in there, and then concatenates them when building the ruleset. Using the zap cookbook would solve for unexpected behaviour of files sticking around. The nice side-effect is that this uses the lexical sorting order for positioning in the generated ruleset. If we wanted to emulate their approach, we'd just convert position to a two-digit string (ie 07 and prepend it to the filename the rule file in /etc/iptables.d/ or whatever.
Anyhow, just a thought. That approach would strike me as more clear to troubleshoot if you've got lots of rules from different cookbooks :)

@patcon thank you for reviewing! In the case of looking at the positioning logic, one option is literally to do a firewall resource lookup and dump the contents, e.g.
  pp resources(:firewall, 'default').rules

Maybe we should put that in the documentation as a way to see what rules exist and/or for troubleshooting. We could also emit a comment in the ruleset file with the position, as sort of a compromise between what we have now (one big file) and writing every rule out to a file, too.
I'm wary of doing anything too elaborate, for fear of having to scale it to other firewall technologies. E.g. we have a PR currently for a Windows implementation.

heh no problemo! Honestly, less need to document = better imho.  Dropping position in comments also deals with the concern perfectly, so whichever your prefer :)

Examples:
             +ufw allow in proto tcp to any port 7788 from any # position=5
             +ufw reject in proto tcp to any from <IP_ADDRESS> # position=49
             +ufw deny in proto tcp to any port 1236 from any # position=50
             +ufw deny in proto tcp to any port 1234 from any # position=50
             +ufw reject in proto tcp to any port 1235 from any # position=50
             +ufw allow in proto tcp to any port 2200,2222 from any # position=50
             +ufw allow in proto tcp to any port 22 from <IP_ADDRESS>/0 # position=50
             +ufw allow in proto tcp to any port 1111 from any # position=50
             +ufw allow in proto tcp to any port 5431,5432 from any # position=50
             +ufw allow in proto tcp to any port 22 from any # position=50
             +ufw allow in proto tcp to any port 80 from 2001:db8::ff00:42:8329 # position=50

iptables example:
             +# position=1
             +*filter
             +# position=2
             +:INPUT DROP
             +# position=3
             +:FORWARD DROP
             +# position=4
             +:OUTPUT ACCEPT
             +# position=5
             +-A INPUT -p tcp -m tcp -m multiport --dports 7788 -m comment --comment "prepend" -j ACCEPT
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 1234 -m comment --comment "temp1" -j DROP
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 22 -m comment --comment "ssh22" -j ACCEPT
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 2200,2222 -m comment --comment "ssh2222" -j ACCEPT
             +# position=50
             +-A INPUT -m state --state RELATED,ESTABLISHED -m comment --comment "established" -j ACCEPT
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 1235 -m comment --comment "temp2" -j REJECT
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 1236 -m comment --comment "addremove" -j ACCEPT
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 5431,5432 -m comment --comment "same comment" -j ACCEPT
             +# position=50
             +-A INPUT -p 112 -m comment --comment "protocolnum" -j ACCEPT
             +# position=50
             +-A INPUT -s 2001:db8::ff00:42:8329/128 -p tcp -m tcp -m multiport --dports 80 -m comment --comment "ipv6-source" -j ACCEPT
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 1111 -m comment --comment "same comment" -j ACCEPT
             +# position=50
             +-A INPUT -p tcp -m tcp -m multiport --dports 1236 -m comment --comment "addremove2" -j DROP
             +# position=100

(iptables doesn't like lines that end in comments, unfortunately)

Ah, I was thinking using the comment module itself, so that it's right in the iptables -L output?

The problem I've encountered is that not all all modules support it. Specifically, there were some distros where ipv6 + comment was unsupported.

Ah ok :+1:


Generic append properties, and *bool support

It is common for build logic to append the values of two property structs together.  The first patch provides generic AppendProperties and PrependProperties to append property structs of the same type, and AppendMatchingProperties and PrependMatchingProperties to append the values in a property struct to any matching properties in a list of destination property structs.
The second and third patches add tests and fix bugs in CloneProperties, CloneEmptyProperties, and ZeroProperties.
To make AppendProperties easy to use appending an unset property should not change the destination property.  This means appending a zero value property must be a no-op.  The only way to accomplish this for a bool property is to OR the two values together, but this is usually not the semantics needed by the build logic.
The fourth patch fixes lists to properly differentiate empty and unset.
The fifth patch adds support for *bool properties with identical syntax to bool properties, but with replace-if-not-nil append semantics.  *bool also provides a better replacement for ContainsProperty, which can only tell if the value was set by a blueprints file, and not set later by a mutator.  *string support is added for the same reason, but has the same append semantics as string.

LGTM

I added one more patch to recursively compare types in property structs, which is useful when using AppendProperties on lists of structs of unknown types.

LGTM


fix(argocd): remove dist-dynamic folder

Description
This is a followup PR to  - https://github.com/janus-idp/backstage-showcase/pull/1697 and aims to load the argocd plugins correctly as a dynamic-plugin. This PR contains the following changes

removed the dist-dynamic folder as this is applicable only for the backend dynamic plugins.
Fixed the scalprum name and updated the correct argocd-plugin entry into the internal DynamicPlugin list.
updated the unit tests.

Remove already generated dist-dynamic folder
Which issue(s) does this PR fix
BLOCKER ISSUE - https://issues.redhat.com/browse/RHIDP-4200
How to test:
Add this in the dynamic-plugins.yaml configmap
  - package: ./dynamic-plugins/dist/backstage-community-plugin-redhat-argocd
    disabled: false

/retest

I have verified this changes using the image quay.io/janus-idp/backstage-showcase:pr-1699 in the cluster, Now it is dynamically loading the argocd plugin properly.
Overview page:

CD tab:

lgtm

/cherry-pick release-1.3

/cherry-pick release-1.3


Allow searching outside google folder for a gapic directory

Thanks @Katee! I'm OK with this change, let's just have the new logic covered by a unit test.


Add settings to enable/disable different types of expensive queries independently

Is your feature request related to a problem? Please describe.
The granularity of the setting allow_expensive_queries is a bit coarse.
This setting enables/disables ALL the following query types:

Queries that need to do linear scans to identify matches

script queries

Queries that have a high up-front cost

fuzzy queries (except on wildcard fields)
regexp queries (except on wildcard fields)
prefix queries (except on wildcard fields or those without index_prefixes)
wildcard queries (except on wildcard fields)
range queries on text and keyword fields

Joining queries
Queries on deprecated geo shapes
Queries that may have a high per-document cost:

script score queries
percolate queries

Describe the solution you'd like
I would like there to be settings for each type and have the allow_expensive_queries override them all on true for backward compatibility (default is true).
Describe alternatives you've considered
preventing certain query types in an external service outside the cluster.
Additional context
Some exceptions to the allow_expensive_queries should be made so we can enjoy the benefits of different query types while remaining protected from other expensive types.

Ok, gonna open a branch and start working on this today:)

I am going to shelf this issue. Coming back to it later. If anyone wants to pick this up be my guest:)
I will touch base later to see if I can prioritize this.
Researching the issue led me to wonder if we should be implementing a more sophisticated pattern that takes into account RBAC if the Security plugin is in use.

A low hanging fruit that may have more value as well is the indices.query.query_string.allowLeadingWildcard setting - turning it into a dynamic setting and perhaps adding rules (allow per index pattern for example) would make this more usable. I will open a separate issue for that though :)


adding sample files

e2e sample that demonstrates:

calling cswinrt on a C++/WinRT runtime component to generate projection
creating nuget from projection
referencing nuget in a NET5 console app

don't check in nuget.exe