[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/eventing-writers knative-sandbox/serving-writers
/assign knative-sandbox/eventing-writers knative-sandbox/serving-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping k8s.io/code-generator fb849a7...fb849a7:
bumping k8s.io/apimachinery 276a8a7...276a8a7:
bumping k8s.io/klog/v2 7ea6d6a...43cc75f:
  > 43cc75f Merge pull request # 309 from serathius/owners
  > fb03dab SetContextualLogger: remove unintentionally merged API call
  > 48ee3dd Cleanup OWNERS file
  > 263155b Merge pull request # 307 from pohly/start-flush-daemon
  > f5927b0 SetLoggerWithOptions: support flushing
  > 6684fc7 StartFlushDaemon: add API with more control over flushing
  > a77ab7d Merge pull request # 304 from pohly/go-1.14-testing
  > ae0c078 Merge pull request # 305 from pohly/flush-and-exit
  > 1e923c6 tests: stop testing with Go 1.14
  > 6631b8c Merge pull request # 296 from pohly/contextual-logging
  > cd54fdc ExampleSetLogger: reset state after test
  > f676d4a Merge pull request # 303 from pohly/flush-and-exit
  > 260ac21 contextual logging
  > 0013f22 exit_test.go: avoid depending on side effect of other tests
  > 56b8a4e structured logging: replacing Fatal/Exit/etc. without loss of flushing
  > d888550 make klog sufficient for working with logr
  > 64be563 move Kubernetes helper code into separate file
  > 07fe246 testinglogger: per-test, structured logging
bumping knative.dev/hack 14f832e...f067737:
  > f067737 Adding code of conduct to reference knative/community's CoC (# 162)
bumping k8s.io/client-go b425fb6...97582f2:
  > 97582f2 Update dependencies to v0.23.5 tag
bumping knative.dev/pkg e6e3cf0...0a1ec2e:
  > 0a1ec2e upgrade to latest dependencies (# 2474)
  > 1f7514a bump k8s deps to v0.23.5 (# 2469)
  > 19a2589 fix coverage settings (# 2471)
  > 2daa86a Electors can provide an initial set of buckets (# 2473)
bumping k8s.io/api a1613d7...cd271e7:
  > cd271e7 Update dependencies to v0.23.5 tag
  > a6b2207 Merge pull request # 108139 from liggitt/automated-cherry-pick-of-# 108138-upstream-release-1.23
  > 80b93d4 Revert v1beta1 PodDisruptionBudget select patchStrategy

/lgtm
/approve


Alexnet GRPC example not working: "upstream connect error or disconnect/reset before headers. reset reason: protocol error"

/kind bug
What steps did you take and what happened:
Following the steps to implement a custom GRPC predictor as per the docs.
The model script and manifest were used as shown in the above linked docs, and tested successfully in a docker container.
Port forwarding to the inferenceservice pod directly also works.
However, trying to ping the inferenceservice on k8s via a port-forward to the istio-gateway gives the following error message:
Traceback (most recent call last):
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\build_utils\docker\kserve-model\serve-example\test_grpc_server.py", line 40, in <module>
    res = client.infer(infer_request=request)
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\kserve\inference_client.py", line 104, in infer
    raise rpc_error
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\kserve\inference_client.py", line 96, in infer
    response = self._client_stub.ModelInfer(
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\grpc\_channel.py", line 946, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\grpc\_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "upstream connect error or disconnect/reset before headers. reset reason: protocol error"
        debug_error_string = "{"created":"@1677794613.394000000","description":"Error received from peer ipv6:[::1]:8080","file":"src/core/lib/surface/call.cc","file_line":1075,"grpc_message":"upstream connect error or disconnect/reset before headers. reset reason: protocol error","grpc_status":14}"
>
Exception ignored in: <function InferenceServerClient.__del__ at 0x0000020EA6BB2820>
Traceback (most recent call last):
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\kserve\inference_client.py", line 77, in __del__
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\kserve\inference_client.py", line 83, in close
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\grpc\_channel.py", line 1564, in close
  File "c:\Users\Sebastian.Scherer\Projects\ml-serve-app\.venv\lib\site-packages\grpc\_channel.py", line 1548, in _close
AttributeError: 'NoneType' object has no attribute 'StatusCode'

client test script used for testing servers (works for docker):
from kserve import InferRequest, InferInput, InferenceServerClient
import os
import io
from PIL import Image

client = InferenceServerClient(url=os.environ.get("INGRESS_HOST", "localhost")+":"+os.environ.get("INGRESS_PORT", "8080"),
                            channel_args=(('grpc.ssl_target_name_override', os.environ.get("SERVICE_HOSTNAME", "custom-model-grpc-kserve-test.example.com")),))

# get image: curl https://www.python.org/static/apple-touch-icon-144x144-precomposed.png > image.png
image_data = image = Image.open('C:\\path\\to\\image.png').convert('RGB')

# bytify image
byteImgIO = io.BytesIO()
image_data.save(byteImgIO, "PNG")
byteImgIO.seek(0)
image_bytes = byteImgIO.read()

infer_input = InferInput(name="input-0", shape=[1], datatype="BYTES", data=[image_bytes])
request = InferRequest(infer_inputs=[infer_input], model_name="custom-model")
res = client.infer(infer_request=request)
print(res)

Checking the inferenceservice's pod istio proxy container logs shows:
[2023-03-02T22:03:22.731Z] "- - -" 0 - - - "-" 9702 1010 13 - "-" "-" "-" "-" "<IP_ADDRESS>:8081" inbound|8081|| <IP_ADDRESS>:34673 <IP_ADDRESS>:8081 <IP_ADDRESS>:56944 outbound_.8081_._.custom-model-grpc-predictor-default.kserve-test.svc.cluster.local -

The istio-gateway pod logs show the following:
[2023-03-02T21:30:30.392Z] "POST /inference.GRPCInferenceService/ModelInfer HTTP/2" 200 UPE upstream_reset_before_response_started{protocol_error} - "-" 120 0 4 - "<IP_ADDRESS>" "grpc-python/1.43.0 grpc-c/21.0.0 (windows; chttp2)" "420834c5-f4bc-9ea7-ba57-a62d60f7f09e" "kserve-neuron-grpc-v2-kserve-test.example.com" "<IP_ADDRESS>:8080" outbound|8080||kserve-neuron-grpc-v2-predictor-default.kserve-test.svc.cluster.local <IP_ADDRESS>:41662 <IP_ADDRESS>:8080 <IP_ADDRESS>:54786 - -
2023-03-02T21:35:41.300626Z	info	xdsproxy	connected to upstream XDS server: istiod.istio-system.svc:15012
[2023-03-02T22:03:22.730Z] "POST /inference.GRPCInferenceService/ModelInfer HTTP/2" 200 UPE upstream_reset_before_response_started{protocol_error} - "-" 6823 0 4 - "<IP_ADDRESS>" "grpc-python/1.43.0 grpc-c/21.0.0 (windows; chttp2)" "3e4346fc-93a7-9c7e-ad5a-7d7f54850c17" "custom-model-grpc-kserve-test.example.com" "<IP_ADDRESS>:8081" outbound|8081||custom-model-grpc-predictor-default.kserve-test.svc.cluster.local <IP_ADDRESS>:56944 <IP_ADDRESS>:8080 <IP_ADDRESS>:45650 - -
2023-03-02T22:06:18.848941Z	info	xdsproxy	connected to upstream XDS server: istiod.istio-system.svc:15012

What did you expect to happen:
A successful response from the inferenceservice
What's the InferenceService yaml:
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"serving.kserve.io/v1beta1","kind":"InferenceService","metadata":{"annotations":{},"name":"custom-model-grpc","namespace":"kserve-test"},"spec":{"predictor":{"containers":[{"image":"484375727565.dkr.ecr.us-east-1.amazonaws.com/vodafone-sentiment-cicd-poc:kserve-serve-example","name":"kserve-container","ports":[{"containerPort":8081,"name":"h2c","protocol":"TCP"}]}]}}}
    serving.kserve.io/deploymentMode: RawDeployment
  creationTimestamp: "2023-03-02T21:14:13Z"
  finalizers:
  - inferenceservice.finalizers
  generation: 1
  name: custom-model-grpc
  namespace: kserve-test
  resourceVersion: "150085493"
  uid: 306e06f9-77a7-4046-8ad9-193101b2d2dc
spec:
  predictor:
    containers:
    - image:<PHONE_NUMBER>65.dkr.ecr.us-east-1.amazonaws.com/vodafone-sentiment-cicd-poc:kserve-serve-example
      name: kserve-container
      ports:
      - containerPort: 8081
        name: h2c
        protocol: TCP
      resources:
        limits:
          cpu: "1"
          memory: 2Gi
        requests:
          cpu: "1"
          memory: 2Gi
status:
  address:
    url: http://custom-model-grpc.kserve-test.svc.cluster.local
  components:
    predictor:
      latestCreatedRevision: "1"
      url: http://custom-model-grpc-predictor-default-kserve-test.example.com
  conditions:
  - lastTransitionTime: "2023-03-02T21:15:27Z"
    status: "True"
    type: IngressReady
  - lastTransitionTime: "2023-03-02T21:15:27Z"
    status: "True"
    type: PredictorReady
  - lastTransitionTime: "2023-03-02T21:15:27Z"
    status: "True"
    type: Ready
  modelStatus:
    copies:
      failedCopies: 0
      totalCopies: 1
    states:
      activeModelState: Loaded
      targetModelState: Loaded
    transitionStatus: UpToDate
  observedGeneration: 1
  url: http://custom-model-grpc-kserve-test.example.com

Environment:

Istio Version: 1.13
Knative Version: n/a
KServe Version: 0.10.0
Kubeflow version: n/a
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm] aws w/ istio as per raw deployment instructions
Minikube/Kind version: n/a
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

Update: I found this solution on stackoverflow and will report back if this fixes it.


Upload HEAD coverage workflow is failing due to out of disk space error

Describe the bug

The Upload HEAD coverage workflow is failing on the main branch due to the runner running out of disk space.
see runs:

https://github.com/thin-edge/thin-edge.io/actions/workflows/head_coverage.yml

To Reproduce

Run the "Upload HEAD coverage workflow" on the main branch.
Expected behavior

The workflow should run without an error
Screenshots

Environment (please complete the following information):

OS [incl. version]
Hardware [incl. revision]
System-Architecture [e.g. result of "uname -a"]
thin-edge.io version [e.g. 0.1.0]

Additional context

We might be able to reuse the existing codecov step in the "Pull Request Checks" workflow which is also run on the PR and merge group events, though we might need to tweak the action if needed.

Removing the workflow and allowing the codecov to be uploaded in the Pull Request Checks workflow (both on PRs and merge queue events) seems to be working as expected, so closing the ticket.


Stop requiring users to depend on landmass.

Right now, to create IslandNavigationMesh, we need to create a landmass::NavigationMesh and a landmass::ValidNavigationMesh. We shouldn't do this. Instead we should either make bevy_landmass wrappers or re-export those symbols.

I believe this is solved since we are now re-exporting NavigationMesh and ValidationNavigationMesh.


视频能够播放,但是一快进或后退,就会重新播放.(而且播放不了本地视频,不过这没关系)

Video can play, but it will play back as soon as it is fast forward or backward, and it doesn't seem to work for video in this project

I encountered the same problem. Everytime I click on the progress bar trying to fast-forward or rewind, the video replays from the very beginning. I've set attribute 'hotkey' true, but did nothing.

@michaelfyc It should be your video server's problem.
The metadata about the video fast forward is provided by the video file server.

@Copay Thank you for your reply. What's interesting is that the problem seems to occur solely on Chrome, while Firefox, Edge, and even IE work rather properly. I guess I'll have to add extra things to headers?

如何播放本地视频


Register custom component that contains Zod schema

👋 I'd like to be able to register a custom component that contains a Zod schema:
For example:
const clientErrorResp = {
  description: 'There was an issue with the request sent by the client.',
  content: {
    'application/json': {
      schema: z.object({
        code: z.string().openapi({ description: 'Class of error that was generated.' }),
        message: z.string().openapi({ description: 'Details about the specific error instance.' }),
        errors: z.array(z.object({}).catchall(z.any())).optional().openapi({ description: 'Further information about the error(s) encountered.' }),
      }).strict(),
    },
  },
};

registry.registerComponent('responses', 'ClientError', clientErrorResp);

Unfortunately, it doesn't look like the Zod schema within gets transformed. Is there a method I can use to pre-transform it myself, or is there a way to convince the library to do that automatically?

My current hack to get around this is to just include a $ref property in the object, use it as part of a path without registering it as a component, and then manually extract all the refs after:
// Register all the endpoints
const registry = new OpenAPIRegistry();
registry.registerPath({
  // ... whatever
  responses: {
    400: {
      $ref: '#/components/responses/ClientError',
      description: 'There was an issue with the request sent by the client.',
      content: {
        'application/json': {
          schema: z.object({
            code: z.string().openapi({ description: 'Class of error that was generated.' }),
            message: z.string().openapi({ description: 'Details about the specific error instance.' }),
            errors: z.array(z.object({}).catchall(z.any())).optional().openapi({ description: 'Further information about the error(s) encountered.' }),
      }).strict(),
        },
      },
    },
  },
});

// Generate the document
const generated = new OpenAPIGenerator(registry.definitions, '3.0.0').generateDocument({});

// Track all refs found
const refs = new Map();
const replaceRefs = value => {
    if (value && typeof value === 'object' && value.constructor === Object) {
        // If this is a ref with other properties, process it
        const keys = Object.keys(value);
        if (keys.length > 1 && keys.includes('$ref')) {
            const ref = value.$ref;
            const match = ref.match(/^#\/components\/([^\/]+)\/(.+)$/);
            if (match) {
                const existing = refs.get(ref);
                if (existing) {
                    if (existing.value !== value) throw new Error(`Cannot redefine ref ${ref}`);
                    return { $ref: ref };
                }

                const unref = Object.fromEntries(Object.entries(value).filter(([ key ]) => key !== '$ref'));
                refs.set(ref, { value: value, processed: replaceRefs(unref), type: match[1], name: match[2] });
                return { $ref: ref };
            }
        }

        // This is a regular object, look for refs within it
        return Object.entries(value).reduce((obj, [ key, value ]) => ({
            ...obj,
            [key]: replaceRefs(value),
        }), {});
    } else if (Array.isArray(value)) {
        return value.map(replaceRefs);
    }

    return value;
};

// Replace all refs in paths and components
const paths = replaceRefs(generated.paths || {});
const components = replaceRefs(generated.components || {})

// Return the schema with refs injected
return {
    ...generated,
    paths,
    components: [ ...refs.values() ].reduce((obj, { processed, type, name }) => ({
        ...obj,
        [type]: {
            ...(obj[type] || {}),
            [name]: processed,
        },
    }), components),
};

This is definitely a hack, but at least lets me use refs anywhere in the document on the fly.

@MattIPv4 thank you for raising this up. I do think we can do that for sure. We are currently working on releasing a major release v5.0.0 containing an update on how the API is used for OpenApi 3.1 vs  OpenApi 3.0. So for the time being we would focus on delivering this.
However once we are done with it I'd go back and take a look on what we can do for this feature request. In the meantime if you want to, feel free to try and open up a PR which we can review.

I found this issue after attempting to share error responses as described in the Reusing Responses section of https://swagger.io/docs/specification/describing-responses/ and would also be interested in a way to accomplish this.


Patches einsum dimensionality in torch_connector - #716

Summary

Closes https://github.com/qiskit-community/qiskit-machine-learning/issues/716
Closes https://github.com/OkuyanBoga/hc-qiskit-machine-learning/pull/18 (merged)
Adds release notes since the dimensionality is automatically matched to the input at the user level.

✅ I have added the tests to cover my changes.
✅ I have updated the documentation accordingly.
✅ I have read the CONTRIBUTING document.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
1908

Relevant Lines:
2058

💛  - Coveralls

The Windows CI seems to be affected by this issue https://github.com/pytorch/pytorch/pull/124932, so we might need to wait for the PyTorch update to reflect in the CI before triggering the tests once again.


Support gzip?

Does this module support using gzip to compress the msg?

Not directly. You will have to create a zlib object and compress/decompress
the payload yourself as that is application specific encoding.
On Thu, Sep 14, 2017 at 9:50 PM Yao Zhao<EMAIL_ADDRESS>wrote:

Does this module support using gzip to compress the msg?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nats-io/node-nats/issues/161, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DEP5PT_WD_cyBvu2u-oTIh0UCpxe2ks5sidfXgaJpZM4PYY7V
.

I noticed this sdk transfer string message, not buffer, does that mean I should base64 my gzipped data?

If you set the option preserveBuffers you should be able to pass a Buffer in as the payload (and get them raw back)

thanks


error event recived but device is missing

Describe the bug
I have been using the integration for a few weeks now and it was working but now I'm getting the error below.
I have tried disabling/enabling and power cycles but no luck. Any idea what could be causing it, I a bit lost where to look next?
i have 4 cameras and one base, ever think seems to be working in the Eufy app and i haven't noticed and loss of devices.
To Reproduce
The error seems to always be present.
Expected behavior
Some help would be awesome to locate and fix the issues.
Screenshots

Hardware Information about Home Assistant
home-assistant OS 7.4  supervisor 2022.01.1
running in a VM on a Lenovo think center
Hardware Information about Cameras
Eufy 2 cam pro

Mine was working fine too, did a reboot after updating to 7.4 and now I get the exact error you are refering too

https://github.com/fuatakgun/eufy_security/issues/280 seems to be the same

after update to latest HA / eufy its back up in my case

this should happen in first install, sometimes we are not able to receive all device specific information at expected time, even though events are receiving. Reinstalling the integration should eliminate this.

@fuatakgun This happened today when I updated the haos to 8.0 and refused to start any camera cards until I did a Dev Tools restart from YAML tab.
Suggest adding in some delay check (not sure what it needs before this error will resolve, waiting on port 3000 on localhost) before attempting to start up cards or adding a start-up delay option in the cards?
"Retrying in background" doesn't seem to fix this issue.
See below for log entries:
2022-05-16 22:03:29 WARNING (MainThread) [homeassistant.config_entries] Config entry 'localhost' for eufy_security integration not ready yet: Exception: Host/port is not reachable localhost 3000!; Retrying in background
.......
2022-05-16 22:03:47 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry localhost for eufy_security
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/eufy_security/__init__.py", line 51, in async_setup_entry
    await coordinator.initialize()
  File "/config/custom_components/eufy_security/coordinator.py", line 87, in initialize
    await self.set_devices()
  File "/config/custom_components/eufy_security/coordinator.py", line 163, in set_devices
    if await self.async_get_device_properties() is False:
  File "/config/custom_components/eufy_security/coordinator.py", line 184, in async_get_device_properties
    for device in self.devices.values():
AttributeError: 'NoneType' object has no attribute 'values'
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected
2022-05-16 22:03:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Event received but device is missing, maybe not connected

Same here. Even after Update to the newest Eufy Integration

delay was introduced by one PRs, this should be resolved


Add EventHub sample code

Please remove those generated files

Please remove those generated files

Removed some files from wwwroot. Let me know if we should also remove the js and css files too.

You would need READM.md to explain everything about this sample project

Can we just reuse the existing WebDemo app and add Event Hub support? I believe it will simplify the app a lot (and reduce the number of files).


status_text() doesn't work

Hi! I have the next problem:
I have two PC's connected to my Pixhawk. One of them is connected via serial port (micro usb) and the other is connected via 'Telem1' port (configured as Mavlink output). What I what to do is so simple. From one PC I want to send a custom command using telemetry_server.publish_status_text(). This message should travel across the pixhawk and it should be read by the other PC where I am using the next code block to be able to see the messages I receive:
async for msg in drone.telemetry.status_text():
        print(str(msg.type) + ": " + msg.text)

Well... If I run manually ./mavsdk_server serial:///dev/ttyACM0:115200 I can see that I receive the messages correctly because they are printed in the console.
However, when I run my python program, I only receive the messages auto generated by the pixhawk (Prearm check, etc etc) but I dont receive my messages.
The code I'm using to send the messages is the following:
from mavsdk import System
from mavsdk.telemetry_server import TelemetryServerError, StatusTextType, StatusText
import asyncio
import sys
import time

async def main(args=None):
    drone = System()
    await drone.connect("serial:///dev/ttyS0:115200")

    text = StatusText(StatusTextType.CRITICAL, "CUSTOM: Hello World")
    while (True):
        try:
            await drone.telemetry_server.publish_status_text(text)
        except TelemetryServerError as e:
            print(e)
            continue
        print("Message Sended!")
        time.sleep(1.5)

if __name__ == "__main__":
    loop = asyncio.get_event_loop()
    loop.run_until_complete(main(sys.argv))

Help please!

So basically you want forward statustext messages from the companion through Pixhawk to the ground station, correct?
I think you're missing two pieces:

You need to make sure forwarding is enabled in PX4. For this, every mavlink instance (connection) needs to have forwarding enabled: For Telem1, this would be: MAV_0_FORWARD, for the USB one it doesn't look like it is easily possible. However, it might work without setting it there. The place where it would need a change is in cdc_acm_check.cpp. You would have to add '-f' before the last argument nullptr.
You probably need to set the system id on the companion side to be the same as the system id of the autopilot, like this: https://github.com/mavlink/MAVSDK-Python/blob/108cb85a11401e007bf1b5a00744c3a7262a7e51/examples/send_status_message.py#L21


Any plans to support adding view permission?

Category

[x] Question
[ ] Documentation issue
[ ] Bug

Expected or Desired Behavior
Currently the roles are read and write. I'm wondering if there's any plan to support view role which could map to sharepoint view permission.
Also what's the resolution on #471?

Thanks for your feedback.
Since you are sharing a new feature request (enhancement / suggestion) about SharePoint, could you please add this via the SharePoint Developer Platform UserVoice at http://aka.ms/sp-dev-uservoice?

Regarding 471 this is an old issue that should be closed out.  If the issue still reproduces please create a new issue.

I'm not asking for a sharepoint feature, it already has a view permission; issue 471 talks about querying the "SP.View Only" role for example which btw doesn't show up in my tests, I can make a new issue.
What I'm asking for is a onedrive feature to support adding/deleting the "SP.View Only" role on an item.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Change language_level for documentation examples to Python 3

It looks like not all of the documentation examples work right with language_level set to 3 (the default) - see #5065 as an example.
I don't think we want to change the test-suite as a whole right now, but the public-facing documentation would be better tested with the settings that people will actually be using.

hello @da-woods, I am considering working on this bug now, is it ok? I am asking because maybe you could have any special suggestions since all issues with help wanted and good first issues are a bit old. :}

I think this still needs doing even if old.
We just haven't been hugely good at keeping up with "help wanted" and "good first issue" tags.
In runtest.py there's an examples_dir - those need to be run with language_level=3 and any issues relating to that fixed.

opened the PRs #6139 and #6140, but more are coming, the goal is to update everything from the examples dir.

#6143 is supposed to solve all problems related to this issue, but while checking everything in examples_dir I stumbled into some edge cases.
Compiling c_property.pyx I got:
warning: docs/examples/userguide/extension_types/c_property.pyx:7:4: complex already a builtin Cython type
Should I change this example to something not defined in cython builtin?

Compiling casting_python.pyx the output was:
warning: docs/examples/userguide/language_basics/casting_python.pyx:4:4: 'Py_intptr_t' redeclared
Do you think I should change this?

From memory_layout_2.pyx:
Error compiling Cython file:
    cdef int[::view.indirect, ::1, :] a
    cdef int[::view.indirect, :, ::1] b
    cdef int[::view.indirect_contiguous, ::1, :] c

    # INVALID
    cdef int[::view.contiguous, ::view.indirect, :] d
            ^
------------------------------------------------------------

docs/examples/userguide/memoryviews/memory_layout_2.pyx:11:12: Only dimension 2 may be contiguous and direct

Error compiling Cython file:
------------------------------------------------------------
...
    cdef int[::view.indirect, :, ::1] b
    cdef int[::view.indirect_contiguous, ::1, :] c

    # INVALID
    cdef int[::view.contiguous, ::view.indirect, :] d
    cdef int[::1, ::view.indirect, :] e
            ^
------------------------------------------------------------

docs/examples/userguide/memoryviews/memory_layout_2.pyx:12:12: Indirect dimension may not follow Fortran contiguous dimension

In this case, I assume everything is as expected because the errors are in the file. Is it correct?

In quickstart.pyx and memoryview_sum.pyx
The compiler is sending a warning suggesting to use a boundscheck(False). Do you think that is needed to update the code or just use the arg -X boundscheck=False is fine?

In condition_sum.pyx we have a "special case". I am using Cython version 3.0.10 and according to the change log and I also checked the code, prange doesn't support the use_threads_if yet, but the code seems to be good.

Apart from the comments mentioned,  cython -3 / cython -3 -+ commands are working as expected.

Compiling c_property.pyx I got: warning: docs/examples/userguide/extension_types/c_property.pyx:7:4: complex already a builtin Cython type
Should I change this example to something not defined in cython builtin?

No - I think it's a good simple example.

Compiling casting_python.pyx the output was: warning: docs/examples/userguide/language_basics/casting_python.pyx:4:4: 'Py_intptr_t' redeclared
Do you think I should change this?

Yes I think so - if you can just get rid of the typedef that'd be good (probably also applies to the pure Python example of the same thing)

In this case, I assume everything is as expected because the errors are in the file. Is it correct?

Yes - that's expected

In quickstart.pyx and memoryview_sum.pyx

Personally I'd leave those - the example still works without boundscheck and adding more things makes it harder to read quickly.

In condition_sum.pyx we have a "special case". I am using Cython version 3.0.10 and according to the change log and I also checked the code, prange doesn't support the use_threads_if yet, but the code seems to be good.

Yes - the docs are for the master branch so include things not yet in a release (although you can also view the docs for the release branch). No need to change anything there.

Compiling casting_python.pyx the output was: warning: docs/examples/userguide/language_basics/casting_python.pyx:4:4: 'Py_intptr_t' redeclared
Do you think I should change this?

Yes I think so - if you can just get rid of the typedef that'd be good (probably also applies to the pure Python example of the same thing)

Included in the PR.

My final question regarding this issue is if I should keep the -3 arg option as it is ? Is it important to keep the support to cy2?

My final question regarding this issue is if I should keep the -3 arg option as it is ? Is it important to keep the support to cy2?

Not completely sure what you mean by that.
However, what I'd suggest is changing the behaviour in runtest.py:
https://github.com/cython/cython/blob/b2965bd476752da410ad5a62447185841da5aa8a/runtests.py#L2848-L2854
This block controls the testing of the examples directory. I think that should just be changed to use language_level=3 and ignore the command-line argument.

My final question regarding this issue is if I should keep the -3 arg option as it is ? Is it important to keep the support to cy2?

Not completely sure what you mean by that.
However, what I'd suggest is changing the behaviour in runtest.py:
https://github.com/cython/cython/blob/b2965bd476752da410ad5a62447185841da5aa8a/runtests.py#L2848-L2854
This block controls the testing of the examples directory. I think that should just be changed to use language_level=3 and ignore the command-line argument.

Thanks, you got it right. I got distracted by the option -3 used by other parts of the code.

Closed d17f7460c6558bf2790acfacddd99c9d52c25a8d


TypeError: Cannot read property 'forEach' of undefined

Hi,
I get this now but i don't know why :/ , any idea ?
Thank you :)
Édit : i use gulp-document 2.2.0,  same  thing with 2.1.0, i tried so many things without success during 2 hours but i dont know why i get This error.  Its mysterious :/

+1

When I try to use format: 'html' I get cannot read property 'forEach' of undefined. Yet, when I try to use format: 'md' I get cannot read property 'reduce' of undefined.

Same problem here, any tips?

I'm having the same issue JordanMajd describes.

+1

Also having this problem.

+1

Can anyone share their gulp configuration? Thanks!

Hi!
Having same issue, both md and html.
Using gulp task as described in your documentation:
gulp.task('documentation', function () {

  gulp.src('./app.js')
    .pipe(documentation({ format: 'md' }))
    .pipe(gulp.dest('md-documentation'));

});

I think upgrading to documentation v4 will solve the problem. I used documentation 4 beta 2 directly from the command line and it works as it should.

+1

+1

i hit a similar issue (which searching for led me here). i knew my problem was from documentation.js failing at dependency resolution.
adding the shallow: true option let me run it successfully. though, of course, it's not resolving the dependencies.
i just installed documentation.js and i have a meteor project with funky requires so i have no idea what i'm missing, but this might at least let you run something:
gulp.task('doc', () => {
  gulp.src('blah.js')
    .pipe(documentation({shallow: true, format: 'md'}))
    .pipe(gulp.dest('./doc'));
});

+1

+1

Hi guys, I know I'm the author of this issue but today, I don't use anymore gulp, so I don't have follow the evolution of this issue. I don't close it but if you think it's good, I let you to close this issue. Good luck ;)

Please update to "documentation": "^4.0.0-beta11"


Run azd pipeline config requires additional operations on CodeSpace

Describe the issue:
When run azd pipeline config  in Dev Container, get error as follow:

Repro Steps:

Clone the repo to local and reopen with Dev Container.
Run azd auth login
Run azd pipeline config

Environment:

OS: Dev Container.
Azd version: 1.4.1  (commit https://github.com/Azure/azure-dev/commit/1cbed85cf47ed235b5ed31868eda79619525bfcc)
Python : 3.11
Template:
https://github.com/Azure-Samples/azure-django-postgres-flexible-aca
https://github.com/Azure-Samples/azure-django-postgres-flexible-appservice
https://github.com/Azure-Samples/azure-django-cosmos-postgres-aca
https://github.com/Azure-Samples/azure-django-cosmos-postgres-appservice
https://github.com/Azure-Samples/azure-django-postgres-addon-aca
https://github.com/Azure-Samples/azure-flask-postgres-flexible-aca
https://github.com/Azure-Samples/azure-flask-postgres-flexible-appservice
https://github.com/Azure-Samples/azure-flask-cosmos-postgres-aca
https://github.com/Azure-Samples/azure-flask-cosmos-postgres-appservice
https://github.com/Azure-Samples/azure-flask-postgres-addon-aca
https://github.com/Azure-Samples/azure-flask-cosmos-mongodb-aca
https://github.com/Azure-Samples/azure-flask-cosmos-mongodb-appservice
https://github.com/Azure-Samples/azure-fastapi-postgres-flexible-aca
https://github.com/Azure-Samples/azure-fastapi-postgres-flexible-appservice
https://github.com/Azure-Samples/azure-fastapi-cosmos-postgres-aca
https://github.com/Azure-Samples/azure-fastapi-cosmos-postgres-appservice
https://github.com/Azure-Samples/azure-fastapi-postgres-addon-aca

Expected behavior:
Run azd pipeline config can pass on CodeSpace.
@pamelafox  for notification.

Looks like it might be https://github.com/microsoft/vscode-remote-release/issues/8488#issuecomment-1549107575
cc @kjaymiller
Does it happen reliably or sporadically?

@pamelafox Tried multiple times, it happen reliably.

This does seem to happen for me as well...

Looks like it might be microsoft/vscode-remote-release#8488 (comment) cc @kjaymiller

That issue mentioned that it was supposed to be fixed in an update to DevContainers... can we verify that Codespaces uses that new version of DevContainers or should we just add the git safe configuration to include the directory

@kjaymiller There is no such issue with CodeSpace and add the git safe configuration to include the directory can reslove it in DevContainer.

I've filed this with azd team to see if they have suggestions, since I don't know why this would be specific to our sample: https://github.com/Azure/azure-dev/issues/2934

Comment from azd team from another thread:
"azd pipeline config won't work from codespaces if you used device-code for auth.
There's a codespaces limitation, as the container hosting the codespaces is not an enrolled-device to Msft, so it can't access MSGraph to create ServicePrincipals.
There's an ugly workaround in case you really need to run pipeline config on codespaces, but I would suggest running that command from your local computer instead"

@pamelafox I'm sorry for the misunderstanding caused by my mistake. This issue occurs on Dev Container instead of CodeSpace.
For testing azd pipeline config inside codespaces, azd team provided us with specific documents, refer to: https://microsoft.sharepoint.com/:w:/t/AzureDeveloperCLIazdPartners/Eb8miZZ_b01NsmOI1wPoDxEBC1h6SE8wqDNfgDrP4A-7QQ?e=BmYI2p


Navio 2 /ErleBrain 2 baseline Linux configuration

Opening this to track our work on getting the POSIX port running on RPi2 hardware and either of those two shields, and even the PXFmini.
Navio 2 :
Target Board : RPi 2
Sensors :
Navio + :
Target Board : RPi 2
Sensors :

MPU9250 IMU
MS5611 Barometer
PCA9685 PWM driver

Erle Brain 2 :
Target Board : RPi 2
Sensors :
PXFmini :
Target board : RPi Zero
Sensors :

MPU9250 IMU
MS5611 Barometer
PCA9685 PWM driver

Thanks for digging through the docs!

@ivereninov It would be fantastic to get a NAVIO 2 to Kabir. We have very much a focus on ports this month.

Thanks @mhkabir for putting this together. A few additional bits about Erle-Brain 2 and PXFmini:
Erle-Brain 2:
Target Board : RPi 2
Sensors :

MPU9250 IMU (SPI, /dev/spidev0.1)
MS5611 Barometer (SPI, /dev/spidev0.0)
PCA9685 PWM driver (I2C, 0x40)

Buses :

SPI : /dev/spidev0.1, /dev/spidev0.0
I2C : /dev/i2c-1
UART : /dev/ttyAMA0

Docs and support:

Erle-Brain 2 docs
Erle Robotics support

PXFmini:
Target Board : RPi0, RPi 2
Sensors :

MPU9250 IMU (SPI, /dev/spidev0.1)
MS5611 Barometer (SPI, /dev/spidev0.0)
PCA9685 PWM drivwqer (I2C, 0x40)

Buses :

SPI : /dev/spidev0.1, /dev/spidev0.0
I2C : /dev/i2c-1
UART : /dev/ttyAMA0

Docs and support:

PXFmini docs
Erle Robotics support

Following! I want to contribute. Let me know what i can do. Thanks!

Native build instructions are up here : https://pixhawk.org/modules/linux/rpi2
You would require my branch from here :
Compilation is relatively fast, even natively, so this setup works out OK for now. The rpi2 build target is stripped down for now.
For cross-compiling, we need a 4.8 cross-toolchain, which I don't think the Pi Foundation provides. Help ? @vmayoral @Clouded @ivereninov

Current state with native build :
pi@navio-rpi:~/PX4/Firmware$
[init] shell id:<PHONE_NUMBER>
[init] task name: mainapp

______  __   __    ___
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

Ready to fly.

pxh>

@vmayoral @bo-rc @Clouded Everyone please see #3527
The cross-compiler and native build targets work fine now.

Hi Kabir,
Do you think we can give this a try on the RPi2 with the Navio+?

@abencomo Yes you can :) Feel free to jump in! Just don't expect any hardware to work just yet.

@mhkabir Are we going to take assignments for the drivers?

+1, waiting for PX4 to work with Navio 2

Following the with great interest!
Just wanted to mention that the link to the RT Linux by Emlid points to the older Navio (1) version, the Navio 2 version (for RPi 3) is here: http://docs.emlid.com/navio2/Navio-APM/configuring-raspberry-pi/

I would also like to know when I can try this out my on rpi2/3

Available on master.


Could be integrated with Codeigniter 3.0?

Hey,
I enjoyed this ORM
but Could be integrated with Codeigniter 3.0?

I'm not sure I understand.

Sorry.
If this orm can be integrated easily with Codeigniter framework.
And if you can explain the integration in the documentation and in this way to reach more people.

Didn't the current instruction work?

The documentation is nice, but does not explain integration with codeigniter.
Thanks

Does Codeigniter have special requirements about integration of classes?

try to use composer and try to require this project and integrate in your codeigniter 3 if it will work


7  recipe detail

recipe detail page UI layout

@lianmccc search_results page looks slightly weird on my laptop

@lianmccc search_results page looks slightly weird on my laptop

@JakinHuangWang search_results and my_recipe page are in branch 6--RecipeCollection, I checkout branch7 based on 6, should we merge branch6 first?

@lianmccc That means the error comes from  6--RecipeCollection, it should be fixed before merge.

@lianmccc That means the error comes from 6--RecipeCollection, it should be fixed before merge.

I think @spencer-jin has a fixed search_results and my_recipe page in 6--RecipeCollection.


[Need Help] useTranslation() lang property is empty on components

Hi,
the lang property from useTranslation() hooks is empty when i log it from any components or custom hooks but the current language is set in every pages.
// Component Level
import useTranslation from 'next-translate/useTranslation'

export default function Header(){
 console.log(useTranslation().lang) // Empty ''
 return (...)
}

Any idea ?
Thanks in advance

@Hypernikao Which way are you using? pre-build with the CLI, using a custom server, dynamic routes?
If you are using the pre-build, check the parent page how is generated inside pages. It should have a I18nProvider with the corresponding lang. It would be very useful if you share here the generated outputted of the page to discard an issue.

Hi @aralroca ,
Thank you for your response.
I use pre-build with the cli. I call my component in custom layout from _app.js
here is the generated parent:
// @ts-nocheck
import I18nProvider from 'next-translate/I18nProvider'
import React from 'react'
import C from '../../_pages'
import ns0 from '../../public/static/locales/fr/common.json'

const namespaces = { 'common': ns0 }

export default function Page(p){
  return (
    <I18nProvider
      lang="fr"
      namespaces={namespaces}
      internals={{"defaultLangRedirect":"lang-path","defaultLanguage":"fr","isStaticMode":true}}
    >
      <C {...p} />
    </I18nProvider>
  )
}

Page = Object.assign(Page, { ...C })

if(C && C.getInitialProps) {
  Page.getInitialProps = ctx => C.getInitialProps({ ...ctx, lang: 'fr'})
}

@Hypernikao the generated output looks correct. Do you have some custom I18nProvider in your code? In that case, you always need to wrap the lang attribute into it.

The useTranslation implementation is just a wrapper of useContext:
import { useContext } from 'react'
import I18nContext from './_context'

export default function useTranslation(){
  return useContext(I18nContext)
}

So looks that the parent I18nProvider doesn't have the lang. 😕

I have not a custom provider.
My _app.js looks like:
import React from 'react';
import App from 'next/app';
import AppLayout from '../components/layouts/appLayout';
import { ThemeProvider } from 'styled-components';
import '../styles/global.css';
import { theme } from '../components/ui/themes/theme';

function MyApp({ Component, pageProps }) {
  return (
    <ThemeProvider theme={theme}>
      <AppLayout>
        <Component {...pageProps}></Component>
      </AppLayout>
    </ThemeProvider>
  );
}

MyApp.getInitialProps = async appContext => {
  const appProps = await App.getInitialProps(appContext);
  return { ...appProps };
};

export default MyApp;

And i just call an header component in my AppLayout

@Hypernikao this is related to this issue: https://github.com/vinissimus/next-translate/issues/44
_app.js is not wrapped right now with any i18nProvider. This is why this is happening... This is documented here.
As a temporal solution, meanwhile this is not fixed, is to move ThemeProviderand AppLayout  from _app.js to every page level...

Yes ! it exactly the point !
Thank you for your time.
I wait for this integration ...hope pretty soon.
Regards,

by the way, I noticed that you have an empty getInitialProps on _app.js level. Removing it, it would provide you a better performance because you are going to activate the Automatic Page Optimization 😊

@Hypernikao thanks to you to report it! Feel free to open more issues or PR 😄
I'm going to close this in favor of #44


Add flag to point Kubernetes volume_plugin_dir to a subdir mounted in…

…to kubelet_wrapper.
Since /usr/libexec/... is read-only on CoreOS, the default for this flag is completely useless. Let's make it useful.

@barakmich could you do  the same for mutli-node/aws/pkg/config/templates/user-data-{controller,worker}?

@barakmich what is status of this? Do you still want these flags?

Closing for now, but @barakmich let me know if you want it re-opened


undeploy endpoint with tests SRX-M5GOA4

There are two checks before undeploy an application:

check locks ( ignore env locks )
check that all releases are un-deployed

After testing I figured out that the first check is useless because no matter what is the type of lock the release will not be un-deployed when calling 'prepareUndeploy' endpoint then the 2nd check will fall immediately so the 2nd check contains the 1st one. ( see test number 4 ).
But I kept the 1st check, for now.

Looks good! Please update the commit message before merging. It should be about "what does the endpoint do", e.g something like this:
Added undeploy endpoint to completely remove a service
This endpoint only works when there are no app locks... and ...


unable to add new models

I was working on this engine and I wanted to add a new model to it. But rails g model is not working . I get the following error.
/home/raj/.rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:inrequire': cannot load such file -- rails/cli (LoadError)
from /home/raj/.rvm/rubies/ruby-2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:54:in require' 	from /usr/bin/rails:9:in '
can anyone help with this.

@rajeevriitm try rails g model at spec/dummy directory

Hi. There is nothing related with the blog engine itself.
Probably, you don't have rails installed.
Try to do the following:
bundle install
bundle rails g model <MODEL_NAME>


Updated to clictune's new domain "www.dlink4.com"

Fix(es):

I only added the new domain www.dlink4.com

[X] I made sure there are no unnecessary changes in the code;
[X] Tested on Chromium (Includes Opera, Brave, Vivaldi, Edge, etc);
[X] Tested on Firefox.

I teste on this link

Thanks!!


reduce bytes length for memory saving, closes #16

All tests passed. If you have any comments, please feel free to leave them.

@sun-jiao the change is actually on point, I am adding a test to re confirm this. Thanks


TabView.SelectionChanged() event handler: sender is not TabView

Describe the bug
In my event handler for a TabView's SelectionChanged, I am observing the sender to be the TabView's private inner ListView. This change was introduced by #971.
Steps to reproduce the bug

Use Microsoft.UI.Xaml.2.2.190731001-prerelease
Subscribe to SelectionChanged on a TabView
Observe that the sender is not the tab view, but instead something else.

Expected behavior
The sender for all non-routed TabView-originated events should be the TabView.
Version Info
2.2.190731001-prerelease

(TabView is just forwarding along the event here:)
https://github.com/microsoft/microsoft-ui-xaml/blob/40a8a80972fb8796586b4424aa1d4dd7ddeb2f1c/dev/TabView/TabView.cpp#L250-L260


RSA Key Pair Generation on JVM - CertificateException: Invalid Padding Bits

First of all great job!
I’m attempting to generate an RSA key pair with the following configuration:
rsa {
    paddings = setOf(RSAPadding.PKCS1)
    digests = setOf(Digest.SHA256)
    publicExponent = SigningKeyConfiguration.RSAConfiguration.F4
}

However, I encounter this error specifically on the JVM target (it works fine on iOS and Android):
java.security.cert.CertificateException: Unable to initialize, java.io.IOException: Invalid number of padding bits
	at java.base/sun.security.x509.X509CertImpl.<init>(Unknown Source)
	at java.base/sun.security.provider.X509Factory.cachedGetX509Cert(Unknown Source)
	at java.base/sun.security.provider.X509Factory.engineGenerateCertificate(Unknown Source)
	at java.base/java.security.cert.CertificateFactory.generateCertificate(Unknown Source)
	at at.asitplus.signum.indispensable.JcaExtensionsKt.toJcaCertificate(JcaExtensions.kt:218)

It appears to be an issue with converting to JcaCertificate. Any insights on resolving this for JVM?
Thanks

Thanks for the report. Looks like an issue with RSA signature encoding. We're on it. expect a hotfix release soon.

started here: https://github.com/a-sit-plus/signum/tree/hotfix/jcaCert but needs proper fixing.

started here: https://github.com/a-sit-plus/signum/tree/hotfix/jcaCert but needs proper fixing.

currently, it is cursed. the proper fix is to rework the RSA signature representation and a proper BIT STRING implementation, which is padding-aware and then fix the parseFromJca mess.

3.10.1 Hotfix release coming tomorrow

Release 3.10.1 (with #196 backported) should now be available from your favorite maven repository.
This should fix your issue, but we'd appreciate if you could confirm!


[Parse][CodeCompletion] Stop code completion within a closure causing parser recovery after the closure.

For example, the completion below would trigger error recovery within the first closure, which we recover from by skipping to that closure's right brace. The fact that we recovered though, wasn't being recorded. The closure was treated as still being in error, triggering another recovery after it that skips over the Thing token, giving a lone closure expression, rather than a
call as the next expression.
CreateThings {
    Thing { point in
      print("hello")
      point.#^HERE^#
    }
    Thing { _ in }
}

This isn't an issue for code completion when the outer closure is a regular closure, but when it's a function builder, invalid elements result in no types being applied (no valid solutions) and we end up with no completion results. We should have a fallback to handle when the other elements are legitimately invalid (rather than from parser recovery skipping things), but when the other elements are valid this fix gets us results in the meantime and should still give more accurate results compared to a single-function-builder-element fallback once we have one.
The fix here is removing the error status from the parser result after the initial parser recovery. We still needed to propagate the fact that the parsed AST node contained a code completion token though, so that the code completion callbacks still happen. This required dropping the invariant that ParserResult::hasCodeCompletion() implies ParserResult::isError(). To ensure there was no unintended behavior change, this updates existing checks of ParserResult::isError() that weren't directly related to this fix to use ParserResult::isErrorOrHasCompletion() instead (which is equivalent to the behavior of isError() prior to this change).

@swift-ci please test

@xedin There can't be multiple code completion token in a code completion invocation. If there's \0 character in a file and it's not at Lexer.CodeCompletionPtr, they are just invalid source characters.
In swift-ide-test, if there're multiple tokens (#^NAME^#) in a file, other tokens are completely removed from the file when testing a token. For example, given:
Thing {
  foo.#^FOO^#
  bar.#^BAR^#
}

The source file is converted to:
Thing {
  foo.\0
  bar.
}

When testing #^FOO^#.

@rintaro This might be a side effect but while Nathan and I were working on the member completion changes I have found a case where unrelated completion token was converted into ErrorExpr - test/IDE/complete_skipbody.swift - while completing #^FUNCTIONBODY^# value.#^LOCALFUNC_PARAMINIT^# became ErrorExpr. I had to adjust constraint generation to avoid failing on multi-statement closure bodies (https://github.com/apple/swift/pull/33590).

Right, bar. with a missing member after it like in Rintaro's example would become an ErrorExpr. What test case specifically are you after? A separate ErrorExpr in the same closure as the completion expr?

@nathawes That, and somewhere else but in the same function builder body so we had all cases covered.

It's not as important for the a regular code because all expressions are type-checked separately but function builders are a different story - whole body is one giant constraint system, so we need to make sure ErrorExpr from other completion tokens don't interfere.

@swift-ci please smoke test


tests: Adds in bills stuff

TL;DR
Added tests to verify that users can create bills and view bill details on the dashboard.
What changed?
New test cases were added to ensure that users can successfully create new bills, view bill details, edit due dates, and delete bills. Tests include verification of UI elements and form submissions.
How to test?

Navigate to the dashboard and log in.
Go to the Bills section.
Follow the steps in the tests to create, view, edit, and delete bills.
Verify that the UI behaves as expected and that the new bills are created, displayed, and updated correctly.

Why make this change?
To ensure that the functionalities for creating and viewing bill details are properly working and to add automated tests for future regression testing.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#68  👈
#67
#66
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jhechtf and the rest of your teammates on  Graphite

Merge activity

Jul 5, 4:04 PM EDT: @jhechtf started a stack merge that includes this pull request via Graphite.


HAI-2390 Update nuisance indexes for hanke areas in hanke form areas page

Description
Get updated nuisance indexes for hanke area from backend when user has filled all nuisance fields for area, or when area geometry or any nuisance fields are changed.
Jira Issue: https://helsinkisolutionoffice.atlassian.net/browse/HAI-2390
Type of change

[ ] Bug fix
[x] New feature
[ ] Other

Instructions for testing

Create new hanke or edit existing
Go to areas page of hanke form and draw new hanke area
Fill all nuisance fields for new area
When all of those are filled, nuisance indexes should be calculated for that area (area color should change and and indexes below fieldset should be updated)
Try modifying area geometry or nuisance fields
Nuisance indexes should be re-calculated on each change (you can verify this also in browser network tab)

Checklist:

[x] I have written new tests (if applicable)
[x] I have ran the tests myself (if applicable)
[ ] I have made necessary changes to the documentation, link to confluence
or other location:

Other relevant info
Please describe here if there is e.g. some requirements for this change or
other info that the tester/user needs to know.

Tested and it works. A few notes:

Selecting an area on the map does not change the area tab - should it?
Sometimes - not always and cannot reproduce this systematically - when the index color changes while dragging e.g. a corner of an area the dragging halts at that point. Not a big deal.
Should index 0 be gray instead of green?

Tested and it works. A few notes:

Selecting an area on the map does not change the area tab - should it?
Sometimes - not always and cannot reproduce this systematically - when the index color changes while dragging e.g. a corner of an area the dragging halts at that point. Not a big deal.
Should index 0 be gray instead of green?

For the 2nd point, it seems that if altering the area that is also selected as tab, this happens: the dragging of a corner halts when index coloring changes.

Tested and it works. A few notes:

Selecting an area on the map does not change the area tab - should it?
Sometimes - not always and cannot reproduce this systematically - when the index color changes while dragging e.g. a corner of an area the dragging halts at that point. Not a big deal.
Should index 0 be gray instead of green?

Fixed these.


feat: Add favicon and title

That's actually super cute! If you would like, you can propose favicons to our other 3 curricula (listed at the bottom of the readme)

Thank you very much!
I added the favicons as you asked me:
Data-science:
https://github.com/microsoft/Data-Science-For-Beginners/pull/235
IOT: https://github.com/microsoft/IoT-For-Beginners/pull/339
ML: https://github.com/microsoft/ML-For-Beginners/pull/450
I started translating some readme's into Italian too! ;)
Soon!
Ludovico
Il giorno dom 31 ott 2021 alle ore 15:19 Jen Looper <
@.***> ha scritto:

Merged #488 https://github.com/microsoft/Web-Dev-For-Beginners/pull/488
into main.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Web-Dev-For-Beginners/pull/488#event-5545263870,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILJSH72WPB5R6UHGU3M7NLUJVF7XANCNFSM5HCKFN4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


[Bug]: odh-dashboard authentication overlay service error in ODH operator 1.4.0 log, OCP 4.10.36

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Manifests version / tag 1.4.0
OCP Cluster Version 4.10.36
KfDef:
apiVersion: kfdef.apps.kubeflow.org/v1
kind: KfDef
metadata:
  name: opendatahub
spec:
  applications:
  - kustomizeConfig:
      repoRef:
        name: manifests
        path: odh-common
    name: odh-common
  - kustomizeConfig:
      overlays:
      - authentication
      repoRef:
        name: manifests
        path: odh-dashboard
    name: odh-dashboard
  - kustomizeConfig:
      repoRef:
        name: manifests
        path: ceph/object-storage/scc
    name: ceph-nano-scc
  - kustomizeConfig:
      repoRef:
        name: manifests
        path: ceph/object-storage/nano
    name: ceph-nano
  - kustomizeConfig:
      overlays:
      - trusted-ca-bundle-path
      parameters:
        - name: trusted-ca-bundle-path
          value: "/opt/app-root/etc/jupyter/custom/cacerts/trustedcas.pem"
        - name: s3_endpoint_url
          value: "http://ceph-nano-0"
      repoRef:
        name: manifests
        path: jupyterhub/jupyterhub
    name: jupyterhub
  - kustomizeConfig:
      overlays:
      - additional
      repoRef:
        name: manifests
        path: jupyterhub/notebook-images
    name: notebook-images
  repos:
  - name: manifests
    uri: https://repo.internal.ch/artifactory/datascience_internal/opendatahub-io-odh-manifests-v1.4-0.tar.gz
  version: master

Application deployment in namespace does not proceed correctly, stuck at stage odh-dashboard. Error message:
...
rolebinding.rbac.authorization.k8s.io/odh-dashboard serverside-applied
deployment.apps/odh-dashboard serverside-applied
time="2022-11-11T13:27:22Z" level=info msg="Watch a change for Kubeflow resource: odh-dashboard.odhsven."
time="2022-11-11T13:27:22Z" level=info msg="Watch a change for Kubeflow resource: odh-dashboard.odhsven."
route.route.openshift.io/odh-dashboard serverside-applied
time="2022-11-11T13:27:22Z" level=warning msg="Encountered error applying application odh-dashboard:  (kubeflow.error): Code 500 with message: Apply.Run : Service \"odh-dashboard\" is invalid: [spec.ports[0].name: Required value, spec.ports[1].name: Required value]"
time="2022-11-11T13:27:22Z" level=warning msg="Will retry in 5 seconds."
secret/dashboard-oauth-config serverside-applied
serviceaccount/odh-dashboard serverside-applied
...

Currently, base service is
https://github.com/opendatahub-io/odh-manifests/blob/master/odh-dashboard/base/service.yaml
overlay is
https://github.com/opendatahub-io/odh-manifests/blob/master/odh-dashboard/overlays/authentication/service.yaml
unclear why the error message spec.ports[1].name missing is appearing, there is no port 1, but probably a follow-up error.
ODH Deployment is stuck because of this. No other software, like in my case jupyter, is installed.
Expected Behavior
service odh-dashboard is created correctly
probably, a name needs to be added in the form of an add-operation to the port in the authentication overlay.
rest of the KfDef components are created correctly
could be a related error to the bug in 4.10 that is only fixed in OCP 4.11:
https://bugzilla.redhat.com/show_bug.cgi?id=2077943
In any case, adding a port name to the one service port is no big deal so that it works with 4.10.
Steps To Reproduce
No response
Workaround (if any)
No response
What browsers are you seeing the problem on?
No response
Open Data Hub Version
1.4.0

Anything else
No response

adding the following to /overlays/authentication/service.yaml worked on our cluster. I now have odh-dashboard running.
I modified the file in the unpacked tar.gz of odh-amnifests, then packed it again and used it in the KfDef server download location
- op: add
  path: /spec/ports/0/name
  value: odh-dashboard

oh, man, I still had services from a previous deployment 1.2.0  in the namespace, had just deleted the Kfef. I got suspicious, used the original manifests again: Working well, even without the name patch. Are there any plans to clean up resources in a namespace correctly when KfDef changes? It did no work for me, except manually deleting all routes, services, configmaps, secrets ...

@shalberd thanks for the issue -- glad you found a way around it. We are working to get a label on everything so you can see what resources are created within the dashboard -- but we didn't go into deployment of the dashboard. That's more operator territory I would think. Let me bring in my colleague to see if we can work on this from the deployment of the dashboard itself angle.
@LaVLaS any thoughts here about cleaning up when KfDef changes?

@LaVLaS @VaishnaviHire  As mentioned, I had the odh-dashboard service present in the namespace and had to delete it in other for the odh-dashboard authentication overlay to work. I am unsure whether to re-open this ticket, because the patch should have worked, yet it threw the errror message, see main text.
main issue could have been that, conceptually, the service odh-dashboard was still present from a pre- 1.4.0 kfctl without server-side apply.
Apparently, when one tries to update objects that were created using client-side apply and now are managed with server-side apply, it creates issues.
Here, someone says:
https://github.com/kubernetes/kubernetes/issues/80916#issuecomment-525049458
"Basically, we are expecting you to --force when you transition into using serverside apply on an object (or apply once with no changes, but that's more steps). There's multiple ways we can make the client-side -> serverside transition smoother in the future."
https://github.com/opendatahub-io/opendatahub-operator/pull/171/files
So, in essence, my way of deleting the odh-dashboard service was in a way a workaround only, I guess.
The overlay update of the port fields should have gone through without any issues on service odh-dashboard, but it did not. The options you set, e.g. to force update, should be totally fine. They should not lead, in the context of kfctl and its use of patch mechanisms, to the error.


Add seek() and tell() to PipedCompressionReader

These are just passed along to the underlying _file (the process` stdout).
This is needed by dnaio on Windows because sys.stdin.buffer on Windows is seekable, which triggers a different code path in dnaio.singleend._detect_format_from_content that relies on seek() and tell().
Also, since PipedCompressionReader.seekable() already exists, we should also really have seek().
Tests fail because coverage drops. I’ll see whether I find the energy to add some. Test added

Thanks for the review!


Multiple fade-ins and fade-outs causing overlapping effect

JSFiddle: https://jsfiddle.net/zb0roed9/3/
If you set fadeIn/fadeOut to something long like 1.5 seconds, and then repeatedly pause and play something in quick succession, multiple instances of the source track can be heard for a brief moment, creating an overlapping/stacking effect.
If the player is in the middle of fading out (due to pause) and the user clicks play, I would instead expect the fade-out to stop at that moment and switch to a fade-in.
Is this overlapping effect intended?

Yeah this is intentional. The fadeOut time happens after 'stop' is hit.
Check out this issue for more discussion on this.

Yeah this is intentional. The fadeOut time happens after 'stop' is hit.
Check out this issue for more discussion on this.


MB-8063 Refactor handler for updating payment service item status to use service object

Description
Makes it so the UpdatePaymentServiceItemStatusHandler now uses the PaymentServiceItemStatusUpdater instead of using QueryBuilder from within the handler.
Reviewer Notes
We'll want to make sure this didn't break anything I missed with the tests. So try starting things up:
make db_dev_e2e_populate
make server_start
make office_client_start

and try reviewing some payment requests. Basic functionality should be unchanged from before.
Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Messages

:book:
:link: MB-8063

  Generated by :no_entry_sign: dangerJS against 3541a29f1c2700900dfaf0d1a0b3909cce041d49


Current ci is broken for python v.3.10

Current ci is broken  with import issues from 3rd party libs like a babel, wtfforms, and flake8 tests

Fixed by https://github.com/flask-admin/flask-admin/pull/2182 cc @michaelbukachi


Add simple dockerfile for email app

In https://github.com/ascoderu/opwen-webapp/issues/13 we intend to make the Lokole email application available via an online web interface. The easiest way to achieve this is to make the app deployable to our production cluster which hosts opwen-cloudserver. This pull request is a first step towards this direction and adds a Dockerfile for the Lokole email app.

Codecov Report

Merging #224 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #224   +/-   ##
=======================================
  Coverage   69.56%   69.56%
=======================================
  Files          28       28
  Lines        1712     1712
=======================================
  Hits         1191     1191
  Misses        521      521

Continue to review full report at Codecov.

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


Evaluate k3s/k3d for local dev

Background
We have used minikube and kind before to get our k8s environment to work against. k3d is another, which run k3s (a light version of k8s), in docker images. Currently I consider kind to be too troublesome to work with locally. Minikube is good at least now, but it isn't so quick to start kubernetes. Could k3d offer us this speedup for local dev and in CI?
Evaluation notes

It is relatively super fast to install and start relatively to minikube and kind.
k8s version can only be decided through choice of k3s release
k3s is a single node, k3d allow for multi node by docker encapsulation
Access to k3s cluster with kubectl is done by k3s kubectl while kubectl is to do what ever was done before. This is perfect in my mind.
Will not be able to use fancy k8s features, as the have been stripped away.
k3d may make more sense for local development as it wraps everything in the docker container, and is still quick
k3d by default need an import-images step, but it can be avoided with configuration, which is essential for performance reasons

Open questions

Can we install calico and test network policy configuration etc?
Are the available k8s features enough for us to run our CI tests?
How does it get its images, do they need to be loaded into the cluster like on kind, or can it access local docker images directly?
Can I use this on mac/windows, if not, what to recommend as a fallback?

Excellent tools, we adopted them and it reduced the CI tests in travis runtime significantly and the time it takes to get started to setup z2jh for local development!
Related PRs:
https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/1664
https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/1696


Export word list

Hi!
We are using it in BlueWallet to validate user input. It would be nice to have it exported by default in your library
Thank you!

LGTM

Can you please release new version to the NPM with this patch?
Thanks

Done


Small tweaks to build documentation

Added a few small changes to build documentation to cover things I ran into building, namely:

install snapcraft
add user to LXD group so they can access LXD during build
line to show how to install the resulting package (there is one in another section, but thought it'd be good to have it up top in regular build instructions)

Accidentally included another commit in this after the fact, I believe I've since reverted it.

Thank you @apnar


Removed usage of CNContactNoteKey

Hi there, while fetching contacts I've encountered error on iOS 13 related with com.apple.developer.contacts.notes, and I've just removed the usage of CNContactNoteKey and removed one line of code using it, and fetching contacts works again. So this is just small PR for that :)
And of course thanks for this lib!!

Thanks @brascene! Will review later.

The above fix worked for me as well, thanks.   In case anyone is searching for this fix, the error message from  Contacts.getContacts on failure is:
"The operation couldn’t be completed. (CNErrorDomain error 102.)"
According to the following post this is due to a privacy change in iOS 13:
https://stackoverflow.com/questions/57442114/ios-13-cncontacts-no-longer-working-to-retrieve-all-contacts

@joshuapinter Did you find time to review this, and can you merge it pls? I'm about to ship an app using this lib :)

Hey @brascene. I'd suggest pointing to your branch of the library in your package.json for now. That won't prevent you from shipping your app.
A breaking change like this will require a major release, unless we can figure out a way to keep the notes field with some changes to permissions, etc.

This has been merged into master and released to npm as v2.0.0-pre.2. Update your package.json accordingly or use master branch.
NOTE: You will no longer be able to access the notes attribute of a Contact so update your app if you're doing that.


Add Recoverer middleware

Description

https://github.com/go-chi/chi/blob/master/middleware/recoverer.go
Also review other middleware that's currently enabled

I'll take a look at this one as well.

@haydentherapper it looks like you already added the recoverer middleware a little while ago https://github.com/sigstore/timestamp-authority/blob/main/pkg/generated/restapi/configure_timestamp_server.go#L112
I can still review the already existing middleware in this issue though.


No tesstrain.sh file after installation

Environment

Tesseract Version:  5
Commit Number: built from source
Platform: Ubuntu 18

Current Behavior:
Running
git clone https://github.com/tesseract-ocr/tesseract.git
./autogen.sh
./configure --disable-graphics
make
make training
sudo make training-install

creates no tesstrain.sh for me, was the file removed? I don't see a mention of this in the docs
Expected Behavior:
Suggested Fix:

https://github.com/tesseract-ocr/tesseract/commit/93348a83a324a4

I'm having the same issue - I see that @amitdo has linked to where the file was removed from the tesseract repository, and that there are new scripts in the tesstrain repository, but the main training documentation has not been updated.

Yes, the documentation was not updated yet. That's why I didn't close this issue.

From version 5.0.0 Release Notes:

Training scripts

Remove the Bash based training scripts.
Move the Python based training scripts to the tesstrain repo.


Update new policies example to use MeshSubset

What happened?
We still have MeshService in top targetRef in our examples. These should be updated to MeshSubset.

We should go over the docs before announcing 2.9

It's already covered in https://github.com/kumahq/kuma-website/issues/1892#issuecomment-2371149455:

remove the top level MeshService

So it's a dup of #1892

We decided to close https://github.com/kumahq/kuma-website/issues/1892 so I'm reopening this because that scope is not yet addressed.

done via https://github.com/kumahq/kuma-website/pull/2003


Use Catch for unit tests

The latest Doctest release added a regression with MSVC 2015 (see #3228 and https://github.com/doctest/doctest/issues/573). Furthermore, Doctest is looking for maintainers (https://github.com/doctest/doctest/issues/554) and the future of the project is unclear. Meanwhile, Catch seems to be actively developed.

Hi @nlohmann,
did you measure the compilation and runtimes of the two libraries?
I switched from Catch to Doctest for one of my projects some time ago because the compilation times were comparatively large with Catch.
However this was before Catch decided to drop the header-only approach, so not sure how the situation looks currently
just curious, as I am somewhat involved with doctest now :)

This was the same reason for me to switch to Doctest. I don't really want to switch back to Catch, but I was afraid that Doctest somehow stalled as they were looking for maintainers (which seems to have been solved now). I did not compare the compilation times yet - the Catch branch #3236 does not work right now, because Catch triggers several compiler warnings. If the newest Doctest release 2.4.8 works, I will close this issue and hope to not touch the test suite again for a long time :)

Closed. Doctest development continues.


Support hostname, use port number other than 102, disabling ping chec…

PR for #77

Ping has been merged as part of https://github.com/killnine/s7netplus/issues/87


[Documentation] clusters: expects a list of projects

While kluctl expects a list for the definition of clusters, the documentation is wrong at that point.
https://github.com/kluctl/kluctl/blob/80a09dfc6c06c5fc7002d088e213664f4e047b09/docs/kluctl_project.md?plain=1#L19-L22
The correct configuration is:
clusters:
  - project:
      url: https://github.com/kluctl/kluctl-example-clusters

Fixed by https://github.com/kluctl/www-kluctl.io/pull/2


Hardcode location of C libraries on OS X

Changes proposed in this pull request:
I have hardcoded the path to the C libraries on OS X because find_library + LD_LIBRARY_PATH is not working. Hardcoding is in line with the official recommendations:

If wrapping a shared library with ctypes, it may be better to determine the shared library name at development time, and hardcode that into the wrapper module instead of using find_library() to locate the library at runtime. (source)

I have tested this on OS X Mojave (10.14.6), and it works as expected.

We don't take pull requests on our repositories. If you have an issue with the repository please contact<EMAIL_ADDRESS>


fix makeHot

This will fix the makeHot so it doesn't force-rerender every tiny little change that happens when used with routers.  It does this by not building a brand new component on every call of the resulting function.
const HotView = makeHot(() => HomeView, 'Home');
console.log(HotView() === HotView());

Before the above would return false, therefore a re-render would be forced every time . getScreen is called by react-navigation

Note that this will still cause problems when utilized as documented since
console.log(makeHot(() => HomeView, 'Home')() !== makeHot(() => HomeView, 'Home')())

Solution there would likely to use a Map of some sort to identify when we should return the previously created component instead of creating a new one.  Since I couldn't be 100% of the effects of doing this type of change I decided to at least make it fixable in the meantime.
See #490

As a bit more - the way to make things work as needed with this setup would be to do the following:
const HotViews = {
  Home: makeHot(() => HomeView, 'Home'),
};

const AppDrawerStack = createDrawerNavigator(
  {
    Home: {
      getScreen: HotViews.Home,
      navigationOptions: {
        drawerLabel: 'Home',
      },
    },

Also updated docs to show the HotViews method since the previously described way would not work as desired without providing some sort of cache layer (good next step).

Any plans for next release?

Released in v1.0.0-rc.10


adds .pam input support

We didn't have a way to pass uncompressed images with alpha to cjxl: .ppm and .pfm cannot do alpha. This adds .pam input. Still to be added is .pam output, but that's for another pull request.

Do we plan on doing .pam output as well at some point?

Do we plan on doing .pam output as well at some point?

We probably should. Atm we have ppm for uncompressed output, but that cannot handle alpha so atm you're forced to use slow png output when decoding images with alpha.
For output, I recommend we use the extension .pnm for "pick whatever is needed", which would use .pam if there's alpha, .ppm if there's no alpha, and .pgm if it's grayscale. That's the most convenient way to do it — and if you want specific output as .pam, .ppm or .pgm, you can use those extensions (in that case you'd get all-opaque alpha or grayscale-as-RGB if you use a format that can do "more than needed", and an error if you use a format that can do "less than needed").


Multi-state device in HS is represented as on/off

I have a virtual device that has four states, each with an assigned attribute/value pair in HS. (Motion, no motion, away, other)
However, within the integration, it is represented strictly as on/off both as a toggle device and on the timeline. The attributes of the entity show both the value (1) and the attribute title (e.g. Away).

This would be hard to handle from both the HS API and HA side, mostly because this does not correspond to an entity type in HA, other than maybe Sensor. This is a single ref in HA? If it’s represented as a switch in HA it’s because you have given on and off values to two attributes  in HS.

I am not extensively familiar with either but I understand what you're saying.
In HS it is a single ref with which I used multiple control values (e.g. onAlternate) but both on and off are present. For my control, I do not use on/off, so they could be removed or changed. If these are changed to NotSpecified, would this change the entity in HA?
Regarding entity types, with those in mind, is there a type that might expose the multiple states for control? I am relatively new to HA and do not expect you to troubleshoot my instance, simply trying to find a meet in the middle solution that allows this to work for both. Thanks!