Inserting data named //insert breaks the repo

I'm running a repo at /testrepo and inserted some data named /testrepo/insert. This broke the related repo functionality forever (i.e. one needs to manually fix the database), because on subsequent startups, ndn-python-repo will keep re-registering the prefixes of inserted data, making repo functionality inaccessible.
14:54:00.376746 Express Interest: /testrepo/insert/0
14:54:00.378678 Received data: /testrepo/insert/0
[2020-02-23 14:54:00]INFO:Segment insertion success, 1 items inserted
[2020-02-23 14:54:00]INFO:Added new prefix into the database: /testrepo/insert
[2020-02-23 14:54:00]INFO:Read handle: listening to /testrepo/insert
[2020-02-23 14:54:00]ERROR:Task exception was never retrieved
future: <Task finished coro=<NDNApp.register() done, defined at /home/davide/.local/lib/python3.7/site-packages/ndn/app.py:335> exception=ValueError('Duplicated registration: /testrepo/insert')>
Traceback (most recent call last):
  File "/home/davide/.local/lib/python3.7/site-packages/ndn/app.py", line 360, in register
    raise ValueError(f'Duplicated registration: {Name.to_str(name)}')
ValueError: Duplicated registration: /testrepo/insert

This seems like a design question... I'm assuming the expected behavior is that the repo rejects any data that overlaps with its own namespace?

Yes, that would be a sensible behavior.

Fixed with 958d96fefaccefa7b30e6b8438a52e401b4d5432.


Fixed FlowerGun AddRelativeForce

The bullet flower in the flower gun is not working.
It always shoots the flower to the same direction.
That is due to a regression in the Untiy Physics Engine.
They are aware of the bug:
https://issuetracker.unity3d.com/issues/auto-sync-transforms-does-not-sync-correctly-when-using-addrelativeforce
However this fix is not even on 2018.1 beta yet.
So it would be nice to add this fix to NewtonVR.
Adding Physics.SyncTransforms() flushes any rotations to the physics engine which then applies the new rotation of the flower and makes it go the right way.

Note that we can also fix this without calling the Physics.SyncTransform() by changing the BulletForce to a float and adding the force like this:
bullet.GetComponent().AddForce(bullet.transform.forward*BulletForce);

@tiagosomda is this still necessary?

I haven't tried it recently.
However, Unity says they have fixed the bug on their side:
https://issuetracker.unity3d.com/issues/auto-sync-transforms-does-not-sync-correctly-when-using-addrelativeforce


bug: table header unnecessary z-index

What version of daisyUI are you using?
v2.52.0
Describe your issue
The first child of a <th> in a table has a z-index of 11. Why is this needed? I don't see the benefit and in my project this produce a weird overlapping with the navbar:

The first column is overlapping my navbar here. I know I can easily increase the z-index of my navbar but the z-index in the <th> makes no sense for me.
Is there a reason why the z-index exists? (code reference)
What browsers are you seeing the problem on?
No response
Reproduction URL (optional)
No response

This is no longer an issue in the new version 3.0 update.
In daisyUI 2.0 table was too opinionated and it was causing issues in many cases. The style is completely rewritten for 3.0 and it's more customizable.


⚠ ClamAV has degraded performance

In e28ae91, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 47 ms

Resolved: ClamAV performance has improved in 8de0bbd.


DCO check fails on some PRs

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project.

We use a Probot GitHub app to run DCO checks on all our PRs:

https://probot.github.io/apps/dco
https://github.com/dcoapp/app

@hangtwenty and I recently observed that this check was failing on some PRs. Let's figure out why!

After a bit of investigating, I think this is caused when a suggested code change from the github.com UI is accepted. Those commits are not signed off:

Here's what a signed off commit looks like:

I looked through the DCO app's configuration options, but none of them really fit this scenario. It is possible to bypass this check for organization members, but in order for that to work, all commits by those members need to be signed (as in GPG signed, not "signed off"). I don't think any of us on the team are currently signing our commits, so probably not worth the effort at this point.
Remediation
Admins: If you see a failing DCO check on a PR:

Look at the individual commits
If none of the commits are signed, let the PR author know they need to sign off their commits
If some of the commits are signed and some are not due to accepted changes:

Click the [Set DCO to Pass] button on the check
Squash and merged the PR with a signed-off message in the commit body

Get on with your life! ✨


CloudTrail event exclusion of a particular event source and action

Hi,
We would like to exclude the certain event source and action from cloudtrail events. For example, all DescribeTable event action from event source dynamodb.amazonaws.com.
How to achieve the same through es-loader script?
regards
Jinu

Followed this instruction to exclude the cloudtrail events
https://github.com/aws-samples/siem-on-amazon-opensearch-service/blob/main/docs/configure_siem.md#excluding-logs-based-on-log-fields-and-values
Created CSV file and upload to geo s3 bucket with following content, but still events are not excluded. Can someone look into this and suggest a solution.?
log_type,field,pattern,pattern_type,comment
cloudtrail,eventName,DescribeTable,text,excludedDescribeTable

Sample JSON payload here;
{
		"eventVersion": "1.08",
		"userIdentity": {
			"type": "AssumedRole",
			"principalId": "masked",
			"arn": "arn:aws:sts::masked:assumed-role/masked",
			"accountId": "masked",
			"accessKeyId": "masked",
			"sessionContext": {
				"sessionIssuer": {
					"type": "Role",
					"principalId": "masked",
					"arn": "arn:aws:iam::masked:role/masked",
					"accountId": "masked",
					"userName": "masked"
				},
				"attributes": {
					"creationDate": "2022-07-13T23:14:17Z",
					"mfaAuthenticated": "false"
				}
			}
		},
		"eventTime": "2022-07-13T23:55:35Z",
		"eventSource": "dynamodb.amazonaws.com",
		"eventName": "DescribeTable",
		"awsRegion": "ap-northeast-1",
		"sourceIPAddress": "masked",
		"userAgent": "Boto3/1.18.55 Python/3.9.8 Linux/4.14.255-276-224.499.amzn2.x86_64 exec-env/AWS_Lambda_python3.9 Botocore/1.21.55",
		"requestParameters": {
			"tableName": "masked"
		},
		"responseElements": null,
		"requestID": "JRKC1GC0H20T0IALVDP123DE33VV4KQNSO5AEMVJF66Q9ASUAAJG",
		"eventID": "64903f5b-ef19-427c-83b7-c2f63d242a56",
		"readOnly": true,
		"resources": [{
			"accountId": "masked",
			"type": "AWS::DynamoDB::Table",
			"ARN": "arn:aws:dynamodb:ap-northeast-1:masked:table/masked"
		}],
		"eventType": "AwsApiCall",
		"apiVersion": "2012-08-10",
		"managementEvent": true,
		"recipientAccountId": "masked",
		"eventCategory": "Management",
		"tlsDetails": {
			"clientProvidedHostHeader": "dynamodb.ap-northeast-1.amazonaws.com"
		}
	}

regards
Jinu

Above mentioned solution worked out to exclude the events.


createVersionSnapshot can actually return a NO_CONTENT status code

Migrating an existing fedora3 directory to fedora4, the migration-utils fails to create version document because the FedoraResourceImpl.createVersionSnapshot() call returns a NO_CONTENT status code which is not expected.

Related: https://github.com/fcrepo4-labs/fcrepo4-client/pull/38


[UF-521] goTo(PlaceRequest place, HTMLElement addTo) doesn't cleanup if it's called twice.

just some mins before the review, I'm changing the API.

jenkins retest this


Multimodal Modeling Methods to Support

For methods to support for multimodal modeling we should support:

[ ] No Fusion approach: Contrastive workflows between modalities where a single embedding is generated for each modality (and/or temporal window) and some contrastive loss is applied to align these modalities. This is inspired by this work. We currently support this for temporal windows, see the EBCL and OCP models.
[ ] Early fusion approach: Our operating assumption is that clinical data is inherently multi-modal but temporally aligned (e.g. lab measurements, medication codes, notes all occur at specific timestamps). For sparse modalities like clinical notes that occur less frequently than dense measurements, we handle this efficiently by:

Processing sparse modalities separately to avoid excessive padding
Encoding sparse events (e.g. notes, ecgs, echos) in a separate batch
Mapping the resulting embeddings back to their temporal positions in the patient sequence
Combining these with the dense measurement embeddings at matching timestamps

This approach maintains temporal alignment while avoiding memory issues from padding sparse modalities to match dense measurement frequencies. See the JNRT padding example for why naive padding is problematic.

I think we can start with creating a new input_encoder class: https://github.com/Oufattole/meds-torch/blob/main/src/meds_torch/input_encoder/triplet_encoder.py, that adds a new modality specific key to batch in the forward pass.
and then making a custom multimodal supervised method: https://github.com/Oufattole/meds-torch/blob/main/src/meds_torch/models/supervised_model.py


Clear all back stack

How to clear all back stack say when login is a success or for other use case like when we want to exit from the app on hitting back instead of going to the previous screen?

tried navigator.popBackStack(), no luck.

Same way as with official compose navigation.
I believe it’s clearBackStack

Let me know if you make it work

No luck,
Here is what I'm trying.
Navigating to dashboard scree.
on adding clear backStack it even prevented navigation to Dashboard Screen.
is VerifyOtpSingleEvent.NavigateToNextScreen -> {
navigator.navigate(
DashBoardScreenDestination()
)
navigator.clearBackStack(DashBoardScreenDestination.route)
}

If you clear after navigating then you also clear the new one 😉
try clearing before navigating.
The official way to navigate while popping back stack is by passing the lambda parameter where you can specify such things. Google it: compose navigation navigate while popping back stack.

Okay, so there are 2 screens before Dashboard which needs to be cleared.
I tried this way, and it clears only the Otp screen from back stack.
The screen before that which is for entering mobile number is still there.
When I hit back it takes me to enter mobile number screen but eventually it should be closing the app.
navigator.navigate(
DashBoardScreenDestination()
) {
popUpTo(EnterOtpScreenDestination.route) {
inclusive = true
}
}

So it just means you need to pass some other route to the popUpTo method right? 🙂

Yeah, its resolved. Thanks :-)


Componentisation proof of concept

This is a proof of concept that demostrates how we might use Packwerk to organise Whitehall into domain components by following Domain-Driven Design principles.
As a proof of concept, I've taken a small feature in Whitehall (the Emergency Banner) and arranged it into a small package. This package is a Rails engine which serves as a "mini-application" including all the things required for the application (such as controllers, views etc), as well as any tests, and the routes.
We use Packwerk to define the package, as well as highlight any parts of the package that use code from the main application.
As well as the Emergency Banner package, I've also added a Base package, which includes things like the Base controllers, helpers, and anything else that may be required across the application. We can then define it as an explicit dependency on both the package and the main application, ensuring that any boundaries are well-defined.
Going forward the ambition would be to move more functionality into packages, making code more well defined and easier to reason about.
This is very much an idea in its draft stage, but if this is something that people are keen to try out / explore adopting, we (the Content Modelling team) can draft a more formal ADR and begin trying this pattern when we build our Object Store within Whitehall.

I'm quite keen on this in principle, but... I'm doubtful that we can invest the time to see this through for the whole of Whitehall, at least if it depends on the Whitehall Experience team to do the work. From a product perspective I think it's going to be very hard for us to justify as I expect it could take quite a long time. I suppose we could just put everything we can't easily separate into one large package, but then would we be gaining anything?
This does offer a nice way to keep the new content block/object store behaviours separate from the rest of Whitehall, which is definitely a good thing. But if we aren't able to do the hard work of decoupling the edition behaviours from each other and the model so that we can leverage this approach for other parts of the app, then does it just become "yet another way of doing things in Whitehall"? Would be very interested to get @richardTowers thoughts - maybe there's an appetite to devote some resource to such an idea?

I also like the idea. Reminds me a bit of my .NET days ( :trollface: ) when we'd have a bunch of .csproj files separating out assemblies, and internal methods and things like that ❤
I agree with Ryan's concerns that we might not be able to commit to this enough for it to get critical mass though.
The value of packwerk feels relatively modest, which would need to balance the modest cost of introducing a new concept. I think we'd get a reasonable benefit if we properly carved things up and used it everywhere, but that's a big bit of work. On the other hand, if we just did a couple of small examples (like this), the cost of the new concept would probably outweigh the benefit. So I think it's a "we should only do this if we're going to really commit to it" thing.
Maybe it would be good to sketch out what sort of module structure we might aim for in the long term? Would we just be using it for things like the emergency banner, which are bolt ons? Or would we have it for more fundamental things like different document types?

I certainly think, in an ideal world, the first thing to be componentised would be the "bolt on" functionality, then potentially the main publishing functionality could be compontentised after. The level of seperation could be as broad or as narrow as we'd like, we could go down to document type level if that makes sense, or just have one "mega component" for all the existing Editionable content. I did have a go at adding a few more components, but didn't push these for the sake of brevity. I'll push them up to show some other use cases too.

Assuming we only included the "bolt on" functionality, I think I'd see the package structure looking a bit like this:
packages/
  cabinet_ministers/
  emergency_banner/
  operational_fields/
  get_involved/
  governments/
  groups/
  organisations/ # This could be split up further into "Organisations and Contacts"
  people/
  roles/
  sitewide_settings/
  topical_events/
  world_location_news/
  worldwide_organisations/
  republishing/

I think I'd like to see an approach of "if you touch it, you move it", but the challenges there are getting buy-in and also enforcing that approach too


my live server in vs code dose not work and i did not receive any error and every time i code , i should tap on the go live button

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

Can you explain in more detail what you mean by that? The newest version of the extension should play well with live server.


Add option to bypass certificate validation

Hi there!
I was super excited to find this tool and wanted to give it a go. However, the corporate firewall I'm behind has a transparent HTTPS proxy in-between my laptop and the public internet. Would it be possible to allow users to supply one of the following?

An intermediate certificate file to verify against in the certificate chain
Proxy configuration to notify dnvm of a HTTPS proxy
A flag to turn off strict SSL verification

Thanks!

Thanks for the feedback -- I'll have to think about the best way to implement this. I've been trying to avoid maintaining too much infra on the hosting side so I'd like to make this as simple as possible to maintain. Maybe I can just pass a flag to HttpClient.


Bug Report

Report Message

I can’t add it to my server because it says it’s not authorized

Report Metadata
Bug Reported By: ゴッチャビッチ#5083<PHONE_NUMBER>65709588)
Bug Reported At: Thursday, March 10, 2022, 5:21:16 PM Eastern Standard Time

I cannot do anything about this, discord will not verify the bot.


Applying the configurationdata on a DSC compliationjob via ARM

Hi
Is there currently any way to apply a configurationdata configuration to a compilationjob similar to what is available via powershell sdk? This is what I am referring to below:
Start-AzureRmAutomationDscCompilationJob -ResourceGroupName "MyResourceGroup" -AutomationAccountName "MyAutomationAccount" -ConfigurationName "CredentialSample" -ConfigurationData $ConfigData
Thanks,
Matt

Hi,
Currently this can only be done via PowerShell. Can you post a feedback item on our UserVoice page (https://feedback.azure.com/forums/246290-automation) so we can track this and other customers can vote for it as well?

Hi Joe
I have added a post regarding this here https://feedback.azure.com/forums/246290-automation/suggestions/11216361-arm-support-for-configurationdata-in-dsc-compilati
Thanks


Script doesnt add kills

seems something may have been updated in the game, have redownload and installed everything from scratch and no kills are being added to any weapon or strange cosmetic. TF2

Seems like it, I don't know what is wrong and I don't have time to try and investigate


Refactor codebase to async/await – spo sitedesign get until spo sitedesign task get, Closes #5106

Closes #5106

Thank you, we'll review it ASAP.

sorry @nicodecleyre for the hold up on this one 🙏. I will try to merge this first thing after the release

ready to merge 🚀

merged manually. Awesome work 👏


src5 interface implementation

**Issue(s): #109

Hey @mubarak23, do you need some additional help for this?

Hey @mubarak23, do you need some additional help for this?

Yes, am kind of stuck on this


Create keystoneapi route and svc endpoint overrides

Creates the route for the keystoneapi, also allows to customize the route via override.
Generats the service override for the env with what is configured in the externalEndpoints, or specified in the service template override.
Depends-On: https://github.com/openstack-k8s-operators/lib-common/pull/313
Depends-On: https://github.com/openstack-k8s-operators/keystone-operator/pull/289
Jira: OSP-26690

/hold

in osctlplane

the externalEndpoints is now outside the service template
it has an override which allows to customize the route
the service template has an override which allows to customize the routes for the service

  keystone:
    enabled: true
    externalEndpoints:
    - endpoint: internal
      ipAddressPool: internalapi
      loadBalancerIPs:
      - <IP_ADDRESS>
      sharedIP: true
      sharedIPKey: ""
    override:
      route:
        metadata:
          annotations:
            "my": "annotation"
    template:
...
      override:
        service:
          - endpoint: public
            metadata:
              annotations:
                "my": "annotation"

the openstack-operator uses the service override to pass in the expected overrides for the endpoint services and results in:
apiVersion: keystone.openstack.org/v1beta1
kind: KeystoneAPI
...
spec:
...
  override:
    service:
    - endpoint: public
      endpointURL: http://keystone-public-openstack.apps-crc.testing
      metadata:
        annotations:
          dnsmasq.network.openstack.org/hostname: keystone-public.openstack.svc
          my: annotation
        labels:
          public: "true"
          service: keystone
      spec:
        ports:
        - name: keystone-public
          port: 5000
          protocol: TCP
          targetPort: 0
        selector:
          service: keystone
        type: ClusterIP
    - endpoint: internal
      endpointURL: http://keystone-internal.openstack.svc:5000
      metadata:
        annotations:
          metallb.universe.tf/address-pool: internalapi
          metallb.universe.tf/allow-shared-ip: internalapi
          metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>
        labels:
          internal: "true"
          service: keystone
      spec:
        ports:
        - name: keystone-internal
          port: 5000
          protocol: TCP
          targetPort: 0
        selector:
          service: keystone
        type: LoadBalancer

it is also possible to just use externalEndpoints to use metallb for public and internal:

  keystone:
    externalEndpoints:
    - endpoint: internal
      ipAddressPool: internalapi
      loadBalancerIPs:
      - <IP_ADDRESS>
    - endpoint: public
      ipAddressPool: internalapi
      loadBalancerIPs:
      - <IP_ADDRESS>
    template:
      databaseInstance: openstack
      secret: osp-secret

results in the following override in keystoneapi:
  override:
    service:
    - endpoint: public
      endpointURL: http://keystone-public.openstack.svc:5000
      metadata:
        annotations:
          metallb.universe.tf/address-pool: internalapi
          metallb.universe.tf/allow-shared-ip: internalapi
          metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>
        labels:
          public: "true"
          service: keystone
      spec:
        ports:
        - name: keystone-public
          port: 5000
          protocol: TCP
          targetPort: 0
        selector:
          service: keystone
        type: LoadBalancer
    - endpoint: internal
      endpointURL: http://keystone-internal.openstack.svc:5000
      metadata:
        annotations:
          metallb.universe.tf/address-pool: internalapi
          metallb.universe.tf/allow-shared-ip: internalapi
          metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>
        labels:
          internal: "true"
          service: keystone
      spec:
        ports:
        - name: keystone-internal
          port: 5000
          protocol: TCP
          targetPort: 0
        selector:
          service: keystone
        type: LoadBalancer

or use the service override to use another LoadBalance for the public endpoint

  keystone:
    externalEndpoints:
    - endpoint: internal
      ipAddressPool: internalapi
      loadBalancerIPs:
      - <IP_ADDRESS>
    template:
      databaseInstance: openstack
      secret: osp-secret
      override:
        service:
        - endpoint: public
          metadata:
            annotations:
              my: loadbalancerannotation
          spec:
            type: LoadBalancer

results in the following override in keystoneapi:
  override:
    service:
    - endpoint: public
      endpointURL: http://keystone-public.openstack.svc:5000
      metadata:
        annotations:
          my: loadbalancerannotation
        labels:
          public: "true"
          service: keystone
      spec:
        ports:
        - name: keystone-public
          port: 5000
          protocol: TCP
          targetPort: 0
        selector:
          service: keystone
        type: LoadBalancer
    - endpoint: internal
      endpointURL: http://keystone-internal.openstack.svc:5000
      metadata:
        annotations:
          metallb.universe.tf/address-pool: internalapi
          metallb.universe.tf/allow-shared-ip: internalapi
          metallb.universe.tf/loadBalancerIPs: <IP_ADDRESS>
        labels:
          internal: "true"
          service: keystone
      spec:
        ports:
        - name: keystone-internal
          port: 5000
          protocol: TCP
          targetPort: 0
        selector:
          service: keystone
        type: LoadBalancer

/test openstack-operator-build-deploy-kuttl

I try to distill my remaining concerns.
With this change the openstack-operator needs to learn new things that was hidden in the service operators:

The number of endpoints the service operator creates
it is creating routes for public endpoints, for internals it is not creating something it is just passing in service overrides which got defined by the end user on the ctlplane CR.

The type of those endpoints and the logic that which endpoint needs routing and which isn't
yes it has the list of endpoint types, which is public and internal. The logic is "stupid" if it is public and no LoadBalancer override specified create route, otherwise just pass in the service override to the service operator and it does all the service part

The naming scheme of the k8s Service objects the service operator creates
Yes, this is the part where the openstack-operator requires knowledge on the naming scheme, but the service name can not be overridden. if there will be a change, it would require a manual change when updating to the new service operator version, but in which situation this will? I'd say the situations are really rare.

This creates extra coupling between the openstack-operators and the service operators. I dislike this increase of coupling.

FYI, I have updated the network_isolation samples to show how the overrides now look like. externalEndpoints is gone and only the overrides from the service template itself is used. so there is no longer a two way patching required as there is now only a single interface to customize the service.

I try to distill my remaining concerns.
With this change the openstack-operator needs to learn new things that was hidden in the service operators:

The number of endpoints the service operator creates

it is creating routes for public endpoints, for internals it is not creating something it is just passing in service overrides which got defined by the end user on the ctlplane CR.

It needs to know which CR reconciliation will result in a service that needs a keystone endpoint that needs to be routed. E.g. it needs to know that the NovaSpec.cellTemplates[].noVNCProxyServiceTemplate represent an entity that will be reconciled to a NovaNoVNCProxy CR and when that is reconciled will create a service that needs to be routed. While a very similarly structured  NovaSpec.cellTemplates[].metadataServiceTemplate will result in a NovaMetadata CR that will also create a service but does not need to be routed.
Also using the keystone interface type as signal for what needs to be routed is fairly opinionated. The keystone definition only says:
The interface type, which describes the visibility of the endpoint. Value is: - public. Visible by end users on a publicly available network interface. - internal. Visible by end users on an unmetered internal network interface. - admin. Visible by administrative users on a secure network interface.

So while it is easy to imagine that "visible on a publicly available interface" most of the cases means it needs to be routed out to a public network. However the definition of internal and admin type does not indicate that it is never need to be routed it only defines visibility. So if our internal_api network needs to be routed for some deployment scenario (edge?) then our current assumption about that only public needs to be routed won't hold.

The type of those endpoints and the logic that which endpoint needs routing and which isn't

yes it has the list of endpoint types, which is public and internal. The logic is "stupid" if it is public and no LoadBalancer override specified create route, otherwise just pass in the service override to the service operator and it does all the service part

The naming scheme of the k8s Service objects the service operator creates

Yes, this is the part where the openstack-operator requires knowledge on the naming scheme, but the service name can not be overridden. if there will be a change, it would require a manual change when updating to the new service operator version, but in which situation this will? I'd say the situations are really rare.

Unfortunately exposing the naming scheme of the Service drags more information with it. E.g. what are the cell level services, what is a cellName, how the cell name is included into the service name.

This creates extra coupling between the openstack-operators and the service operators. I dislike this increase of coupling.

FYI, I have updated the network_isolation samples to show how the overrides now look like. externalEndpoints is gone and only the overrides from the service template itself is used. so there is no longer a two way patching required as there is now only a single interface to customize the service.
+1 on not having two way to achieve the same thing.

I think all this boils down to the amount of benefits we get from the centralized solution versus the future risk we take by creating more coupling between the openstack-operator and the service-operator.

I think we need to talk about the goals we want to achieve with this change. So far I heard about the following goals:

make it possible to implement TLS in a single place
I think this is not possible after this change. Based on https://github.com/openstack-k8s-operators/keystone-operator/pull/289#discussion_r1295415582 For the TLS implementation we still need to adapt each service operator to use TLS (endpoint scheme change and cert secret usage).

allow seamlessly changing the openshift Route to some other way of exposing our services (Gateway API?)
This change makes the switch possible by changing openstack-operator. However before this change we already had every Route creation hidden within lib-common behind ExposeEndpoint() so switching to a new route resource would be a lib-common change.
The openstack-operator based route creation forces us to teach service operator specific knowledge (the number of services to expose with a route, the name of the k8s services etc) to openstack-operator, while the lib-common based solution would allow keeping the service operator specific knowledge to stay only in the service operators. (This is mostly due to the "call path". If openstack-operator creates the route then openstack-operator needs to know the information to create them, if lib-common creates the route then because lib-common is called by the service operator it is enough if the service operator knows this information)

decouple the service deployment step from the external exposure of that service
I think this goal refers to deployment pattern supported by the oc expose command. However I don't think we are actually supporting this pattern with the proposed change. For me the pattern is:
i) create a deployment with a service
ii) check that it works OK
iii) use oc expose to publish the service to the outside world
However the proposed change pre-creates the routes even before any service is deployed.
Also note that openstack itself might not support this pattern today as openstack needs to know the public URL of the service (e.g. for the keystone endpoint or for the compute vnc configuration) even before the openstack service can be fully deployed.

Please let me know if I missed other goals.

I think we need to talk about the goals we want to achieve with this change. So far I heard about the following goals:

make it possible to implement TLS in a single place
I think this is not possible after this change. Based on Update keystoneapi to use service override keystone-operator#289 (comment) For the TLS implementation we still need to adapt each service operator to use TLS (endpoint scheme change and cert secret usage).
allow seamlessly changing the openshift Route to some other way of exposing our services (Gateway API?)
This change makes the switch possible by changing openstack-operator. However before this change we already had every Route creation hidden within lib-common behind ExposeEndpoint() so switching to a new route resource would be a lib-common change.
The openstack-operator based route creation forces us to teach service operator specific knowledge (the number of services to expose with a route, the name of the k8s services etc) to openstack-operator, while the lib-common based solution would allow keeping the service operator specific knowledge to stay only in the service operators. (This is mostly due to the "call path". If openstack-operator creates the route then openstack-operator needs to know the information to create them, if lib-common creates the route then because lib-common is called by the service operator it is enough if the service operator knows this information)
decouple the service deployment step from the external exposure of that service
I think this goal refers to deployment pattern supported by the oc expose command. However I don't think we are actually supporting this pattern with the proposed change. For me the pattern is:
i) create a deployment with a service
ii) check that it works OK
iii) use oc expose to publish the service to the outside world
However the proposed change pre-creates the routes even before any service is deployed.
Also note that openstack itself might not support this pattern today as openstack needs to know the public URL of the service (e.g. for the keystone endpoint or for the compute vnc configuration) even before the openstack service can be fully deployed.

Please let me know if I missed other goals.

this indeed looks like an unwanted coupling, and teaching the CP operator a lot of services-specific things, great summary.

I think we need to talk about the goals we want to achieve with this change. So far I heard about the following goals:

make it possible to implement TLS in a single place
I think this is not possible after this change. Based on Update keystoneapi to use service override keystone-operator#289 (comment) For the TLS implementation we still need to adapt each service operator to use TLS (endpoint scheme change and cert secret usage).

With this change it is possible to:

handle TLS for public endpoints in a single place as all routes get created in a single place
manage TLS certs in a single place for the TLS-E situation when the route should use re-encryption to the backend deployment and only pass in a cert secret to the service (analog to rabbitmq)

In the situation for TLS-E the service operator required  change is:

use https if cert secret is provided
use the cert information from the secret in the deployment for e.g. httpd or service direct
consider the cert secret in the hash calc for configuration data to restart if the certs get renewed by cert-manager

allow seamlessly changing the openshift Route to some other way of exposing our services (Gateway API?)
This change makes the switch possible by changing openstack-operator. However before this change we already had every Route creation hidden within lib-common behind ExposeEndpoint() so switching to a new route resource would be a lib-common change.

or use a different ingress than route by passing in the endpointURL. No route would then be created and the user has to create the ingress manually.

The openstack-operator based route creation forces us to teach service operator specific knowledge (the number of services to expose with a route, the name of the k8s services etc) to openstack-operator, while the lib-common based solution would allow keeping the service operator specific knowledge to stay only in the service operators. (This is mostly due to the "call path". If openstack-operator creates the route then openstack-operator needs to know the information to create them, if lib-common creates the route then because lib-common is called by the service operator it is enough if the service operator knows this information)

decouple the service deployment step from the external exposure of that service
I think this goal refers to deployment pattern supported by the oc expose command. However I don't think we are actually supporting this pattern with the proposed change. For me the pattern is:
i) create a deployment with a service
ii) check that it works OK
iii) use oc expose to publish the service to the outside world
However the proposed change pre-creates the routes even before any service is deployed.
Also note that openstack itself might not support this pattern today as openstack needs to know the public URL of the service (e.g. for the keystone endpoint or for the compute vnc configuration) even before the openstack service can be fully deployed.

The current flow and implementation in this patch is only to have a simple process/reconciliation. An alternative workflow idea I have is:

do not pre-create route (like at the moment) in the openstack-operator
create OSP service CR without setting endointURL
let the service operators create their deployment + services
service gets initially registered with service url instead of route url
service-operators to set an "create ingress" annotation on the created service for which a route/ingress should be created and the service type is not LoadBalancer
for default situation with OCP route

on reconcile of the openstack-operator it checks for the services having the "create ingress" annotation on the service
openstack-operator creates route and set endpointURL
service operator updates its keystone-endpoint using the endpointURL information

if a different ingress should be used (might need a switch to disable create of route) user to set the endpointURL of the service and create the ingress manually

Also in this approach the openstack-operator would create certs after the initial create for the services and set the cert secret name. The service then switches to tls.

Please let me know if I missed other goals.
Additional goals:

reduce service operator dependencies (go.mod)

don't have a dependency of the service operators to OCP specific resource type routes. with this also can be used independent upstream or with native k8s
don't have a dependency of the service operators to cert-manager and provide just a named secret to be used

allow customization of services via overrides. This allows also the usage of 3rd party LoadBalancer instead of MetalLB
move into being able to use the service operators on native k8s
allow using a different ingress than OCP route

@stuggi I discovered that we need to include the novnc public URL into the nova-compute config. So from nova-operator perspective when the endpointURL will be set on NovaNoVNCProxy the EDPM compute config Secret will be updated. Then we expect the dataplane-operator to trigger the rerun of the ansible that copies that updated config to the EDPM nodes. The last part of this is not yet implemented, the dataplane-operator does not watch the config. But we need that anyhow for rabbit password rotation for example.

closing in favor of #457


Use Align function on a segment of the depth image

We need to find the depth of tags identified in the RGB image. Using the Align function on the entire IR image is resource consuming, and we are trying to reduce the burden of this process. Is it possible to define a range in the IR image and run the align function of that range alone (e.g. a range of 20X20 pixels)?

In applications with a processing burden such as align, you can offload some of the work onto the GPU.  With Nvidia GPUs this can be done by building the SDK with CUDA support.   For non-Nvidia GPUs, vendor-neutral GLSL Processing Blocks can be used, though it may be ineffective on low-power devices.
https://github.com/IntelRealSense/librealsense/issues/4905#issuecomment-533854888
In regard to isolating part of the image, this could be done by defining a 'Bounding Box' area on the screen that excludes data outside of the box.  More information on this can be found here:
https://github.com/IntelRealSense/librealsense/issues/2016

Thank you very much MartiG. Can you expand a little on the bounding box option? In our application we will have 32 regions of interest for which we would like to map the depth values to the RGB image. Can you apply 32 bounding boxes to a single frame and run the Align function on them?
From: MartyG-RealSense<EMAIL_ADDRESS>Sent: Monday, March 23, 2020 11:43 AM
To: IntelRealSense/librealsense<EMAIL_ADDRESS>Cc: Noam Levy<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [IntelRealSense/librealsense] Use Align function on a segment of the depth image (#6113)
In applications with a processing burden such as align, you can offload some of the work onto the GPU. With Nvidia GPUs this can be done by building the SDK with CUDA support. For non-Nvidia GPUs, vendor-neutral GLSL Processing Blocks can be used, though it may be ineffective on low-power devices.
#4905 (comment)https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIntelRealSense%2Flibrealsense%2Fissues%2F4905%23issuecomment-533854888&data=01|01|noaml%40brainsgate.com|7b3d35c8425f4af80b1808d7cf0e9331|ba1b9a8211954a63b7107dab2a24ddaf|0&sdata=MWb3hFUibMW0thDY9DTyp09HoJHFFoL39D09KzlwwX0%3D&reserved=0
In regard to isolating part of the image, this could be done by defining a 'Bounding Box' area on the screen that excludes data outside of the box. More information on this can be found here:
#2016https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIntelRealSense%2Flibrealsense%2Fissues%2F2016&data=01|01|noaml%40brainsgate.com|7b3d35c8425f4af80b1808d7cf0e9331|ba1b9a8211954a63b7107dab2a24ddaf|0&sdata=C5d1VULC9mRGFR1kcYvk71vByjQCEzYLCG%2FerxOmnh8%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIntelRealSense%2Flibrealsense%2Fissues%2F6113%23issuecomment-602486675&data=01|01|noaml%40brainsgate.com|7b3d35c8425f4af80b1808d7cf0e9331|ba1b9a8211954a63b7107dab2a24ddaf|0&sdata=WXcMZQy6gdXqba0ztEzCqO5Kkl63YJ6BG9hkMWPvSyc%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGGZS4VITXAHWDNH5P7NCI3RI4VKFANCNFSM4LRXDKMQ&data=01|01|noaml%40brainsgate.com|7b3d35c8425f4af80b1808d7cf0e9331|ba1b9a8211954a63b7107dab2a24ddaf|0&sdata=bFqGeh0Q8iBYZvdMiXy51LYEATS7WBywYe9%2FupA4YCw%3D&reserved=0.

It is certainly possible to define multiple bounding boxes on-screen at the same time in real-time.  An example of this is the MobileNet SSD person tracking program, whose multiple-box ability is demonstrated in the link below.
https://github.com/apoorvavinod/Real_time_Object_detection_and_tracking#mobilenet_ssd-with-kcf-tracker
I would therefore speculate that 32 boxes on screen should be possible as long as your computing hardware can cope with the processing involved in keeping track of the individual boxes (though the calculations may be less with static regions of interest than with moving boxes).
As long as you do the align operation after the 32 boxes have been updated then I don't see why align would not work, as the align would probably just be doing a normal align of the image data that is left remaining after the bounding boxes have excluded the unwanted parts.

This case will be closed after 7 days from the time of writing this message if there are no further comments.   Thanks!


FEAT add float scale threshold scorer

Description

This scorer can wrap a float-scale scorer when we require a binary true-false scorer but would like to see the rich output from a scale scorer. FYI @saphirq7

Tests and Documentation

added unit tests

As discussed, could you please make the update to store the original Likert score and include it in the scoring rationale?


artemisUnknown enum generated when there doesn't appear to be any unknowns

Bug description
When building, I get several errors in graphql_api.graphql.dart as every table that has some constraint on it appears to generate an "artemisUnknown" enum. The generated code is (graphql_api.graphql.dart):
  @JsonKey(unknownEnumValue: BrandConstraint.artemisUnknown)
  BrandConstraint constraint;

  @JsonKey(name: 'update_columns')
  List<BrandUpdateColumn> updateColumns;

the above generates a couple of errors Undefined name 'BrandConstraint' and The name 'BrandUpdateColumn' isn't a type so it can't be used as a type argument.  Further down the file:
enum brand_constraint {
  @JsonValue("brand_name_key")
  brandNameKey,
  @JsonValue("brand_pkey")
  brandPkey,
  @JsonValue("ARTEMIS_UNKNOWN")
  artemisUnknown,
}

Looking at the enums for BrandConstraint in my schema:
"""
unique or primary key constraints on table "brand"
"""
enum brand_constraint {
  """unique or primary key constraint"""
  brand_name_key

  """unique or primary key constraint"""
  brand_pkey
}

I am not sure where the third "unknown" enum is coming from. A clue could be that this error only presents itself when adding a mutation with an input type (see below for mutation code). Mutations that split out each field into its own variable do not present this issue.
The backend service is Hasura.
Specs
Artemis version: ^6.4.4-beta.1

build.yaml:
targets:
  $default:
    sources:
      - lib/**
      - lib/graphql/**
    builders:
      artemis:
        options:
          schema_mapping:
            - schema: lib/graphql/schema/koalaroo.schema.graphql
              queries_glob: lib/graphql/data/**/**.graphql
              output: lib/graphql/graphql_api.dart
          scalar_mapping:
            - graphql_type: timestamptz
              custom_parser_import: 'package:strayan_app/services/artemis_timeconvert.dart'
              dart_type: DateTime
            - graphql_type: jsonb
              dart_type: dynamic

Artemis output: https://gist.github.com/FickleLife/1b089eec16f6b03e0b90ff6da84bc79b
GraphQL schema: https://gist.github.com/FickleLife/de43d6aab9f08fc2172f90d1131cd3b9
GraphQL query:
This error only presents itself when adding a mutation with an input type. Mutations that split out each field into it's own variable do not present this issue. This is the mutation I am trying to add:
mutation ProductInsertOne2($payload: product_insert_input!) {
  insert_product_one(object: $payload) {
    __typename
    id
    brand {
      __typename
      id
    }
    productTags {
      __typename
      id
    }
  }
}

Apologies, but any clues on this one?

Hi, @FickleLife, I have faced the same issue on version ^6.4.4-beta.1. It seems that the generated enum class is lowercase_with_underscores style, but the style in @JsonValue(...) is UpperCamelCase. In your case, the BrandConstraint is not matched with brand_constraint.
 @JsonKey(unknownEnumValue: BrandConstraint.artemisUnknown)
  BrandConstraint constraint;

enum brand_constraint {
  @JsonValue("brand_name_key")
  brandNameKey,
  @JsonValue("brand_pkey")
  brandPkey,
  @JsonValue("ARTEMIS_UNKNOWN")
  artemisUnknown,
}

I changed the UpperCamelCase to lowercase_with_underscores manually, then everything is ok.
I'm not sure if this is workable for your case. Maybe you can try it.

I found a bug I'll make a PR after https://github.com/comigor/artemis/pull/165 will be merged

@FickleLife please check v6.5.1-beta.1

Thank you @vasilich6107 - all fixed.  Cheers!


Replace rather than update latest release

Uses github-script to delete tags/latest so we get a new latest release that matches our most recent release.
Example (I've since deleted these releases):

Dislike but ok

You'd prefer it as a single action to replace latest?

I think this is a bug with the new action you selected - can you confirm correct behaviour with them and raise an issue?

I think this is a bug with the new action you selected - can you confirm correct behaviour with them and raise an issue?

Seems to be correct behaviour https://github.com/softprops/action-gh-release/issues/47

I think this is a bug with the new action you selected - can you confirm correct behaviour with them and raise an issue?

Seems to be correct behaviour softprops/action-gh-release#47

Looks like this PR gives the behaviour we require.
softprops/action-gh-release/pull/188


Alias in trigger condition loses gain/offset in device

Embedded graph trigger conditions have a weakness when comparing an alias with gain/offset with another operand that has a different scale (literal or other watchable).  The gain/offset is not communicated to the device and the device checks the underlying item without applying the gain/offset, leading to confusion.
if alias1 = var1*10
then "Alais1 > 10" should be equal to "var1>1", but the device does   "var1>10"
Possibly better to handle on the server side by scaling other literals operands. Disallow edge cases of multiple alias operands.

Fixed by scaling literals. Does not allow scaled alias with anything else than a literal


Typescript intellisense performance timeouts/hints

I have recently found out, that certain dependency import kills vscode intellisense in my project for some reason (I have to yet investigate reason why - it's local dependency, so issue is on my side - maybe circular dep or smthing). It went from 5 seconds "Loading..." to about 255 seconds "Loading..." waiting for autocomplete dropdown. Hovers also don't work with "Loading...". Due to nature of my "nonstandard" setup, I had no idea what went wrong, did not notice exact time when it started and therefore suspected many things. (wsl2, docker devcontainer, monorepo, wrong configurations...).
Luckily I found this great guide https://github.com/microsoft/TypeScript/wiki/Performance-Tracing which pointed me to two files having mentioned local dependency import, taking about 100 seconds each to compile.  I'm using nextjs devserver so I don't  build with tsc (I think nextjs even doesn't use tsc in background - rather swc), editor probably does use tsc, therefore I did not suspect typescript to be an issue since devserver worked fine, just autocomplete did not.
 You can't even use snippets / text occurence autocomplete. It even stops working for other files too (other than one having problematic import). I can imagine some npm dependency to introduce similar issue "killing" our editors time to time. I don't like fact that due to my local dependency issue, autocomplete for other things, eg. other npm library stops working too.
Could this be improved somehow? Eg. Automagically performing performance tracing in background and throwing alerts in editor for problematic files. Or getting just partial intellisense while timeouting bad performing files. Waiting 200+ secs for autocomplete dropdown is nonsense.

Please file this against the TypeScript project with an example project demonstrating the issue


Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin'

I tried to run "npm run build"
Then appear this error. and I have issue with npm start.
"annguyen36:~/workspace/cezerin (master) $ npm run build

<EMAIL_ADDRESS>build /home/ubuntu/workspace/cezerin
NODE_ENV=production npm run compile && npm run theme:build && npm run webpack:admin

<EMAIL_ADDRESS>compile /home/ubuntu/workspace/cezerin
babel src/store -d dist/store --quiet

<EMAIL_ADDRESS>theme:build /home/ubuntu/workspace/cezerin
babel theme/src -d theme/dist --quiet && npm run webpack:store

<EMAIL_ADDRESS>webpack:store /home/ubuntu/workspace/cezerin
webpack --config webpack.config.store.js --mode production

Hash: b2af1e2f0e2ef9072973
Version: webpack 4.1.1
Time: 32163ms
Built at: 3/12/2018 12:55:07 AM
2 assets
Entrypoint app = assets/js/app-e441451a78a502bb9f2e.js
Entrypoint theme = assets/js/theme-9eb3390c7dd2fb28e1da.js
[9] ./node_modules/react-redux/es/index.js + 14 modules 37.4 KiB {1} [built]
|    15 modules
[14] ./node_modules/redux/es/index.js + 6 modules 20.6 KiB {1} [built]
|    7 modules
[66] ./node_modules/redux-form/es/index.js + 225 modules 296 KiB {1} [built]
|    226 modules
[67] ./src/store/shared/actions.js 19.3 KiB {1} [built]
[74] (webpack)/buildin/global.js 509 bytes {1} [built]
[140] ./node_modules/react-router-dom/es/index.js + 13 modules 13.4 KiB {1} [built]
|    14 modules
[147] ./src/store/shared/analytics/index.js 3.74 KiB {1} [built]
[148] ./src/store/shared/actionTypes.js 2.76 KiB {1} [built]
[194] multi theme 28 bytes {0} [built]
[195] ./src/store/shared/containers/search.js 596 bytes {1} [built]
[196] ./src/store/shared/containers/notfound.js 598 bytes {1} [built]
[277] ./src/store/shared/app.js 5.83 KiB {1} [built]
[279] ./src/store/shared/reducers.js 3.88 KiB {1} [built]
[295] ./src/store/client/index.js 1.52 KiB {1} [built]
[498] multi babel-polyfill ./src/store/client/index.js 40 bytes {1} [built]
+ 486 hidden modules
ERROR in multi theme
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin'
@ multi theme
ERROR in ./src/store/shared/containers/shared.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/shared.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/index.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/index.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/category.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/category.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/product.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/product.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/page.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/page.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/checkoutSuccess.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/checkoutSuccess.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/notfound.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/notfound.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/search.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/search.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
ERROR in ./src/store/shared/containers/checkout.js
Module not found: Error: Can't resolve 'theme' in '/home/ubuntu/workspace/cezerin/src/store/shared/containers'
@ ./src/store/shared/containers/checkout.js 17:13-29
@ ./src/store/shared/app.js
@ ./src/store/client/index.js
@ multi babel-polyfill ./src/store/client/index.js
Child html-webpack-plugin for "assets/index.html":
1 asset
Entrypoint undefined = assets/index.html
[0] (webpack)/buildin/module.js 519 bytes {0} [built]
[1] (webpack)/buildin/global.js 509 bytes {0} [built]
[3] ./node_modules/html-webpack-plugin/lib/loader.js!./theme/index.html 2.49 KiB {0} [built]
+ 1 hidden module
npm ERR! Linux 4.9.80-c9
npm ERR! argv "/home/ubuntu/.nvm/versions/node/v6.11.2/bin/node" "/home/ubuntu/.nvm/versions/node/v6.11.2/bin/npm" "run" "webpack:store"
npm ERR! node v6.11.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>webpack:store: webpack --config webpack.config.store.js --mode production
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>webpack:store script 'webpack --config webpack.config.store.js --mode production'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cezerin package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     webpack --config webpack.config.store.js --mode production
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cezerin
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cezerin
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/workspace/cezerin/npm-debug.log
npm ERR! Linux 4.9.80-c9
npm ERR! argv "/home/ubuntu/.nvm/versions/node/v6.11.2/bin/node" "/home/ubuntu/.nvm/versions/node/v6.11.2/bin/npm" "run" "theme:build"
npm ERR! node v6.11.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>theme:build: babel theme/src -d theme/dist --quiet && npm run webpack:store
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>theme:build script 'babel theme/src -d theme/dist --quiet && npm run webpack:store'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cezerin package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel theme/src -d theme/dist --quiet && npm run webpack:store
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cezerin
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cezerin
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/workspace/cezerin/npm-debug.log
npm ERR! Linux 4.9.80-c9
npm ERR! argv "/home/ubuntu/.nvm/versions/node/v6.11.2/bin/node" "/home/ubuntu/.nvm/versions/node/v6.11.2/bin/npm" "run" "build"
npm ERR! node v6.11.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: NODE_ENV=production npm run compile && npm run theme:build && npm run webpack:admin
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'NODE_ENV=production npm run compile && npm run theme:build && npm run webpack:admin'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cezerin package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_ENV=production npm run compile && npm run theme:build && npm run webpack:admin
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cezerin
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cezerin
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/workspace/cezerin/npm-debug.log"
Please help me.
Thanks a lot.

I think you should have newer version of node. Try instaling with node 8.9

I use LTS Node 8.10.

thanks Ill give it a shot
On Wed, Mar 14, 2018 at 5:56 AM, Restmount<EMAIL_ADDRESS>wrote:

I use LTS Node 8.10.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cezerin/cezerin/issues/397#issuecomment-372964957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGxBh3N8_eq6XsjcSyInu3OJzX5tbNWpks5teOlfgaJpZM4Sl8cd
.

Anyone resolved this issue?
It is happened to me on two environments
Linux and mac.
I tried different node versions changing them by nvm.

What's your Node.js and NPM version?
Do you execute npm run build in root folder?

i just got same problem.
My env:
node v8.11.1
npm 5.6.0
cezerin lastest

Just to clarify you do this:

npm i
npm run build
npm start

Check you console log.
Does dist folder exists on root and on /theme folder?

I am also facing the same issue on windows. have the latest version of the code , Node version is 8.11.2 . Can you please let me know how to resolve this?

sorry to distract you @restmount , i too got the same message in this ticket.  running latest everything & fresh build. I was following your instructions for "Getting started with github"

Actually, I got it to work.  Unconfirmed:   it was webpack as the issue.

Now I got the same issue on Mac. I am running npm 6.3.0. any ideas?

@dukemai
npm i && npm run build && npm start

if you'll see errors, please attach it here.

thanks, it works now. what is the difference between my previous steps. I did

yarn
yarn run build => failed here

I have the same issue on Mac OS, last version npm, node, cezerin.

+1 same issue

npm i --f

same issue, that happens when i use yarn.Finally with npm i && npm run build && npm start it works.

+1

I had the same problem on the 8.10 node version. Was solved by installing version 8.12

my solution: Run npm i --save ./theme. ->ok


[L] Payment options analysis & documentation based on prototypes

Description:
We need to document a simple options analysis (pros/cons; rationale; implications) to back up decision making around payment options. Will be blocked by 2 prototype tickets, and likely same person doing it
Acceptance Criteria:

[ ] Document outlining pros/cons/implications of payment options, informed by bambora and stripe payment prototypes

Development Checklist:

[ ] ...
[ ] ...
[ ] ...

Dependencies

Blocked by #479 and #448
Blocking

Relevant documentation as reference
Definition of Ready

[ ] Acceptance criteria are included
[ ] Wireframes are included (if applicable)
[ ] Design / Solution is accepted by Product Owner (if applicable)
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] UI meets accessibility requirements
[ ] Unit tests are written
[ ] Work is traceable in GitHub
[ ] PR linked to ticket number
[ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

[ ] Code is peer reviewed and has passed CI/CD tests

QA:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Code is potentially shippable to the production environment
[ ] Functional features have been tested and passed by QA
[ ] UI components tested by designer
[ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

PO Review:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Reviewed and approved by Product Owner

Notes:

A comparison between Bambora and Stripe is part of the Figjam file where the payment flows were documented as part of #465. Refer to this comment for Figjam link.
I've also attached a partially attempted/filled out PIA form. It is super high level of detail (and incomplete) but should probably be done in tandem with someone who will be filling it out for real - I'm happy to work with whomever that may be. Basically - as far as PI is considered when discussing Bambora vs Stripe, both options are going to be very similar in the major points of the PIA - namely the types of PI being collected and the assumptions of risks that go along with them. Bambora is much more difficult to get a clear answer on points of their data storage methodologies, their service providers and the location of their servers.
PIA_PRDT.docx
When it comes to the backcountry reservation system, the region where Osprey's responsibilities re: PCI compliance lie does not really overlap with either Bambora and Stripe. It is our responsibility to remain PCI compliant while collecting financial and personal information from our users, and that responsibility does not change much whether or not Bambora or Stripe is used.
My job as a software developer and consultant is to provide my best recommendations from a software development standpoint, and from that standpoint, Stripe is a clear, no-contest winner when it comes to choosing a payment processing service. Their modern administrative portal, extensive developer resources and implementation examples, and proven real-world use cases give me confidence that Stripe would effectively meet (and exceed) the payment service needs Osprey has for this new backcountry payment system. Bambora could be made to meet these needs too, but doesn't seem to hold the same pedigree necessary for the size and importance of the payment handling demand that BC Parks has. For this product to succeed, it will need to grow iteratively, so lets iterate using the modularity and scalability of a Stripe foundation with assurance it will grow with us.
Some things that are out of the scope of my comparison are any considerations that are not explicitly technical, for example: cost, contracts, and non-technical PIA/STRA considerations. I will say that I foresee developer implementation time being a huge upcoming investment that can be lessened/hastened by choosing a payment platform that is easy and versatile for developers to leverage.


events fire before images have loaded

images of a container are still loaded but the event already fired.
using angular 1.4.8
imagesloaded 4.1.0
and latest of this directive.
happens on dev, on prod both chrome and safari

Hi @pacu, could you show some code please? A plunkr/fiddle would be useful.

@homerjam sure. I'd need images from a service to recreate the situation on a plunkr so I'll try with code first.
Context: This is a image matching game, for a e-learning platform. there are two image carousels side by side and the user needs to match 2 of them. There are images that are served statically from the web server and others that come from a service. the responses are quite big and but the image quality is very important for the purpose of the platform. There are some overlays for these images and re-scaling of resources to be done once the images are rendered on the screen. that's why I need to know when the images have been loaded completely.
HTML file

                                        <scale-meter ng-if="showScales" id="{{'satellite-scale-'+$index}}" properties="sPhoto.scaleProperties" width="394" height="20"></scale-meter>

controller.js
$scope.carrouselSatelliteLoaded = {
          always: function(instance) {
              // Do stuff
          },

          done: function(instance) {

              console.log('pl-satellite-slides-carrousel LOADED');

          },

          fail: function(instance) {
              // Do stuff
              console.log("pl-satellite-slides-carrousel LOADED FAILED");
          }
      };

I'm on my phone so can't look properly but a couple of thoughts - can you
try using ng-src for all images. And are the images progressive jpegs? I
wonder if that could be a factor...
On 9 Dec 2016 6:46 p.m., "Francisco Gindre"<EMAIL_ADDRESS>wrote:
@homerjam https://github.com/homerjam sure. I'd need images from a
service to recreate the situation on a plunkr so I'll try with code first.
Context: This is a image matching game, for a e-learning platform. there
are two image carousels side by side and the user needs to match 2 of them.
There are images that are served statically from the web server and others
that come from a service. the responses are quite big and but the image
quality is very important for the purpose of the platform. There are some
overlays for these images and re-scaling of resources to be done once the
images are rendered on the screen. that's why I need to know when the
images have been loaded completely.
HTML file

                                    <scale-meter

ng-if="showScales" id="{{'satellite-scale-'+$index}}"
properties="sPhoto.scaleProperties" width="394"
height="20">

controller.js
$scope.carrouselSatelliteLoaded = {
always: function(instance) {
// Do stuff
},
      done: function(instance) {

          console.log('pl-satellite-slides-carrousel LOADED');

      },

      fail: function(instance) {
          // Do stuff
          console.log("pl-satellite-slides-carrousel LOADED FAILED");
      }
  };

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/homerjam/angular-images-loaded/issues/11#issuecomment-266090135,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAcGUy9d9l11TmCTbFq21PinDfcIsyTks5rGaIYgaJpZM4LIiX8
.

I found the problem I had a typo on several images and the  did not have the ending /
this made the DOM render but the directive to fail and to work only with the static images that where  correctly tagged

Glad you figured it out!
On 11 Dec 2016 8:36 p.m., "Francisco Gindre"<EMAIL_ADDRESS>wrote:

I found the problem I had a typo on several images and the did not have
the ending /
this made the DOM render but the directive to fail and to work only with
the static images that where correctly tagged
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/homerjam/angular-images-loaded/issues/11#issuecomment-266305944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAcGbQwVxg-UikI-ulSMf5zdDJVUDWcks5rHF60gaJpZM4LIiX8
.

@homerjam It was a false positive. I can still see the same issue as before regardless having a well-formed html now.
The JPEGs I'm loading are not progressive but the PNGs are actually interlaced  now that you mentioned it.
I'll try to remove those and give you an update

Ok. The quickest way to resolve will be creating a live example - I believe the problem probably originates outside of the scope of this plugin. You can use https://placehold.it/ or http://lorempixel.com/ for images.

@homerjam  I suck at plunkr so I don't know how to include angular-images-loaded.
https://plnkr.co/edit/SqMauzKWUetm34p6VLWr?p=info

I've added angular-images-loaded via rawgit. I've also updated your plunkr to show the plugin working (even with failing images). Possibly you've misunderstood how images-loaded works?
https://plnkr.co/edit/IEOFXDoXCPQv0gCY92Oc?p=preview

Possibly you've misunderstood how images-loaded works?
I wouldn't discard that option either. I'm replicating this on my project to see what happens.
thanks


3rd level Cascading Filters

I have a problem similar to what's described in Issue #1010. As I mentioned there, I want to implement 3rd level filtering (IdDepartamento -> IdProvincia -> IdDistrito), with all data being taken from a single table.
This is how my table with the 3 ids work:

The first two filters are working, but when I select the third combo, it just validates with IdProvincia (second combo), and not with IdDepartamento(firts combo).
I want to implement that logic in a form.
Here is the code, I use custom lookups because the first two Ids need special conditions to be met :
    [LookupEditor(typeof(Scripts.UbigeoDepartamentoLookup))]
    public String IdDepartamento { get; set; }
    [LookupEditor(typeof(Scripts.UbigeoDepartamentoProvinciaLookup),
    CascadeFrom = "IdDepartamento", CascadeField = "IdDepartamento")]
    public String IdProvincia { get; set; }
    [LookupEditor(typeof(Scripts.UbigeoDepartamentoProvinciaDistritoLookup),
    CascadeFrom = "IdProvincia", CascadeField = "IdProvincia")]
    public String IdDistrito { get; set; }

How can I validate the 3rd level filtering correctly?  I can't find where or how to do it, so I'd like some help with this.
Thanks in advance.

Does this lookup, UbigeoDepartamentoProvinciaDistritoLookup, include IdProvincia and other fields.

This is UbigeoDepartamentoProvinciaDistritoLookup code:
public class UbigeoDepartamentoProvinciaDistritoLookup : RowLookupScript<Entities.UbigeoRow>
{
public UbigeoDepartamentoProvinciaDistritoLookup()
{
IdField = UbigeoRow.Fields.IdDistrito.PropertyName;
TextField = UbigeoRow.Fields.Nombre.PropertyName;
}
    protected override void PrepareQuery(SqlQuery query)
    {
        base.PrepareQuery(query);
        var fld = UbigeoRow.Fields;
        query

        .Select (fld.IdDepartamento)
        .Select(fld.IdProvincia)
            .Where(

                new Criteria(fld.IdDistrito) != 0 &
                new Criteria(fld.IdProvincia) != "" &
                new Criteria(fld.IdProvincia).IsNotNull() &
                new Criteria(fld.IdDepartamento) != "" &
                new Criteria(fld.IdDepartamento).IsNotNull());
    }

    protected override void ApplyOrder(SqlQuery query)
    {
    }
}

If i understand right, your IdDistrio is not empty but it brings distrito from all departments. This is completely normal, you need to use a unique ID, it won't work this way.

You might try using a combination ID, e.g. IDDepartmanto_IdProvincia, like 02_02

Yes, IdDistrito is not empty, but it brings Distritos (Districts) from all departments.
I will try to use a combination ID and post here if it works.

Hi @CAlva123 & @volkanceylan ,
When it rains, it pours!
I am having exactly the same issue...and I am even pushing to reach a 4th level cascading filter on the same table. Is that even possible Volkan?
I would really like to hear about your results @CAlva123 - if you would be so kind to share.

I combine both Id's in mytable.Row using CONCAT:
[DisplayName("combination ID"), Size(4), NotNull, LookupInclude, Expression("CONCAT(T0.[IdDepartamento], CONCAT('_', T0.[IdProvincia]))")]
public String IdDepPro
{
get { return Fields.IdDepPro[this]; }
set { Fields.IdDepPro[this] = value; }
}
And this is the result:

However,  I don't know how or where I can add the validation for the 3rd combo using this new field.
I have tried some combinations in my lookup, but without success.
Can you help me a little more with this please?

That new field will become CascadeField, that's all.


Feature/update

Done

Change txHash to tx_hash
Update ain-js version to 1.1.2
Add deploy_workers script
Add start_workers script

Thanks for reviews! Merged!

Thanks for reviews! Merged!


Fix typo

Description
Address https://github.com/Azure/azure-sdk-for-java/issues/31637
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Zeros appear in error message in Programmer mode when using binary

Describe the bug

When attempting to divide by zero in Programmer mode when set to binary, the error message appears as "00Cannot divide by zero". Trying 0 divided by 0 will give "000Result is undefined". In binary mode, leading zeros are added on the beginning according to the number of other characters in the display to make the number of characters divisible by 4. However, it also does this when there is an error on the display.
Steps To Reproduce

Go into Programmer mode
Switch to binary (BIN)
Type any number divided by 0
See error message with 0s at the beginning

Expected behavior

The error message would appear without any 0s at the beginning.
Screenshots

Device and Application Information

OS Build: Windows 10 Home build 19045.4894
Architecture: 64-bit
Application Version: 11.2405.2.0
Region: en-US
Dev Version Installed: None

Additional context

Requested Assignment

I'm just reporting this problem.  I don't want to fix it.

Here's an explanation in English of why zero cannot be divided by zero:
The Problem with Dividing Zero by Zero
Dividing any number by zero is undefined in mathematics. Here's why, specifically in the case of 0 divided by 0:

Division as the Inverse of Multiplication: Division is the opposite of multiplication.
When we say a / b = c, it means that b * c = a.
Applying it to 0/0: If 0 / 0 = c, then it should mean 0 * c = 0.
The Issue: The problem is that any number multiplied by 0 equals 0. This means there's no single, unique answer for 'c'. It could be 1, 5, -3, or any other number.
Indeterminate: Because there's no single answer, we say 0/0 is "indeterminate". It doesn't have a defined value.
In simpler terms:

Imagine you have zero cookies, and you want to divide them equally among zero friends. How many cookies does each friend get? The question doesn't make sense because there are no cookies and no friends to divide them among.

The Problem with Dividing Zero by Zero
Dividing any number by zero is undefined in mathematics. Here's why, specifically in the case of 0 divided by 0:

Division as the Inverse of Multiplication: Division is the opposite of multiplication.
When we say a / b = c, it means that b * c = a.
Applying it to 0/0: If 0 / 0 = c, then it should mean 0 * c = 0.
The Issue: The problem is that any number multiplied by 0 equals 0. This means there's no single, unique answer for 'c'. It could be 1, 5, -3, or any other number.
Indeterminate: Because there's no single answer, we say 0/0 is "indeterminate". It doesn't have a defined value.
In simpler terms:

Imagine you have zero cookies, and you want to divide them equally among zero friends. How many cookies does each friend get? The question doesn't make sense because there are no cookies and no friends to divide them among.

Hello, I would like to take a look at this please.


Will not tansfer to wallet

Wallet will not sync, (V<IP_ADDRESS>-g; Tor+OBFS4 connection online) no clear instructions on how to fix the issue. Purchased and confirmed coin, the balances will show up as zero. Always in syncing mode, staking will not connect (wallet offline), other internal wallets working fine. My system is Windows 7, X86
Symptoms: Total balance is shown as 0.00 XSPEC, no transactions are shown, All 6 Balances (public, private, reserved, stake, unconfirmed, immature) are shown as zero. When going to "Wallets"->"Receive" addresses (default address and default stealth address) are there. Restarted numerous times, rebooted, new IP . Need some clear instructions on what is going on and how to fix it.

Please take a look here: https://github.com/bitcoinx2/spectre/wiki/FAQ#6-i-have-zero-connections
And use Slack for further user support questions please. :)

Duplicate of https://github.com/spectrecoin/spectre/issues/21


Document DAS-CMOP and MW

I added some documentation for both DAS-CMOP and MW.
I put a picture for all MW problems, but only selected 2 examples for DAS-CMOP. It doesn't make much sense to show all 144 combinations.

Awesome! I just had a look and it looks very nice. This is exactly what I had in mind!
(Yes for DAS-CMOP it really does not make sense to add all the plots!)


for windows.

Coverage remained the same at 50.3% when pulling 1cbde2d7bae1f8057b814b5d08a5402863832ecf on windows_metric into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

Coverage remained the same at 50.3% when pulling a5eda3a3b9b4bd94a21bedf6cf03cbba026a9c88 on windows_metric into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

Coverage remained the same at 50.3% when pulling 830988494b3ac16a2f01a0d0decc0fd89e6fc211 on windows_metric into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

Coverage remained the same at 50.3% when pulling dea88b3c1693fc1e32dac7bdc9f8d037929bdc54 on windows_metric into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

Coverage remained the same at 50.3% when pulling d4bc158a4efe6015d4fabe6af4515e8c7a3a6a9d on windows_metric into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

Coverage remained the same at 50.3% when pulling a8f6624a4f81732685ae36558a5800cbb80d9cb6 on windows_metric into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

Coverage remained the same at 50.3% when pulling 56f51eacbe6ff57f5d5b110a3001c947484e6fc0 on windows_metric into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

LGTM! :rocket:

Coverage remained the same at 50.3% when pulling c854a9ec37476a53846515bfd9f7d3c17597dad4 on windows_metric into 6bed630d81a2d4151a5a743d181654e1c5561de3 on master.

Coverage remained the same at 50.3% when pulling 3e3f5ec7990b636ecf5829be0d03c5deadac1159 on windows_metric into 6bed630d81a2d4151a5a743d181654e1c5561de3 on master.

Coverage remained the same at 50.3% when pulling 3e3f5ec7990b636ecf5829be0d03c5deadac1159 on windows_metric into 6bed630d81a2d4151a5a743d181654e1c5561de3 on master.

Coverage remained the same at 50.3% when pulling 3e3f5ec7990b636ecf5829be0d03c5deadac1159 on windows_metric into 6bed630d81a2d4151a5a743d181654e1c5561de3 on master.

Coverage remained the same at 50.3% when pulling b810b8de3e8fc4b20bd24987ce2e51056cdfbc61 on windows_metric into 6bed630d81a2d4151a5a743d181654e1c5561de3 on master.


docs(ui/card): use the setup script for exmple and docs

Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

Codecov Report

Merging #425 (a2603a8) into docs/script-setup (f3ccb83) will not change coverage.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           docs/script-setup     #425   +/-   ##
==================================================
  Coverage              96.38%   96.38%
==================================================
  Files                    217      217
  Lines                   5148     5148
  Branches                 944      944
==================================================
  Hits                    4962     4962
  Misses                   186      186

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 f3ccb83...a2603a8. Read the comment docs.

需要把文档中的引入部分删掉

还有一个就是 以后尽量一个组件一个pr


Issue with Fill

Bug Description
The fill does not consistently work.
Expected Behaviour
Fill should expand the image  and fill the entire page
Steps to Reproduce

Add an image to a page
Decrease the size of the image by dragging from a corner
Press the fill button
Notice that the image is brought to the top left corner as the existing size

Screenshots

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

@jauyong duplicate of #942.


Add support french.

Support for French language.

Same issue here for german and italian. I think ending up with 200 -or is not a solution here. Would it be better to 1.) determine the language of the os 2.) have a hashmap de => valueX 3.) check if the property exists? Or can you think of another way to check if the required permissions exist which is language independent?


Sort according to country code

Will be great if we can sort like this
+1 Canada
+7 US
+20 Egypt
+27 South Africa

Hi, please provide this sorting functionality or search functionality for countries, it will be difficult to user to scroll through all the countries. Right now, the sorting is based on country names but we are not displaying country names. At least, give option to display country name.
thanks.


Angular distance for one lens and multiple sources

Closes #822

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 97.103%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
4559

Relevant Lines:
4695

💛  - Coveralls

@hsinfan1996 would you be able to give this one a quick review?

@hsinfan1996 would you be able to give this one a quick review?

@damonge Thank you. It is working as expected and does not break anything on our end.

Great, can you officially review and approve?


Milestone2: Processing data

In this milestone I:

Created each model class based on the ER diagram
Added additional methods for each class
test the class with rails console

Thank you


dotnet-ubuntu.16.10-x<IP_ADDRESS>.tar.gz can't downloaded

dotnet-install: Downloading https://dotnetcli.blob.core.windows.net/dotnet/preview/Binaries/1.0.0/dotnet-ubuntu.16.10-x<IP_ADDRESS>.tar.gz
dotnet_install: Error: Download failed

If you are trying to install by following the Wiki post I'm not 100% sure this will work since I wrote it when we we're on pre-releases of .NET Core.


Merge upstream patches

These are the needed patches, already submitted upstream, but not merged.

thanks @oleorhagen !
thanks @alfrunes !
I think/hope I fixed everything.


refactor: streamline some traits and bounds

What this does

removes uneeded trait bounds in a few places (1st commit),
pegs the group trait on the zkcrypto::group::Group (2nd commit),

What this does not do

use the zkcrypto::group::GroupEncoding trait, as the chosen GroupEncoding implementations for Pallas and Vesta are the same ([u8;32]) and it would thus not be possible to implement two distinct instances of CompressedGroupElement on this type, requiring exactly the same sort of wrapper as we have now.

Partially helps with #198.
Happy to adapt depending on feedback:

e.g. for cosmetics, we could rename the Group::Scalar associated type to Something Else - feel free to suggest -, alleviating the ambiguity with zkcrypto::group::Group::Scalar and allowing us to replace the qualified instances <G as Group>::Scalar to G::SomethingElse.
I'm also fine with giving up on the second commit (or #198) as I'm not sure it would help with #202.

What this does

removes uneeded trait bounds in a few places (1st commit),
pegs the group trait on the zkcrypto::group::Group (2nd commit),

What this does not do

use the zkcrypto::group::GroupEncoding trait, as the chosen GroupEncoding implementations for Pallas and Vesta are the same ([u8;32]) and it would thus not be possible to implement two distinct instances of CompressedGroupElement on this type, requiring exactly the same sort of wrapper as we have now.

Partially helps with #198.
Happy to adapt depending on feedback:

e.g. for cosmetics, we could rename the Group::Scalar associated type to Something Else - feel free to suggest -, alleviating the ambiguity with zkcrypto::group::Group::Scalar and allowing us to replace the qualified instances <G as Group>::Scalar to G::SomethingElse.
I'm also fine with giving up on the second commit (or Move to actual group traits and create GroupExt for the extra extensions of the Group trait #198) as I'm not sure it would help with Reduce duplicate code across different curve cycle providers #202.

Thanks for the PR, @huitseeker!
The first commit looks great!
I've mixed feelings about the second commit. Could you please elaborate a bit more on what is the gain from taking a dependency on the group crate? I couldn't quite tell if it simplified the Nova code in some way. It looks like it made our code more verbose because we have to disambiguate the two Groups.

I couldn't quite tell if it simplified the Nova code in some way. It looks like it made our code more verbose because we have to disambiguate the two Groups.

Yes. That's what I was saying. Though the disambiguation can be done by chosing a different name for the associated type, rather than using a qualified, the gains are overall limited to fewer explicit trait requirements.
I was hoping for @CPerezz to share some insight. Otherwise, as I mentioned, I'm happy to revert the last commit.

Hey!
Apologies, I've been OOO for the last days.
So I kinda see the point of @srinathsetty but I think once #198 is actually done, the syntax could definitely improve.
But I think once #198 is executed (Will try to start this week), then this syntax will not happen or at least the situation will improve.
Not sure which is the best way to go for now. Specially since #198 is not even prototyped yet. The main idea for me there is to have the Group trait being declared in group and then, any other thing we miss, added on a GroupExt crate or similar.

@CPerezz @srinathsetty I've reverted the last commit, leaving addressing the group-based trait to @CPerezz when #198 is more fleshed out.

@huitseeker will try to get at it this week! There's quiote a lot of work on HyperNova


Add wix installer toolset in appveyor setup

The msi packaging tests won't be run if this is not installed.
These is no change at all to scons itself - so no doc or test, and no change to CHANGES.txt.
Signed-off-by: Mats Wichmann<EMAIL_ADDRESS>Contributor Checklist:

[X] I have created a new test or updated the unit tests to cover the new/changed functionality.
[ ] I have updated master/src/CHANGES.txt directory (and read the README.txt in that directory)
[X] I have updated the appropriate documentation

Coverage decreased (-1.06%) to 78.911% when pulling 73db02496427f4c62ed8a5eb622e1360340dfd70 on mwichmann:add-wixtoolset into 748b05d34deacb718a57b2463aa9a1f10958740c on SCons:master.

Hmmm, it installs fine but apparently isn't being found, as the tests are still skipped. I had this working after manual installation, does chocolatey not add the path?
139/294 (47.28%) C:\\Python27\\python.exe -tt test\packaging\msi\explicit-target.py
No 'candle' found; skipping test
NO RESULT for test of C:\projects\scons\src\script\scons.py
	at line 46 of test\packaging\msi\explicit-target.py
140/294 (47.62%) C:\\Python27\\python.exe -tt test\packaging\msi\file-placement.py
No 'candle' found; skipping test
NO RESULT for test of C:\projects\scons\src\script\scons.py
	at line 45 of test\packaging\msi\file-placement.py
141/294 (47.96%) C:\\Python27\\python.exe -tt test\packaging\msi\package.py
No 'candle' found; skipping test
NO RESULT for test of C:\projects\scons\src\script\scons.py
	at line 45 of test\packaging\msi\package.py

expecting is to have landed in c:\Program Files (x86)\WiX Toolset 3.11\bin

Take a look at what I did with clang and java for windows. Something similar is likely right, and/or we add chocolatey's path to the default windows path..  That might be the simplest.. Try that?

No, the choco path won't help, that's mainly its own internal stuff.  If the thing it's installing is a standard pkg, it just goes the normal place, for wix it's the one a few comments above in the 32-bit Program FIles.  If it's not a full installer thing, it goes into whatever is the ChocolateyToolsLocation path, but even there you get subdirs, keeping the helpful Windows model of everything-gets-their-very-own-directory.  All this from experimentation the other day, I'm no choco expert.  I had to learn about ChocolateyToolsLocation because it defaults to C:\tools, which an anti-ransomware tool I have objects to and end ends up blocking - things can't write to the "root directory'.

I have a blurb of logic to  check reasonable default paths for wix install and add to PATH.
See:
https://github.com/bdbaddog/scons/commit/a30df639b15c681e1b0b8585b6982b4ff929a2bd

Hmmm, choco does make shims for some of the things it installs, I think only for the ones that don't have a classic installer and end up in Program Files* ... so that doesn't include wix.

I added a note with a pointer to a commit on a branch in my repo which
fixes finding the tool, but then yields some errors in the logic.
Care to take on resolving that and pulling in my location finding logic?
On Sat, Oct 6, 2018 at 10:52 AM Mats Wichmann<EMAIL_ADDRESS>wrote:

Hmmm, choco does make shims for some of the things it installs, I think
only for the ones that don't have a classic installer and end up in Program
Files* ... so that doesn't include wix.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SCons/scons/pull/3204#issuecomment-427593708, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFBNDJHasHjrx6sBUIghqxN9KmaiuXqks5uiO3tgaJpZM4W_p66
.

Hmmm, magical new failure, about multiple targets. e.g. the file-placement test. I don't recall seeing this when I was creating the patch. Guess this will need more work.
File "C:\Users\appveyor\AppData\Local\Temp\1\testcmd.4516.toeggl23\SConstruct", line 19, in <module>
140/294 (47.62%) C:\\Python36\\python.exe -tt test\packaging\msi\file-placement.py
FAILED test of C:\projects\scons\src\script\scons.py
	at line 624 of C:\projects\scons\testing\framework\TestCommon.py (_complete)
	from line 727 of C:\projects\scons\testing\framework\TestCommon.py (run)
	from line 393 of C:\projects\scons\testing\framework\TestSCons.py (run)
	from line 67 of test\packaging\msi\file-placement.py
C:\projects\scons\src\script\scons.py returned 2
STDOUT =========================================================================
scons: Reading SConscript files ...
STDERR =========================================================================
scons: *** Two environments with different actions were specified for the same target: foo-1.2
File "C:\Users\appveyor\AppData\Local\Temp\1\testcmd.4980.bbqbmgk_\SConstruct", line 12, in <module>

So I still don't get this: all three msi tests fail with the same kind of error, which claims multiple environments. I see only one environment being created... this is the one from explicit-target.py.
scons: *** Two environments with different actions were specified for the same target: mypackage.msi

So this should be finding candle and light without adding the toolset with choco, since we hear the Appveyor images already come with it.  Should I remove the .appveyor.yml bit and see if it does find it?  I have installed the standard package and it sets the WIX environment varialble, which the patch now fetches; and also the last-chance location should be the correct one.

Appveyor responded this:
http://help.appveyor.com/discussions/questions/34138-where-is-the-wix-binaries-located
On Mon, Feb 4, 2019, 5:25 PM William Deegan<EMAIL_ADDRESS>wrote:

It doesn't. they're not all in choco's path.
I've gone down this route before trust me on this...
On Mon, Feb 4, 2019 at 5:49 PM Mats Wichmann<EMAIL_ADDRESS>wrote:

So this should be finding candle and light without adding the toolset
with choco, since we hear the Appveyor images already come with it.
Should
I remove the .appveyor.yml bit and see if it does find it? I have
installed
the standard package and it sets the WIX environment varialble, which the
patch now fetches; and also the last-chance location should be the
correct
one.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SCons/scons/pull/3204#issuecomment-460444664, or
mute
the thread
<
https://github.com/notifications/unsubscribe-auth/AAFBNMY8bzOLdvSL4KGpOwfCowkrQuP3ks5vKLj4gaJpZM4W_p66
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SCons/scons/pull/3204#issuecomment-460454397, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF2YzMIyuEQbo88mLRxV0tK45TP8Q_tXks5vKMFjgaJpZM4W_p66
.

It doesn't. they're not all in choco's path. I've gone down this route before trust me on this...
…

In my test VM it does find it with the code in this PR, I just tried - and the location is the same as we just heard back from appveyor.

Closing this, will proceed with #3294 instead.


placeholders for open data plans

create a template and placeholders for the department open data plans

this work was completed at plans.opendata.rocks; link added to manual


Set TLS 1.2 protocol to allow communication with chocolatey.org

The removal of TLS 1.2 on the chocolatey.org website has stopped the Package Verifier from being able to download chocolatey in the normal way.
We've confirmed that the Package Verifier virtual image has the correct cipher suites. The protocol just needs to be enabled.

@pauby are you happy to get this released, and then we can close this out?

@pauby I am fairly sure that this has been released, so I am going to go ahead and close out this issue, let me know if you have any questions.

This hasn't been publicly released as yet. It will be released when I submit the new package code.

This has been released now.