process: avoid the possibility of some commands hanging indefinitely

Currently, if we're trying to stop or start processes and waiting for them
to become stopped or running, that wait will wait indefinitely if
some concurrent command starts or stops one of the processes while
we're waiting, because the wait waits only for the expected state.
Fix this by always waiting for a steady state (e.g. Running, Stopped, Fatal),
and then checking that the steady state is the one that we're expecting.
We avoid a race condition by adding a reply channel to the request
that allows the process to notify the caller when its state has been
initially updated in response to the request.

I reviewed this PR and it looks good so far – this will be a nice improvement to consistency and stability.


Divide two numbers

Description
Input  : 2 4
Output : 0.5

Program added successfully :tada:
Thanks for your contribution :hugs:


kaboom 100 b64 added in after section doesn't execute

Describe the bug
I added kaboom 100 b64 to after section and after .nuke it doesn't run.
 Enter some testing server.
3. Execute .nuke
4. After deleting everything it doesn't create any chanels.
What did you expected to happen
That C-REAL will execute kaboom 100 b64 and 100 channels will appear.
What actually happened
It just nukes and doesn't execute kaboom in after section.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
C-REAL version 2.4.0

I was able to reproduce the bug
I'm going to take a look into this

I have fixed this bug
It looks like disabling community mode no longer works due to some weird discord backend update (this is what I assumed don't take my words for it)
You should be able to pull the fixed version from the main branch

Now it works!!!!
Thanks.


Improving Password Generator project

Project name
Password Generator
Project link
Password Generator
Problem
The field password length is a required field but it is not indicated to the user.
Improvements suggested

[ ] 1. Add Required field * against password length field
[ ] 2. Add a pop-up of 'required field' in case a user submits before entering the length
[ ] 3. Add a drop-down with integers in the password length to make it easier for user to select the length

@khushi-purwar can I get this issue assigned to myself?

@devgirlcodes you can start working on this issue.


feat(source-installation): recommend installation via Ansible over manual installation

Description
I see many people on social media doing manual installations instead of automated environment setups using Ansible.
Manual installation is difficult and many people fail.
Therefore, I have changed to recommend automatic environment setup using Ansible.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@xmfcx @esteve Any opinions would be appreciated. :pray:

@xmfcx
Thank you for your advice.

I'd still prefer to keep manual installation steps under a separate heading instead of a Note section.

Do you mean to create a manual installation page in troubleshooting or somewhere else?
If you give us more details, I may be able to do ti.

But I leave the decision to you @yukkysaito . But I am sure some people will complain that Ansible method has made unwanted changes on their system, time will tell.

In japan, many people say installing Autoware is too difficult. also, installing Autoware is called "Autoware challenge".
I am afraid that if this situation continues, the number of people who use Autoware will decrease.
Therefore, I wanted to recommend ansible to simplify the procedure.
However, you are right that it may cause more trouble by using ansible.
Regarding that, I would like to improve troubleshooting, etc. in the future.

I've made some rephrasing of some sentences along the way. After you review them, I think we can merge this.

Thank you very much. I committed the fix.

@kenji-miyake @xmfcx @yukkysaito Sorry, didn't see this before. I still prefer the manual installation and I think it's not good for users to have their environment changed via a script without their control (see for example installing rocker via sudo pip vs sudo apt-get).
However the work done in https://github.com/autowarefoundation/autoware/issues/3222 should largely make some of the Ansible steps obsolete, since users will be able to install Autoware directly from Debian packages (see https://github.com/esteve/autoware_packages/tree/jammy-humble for an APT repository that users can already use to install Autoware).
In any case, as long as the manual instructions are kept and that the Ansible scripts do not modify a user's environment without their consent, I'm fine.


ocamlPackages: add crowbar, enable crowbar tests

Motivation for this change
Add crowbar, an afl based test framework, which some test suites in ocamlPackages depend on (index and eqaf as far as I know which have their test suites enabled in this PR).
One issue this PR currently has is that it probably doesn't make sense to run the crowbar tests on a compiler which does not support afl. We could detect afl and enable/disable the tests like this (although its not nice):
{
  doCheck = lib.hasInfix "afl" ocaml.name;
}

However, this has another issue: The affected packages have a normal test suite as well which doesn't require crowbar. Selectively activating and deactivating parts of the test suite could become rather cumbersome and I think it is not really that big of an issue since crowbar runs and compiles without any errors even when afl is not enabled.
Note that this PR also includes the eqaf update from #88467.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@grahamcofborg build jackline ocamlPackages.irmin-unix

@GrahamcOfBorg build jackline ocamlPackages.irmin-unix

@GrahamcOfBorg build jackline ocamlPackages.irmin-unix

The eqaf test just failed for me, will investigate.

I think it failed on me once in nixpkgs-review, but I can't reproduce it anymore, maybe someone else can run the tests as well (eqaf tests take forever unfortunately).

@GrahamcOfBorg build ocamlPackages.afl-persistent

afl-persistent has been merged into master as 0679fb9696a275291e3ea7ad4977e6b72f57e6be

@GrahamcOfBorg build ocamlPackages.crowbar

@GrahamcOfBorg build ocamlPackages.crowbar

@GrahamcOfBorg build ocamlPackages.index

crowbar has been merged into master as 1c7fd15a423cf26590207dd9c133fba051a55af6

Is it wise to enable tests that “take forever”?

Probably not, since then builds will timeout all the time, although it'd be nice to have eqaf tests since it is kind of a security sensitive library. Hydra has a build timeout right?


Can't assign folder path with special characters

I assigned a slice to open a certain folder, but when I try to open it, I get the following error:
---------------------------
PieMenu.ahk
---------------------------
Cannot find directory:
C:\Users\user\OneDrive - NÃ‰RY\Ãrea de Trabalho\FlÃ¡vio\AutoHotkey
---------------------------
OK
---------------------------

I presume this is because the file path has special characters. Is that right? Is there a way for me to manually correct this?

Could you paste what the intended path is including special characters here?  I may be able to account for this on my end.
You can export the settings file (File > Export Settings) edit that json file and then import it.

This is what it is supposed to look like:
C:\Users\flima\OneDrive - GERALDO NÉRY LOPES ADVOGADOS ASSOCIADOS\Área de Trabalho\Flávio\AutoHotkey
Checking the .json file, this is what was there:
C:\\Users\\flima\\OneDrive - GERALDO NÉRY LOPES ADVOGADOS ASSOCIADOS\\Área de Trabalho\\Flávio\\AutoHotkey
Changing the double backslashes to single ones had no effect and produced the same error message.

Thanks!  Looking into this now, seems like AHK just doesn't handle special characters in filepaths on its own, but everything on the frontend is working fine.  This should be fixable on my end.

Great, thanks for the feedback!

Still working on this, for the time being all I'd say is don't use special characters in filepaths, but I plan on having this fixed before any "official" release.
In case anyone can assist, the issue is the JSON.ahk library I'm using to read json files.  Special characters in value strings get misread.  Currently I'm trying to modify this library to fix this, unless there is another AHK library out there to handle this.

That's great to hear! I can change file paths in my own PC, but since this script will be particularly helpful to me at work, and I can't change file paths there, knowing this will eventually be addressed is nice. Thanks for this great script!

omg the solution ended up being really simple.  This is fixed in v1.0.17-alpha.

Just tested and it works! Thank you very much!


SHACL-SPARQL

It would be very useful to extend the capabilities of SHACL to include SPARQL based contraints.
My specific use case is to detect duplicate values of a property across all entities in a data graph, which is something SHACL Core cannot do AFAIK.
This feature request is referring to the draft SHACL Advanced Features 1.1 Specification
https://w3c.github.io/shacl/shacl-af/

I’ll look into it. I just finished a major update to the SPARQL gem, so it’s a good time to look back into shacl.

Much of what you want should now be on the develop branch, but depends on unreleased features added to the rdf and sparql gems. Try running with a Gemfile based on the one in this repository.
More work to do for SPARQL-based Constraint Components and more Advanced Features. You should be able to use use all the features described in SPARQL-based Constraints.

Amazing. I’ll test out some SPARQL based contraints that I need in my projects and let you know how it goes :-)

Hi.  I have a simple SHACL-SPARQL in this repo that is not working as expected. Running bundle exec ruby test-country.rb does not produce a shacl:Violation with the sh:SPARQLConstraint. The example is text book.  I am loading 'develop' branch gems. So for now I am blocked.

Thanks for the example. That essentially duplicates a passing test case from the shacl test suite, so may be some other setup issues. Should have it straightened later today.

I notice that the property shape includes sh:minCount 2, and none of the tested objects has more than one property value for ex:germanLabel. If you remove that constraint, your test passes, but it ends up that's a false positive.
Additionally, the query uses the prefix ex, but it is not defined. In the original test, it would be defined where referenced using something like:
<http://datashapes.org/sh/tests/sparql/node/sparql-003.test>
  sh:declare [
      rdf:type sh:PrefixDeclaration ;
      sh:namespace "http://datashapes.org/sh/tests/sparql/node/sparql-003.test#"^^xsd:anyURI ;
      sh:prefix "ex" ;
    ] ;

In the test suite, the data graph and the shapes graph are combined, and this was masking a problem creating an aggregated repo containing them both (which is required for some use cases). It ends up you're missing  a develop gem:
gem 'rdf-aggregate-repo', git: 'https://github.com/ruby-rdf/rdf-aggregate-repo.git', branch: 'develop'

Try again using the develop version of rdf-aggregate-repo, and either adding property values to satisfy minCount, or remove that restriction, as well as either making the PREFIX definition explicit in the query, or with a properly scoped sh:declare. You can also add a logger: option to SHACL.open (should/will be able to with shacl.execute that can emit some runtime detail and/or add SXP::Genrator.print(shacl.to_sxp_bin) to get some insight into the parsed SHACL constraints.
(shapes
 (
  (NodeShape
   (id <http://example.com/ns#LanguageExampleShape>)
   (type shacl:NodeShape)
   (targetClass <http://example.com/ns#Country>)
   (PropertyShape (path <http://example.com/ns#germanLabel>))
   (sparql
    (type shacl:SPARQLConstraint)
    (message "Values are literals with German language tag.")
    (prefix
     ((ex: <http://example.com/ns#>))
     (project
      (?this ?value ?path)
      (extend
       ((?path ex:germanLabel))
       (filter
        (|| (! (isLiteral ?value)) (! (langMatches (lang ?value) "de")))
        (bgp (triple ?this ex:germanLabel ?value))) )) )) )) )

Result I get after removing the minCount constraint is:
false
Result for: "Spain"@en
  focus: <http://example.com/ns#InvalidCountry>
  path: <http://example.com/ns#germanLabel>
  shape: <http://example.com/ns#LanguageExampleShape>
  resultSeverity: shacl:Violation
  component: shacl:SPARQLConstraintComponent
  message: "Values are literals with German language tag."

Thanks for your detailed response. I was able to get it to work as expected. My problem was the undefined PREFIX ex: that you pointed out. I had the PREFIX ex: defined in the shape turtle, but not scoped or defined explicitly in the SPARQL query.  Also, thanks also for the logger: option. Very helpful.


Editable column does not redraw the checkbox after editing

Hi,
I just noticed that when using a column as editable, that uses a checkbox for selection, after editing the field the checkbox is not redraw.
Please take a look at the example http://www.angulargrid.com/example.html

Select Editable Yes.
Edit the Name column.

You will notice the checkbox is not redraw
regard,

Thanks for creating the issue. This is on my list.
On 7 Apr 2015 19:06, "jdcaballerov"<EMAIL_ADDRESS>wrote:

Hi,
I just noticed that when using a column as editable, that uses a checkbox
for selection, after editing the field the checkbox is not redraw.
Please take a look at the example http://www.angulargrid.com/example.html

Select Editable Yes.
Edit the Name column.

You will notice the checkbox is not redraw
regard,
—
Reply to this email directly or view it on GitHub
https://github.com/ceolter/angular-grid/issues/48.

This is now fixed.


really disable risky functions

Ready for review
Tested with PHP 5.6, 7.0, 7.1, 7.2, 7.3, 7.4 and 8.0.0beta4

See https://www.php.net/manual/en/ini.core.php#ini.disable-functions

@Whissi FYI, this package was requested by user of my repository, the reason why I look a bit on it
(I don't use it myself)
See https://blog.remirepo.net/pages/PECL-extensions-RPM-status
And https://forum.remirepo.net/viewtopic.php?id=4043


Symbiotic prepare phase fails when sigaction is used

This code gives ERROR (Prepare phase failed),
but when signal is used instead of sigaction it works fine.
#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#include <unistd.h>
void handler(int);

int main (void)
{
    struct sigaction sa={
        .sa_handler=handler
    };
    sigaction(SIGTERM, &sa, NULL);
    return 0;
}

void handler(int signum)
{
    kill(SIGKILL,0);
}

Tested with release symbiotic-5.0.1

I can reproduce the crash, thanks. By the way, symbiotic does not support any asynchronous actions (like signals) as KLEE does not support them, so it may miss bugs in code that uses them.

The crash should be fixed by the latest commit. However, the inability to work with signals cannot be fixed that easily.


kubectl get serviceexport with "-o wide" does not show more info

$ oc get serviceexport "nginx-cl-b"
NAME         AGE
nginx-cl-b   9m7s

$ oc get serviceexport "nginx-cl-b" -o wide
NAME         AGE
nginx-cl-b   9m13s

What would you like to be added:
Please show more info with the "-o wide" option enabled.

What more information would you like to see? Other than the standard k8s metadata, ServiceExport has a Status field that is an array so wouldn't seem suitable as columnar data. For that use '-o=yaml' or kubectl describe.

Looking at:
$ oc get serviceexport "nginx-cl-b"  -o yaml

apiVersion: lighthouse.submariner.io/v2alpha1
kind: ServiceExport
metadata:
  creationTimestamp: "2020-07-26T05:32:51Z"
  generation: 2
  name: nginx-cl-b
  namespace: test-submariner
  resourceVersion: "6803005"
  selfLink: /apis/lighthouse.submariner.io/v2alpha1/namespaces/test-submariner/serviceexports/nginx-cl-b
  uid: 70db9f33-4aa5-4aca-ae13-23439eac7655
status:
  conditions:
  - message: Service was successfully synced to the broker
    status: "True"
    type: Exported

I would say we can add columns for:

FQDN (or at least namespace and supercluster suffix),
Creation time
And maybe rename "status" to "Exported" (btw, when could the status be false ?)

@nyechiel, @mangelajo what do you think ?

Looking at:
$ oc get serviceexport "nginx-cl-b"  -o yaml

apiVersion: lighthouse.submariner.io/v2alpha1
kind: ServiceExport
metadata:
  creationTimestamp: "2020-07-26T05:32:51Z"
  generation: 2
  name: nginx-cl-b
  namespace: test-submariner
  resourceVersion: "6803005"
  selfLink: /apis/lighthouse.submariner.io/v2alpha1/namespaces/test-submariner/serviceexports/nginx-cl-b
  uid: 70db9f33-4aa5-4aca-ae13-23439eac7655
status:
  conditions:
  - message: Service was successfully synced to the broker
    status: "True"
    type: Exported

I would say we can add columns for:

FQDN (or at least namespace and supercluster suffix),
Creation time
And maybe rename "status" to "Exported" (btw, when could the status be false ?)
FQDN and supercluster is not a part of this CRD , it is configured in the configmap so it may not be relevant.

When submariner-io/lighthouse/issues/226 fixed you could use "oc  wait" command, so you will have a way to retrieve status, do you think still think status is relevant here too?

@nyechiel, @mangelajo what do you think ?

When submariner-io/lighthouse/issues/226 fixed you could use "oc wait" command, so you will have a way to retrieve status, do you think still think status is relevant here too?

I actually posed the question of whether or not the Status field adds any value last week on slack given the other fields (Type, Reason, and Message). But all these fields are defined in the u/s API so it seems we should stay consistent with it even though it hasn't been finalized. We actually did find a use case for Status == false, based on the u/s definition, in one case when Type == Initialized 😄

In upstream spec the status have been changed from the time we started. It is now  of the format
const {
// ServiceExportValid means that the service referenced by this
// service export has been recognized as valid by an mcs-controller.
// This will be false if the service is found to be unexportable
// (ExternalName, not found).
ServiceExportValid ServiceExportConditionType = "Valid"
// ServiceExportConflict means that there is a conflict between two
// exports for the same Service. When "True", the condition message
// should contain enough information to diagnose the conflict:
// field(s) under contention, which cluster won, and why.
// Users should not expect detailed per-cluster information in the
// conflict message.
ServiceExportConflict ServiceExportConditionType = "Conflict"
}
type ServiceExportCondition struct {
Type ServiceExportConditionType json:"type"
// Status is one of {"True", "False", "Unknown"}
Status corev1.ConditionStatus json:"status"
// +optional
LastTransitionTime *metav1.Time json:"lastTransitionTime,omitempty"
// +optional
Reason *string json:"reason,omitempty"
// +optional
Message *string json:"message,omitempty"
}
an example would be
status:
conditions:

type: Ready
status: "True"
lastTransitionTime: "2020-03-30T01:33:51Z"
type: InvalidService
status: "False"
lastTransitionTime: "2020-03-30T01:33:55Z"
type: Conflict
status: "True"
lastTransitionTime: "2020-03-30T01:33:55Z"
message: "Conflicting type. Using "SuperclusterIP" from oldest service export in "cluster-1". 2/5 clusters disagree."

So if this helps in kubectl commands, I think we can think of using the updated proposal.

In upstream spec the status fields have been changed from the time we started.
...
So if this helps in kubectl commands, I think we can think of using the updated proposal.

@aswinsuryan, did you resolve it ?

This shall be done as a part of https://github.com/submariner-io/lighthouse/issues/336 or after the changes related to this issue is merged.

@aswinsuryan now with the new CRDs, any change of behaviour that we just inherit?

@manosnoam I am still not convinced that there is anything to fix here. If you want to get more info on a certain ServiceExport object, you can always use kubectl describe.
@aswinsuryan now with the new MCS CRDs=, any change of behaviour that we just inherit?

@manosnoam I am still not convinced that there is anything to fix here. If you want to get more info on a certain ServiceExport object, you can always use kubectl describe.
@aswinsuryan now with the new MCS CRDs=, any change of behaviour that we just inherit?

I was expecting this to work , but seems to be not. Not sure if the syntax is correct.
kubectl -n default wait --for=condition=Valid --timeout=5s serviceexports.multicluster.x-k8s.io/nginx

Besides the current issue of no additional info for the -o wide, there's a weird behavior in the age (duration) when checking for serviceexport, with and w/o -o wide (notice the timestamps):
$ oc get serviceexport "nginx-cl-b"
08:40:23 NAME         AGE
08:40:23 nginx-cl-b   52s

$ oc get serviceexport "nginx-cl-b" -o jsonpath='{.status.conditions[?(@.status=="True")].type}' | grep "Valid"
08:40:24 Valid

$ oc get serviceexport "nginx-cl-b" ${namespace:+ -n $namespace} -o wide
08:40:25 NAME         AGE
08:40:25 nginx-cl-b   3s

full test report:
https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS-Globalnet/44/Test-Report/

Besides the current issue of no additional info for the -o wide, there's a weird behavior in the age (duration) when checking for serviceexport, with and w/o -o wide (notice the timestamps):
$ oc get serviceexport "nginx-cl-b"
08:40:23 NAME         AGE
08:40:23 nginx-cl-b   52s

$ oc get serviceexport "nginx-cl-b" -o jsonpath='{.status.conditions[?(@.status=="True")].type}' | grep "Valid"
08:40:24 Valid

$ oc get serviceexport "nginx-cl-b" ${namespace:+ -n $namespace} -o wide
08:40:25 NAME         AGE
08:40:25 nginx-cl-b   3s

full test report:
https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS-Globalnet/44/Test-Report/

As discussed this seems to be not observed in the local setup and the Openshift setup. It could be since a subsequent test recreated the resource.

@manosnoam If we could not reproduce the latest issue can we close this bug. I think now since it is a standard API  there is no much option to customize it unless it is really important.

Today I saw a different response of the age: <invalid>
08:40:21 Name:         nginx-cl-b
08:40:21 Namespace:    test-submariner
08:40:21 Labels:       <none>
08:40:21 Annotations:  <none>
08:40:21 API Version:  multicluster.x-k8s.io/v1alpha1
08:40:21 Kind:         ServiceExport
08:40:21 Metadata:
08:40:21   Creation Timestamp:  2020-12-22T06:39:31Z
08:40:21   Generation:          1
08:40:21   Resource Version:    25028079
08:40:21   Self Link:           /apis/multicluster.x-k8s.io/v1alpha1/namespaces/test-submariner/serviceexports/nginx-cl-b
08:40:21   UID:                 a84ba48e-9ef1-4d69-9a65-c89548007d15
08:40:21 Status:
08:40:21   Conditions:
08:40:21     Last Transition Time:  2020-12-22T06:38:32Z
08:40:21     Message:               Awaiting sync of the ServiceImport to the broker
08:40:21     Reason:                AwaitingSync
08:40:21     Status:                False
08:40:21     Type:                  Valid
08:40:21     Last Transition Time:  2020-12-22T06:38:32Z
08:40:21     Message:               Service was successfully synced to the broker
08:40:21     Reason:
08:40:21     Status:                True
08:40:21     Type:                  Valid
08:40:21 Events:                    <none>
08:40:21

$ oc get serviceexport "nginx-cl-b"
08:40:22 NAME         AGE
08:40:22 nginx-cl-b   <invalid>

# More info
08:40:24 apiVersion: multicluster.x-k8s.io/v1alpha1
08:40:24 kind: ServiceExport
08:40:24 metadata:
08:40:24   creationTimestamp: "2020-12-22T06:39:31Z"
08:40:24   generation: 1
08:40:24   name: nginx-cl-b
08:40:24   namespace: test-submariner
08:40:24   resourceVersion: "25028079"
08:40:24   selfLink: /apis/multicluster.x-k8s.io/v1alpha1/namespaces/test-submariner/serviceexports/nginx-cl-b
08:40:24   uid: a84ba48e-9ef1-4d69-9a65-c89548007d15
08:40:24 status:
08:40:24   conditions:
08:40:24   - lastTransitionTime: "2020-12-22T06:38:32Z"
08:40:24     message: Awaiting sync of the ServiceImport to the broker
08:40:24     reason: AwaitingSync
08:40:24     status: "False"
08:40:24     type: Valid
08:40:24   - lastTransitionTime: "2020-12-22T06:38:32Z"
08:40:24     message: Service was successfully synced to the broker
08:40:24     reason: ""
08:40:24     status: "True"
08:40:24     type: Valid
08:40:24
08:40:24 # Describe Lighthouse Exported Services:
08:40:24
08:40:24 Name:         nginx-cl-b
08:40:24 Namespace:    test-submariner
08:40:24 Labels:       <none>
08:40:24 Annotations:  <none>
08:40:24 API Version:  multicluster.x-k8s.io/v1alpha1
08:40:24 Kind:         ServiceExport
08:40:24 Metadata:
08:40:24   Creation Timestamp:  2020-12-22T06:39:31Z
08:40:24   Generation:          1
08:40:24   Resource Version:    25028079
08:40:24   Self Link:           /apis/multicluster.x-k8s.io/v1alpha1/namespaces/test-submariner/serviceexports/nginx-cl-b
08:40:24   UID:                 a84ba48e-9ef1-4d69-9a65-c89548007d15
08:40:24 Status:
08:40:24   Conditions:
08:40:24     Last Transition Time:  2020-12-22T06:38:32Z
08:40:24     Message:               Awaiting sync of the ServiceImport to the broker
08:40:24     Reason:                AwaitingSync
08:40:24     Status:                False
08:40:24     Type:                  Valid
08:40:24     Last Transition Time:  2020-12-22T06:38:32Z
08:40:24     Message:               Service was successfully synced to the broker
08:40:24     Reason:
08:40:24     Status:                True
08:40:24     Type:                  Valid
08:40:24 Events:                    <none>

020-12-22T06:39:31Z"

Oh ok , but lighthouse/submarienr  does not have any role in reporting this. The creation timestamp is populated by Kubernetes and I think the age should be derived from it while we query. So this could be related to some issue kube-apiserver, like it got too busy or another issue.


Output in identifyable elements

I'm trying to use this project to make integration tests for one of my projects. However it would make it a lot easier if I could use jquery to get things like the "last command" and "last output" which could be obtained by wrapping them in spans or divs.
This can somewhat be emulated by jquery now:
Last Command:
jQuery('#content > [id^=ln]:eq(-2) #lnCnt').text()

Last Output:
$( "#content" )
  .contents()
    .filter(function() {
      return this.nodeType === 3;
    })
      .wrap( "

" )
      .end()
    .filter( "br" )
    .remove(); // wrap text nodes
text = [];
$('#content > [id^=ln]:eq(-2)').nextAll().slice(0, -1).each(function(i, el) {
    text.push($(el).text());
});
text.join('\n'); // output

Hey Blaine,
Happy New Yer!
Sorry for the late response, I was on vacation.
I will try to push it within the next a few days. By the way, do you want to become a maintainer for this repo and the NPM? It would be nice to have someone else to help me with such tasks.


Hide filter cancel button if filter input is an empty string

The filter cancellation button is still visible if I type some characters into a filter textbox and subsequently delete all the characters.  The "ng-show" on the filter cancellation button currently does not test for empty strings.

In master this appears to work already - look at the 208 tutorial as an example.  Are you perhaps fixing something that is already fixed, or is there a particular case that is not working?

Hi PaulL1,
Thanks for the response.  I have confirmed that the tutorial works properly and have also confirmed that the problem exists on my end.  I'll review differences between the two setups and see if I can isolate the problem.
Thanks!

Hi PaulL1,
I was using RC21 and it looks like you have committed a fix to master here
https://github.com/angular-ui/ng-grid/commit/22e6acd81ece42f1133712199edc0142df920ed1
Sorry, I made some rush assumptions and that definitely caused some misjudgments on my end.
Thanks!


Mobile UX is junk

Trying to use the mobile is not a good experience.  This needs to be nice and buttery before V1.  Specifically easing animations are very poorly executed, lots of jittery behavior due to poor point per second calculations and/or touch end animations.  This should probably be completely refactored.

Mobile UX is no longer junk.  There are some missing features still.  I will create tickets for each feature.


Unhandled exception in line 105 of Progress.py#render

I have a mirrored instance of Nexus with Nexus2Artifactory installed on it, running in a docker container. Inside of that container I started a session of GNU Screen, to have the migration running as a background task and independently from my network connection. That migration took about 20 hours, so I reattached to the screen session on the next day. I saw that the migration was executed successfully (apart from several errors) and I wanted to quit the tool by pressing "q". But then this exception occured:
2019-10-21 09:23:08,582 [MainThread] [ERROR] (root:30) - Error running Nexus migration tool:
Traceback (most recent call last):
  File "./NexusToArtifactory.py", line 27, in initInteractive
    win.show()
  File "/nexus2artifactory/nex2art/core/Menu.py", line 179, in show
    if self.runact(sel, sel['act']): return
  File "/nexus2artifactory/nex2art/core/Menu.py", line 203, in runact
    elif hasattr(act, '__call__'): cont = self.showCall(sel, act)
  File "/nexus2artifactory/nex2art/core/Menu.py", line 223, in showCall
    cont = act(sel)
  File "/nexus2artifactory/nex2art/menu/Main.py", line 64, in runmigration
    status, msg = Progress(self.scr).show(self.scr.state.todict())
  File "/nexus2artifactory/nex2art/core/Progress.py", line 39, in show
    self.render(result)
  File "/nexus2artifactory/nex2art/core/Progress.py", line 105, in render
    while chr(self.scr.getch(self.scr.win)) != 'q': pass
ValueError: chr() arg not in range(256)
2019-10-21 09:23:08,637 [MainThread] [INFO] (root:33) - Terminating Nexus migration tool.

Currently I cannot reproduce it, I am not really sure what exact key sequence of keys I pressed. It seems there is a try to cast the input to a character, but my terminal sent some sequens which wasn't a character. Maybe an alternative should be found for the function chr.

Merged your PR, thanks! It definitely seems like that will fix it.


Pattern: Content block - segmented QA testing - Production level version

User Story

As a [user role below]:
developer using the ibm.com Library content block - segmented

I need to:
have a version of the pattern or component that has been tested for accessibility compliance as well as on multiple browsers and platforms

so that I can:
be confident that my ibm.com web site users will have a good experience

Additional information

Browser Stack link
Browser Standard
Browser versions to be tested:  Tier 1 browsers will be tested with defects created as Sev 1 or Sev 2.  Tier 2 browser defects will be created as Sev 3 defects.
Platforms to be tested, by priority:  1)  Desktop  2)  Mobile  3)  Tablet
Mobile & Tablet iOS versions: 13.1 and 13.3
Mobile & Tablet Android versions: 9.0 Pie and 8.1 Oreo
Browsers to be tested:  Desktop: Chrome, Firefox, Safari, Edge, IE, Mobile: Chrome, Safari, Samsung Internet, UC Browser, Tablet: Safari, Chrome, Android
Accessibility Checklist
Creating a QA bug
functional specs issue link (#1128)
functional specs
Design specs
alpha dev issue (#1021)

Acceptance criteria

[ ] Accessibility testing is complete.  Pattern is compliant.
[ ] All browser versions are tested
[ ] All operating systems are tested
[ ] All devices are tested
[ ] Defects are recorded and retested when fixed

@Praveen-sr @chetankan The design specs are available through the Box folder in the above description

@Praveen-sr @chetankan this is ready to be reviewed
https://github.com/carbon-design-system/ibm-dotcom-library/pull/1437


Fixes #191

First fruit of my C++ tutoring from @jimhester.
Prevents attempt to read value of a nonexistent attribute (can occur in xlsx written by something other than Excel).

The appveyor failure is spurious, I think. It's refusing to attempt the build vs. building and failing. I can't tell why it thinks this PR is un-mergeable.

LGTM


TypeError: chrome.pageAction is undefined

Hello,
I tried using latest commit (https://github.com/ArakawaHenri/iCloudPasswords_for_Firefox/commit/f60ca2298699ac1f2578c3506126c7747b2f0e97) but I still have same issue like with latest release version - it autofill username, but not password

i'm having the same problem; the extension only seems to be autofilling usernames. passwords and one-time codes aren't autofilled properly. @ArakawaHenri any chance of a fix?


Job url

🤔 What's changed?
Added job url into execution summary
⚡ What's your motivation?
https://github.com/cucumber/react-components/issues/50
🏷 What kind of change is this?

:zap: New feature (non-breaking change which adds new behaviour)

📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[x] I've changed the behaviour of the code

[x] I have added/updated tests to cover my changes.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] Users should know about my change

[ ] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

This text was originally generated from a template, then edited by hand. You can modify the template here.

@aurelien-reeves Sure, I was experimenting with different icons, such as arrows spin for the job url, but it didnt feel like 100%. What labels - Git ref and Job?

Git ref and Job?

Yeap, looks good :)

Current look with labels:


highlight stops working after loading some colorscheme

Like https://github.com/cocopon/iceberg.vim/issues/90, some colorscheme uses hi clear to clear previous colorscheme.
This removes skkeleton_indicator.nvim's highlight.

I forgot to say thank you for this artifact.
The statusline is insufficient as I can't check the mode in my sight while writing.
Also, this issue is not confirmed in 37669aa699258b6dcbec85e3ed866ecc5d4c0713 and the commit eb16c7325f530add0a365def0509880433bf5240 seems to be the cause.

@Matts966 Thank you for reporting. I made a patch to solve this: #8. I will merge after you check it.

@delphinus
That works perfectly! Thank you 🎉


How To Reference An Element?

Let's say I want to access an element from a function bound to a button. In react/JSX it'd be possible to use ref=. Is there anything similar for hyperapp without manually keeping track of ids or going through the reducer?

@dodekeract HyperApp supports lifecycle events, it's just missing from the docs.
You can use oncreate (or onupdate) to get reference to any DOM element.
Lifecycle Events

oncreate
onupdate
onremove

Examples
app({
  view: _ => html`

 console.log(e)}>Hi.
`
})

CodePen

@dodekeract Does that help? If you give me a more concrete example I can put something together.

@jbucaran I think that depends on the use-case. It should be possible to assign the element to a variable though, which is nice. Adding this to docs should make a workaround possible for most stuff.

@dodekeract When you say keeping track of ids do you mean the global variables that ids create referencing their nodes?
Here is an example: http://jsbin.com/yipaka/2/edit?html,js,console
Just making sure that is what you meant 👍

@dodekeract Think we can close here? Lifecycle Events have been documented.
Or is there anything else missing?

Summary
Hyperapp has no refs, but you can access a virtual node's actual DOM element through lifecycle events.


Create dataset loader for ID Short Answer Grading

https://indonlp.github.io/nusa-catalogue/card.html?id_short_answer_grading

I think this one can be framed as nusantara_pairs schema with text_1 denotes question and text_2 denotes answer, and the label is the score.

#self-assign

Btw, it seems that this issue needs a new task to be declared. Should I add a new constant for SHORT_ANSWER_GRADING task? @SamuelCahyawijaya @afaji @bryanwilie @gentaiscool

@holylovenia : yes, that would be great! I agree that we need to add a new task for this.


Config not disabling ore gen.

config options to disable lead and silver are not working.

I'm pretty sure the config option is a leftover from older versions. Now it's all controlled with datapacks.


Tracking Epoch Time

Need to write a custom callback function to find the time per epoch and other potentially important information during the training of the model.


fix colors

Fix #1
Not sure if this works for every setup but I got it working there

Hmm this is odd as I tested it on my ST7789 and it worked without the invert. I'll double check, give me a day or two to get the setup back to working order :)

If you don't mind I rather close this one and open another PR with the full init code taken from the original ST7789 driver.


Repopulate query / headers if missing from trigger metadata

Resolves https://github.com/Azure/azure-functions-nodejs-worker/issues/324

@yojagad and @pragnagopa - ping for review if you can! Part of these work items:
https://github.com/Azure/azure-functions-language-worker-protobuf/issues/49
https://github.com/Azure/azure-functions-nodejs-worker/issues/317


Migrate precise strike damage to actor flags

For #13061

Per shark's suggestion, I've changed the flag from flags.pf2e.swashbuckler.preciseStrike.value to flags.pf2e.swashbuckler.preciseStrike, so this will need to change too. Sorry about that!


Change terminology to IBC Deposit Address

Cf https://github.com/penumbra-zone/penumbra/issues/3381#issuecomment-1869311071

Build failures seem unrelated to the content of the PR, maybe someone else could pick this up.

but "ibc deposit address" feels like opaque jargon

Yeah, I think that's OK. Probably better to have jargon that's precise than to make up a word people can project their meaning onto. If people don't use them because they don't know what it means that seems fine (per motivation in https://github.com/penumbra-zone/penumbra/issues/3381#issuecomment-1869311071)


[ASTMangler] Fix USR generation/mangling crash in invalid code

In invalid code it seems decls can end up with an opened archetype type that the mangler doesn't like (hitting this unreachable). We still want to be able to generate a USR for these decls so that we can index and rename their occurrences successfully. To allow this, this patch calls mapTypeOutOfContext on types that have primary or opened archetype types prior to mangling.
This is like the issue @rintaro fixed for sourcekitd's ConformingMethodList request in https://github.com/apple/swift/pull/25130, but for indexing.
Resolves rdar://problem/54310026

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - f41aca8623695a13a4458fc1c68c0bd9b4c4b6fb

Build failed
Swift Test OS X Platform
Git Sha - f41aca8623695a13a4458fc1c68c0bd9b4c4b6fb

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - d201fd1cc5386cfef6fc0e6c81bba6db209cdc0a

Build failed
Swift Test OS X Platform
Git Sha - d201fd1cc5386cfef6fc0e6c81bba6db209cdc0a


More Code Cleaning

@yoantran: Continue #47 at missed spots (hint: search for .connect(").
@yoantran: Update SfxController as follow:

# ============================================================================ #
#region Public methods

## Plays a child [AudioStreamPlayer].
func play_sound(audio_stream_name: StringName) -> void:
    var audio_stream_player: AudioStreamPlayer = get_node("%s" % audio_stream_name)
    if audio_stream_player:
        audio_stream_player.play()

## Plays a child [AudioStreamPlayer2D].
func play_sound_2d(audio_stream_name: StringName, position: Vector2, global: bool = true) -> void:
    var audio_stream_player: AudioStreamPlayer2D = get_node("%s" % audio_stream_name)
    if audio_stream_player:
        if global:
            audio_stream_player.global_position = position
        else:
            audio_stream_player.position = position
        audio_stream_player.play()

#endregion
# ============================================================================ #

@miketvo: Fix incorrect value in default_bus_layout.tres: Bus Gameplay should be routed to GlobalEffects.
@miketvo: Update the signature of State overridable methods to have game_state_data = null default value.

Search pattern
(\w*)\.connect\("(.+)", ([\w\d\.\(\)\{\}\[\]:\s]+)\)

Replace pattern
$1.$2.connect($3)

Files to Include
*.gd

Files to Exclude
addons/*

Item 1 and 2 done by @yoantran


capacity vs demand

I think there needs to be a distinction between capacity and demand.
For example, the sink currently 'demands' waste, which might trigger large number of deployment. It instead should 'supply' capacity.

We have frequently discussed this in the context of Cyclus in general (there may even be a CEP). You have the right idea. The traded object still needs to be the waste though.

Ah yes.
The sink was giving a demand because my initial thought was for d3ploy to handle the reversal. Basically setting up d3ploy to have two commodity streams. One would be how it works now, the other reversing the flow by allowing a demand to be framed as a supply.
I did this because I thought it would be better for archetype developers to follow a 'I'm asking for this commodity, therefore it is a demand' thought. However, I'm open to changing it.  I don't actually see a reason the sink would demand something, but it's possible another type of facility might serve a similar sink function but actual demand something...like heat maybe?


[Feature] TH should complain if there was no PICS file supplied

Feature description
Right now, the TH appears to be faking a PICS file and sending it to the scripts, but if there's no PICS file, it supplies an empty PICS file, which basically mean "test nothing".
Since the test framework does RECEIVE a PICS file, we have no way to determine if the PICS are set as intended, or if this was something made up by the TH because someone forgot to load the file into the config, or loaded it incorrectly.
Use Cases
If the TH could just pass through the ACTUAL pics files to the test framework, we can ensure that the correct PICS file was supplied when tests go to check pics.
Test Cases
Run a test that relies on PICS, run test, test should complain that there was no PICS file.
Additional Information
No response

@rquidute please try to reproduce this.


[BUG] fails removing unused import when in a tuple

Describe the bug pycln fails to remove unused imports if they are in a tuple
To Reproduce Steps to reproduce the behavior:

Take this code snippet:
 from typing import Any, Dict, List

 def nothing(a: List[str]) -> Any:
     return a

Run this Pycln command:
$ pycln test.py

Error traceback or unexpected output (if present):
 test.py:1:0 'from typing import Dict' was removed! 🔮
 test.py:1:34 libcst.ParserSyntaxError: Internal error: __init__() got an unexpected keyword argument '__slots__': 'from typing import Any, Dict, List' ⛔

 Oh no, there was an error! 💔 ☹
 1 import was removed, 1 file left unchanged, 1 file has failed to be cleaned.

Unexpected fixed code (if present):

Expected behavior:

Description: A clear and concise description of what you expected to happen.
PyCln should remove the Dict from the import without failing

Expected output (if present):

Expected fixed code (if present):

from typing import Any, List

def nothing(a: List[str]) -> Any:
    return a

Environment (please complete the following informations):

Python Version: Python 3.6.15
Pycln Version: 2.1.1
OS Type: Linux Fedora 36

Additional context
The following versions did not work either: 1.3.5, 2.0.1, 2.0.4
This works with pycln=1.2.0

@gboutry Thanks for reporting the issue. Clearly the issue was with LibCST >=0.4.1 and Python 3.6.

@hadialqattan It works as expected in python 3.6, thank you very much!


Port user scripts to new job store API in 3.1.0

From @benedictpaten on September 8, 2015 23:13
null
Copied from original issue: BD2KGenomics/toil#378

From @benedictpaten on September 16, 2015 6:46
He John, you own this, but need to wait till PR #393 goes in. You can take a look at the modified Job.FileStore interface here:
https://github.com/BD2KGenomics/toil/pull/397
It is considerably simpler. You'll want to use promises everywhere you previously used empty job store files. They can now be arbitrarily nested.

From @jvivian on September 30, 2015 20:49
Rewritten:

[x] Batch Alignment
[ ] Somatic variant calling
[ ] RNA Seq

Tested:

[ ] Batch Alignment
[ ] Somatic variant calling
[ ] RNA Seq

From @benedictpaten on September 20, 2015 20:7
Now that #397 is in, you are unblocked on this.

This issue should be associated with toil-scripts, not toil.


NIFI-1547: DistributedMapCacheServer: Ambiguous error on misconfiguration

NIFI-1547: DistributedMapCacheServer: Ambiguous error on misconfiguration
Updated PersistentMapCache constructor in PersistentMapCache.java to
catch an OverlappingFileLockException and present a more useful error
message before propagating the exception forward. The log message alerts
user to possible duplicated persistencePath in call to
PersistentMapCache.
Created a test method to verify the exception is thrown as expected.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x ] Is your initial contribution a single, squashed commit?

For code changes:

[x ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

+1 LGTM, ran build with unit tests and contrib-check. Thanks for the improvement! Merging to master


[BUG] - css prop (declared but never used)

Describe the bug
In my react file I am attempting to import and then use the css prop to change the font color of this user icon. When I import the css prop my IDE yell at me for not having used the prop. Not 100% sure if this is actually a bug or if I'm just dumb and doing things wrong.
I've attempted to use the prop without the import as well.
Hoping someone can help me with this. Thanks!
import PropTypes from 'prop-types';
import { css, User } from '@nextui-org/react';

function UserIcon({ src, name, size }) {
  return <User src={src} name={name} size={size} css={{ color: 'white' }} />;
}

export default UserIcon;

UserIcon.propTypes = {
  src: PropTypes.string.isRequired,
  name: PropTypes.string.isRequired,
  size: PropTypes.oneOf(['xs', 'sm', 'md', 'lg', 'xl']).isRequired,
};

### Your Example Website or App

Working in private repo

### Steps to Reproduce the Bug or Issue

Private repo

### Expected behavior

As stated in description

### Screenshots or Videos

_No response_

### Operating System Version

Windows

### Browser

Chrome

Hi @Ddupasquier
css prop (declared but never used) - means importing something you are not using inside code.
As you are using css here - <User src={src} name={name} size={size} css={{ color: 'white' }} />
Maybe you thought you needed to import css but actually you don't need to do it. Because User Component already comes with css props, so you can just pass your props here.
Find out more here - https://nextui.org/docs/components/user (go to down on the props part)
I've also made an example if you feel confused - https://stackblitz.com/edit/nextjs-myyf2g?file=pages/index.js


update k8s deps to 1.28

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

cc @jichenjc @adisky I do not have barbican so it is pretty difficult for me to migrate from v1beta1 to v2 kms. I can do that but it might be that its not working after that. I am kind of requesting help here. If we do not find volunteers then we might need to drop support for kms plugin.

/assign kayrus

@kayrus thank you! cherry-pick done

/lgtm

/approve


Optionals support. Style and Swift 1.2 updates.

-Changed from Objective-C runtime reflection to Swift MirrorType reflection to enable optionals.
-Fixed Swift 1.2 errors.
-Altered the conditionals to use optional chaining to reduce repetitive typecasting.
-Updated test in readme to leverage new optional capabilities.
Addresses #3 and #6

@mpavlinsky your code looks good but looks like another PR I've merged in interrupted the auto merge. Can you pull latest and adjust your code and resubmit? Thanks for the awesome work!

I rebased, but there seems to be some issue with this reflection method and the Int64 type right now in Swift. You can see it behaving weirdly in the debugger like so:
(lldb) po Int64(10) as? AnyObject
nil

(lldb) po Int(10) as? AnyObject
Optional(10)

So this looks like a Swift bug of some sort. The current workaround is to use NSNumber as your data type if you need the precision, although I think Int should be mostly fine. I need more information about #7 to know if this is valid.

Uh just stumbled on this. Readding swift-serializer manully to my project and noticed timestamps wouldn't be serialized any more. My reasoning for adding int64 was that NSNumber doesn't hold timestamp in epoch ms. NSNumber has INT_MAX limit  which translates to<PHONE_NUMBER>, while a timestamp can be<PHONE_NUMBER>845.


Comment is removed on formatting

When rustfmt is run this code (from chapter 3.19 Traits in the first edition of "The Rust Programming Language"), the last comment is removed.

I will close this issue since this is a duplicate of #458.


Index was out of range on /p:CoverletOutputFormat="cobertura,opencover"

By providing multiple outputformats we get this error
dotnet test myProject.csproj --no-build --configuration release --logger trx /p:CollectCoverage=true /p:CoverletOutputFormat="cobertura,opencover" /p:CoverletOutputDirectory=C:\temp\coverage --results-directory C:\temp
\coverlet.msbuild.targets(23,5): error : Index was out of range. Must be non-negative and less than the size of the collection. [C:\git\MyProject.Tests\MyProject.Tests.csproj]
C:\Users\xxx.nuget\packages\coverlet.msbuild\2.0.1\build\netstandard2.0\coverlet.msbuild.targets(23,5): error : Parameter name: index [C:\git\MyProject.Tests\MyProject.Tests.csproj]

Woah, this is a first. Will take a look, shouldn't be too hard to fix

I have updated to the last version from Nuget (v2.0.1) and cannot reproduce this error in my tests.
I have executed the following command and both files are generate in folder:
dotnet test test/ducktales.tests/ducktales.tests.csproj /p:CollectCoverage=true /p:CoverletOutputFormat=\"cobertura,opencover\" /p:CoverletOutputDirectory=coverage /p:Exclude="[NUnit3.*]*"

Calculating coverage result...
Generating report 'coverage\coverage.cobertura.xml'
Generating report 'coverage\coverage.opencover.xml'

My repo url:
https://bitbucket.org/andre-castro-garcia/ducktales
(I use the bitbucket because a native integration with bitbucket pipelines and sonarcloud)
@elvirdolic you can shared your repository or code snippet from your test project?
Andre Garcia

By using this /p:CoverletOutputFormat="cobertura,opencover" it does work. But somehow on VSTS this escaping doesn't work correctly. Thx for your support!!


CollisionObject3D::input_event reports incorrect normals when input_capture_on_drag is enabled

Godot version
v4.0.beta3.official [01ae26d31]
System information
Manjaro Linux (6.0.2-2-MANJARO x86_64) Vulkan, GTX 2060 SUPER with proprietary drivers
Issue description
If a CollisionObject3D has input_capture_on_drag set to true the emitted input_event signals only report correct position and normal on mouse button click.
On mouse button release or mouse motion both position and normal are always reported as (0,0,0), even if the mouse pointer is on top of the collider.
I'm not familiar with the code but I assume the problem is here:
https://github.com/godotengine/godot/blob/11e1bac768349ae821647a582282458e83b8d72b/scene/main/viewport.cpp#L704
The Vector3(), Vector3() should be the correct values only when dragging or releasing outside the collider but no ray is being cast.
Some additional issues:

If capture is enabled, mouse_exited is not emitted when the mouse leaves the collider, only when the mouse button is released. If this is expected I'll open a godot documentation issue
The auto generated callback for input_event uses position as a parameter name which will always collide with Node3D.position

Steps to reproduce

Run the MRP
Click, drag and release inside the sphere on the right
Expected: The text at the bottom should show valid position and normal
Actual: (0,0,0) is reported when it shouldn't

Minimal reproduction project

CaptureOnDragNormalMRP.zip

I'm not familiar with the code but I assume the problem is here

Thanks for identifying the correct location in the source code.

If capture is enabled, mouse_exited is not emitted when the mouse leaves the collider, only when the mouse button is released. If this is expected I'll open a godot documentation issue

This sounds like the same problem as we currently have for 2D: #20881, which might get solved by #67791
I believe, that it is reasonable to keep the behavior consistent in 2D and 3D.

The auto generated callback for input_event uses position as a parameter name which will always collide with Node3D.position

I don't know, how that could be solved.

The auto generated callback for input_event uses position as a parameter name which will always collide with Node3D.position

I am not familiar with how to solve this.
I think you need to change it here:
https://github.com/godotengine/godot/blob/754552b34d3523a76656940145bd37328536292d/scene/3d/collision_object_3d.cpp#L475

Instead of position which is guaranteed to collide it can be something like hit_position (and maybe hit_normal for consistency).
It's a really minor annoyance since it's just the default parameter name in the editor-generated callback so the user can just go and change it to something different or leave it as is if he doesn't intend to read/write to Node3D::position. It might confuse newbie users though.
I'll open a proposal since it's not really a bug.


chore(jobs): remove workflow-e2e-pr.groovy DSL as it will be superceded by representation in charts repo

See https://github.com/deis/charts/pull/166 for charts PR referenced

:ship:


Don't pass embedded fs.FS to http/template.TagPacker

@steven-klein this ended up being the fix. We can revisit embedding client/dist in the future, but not strictly necessary.


Test for p2p payment to another wallet

Please add test for payment to another Yandex.Money wallet.
Here is my parameters, fetched from debug print:
amount=1.00&comment=zzzzzzzzzz&to=41001649634926&test_payment=true&message=zzzzzzzzz&pattern_id=p2p
Response always is: status=REFUSED, error=ILLEGAL_PARAMS
What can be a problem, please?

If you're making a test payment you must provide test_result parameter as well.


$record model attached to martin.forms.afterSaveRecord

Firstly i'd like to commend you for a great plugin, this plugin has saved huge amounts of time in form additions.
Secondly, I'd like to access the Martin\Forms\Models\Record model using the event provided from the Martin\Forms\Classes\MagicForm class to manipulate the data / file further.
// FIRE AFTER SAVE EVENT
Event::fire('martin.forms.afterSaveRecord', [&$post, $this]);

Is it possible to retrieve the Martin\Forms\Classes\MagicForm with bound System\Models\File model from the $this object or would it require an extra argument which would supply the Martin\Forms\Classes\MagicForm model.
i.e
// FIRE AFTER SAVE EVENT
Event::fire('martin.forms.afterSaveRecord', [&$post, $this, $record]);

Thanks in advance

Hello @boxxroom
Have you seen this article? https://skydiver.github.io/october-plugin-forms/docs/advanced/events/
Look Magic Form Extender section.

Hi @skydiver
No, I hadn't seen this thank you.
I have created a plugin which in theory does exactly the same as https://skydiver.github.io/october-plugin-forms/docs/advanced/events/ and extends the martin.forms.afterSaveRecord event within the boot method with a few additions for communicating with the api.
That said, the Magic Form Extender still only provides two arguments $formdata, $component but not the model Martin\Forms\Classes\MagicForm of the newly saved record - unless I am missing something.
My PR adds the Martin\Forms\Classes\MagicForm as the third argument so on event extension you also have the newly created Martin\Forms\Classes\MagicForm object data at hand.
My use case is with using the UploadForm class and needing the saved files. What I believe is that files are uploaded before the form submission, on form submission (onFormSubmit) the file data isn't available in the $_POST data by the time it reaches the martin.forms.afterSaveRecord event, by passing the Martin\Forms\Classes\MagicForm saved record as the third argument to the martin.forms.afterSaveRecord event it gives access to the files relation.
Hope this all makes sense.
Again, thanks in advance.

Yes record model must be passed on Events so it can be used further. Right now I need saved record id in event aftersave method but it was not passed into that. I would plugin author to please add that feature.
Thanks


Initial check all existing TSDB chains for brokenness

When the BR initiates, it loads the existing TSDB chunks from /storage and forms doubly-linked chains. however, there is no mechanism to see if the doubly linked chains formed are valid or not. There could be a discontinuity in the normalised chain, faulty address assignment, etc (dig out what more possibility could there be) .
A check should be implemented which should propagate each chain formed from the blocks of chunks, and notify the user if any of the error is found.

We have something similar in the tsdb_test.go where the chain verification is done by propagating the same. However, this time it should be propagation in both directions intensively. Please see if any other verification could be done in order to make the system more reliable.

At present, this happens by default. Hence, closing.


Install the package with the console script ?

Setuptools can inherently create a console script from the pyproject.toml, and users can use
medusa --model path/to/model

medusa as the CLI name may clash with other eariler CLIs for any other tools though, so I'd suggest to make the name of the CLI sth like medusa-llm.

Thanks for the suggestion! We currently don't have a plan to enable the CLI name as this is a more research-oriented project rather than a battle-test product :)


uh oh

new repo

oh god, i looked in index.html, what is "the line"

i now know what the line is


Doc: Important Fix in CONTRIBUTING.md

Describe the documentation update needed

Issue is that when someone new in open source wants contribute to this project He goes through contributing guidelines.
But there is an bug in the documentation You have to first FORK this repo and then clone that FORKED REPO. That step is missing here.

Reason for Update

This update would help new contributors Understand how to contribute to this project.

Proposed Changes

I have already fixed the instructions.

Please @Yashshukla11 assign me this issue so that I can raise a PR.
Little about me : I am experienced contributor as I have completed Hacktoberfest-2020 and Hactoberfest-2023 successfully.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

Hey! @Yashshukla11 I have raised a PR.
Kindly, review it.


Exception while invoking method 'c.sign' undefined

i downgraded to version 4.2.2.
and this happen when upload.

@lyquocnam This issue has been fixed in 4.2.4, If it is the same one I had regarding Match.Maybe() (Please and details about the bug). Unfortunately there is another bug in that version. Here is my workaround
Match.Maybe = (pattern) => { return this.pattern = pattern; };

@jessylachapelle i don't know, i do like tutorial in readme so it happen.
in 4.2.4 with this issue https://github.com/Lepozepo/cloudinary/issues/95
you can more detail about this workaround ? i don't know how to use Math.Maybe, where place for it ?

@lyquocnam Match is part of the Meteor check package. My problem was that the version of check used in 4.2.2 uses the Match.Maybe() method which did not exist in my version of check. If this is the case for you, all you have to do is add the code for the Match.Maybe() method to the lib folder of your project. Although, this may not be your problem, it would help to have the entire console error.

I'm having this problem, but I have the latest version of check, so... other ideas?

The problem is this for some reason:
signature = Cloudinary.uploader.direct_upload "",ops
Any ideas? I'd be happy to submit a PR, but I have no idea why it's not working.

I tried 4.2.4 and 4.2.2, same problem... I'm on Meteor <IP_ADDRESS>, here's the packages I have installed:
accounts-password                  1.3.0  Password support for accounts
accounts-ui-unstyled               1.1.12  Unstyled version of login widgets
alanning:roles                     1.2.15  Authorization package for Meteor
andruschka:jquery-ui-sortable      1.11.2  Sortable is a jQuery UI behaviour for interactively drag-reordering table rows.
arillo:flow-router-helpers         0.5.2  Template helpers for flow-router
babrahams:editable-text            0.8.24  Editable text drop-in template helper
blaze-html-templates               1.0.5  Compile HTML templates into reactive UI with Meteor Blaze
check                              1.2.3  Check whether a value matches a pattern
chriswessels:hammer                4.0.2  A smart-package for integrating with Hammer.js for multi-touch gesture support in your Templates.
copleykj:jquery-autosize           1.17.8  Automatically adjust textarea height based on user input.
cordova:cordova-plugin-statusbar   2.1.3
crosswalk                          1.6.2  Makes your Cordova application use the Crosswalk WebView instead of the System WebView on Android
differential:event-hooks           1.5.0  Provides hooks for various user-triggered events
ecmascript                         0.5.8  Compiler plugin that supports ES2015+ in all .js files
ejson                              1.0.12  Extended and Extensible JSON library
email                              1.1.17  Send email messages
force-ssl                          1.0.12  Require this application to use HTTPS
fourseven:scss                     3.10.0  Style with attitude. Sass and SCSS support for Meteor.js.
gwendall:ui-hooks                  0.1.7  A simpler API for Blaze _uihooks
jagi:astronomy                     1.2.11* Model layer for Meteor
jagi:astronomy-relations           1.0.0  Relations for Meteor Astronomy
jagi:astronomy-sort-behavior       1.0.0  Sort behavior for Meteor Astronomy
jagi:astronomy-timestamp-behavior  1.1.0* Timestamp behavior for Meteor Astronomy
jquery                             1.11.9  Manipulate the DOM using CSS selectors
kadira:blaze-layout                2.3.0  Layout Manager for Blaze (works well with FlowRouter)
kadira:flow-router                 2.12.1  Carefully Designed Client Side Router for Meteor
lepozepo:cloudinary                4.2.4* Upload files to Cloudinary
less                               2.7.5  Leaner CSS language
logging                            1.1.15  Logging facility.
mdg:camera                         1.4.1  Photos with one function call on desktop and mobile.
meteor-base                        1.0.4  Packages that every Meteor app needs
meteorstuff:materialize-modal      1.0.6  Display a modal via Materialize written in coffeescript
mobile-experience                  1.0.4  Packages for a great mobile user experience
momentjs:moment                    2.15.1  Moment.js (official): parse, validate, manipulate, and display dates - official Meteor packaging
mongo                              1.1.12  Adaptor for using MongoDB and Minimongo over DDP
natestrauser:animate-css           3.5.1  Animate.css packaged for meteor
natestrauser:select2               4.0.3  Select2 is a jQuery based replacement for select boxes.
poetic:materialize-scss            1.97.6_1  Materialize (official): A modern responsive front-end framework based on Material Design
raix:handlebar-helpers             0.2.5  Handlebar helpers
raix:push                          3.0.2  Isomorphic Push notifications for APN and GCM
random                             1.0.10  Random number generator and utilities
reload                             1.1.10  Reload the page while preserving application state.
reywood:publish-composite          1.4.2  Publish a set of related documents from multiple collections with a reactive join
session                            1.1.6  Session variable
shell-server                       0.2.1  Server-side component of the `meteor shell` command.
spacebars                          1.0.13  Handlebars-like template language for Meteor
standard-minifier-css              1.2.0  Standard css minifier used with Meteor apps by default.
standard-minifier-js               1.2.0  Standard javascript minifiers used with Meteor apps by default.
stevezhu:lodash                    3.10.1* A utility library delivering consistency, customization, performance, & extras.
summernote:standalone              0.8.1  summernote standalone (official): WYSIWYG editor with embedded images support, packaged without deps
tracker                            1.1.0  Dependency tracker to allow reactive callbacks
useraccounts:flow-routing          1.14.2  UserAccounts package providing routes configuration capability via kadira:flow-router.
useraccounts:materialize           1.14.2  Accounts Templates styled for Materialize Css.
vsivsi:job-collection              1.4.0  A persistent and reactive job queue for Meteor, supporting distributed workers that can run anywhere

Same problem, using latest version (4.2.6) and latest Meteor (1.4.1).
Packages:
Meteor packages used by this project, one per line.
Check this file (and the other files in this directory) into your repository.

'meteor add' and 'meteor remove' will edit this file for you,
but you can also edit it by hand.
<EMAIL_ADDRESS>           # Packages every Meteor app needs to have
<EMAIL_ADDRESS>     # Packages for a great mobile UX
<EMAIL_ADDRESS>                 # The database Meteor supports right now
<EMAIL_ADDRESS>  # Compile .html files into Meteor Blaze views
<EMAIL_ADDRESS>          # Reactive variable for tracker
<EMAIL_ADDRESS>               # Meteor's client-side reactive programming library
<EMAIL_ADDRESS> # CSS minifier run for production mode
<EMAIL_ADDRESS>  # JS minifier run for production mode
<EMAIL_ADDRESS>              # ECMAScript 5 compatibility for older browsers.
ecmascript              # Enable ECMAScript2015+ syntax in app code
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>kadira:flow-router
kadira:blaze-layout
linto:jquery-ui
mrt:jquery-ui-sortable
momentjs:moment
viacdn:font-awesome
liadrian:ionicons-cdn
<EMAIL_ADDRESS>rajit:bootstrap3-datepicker
dangrossman:bootstrap-daterangepicker
clubfest:raphael
twbs:bootstrap
mrt:bootstrap3-wysihtml5
bshamblen:morrisjs
benmgreene:jquery-sparklines
rochal:slimscroll
<EMAIL_ADDRESS>jplack:bootstrap-timepicker
bigdsk:inputmask
postrednik:meteor-rangeslider
cloudspider:icheck
flot:flot
fullcalendar:fullcalendar
j4507:datatables-bootstrap-3
risul:bootstrap-colorpicker
fortawesome:fontawesome
zimme:select2-bootstrap3-css
jss:pace
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>mpowaga:jquery-ui-widget
useraccounts:bootstrap
u2622:persistent-session
3stack:idle-watcher
<EMAIL_ADDRESS>aldeed:collection2
aldeed:autoform
insecure
autopublish
lepozepo:cloudinary

So in one of my apps (have to try the original), the problem was this (thanks go to @copleykj):

I tried to port over my code from another project and realized in doing so that the issue came down to Cloudinary.config = { props } as opposed to Cloudinary.config({props})

That solved it for us, and with that I add another vote to #96, because if it wasn't in coffeescript I would have understood it properly. It's my bad, but just sayin'!


Update README.md

@axel-lauer @remi-kazeroni
Here is the updated readme. Let me know if there are any other feedback


cmd: fix mount via fstab

use args replace os.args

Codecov Report

Merging #1084 (c95fa16) into main (37c59f7) will decrease coverage by 0.08%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main    #1084      +/-   ##
============================================
- Coverage     53.37%   53.28%   -0.09%
  Complexity      149      149
============================================
  Files           147      147
  Lines         22707    22707
  Branches        422      422
============================================
- Hits          12120    12100      -20
- Misses         9126     9142      +16
- Partials       1461     1465       +4

Impacted Files
Coverage Δ

cmd/main.go
56.25% <0.00%> (ø)

pkg/vfs/reader.go
76.45% <0.00%> (-3.11%)
:arrow_down:

pkg/meta/sql.go
68.20% <0.00%> (-0.48%)
:arrow_down:

pkg/fuse/fuse.go
30.22% <0.00%> (+0.64%)
:arrow_up:

pkg/meta/sql_lock.go
75.49% <0.00%> (+2.64%)
:arrow_up:

Continue to review full report at Codecov.

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


Bugfix/rm units to fits

This should in principle solve the problem with the astropy units when saving RSS data.

Yes! It works!


cpal: Unstable device identifiers

The numbers returned when invoking enumerate_devices_sync() and in is_valid_sink_id() differ depending on the time of invocation. Later, when creating the AudioContext, the input devices seem to be missing and the output devices are renumbered. It is not possible to create an AudioContext by setting sink_id to one of the device_ids returned by enumerate_devices_sync() invoked before.
See also #355, that unfortunately doesn't fix this bug.

Example:
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "5": "pipewire"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "6": "default"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "7": "sysdefault:CARD=PCH"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "8": "hdmi:CARD=PCH,DEV=0"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "9": "hdmi:CARD=PCH,DEV=1"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "10": "hdmi:CARD=PCH,DEV=2"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "11": "sysdefault:CARD=DJ"
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "1", group_id: None, kind: AudioInput, label: "pipewire", device: Any { .. } }
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "2", group_id: None, kind: AudioInput, label: "default", device: Any { .. } }
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "3", group_id: None, kind: AudioInput, label: "sysdefault:CARD=PCH", device: Any { .. } }
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "4", group_id: None, kind: AudioInput, label: "sysdefault:CARD=DJ", device: Any { .. } }
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "5", group_id: None, kind: AudioOutput, label: "pipewire", device: Any { .. } }
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "6", group_id: None, kind: AudioOutput, label: "default", device: Any { .. } }
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "7", group_id: None, kind: AudioOutput, label: "sysdefault:CARD=PCH", device: Any { .. } }
[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "8", group_id: None, kind: AudioOutput, label: "sysdefault:CARD=DJ", device: Any { .. } }

Hey,
Yup I really agree that this simple counter strategy is too weak for many real world use-cases, e.g. recalling some stored config even if some sound card have been plugged / unplugged, etc. (...and it doesn't even tries to follow the spec https://www.w3.org/TR/mediacapture-streams/#dom-mediadeviceinfo-deviceid).
Just rapidly checked what infos we can grab from cpal and maybe some hash of: device kind (input | output), device name, device (input | output) number of channels, would be more stable?
It wouldn't be perfect neither and should have to implement some strategy to handle the rare cases where these infos do not create a unique identifier (e.g. someone plugs-in two exact same sound cards). But it seems to me it would be far more robust and useful in most use cases, and would actually solve your issue.
Just two notes on the logs:

seems that the input have been correctly numbered as the pipewire id is 5 at the very beginning:

[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "5": "pipewire"

which is consistent with:

[2023-08-15T22:39:58Z INFO  web_audio_api::context::online] ### Device: MediaDeviceInfo { device_id: "5", group_id: None, kind: AudioOutput, label: "pipewire", device: Any { .. } }

maybe they are filtered out somewhere else in your app?

All the hdmi devices just disappeared from the output list, which is indeed quite weird (but at least explains why the CARD=DJ just gone from 11 to 8)

[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "8": "hdmi:CARD=PCH,DEV=0"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "9": "hdmi:CARD=PCH,DEV=1"
[2023-08-15T22:39:58Z INFO  app] Found audio output device with sink id "10": "hdmi:CARD=PCH,DEV=2"

The first list log entries is filtered by me and only contains the output devices before creating the AudioContext. That's why the numbering starts at 5, nothing to worry about.
The second list are the devices that are checked by is_valid_sink_id while creating the context.

Perhaps the issue of name collisions is not too bad because the end user will have no way to discern these entries anyway so it is okay for us to mix them up?

Not sure this is cool (ok this is edge case stuff but as it can be quite simply mitigated further with a simple counter... not bullet proof neither but better than nothing?). But in the other hand I actually don't know if its a real problem neither... I can ask around to know 1. if the problem really exists in real world, and 2. what is expected or acceptable in such cases


fix #2590

Codecov Report

Merging #2592 into dev will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #2592      +/-   ##
==========================================
+ Coverage   94.42%   94.42%   +<.01%
==========================================
  Files         160      160
  Lines       19477    19489      +12
==========================================
+ Hits        18391    18403      +12
  Misses       1086     1086

Impacted Files
Coverage Δ

qiita_db/test/test_artifact.py
99.85% <100%> (ø)
:arrow_up:

qiita_db/artifact.py
98.3% <100%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


ARROW-2711: [Python] Fix inference from Pandas column with first empty list

Codecov Report

Merging #2309 into master will increase coverage by 2.39%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2309      +/-   ##
==========================================
+ Coverage   84.37%   86.76%   +2.39%
==========================================
  Files         293      237      -56
  Lines       44741    42008    -2733
==========================================
- Hits        37749    36449    -1300
+ Misses       6961     5559    -1402
+ Partials       31        0      -31

Impacted Files
Coverage Δ

cpp/src/arrow/python/numpy_to_arrow.cc
89.08% <100%> (+0.02%)
:arrow_up:

python/pyarrow/tests/test_convert_pandas.py
94.92% <100%> (+0.02%)
:arrow_up:

rust/src/builder.rs

go/arrow/array/numericbuilder.gen.go

rust/src/list.rs

go/arrow/array/util.go

go/arrow/array/bufferbuilder.go

go/arrow/datatype_fixedwidth.go

go/arrow/array/bufferbuilder_byte.go

go/arrow/array/bufferbuilder_numeric.gen.go

... and 49 more

Continue to review full report at Codecov.

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

thanks!


The app is showing error

@raunakmods
Make sure you have installed the game on your device
This error does not bring much information

@raunakmods
I deleted the issue you created in response to this
Do not create another issue to answer this
We can talk here

Delete the project
Create an empty project in Android Studio with a unique package name
Modify the files mentioned in the Readme
Create the same Classes used in the project and then just copy the codes

This happens when i follow your method can you send me the link of build apk? I want to see something

@raunakmods
Send screenshots, vídeo,  Android version, etc to @jonathansilva0x00 ( Telegram )


Click on Select Box in TableGrid Example generates Null Pointer

Apex script unhandled exception
Visualforce Page: /apex/warrior_serve__tableGridStandalone
caused by: System.NullPointerException: Attempt to de-reference a null object
Class.warrior_serve.TableGridController.doHandleSelection: line 272, column 1

@dschueler could you solve this? Would you mind merging you solution back?


The size of the build output exceeds the max allowed size after Nextjs 14 Update

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
NEW_APP
AWS Region
ca-central-1
Amplify Hosting feature
Frontend builds
Question
Hey,
we updated Next to 14.0.2, with Custom Image (public.ecr.aws/docker/library/node:18.17.0).
Now we're facing this issue:
The size of the build output (235208983) exceeds the max allowed size of230686720 bytes. Please reduce the size ofyour build output and try again.
If I check the file size local, I got this one here:
du -h -d 1
152M	./cache
 44M	./server
 60M	./static
260M	.

I'm not sure if it's possible to get rid of the cache folder after the successful build, I think many other people facing this issue, but I didn't found any solution yet.

I updated my build setting to the latest "Linux 2023" build and have the same problem with Next 14.0.2.

Hi @gstrobl @danielkoller 👋 , we have updated our documentation with a troubleshooting guide for the build output size limitation: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html#build-output-too-large. This should enable you to:

Download and inspect your build artifacts
Measure the size of your compute and static directories
Review the dependencies within the node_modules folder
Delete the binaries that aren't required at runtime


Loan Contract should allow for early settlement

Originally, Ines requested for the ability to do "early settlement" for the loan request (e.g. after 5 years) as the cost of interest is very high

Early settlement by paying off the entire loan (i.e. clearing out all future loan tranches) is very easy. Just sum over all outstanding loan tranches and pay it off

Early settlement by waiving additional interest (i.e. paying on the principal on future loan tranches) requires us to have a PMT function to break down future loan tranches into principal, interest payments - and only pay off the outstanding principal amounts

For example

(early repayment by paying all outstanding loan tranches) at the 5 year mark in April 2026: Ines will pay total of $85,774

(early repayment by waiving additional interest): Ines will only pay 5 years worth of interest (I'd estimate around $72,000)

After discussing with @wimanesti on 22nd April 2019:

We decided to not have an early termination option
This might make the loan less attractive
Also more difficult to code


Remove marketdata project from RTD

Details

Read the Docs project URL: https://readthedocs.org/projects/marketdata/
Read the Docs username (if applicable): @milktrader

Following https://github.com/JuliaQuant/MarketData.jl/issues/46
We need to remove project page https://readthedocs.org/projects/marketdata/ because doc is now available at http://juliaquant.github.io/MarketData.jl/latest/

Hello @humitos
I haven't get any reply from @milktrader.
Could you remove RTD project page https://readthedocs.org/projects/marketdata/ because doc is now available at http://juliaquant.github.io/MarketData.jl/latest/
Kind regards

Hi @humitos
Any news?
Kind regards

I didn't get any response either. I removed the project. Thanks for your patience.

Thanks @humitos


chore: Rename MyProfile to CollectorProfile

The type of this PR is: Chore

This PR resolves this ticket
Here is the discussion
Description

PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Rename MyProfile to CollectorProfile everywhere in the app - sam

This PR contains the following changes:

Dev changes (Rename MyProfile to CollectorProfile everywhere in the app - sam)

  Generated by :no_entry_sign: dangerJS against 9c95553abb1178f5457be485be5cec8774654350

I thought the idea was to remove My, not to add Collector, right?

I thought the idea was to remove My, not to add Collector, right?

I wanted the same. but then we decided to make it CollectorProfile in our retrospective.
I am happy to make it Profile though. Let's what others feel about it.

I would definitely vote for just Profile, even though I don't mind MyProfile that much. But definitely Profile seems like a better choice. It's a simpler, there is only one profile in the app. that one. no need to give it an extra description. I was not in the discussion so I don't know what the other choices and reasoning were, so I will not block this, but as a reviewer I definitely think this is not an improvement on what we have now 🤔.

Closing PR for inactivity - please feel free to reopen it if needed 👌


Integrate quilljs component for custom task views

Adds the Quill editor as an optional directive to be included in custom task views.

Quick sniff test lgtm.  One question on here.
It might be nice to include a quick example html snippet of how to include a quill editor in a task, and an update to the README to explain its dependence on things like S3, how to configure it, etc.

Three comments, but you can fix/squash/merge w/o another review assuming the fixes are simple/obvious :)


Eagle: Auto and RTL non responsive

Running master c0c0666
Auto and RTL do not respond despite having good gps lock
Flight in position mode without issues
https://logs.px4.io/plot_app?log=474076d1-969e-41fd-bcf7-eaa0489c3038
https://logs.px4.io/plot_app?log=f9593388-cbae-48b9-a55d-4884dd162644
Logs not showing error messages

this issue has been resolved and both platforms work on 1.8.0 stable


Add comments to metrics code and add error handling

Adds a try-except block to help debug if github secret isn't being accessed or is malformed
Adds comments and docstrings throughout.
Still need to update contributing guide.

Thanks for the review @erogluorhan because of this I can tell that the length of our key is 1732. This is good news because I was afraid it would return a length 0 or be unable to find the secret, which is a much harder problem to solve.
One discrepancy in the key that I encountered is sometimes all of the '\n' characters added to a GH secret are rendered as '\n'. I don't completely know why this is, but I saw it come up a lot when I was wrestling with this malformed key error.
Incidentally, if I take the known key and replace those characters locally, it has length 1732. I'm going to add a quick string manipulation in another PR that should ensure our key has one slash instead of two.


Access Denied (sorry your link has timed out)

I've setup a EC server/GoLang/thunderzippy successfully.
I use the following command to create the link:
curl -H "Content-Type: application/json" -X POST -d '[{"Filepath":"images/example.jpg","Url":"https://upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg"}]' http://localhost:8080/zip/{"ref":"z95h07"}
But when I try to get the zip download file with the following command, I got  Access Denied
curl http://localhost:8080/zip/?ref=z95h07 -o "download.zip"
Is there anything wrong or any setting I should check.

Finally found the reason why.
I cannot pass the ref code while creating the zip, I can only wait the response and use the ticket no to reference the d/l link.
curl -H "Content-Type: application/json" -X POST -d '[{"Filepath":"images/example.jpg","Url":"https://upload.wikimedia.org/wikipedia/mediawiki/a/a9/Example.jpg"}]' http://localhost:8080/zip

That's correct. The ref code is supplied in the response from the initial POST request and used in the subsequent GET request. I can see why the README might have mislead you on this through lack of whitespace and will look at clarifying the documentation. Thanks.


Support Webp Encoding

With webp support now available in both Gd and Imagick (and the fact that webp is an awesome format), it really is time for this package to support this format.
This PR adds basic functionality to encode to webp.
A NotSupportedException will be thrown at encode-time if the driver has not been compiled with webp support.

+1

Any thoughts on this?
I have been using my fork for another project, and both modern Gd and IM drivers work very well for encoding to WebP

Included in baeeac5125b7015f3fad0f9333b5e33585430f38 and 961c58a9951acd688b9a2d17ff24ac9bcb199f84.


Design tooltips / help text to provide additional context to the calculated fields to avoid confusion

Describe the task
According to @pbastia: The rules for some calculated fields are getting too complex even for someone familiar with the CIF program. We might want to start working on contextual help and tooltips. The generic

This field cannot be calculated due to lack of information now.

help text isn't enough.
Acceptance Criteria

[x] List the calculated fields needing additional help text refer to the Calculations doc
[x] Draft contextual help text for the fields above
[ ] Refine the copy with CIF's feedback
[x] Create ticket(s) for implementation with CIF's validation

Additional context

Tooltip components in #979 & #1573 can be reused for the implementation of this
@suhafa's suggestion:

Something more specific would be helpful. I have an idea -Wealthsimple has a fantastic way they handle incomplete information. When the user submits the erroneous application, an alert box will let them know something isn't right and then the user is directly taken to fields they need to enter information in step-by-step to sort the issue. We could also utilize these 'guided' field filling paths for calculations.

Hi @pbastia - This ticket #1635 would be a research/design ticket to determine what the contextual help text would be for the calculated fields on Budgets, Milestone Reports, and Emissions Intensity Report forms.
Once the tooltip component is implemented in either #979 or #1573, it can be reused here too.
This ticket is fully refined and I can remove the tag unless you have additional input. :)

The Tooltips for Calculated Fields has been drafted and shared with the CIF team for feedback/validation.

Hi @pbastia - This ticket is ready for you to review and can be closed with:

Tooltips drafted and uploaded to our team's channel
#1692 created for implementation

Note:
We didn't get CIF's input for the draft with a few nudges. Re: @pbastia's input:

Let's implement the tooltips as stated in this document, future text changes are really easy if needed


Port the image attachments from the old UI to the new one

[x] Ability to upload by manually upload, pasting from clipboard, or drag-and-drop

I've started this task


the "arXiv" link doesn't always go to an arxiv website

why is this? why is it titled arXiv if it doesn't go to the arXiv?

In a perfect world researchers would all submit their papers to arXiv, but as this is not always the case: the important thing is for the article to be "freely" available. Also for older papers, arXiv wasn't around yet :)
Then there's also other variants of arXiv, ie for biology: biorxiv.org

I agree, its confusing at time. We are looking at options how to make this clearer.
What do you think about this:
arXiv = Text
GitHub = Code
underneath we would always show the actual URL where the link goes to.
Comments?

i think when someone submits a link they can just type in what the name is
maybe it could be a choice of "arXiv/.../other".
i would really like to be able to differentiate those submissions that are actually related to arXiv papers.

We are investigating options here as described above. The "user can just type what ever they like" scenario is sub-optimal, as it means A) more mental work for the editor B) attack vector space for trolls. I agree with the problem you highlight though, it should be easier to see where links lead to.

yeh I agree its not optimal right now, maybe just expose the link itself, or domain it leads to: should be an easy enough fix.

It's really unpleasant to click a link titled "arXiv" and to land somewhere else. It's also best if the user will know if they're clicking on a PDF link or a web link. I'd suggest that the system should detect if the link is to an arXiv paper, and if so: (a) re-generate the link as an /abs link so that the UX is consistent; (b) use "arXiv" for the title. Else if not an arXiv link, just call it "text" or whatever you like.

@danstowell your suggestion sounds great, we´ll investigate this in the next iteration.


swayrbar: Init at 0.3.4

Description of changes
Added new package swayrbar

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Thanks for the feedback, I've adjusted the PR :)

Please mark platforms as linux only, build is failing on darwin.

Please mark platforms as linux only, build is failing on darwin.

Done or do I need badPlatform as well?

Nope, platforms alone is enough.