Design System - Add notifications

https://www.figma.com/file/2MLHeIeL6XPVi3Tc2DfFCr/❖-Leather-–-Design-System?type=design&node-id=8651-167026&mode=design&t=GWkPk0GFV2vMVala-4

This is typically what I'd call a toast, re https://react-hot-toast.com/

I believe this issue is intended for inline notification messages whereas https://github.com/leather-wallet/extension/issues/4310 is for toasts

@kyranjamie https://www.radix-ui.com/primitives/docs/components/toast

It's really more about how it behaves than how it looks. These are fairly simple UI elements and we can style them as we like. The behaviour isn't something we can easily change.
If this is to be placed in the corner, it's a toast. If it's inline with content how we choose, it's a callout

I presume once we add this callout component, we'll replace all instances such as here as part of this ticket – or should we create separate tickets for each instance where it'll need application?

I think for this it can be part of the same issue to replace?

I'm moving this to the product backlog to create an inventory of where we currently have callouts in the design, and determine whether it makes sense to update the current instances or wait on redesigning core flows.

@mica000 FYI I'm adding this to the approval UX milestone since I presume it's most immediately needed for that project

@markmhendrickson I see this more part of the "estab. ui" milestone since it's a dumb component several projects will use, similar to items, buttons, etc..

That was all I'd done basically, so no worries with the branch
import { css } from 'leather-styles/css';
import { Box, type BoxProps } from 'leather-styles/jsx';

const calloutStyles = css({
  color: 'ink.2',
  '&[data-variant="default"]': {
    backgroundColor: 'success.background',
  },
  '&[data-variant="success"]': {
    backgroundColor: 'success.background',
  },
  '&[data-variant="error"]': {
    backgroundColor: 'error.background',
  },
  '&[data-variant="warning"]': {
    backgroundColor: 'warning.label',
  },
  '&[data-variant="neutral"]': {
    backgroundColor: 'accent.non-interactive',
  },
});

interface CalloutProps extends BoxProps {
  variant?: 'info' | 'warning' | 'error' | 'success' | 'neutral' | 'default';
}
export function Callout(props: CalloutProps) {
  const { variant = 'default', ...rest } = props;
  return <Box data-variant={variant} className={calloutStyles} {...rest} />;
}

It appears this issue is dependent on: https://github.com/leather-wallet/extension/issues/4831
Will do that one first.

Replace TestnetBtcMessage component with callout when ready src/app/pages/send/send-crypto-asset-form/family/bitcoin/components/testnet-btc-message.tsx


Error while installing ukfast/safedns v1.1.2: checksum list has unexpected SHA-256 hash

When attempting to use v1.1.2 of the plugin e.g.
safedns = {       source = "ukfast/safedns"       version = "1.1.2"     }
Then running terraform init, i'm receiving the following error:

Error: Failed to install provider
Error while installing ukfast/safedns v1.1.2: checksum list has unexpected
SHA-256 hash 1ed01664ddfd8b63d298110ed27f40b5e9d8d7ac408b7323fd52fa77f8d33980
(expected 7a1fea04bdcfeadbbf317603451ece83b374325a5d9442718d142fb989c2953f)

Hi @djalertive - this provider has been moved over to the ans-group organisation, however it would appear the redirect is broken.
I would recommend updating your provider reference whilst we look into this:
https://registry.terraform.io/providers/ans-group/safedns/1.1.3

Thanks for the quick response @0x4c6565, updating to the following resulted in the terraform init completing without error:
safedns = {       source = "ans-group/safedns"     }

@0x4c6565 any chance this can be updated within README or updating the registry docs to reflect this?

@0x4c6565 any chance this can be updated within README or updating the registry docs to reflect this?

Added to readme @rcunningham-cr:
https://github.com/ans-group/terraform-provider-safedns/blob/master/README.md#upgrading


Update PHPUnit

Alongside support for PHP 8.0 (#11), the supported version of PHPUnit should be updated to 9+.
This implies that tests will no longer to be able to be run on versions of PHP <7.3, which is the minimal version of PHP supported by PHPUnit 9.
Should anyone wish to make a PR including support for older versions using PHPUnit-Polyfills then this would be very welcome!

WIP Branch: see #16

Closed with #16


Update blog command with correct year

The commands for creating a blog post template file still use the year 2023. This PR updates the year to 2024.

good catch! We might consider replacing this with some hugo magic to print the current year, but let's fix it that way first


Running Connexion as an extension

It would be nice to be able to pass an existing Flask app instance to connexion.
A use case is a Flask application that implements other stuff than swagger-based API endpoints.
This is my lame attempt to do it: https://gist.github.com/tarekziade/595f003c0a9b9aa0934f21b814717441
It "works" but I think we'd need something self-contained to the Blueprint, and I was not able to do that kind of integration.

You should be able to use the Api class of Connexion without the App: https://github.com/zalando/connexion/blob/master/connexion/api.py#L57

Yes I was able to do it eventually. I updated the gist. Thanks!

Note that the way to do this as of the version 1.1.15 is from connexion import Api


Update lxml version to support python3.11

This PR updates lxml version to suport python3.11
python3-saml also has to be updated because of a dependancy.

@subbink we will definitely need some of the other members to review and verify this as I can't help but think I remember there being some issue that previously popped up and lead to a change revert in relation to upgrading the lxml package.
Does this ring a bell @jbe-dw or @corubba?

@corubba thank you. That rings a bell and I believe that is what I was thinking of. It doesn't seem like a great idea for us to proceed with the addition of something that isn't yet officially supported. I realize there are probably other instances like this in the project already, but I'm not trying to make matters worse.

@subbink I am rejecting this PR for the time being as it seems that the required changes would introduce another unsupported configuration into the project. If this can be disproved or a reasonable alternative ensured, then I would be happy to reconsider.

@nkukard this is great information, thank you!
I will reopen and get this done.

I'm busy testing a MR to fix this, will submit soon.

Please don't forget, that we had some issues with high lxml version, see  #1307
Please check this PR against various distributions!

Please don't forget, that we had some issues with higher lxml version, see #1307
Please check this PR against various distributions!

It would of helped if logs were included. I will ask for them.
Is the recommended way of installing PowerDNS Admin not using a venv? or the Docker container?
It is unlikely any distribution will have the versions listed in requirements.txt installed by the OS as packages.

Is the recommended way of installing PowerDNS Admin not using a venv? or the Docker container?

Locally in a venv and the public docker image are the recommended options. AFAIK we have removed all documentations working without venv.
Some python packages have dependencies with system libraries or system tools. These dependencies can break the installation undepended from venv.

Should be fine. Is there perhaps a list of supported distributions and their versions? I'll add it to my test framework.

This PR is no longer needed, because PR #1451 implements the same, but in a more compatible way.


Secure 20.2 playground cluster

This change is

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7ee5e33554a3ebff26ba742198323b8676b98860/

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7ee5e33554a3ebff26ba742198323b8676b98860/


Source maps

CST is more suitable for transpiling than AST. Kataw could replace tools like babel or recast, or hand-written tools using a parser (esprima, acorn, meriyah) and formatter (escodegen, astring). However, transpilers have to produce a source map, otherwise debugging would be impossible.
How about adding the source map support? ecodegen offers it by integrating source-map internally. astring expects a SourceMapGenerator with the interface as provided by source-map sent from the outside.

Pretty sure @KFlash is out of action at the moment. Not sure if he just doesn't have the bandwidth to work on the project right now, or if lack of community uptake of kataw killed his motivation. In any case, you likely won't get a response at the moment, but keep tabs on the project, as he might return sooner or later.

@axefrog I'm pretty sure he lost access to his GitHub acc after someone burned down his house, shoot at him and made him end up in jail before released on bail and all charges dropped.


[a11y] ExpansionTile missing expansion details and interaction behavior on web

Internal: b/326218346
Steps to reproduce
This is basically the same issue as https://github.com/flutter/flutter/issues/120650, but specific to web. I believe that issue was fixed but only for Android and iOS (not sure about other platforms either). When using a screen reader on an ExpansionTile element, it reads as "group" instead of "button" and gives no hint as to how to activate it. On Android and iOS, it reads something like "Double-tap to expand" or "Double-tap to collapse".
I'm able to reproduce the iissue with the code sample below just in dartpad, using VoiceOver on my Mac laptop. Run the sample and navigate to the ExpansionTile element using the screen reader.
Expected results
Screen reader should read something like "Hello World! button, double tap to expand"
Actual results
Screen reader reads "Hello World! group"
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: ExpansionTile(
            title: Text('Hello, World!'),
            children: [
              Text('Item 1'),
              Text('Item 2'),
              Text('Item 3'),
            ],
          ),
        ),
      ),
    );
  }
}

Screenshots or Video
None
Logs
N/A
Flutter Doctor output
N/A

I wasn't aware of https://github.com/flutter/flutter/pull/124281 that fixed the mobile side. I'm not sure that was a good fix for the issue.
On the web, there's a formal way to mark an expandable widget with expanded/collapsed state using the aria-expanded attribute. However, Flutter's fix is to pass a piece of text through the hint property. We should have a pair of SemanticsFlag.hasExpansionState and SemanticsFlag.isExpanded, similar to hasEnabledState/isEnabled. On the web we would translate it to aria-expanded. Similarly, on macOS we could use NSAccessibility.Attribute.expanded. Platforms that do not support this attribute directly would use the best fallback method. Unfortunately, we seem to have gone straight with the fallback method at the framework level, so the engine is unable to implement it through a formal a11y API.
As a short-term solution, we can pretend that the web doesn't have aria-expanded and implement the hint-based fallback.
Having said that, https://github.com/flutter/flutter/pull/124281 did partially address the issue on the web as well. The widget is interactive using the screen reader, and the accessibility announcement "Expanded"/"Collapsed" is voiced correctly. So I'm going to reduce the severity of the issue to P1.

The more pressing issue with this bug is that the widget is not being announced as interactable. That seems like a P0 issue to me.

Gotcha. To give it the formal "button" role the framework should set the isButton field on the semantics node. It looks like in https://github.com/flutter/flutter/pull/124281 it was decided that this widget should not be classified as a button (I don't see button: true set in the Semantics constructor invocation).
However, with https://github.com/flutter/engine/pull/51529, this is what I get from VoiceOver:

That seems reasonable, thanks!

I filed a follow-up issue here: https://github.com/flutter/flutter/issues/145434


Sanity checks for IPsec

We cover the following cases:

StrongSwan packages are not installed properly (that includes default
plugins): this check is enforced early on in start_ovs_ipsec; if it
fails, we will log a message and exit the container
Missing antrea-ipsec container in antrea-agent Pod: this is fairly
unlikely unless someone is messing around with YAML manifests (and
somehow forgets that container while still defining the secret for
the PSK...); we perform this check by verifying that
/var/run/openvswitch/ovs-monitor-ipsec.pid exists

Tested both error cases manually.
Fixes #1392

Codecov Report

Merging #1430 into master will decrease coverage by 2.53%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1430      +/-   ##
==========================================
- Coverage   67.80%   65.26%   -2.54%
==========================================
  Files         159      159
  Lines       12671    12688      +17
==========================================
- Hits         8591     8281     -310
- Misses       3178     3514     +336
+ Partials      902      893       -9

Flag
Coverage Δ

#integration-tests
47.84% <ø> (+<0.01%)
:arrow_up:

#kind-e2e-tests
49.44% <0.00%> (-5.98%)
:arrow_down:

#unit-tests
41.99% <0.00%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/agent.go
49.28% <0.00%> (-2.96%)
:arrow_down:

pkg/controller/networkpolicy/tier.go
0.00% <0.00%> (-90.00%)
:arrow_down:

pkg/k8s/name.go
33.33% <0.00%> (-66.67%)
:arrow_down:

pkg/agent/types/networkpolicy.go
23.52% <0.00%> (-64.71%)
:arrow_down:

pkg/agent/proxy/types/groupcounter.go
40.00% <0.00%> (-55.00%)
:arrow_down:

pkg/apiserver/handlers/webhook/validation_crd.go
0.00% <0.00%> (-52.64%)
:arrow_down:

pkg/controller/networkpolicy/validate.go
0.00% <0.00%> (-46.16%)
:arrow_down:

pkg/agent/proxy/proxier_linux.go
0.00% <0.00%> (-25.00%)
:arrow_down:

pkg/apis/controlplane/v1beta1/helper.go
46.15% <0.00%> (-23.08%)
:arrow_down:

pkg/apiserver/apiserver.go
73.49% <0.00%> (-10.85%)
:arrow_down:

... and 19 more

/test-all


CDA Requirements schema and schematron validation

Description
As NHS111 is CDA accreditated document, the CDA functionality requires that the CDA document is validated against content validation (particularly wrong OID, wrong clinical terminology). Most of the terminology is SNOMED CT, and some ID requires a specific OID.
For example.
ClinicalDocument->code@codeSystem must be "2.16.840.1.1138<IP_ADDRESS>.2.4.15"  (specs, DMS)
ClinicalDocument->recordTarget->patientRole->id, can have multiple id, but the the id@root should be either:
2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>
2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>
2.16.840.1.1138<IP_ADDRESS>.1  (spec DMS)
All of this check can be verified and validated, by running schema validation against :

NHS111 on the wire format
Transform to templated format, and validate again
Verify using Schematron validation

The validation can be found in the NPFIT-FNT-TO-TAR-0081.03 CDA Document Technical Requirements v2.0.pdf from NHS Interoperability Toolkit CDA Functional Requirements pack and can be dowloaded from TRUD. The stylesheet to do transformation may not be in the in DMS but can be retrieved from other MIM.
Component
NHS111 adapter
Version
0.1.0
Step to Reproduce

Put the valid a CDA in the payload
Change either:

ClinicalDocument->code@codeSystem to something else
ClinicalDocument->recordTarget->patientRole->id@root

Test Data
Any data
Preconditions
None
Environment
local environment
Severity
Low,
Priority
Not urgent
Expected Behavior
The response returns a SOAP Fault (as a consequence of sync mode of the adapter) with error text and/or diagnostic:

CDA 'on the wire' Schema validation failure. Detail: "{0}" => if generic cda validation
CDA Message Definition Schema validation failure. Detail: "{0}" => if templated cda validation
CDA Document content validation failure. Detail "{0}" => if schematron validation

The placeholder value is whatever returned from schema or Schematron validation.
The OID for this error is 2.16.840.1.1138<IP_ADDRESS>.<IP_ADDRESS>, and the error Code can be found from the below link.
See point to point error documentation, NPFIT-FNT-TO-TAR-0083 02 CDA Interoperability - Point to Point Error Codes v1.0 from NHS Interoperability Toolkit CDA Functional Requirements pack.

@Kusnaditjung find attached the requirement source document reference by Kainos and the list of test cases related to the requirements that was required by NHSD Assurance
111 PEM Kainos Assurance Cases.xlsx
ITK2.2-Supplier Certified Requirements Coverage v8.5.pdf

I think schema and templated schema validation is within MOD-VAL-01 (MUST), this said it must be configurable. I think the NHS 111 adapter only work for NHS 111 and not other CDA document type (discharge, out of hours, etc), so the configuration aspect can be skipped.
I think the additional content validation is within MOD-VAL-04 (SHOULD)

@Kusnaditjung schema validation is performed. However, OID checks you described above are not part of schema validation. These could be performed as part of  "additional content validation" - but there was no specific requirement to validate them, so it was never implemented.

@dawidskainos   yep it says SHOULD for content validation. For schema validation, there are two schema validation (one is for CDA, and one is templated CDA). For my other observation (in the slack chat) for version 0.10  apparently, the templated CDA has not been performed yet on that version, because there are some elements that should not be there (I check against the NHS 111 DMS in TRUD) for the custodian. Do I need to change the description to limit the issue to schema validation or create a new issue?

@Kusnaditjung can you please narrow down the description to reflect what you think is an issue now? We might need to check with NHS whether we want to fix it.

@Kusnaditjung  closing this please comment here with new issue raised

this is closed due to schematron validation is optional.
I have created a new issue for just the schema validation #131


Change parameterize to use a regex replacement like that in rails

Hi there!
When I came across this library, I was looking for something more along the lines of the Rails .parameterize which replaces more characters than just spaces with the given separator for URL/Filename readability. https://github.com/rails/rails/blob/92703a9ea5d8b96f30e0b706b801c9185ef14f0e/activesupport/lib/active_support/inflector/transliterate.rb#L90
This would be helpful for me, but if it's not what you are going for here, no worries! I'd be happy to change this to an optional behavior with another function parameter or something.
Thanks!

Hi, @zcotter.
I hope everything is well.
Are you still interested in implementing this?
Hi, @nurugger07.

I can make a PR if you want.

@styd this has been awhile so I'm closing the PR. Let me think on it but my initial thought is it's not needed. I could be convinced otherwise though


adding all supported runtimes

https://harness.atlassian.net/browse/CDS-52554
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/CDS-52554

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://hdh.pr.harness.io/pr-894


Data-layer pods pending during deployment to kubernetes

Hello,
Context
The data-layer statefulset has a podAntiAffinity rule, imposing the 1-1 relation between its pods and physical K8s nodes.
When the number of replicas of data-layer component surpasses the number of available physical nodes. The surplus replicas will then be stuck in the Pending state.
For example, we have two hospitable nodes in our cluster. When data-layer component creates three replicas, one always stays in Pending state.
Why is this rule applied? Should the podAffinityRule be loosened?
$ k get pods
NAME                      READY   STATUS             RESTARTS   AGE
dl-mfn-0                  1/1     Running            0          12m
dl-mfn-1                  0/1     Pending            0          3m8s
dl-mfn-2                  1/1     Running            0          12m

$ k describe pods dl-mfn-1
Name:           dl-mfn-1
Namespace:      knix-test
Priority:       0
Node:           <none>
Labels:         app=microfunctions-datalayer
                controller-revision-hash=dl-mfn-7f4cff64cf
                release=mfn
                statefulset.kubernetes.io/pod-name=dl-mfn-1
Annotations:    kubernetes.io/psp: restricted
                seccomp.security.alpha.kubernetes.io/pod: docker/default
Status:         Pending
IP:
IPs:            <none>
Controlled By:  StatefulSet/dl-mfn
Containers:
  datalayer:
    Image:      slfg92.rcs.de.alcatel-lucent.com:443/microfn/datalayer:latest
    Port:       4998/TCP
    Host Port:  0/TCP
    Limits:
      cpu:     500m
      memory:  500Mi
    Requests:
      cpu:      100m
      memory:   200Mi
    Readiness:  tcp-socket :4998 delay=0s timeout=30s period=10s #success=1 #failure=10
    Environment:
      RIAK_CONNECT:        rk-mfn.knix-test.svc.cluster.local:8087
      DATALAYER_BIND:      <IP_ADDRESS>:4998
      ALL_DATALAYER_BIND:  dl-mfn1-0.datalayer.knix-test.svc.cluster.local:4998,dl-mfn1-1.datalayer.knix-test.svc.cluster.local:4998,dl-mfn1-2.datalayer.knix-test.svc.cluster.  local:4998
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-vbh6g (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  default-token-vbh6g:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-vbh6g
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     <none>
Events:
  Type     Reason            Age        From               Message
  ----     ------            ----       ----               -------
  Warning  FailedScheduling  <unknown>  default-scheduler  0/4 nodes are available: 2 node(s) didn't match pod affinity/anti-affinity, 2 node(s) didn't satisfy existing pods   anti-affinity rules, 2 node(s) had taints that the pod didn't tolerate.
  Warning  FailedScheduling  <unknown>  default-scheduler  0/4 nodes are available: 2 node(s) didn't match pod affinity/anti-affinity, 2 node(s) didn't satisfy existing pods   anti-affinity rules, 2 node(s) had taints that the pod didn't tolerate.

k describe pods dl-mfn-1
Name:           dl-mfn-1
Namespace:      knix-test
Priority:       0
Node:           <none>
Labels:         app=microfunctions-datalayer
                controller-revision-hash=dl-mfn-7f4cff64cf
                release=mfn
                statefulset.kubernetes.io/pod-name=dl-mfn-1
Annotations:    kubernetes.io/psp: restricted
                seccomp.security.alpha.kubernetes.io/pod: docker/default
Status:         Pending
IP:
IPs:            <none>
Controlled By:  StatefulSet/dl-mfn
Containers:
  datalayer:
    Image:      slfg92.rcs.de.alcatel-lucent.com:443/microfn/datalayer:latest
    Port:       4998/TCP
    Host Port:  0/TCP
    Limits:
      cpu:     500m
      memory:  500Mi
    Requests:
      cpu:      100m
      memory:   200Mi
    Readiness:  tcp-socket :4998 delay=0s timeout=30s period=10s #success=1 #failure=10
    Environment:
      RIAK_CONNECT:        rk-mfn.knix-test.svc.cluster.local:8087
      DATALAYER_BIND:      <IP_ADDRESS>:4998
      ALL_DATALAYER_BIND:  dl-mfn1-0.datalayer.knix-test.svc.cluster.local:4998,dl-mfn1-1.datalayer.knix-test.svc.cluster.local:4998,dl-mfn1-2.datalayer.knix-test.svc.cluster.  local:4998
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-vbh6g (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  default-token-vbh6g:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-vbh6g
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     <none>
Events:
  Type     Reason            Age        From               Message
  ----     ------            ----       ----               -------
  Warning  FailedScheduling  <unknown>  default-scheduler  0/4 nodes are available: 2 node(s) didn't match pod affinity/anti-affinity, 2 node(s) didn't satisfy existing pods   anti-affinity rules, 2 node(s) had taints that the pod didn't tolerate.
  Warning  FailedScheduling  <unknown>  default-scheduler  0/4 nodes are available: 2 node(s) didn't match pod affinity/anti-affinity, 2 node(s) didn't satisfy existing pods   anti-affinity rules, 2 node(s) had taints that the pod didn't tolerate.

Expected behavior
Surplus replicas can still be created (with a warning if necessary).

knix requires at least 3 nodes for a riak cluster due to the requirement of achieving strong consistency in riak.

Yes, @ruichuan is right that we need 3 nodes for a riak cluster. However, I think the issue is still valid: 3 nodes of riak don't necessarily have to correspond to 3 physical nodes of the kubernetes cluster. Of course, loosening that podAntiAffinity role will also mean a looser fault-tolerance (i.e., if the physical node goes down, it will take down 2 of the riak nodes, potentially making it unstable).
@hpthai7: I'd think that this suggestion is very specific to the environment in question, though: you have 2 nodes in your cluster. My thought would be that you modify the relevant riak templates to remove or modify that rule for your own setup. As a general case, I doubt that we'd want to make it a general fix.
@manuelstein, @paarijaat: What do you think?

Putting 3 replicas onto 2 physical nodes doesn't make them more reliable.
As a general rule, it's recommended to have at least 3 nodes for the
cluster.  Though, for this specific setup, it'd be worthwhile to modify
that rule..
On Tue, Jun 16, 2020 at 1:59 PM Istemi Ekin Akkus<EMAIL_ADDRESS>wrote:

Yes, @ruichuan https://github.com/ruichuan is right that we need 3
nodes for a riak cluster. However, I think the issue is still valid: 3
nodes of riak don't necessarily have to correspond to 3 physical nodes of
the kubernetes cluster. Of course, loosening that podAntiAffinity role will
also mean a looser fault-tolerance (i.e., if the physical node goes down,
it will take down 2 of the riak nodes, potentially making it unstable).
@hpthai7 https://github.com/hpthai7: I'd think that this suggestion is
very specific to the environment in question, though: you have 2 nodes in
your cluster. My thought would be that you modify the relevant riak
templates to remove or modify that rule for your own setup. As a general
case, I doubt that we'd want to make it a general fix.
@manuelstein https://github.com/manuelstein, @paarijaat
https://github.com/paarijaat: What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/knix-microfunctions/knix/issues/41#issuecomment-644718071,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQSEDHTHB5475WBMWKJNI3RW5NBZANCNFSM4N7PGVKA
.

Ah, I just noticed this is not about riak nodes; this is about datalayer service nodes! (That said, it may not be necessary for them to have a statefulset.)
@hpthai7: Data layer service needs to be running on every physical node for locality purposes. As a result, there is no point of having two replicas running on a single host.
Even if the podAntiAffinity rule causes the replica to be in a pending state, that should not affect the platform. So I think your setup would still work without any changes.

OK for the data layer service then. I meant that was just a suggestion for the service itself.

Great, thanks for the suggestion!
I think we might revisit the 'statefulset' requirement for the datalayer service, but that is not relevant for this particular issue. I am closing this issue now. If the data layer service seems to have a problem related to the 3rd (pending) replica, please re-open.


hello world

could you make a simpler "hello world" version of this, with everything removed except for the bare minimum to get NW.js + Parcel to work together. There's just a lot of extra cruft (Pixi, React, RES, etc) that makes it difficult to see what is actually needed.
either as it's own repo or branch. I'd be happy to host/maintain it on nw-utils (repo of NW.js resources/boilerplates)

@TheJaredWilcurt  ho , i had not seen your message, I will see when I have a little time this month.
it was actually a base for all my projects, but i will try make a super simple version.

@TheJaredWilcurt
finish , plz see branch hellowWorld
https://github.com/djmisterjon/nw-Parcel-hmr-boilerplate/tree/helloWorld
hope is ok and clear for you.
i up the readme and remove some node stuff dependency.
Now is fully supported inside inline scripts from package.json.
npm i  install nwjs and dependency for parcel and nwjs (parcel have dependence because have some limited CLI argument)
npm run start-nw - dev you app
npm run build-nw - final productions
Make a test and tell me if all fine or have questions, also dont hesitate to tell me if you have better approach ! am always curious.

@djmisterjon I did some rewording and tweaks as a PR to try to simplify it for new people. But I think it's in really good shape!

@djmisterjon I did some rewording and tweaks as a PR to try to simplify it for new people. But I think it's in really good shape!
sure, nice, sorry and tanks for the english grammar !


Use newer gifsicle from backports repo

Browsing mediawiki's Phabricator I found that they upgraded gifsicle to 1.88 due to some issues with older versions. https://phabricator.wikimedia.org/T151455
I noticed on apsl/thumbor image newer gifsicle is available from backports repo, but was not installed, probably due to version priorities (?), so pinning works.

Thank you, this is merged in the new version 6.2.1 we are building.


BC 360 video player styling

Hi @rdunk — we're having a few issues regarding our 360 video player on Stories. I've logged a ticket with Brightcove Support but wanted to give you an overview here in case there was a crossover with your own work.
When we add the M+ Stories styling to our new '360' player inside of Brightcove, the player's interactive 360 video becomes disabled. It appears 'flat'.
We've had to use default Brightcove styling in order to display the video. This can be seen in our most recent blog post.
We had to embed the player into the blog using

 elements. We're unable to see our new 360 player in the drop-down menu within the CMS for the Brightcove Player content block:

Is there a way that we can select out 360 player from this drop-down menu? It's living in our account in Brightcove currently.
What is good about the default styling is that it has a special button which denotes 360 videos (see below). Is this something that we can include in our own styling (blue button)?

I'll keep you in the loop regarding what happens with Brightcove Support.

Under "Setup" in the admin panel, there is be a section called "Brightcove" which will allow you to update the list of players. I've just updated them, see below:

@rdunk — regarding the second note — can we implement a 360 player button for the 360 player? It seems important to denote.
Ref:

Should be easy enough to add if it's just a question of styling. I'll look into this today.

It looked like the problem with the 360 player not initialising was due to a configuration option for the language detection plugin being present without the actual plugin itself being included. I've added that in and it initialises correctly now.
I've updated the stories styling to now use a round (blue) button for all videos—both normal and 360. The 360 icon should now appear as you'd expect.
Should be able to use the CMS integration rather than embedding as iFrames now, let me know if you run into any problems.

@rdunk — I don't think our profiles allow us to update player settings from the admin panel. Is this the case?

@chrismplus do you mean your CMS admin permissions or profiles within the Brightcove platform?

@rdunk — within the ProcessWire

You should have all the available permissions, what settings are you trying to update?

Do the players automatically update via the ProcessWire interface? Or are they manually meant to be checked? If it’s that latter then my account doesn’t have the permissions to select players to update.

What error message are you seeing when you try to access the configuration page?

There’s no error message. I just can’t ‘tick’ to update any of the players. That’s why I wanted to check whether it was a dynamic process.

You can't manually select which players to update if that's the question, it just presents a list of players that need updating and then updates them when you confirm by clicking OK.

OK. Understood, that makes sense. Closing issue.


Tried model using lanchain_together

[ ] I checked the documentation and related resources and couldn't find an answer to my question.
Your Question
Getting Error: AttributeError: 'Generation' object has no attribute 'message'
Code Examples
from ragas.dataset_schema import SingleTurnSample
from ragas.metrics import NoiseSensitivity
from langchain_together import Together
import asyncio
from ragas.llms import LangchainLLMWrapper
from custom_embeddings import LocalEmbeddings

generator_llm = Together(
        model="mistralai/Mistral-7B-Instruct-v0.2",
        temperature=0.7,
        top_k=50,
        top_p=0.7,
        repetition_penalty=1,
    )
evaluator_llm = LangchainLLMWrapper(Together(
        model="mistralai/Mistral-7B-Instruct-v0.2"
    ))
evaluator_embedding = LocalEmbeddings(model_path="")

sample = SingleTurnSample(
    user_input="What is the Life Insurance Corporation of India (LIC) known for?",
    response="The Life Insurance Corporation of India (LIC) is the largest insurance company in India, known for its vast portfolio of investments. LIC contributes to the financial stability of the country.",
    reference="The Life Insurance Corporation of India (LIC) is the largest insurance company in India, established in 1956 through the nationalization of the insurance industry. It is known for managing a large portfolio of investments.",
    retrieved_contexts=[
        "The Life Insurance Corporation of India (LIC) was established in 1956 following the nationalization of the insurance industry in India.",
        "LIC is the largest insurance company in India, with a vast network of policyholders and huge investments.",
        "As the largest institutional investor in India, LIC manages substantial funds, contributing to the financial stability of the country.",
        "The Indian economy is one of the fastest-growing major economies in the world, thanks to sectors like finance, technology, manufacturing etc."
    ]
)

scorer = NoiseSensitivity(llm=evaluator_llm)

async def main():
    response = await scorer.single_turn_ascore(sample)
    return response
asyncio.run(main())

Additional context
Anything else you want to share with us?

hey @Eknathabhiram use ChatTogether - it only works with that - could you try it out and let me know if it works.
also can you run evaluate() with raise_exceptions=True? and share you're entire trace? I'll add a better error message so others don't get confused here 🙂

raise LLMDidNotFinishException()

ragas.exceptions.LLMDidNotFinishException: The LLM generation was not completed. Please increase try increasing the max_tokens and try again.
I have used chatTogther but still I am facing this issue.., Tried max tokens 2096 too,

can you increase it to the max possible - 8k preferably

I have the same problem when generating the dataset during summary extraction.
Applying [SummaryExtractor, HeadlinesExtractor]:   0%|          | 0/14 [00:00<?, ?it/s]
ERROR:ragas.testset.transforms.engine:unable to apply transformation: The LLM generation was not completed. Please increase try increasing the max_tokens and try again.
I checked the SummaryExtractor(LLMBasedExtractor) class and the given LLM (Google Gemini) has an output token of 8190, so I don't know how to fix it.

Also getting LLMDidNotFinishException(The LLM generation was not completed. Please increase try increasing the max_tokens and try again.) when running the code below.
ragas 0.2.7, Python 3.10.15
I tried using different models e.g. gemini-1.5-pro-001,gemini-1.5-pro-001,  gemini-1.5-flash and all of them returned the same result.
from langchain_google_vertexai import VertexAI
from langchain_google_vertexai import VertexAIEmbeddings
from ragas.embeddings import LangchainEmbeddingsWrapper
from ragas.llms import LangchainLLMWrapper
from ragas import evaluate
from ragas.metrics import LLMContextRecall, Faithfulness, FactualCorrectness, SemanticSimilarity
from ragas import EvaluationDataset
from datasets import load_dataset

dataset = load_dataset(
    "explodinggradients/amnesty_qa",
    "english_v3",
    trust_remote_code=True
)

eval_dataset = EvaluationDataset.from_hf_dataset(dataset["eval"])

project_id = 'MY_PROJECT'
location = 'europe-west2'
llm_model = 'gemini-1.5-pro-002'
embedding_model = 'text-embedding-004'

llm = VertexAI(model_name=llm_model)

embedding_function = VertexAIEmbeddings(
    model_name=embedding_model,
    project=project_id,
    location=location,
    request_parallelism=1,
)

evaluator_llm = LangchainLLMWrapper(llm)
evaluator_embeddings = LangchainEmbeddingsWrapper(embedding_function)

metrics = [
    LLMContextRecall(llm=evaluator_llm),
    FactualCorrectness(llm=evaluator_llm),
    Faithfulness(llm=evaluator_llm),
    SemanticSimilarity(embeddings=evaluator_embeddings)
]
results = evaluate(dataset=eval_dataset, metrics=metrics)

df = results.to_pandas()
df.head()

I was having the same issue using google's api. Seens like the #1728 works here with the googles api.
with the:
python is_finished_parser=gemini_is_finished_parser


abandoned/stale branches

Hi guys, this is not a bug/issue really but a call for attention.
I noticed that there are two branches that don't correspond to any Yocto release and seem to be fixes that were forgotten to be removed.

bcm2835-fix, Updated 11 months ago by agherzan [merged]
fix-rpi0wifi-kernel, Updated 7 months ago by agherzan [merged]

Perhaps the repo needs a vacuuming for these? :)
Cheers!

Vacuumed. Thanks @hhromic.

happy to help


Idea: Auto nock

Simply require nock and all should work.
Nock could save tests on the first run to the file system. Then replay wouldn't be done cause it was nocked.
A way to invalidate bad results would be necessary, so max a user would do is
nock.rewind();

Or you could generate code files
require('nock')

nock.record(function (js_file) {
  do whatever
}, 5000)

Sorry, didn't read, think this is a good idea!
No dia 2 de Dez de 2011, às 02:35, Nuno Job
<EMAIL_ADDRESS>escreveu:

Simply require nock and all should work.
Nock could save tests on the first run to the file system. Then replay wouldn't be done cause it was nocked.
A way to invalidate bad results would be necessary, so max a user would do is
nock.rewind();

Reply to this email directly or view it on GitHub:
https://github.com/pgte/nock/issues/14

@kelaban's PR with the said functionality has been merged into master.


Setting enviroment

I'm setting up this plugin to the backend with an already existing frontend in js, and that environment is not the same as the CRAFT_ENVIRONMENT.
Shouldn't the SENTRY_ENVIRONMENT be added and have presidence over the environment set in Craft? And/or be able to set this in the config.

Sure @espensgr, I will add an environment parameter and make a release soon.

@espensgr This should be fixed with the release 1.1.3.


Small window size cuts the chat window

when using small window , the window only show half of the window, making it almost impossible to see chat on small window

This problem isnt present anymore in the new beta.
Please see https://github.com/Aluxian/Facebook-Messenger-Desktop/issues/458


add RBAC for subjectaccessreviews, remove deprecated ao-logs container

Description
Check each of the following when appropriate to help reviewers verify work is complete.
Modifying an existing version

[ ] I modified operator permissions in the OLM CSV and operator.yml
[x] I modified the operator deployment in the OLM CSV and operator.yml
[x] I modified operand permissions in the OLM CSV and ansible role
[ ] I modified CRDS in the OLM CSV and ansible role

Adding a new release version

[ ] I created a new z release directory in deploy/olm-catalog/konveyor-operator
[ ] I updated channels in the konveyor-operator.package.yaml
[ ] I created a new release directory in deploy/non-olm
[ ] I created or updated the major.minor link in deploy/non-olm
[ ] I updated the spec.skips parameter in the CSV
[ ] I updated downstream-prep.sh to only update the latest CSV patch version in the channel

This is required for konveyor/mig-controller#559

I am hesitant to remove ao-logs right now as the ansible-operator we have to deal with downstream is fairly behind upstream.I realize sooner or later we're going to have to do this but I am hoping downstream will catch up to this change before we do it. Right now the logs in the downstream operator container are not as easy to read as the new mechanism in the upstream container.

Can you pull out the ao-logs change and make this one purely about the operator changes you need? I'm fine with an issue and a draft PR for the ao-logs change so we can do it when we're ready. I think I would actually pin upstream to an old release if they forced our hand and we were still waiting for dowsntream to catch up so we didn't have divergent code upstream and down.

@jmontleon uhm, without those changes I was not able to deploy non-admin branches. My mig-operator pod was crashlooping with something like ao-logs command not found. I can leave out the changes, and test with pinning to older upstream, so we don't crashloop

I think I would actually pin upstream to an old release if they forced our hand and we were still waiting for dowsntream to catch up so we didn't have divergent code upstream and down.

@jmontleon It looks like latest operator is already crashing with the "ao-logs no such file directory"  :
  Warning  Failed   130m  kubelet, ip-10-0-158-62.eu-west-1.compute.internal  Error: container create failed: time="2020-06-05T16:05:45Z" level=error msg="container_linux.go:349: starting container process caused \"exec: \\\"/usr/local/bin/ao-logs\\\": stat /usr/local/bin/ao-logs: no such file or directory\""
container_linux.go:349: starting container process caused "exec: \"/usr/local/bin/ao-logs\": stat /usr/local/bin/ao-logs: no such file or directory"
  Warning  Failed  130m  kubelet, ip-10-0-158-62.eu-west-1.compute.internal  Error: container create failed: time="2020-06-05T16:05:47Z" level=error msg="container_linux.go:349: starting container process caused \"exec: \\\"/usr/local/bin/ao-logs\\\": stat /usr/local/bin/ao-logs: no such file or directory\""


More useful parameters for e2e tests

For some reason BUILDKITE_BRANCH is a commit hash within Deployment-triggered pipelines, and the message is always "Deployment" 🤷

I wonder if this might help with this action from our last retro:
DMc/Exp devs
Work out why e2e tests didn't fail when they should have

@pollecuttn afraid this is unrelated to that - a bit unclearly named from me, actually about CI pipelines


First-run database migrations required

I just set up a cluster per the recommendations here and found that I needed to set up the sqlite database for a first run lest specific queries fail such as graphite/metrics/find?query=*:
# curl graphite/metrics/find\?query=\*

Graphite encountered an unexpected error while handling your request.

Please contact your site administrator if the problem persists.

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 149, in get_response
    response = self.process_exception_by_middleware(e, request)
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 147, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/opt/graphite/webapp/graphite/metrics/views.py", line 150, in find_view
    profile = getProfile(request)
  File "/opt/graphite/webapp/graphite/user_util.py", line 25, in getProfile
    return default_profile()
  File "/opt/graphite/webapp/graphite/user_util.py", line 41, in default_profile
    'password': '!'})
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/manager.py", line 122, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 465, in get_or_create
    return self.get(**lookup), False
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 381, in get
    num = len(clone)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 240, in __len__
    self._fetch_all()
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 1074, in _fetch_all
    self._result_cache = list(self.iterator())
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 52, in __iter__
    results = compiler.execute_sql()
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 848, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line 95, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/sqlite3/base.py", line 323, in execute
    return Database.Cursor.execute(self, query, params)
OperationalError: no such table: auth_user

Luckily, it wasn't too difficult to figure out how to set up the schema for a first run:
PYTHONPATH=/opt/graphite/webapp django-admin.py migrate --settings=graphite.settings --run-syncdb

I'm going to propose that this be done immediately following the creation of the database file or inside a file missing or zero length test in the entry point.

Thanks for reporting this,
your issue should be fixed by https://github.com/nanit/kubernetes-graphite-cluster/commit/0a9c2d1a4dd2bd40c586e6bfaf54ff1597cd6d8e
Please Re-Open if you still experience problems


Bug:  options for conncet to Oracle database as SYSDBA or SYSOPER

Chat2DB Version
2.0.1
Describe the bug
连接Oracle的时候，如果用sys用户连接，没有以 SYSDBA 或者 SYSOPER 的选项。
023-07-07 03:15:54.453  INFO 1 --- [io-10824-exec-1] a.chat2db.server.start.log.EasyLogSink  .67 : e1bf1a66-d577-4594-8443-84e9ec407a0b | http : POST|/api/connection/datasource/pre_connect|643|{"ssh":{"use":"false","host":"","port":"","userName":"","localPort":"","password":""},"alias":"orcl@<IP_ADDRESS>","host":"<IP_ADDRESS>","port":"1521","sid":"orcl","driver":"thin","authentication":1,"user":"sys","password":"sys","url":"jdbc:oracle:thin:@<IP_ADDRESS>:1521:orcl","extendInfo":[],"ConnectionEnvType":"DAILY","type":"ORACLE"}|{"success":false,"errorCode":"ORA-28009: connection as SYS should be as SYSDBA or SYSOPER\n","errorMessage":null,"traceId":null}

marked in #407


Updating Contributing.md:Fixing rendering issue

- What I did
Removed all the link of images which were missing and not rendering.
- How I did it
- How to verify it
- Description for the changelog

FIXES #166

Please Review @yahu1031

Although this works good for a quick fix, but bringing the images over from https://github.com/atsign-foundation/at_app/tree/trunk/images, and making the code work would be the correct thing to do.

Closing this PR
Reference #184

please try making changes in one PR. :)


Question: add boost json to oss-fuzz?

There is already fuzzing inplace using github actions. That is good, and I do not want to change that. But I would like to get boost json on to oss-fuzz. The reason is that the oss-fuzz machinery is much more sophisticated. One gets nice fuzz coverage reports, for instance so it is easier to understand what needs to be fuzzed.
I made an initial attempt over here: https://github.com/google/oss-fuzz/compare/master...pauldreik:boost_json?expand=1
I used the boost variant instead of standalone since I read somewhere the boost json standalone version might go away.
First, I want to know if you are ok with going forward with this. If not, I will just stop working on this.
In case you are ok with this, I would need some advice regarding building and which branch to use
Branch
I used the the boost-1.76 tag in the super repo. The point is to follow the development of primarily json but also boost in case boost json needs changes from the rest of boost. I do not know if there is a branch (like "develop" or so) in the super repo that could be used for this?
The branch for boost json should be develop, I assume. For now I just used the tag in the super repo.
Build system
The existing fuzzer uses cmake but the oss-fuzz version just invokes CXX directly. I made a jam file for compiling the rest of boost (see build.sh in the linked pull request), I would be happy to get a pointer to how to build the fuzzers using that jam file.

What are plans regarding this? Are you planning to support it in the future?
Boost does have develop and master branches. master is supposed to be rather stable, and might not get updated very often (potentially, only before a Boost release).
The existing fuzzer doesn't actually use CMake (or any proper build system), it uses a POSIX shell script fuzzing/fuzz.sh

@pauldreik wrote the fuzzer FYI.. lol

1. What are plans regarding this?

The plan is to get it going and then it will file bugs when needed. I have worked with getting simdjson and fmt into oss-fuzz and those projects just keep on fuzzing without much work at all.

Are you planning to support it in the future?

Yes. I don't expect it to be much work because boost json is now released and won't change it's api as fast as when I wrote the fuzzers. Also, thanks to the CI fuzzer job, the fuzzers won't stop working silently.

2. Boost does have develop and master branches. master is supposed to be rather stable, and might not get updated very often (potentially, only before a Boost release).

I guess the master branch is suitable then.

3. The existing fuzzer doesn't actually use CMake (or any proper build system), it uses a POSIX shell script fuzzing/fuzz.sh. And currently uses standalone mode, BTW.

 I wrote that from memory without checking :-)  Glad there's git to prove I did it...
One thing I forgot to mention is that getting it on to oss-fuzz also requires the oss-fuzz project to accept it. There is a boost job already (which I improved a bit) but it uses only header only libraries. I don't think it makes sense to have all of boost in the same job. But the first step is to get an OK or stop from the boost json team.

I say, the more the merrier 👍🏻

I see no reason to object to someone doing more testing for this library. And in fact, more thorough fuzzing was the main recommendation in Bishop Fox's assessment.

Good, I will update my oss-fuzz branch. I put myself as the primary contact but maybe it is better to put one of you as primary. Which email addresses would you like me to use? They will be put in the yaml file, so expect them to be subject to spam.

You can use my email, Google has a good spam filter and my email address is already public. Thanks!

<EMAIL_ADDRESS>would be OK, it's on the Internet anyway.

@pauldreik this has been resolved successfully, right?

Yes, it was accepted and it works (first bug found and fixed), so this
issue can be closed now!

I just looked at the statistics from oss fuzz. Seems like it has used something in the order of 60 cores to fuzz boost json. I do not know if they give new projects a boost in compute power, but that is just an awesome amount of fuzzing power. Let's wait for a few days and see if anything new pops up, and if not, I will test enabling the memory sanitizer for oss fuzz as well.


question about feat_encoder

The code extracts the features of img1 and img2 respectively, while in RAFT, the features of two images are extracted at the same time by concat, is there a difference in effect?
Code snippets (RAFT) :
fmap1, fmap2 = self.fnet([image1, image2])
Code snippets (FlowFormer) :
feat_s = self.feat_encoder(img1)
feat_t = self.feat_encoder(img2)
It seems that both are weight-sharing, but will running the extractor twice be slower?

Thanks for such a detailed code check. The image pair in RAFT are concatenated along the batch dimension, which makes the two inferences combined in a single inference. After testing, we find that inference with concatenation costs around 0.0052s while separated inference costs around 0.0085s :dizzy_face:. However, the computation is exactly the same and the time reduction is minor compared to the whole inference time. Thanks for pointing that out. We will update the code.

Thanks for the prompt and patient response!

Thanks for such a detailed code check. The image pair in RAFT are concatenated along the batch dimension, which makes the two inferences combined in a single inference. After testing, we find that inference with concatenation costs around 0.0052s while separated inference costs around 0.0085s 😵. However, the computation is exactly the same and the time reduction is minor compared to the whole inference time. Thanks for pointing that out. We will update the code.

Thanks for the prompt and patient response!

The code has been updated~


[Feature request]: Backend API for resource predictions

Contact details
No response
Is your feature request related to a problem? Please describe
Enable predicting the scaling laws of the data pipeline using the backend API
Describe the solution you'd like
In the backend controller API, create an endpoint that takes dryRuns as input and computes the scaling parameters of input metrics. The input metrics are functions f, of the size of the input data x.
The functions f(x) are assumed to be linear (a + xb) or a power law function (ax**b)
For each step in the workflow/data pipeline, the scaling parameters are computed for each metric.
The returned data should contain something like:
output_data = {
{
step_id: string,
step_name: string,
x_data: number[],
cpu: {
y_data: number[]
scaling_law: string,
scaling_parameters: [number, number]
scaling_law_r2: number
},
...
}
where x_data is the input file size of the dryRuns and here cpu is metric data for cpu usage. The scaling law can be "power" or "linear", r2 is the coefficient of determination and the scaling parameters are coeficcients a, b for the scaling law:
linear scaling law: a  + bx
power scaling law: ax**b
Describe alternatives you've considered
No response
Additional context
No response

done.
compute metrics
predict scaling


How files and layer work

We need some clear instructions on how QGIS files and layers work. It would be good to have some basic diagram of how files related to projects are organised and listed in the same folder and relative to the QGIS project on the PC. And then, when user wants to add a new layer, how they should do it (I know there is a section on it in the docs, but due to search and indexing, I never manage to find it).
The section can go here: https://merginmaps.com/docs/layer/best-practice/

OK, I see this section: https://merginmaps.com/docs/manage/project/#adding-a-layer-to-the-project which explains it well. Maybe adding a new sections for troubleshooting: Why I cannot see my layer in the app?...


Add a loading screen to the "add device" screen.

When adding a new device, there is a screen on which it appears to think for a second that Bluetooth is off, even if it is turned on.
So there should either be a loading screen, or it should be inverted so that it first opens the normal screen and then the Bluetooth off screen.

Fixed another way


Loop over root element

I have a vector of structures, which I want to format. Unfortunately I can't access the root element to loop over it: {{ for item in ??? }} {item.field} {{ endfor }}. Is it possible? What template should I write?

Hey, thanks for the suggestion.
Y'know, it never occurred to me that anyone would want that (I'm still kind of surprised when I find out anyone but Criterion.rs is using TinyTemplate). I don't think that's possible right now, except to wrap your vector in its own struct so that you can give it a name.
Thing is, I'm not really sure if I want to support this. The obvious way to support it is to add a special @root keyword, but since the workaround is easy, it's not obvious that it's worth the tradeoff. I'll have to think about that.

Don't be surprised, TinyTemplate is a great tool for formatting complex data!
The @root would be perfect. Another solution would be to allow paths to start from a . to explicitly indicate that they are absolute. That was one of the first things I felt was right to try: {{ for item in . }} ....
That's a pity, but I will understand. The wrapper is exactly what I ended up doing, but it's an ugly workaround.

Would be cool to support that! tinytemplate is otherwise really great!

Alright, seems this is more desired than I thought. It wasn't too hard to add support for. I've added the @root keyword in 1.0.4; if the root context value is the right type you can print it, branch on it, or iterate over it.


chore(main): release 1.0.7

:robot: I have created a release beep boop
1.0.7 (2024-06-14)
Bug Fixes

deps: update dependency matterbridge-home-assistant to v0.5.2 (#47) (36b45f9)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.0.7
:sunflower:


Add ReturnCountRule.

Fixes #249

Is this a rule we want to enable by default?

We could disable it by default. Open to that.


[SPARK-31785][SQL][FOLLOWUP] Rename withAllParquetReaders to withAllNativeParquetReaders

What changes were proposed in this pull request?
This PR aims to rename withAllParquetReaders to withAllNativeParquetReaders
Why are the changes needed?
Apache Spark have non-native Parquet reader too. In SQL module, we only test native readers.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Exists test.

ping @dongjoon-hyun cc @cloud-fan @gengliangwang @MaxGekk

Apache Spark have non-native Parquet reader too

Which reader do you mean? vectorized reader?

Test build #146019 has started for PR 34840 at commit bce74ec.

Apache Spark have non-native Parquet reader too

Which reader do you mean? vectorized reader?

I just references https://github.com/apache/spark/pull/34733#issue-1065664481. Maybe @dongjoon-hyun could give our a better description.

I think he meant Hive ORC reader VS Spark ORC reader but that's not the case for Parquet.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50495/

I think he meant Hive ORC reader VS Spark ORC reader but that's not the case for Parquet.

I'm sorry. Could you explain in more detail?

There are two ORC reader implementation. one uses Hive's library, and one uses plain ORC's library. See also spark.sql.orc.impl configuration.

There are two ORC reader implementation. one uses Hive's library, and one uses plain ORC's library. See also spark.sql.orc.impl configuration.

Thank you for your explanation.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50495/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50495/

Test build #146019 has finished for PR 34840 at commit bce74ec.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146019/


CVE-2023-1370 on dependency

Describe the bug
Via dependency numbus-jose-jwt-9.22 the below dependency is included, this have a CVE-2023-1370
net.minidev_json-smart version 2.4.8
Path: /home/app.jar/nimbus-jose-jwt-9.22.jar
Json-smart is a performance focused, JSON processor lib. When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code parses an array or an object respectively. It was discovered that the code does not have any limit to the nesting of such arrays or objects. Since the parsing of nested arrays and objects is done recursively, nesting too many of them can cause a stack exhaustion (stack overflow) and crash the software.

Just to add, have also encountered this with

com.azure
azure-identity
1.8.1

Thank you for filing this @ukv001, usage of the impacted versions of json-smart appear to be, as you've mentioned, a shaded usage in nimbus-jose-jwt which is resolved to upgrading to a version of 9.23 or later as that is when shaded json-smart was replaced with shaded gson and in msal4j using json-smart as a dependency which should be resolved in their next release as the latest released version is still using 2.4.8 but is upgraded to 2.4.10 in source.

FYI @billwert, @g2vinay to update the version of msal4j in azure-identity once a version is available

@alzimmermsft, do you know when the next release of com.azure:azure-identity will occur that includes the fix for this issue?  We're waiting for this fix to be published.  Thanks!

@halprin It will ship toward the end of this week (or early next at the latest.)


Context menu item not highlighted

When I press Enter to select one of the available options from the context menu, I can't see the highlighted option at all (see the first image below). I think that maybe it is due to my terminal colors, because it works well on a simple tty.
However, many other curses-based tools I use have not this problem. The second image, for example, is taken from wicd-curses.
Is it possible to change the highlighted item style in some way?

Pulsemixer uses bold text to highlight selected item in context menu. Likely your terminal emulator doesn't allow bold.
5b78f57 commit adds an arrow to better indicate selected item. Since pulsemixer is already heavy with color I'm somewhat reluctant to do background highlighting like wicd does. So, a simple arrow instead.

Thanks a lot, I'll wait for the updated package on the AUR. In the meantime, I've enabled the bold fonts in urxvt.


Make 'createElement' more discoverable in the documentation

Greetings,
I recently had a scenario in which this:
var vm = new Vue({
    el: document.getElementById("app"),
    render: createElement =>
        createElement(app, {
            props: {
                viewMode: FinancialPlanViewMode.Advisor
            }
        })
});

was the solution.
There seems to be little documentation of this 'createElement' bit in 'render' when creating a new Vue instance. I think I eventually found some sample around this on StackOverflow on somewhere, but I would have loved to find something here.
Any thoughts on what would make the most sense to make this more discoverable? Namely, which page?

Well, if you know that you need to write a render, you would probably check the docs on render function, and the first example of render function contains the createElement argument.
What was your path to discover the render and createElement?

I guess the confusion, on my part, was assuming 'render' was somehow
different between a component and a full vue instantiation.
On Tue, Mar 14, 2017 at 10:56 AM, Denis Karabaza<EMAIL_ADDRESS>wrote:

Well, if you know that you need to write a render, you would probably
check the docs on render function
https://vuejs.org/v2/guide/render-function.html, and the first example
of render function contains the createElement argument.
What was your path to discover the render and createElement?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vuejs.org/issues/824#issuecomment-286446920,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3Vvk23hbV0h8hn-Vt2xYpcvNBURE6Bks5rlqqRgaJpZM4Mco_O
.

The page on the template syntax now links to render function near the beginning and I think it's made more clear that wherever a template can be used, a render function could be used instead, so closing this for now.


Trouble installing the ARChon Runtime Extension for Google Chrome

I want to install the ARChon extension. I followed the guidelines saying "go to 'chrome://extensions' and turn on developer mode, and load unpacked". When I do that, it successfully pops up like all the other extensions, but it has a 'reload' button, and sometimes two warnings (that I just ignored). For it to work I thought I should click the button, but it just magically disappears. However if I don't click the button, the extension is just not working.
This is what Google Chrome on Mac OS Catalina shows:
Version: 38.4410.120.43
Size: 273 MB
ID: mfaihdlpglflfgpfjcifdjdjcckigekc
Loaded from: ~/Downloads/vladikoff-archon-6ad1d59d5f1a

Could anyone please explain how this works, and / or tell me how to fix it?
Thanks in advance
This is a screenshot of how it looks:

[need-help]

Don't click it 😎

Don't click it 😎

If I don't click it, it just doesn't work!

What you mean by doesn't work. I too have some issues

What you mean by doesn't work. I too have some issues

The extension just isn't there, it disappears.

did you find a solution ? i'm a bit late but i get the same issue

@daygaa No, I found no solution 😢
I ended up using BlueStacks instead


Fixed all the scripts in package.json

As discussed, I have fixed all the scripts in the package.json file of quantum-jobs. I have used appconfiguration package as reference.
Added a simple test case as a starting point.
@ramya-rao-a Please review and approve.

Thanks @sarangan12
@HarshaNalluru Can you review this please?

Thanks @sarangan12
@HarshaNalluru Can you review this please?

I have used appconfiguration package as reference.

@HarshaNalluru A lot of your comments may apply to App Config as well. Can you log an issue to review the npm scripts across all our track 2 packages and the template package?

I have used appconfiguration package as reference.

@HarshaNalluru A lot of your comments may apply to App Config as well. Can you log an issue to review the npm scripts across all our track 2 packages and the template package?


Remove TechPowerUp.NVCleanstall version 1.15.1

URL is 404
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

Why remove it entirely from winget and not just updating the URL?


org.scala-sbt organization

I noticed that sbt-autoversion uses org.scala-sbt organization.
We want to reserve the use of org.scala-sbt for sbt uses, so please use com.github.sbt or some other domain name please.
We are working on dependency resolution optimization, org.scala-sbt artifacts might not be included into the resolution (since sbt itself is already resolved by the launcher once), which affects this plugin.

Will tackle it ASAP, thanks for the notice !


AtlasTeam is created but modifications don't reconcile

What did you do to encounter the bug?
Create an AtlasTeam:
apiVersion: atlas.mongodb.com/v1
kind: AtlasTeam
metadata:
  name: team-name
spec:
  name: "Team name"
  usernames:
    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>
The team is created. However, if you add another user to the team:
apiVersion: atlas.mongodb.com/v1
kind: AtlasTeam
metadata:
  name: team-name
spec:
  name: "Team name"
  usernames:
    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>
Then reconciling fails. Describing AtlasTeam you get the following status:
Status:
  Conditions:
    Last Transition Time:  2023-01-05T13:52:03Z
    Message:               context canceled
    Reason:                TeamUsersNotReady
    Status:                False
    Type:                  Ready
  Id:                      63b33c930b3b9d3a0ce440d1
  Observed Generation:     3
Events:
  Type     Reason             Age        From          Message
  ----     ------             ----       ----          -------
  Normal   Ready              <invalid>  AtlasProject
  Warning  TeamUsersNotReady  <invalid>  AtlasProject  context canceled

And in the operator logs you see the following:
{"level":"WARN","time":"2023-01-05T13:52:03.379Z","msg":"failed to retrieve users to add to the team 63b33c930b3b9d3a0ce440d1","atlasteam":"xxx/xxx"}

What did you expect?
The team should have a new member.
What happened instead?
The team in Atlas wasn't modified.
Screenshots
If applicable, add screenshots to help explain your problem.
Operator Information

1.5.1

Kubernetes Cluster Information

GKE
1.24.7-gke.900

Additional context
I initially tried with user<EMAIL_ADDRESS>not being part of the users in the organization, to see if it would invite them as well. It didn't work. I tried again manually adding the user as an Organization Member, waiting for email to be verified, and then adding them to the team through the operator. Failed as well.
If possible, please include:

kubectl describe output
yaml definitions for your objects
log files for the operator and database pods

I appear to have to the same problem:
Also have the same log lines in my operator
{"level":"INFO","time":"2023-01-06T11:07:13.311Z","msg":"-> Starting AtlasTeam reconciliation","atlasteam":"***","spec":{"name":"***","usernames":[***]}}
{"level":"WARN","time":"2023-01-06T11:07:13.711Z","msg":"failed to retrieve users to add to the team ***","atlasteam":"***"}

I'm running on AKS and using the latest operator (1.5.1).
I also removed users that didn't accept the invite to create a login, but that doesn't help as well.

Awesome, thanks for the workaroud and the clarification about the users being in the org.


How to display the date of seven days a week instead of the whole month?

How to set the display of data for only one week？

Simple, just use the .week enum for the calendar scope: self.calendar.scope = .week

Simple, just use the .week enum for the calendar scope: self.calendar.scope = .week


There are 5 references to host.Run() instead of host.RunAsync()

We should be using RunAsync() otherwise Run() just triggers the async wrapper if I remember correctly right?
public static void Run(this IHost host)
{
    host.RunAsync().GetAwaiter().GetResult();
}

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

ID: 6ad5f362-cbfb-0621-4389-6378f50359e4
Version Independent ID: ebf1a8f3-ab9d-d295-e3a4-a982ed9df1e9
Content: Guide for running C# Azure Functions in an isolated worker process
Content Source: articles/azure-functions/dotnet-isolated-process-guide.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@Tyler-V
Thanks for your feedback! We will investigate and update as appropriate.


Optionally ignore unmatched arguments

When developing in Visual Studio, I often write a number of command line arguments that I'm testing or use frequently into the project Properties / Debug / Start Options, e.g.
/file:C:\Some\Long\Path /pre:12345678
When I don't want a particular option for a particular execution, I just change the parameter name
/XXXfile:C:\Some\Long\Path /pre:12345678
Unfortunately, and apparently by design, any unrecognized argument causes PowerArgs to throw an Exception.
It would be nice there were a class level attribute to control this behavior.  That would allow for e.g.
#if DEBUG
[ArgIgnoreUnmatchedArguments]
#endif
public class MyArgs

:+1:

How do you expect to be able to consume these unmatched arguments in your code?

Also, you can already do something like this:
#if RELEASE
[ArgIgnore]
#endif
public string FooArgument{get;set;}

On Thu, Oct 8, 2015 at 11:28 AM, Adam Abdelhamed<EMAIL_ADDRESS>wrote:

How do you expect to be able to consume these unmatched arguments in your
code?

I don't want to consume them at all, that is the point.
I want to be able to specify an argument that is completely ignored by the
argument parser.
That is the opposite of [ArgIgnore].
The reason is that I often find myself typing in lengthy arguments while in
the develop/test cycle.  Visual Studio has a properties box where I can
enter my arguments.  Rather than delete a lengthy argument only to type it
in again next time I need it, I just change the name of the argument to
something meaningless (e.g. by prepending xxx).  Prior to adopting
PowerArgs that worked fine.  My prevous argument parser would just ignore
arguments that it did not understand.
I don't see any valid purpose for this for released code, but it would be
pretty handy during development.
Eric

I just checked this in directly into the master branch.  I'll publish it sometime this weekend.

Thank you, this change is very helpful.

You're welcome


Rename diagnose firewall commands

Now that we have vxlan as one of the cable driver, it could lead
to confusion between verifying firewall config within the local
cluster vs inter-cluster traffic. This PR deprecates and replaces
the following commands to make it more readable.
vxlan  -> intra-cluster
tunnel -> inter-cluster
Signed-Off-by: Sridhar Gaddam<EMAIL_ADDRESS>

Thanks for addressing this so quickly, @sridhargaddam. Please also update the docs accordingly: https://submariner.io/operations/deployment/subctl/#diagnose

Thanks for addressing this so quickly, @sridhargaddam. Please also update the docs accordingly: https://submariner.io/operations/deployment/subctl/#diagnose

Done, the following PR handles the changes - https://github.com/submariner-io/submariner-website/pull/577


Results and Presentation

[x] Upload the presentation in pdf format
[ ] Edit README

Added presentation -> fe199d3d3d87e66511b3d19e1ebb8656e29de022


Unexpected capture of EngineLayer when capturing int value

observed behavior
The following code executes fine:
  @override
  void initState() {
    super.initState();
    _getAgent().then((agent) async {
      final String? decoded =
          await agent.query((state) => state.decodedMessages[0]);
      if (mounted) {
        setState(() {
          _text = decoded;
        });
      }
    });
  }

If I change the integer literal to index, the app errors:
  @override
  void initState() {
    super.initState();
    final int index = widget.index;
    _getAgent().then((agent) async {
      final String? decoded =
          await agent.query((state) => state.decodedMessages[index]);
      if (mounted) {
        setState(() {
          _text = decoded;
        });
      }
    });
  }

error log
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Illegal argument in isolate message: (object extends NativeWrapper - Library:'dart:ui' Class: EngineLayer)
#0      _SendPort._sendInternal (dart:isolate-patch/isolate_patch.dart:249:43)
#1      _SendPort.send (dart:isolate-patch/isolate_patch.dart:230:5)
#2      Agent.query (package:isolate_agents/isolate_agents.dart:104:15)
#3      _MessageState.initState.<anonymous closure> (package:romeo_juliet/main.dart:144:23)
<asynchronous suspension>

expected behavior
Since I am copying the widget.index value to its own integer, I expect that to get captured, not the widget and thus no error about capturing and sending ui elements to an Isolate.

Duplicate of #36983

tldr: Dart VM creates contexts from scopes, rather than creating a context pre-closure. This makes closures that share the same scope overcapture things, e.g.
void f() {
  var x, y;
  foo() => x;
  bar() => y;
}
// Both [foo] and [bar] capture x & y.

I moved the crux of this issue over to that one since I think this is a novel problem for a known issue.


Eloquent-stored json wont Attribute-cast to collection (Query builder-stored will cast normally)

Laravel Version: 5.5.21, tested on homestead 4.0.0, 3.1.0 and Heroku
PHP Version: 7.1.9
Database Driver & Version: MySql 5.7.19 (Homestead 3.1.0 and 4.0.0) and PostgreSQL 9.6.4 (Heroku)

Description:
with previous laravel 5.5.16 version, i was storing json_encoded() fields to database (also json-datatyped fields) and retrieving them casted to collection by a model attribute casting.
i did composer update and got to laravel version 5.5.21, now, data is beeing stored differently and model's json-to-collection castings are not working.
Steps To Reproduce:
Model
<?php
namespace App;
use Illuminate\Database\Eloquent\Model;

class Summon extends Model
{
	protected $guarded = [];
	protected $casts = [
		'names'   => 'collection',
	];
}

using eloquent, i'm storing this array/json
[
    "Siren",
    "塞壬",
    "세이렌",
    "Sirène",
    "Sirene",
    "Sirena"
 ]

with this code:
($summon['names'] contains the previous array)
$newSummon = new Summon();
$newSummon->names = json_encode($summon['names']);
$newSummon->save();

previously, with version 5.5.16 it was stored like this

and whenever i retrieved it, i got the data casted to collection:

now, with version 5.5.22, it's beeing stored like this

and i get a string.

i'm retrieving it with this code
$summon = Summon::findOrFail($id);
return Response()->json($summon, Response::HTTP_OK);

this was the last test i did before posting this issue:
i stored the  value using Query Builder (green box)
and got it working as before
The commented code within the red box used to work in 5.5.16 until i did composer update to 5.5.21

you may notice a bit more code in this last screenshot, i just shortened the code here to be more readable, this issue happens with every json field (like skill, color, entries) stored using eloquent and work as desired storing the using Query Builder.
I'm relatively new to laravel, hope i'm not skipping something 👍
Thank you!

i'm closing this, i believe the issue is caused by enconding a already encoded json


only works on initial web view.

Hi,
I'm building a tool that allows editing a document in a webview with a native toolbar. Everything works fine the first time around, but if I dismiss a view controller, then reload it again (creating a new post), none of the events work anymore.
I have this
override func viewDidLoad() {
  self.wv!.frame = CGRectMake(0, 65, self.view.bounds.width, self.view.bounds.height - 50)
  self.wv = UIWebView()
  self.view.addSubview(self.wv!)

  Caravel.get("editor", webView: self.wv!).whenReady() { bus in
    bus.register("highlight") { name, data in
      // all is good here!
    }
  }
}

editor.on('highlight', function () {
  Caravel.get("editor").post('highlight')
})

As mentioned, it all works great until I attempt to load it the second time around. Any ideas?

Hi Dustin!
Thank you for your interest in Caravel!
The issue you pointed out should have been fixed in the latest release. Please let us know how it goes :)

i'll give it a try. btw I got it to eventually work — I think the main issue is that webView's cache all the resources that get requested, thus I needed to reload my caravel.min.js file...
So in my webpage I did the following:
head
  script(src='/js/caravel.min.js?no_cache=' + Math.random())
body
  ....

Actually, I found out the origin of the issue was in Swift part. When reloading a controller, the UIWebView instance may change. So, if that happens, the bus should watch the new instance instead of the former one.

gotcha. perhaps i'll revert a few of my changes then :)


chore: update OCI image bases

Feature or Problem

This will be automated in #3663
Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Superseeded by automated update in #3664


HJST Usage

Can this code be used with spectrographs other than NRES/HARPS?  More specifically, ones that have separate calibration lamp and science images?  And possibly different table formats?

Dear Kenneth,
Absolutely yes! There are some dials to turn when calibrating a new
spectrograph, but so long as the signal to noise is high it usually isnt
too much of a chore.
xwavecal is actually designed for separate cal/science frames. So yes your
use case is the preferred use case.
If you already have an extracted 1d spectrum: so flux vs pixel, for all the
orders, its pretty easy to run xwavecal on that.
What is the current format of your spectra?
On Mon, Mar 13, 2023 at 4:12 PM kennethcarrell @.***>
wrote:

Can this code be used with spectrographs other than NRES/HARPS? More
specifically, ones that have separate calibration lamp and science images?
And possibly different table formats?
—
Reply to this email directly, view it on GitHub
https://github.com/gmbrandt/xwavecal/issues/26, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGORGH33AQBKFRG75EMP5LW36SVFANCNFSM6AAAAAAVZWUMMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have 1-D spectra that are output from the PyReduce package.  I’ve tried to use the wavelength calibration in that code, but it has not worked after repeated attempts and code modifications by that author.
The files are fits format (‘.ech’ ending) with a binary table as the second HDU.

Ok cool.
Critical for xwavecal are the presence of overlaps (duplicated lines)
between one order and the next. These overlaps are cut off or too small on
some spectrographs. Could you send an example wavelength calibration
spectrum?
On Mon, Mar 13, 2023 at 8:49 PM kennethcarrell @.***>
wrote:

I have 1-D spectra that are output from the PyReduce package. I’ve tried
to use the wavelength calibration in that code, but it has not worked after
repeated attempts and code modifications by that author.
The files are fits format (‘.ech’ ending) with a binary table as the
second HDU.
—
Reply to this email directly, view it on GitHub
https://github.com/gmbrandt/xwavecal/issues/26#issuecomment-1467308714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGORGEUM2TMO4KXEGFGVDTW37TGDANCNFSM6AAAAAAVZWUMMY
.
You are receiving this because you commented.Message ID:
@.***>

n10001.thar.ech.zip
This code will allow you to plot the 6th order (with numpy as np and matplotlib.pyplot as plt):

fin = fits.open("n10001.thar.ech")
data,header = fin[1].data['SPEC'][0], fin[0].header
spec = np.flip(data,axis=0)
x = np.arange(0,len(spec[0]))
plt.plot(x,spec[5])
plt.show()

The approximate wavelength range is ~3500 - 10,000 angstroms

awesome.
By the way, I am not in science full time anymore -- so there will be some
delay until I get to looking at this.
On Mon, Mar 13, 2023 at 9:17 PM kennethcarrell @.***>
wrote:

n10001.thar.ech.zip
https://github.com/gmbrandt/xwavecal/files/10964034/n10001.thar.ech.zip
This code will allow you to plot the 6th order (with numpy as np and
matplotlib.pyplot as plt):
fin = fits.open("n10001.thar.ech")
data,header = fin[1].data['SPEC'][0], fin[0].header
spec = np.flip(data,axis=0)
x = np.arange(0,len(spec[0]))
plt.plot(x,spec[5])
plt.show()
The approximate wavelength range is ~3500 - 10,000 angstroms
—
Reply to this email directly, view it on GitHub
https://github.com/gmbrandt/xwavecal/issues/26#issuecomment-1467332290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGORGEOHYUPVIZSJ6UXCD3W37WPDANCNFSM6AAAAAAVZWUMMY
.
You are receiving this because you commented.Message ID:
@.***>

Not a problem, I really appreciate you taking time to help me out!
I think (hope?) it will be an easy fix.  I have code to create a file I think is in the correct format to input into this code, I've attached it here:
rearrange.py.zip
I can run the TEST_1.fits file in xwavecal, but the solution fails.
I'm not positive if the file is blue->red or vice versa.
There are definitely overlaps in the blue orders, but by the reddest orders there are no longer any overlaps.

Long delay. Anyway, looking at the spectra I agree there are clear overlaps in the blue orders. The issue, and the thing that is going to kill xwavecal's ability, is that the spectra are not blaze corrected. This is correctable though.
For example, look at this prominant overlap between order 10 and 11:

The duplicated lines between the two orders are clearly visible by eye, but xwavecal relies on these two sets of lines having the same flux within at least ~50% (this is configurable though).
Right now, it looks like they differ by 200% or more. Which is pretty typical when a spectrum is not blaze corrected.
Is there any flat file that you can divide this arc spectrum by? Usually things work pretty well if you just literally divide the 2d arc frame by a flat file (or a smoothed flat file), and then do the arc 1d extraction.
So my suggestion is: do that crude blaze correction outline above, then do the extraction and do the same kind of inspection of orders 10 and 11, and that same region, and see then if the raw amplitudes of the extracted peaks are within 40-50% of each other.


add some documentation [WIP]

Hi,
first thanks for creating this Addon, but this Addon needs some Documentation. I will list them here and may create a PR for the Readme later
What API Permission are needed?
If I just tick every Box in Tasks, that seems to be not enough
Something really wrong happened!
Traceback (most recent call last):
  File "/config/custom_components/hacs_vikunja_integration/api.py", line 95, in _api_wrapper
    raise HacsVikunjaIntegrationApiClientAuthenticationError(
custom_components.hacs_vikunja_integration.api.HacsVikunjaIntegrationApiClientAuthenticationError: Invalid credentials

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/hacs_vikunja_integration/config_flow.py", line 31, in async_step_user
    await self._test_credentials(
  File "/config/custom_components/hacs_vikunja_integration/config_flow.py", line 79, in _test_credentials
    await client.list_projects()
  File "/config/custom_components/hacs_vikunja_integration/api.py", line 48, in list_projects
    return await self._api_wrapper(method="get", url=url, headers=headers)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs_vikunja_integration/api.py", line 110, in _api_wrapper
    raise HacsVikunjaIntegrationApiClientError(
custom_components.hacs_vikunja_integration.api.HacsVikunjaIntegrationApiClientError: Something really wrong happened!

What Version is needed?
I had some old Version running, you need need at least Version 0.23.0, with the new API System
Where to find the To-do lists
Only found the new Todo Entities , but not the Tasks itself. Took a bit to find the new Item in the Navbar

and its using the new Home Assistant ToDo List Function, added in 2023.11.

** Can you use Automations? **
?
** Can you filter the Todo lists (closed, overdue...) **
?

Hey, sorry. Ive seen this issue right now. My permissions on the vikuna side are like this:

I stopped using vikunja, because we migrated to YouTrack. But im still open to help. Automations are not available except the ones which u can use for home assistant's todo lists.
There is no filter available. It should only list undone tasks

Question regarding home-assistants todo-list funtions.
I've seen code implementations for task deletion & creation.
However it seems to be commented out.
Is there a specific reason for this?


Export realtime_client

Improve developer experience by not having manually import realtime_client since it's a transitive dependency
What kind of change does this PR introduce?
Since RealtimeClient is a transitive dependency (for projects importing this package), dart doesn't automatically suggest importing from realtime_client package. So i added the one liner to supabase.dart
What is the current behavior?
You need to manually import 'package:realtime_client/realtime_client.dart'
What is the new behavior?
The manual import is not needed anymore.
Additional context

Thank you so much @igoriuz for pointing this out!
I think we can omit one line that I suggested, but other than that , LGTM!

Good catch! It's now committed @dshukertjr

@igoriuz Amazinng! LGTM!


do not encourage add custom jars to default connectors in presto-admi…

…n docs examples

looks good, thanks!


[WIP] doc: Add ADOPTERS.md

are these badges provided by BA?
it's nicer if different badges have different colors.

are these badges provided by BA? it's nicer if different badges have different colors.

It is auto generated by https://img.shields.io with putting the text, color, style in the link, e.g. https://img.shields.io/badge/-production-blue?style=flat, or https://img.shields.io/badge/-production-orange?style=flat

are these badges provided by BA? it's nicer if different badges have different colors.

Done, changed the color of Undisclosed to orange.


Analyze retain-by-default Python client behavior

In many cases, it seems counter intuitive that settings configured via python are retained-by-default.
For test scripts, this means every call to command() has to have retained=False. Instead, it may make sense to have the CLI operate in retained-by-default, but make the API exposed over python only operate as retained-when-specified.

Sounds good.


No difference in status after clicking 'accept' or 'decline' buttons

Environment
browser
Reproduction
watch(
() => cookieControl.isConsentGiven.value,
(current, _previous) => {
console.log(cookie isConsentGiven current=${JSON.stringify(current,null,4)})
console.log(cookie isConsentGiven previous=${JSON.stringify(_previous,null,4)})
},
{ deep: true }
)
logs the same:
cookie isConsentGiven current=true
cookie isConsentGiven previous=false
for both buttons 'accept' and 'decline'
Describe the bug
In both cases isConsentGiven changes from false to true:
const accept = () => {
setCookies({
isConsentGiven: true,
cookiesOptionalEnabled: moduleOptions.cookies.optional,
})
}
const decline = () => {
setCookies({
isConsentGiven: true,
cookiesOptionalEnabled: moduleOptions.cookies.necessary,
})
}
so no way to determine which choice is done.
Seems that setting
isConsentGiven: true,
when decline() in not logically correct.
The changes
undefined --> true  when accept()
undefined --> false when decline()
would look logically better.
Additional context
If initial status of isConsentGiven is undefined
then it becomes possible to watch a change in
const declineAll = () => {
setCookies({
isConsentGiven: false,
cookiesOptionalEnabled: [],
})
}
which now is impossible.
Logs
No response

isConsentGiven applies to all cookies and decline only applies to optional cookies (could be named declineOptional instead). Declining optional cookies still consents to required cookies, so isConsentGiven is set to true.
declineAll applies to required cookies aswell, so no consent is given in that case.
To make it more clear I think it would make sense for me to change the naming a bit.
So in summary:

use isConsentGiven to check if cookies were given consent at all
use cookiesEnabled or cookiesEnabledIds so check if the cookie you're interested in was given consent

"use isConsentGiven to check if cookies were given consent at all"
This is  ambiguous
isConsentGiven = true
means both:

optional+necessary cookies  were given consent ( by 'accept')
only necessary  cookies were given consent ( by 'decline' )

Yes, it is possible to distinguish by introduction of both
‘necessary' and ‘optional’  cookies but impossible without having ‘optional’ cookies. Documentation does not mention this feature.

I don't really understand the answer. Is there anything you wish for? If so, please give a detailed specification :heart:

Closing this as it seems reasonable to me to watch the enabled cookies. If you need button click events feel free to submit a PR! Should be fairly easy to implement :raised_hands:

I also disagree with the current logic.
If you click decline, you expect that isConsentGiven will return false.
Everything else is not intuitive.
Could you add the logic in the docs, so others can understand.


Add version warning.

Fixes #649

@tomdee does the ordering of versions.yml have any current significance?
I moved master to the bottom so .first always returns the latest release.

I don't think the overall version ordering matters. The patch order is important so it displays properly on the releases page.


Hotfix/0.9.1

What does this PR do

Corrects usage of parameters in fastlane/AppCenter iOS template
Introduces make ci, used by Github Actions to use a pre compiled binary.

Task

resolves #104
resolves #105

Checklist:

[x] I ran make validation locally with success
[x] I have not introduced new bugs
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new errors

Warnings

:warning:
The library files were changed, but the tests remained unmodified.
Consider updating or adding to the tests to match the library changes.

  Generated by :no_entry_sign: Danger Swift against 525019a318441c9e060a39a3d0fbe5309d5cc7d9


Question about ablation in the paper: "Ours + StableDiffusion"

Hi,
thanks for releasing the code/paper, I really enjoyed reading it!
While looking at the ablations, I was wondering how exactly you implemented "Ours + StableDiffusion":

Did you apply the img2img task with StableDiffusion (e.g. as in SDEdit)?

Did you estimate monocular depth and apply the depth2img task with a finetuned StableDiffusion model + start from noised input image as in SDEdit?

These two would provide some form of image conditioning, but only using the current rendered image as input (without the original image as additional conditioning).
So is my understanding correct that the edits with these approaches are too low-quality / inconsistent and that the InstructPix2Pix performs better at this task, which is why you get so much better results in the end?
Thank you so much in advance!
Lukas

Hi!
So our implementation of "Ours + StableDiffusion" is simply using our Iterative Dataset Update method but instead of editing the images with InstructPix2Pix, we edit the image using Stable Diffusion. Therefore, there is no image conditioning. We did not apply the img2img task nor estimate monocular depth. I agree that the two ideas you listed would provide Stable Diffusion with some form of image conditioning.
The reason the "Ours + StableDiffusion" result looks poor is that when you input the current render and try to edit it, 1) the text prompt is hard to formulate as we cannot use a simple text instruction, but rather we have to come up with an elaborate prompt to describe a real-world image, and 2) there is no grounding in the original image to enforce consistency. This is why the results look unreasonable. Let me know if you have any other questions!

Thank you very much for the response, that makes sense clears up the implementation for me :)


SSL certificate problem: certificate has expired

It appears that the SSL certificate has expired for wttr.in
$ curl https://wttr.in/
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Thank you


luci: remove installation of attendedsysupgrade

The package is only useful when running an official build. The ImageBuilders used for this service can not contain any special compiler flags etc. used by custom builds.
Instead of installing the package whenever luci is installed, it should be installed via the buildbots itself, like it's currently done for luci.
@ynezz do you mind adding the loci-app-attendedsysupgrade package via the buildbots?
Signed-off-by: Paul Spooren<EMAIL_ADDRESS>

Sounds like you want luci-light? See https://github.com/openwrt/luci/pull/6211

Well I don't want to confuse people using a custom build


indexQuery - indices not applied when filtering without condition i.e. has("index")

As discussed in this thread https://groups.google.com/d/msg/aureliusgraphs/lbRw4ItFxtg/IsJ9K_jPktMJ there is currently a limitation when filtering without condition on ES extended indices.
At the moment, code is not applying indices when filtering without condition since is necessary working out how to make this call to ES. See the if sentence on StandardTitanTx#execute()
(https://github.com/thinkaurelius/titan/blob/master/titan-core/src/main/java/com/thinkaurelius/titan/graphdb/transaction/StandardTitanTx.java#L882).
Also, as this is a purely backend related issue, any backend specific logic would be better placed only into the backend adapter.

Related to #932.


Add network ID to container inspect

Fixes issue #19089
Signed-off-by: Wen Cheng Ma<EMAIL_ADDRESS>

Adding this to the milestone, not sure if "design review" is actually needed, so feel free to skip forward to "code review"
/cc @mrjana

LGTM.
Just a note (I dont think we must document it... but wont harm I guess) :
the network-id for default bridge network will change across daemon restarts.
That's because default-bridge network is the only network for which the network
configuration can change across reboots (due to the legacy daemon configurations).

LGTM

docs LGTM
ping @vdemeester @MHBauer for review

docs LGTM 🐸

Userns build completed successfully but GitHub was never notified:
14:59:05 ---
14:59:05
14:59:05 Error response from daemon: no such id: docker-pr-userns4914
14:59:05 Error: failed to remove containers: [docker-pr-userns4914]
14:59:05 Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
14:59:06 Finished: SUCCESS

Merging! :tada:


IP2Location LITE in Varnish 4 VMOD?

Does this library also support IP2Location LITE database?
http://lite.ip2location.com?

No, this only covers GeoIP2 from maxmind.
There is a IP2Location VMOD at https://github.com/controversy187/libvmod-ip2location.
Haven't tried myself so I can't comment on it.