Fix tagging of localizable keys by multiCombo fields

Use the raw subkey as the value of each option in a multiCombo field’s dropdown menu.
Fixes #9164.

Not sure if it’s related, but every time I hover over the feature, each chip in the field adds the localized value to the label redundantly:


Time zone format throws an UnimplementedError

This is something that is supposed to work according to the documentation:
https://api.flutter.dev/flutter/intl/DateFormat-class.html
Reference: https://github.com/dart-lang/intl/blob/5be03cb1d6613f546702d7ea51bf41e4443d04ca/lib/src/intl/date_format_field.dart#L626
https://github.com/dart-lang/intl/blob/5be03cb1d6613f546702d7ea51bf41e4443d04ca/lib/src/intl/date_format_field.dart#L631
https://github.com/dart-lang/intl/blob/5be03cb1d6613f546702d7ea51bf41e4443d04ca/lib/src/intl/date_format_field.dart#L635

From the docs

Known limitations: Time zones are not yet supported. Dart DateTime objects don't have a time zone, so are either local or UTC. Formatting and parsing Durations is not yet implemented.

:(

This seems like a duplicate of https://github.com/dart-lang/intl/issues/19 or https://github.com/dart-lang/intl/issues/74.

Yes, unfortunately it is... Closing in favor of #19 .


Login page shows error 400 when hosted on a non-standard port

Describe the bug
Signin page shows error 400 when hosted on a non-standard port.
Steps to reproduce
Steps to reproduce the behavior:

Install binary release, disable built-in tls
Configure nginx to listen on ports other than 443 and proxy to ocis
Open the webpage in browser (ideally in chrome)

Expected behavior
There should be no error.

If you remove the :8443 from the origin and referer header in the curl command the response code will actually be 200.

Update: it appears that this is caused by this line in my nginx.conf:
proxy_set_header Host $host

Which strips the port part from the original Host header. This can be fixed by changing it to:
proxy_set_header Host $host:$server_port

Now I'm not sure whether or not this is a bug.

Thanks for posting it.
Reverse proxy config is always considered "outside" of ocis. But good to know. The ocis built in IdP has a check for the domain match. It can only be run exactly on the same domain.
For other setups I recommend to use keycloak like in the the deployment examples.

@mmattel FYI


Enhance the Falcon Helm charts with Falcon Container

The Helm charts need to be able to deploy Falcon Container or the kernel sensor

@redhatrises isn't that already the case? Or am I missing something here.
https://github.com/CrowdStrike/falcon-helm/blob/main/helm-charts/falcon-sensor/values.yaml#L6

There is missing functionality to fully closing this. With the operator providing more functionality and ultimately the helm chart will be updated to deploy the operator, I continue to debate adding in all the missing components.

Closing this as a lot of remaining functionality has been added. See #103


Python: add FUNCTION DUMP and FUNCTION RESTORE commands

Issue #, if available:
N/A
Description of changes:
https://redis.io/docs/latest/commands/function-dump/
https://redis.io/docs/latest/commands/function-restore/
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can you add this to transaction or not yet?

Can you add this to transaction or not yet?

I will create a different PR to address transacations for Dump, Restore, Function Dump, and Function Restore commands.


CLI releases failing

CLI release from https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/pull/1030 is failing with Resource not accessible by integration. https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/runs/4466990336?check_suite_focus=true
This does not seem related to GCP auth. https://github.com/actions/create-release/issues/103 seems similar but we should not need a PAT. actions/create-release also seems to be deprecated, so we will need to migrate to a maintained Action.

Workflow ran successfully, release created
https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/releases/tag/v0.4.1


Update _config.yml

good

It looks like you are attempting to push a change to the part repository, for help with deploying please start a new thread in the discussions.


not able to access the application deployed via spn -AADSTS500011: The resource principal named api:// was not found in the tenant

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

Minimal steps to reproduce

Tried to deploy the app using SPN , however am not able to access the application . Getting below Error
AADSTS500011: The resource principal named api:// was not found in the tenant named ***. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.

Any log messages given by the failure

AADSTS500011: The resource principal named api:// was not found in the tenant named ***. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.

Expected/desired behavior

OS and Version?

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

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

This issue is resolved

@achu152  How??


Prometheus Operator Failed to generate Kubelet Service

What did you do?
Deployed the Prometheus Operator
What did you expect to see?
The kubelet service with the associated endpoints
What did you see instead? Under which circumstances?
Two of our instances did not have an External IP or Internal IP registered with K8s while the AWS console reported an External IP and Internal IP.
The Prometheus operator tried to generate endpoints for all the Kubelets but failed since the Kubelets on the two instances didn't have valid IPs associated with them. Ultimately, we restarted the kubelets on the instances and K8s reported IPs for the instances.
I wonder if the better behavior should be to log this error and continue to generate endpoints for the remaining Kubelets so that a user can have some visibility.
Environment
CloudProvider: AWS

Prometheus Operator version:
quay.io/coreos/prometheus-operator:v0.23.1

Kubernetes version information:
v1.11

Kubernetes cluster kind:

Deployed via Kops on AWS

Manifests:

apiVersion: apps/v1beta2
kind: Deployment
metadata:
  labels:
    k8s-app: prometheus-operator
  name: prometheus-operator
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: prometheus-operator
  template:
    metadata:
      labels:
        k8s-app: prometheus-operator
    spec:
      containers:
      - args:
        - --kubelet-service=kube-system/kubelet
        - --logtostderr=true
        - --config-reloader-image=quay.io/coreos/configmap-reload:v0.0.1
        - --prometheus-config-reloader=quay.io/coreos/prometheus-config-reloader:v0.23.1
        image: quay.io/coreos/prometheus-operator:v0.23.1
        name: prometheus-operator
        ports:
        - containerPort: 8080
          name: http
        resources:
          limits:
            cpu: 200m
            memory: 200Mi
          requests:
            cpu: 100m
            memory: 100Mi
        securityContext:
          allowPrivilegeEscalation: false
          readOnlyRootFilesystem: true
      nodeSelector:
        nodePool: admin
      securityContext:
        runAsNonRoot: true
        runAsUser: 65534
      serviceAccountName: prometheus-operator

Prometheus Operator Logs:

Oh, sorry I didn't catch that! Thanks!


Database Not found

Database is missing . can u update database

I want too.

You want to contribute
On Jul 22, 2017 4:50 AM, "IMRAN NAZIR EMON"<EMAIL_ADDRESS>wrote:

I want too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vishusingh/student-information-system/issues/1#issuecomment-317145981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APlGEdn8nAisg_EDcxzPSbWdpRVwEk60ks5sQVVagaJpZM4D-06F
.

@emon-root database is updated

Where will I get it? Can you please give me a link?

working version of app is here http://arksnorman-sis.herokuapp.com/login/

@emon-root ^

Databse not found

@bolukom here https://sis.arksnorman.tk/
use admin as username and password


Fix and match tab groups in GRPC topic

Internal Review Topic
Quick patch for a couple of nits and tab groups. A warning cropped up this morning on another PR ...

| invalid-tab-group | aspnetcore/tutorials/grpc/grpc-start.md | Tab group with different tab id set. |

I think it was from a missing paren on https://github.com/aspnet/AspNetCore.Docs/pull/13954.

ok ... think that got it. There was also an inconsistent tab heading level.
Note that this topic isn't internally consistent on tab heading levels. I thought that we were always using 1st level headings for tabs (#) and ignoring the linter, which complains about the heading levels.
Anyway ... I left that alone, but I made sure that the tabs in each group use the same heading levels. If you want all tabs on 1st level, let me know, and I'll add a commit here to fix that.


The editor camera is grey / does not work

Happened as soon as we switched to bevy_dolly
https://github.com/janhohenheim/foxtrot/pull/231

Hmm, I haven't gone through all your code yet but I think the camera needs the editor camera component (I'll check up on this tomorrow).
See component here


Turn C# projects into Portable Class Libraries projects

Looks making Grpc.Core a PCL is not feasible (because DllImport and some other capabilitities are not part of the Profile259), but we can still make gRPC make work with CoreCLR by explicitly listing the dependencies.


S3 provider - Video upload in another folder

Hi, i was using amazon s3 , and i was trying to save the videos in a folder instead of the root folder. is there a way to specified the folder in the s3 provider configs. thank you so much

+1, I Have the same problem, looks like in the S3 Provider in the PutObject command the key for will always be just the name of the file (thanks to path.basename), so the file will be always be saved on the root of the S3.
Maybe we can a add an optional folder parameter in the S3 provider to add a custom folder where to save the videos.
async function putAsset(filePath: string, size: number, stream: ReadStream | Readable) {
  log.info(log.label('Uploading file:'), `${filePath} (${size} bytes)`);

  try {
    await putObject(s3, {
      ACL: 'public-read',
      Bucket: bucketName,
      Key: path.basename(filePath),
      Body: stream,
      ContentLength: size,
    });

yes, that seems like a useful feature! thanks for the feedback.
I'll add this for the bucket based providers.
/videos/ will translate to bucket root but folders in /videos/ will be kept if this is possible.
so /videos/cats/clip1.mp4 will go to /cats/clip1.mp4 in the bucket...
would that work for your use cases?

Yes that would be perfect thank you so much

Is this will also work for videos that come from remote sources? like a video from example.s3.com.video.mp4 i wanted to save this and another remote videos to videos(root S3)/todoApp/videos

that's a good call. it can't work with remote source urls.
we could add an extra config option but it would be fixed to one folder, does that work?

this is implemented in v0.14.0, would be great if you could test it out!
you can change the path locally to the video config JSON as well with a remoteSourceAssetPath callback.
an example next.config.js
// @ts-check
const path = require('path');
const crypto = require('crypto');
const { withNextVideo } = require('next-video/process')

/** @type {import('next').NextConfig} */
const nextConfig = {}

module.exports = withNextVideo(nextConfig, {
  remoteSourceAssetPath,
  provider: 'amazon-s3',
  providerConfig: {
    'amazon-s3': {
      endpoint: 'https://s3.us-east-1.amazonaws.com',
      generateAssetKey
    }
  },
})

function remoteSourceAssetPath(url) {
  const urlObj = new URL(url);
  return 'remote/' + toSafePath(decodeURIComponent(`${urlObj.hostname}${urlObj.pathname}`));
}

function generateAssetKey(filePathOrURL, folder) {
  if (!isRemote(filePathOrURL)) return filePathOrURL;

  const url = new URL(filePathOrURL);
  let hostnameHash = crypto.createHash('md5').update(url.hostname).digest('hex');

  return `${folder}/remote/${hostnameHash}/${path.basename(decodeURIComponent(url.pathname))}`;
}

function isRemote(filePath) {
  return /^https?:\/\//.test(filePath);
}

function toSafePath(str) {
  return str
    .replace(/^[^a-zA-Z0-9]+|[^a-zA-Z0-9]+$/g, '')
    .replace(/[^a-zA-Z0-9._-]+/g, '_');
}


Avatar spoofing from Slack to Discord with uppercase in nick doesn't work

Describe the bug
Avatar spoofing from Slack to Discord only works if nick is in lowercase.
To Reproduce

Make a webhook on Discord to allow nick and avatar spoofing
Configure a gateway between Slack and Discord
If nick on Slack is in lowercase, no issue. If there is an uppercase in nick, then the avatar is not spoofed.

Expected behavior
The avatar should be spoofed even it the nick has uppercases.
Screenshots/debug logs

Environment (please complete the following information):

OS: linux
Matterbridge version: 1.10.0

Additional context
not needed

Thanks for reporting and fixing! :)


Repair failling tests

Create test cases specific to state space/polynomial models ?

Resolved with the latest commits


Update ReadMe with new section and images

Hello Katie, I have updated the ReadMe with Jacob advises and new sections.
Could you please review, modify & merge this PR ?
Enclosed the 3 files

Mariam

This PR will be replace by a new one


Upload multiple images as assets [enhancement]:

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
Discord: shanedk
What should this feature add?
The ability to drag-and-drop multiple images to a board and have them import as assets. As it is, only individual PNG or JPEG files can be imported.
Alternatives
No response
Additional Content
I've run into this annoyance several times. Here's my latest experience, for a real-world example:
I downloaded an OpenPose collection so I could have ready-made poses to use: https://civitai.com/models/22214/openposes-collection
This is a collection of 47 poses. I'd like to put them into a "Poses" board as Assets so I can go to it any time I want and just grab the pose. As it is, I have to drag each of the 47 poses individually into Invoke to get them in as assets.
I should be able to just drag them all in at once. It would add them all as Assets for the current board and I could start using them, in ControlNets, IP Adapters, or whatever.

Closed with https://github.com/invoke-ai/InvokeAI/pull/7123


getClientRects() fails on Safari

In file text.ts, on line 86 the function getClientRects() fails on Safari browser.
This happened on text elements that had a whitespace to their left. Removing that whitespace, fixed the issue. Example:
 Text
does not work, but this:
Text
works

Could you give more detail what you mean with "fails"?
A codesandbox would help too

Will try to reproduce this as soon as I can


changed dhvParamCodes to CO2 and mhvParamCodes to FLOW. In where clause

Ticket
Emissions import errors from historical
Changes

Changed the use of the dhvParamCodes and mhvParamCodes variables in the where clause to use just 'CO2' and 'FLOW'.

This issue is being inadvertently handled in #5793.


Allow a single key type to map to multiple value types.

At the moment Phony rules, FileHash rules and ModTime rules all get mushed into one, because you want all of them to match on String keys. If some variant of apply_ was introduced, which didn't care about the result type (as most of them don't) you could use separate rules for each set of rules but make them all depend on the same key type.

Note that also rules currently do two modtime checks per file. With apply_ I could make that one and shrink the database a bit.

If you don't need an open universe on strings, you could use a GADT to encode the return type. This has the added benefit that you can still support apply with a return type (pattern matching on the GADT to determine the return type). This is especially true since you don't want to allow overlaps for rules which have different outputs but the same key.
For that matter, if you apply for a specific value, and there exists a rule for that key, but a different value, what are you supposed to do?

I definitely want an open universe, since then all the Shake rule types can be entirely separate from each other, without overlap.
I don't think there is any problem with different rules returning different keys, or overlaps. If given a particular string there are two matches, then that's an error, just like now. Overlaps of different types are not special.

For that matter, if you apply for a specific value, and there exists a rule for that key, but a different value, what are you supposed to do?

Not totally sure what that is asking. When you call apply the first time it will find the associated action from rule and run it, producing an output type. If you do it again, it won't be looking at the rule/action, it will just see a key/value pair in the database, with types that must be unique (given the key type and the value type), and then check it. I guess the thing that stops any problems is that each entry in the database is indexed by key, key type, and value type. (Or, if it's not, it will have to be.)

Yes, you'll have to index by key type and value type. If you only know about the monomorphic interface, that's kind of surprising, but OK!

What do you mean by the monomorphic interface - via need? I don't think such users are even aware that the underlying rule returns a value.

Yeah. (Well, it's only confusing if you decide you need to define some sort of rules on not filenames, and then you discover that it's indexed by key type and value type.)

Given the move to RuleResult which seems to have been a very good idea this is no longer possible, and thus was probably a bad idea anyway.


[.NET SDK] Herocard bug - not responding always

System Information (Required)

SDK language (C#)
Development environment -Azure Bot Service

Issue Description
I have built a bot and it displays a herocard as a response to a command. I have noticed that if I try to send the command in a new conversation with the bot, the bot does not respond with an answer, but if I send another command first, then the bot will answer with the HeroCard.
Code
List<CardAction> list = new List<CardAction>();
 list.Add(new CardAction { Title = "help", Type = ActionTypes.ImBack, Value = "help" });
 list.Add(new CardAction { Title = "commands", Type = ActionTypes.ImBack, Value = "commands" });
HeroCard hero = new HeroCard();
hero.Title = "Hello";
hero.Text = "text";
hero.Buttons = list;
var msg = ctx.MakeMessage();
msg.Attachments.Add(hero.ToAttachment());
await ctx.PostAsync(msg);

Example
Herocard response --> Hello
Normal response --> Goodbye
If i send first hello and then goodbye, the bot will answer only to the goodbye function. If I send first goodbye and then hello, then the bot will answer as normal both functions.
Steps to Reproduce

Send a herocard response right after the first message of the user.

Actual Results
There was an error sending this message to your bot: HTTP status code InternalServerError

@jerrak0s Can you post the code that reproduces this issue?

@jerrak0s What version of BotBuidler nuget package are using? Current version is 3.8.0.

@nwhitmont v3.5.5

@jerrak0s can you attach debugger and debug your bot? Based on your report, it seems that your bot code is hitting an exception and you see the internal server error. Let us know if this is an exception thrown by SDK.

@msft-shahins in skype i get this reponse
There was an error completing this request due to an internal channel failure.

@jerrak0s Are you still experiencing this problem?  Please share more of your bot's code.  It seems there is an issue inside the bot itself.

@EricDahlvang I tried the bot again today.

There was an error completing this request due to an internal channel failure.

@jerrak0s  Please share the code for the bot.

please reopen this if needed


startwith/startautomatically error squelched

When starting (this happens during StartWith and StartAutomatically) as a console app and encountering a file access error (which happens every time the app is running as a Service), the error is squelched.
I wouldn't consider this a crucial error, and after 2+ years of using this package, I'm down to about 10 minutes before I figure out what went wrong. But it would have saved me some severe headaches in  the past, so: can it be fixed?

I am closing all issues that haven't seen any activity. You're welcome to submit a PR to resolve the issue or provide more information.


Move AS<>IdP spec out of this repo

and potentially also the AS<>RS spec.
I still think the AS<>RS spec should stay because it is modeled after the GNAP Resource server spec.
@adrianhopebailie @wilsonianb

But is that a reason to make it part of the Open Payments standard?
If you look at the introduction of the GNAP RS spec it says:

The core GNAP protocol does not define any one specific mechanism for the resource server (RS) to communicate with the authorization server (AS), allowing the connection between these components to be solved orthogonally to the core protocol's concerns

The same applies for Open Payments. If we make this RS <> AS spec part of the standard we impose a lot of implementation burden on implementors that might want to build some much simpler because they know they will only ever have a single server that runs both the AS and RS components.
Let's wait and see if there is a need for interop between RS and AS implementations before we add anything more to the standard. If that time comes, we have a well defined spec in Rafiki that can be adopted as the standard.

I still think of the Rafiki AS as a reference implementation that can be plugged in and out. For AS' to be plug-able, the RS <> AS interaction should be standardized. But I see that this may be a weak argument and I guess I can be convinced to not standardize it for now.

Resolved in #205


SRV-H-1.3: ALB to ECS encryption

Finding:
ALB communications to backend is unencrypted over HTTPS
Recommendation:
Enable TLS on backend

Issue finding category updated to HTTPS

Potentially use https://aws.amazon.com/blogs/compute/using-aws-app-mesh-with-fargate/

Talked with @maxneuvians about using Envoy Sidecar to enable TLS for the Go Services


jsdoc types - jsx children - No overload matches this call. Property 'children' is missing in type. ts(2769)

Describe the bug
App.jsx
import { Show } from 'solid-js';

export default function App() {
  return (
    <Show when={true}>hello</Show>
  )
}

type error TS2769 at Show
No overload matches this call.
    Property 'children' is missing in type X but required in type Y. ts(2769)

stupid workaround
import { Show } from 'solid-js';

export default function App() {
  return (
    <Show when={true} children={<>hello</>}></Show>
  )
}

Your Example Website or App
https://stackblitz.com/edit/solidjs-templates-56uveg?file=src/App.jsx
Steps to Reproduce the Bug or Issue
repro does NOT work on stackblitz
jsconfig.json: jsx = preserve, checkJs = true
{
  "compilerOptions": {
    "module": "ESNext",
    "moduleResolution": "Node",
    "target": "ES2020",
    "jsx": "preserve",
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "checkJs": true,
  },
  "exclude": [
    "node_modules",
    "**/node_modules/*"
  ]
}

Expected behavior
no type error
quickfix: make children optional
Screenshots or Videos
No response
Platform
solid-js 1.6.0
vscodium
Additional context
No response

Also make sure to set the "jsxImportSource": "solid-js" as you might end up with like React types if you aren't careful.

set the "jsxImportSource": "solid-js"

yes, that was missing ... thanks!


Updating the documents in the repo after initial uses of OCA Bundles

Signed-off-by: Stephen Curran<EMAIL_ADDRESS>

Lots of fun updates to the docs.


doc: kconfig: Add some docs on 'if' and sanity checking in menuconfig

Two changes to the Kconfig best practices page:
doc: kconfig: Add section on (lack of) conditional includes

Add a section on how 'if' works to the 'Kconfig - Tips and Best
Practices' page, especially when combined with 'source'.

 It's probably simpler than most people assume.

doc: kconfig: Encourage using menuconfig as a sanity check

Some people never use the menuconfig, but it makes a good sanity check
when making Kconfig changes, so encourage it for that. Mention a few
things that can be checked in it.

Codecov Report

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

@@           Coverage Diff           @@
##           master   #14241   +/-   ##
=======================================
  Coverage   52.02%   52.02%
=======================================
  Files         307      307
  Lines       45484    45484
  Branches    10535    10535
=======================================
  Hits        23662    23662
  Misses      17030    17030
  Partials     4792     4792

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 5ac2461...37cd38b. Read the comment docs.


How to use the package?

Hi,
I used this package about 3 years ago and got great success with it. Now I'm trying to use it again but seems a lot has changed. Can you tell me how to get it working?
After installing package from git URL, I don't get any option to 'import' it in my project and hence I'm not able to use prefabs.
I tried downloading the package as a zip and opening scene in unity but that ran into same error as mentioned in #157
please could you help me out?
Thanks.

@sawan-kcl
Thank you for coming back to UnitySensors again!
Could you tell me what version (or URL) you used for the installation?

Hi,
Thanks for your response.
https://github.com/Field-Robotics-Japan/UnitySensors is what i used which i believe is version 2.0.4.

@sawan-kcl
Sorry for the late reply.
Changes in PR #158 that fixes #157 were not merged to version 2.0.4.
To use version 2.0.4, the same fix as in #157 must be made.
I will later release version 2.0.5 which fixes those issues.

@Autumn60
Thank you for your response. I did try using feature/commonPublisher branch but I couldn't get any data in RViZ. At this point I'm completely lost if I can even use this package.
Given the circumstances, please could you tell me what would be the best way for me to use this package?

@sawan-kcl
I updated master branch for fixing the issue.
Could you try master branch?
The URL used for installation is as follows.

UnitySensors: https://github.com/Field-Robotics-Japan/UnitySensors.git?path=/Assets/UnitySensors#master.
UnitySensorsROS: https://github.com/Field-Robotics-Japan/UnitySensors.git?path=/Assets/UnitySensorsROS#master.

@Autumn60
I tested it. The error msg in #157 does not pop up but the other issues remain. I'll list them down below:

No option to 'import' the package after installing, thus the prefabs don't show up in assets folder. when i try a search in 'All Prefabs' option under 'Favorites', I can see them and that's how I've been using them so far.

When trying to display images in Rviz2 (both from RGB and RGBD camera), RviZ2 crashes with following error:
terminate called after throwing an instance of 'image_transport::TransportLoadException' what():  Unable to load plugin for transport 'image_transport/compressed_sub', error string: According to the loaded plugin descriptions the class image_transport/compressed_sub with base class type image_transport::SubscriberPlugin does not exist. Declared types are  image_transport/raw_sub Aborted (core dumped)

When trying to display pointcloud2 data from RGBD, RViZ2 doesn't crash but i can't see any cloud ( I checked the frame_id ).

apparently the IMU works.

GPS throws following error in Unity:
NullReferenceException: Object reference not set to an instance of an object UnitySensors.Sensor.GNSS.GNSSSensor.UpdateSensor () (at ./Library/PackageCache/com.frj.unity-sensors@dc59e69b7f/Runtime/Scripts/Sensors/GNSS/GNSSSensor.cs:29) UnitySensors.Sensor.UnitySensor.Update () (at ./Library/PackageCache/com.frj.unity-sensors@dc59e69b7f/Runtime/Scripts/Sensors/UnitySensor.cs:36)

When i used the package back in 2021 (with ROS 1), from what i remember, I had to build and modify some Velodyne ROS packages to get the LiDAR data. I don't know if that's still the case. Any documentation on this would be very helpful. Then i can test out LiDAR pointclouds as well.

Also, please let me know if there are any documentations available to get the other sensors working as well.

Any updates on this?

@sawan-kcl
Thank you for the detailed report on each element.
I am not good at English, so I will answer in bullet points.

This is expected behaviour. Prefabs included in the package do not appear in the Asset list.
The name of the topic may be suffixed with ‘/compressed’ to ensure that the image is displayed correctly.

Thank you for testing!

Currently, the data is output as PointCloud2, so there is no need to prepare or modify the ROS package.

GNSSSensor requires an object _coordinateSystem to be set up to define the coordinate system in order to be used. For specific use cases, check the Demo_GNSS_ros scene.

https://github.com/Field-Robotics-Japan/UnitySensors/blob/b1a50503bb38017f902cb232b489de2de334d62b/Assets/UnitySensors/Runtime/Scripts/Sensors/GNSS/GNSSSensor.cs#L12-L13

@Autumn60
Thank you for your response.
Please also investigate number 2. It's not a topic naming convention problem. I checked.
I'm using ROS humble with Ubuntu 22.04 and Unity Editor version 2022.3.30f1.

There could be multiple causes. Can you confirm that the topic is flowing successfully with rostopic echo /pointcloud?

yes i can see data with ros2 topic echo /camera/depth/points but getting the buffer overflow while trying to display it in rviz2.

[rviz]: Message Filter dropping message: frame 'camera_frame' at time 34.786 for reason 'discarding message because the queue is full'

GNSSSensor requires an object _coordinateSystem to be set up to define the coordinate system in order to be used. For specific use cases, check the Demo_GNSS_ros scene.

https://github.com/Field-Robotics-Japan/UnitySensors/blob/b1a50503bb38017f902cb232b489de2de334d62b/Assets/UnitySensors/Runtime/Scripts/Sensors/GNSS/GNSSSensor.cs#L12-L13

while trying to open the scene, it says 'not allowed to open a scene in read only package.'

@Autumn60 Thank you for your response. Please also investigate number 2. It's not a topic naming convention problem. I checked. I'm using ROS humble with Ubuntu 22.04 and Unity Editor version 2022.3.30f1.

I was able to verify the behavior by modifying the topic name in the CameraInfo message.

Image topic name: /camera/color/image/compressed
CameraInfo topic name: /camera/color/image/camera_info
Rviz2 frame: camera_frame and

GNSSSensor requires an object _coordinateSystem to be set up to define the coordinate system in order to be used. For specific use cases, check the Demo_GNSS_ros scene.

https://github.com/Field-Robotics-Japan/UnitySensors/blob/b1a50503bb38017f902cb232b489de2de334d62b/Assets/UnitySensors/Runtime/Scripts/Sensors/GNSS/GNSSSensor.cs#L12-L13

while trying to open the scene, it says 'not allowed to open a scene in read only package.'

I had forgotten that a Scene imported as a package cannot be opened.
Can you recreate the scene using the following screenshots?
Set a GeoCoordinateSystem object for the CoordinateSystem in the GNSSSensor script component.

Hi,
I couldn't get the sensors working and it has been very frustrating. I really needed the depth camera for my project.
It was disheartening to not be able to use this package when I had already used it once before.
I'm going to look for other options now and I'll mark this issue as closed.

Hi, I just wanted to let you know that while trying to make my own sensor plugins, I was able to solve this problem. The main issue was the dependency on ROS2 package image-transport-plugins which can be installed with sudo apt install ros-${ROS_DISTRO}-image-transport-plugins and also the 'camera_info' topic for both RGB and Depth camera was mismatched which can be solved by the naming convention you suggested above.
I'm very happy that i got it working finally. I haven't tested the GPS yet but i'll let you know if i do.
Thank you.


update windows CI to glib 2.74

I figured this should be updated along with https://github.com/gtk-rs/gtk3-rs/pull/793 before I forget. Also update the windows VM so we can get the latest version of python and gvsbuild, and update gvsbuild command as it now works like a real python package.

I haven't noticed that we use gvsbuild to build gtk nowadays.
I guess the book should use that then too.

That's for gtk3

I see


Add support for Project Balkans

The Project Balkans map (Promods addon) is not currently supported. The mod has no localization support and also uses the improper names for several cities.
I have created a support file in my branch balkans for it https://github.com/erbkaiser/ETS2-Localization/tree/balkans

Project Balkans 5.2: https://promods.net/viewtopic.php?f=42&t=6779


Fix World.CreateRandomVehicle and add methods/properties for ambient entity spawning

I think I should define struct for the ped personality array.
The members will not likely to be changed at all, so hard-coding offsets for that array won’t be a problem.

I'm feeling like I should explain why the new World.CreateRandomVehicle has the predicate parameter. Dimensions of
ambient peds are so predictable unless you add big or small peds and make them spawn as ambient peds. However, those of ambient vehicles are not that predictable. That's the main reason why I add the predicate parameter.
This PR adds a overload ofWorld.CreateRandomPed with the predicate param, but that's a kind of advanced option.


Add document_topic matrix to output

We should have easy access to the distribution of topics for each document (the gamma matrix in LDA from the topicmodels package).
library(sparklyr) # version <IP_ADDRESS>32
library(dplyr)

sc <- spark_connect(master = "local")
fake_data <- data.frame(a = c(1, 2, 3, 4),
                        b = c("the groggy", "frog was", "a very groggy", "frog"))
fake_tbl <- sdf_copy_to(sc, fake_data, overwrite = TRUE)

fake_tokenized <- fake_tbl %>%
  ft_tokenizer(input_col = 'b', output_col = 'tokens')

count_vectorizer_model <- ft_count_vectorizer(sc, input_col = "tokens", output_col = "features",
                    dataset = fake_tokenized)

fake_model <- count_vectorizer_model %>%
  ml_transform(fake_tokenized) %>%
  ml_lda(features_col = 'features', k = 2)

# How can I find the distribution of topics (1, 2) for each document (1, 2, 3, 4)?

Is ml_topics_matrix(fake_model) what you're looking for?

Hi Kevin -
I believe that ml_topics_matrix(fake_model) returns a matrix with the distribution of words in each topic.  The gamma matrix should return the distribution of topics in each document.
Thanks,
-Alex

@alexpavlakis thanks, we'll a closer look for the next release. In the meantime could you check out https://spark.apache.org/docs/latest/api/scala/index.html#org.apache.spark.ml.clustering.LDAModel to see if this information is available/can be derived from the model class?

@kevinykuo thanks.  It should be available via "topicDistribution".  In fact, it looks like it should be available in ml_lda.  From the help file:
topic_distribution_col: Output column with estimates of the topic mixture distribution for each document (often called "theta" in the literature). Returns a vector of zeros for an empty document.

However, it doesn't seem to be available in the fitted model object.  Should it be possible to access with something like invoke(jobj, "topicDistribution") ?

You can transform the input dataset to ml_lda() with the model:
fake_features <- count_vectorizer_model %>%
  ml_transform(fake_tokenized)
fake_model <- ml_lda(fake_features, features_col = 'features', k = 2)
ml_transform(fake_model, fake_features) %>%
  dplyr::glimpse()

@kevinykuo, thanks that is very helpful.


&.% operator raise syntax error

work
p [10, 20, 30].map &.+(3)
p [10, 20, 30].map &.modulo(3)

raise syntax error
p [10, 20, 30].map &.%(3)

# Syntax error in test.cr:1: expecting any of these tokens: IDENT, +, -, *, /, %, |, &, ^, **, <<, <, <=, ==, !=, =~, !~, >>, >, >=, <=>, ===, [], []=, []?, [ (not 'DELIMITER_START')
#
# p [10, 20, 30].map &.%(3)
#                      ^

crystal version
Crystal 0.23.0 (2017-06-30) LLVM 4.0.1

This is a bug in the lexer, it's lexing &.%(3) as & . %( 3 ), making % as a delimiter start, and not as a identifier for a method name.


Strip bmi

This PR removes all of the references to the BMI that I could find.
Additionally, I added a line to the README that points to the BMI_pyDeltaRCM repository, where we now support the BMI as a wrapper around the pypi version of this package.
IMPORTANT: if y'all approve of this PR, I would like to remove the _WMT at the end of the repository. I will do this immediately after we merge this PR. I will then create 1) another PR that updates all of the links and text in this repository, and 2) update the deltarcm.org website accordingly. In the meantime, I believe GitHub will automatically redirect requests at the old repo name to the new repo name. You will want to update the remotes on your local git accordingly.

Codecov Report

Merging #82 into develop will increase coverage by 1.44%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop      #82      +/-   ##
===========================================
+ Coverage    84.44%   85.89%   +1.44%
===========================================
  Files           12       11       -1
  Lines         1305     1191     -114
===========================================
- Hits          1102     1023      -79
+ Misses         203      168      -35

Impacted Files
Coverage Δ

pyDeltaRCM/__init__.py
100.00% <100.00%> (ø)

pyDeltaRCM/_version.py
100.00% <100.00%> (ø)

pyDeltaRCM/model.py
85.18% <0.00%> (-5.56%)
:arrow_down:

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 cb82e79...3923430. Read the comment docs.

but we don't need to keep the parameters.yaml or deltaRCM.yaml.tmpl files in the BMI_pyDeltaRCM repo?

It's a good question. When I read the BMI 2.0 specifications, I couldn't find anything about it. The files will never be deleted from the .git history, so will always be recoverable based on the commit hash.
I'll do these steps today:

open an issue in BMI_pyDeltaRCM that asks whether we need these files.
include a permalink to the files on github in that issue
open a question on the csdms/help-desk repo asking about these files

but we don't need to keep the parameters.yaml or deltaRCM.yaml.tmpl files in the BMI_pyDeltaRCM repo?

It's a good question. When I read the BMI 2.0 specifications, I couldn't find anything about it. The files will never be deleted from the .git history, so will always be recoverable based on the commit hash.
I'll do these steps today:

open an issue in BMI_pyDeltaRCM that asks whether we need these files.
include a permalink to the files on github in that issue
open a question on the csdms/help-desk repo asking about these files

Sounds good, at least that'll keep us from forgetting they ever existed (even if the git history never forgets, we might).

See question in the help-desk here
See issue in BMI_pyDeltaRCM here


Read Handler Slow to respond

Describe Your Problem:
Read Handler Slow to respond , is there a way to set the system to wait longer for this so it does not generate this message to the log file.
Logs:
/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'BasementO/S' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Kitchen Cntr' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Craft Cove' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Basem. Kitch' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Deck Chand' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Deck Sconce' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'MudRoom' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'KitchenCans' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'O/SMainE.LT' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Entry Chands' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Livingroom' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'LivingRmwest' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'DiningChand.' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'DiningWest' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'BackDeck' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'O/SN.Entry' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@On] The read handler for the characteristic 'On' on the accessory 'Deck chandel' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@Current Temperature] The read handler for the characteristic 'Current Temperature' on the accessory 'Thermostats' was slow to respond!
5/20/2021, 1:39:07 PM [HOOBS 0160@Current Temperature] The read handler for the characteristic 'Current Temperature' on the accessory 'Temp Sen. Outdr' was slow to respond!

**Plugin Config:**

```json
 {
            "platform": "OmniLinkPlatform",
            "plugin_map": {
                "plugin_name": "homebridge-omnilink-platform"
            },
            "name": "Omni",
            "port": 4369,
            "includeAreas": true,
            "includeZones": true,
            "includeBypassZones": false,
            "includeButtons": true,
            "includeUnits": true,
            "includeThermostats": false,
            "includeEmergencyAlarms": false,
            "includeAccessControls": false,
            "includeAuxiliarySensors": true,
            "setHomeToAway": false,
            "setNightToAway": false,
            "syncTime": true,
            "showHomebridgeEvents": false,
            "showOmniEvents": false,
            "showRequestResponse": false,
            "clearCache": false,
            "forceAutoDiscovery": false,
            "defaultAccessoryMappings": {
                "zone": "motion",
                "zoneFireEmergency": "smoke",
                "unit": "switch"
            },
            "sensors": [
                {
                    "zoneId": 1,
                    "sensorType": "none"
                },
                {
                    "zoneId": 2,
                    "sensorType": "none"
                },
                {
                    "zoneId": 3,
                    "sensorType": "none"
                },
                {
                    "zoneId": 4,
                    "sensorType": "none"
                },
                {
                    "zoneId": 5,
                    "sensorType": "none"
                },
                {
                    "zoneId": 6,
                    "sensorType": "none"
                },
                {
                    "zoneId": 7,
                    "sensorType": "none"
                },
                {
                    "zoneId": 8,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 9,
                    "sensorType": "none"
                },
                {
                    "zoneId": 10,
                    "sensorType": "none"
                },
                {
                    "zoneId": 11,
                    "sensorType": "none"
                },
                {
                    "zoneId": 12,
                    "sensorType": "none"
                },
                {
                    "zoneId": 13,
                    "sensorType": "none"
                },
                {
                    "zoneId": 14,
                    "sensorType": "none"
                },
                {
                    "zoneId": 15,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 16,
                    "sensorType": "none"
                },
                {
                    "zoneId": 17,
                    "sensorType": "none"
                },
                {
                    "zoneId": 18,
                    "sensorType": "none"
                },
                {
                    "zoneId": 19,
                    "sensorType": "none"
                },
                {
                    "zoneId": 20,
                    "sensorType": "none"
                },
                {
                    "zoneId": 21,
                    "sensorType": "none"
                },
                {
                    "zoneId": 22,
                    "sensorType": "none"
                },
                {
                    "zoneId": 23,
                    "sensorType": "none"
                },
                {
                    "zoneId": 24,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 25,
                    "sensorType": "none"
                },
                {
                    "zoneId": 26,
                    "sensorType": "none"
                },
                {
                    "zoneId": 27,
                    "sensorType": "none"
                },
                {
                    "zoneId": 28,
                    "sensorType": "none"
                },
                {
                    "zoneId": 29,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 30,
                    "sensorType": "none"
                },
                {
                    "zoneId": 31,
                    "sensorType": "none"
                },
                {
                    "zoneId": 32,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 33,
                    "sensorType": "none"
                },
                {
                    "zoneId": 34,
                    "sensorType": "none"
                },
                {
                    "zoneId": 35,
                    "sensorType": "none"
                },
                {
                    "zoneId": 36,
                    "sensorType": "none"
                },
                {
                    "zoneId": 37,
                    "sensorType": "none"
                },
                {
                    "zoneId": 38,
                    "sensorType": "none"
                },
                {
                    "zoneId": 39,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 40,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 41,
                    "sensorType": "none"
                },
                {
                    "zoneId": 42,
                    "sensorType": "none"
                },
                {
                    "zoneId": 43,
                    "sensorType": "none"
                },
                {
                    "zoneId": 44,
                    "sensorType": "none"
                },
                {
                    "zoneId": 45,
                    "sensorType": "none"
                },
                {
                    "zoneId": 46,
                    "sensorType": "none"
                },
                {
                    "zoneId": 47,
                    "sensorType": "none"
                },
                {
                    "zoneId": 48,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 49,
                    "sensorType": "contact"
                },
                {
                    "zoneId": 50,
                    "sensorType": "none"
                },
                {
                    "zoneId": 51,
                    "sensorType": "none"
                },
                {
                    "zoneId": 52,
                    "sensorType": "none"
                },
                {
                    "zoneId": 53,
                    "sensorType": "none"
                },
                {
                    "zoneId": 54,
                    "sensorType": "none"
                },
                {
                    "zoneId": 55,
                    "sensorType": "none"
                },
                {
                    "zoneId": 56,
                    "sensorType": "none"
                },
                {
                    "zoneId": 57,
                    "sensorType": "none"
                },
                {
                    "zoneId": 58,
                    "sensorType": "none"
                },
                {
                    "zoneId": 59,
                    "sensorType": "none"
                },
                {
                    "zoneId": 60,
                    "sensorType": "none"
                },
                {
                    "zoneId": 61,
                    "sensorType": "none"
                },
                {
                    "zoneId": 62,
                    "sensorType": "none"
                },
                {
                    "zoneId": 63,
                    "sensorType": "none"
                },
                {
                    "zoneId": 64,
                    "sensorType": "none"
                },
                {
                    "zoneId": 65,
                    "sensorType": "none"
                },
                {
                    "zoneId": 66,
                    "sensorType": "none"
                },
                {
                    "zoneId": 67,
                    "sensorType": "none"
                },
                {
                    "zoneId": 68,
                    "sensorType": "none"
                },
                {
                    "zoneId": 69,
                    "sensorType": "none"
                },
                {
                    "zoneId": 70,
                    "sensorType": "none"
                },
                {
                    "zoneId": 71,
                    "sensorType": "none"
                },
                {
                    "zoneId": 72,
                    "sensorType": "none"
                },
                {
                    "zoneId": 73,
                    "sensorType": "none"
                },
                {
                    "zoneId": 74,
                    "sensorType": "none"
                },
                {
                    "zoneId": 75,
                    "sensorType": "none"
                },
                {
                    "zoneId": 76,
                    "sensorType": "none"
                },
                {
                    "zoneId": 77,
                    "sensorType": "none"
                },
                {
                    "zoneId": 78,
                    "sensorType": "none"
                },
                {
                    "zoneId": 79,
                    "sensorType": "none"
                },
                {
                    "zoneId": 80,
                    "sensorType": "none"
                },
                {
                    "zoneId": 81,
                    "sensorType": "none"
                },
                {
                    "zoneId": 82,
                    "sensorType": "none"
                },
                {
                    "zoneId": 83,
                    "sensorType": "none"
                },
                {
                    "zoneId": 84,
                    "sensorType": "none"
                },
                {
                    "zoneId": 85,
                    "sensorType": "none"
                },
                {
                    "zoneId": 86,
                    "sensorType": "none"
                },
                {
                    "zoneId": 87,
                    "sensorType": "none"
                },
                {
                    "zoneId": 88,
                    "sensorType": "none"
                },
                {
                    "zoneId": 89,
                    "sensorType": "none"
                },
                {
                    "zoneId": 90,
                    "sensorType": "none"
                }
            ],
            "pushover": {
                "alarms": {
                    "burglary": false,
                    "fire": false,
                    "gas": false,
                    "auxiliary": false,
                    "freeze": false,
                    "water": false,
                    "duress": false,
                    "temperature": false
                },
                "troubles": {
                    "freeze": false,
                    "batterylow": false,
                    "acpower": false,
                    "phoneline": false,
                    "digitalcommunicator": false,
                    "fuse": false
                }
            },
            "mqtt": {
                "showMqttEvents": false

**Screenshots:**
<!-- If applicable, add screenshots to help explain your problem. -->

**Environment:**

* **Plugin Version**:
**1.4.1**

* **Homebridge Version**: <!-- homebridge -V --> HOOBS 3.3.5
* **Node.js Version**:
**14.15.1**
* **NPM Version**: <!-- npm -v -->
* **Operating System**: <!-- Raspbian / Ubuntu / Debian / Windows / macOS / Docker / hb-service -->
**Raspbian**
<!-- Click the "Preview" tab before you submit to ensure the formatting is correct. -->

Hi @Tesla-P100FX,
Do you see these log messages every time you restart Homebridge?
Has it only started since you upgraded to 1.4.1?
Can you supply more of the logs. I'd like to see all the messages from the point that Homebridge is started to when you see the first message about the "read handler"

Hi @Tesla-P100FX,
Do you see these log messages every time you restart Homebridge?
Has it only started since you upgraded to 1.4.1?
Can you supply more of the logs. I'd like to see all the messages from the point that Homebridge is started to when you see the first message about the "read handler"

It's not always associated with starting the service.  It happens at random times.  It has done it since my first install not 1.4.1.   I will send a complete log tomorrow.   Have a nice evening 😷

Here is the complete startup log.  It did not happen in this window of time  but suspect it might later.
5/21/2021, 9:16:03 AM Initializing HAP-NodeJS v0.9.3...
5/21/2021, 9:16:04 AM Loaded plugin 'homebridge-myq'
5/21/2021, 9:16:05 AM [5/21/2021, 9:16:04 AM] Registering platform 'homebridge-myq.myQ'
5/21/2021, 9:16:05 AM Loaded plugin 'homebridge-omnilink-platform'
5/21/2021, 9:16:05 AM [5/21/2021, 9:16:05 AM] Registering platform 'homebridge-omnilink-platform.OmniLinkPlatform'
5/21/2021, 9:16:05 AM [5/21/2021, 9:16:05 AM] The plugin "homebridge-platform-wemo" requires Node.js version of ^14.16.1 which does not satisfy the current Node.js version of v14.15.1.    Have time to give this plugin a review? http://bit.ly/hb-wemo-review
5/21/2021, 9:16:09 AM [myQ] myQ API: Successfully connected to the myQ API.
5/21/2021, 9:16:09 AM [myQ] myQ API: Discovered device family garagedoor: Garage Door (serial number: ************gateway: GW23001A4270).
5/21/2021, 9:16:09 AM [myQ] myQ API: Discovered device family gateway: Hub [Chamberlain Smart Garage Hub] (serial number: GW23001A4270).
5/21/2021, 9:16:09 AM [myQ] Garage Door: Door position sensor detected.         In my own case (a QNAP NAS) I found I was getting warnings from Homebridge when the CPU was running high (90+%). This was caused by another process (not related to Homebridge) which I disabled and have not seen the warnings since. The CPU is normally running at around 10%
You are running a few plugins I noticed so maybe the RPi hardware is struggling. Other than Homebridge is anything else running on your RPi?
You could also try running the plugin in a Child Bridge (which is what I do). Just be aware that if you do this all the HomeKit accessories for the plugin will be removed and then re-added so you may need set up any scenes and automations again.

Sorry I have not followed up.  CPU usage is always super low , do it's not that.   I'll debug tomorrow between meetings

No worries. I think the issue may be that you have a quite a number of units, zones etc.  When HomeKit requests updates for the various accessories the plugin will fetch the current status for each one (one at a time) from the Omni controller. It could be this that's taking too long to respond.
I'm working on a way to reduce these calls to the Omni controller to hopefully help with this issue.
If you do find anything else with your own debugging please let me know.

Thanks for working on an update to solve this.  I will update as soon as it shows up in the Hoobs plug in directory

I just released a new version of the plugin (1.4.3) which may fix the issue. Give it a go and let me know what happens.

Thanks I will as soon as I see it as a package  in Hoobs

Hi @Tesla-P100FX, did you upgrade the plugin? Has it helped at all?

Yes thank you!   I thought I would wait a couple of days to see if it had any errors.  I installed on 5/29 and no errors since then:-)
Thank you!!

That's great news. I'll leave this issue option for now but if I haven't heard anything further from you by next weekend I'll assume its ok and close it


feat(UI): Use Intl.DisplayNames to show the language name

This is causing test failures on Google TV devices, and I think the tests are correct.  For some reason, Intl.DisplayNames is returning garbage for most things on that device.
On Chrome on Linux, en yields English and fr yields français.  On Google TV, en yields en and fr yields fr.  We shouldn't use this if it's unreliable.
I would like to start by reverting this change to make the tests green.  We can follow-up with a change that either excludes Google TV devices or that falls back to the internal map when the output matches the input.


Date Extension (#3)

Add first extension for Date

Current dependencies on/for this PR:

develop

PR #9   👈

This stack of pull requests is managed by Graphite.


Can not use "Maximize" mode of ckeditor in nb-tabset>nb-tab

Hi team,
If I put ckeditor inside nb-tab then the display issue (all style broken) will occur when I click on "Maximize" button.
<nb-card>
      <nb-tabset>
        <nb-tab>
             <ckeditor [config]="{ extraPlugins: 'divarea', height: '320' }"></ckeditor>
        </nb-tab>
      </nb-tabset>
<nb-card>

Please help advice.
Thanks,.

Had the same issue today. Any information ?

I am facing Same issue on maximize button inside nb-tab ,


Private class members cause TS2322 is not assignable to type

Vue version
3.4.29
Link to minimal reproduction
https://play.vuejs.org/#eNp9Ul1r2zAU/St3ekkCmcPYnjwnsJXCNtgHXaEPVSmuc2OrlSUhyW7A+L/3SqqTtJS+Sfeccz/PwL4Zk/UdspwVrrLCeHDoOwOyVPWaM+8423AlWqOthwEucLcEizsYYWd1CzPSzrjiqtLKeWhdDeuAz2c/UEoNV9rK7YfZIlJk6RxcNngWHwNXAMaKvvQIt77B39jeoc3BeStU/TVIAGJe21Ve2/kiaQB8I1x2lFBJzkroS9khZyQEGJPadHdSVFCjD3UTe76YSkzpLE1s1eusU56YKo1HWOp9DQofD6PMF8R9yUCXH+DrG+JfT8jNG1zaah5WWxwlm+c9HkmhSJJqiZnU9QlG2gAXq3RDuhh9PLZG0nLpB1A0nzbDEA80jsWKfjEqlOk89B9bvUVJ9yacM1gRWKxO9GxJTqDSO1Fn904rskvcHWeVbo2QaP8aL6g1zvJpq3QScsDjrxijE+JyilcNVg9vxO/dPsQ4+2fRoe3pmAfMl5aumODz/39wT+8DSN13ktjvgBdIa+tCj4n2vVNbavuEF7v9GY1O3rh053uPyk1DhUajISKfM/L92TujH9v9nH2ZjMTGJ+8PKoI=
Steps to reproduce
Scaffold a new project using npm create vite@latest (Vue and TypeScript)
In the HelloWorld.vue file create the following code:
class TheClass {
private _theMember: string;
constructor() {
this._theMember = "a value";
}
public get TheMember(): string {
return this._theMember;
}
}
const theClass = new TheClass();
const theClasses: TheClass[] = [theClass];
const theClassesRef: Ref<TheClass[]> = ref(theClasses);
the line const theClassesRef: Ref<TheClass[]> = ref(theClasses); causes the error:
error TS2322: Type 'Ref<{ readonly TheMember: string; }[]>' is not assignable to type 'Ref<TheClass[]>'.
Type '{ readonly TheMember: string; }[]' is not assignable to type 'TheClass[]'.
Property '_theMember' is missing in type '{ readonly TheMember: string; }' but required in type 'TheClass'.

What is expected?
There should be no error that the private member is missing.
What is actually happening?
The TS error is unexpected because the class member is marked private.

System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
    Memory: 19.55 GB / 31.94 GB
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (126.0.2592.87)
    Internet Explorer: 11.0.19041.4355

Any additional comments?
No response

Closing as a duplicate of #2981.
As a workaround, see: https://github.com/vuejs/core/issues/2981#issuecomment-1831724017


Web api 2 with api version in url

Hello,
I'm using these nswag packages in a .net 4.6 application (with web api 2)
packages
My api is url versioned (myserver/api/v1/echo?id=test)
I have this configuration for the versioning :
var constraintResolver = new DefaultInlineConstraintResolver()
{
      ConstraintMap =
      {
          ["apiVersion"] = typeof( ApiVersionRouteConstraint )
      }
};

config.MapHttpAttributeRoutes(constraintResolver, new CentralizedPrefixProvider("api/v{version:apiVersion}"));
config.AddApiVersioning(o => o.ReportApiVersions = true);

And my controllers look like this
   [ApiVersion("1.0")]
    public class EchoController : ApiController
    {
        [Route("echo")]
        [NSwag.Annotations.SwaggerTag("System Check")]
        public HttpResponseMessage Get(string id)
        {
            return Request.CreateResponse<string>(id);
        }
    }

I used this for swagger generation (with the WebApiToSwaggerGenerator)
app.UseSwagger(typeof(Startup).Assembly, settings =>
{

});

app.UseSwaggerUi3(typeof(Startup).Assembly, settings =>
{

});

When I generate the swagger file, I don't have the version specified, I only have
  "paths": {
   "/echo": {
      "get": {

instead of
  "paths": {
   "/api/v1/echo": {
      "get": {

I tried to force different routes without any success
app.UseSwagger(typeof(Startup).Assembly, settings =>
{
	settings.GeneratorSettings.DefaultUrlTemplate = "api/v{version:apiVersion}/{controller}/{id}";
});

Could you help figuring out how to configure the version ?

for information:
it's working if I don't use a DefaultDirectRouteProvider to automaticaly add the "api/v{version:apiVersion}" for every route attribute
        [Route("api/v{version:apiVersion}/echo")]
        public HttpResponseMessage Get(string id)
        {
            return Request.CreateResponse<string>(id);
        }

Maybe this has to be solved with a custom operation processor which fixes the paths...


[SPARK-44283][Connect] Move Origin to SQL/API

What changes were proposed in this pull request?
This PR move Origin and SQLQueryContext to sql/api.
Why are the changes needed?
This change allows us to move ParseException to sql/api.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.

cc @amaliujia

LGTM

Merging.


Getting TypeError: eventTypes.includes is not a function

Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.0.2
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
2.0.2
Public or Confidential Client?
Public
Description
Hi Team - I have started seeing the error - TypeError: eventTypes.includes is not a function in the last few days in our test environments, though higher environments does not have this issue.
Error Message
TypeError: a.includes is not a function
at EventHandler.ts:99:36
at Map.forEach ()
at _c.emitEvent (EventHandler.ts:89:33)
at Il.initialize (StandardController.ts:341:27)
at Ol.initialize (PublicClientApplication.ts:95:32)
at index.js:85:6
at f (authentication.js:102:3)
at index.js:17:1
at index.js:158:7
at index.js:158:7
MSAL Logs
There are no MSAL logs in the console
Network Trace (Preferrably Fiddler)

[ ] Sent
[ ] Pending

MSAL Configuration
export const msalConfig = {
    auth: {
        clientId: XXXXXXX,
        authority: `https://login.microsoftonline.com/XXXXXXX`,
        redirectUri: window.location.origin,
        knownAuthorities: ["login.microsoftonline.com"],
        navigateToLoginRequestUrl: true,
        postLogoutRedirectUri: window.location.origin,
    },
    cache: {
        cacheLocation: "sessionStorage", // This configures where your cache will be stored
        storeAuthStateInCookie: false, // Set this to "true" if you are having issues on IE11 or Edge
        secureCookies: true,
        cacheMigrationEnabled: true,
    },
    system: {
        loggerOptions: {
            loggerCallback: (level, message, containsPii) => {
                if (containsPii) {
                    return;
                }
                switch (level) {
                    case LogLevel.Error:
                        console.error(message);
                        return;
                    case LogLevel.Info:
                        console.info(message);
                        return;
                    case LogLevel.Verbose:
                        console.debug(message);
                        return;
                    case LogLevel.Warning:
                        console.warn(message);
                        return;
                    default:
                        return;
                }
            }
        }
    }
};

Relevant Code Snippets
msalInstance
        .initialize()
        .then((res) => {
          // handle auth redirect/do all initial setup for msal
          msalInstance
            .handleRedirectPromise()
            .then((authResult) => {
              // redirect anonymous user to login page
              msalInstance.loginRedirect();
              const accounts = msalInstance.getAllAccounts();
              msalInstance.setActiveAccount(accounts[0]);
            })
            .catch((err) => {
              console.log(err);
            });
        })
        .catch((err) => {
          console.log(err);
        });

Reproduction Steps
I see a blank screen instead of the login screen when navigating to the app url
Expected Behavior
The login page should be displayed when there is no active account or The App Home page should be displayed when there is an active account.
Identity Provider
Entra ID (formerly Azure AD) / MSA
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge
Regression
"@azure/msal-browser": "3.0.2"

same issue here, didn't do any MSAL upgrades but it just started happening

Same issue.


IOS should pass credentials to webapp via service worker

When adding app to homescreen on ios, when opening the webapp the user is not logged in to his wallet because on ios storage is not shared between safari and webapp.
The only way to solve it is via service worker cache.
https://www.netguru.com/codestories/how-to-share-session-cookie-or-state-between-pwa-in-standalone-mode-and-safari-on-ios

add the code from step 1 to sw-dev.js to test it locally
verify in console step 2 + step2 to add and fetch token from cache
when we show the add to home popup on ios push the mnemonic to cache
in app when we do serviceWorker.register(config) use the config callback (see serviceWorker.js) to:

check if ios fullscreen mode
check if no mnemonic in localstorage
fetch mnemonic from cache and set it in localstorage (+ need to set isloggedin, see how recover is done)

Definition of Done

[ ] user is logged in on IOS webapp automatically after adding to home screen

no possible solutions at the moment

there's no current way to do that.. closing


Highlight wrong keyword on matching string

If the same keyword came before the current parameter's name such as string $foo, string $string
first matching keyword is highlighted (string before $foo in above example)

... string $string, ...  is never highlighted

what PHP lsp you are using?

Sorry I wasn't very detailed.
I'm using Nvim 0.5 with ALE and Compe
And phpactor as the PHP language server

PHP variable starting character "$" might be the reason. Because it breaks the signature window too.
Basically as soon as I put $, the windows just disappears.
As the screenshots show, $ char is not even highlighted. So matching pattern probably just ignores it.

My codes should have cover '$'. But I need to test it.

I tried but phpactor failed to work. I got a 255 error.
I also tested intelephense, it works correctly with $
Please enable the logs by:
  require "lsp_signature".setup({
            log_path = "/your_log_path/sig.log",
            debug = true,
  })

And attach the logs sig.log

I'll try to in the first opportunity.

I'm not sure if this is related, but using Neovim's builtin client and the Jedi language server, I've noticed a similar problem with Python. When the name of the argument appears elsewhere earlier in the signature, the highlight is in the wrong place.

Whereas if the argument's name doesn't appear anywhere else before it, it works as expected.


feat: add dev package release from new develop branch

Since we need to use this repo again for RPC and runtime calls, I created a develop branch as the default which mirrors what we do in the SDK and in the node repos. The goal is that of having a master branch of types that can be used by the master branch of the SDK and that work with the master (or latest released) version of the chain. Similarly, the develop branch must be compatible with the SDK and node develop branches.
This PR introduces a GH action that pushes dev packages whenever something is pushed to the develop branch, very similarly to what we do for the SDK.

Closing as this repo has been merged in the SDK monorepo as part of https://github.com/KILTprotocol/sdk-js/pull/658.


Better audio timestamp support

Currently audio timestamps are averaged based on the number of chunks in the audio stream.  This generally works pretty well if the audio is muxed with a consistent time frame.  It may have issues in the future.  With PCM and possibly others, it should be possible to produce highly accurate timestamps based on the chunk size.

https://github.com/dburckh/ExoPlayer/issues/10 is closely related to this topic as code described above could be used to correct problems caused by poorly muxed streams.

This issue is partially addressed with the addition of the MpegAudioStreamHandler.  However this is only part of the problem.
They complete fix is documented here.  https://github.com/dburckh/Media3Avi/issues/1


[Bug] HEAD breaks pc-relative maths compared to v0.3.6 release

Instruction (source):
_06D2:
    jp @ + 2

v0.3.6 behavior:
C3 D5 06 ; intended

HEAD beahvior:
C3 D4 06 ; branch ends 1 byte early

How is @ = $06d3 intended? That makes no sense; the HEAD behavior seems reasonable.

Yes, it doesn't make sense, that's the correct behaviour.

JP is s 3 byte instruction.

Hopefully this new release 0.3.7 will fix the mess caused by the bug of version 0.3.6.


question here

https://github.com/drofphilosophe/USElecData/blob/ef18a2f4986708677f49509d8e42a1b7968a0eea/src/EPA-CEMS/loadCEMSData.R#L802
flagging to ask your goal with the monthly file. also flagging that when i run this file i miss years 2001-2021. looking into this on my end but reminder to discuss monday.

The monthly file was not being created when there was no pre-existing data.


(maint) synced file(s) with chocolatey/.github

synced local file(s) with chocolatey/.github.

Changed files

synced local directory .github/ISSUE_TEMPLATE/ with remote directory .github/ISSUE_TEMPLATE/

This PR was created automatically by the repo-file-sync-action workflow run #7961483646

:tada: This issue has been resolved in version 0.2.0 :tada:
The release is available on:

GitHub Release
Chocolatey Package

Your GitReleaseManager bot :package: :rocket:


GoogleAppMeasurementWithoutAdIdSupport.xcframework has an incorrect or unknown format

Disabling Ad Id Support with the following code results in the error GoogleAppMeasurementWithoutAdIdSupport.xcframework has an incorrect or unknown format
<PropertyGroup>
  <FirebaseWithoutAdIdSupport>True</FirebaseWithoutAdIdSupport>
</PropertyGroup>

Xamarin.Firebase.iOS.Analytics: 8.10.0
Visual Studio for Mac: 8.10.19 (Build 2)
Xamarin.iOS: <IP_ADDRESS>

Sample.zip

It looks like there were name changes in version 8.8.0  of the Firebase SDK:

AdIdSupport was changed from GoogleAppMeasurement.xcframework to GoogleAppMeasurementIdentitySupport.xcframework
WithoutAdIdSupport was changed from GoogleAppMeasurementWithoutAdIdSupport.xcframework to GoogleAppMeasurement.xcframework


Instructor can't add a project to his own course

Describe the bug
When I login as an instructor I can't add a project to a course that I am the instructor for.
To Reproduce
Steps to reproduce the behavior:

Login into the system as an instructor and navigate to courses tab
Click on a course that you are an instructor for or click to create a course with the + button to create course
Then from this screen there should be a plus button to add a project to the course and it will say "not authorized" (we need to fix that)

Expected behavior
As an instructor I should be able to add projects to my own courses.

Solved as of 75ef4e396c21285ae8f95dfe4c82939d37b53dbb


card: actionBarVisible doesn't lock action bar visible

Bug
Expected behavior

Add this boolean prop, see action bar all the time

Actual behavior

Still only visible on hover/focus, as default

Steps to repro
Observable in last card in this example https://design-system.pluralsight.com/components/card/#in-app-example

Verified working. Done.


Cannot use it inside UITableViewCell

I needed to use it inside UITableViewCell and it wasn't working, because my view controller had to implement UITableViewDelegate also, in which case PTETableViewDelegate methods stopped working.

I think your controller can be both a UITableViewDelegate and a PTETableViewDelegate as the method names don't conflict.
Otherwise you could try making directly the cell a PTETableViewDelegate.


Use certificate validFrom and validTo vs. cert order

Fixes #655
To test, create a cert on dev, and it should be way in the future vs. tomorrow:

Confirmed on staging:

Thanks for the reviews @SerpentBytes, @Eakam1007!


tag created vmare VMs

tag VMs with 'gitlba-ci-test' images so they can get removed with
cloud cleaner
This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

Rebased to fix CI.


Fix version typo by dependabot

/dobby version patch

Sorry I thought there's a typo but its all good.


Create test.php

/close
There is nothing in this PR and the kubernetes website does not use PHP


[#170953174] Make OmbuLabs blog accessible: screen reader compatibility

Pivotal ticket reference: https://www.pivotaltracker.com/story/show/170953174
This PR:

Improves accessibility for Screen Readers adding landmarks, aria attributes, etc.

Here are the videos, @ABizzinotto
https://ombulabs.slack.com/files/UEY0DCHH9/FTS01HEVD/blog-home.mov
https://ombulabs.slack.com/files/UEY0DCHH9/FTCKQTT8T/blog-index.mov
https://ombulabs.slack.com/files/UEY0DCHH9/FTQ430V8Q/blog-pagination.mov
https://ombulabs.slack.com/files/UEY0DCHH9/FTQ430V6U/blog-post-author.mov
https://ombulabs.slack.com/files/UEY0DCHH9/FTBAAHML2/blog-post-tags.mov

@nykka videos look good. Can you look into this test failure though? Thanks!


Draw the omage to vicious1.

Yeah, since I can't do arcs, it has quite a few points to define it. I'm assuming estlcam does something smart with resolution, but I want the shapes "normalized", but I can't drop the resolution, someone might still want to draw one 500mmx500mm.


Running specified suite by pattern broken

Have updated from version 14 to 17. Running specified suite by pattern seems broken.
Want to run DataTable.test.js:
npm test DataTable

runs all suites in project
npm test DataTable.test

runs all suites in same directory and it subdirectories
npm test DataTable.test.js

only this runs desirable test suite
All this worked correctly in jest 14
Running with directory patterns works ok:
npm test /datat

runs all suites in /datatable
configuration:
"jest": {
    "testRegex": ".*.test.js",
    "coverageThreshold": {
      "global": {
        "branches": 50,
        "functions": 80,
        "lines": 60,
        "statements": 50
      }
    },
    "moduleNameMapper": {
      "\\.(css|less)$": "identity-obj-proxy"
    }
  }

Can you explain what exactly doesn't work any more now?

Cannot run specific suite by pattern (e.g. part of name), need to specify full name:
npm test DataTable.test.js instead of npm test DataTable

I cannot repro. Please try and clone the Jest repo and run these:

npm run test "has.*map"
npm run test haste-map
npm run test packages/jest-haste-map/src/__tests__/index-test.js

they will all run the appropriate tests.


feat: improve the response time of (ebrains) features

supercedes #61
After discussion, this is a simplified, but equally effective:
--- preheat-1:<PHONE_NUMBER>9363708 seconds ---
--- preheat0:<PHONE_NUMBER>1216125 seconds ---
--- preheat1: 0.36009788513183594 seconds ---
--- with preheat again: 0.3659327030181885 seconds ---

@dickscheid @marcenko can you please take a look at the rework of the PR
The performance is not as quick (0.4sec vs 0.01sec), but already a great improvement. The benefit is that change of repo is minimal, and should be more readable.

Marked as draft for now. Found a bug. Well provide a fix, then mark as ready.

Marked as draft for now. Found a bug, will provide a fix today. Will mark as ready when done.

The failing test is (indirectly) due to the errornous implementation of the connectivity profile (and potentially connectivity matrix)
I will raise a separate PR to fix that issue. Only when the tests passes, I will open this PR for review.


Fix inkscape extensions

Description of changes

Fix inkscape manage extensions #197044
Update hexmap extension

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 258885 run on x86_64-linux 1

3 packages marked as broken and skipped:

hackneyed
spring
springLobby

42 packages built:

adapta-gtk-theme
arc-theme
arx-libertatis
asciidoc-full
asciidoc-full-with-plugins
asciidoc-full-with-plugins.dist
asciidoc-full.dist
ayu-theme-gtk
capitaine-cursors
cinnamon.cinnamon-screensaver
cinnamon.iso-flags-png-320x420
cinnamon.iso-flags-svg
clevis
clevis.man
coreboot-configurator
dblatexFull
disorderfs
emojione
fim
hikounomizu
inkscape
inkscape-extensions.hexmap
inkscape-with-extensions
iso-flags
k40-whisperer
kabeljau
rep (kakounePlugins.rep)
luksmeta
mate.mate-utils
mojave-gtk-theme
numix-cursor-theme
numix-solarized-gtk-theme
plata-theme
pop-gtk-theme
python310Packages.diagrams
python310Packages.diagrams.dist
python311Packages.diagrams
python311Packages.diagrams.dist
tang
tang.man
volantes-cursors
wpa_supplicant_gui

Could you please check if filelock is still needed in 1.3? IIRC I did not see any references in the source code: https://github.com/NixOS/nixpkgs/pull/245431#discussion_r1313824049

Filelock is listed as a dep for the Inkscape extension manager and introduced here.

Turns out it is an optional runtime dependency for cachecontrol.


Fix vulnerability dependency

in order to fix the ms vulnerability we should consider to update the finalhandler dependency

Coverage increased (+0.04%) to 93.316% when pulling 7bb7c1396d773536fa62ed1e2938800b8f3c29b7 on tobiaslins:fix-vulnerability-dependency into 41982c13519efafde9586f6de5df8b75ac57831f on vpulim:master.

Coverage remained the same at 93.273% when pulling 7bb7c1396d773536fa62ed1e2938800b8f3c29b7 on tobiaslins:fix-vulnerability-dependency into 41982c13519efafde9586f6de5df8b75ac57831f on vpulim:master.

works for me!  thanks!


Change DropTableDoesExist method and DropTypeDoesExist method in test cases

Purpose
$title
Examples
Checklist

[ ] Linked to an issue
[ ] Updated the changelog
[ ] Added tests

Closing this PR to send a another PR. https://github.com/ballerina-platform/module-ballerinax-oracledb/pull/15


Fails in PR with "TypeError: Cannot read properties of undefined (reading 'split')"

I have a PR in a project, where the action suddenly fails with the following error message:

Error: TypeError: Cannot read properties of undefined (reading 'split')

All other PRs work, also with the same version of the action.
In debug mode also no helpful information is printed. I only see the resolved path of the XML file before the action dies.

Hi, I have the same issue - any version of it that works for you ?

I updated the jacoco-report version from 1.6 to 1.6.1.  Fix it.


Update python-packages.csv - display name (Azure AI Search)

Display name updates for Azure AI Search, formerly known as Cognitive Search.

#sign-off

/azp run azure-sdk - ci


Fix windows setup

Makes npm run build windows safe

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: ncordon:x: anderson4jYou have signed the CLA already but the status is still pending? Let us recheck it.


react-router-redux sync history with store broke navigation through dispatched actions

using react-router-redux push to change url through redux while wrapping history (browserHistory) with syncHistoryWithStore doesn't work.
the problem arises because the syncHistoryWithStore returns a new history object, therefore the history used for creating the redux store (in routerMiddleware) does not match with the one used in the routing (this one has a dependency to the store: syncHistoryWithStore(browserHistory, store)
Example:
// history.js
import { createBrowserHistory } from 'history';
export defaulr createBrowserHistory();

// store.js
import { routerReducer, routerMiddleware } from 'react-router-redux';
import { createStore, applyMiddleware, combineReducers } from 'react-redux'
import browserHistory from './history';

const store = createStore(
    combineReducers({
        // ...reducers,
        routing: routerReducer
    }),
    applyMiddleware(
      // ...middlewares,
      routerMiddleware(browserHistory)
    )
  );

export default store;

// routes.js
import { syncHistoryWithStore, push }  from 'react-router-redux';
import { Router, Switch, Route } from 'react-router-dom';
import { Provider } from 'react-redux';
import history from './history';
import store from './store';

const browserHistory = syncHistoryWithStore(history, store); // sync func. returns new instance of `history`
browserHistory.listen(location => console.info('-> location:', location));

const Store = (
   	<Provider store={store}>
		<Router history={browserHistory}>
			<Switch>
				<Route exact path="/" component={Home} />
				<Route path="/about" component={About} />
			</Switch>
		</Router>
	</Provider>
);

// render to dom...

// expected result: the browser renders the /About page
store.dispatch(push('/about'));
// but, the previous line only changes the url
// not the store, neither the component tree

A solution for this issue could be found in this fork
The commit change here
note: simplified example in codepen (using hash history)

Don't create your store in store.js, just export a function that takes a history as an argument and creates the store using it.


Removing unused external test dependencies and adding third party notice

Assuming all tests still pass after removing those references then :+1: .

The tests do pass on my box!


Add test case showing incorrect behaviour

This should just generate a simple div tag containing a single block.  Instead it has a block with another block in it.  Not sure why thats happening.

I think this is because parseText sometimes returns a block, but sometimes returns a single element.  It does this depending on how many tokens it returns, rather than on the block option it's passed.  The block option just determines whether newlines are allowed.  I think we should rename that method, then have it always return a block.  This block can then be flattened (if appropriate) at the next level up.

Unfortunately that is true. I submitted that specific code change and didn't do anything about it since code-gen was happy with it. Technically nothing in the AST spec prevents a Block from being a child of another Block but I agree that it's not GOOD either way.
Also the empty dot block syntax suffers(ed?) from the same problem.


See if Tracker can announce how many Hyper Beam shots Mother Brain needed

It might be fun if Tracker could say how many Hyper Beam shots it took to finish off Mother Brain when she announces the defeat, if it's fewer shots than it would have taken if the player didn't do the stand-up glitch. The number of shots should be equal to MB's health when Hyper Beam is enabled, divided by the damage each shot does.
We probably can't have the C# code retrieve MB's health value reliably while the player is still shoooting charged shots around, but we could potentially hijack the code that enables the Hyper Beam and have it copy MB's health value to a safe RAM location that we could then read at our leisure.
That subroutine lives here: https://patrickjohnston.org/bank/91#fE5F0

Looks like RAM address $7E0FCC is set to 0x8CA0 (36,000) when the Baby detaches from MB. Hyper Beam damage is 1,000.


@bind-Value doesn't working in SSR form submit (POST)

In SSR form submit post method, built-in input component's name attribute automatically is set by Blazor engine. In below example:
<InputText @bind-Value="Model.Email" Placeholder="Enter your email" />
The rendered html will be:
<input placeholder="Enter your email" name="Model.Email" class="valid"<EMAIL_ADDRESS>The values will be set on the server for the Model.
But, in our component library the rendered result is:
<input placeholder="Enter your email" name="Value" class="valid"<EMAIL_ADDRESS>And, SSR form won't be work.

I have created a sample component inheriting built-in InputText component:
InputTest.razor
@inherits InputText

Test

@{
    base.BuildRenderTree(__builder);
}

And I used the component in setup page:
    <PluginForm Model="@Model" OnSubmit="OnSubmit" Name="@FORM_NAME" Title="@($"Welcome To FluentCMS {Model.Username}")">
        **<InputTest @bind-Value="Model.Username" Placeholder="Enter your username" />**
        <InputText @bind-Value="Model.Email" Placeholder="Enter your email" />
        <InputText @bind-Value="Model.Password" Placeholder="Enter your password" type="password" />
        <InputText @bind-Value="Model.AppTemplateName" />
        <InputText @bind-Value="Model.SiteTemplateName" />
        <InputText @bind-Value="Model.AdminDomain" />
        <PluginFormActions>
            <Button Block="true"  Color="Color.Primary" Type="ButtonType.Submit">
                Setup
            </Button>
        </PluginFormActions>
    </PluginForm>

The above code is working fine, I think there is a bug in our input components.

Let's consider extending Microsoft's InputBase instead of creating our own implementation.
https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.inputbase-1?view=aspnetcore-8.0
I believe InputText is a good reference for its implementation.
https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.inputtext?view=aspnetcore-8.0
https://github.com/dotnet/aspnetcore/blob/3f1acb59718cadf111a0a796681e3d3509bb3381/src/Components/Web/src/Forms/InputText.cs


Update PortoutModel.php

Add missing fields to PortOuts

Hey Andrew,
Thanks for this contribution! Let me check with the dev on our team who built our deploy pipeline before merging this, we are modifying the process and I want to make sure this will deploy successfully.
He is back next week after New Years

@ajrice6713 Hey AJ!
We've actually talked a couple of times over support. Anyways everything you've said is all good. I've already extended the class to add what I wanted for now, which leads me to my next quick question if you have the time. Why are all classes in this API final, for my 'extend' I simply just recreated the file but if I could extend it it would have been much easier.

@tm1000 Hey Andrew!
Great question on the final classes - this is an older SDK that was written by someone who doesn't work at Bandwidth anymore - so as for the 'why' they are all final classes, I couldn't tell you.
We are working on a new IRIS SDK that will be auto generated from our OpenAPI spec, we are closing in on the final stages and hope to have something released in Q1. This new SDK shouldn't utilize final classes, and when the team at bandwidth that manages the IRIS API publishes a new spec with any changed fields, the SDK will be automatically updated to match when they publish their updated API spec - hopefully resolving issues like this one in the future.

@tm1000 Hey Andrew!
Great question on the final classes - this is an older SDK that was written by someone who doesn't work at Bandwidth anymore - so as for the 'why' they are all final classes, I couldn't tell you.
We are working on a new IRIS SDK that will be auto generated from our OpenAPI spec, we are closing in on the final stages and hope to have something released in Q1. This new SDK shouldn't utilize final classes, and when the team at bandwidth that manages the IRIS API publishes a new spec with any changed fields, the SDK will be automatically updated to match when they publish their updated API spec - hopefully resolving issues like this one in the future.

Thanks for the explanation AJ! Looking forward to the updates coming up!

Thanks for the explanation AJ! Looking forward to the updates coming up!


HTML result has disabled attribute hard coded on the checkbox input

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions
<EMAIL_ADDRESS>Link to runnable example
No response
Steps to reproduce
Process:
import parse from 'remark-parse';
import gfm from 'remark-gfm';
import toHTML from 'remark-html';

unified()
.use(parse)
.use(gfm)
.use(toHTML)
.process(`
- [] foo
`);

Expected behavior
<input type="checkbox">

Actual behavior
<input type="checkbox" disabled="">

Checkbox is disabled due to this hard coded line: https://github.com/micromark/micromark-extension-gfm-task-list-item/blob/main/dev/lib/html.js#L17
Maybe it can be configured somehow, to opt-out of the disabled default?
Runtime
Node v16
Package manager
No response
OS
macOS
Build and bundle tools
No response

And then? You’d still need to do other things to make a form. What’s your use case?

If you can add event listeners, then you can also remove attributes indeed!
You should then also add names to each checkbox. And likely wrap in a form (or associate a form otherwise). Depends on where you want to store this info.

Sure. But may I ask why the default state is disabled: true?

It is set in the standard https://github.github.com/gfm/#task-list-items-extension-
The reason behind that markdown is a static document.
Input is interactive, it requires additional scripts, backend, and html context which isn't part of the markdown standard.

It is set in the standard

Hm, no, it's not set. On the contrary, the spec literally has a paragraph saying that implementors are free to do whatever with the disabled prop:

This spec does not define how the checkbox elements are interacted with: in practice, implementors are free to render the checkboxes as disabled or inmutable elements, or they may dynamically handle dynamic interactions (i.e. checking, unchecking) in the final rendered document.

Use your listening ears @brookback 😉
The standard offers two options.
Micromark is not a full stack platform it is a static and immutable document rendered.
So we offer the static and immutable disabled.
If you want to make it dynamic consider using one of our higher level packages like https://github.com/remarkjs/react-markdown
Which allows you to customize this.

I didn't want to come off as pushy, sorry if so. Just asking since I want to understand the goals and reasoning, and I felt your initial comments weren't exhaustive.
Thanks so much for your time!

(my use case is that we use Remark on the server and pass the rendered HTML to the client. Thus, I don't use the React package linked. I still want client interactions on that rendered HTML though. So it's sort of an in between the chairs of the "immutable document" and "dynamic React component" worlds).

If you use remark, then the HTML part of this project isn't used! Instead, these props are defined in mdast-util-to-hast.
With hast, there are trees, which could be changed.
But it all kinda depends on what you're doing. Should every user be able to modify markdown? Should their interactions be stored in a database to their account or in local storage?
To do all of that you'd more than just the disabled prop. Client side JS, or transforming the tree, adding more info like names and forms.
So I don't think it's sensible to do just that

my use case is that we use Remark on the server and pass the rendered HTML to the client. Thus, I don't use the React package linked.

The package linked can work server side, but lower level remark packages work too!

So it's sort of an in between the chairs of the "immutable document" and "dynamic React component" worlds

It's also possible with the lower level packages.
remark focuses purely on markdown representation, but to render you're likely passing through rehype, which handles HMTL https://unifiedjs.com/learn/
rehype supports plugins, which allows defaults to be changed.
import type { Root } from 'hast';
import { visit } from 'unist-util-visit';

export function rehypeEnableCheckbox() {
  return function checkboxTransform(tree: Root) {
    visit(tree, 'element', (node) => {
      if (node.tagName === 'input' && node.properties.type === 'checkbox') {
        node.properties.disabled = false;
      }
    });
  };
}

runnable example https://stackblitz.com/edit/github-zqnym5?file=src%2Fmain.ts

@ChristianMurphy Huge thanks for the explanation! I use remark-html as a shortcut, but I see now how it's useful to drop down to the Rehype plugins separately :) I tried something like your transformer plugin, but gave up when setting disabled didn't work (due to me not using the plugin properly).
🙏🙏🙏


Updated Agentic RAG recipe

What does this PR do?

Fixes #231.
I've tested the notebook with these changes and the final results changed a little:

I know that the output should go in the opposite direction and that the final results may vary but it still looks a bit off to me. What do you think?
cc @aymeric-roucher
Who can review?
@merveenoyan and @stevhliu.

The contrast between results looks strange... i've updated the scores and still get much higher score for agentic rag (although with Qwen-2.5-72B for both the agent and the standard RAG)

Anyway, thank you for the updates with the login, let's merge this and add my change to Qwen 2.5 on top in a later PR!


engine: move raft engine purge job to a dedicated thread

Signed-off-by: tabokie<EMAIL_ADDRESS>What problem does this PR solve?
Issue Number: ref #11119
Problem Summary:
purge_expired_files could be time-consuming, e.g. a screenshot of TiKV nodes with 20K+ regions

What is changed and how it works?
What's Changed:
Move purge to a dedicated worker, and also implement batch_gc for raft-engine for better GC performance.
Related changes
Check List
Tests

Unit test

Release note
None

/merge

/run-test