Very slow rendering of my "big" (not really) stage. Please help me figure it out.

(Sorry for asking this here, but the forum is as annoying as most forums and doesn't let me post. Why doesn't Github have an exact copy of "issues" but for tech support anyway?)
For the last week, I've been trying to move from Canvas 2D to WebGL for my game due to the fascinating sluggishness of the former, and the amazing speediness of the latter. To make a long story short, I've arrived at a final solution that should work for me, but currently doesn't.
_Important: what I have technically works exactly as intended, in every regard, except for the rendering speed. It's even slower than Canvas 2D currently, which can only mean that I have done something horribly, HORRIBLY wrong._
I've looked through my code 10 times now and can't find anything obvious. It seems to me that it should be very fast.
Note: I'm well aware of the fact that I have no "culling" routine yet. However, the entire world map is so small, that it barely covers a few screens. Also, I'm gonna have a feature where the user can zoom out to see the whole world at once anyway, so I can't really do culling most of the time.
Either case, the culling is not the problem here. The problem must be something I'm confused about, because again, this is even slower than Canvas 2D. I'm 100% convinced that this is not due to WebGL or Pixi.js, but due to some error of mine. Can you help me find and fix it?
I cannot make a working example due to the complexity of my project, but I did spend significant time creating this minimal example with real code but which doesn't actually run as a program. It contains all the relevant parts and shows exactly what I'm doing for all the relevant parts.
CPU usage: 24-33%. GPU usage: 14-33%. OS: Windows 8.1 Update 1. Latest stable Chromium. WebGL confirmed to work. Very fast and beefy computer. Very slow perceived rendering of my world. As in, Mario Paint on the SNES kind of rendering. Almost.
The code:
var renderer = new PIXI.WebGLRenderer(800, 600); // This is set the size of the screen when resized.

var stage = new PIXI.Stage(); // Important note to self: Stage objects are for some reason special and cannot be modified! Only use for a "wrapper" of sorts, and remember to render() it, but otherwise, do everything to "root" instead of stage!
var root = new PIXI.DisplayObjectContainer(); // root is the real stage, which can be modified in all kinds of ways, unlike stupid Stage.
stage.addChild(root);

function doThisOnceToSetTheGameUp()
{
    for (var i = 0; i < mapLayers.length; i++)
    {
        var theLayer = new PIXI.DisplayObjectContainer();

        for (var x = 0; x < (WORLD_WIDTH_IN_TILES * TILE_SIZE); x += TILE_SIZE)
        {
            for (var y = 0; y < (WORLD_HEIGHT_IN_TILES * TILE_SIZE); y += TILE_SIZE)
            {
                var theTileSprite = new PIXI.Sprite(/* complicated calculation that works; it just grabs the correct texture from the world map */);
                theTileSprite.position.x = x;
                theTileSprite.position.y = y;
                theTileSprite.layer = i;
                theLayer.addChild(theTileSprite);
                screenTiles.push(theTileSprite);
            }
        }

        root.addChild(theLayer);
    }
}

function drawStuffWhenAnimationFrameIsGiven()
{
    root.position.x = -cameraX;
    root.position.y = -cameraY;

    renderer.render(stage); // Since stage is rendered, root is rendered, thus each of the layers, thus all the sprites in each layer.
    requestAnimationFrame(drawStuffWhenAnimationFrameIsGiven);
}

Edit: Added code markdown styles.

Have a similar Problem, but depends on the Browser. Chrome x64 on Ubuntu 16.04 runs like silk with +30fps.
Firefox on same Machine behaves like a total failure and displays nothing with far below 1fps.
http://jsfiddle.net/nikkikoole/tq13caus/3/

@steffomix possibly Ubuntu related - firefox & chrome both +30fps on my win10 box

@NikkiKoole ,
Could you suggest me a good lib to visualize a large amount of data as a network in browser with binding events for nodes, edges and a view ( like rightclick, drag node, drag view, zoom, multiple select and text labels for nodes and edges).
I`ve tested cytoscape.js, vis.js, sigma.js.
Cytoscape.js animate smoothly up to 3k nodes and 5k edges.
Vis a little bit less than Cytoscape.js
Sigma visualize and animate smoothly up to 5k nodes and 8k edges.
(10k * 10k is too laggy for Sigma)
Sigma is the best choice but it`s still not enough performance for such large network.
Need more or equal to 10k nodes and 10k edges to animate them smoothly on changing layout from random position to circle for example or other type of layout
Does it a good idea to use PIXI for example?
Thanks in advance


Create new external compactions admin utility

Create a few options for external compactions
Create new RPC calls for cancelling an external compaction
Closes #2386

I was thinking of adding a thrift method to the CompactionCoordinator called cancel() that will call cancel on the appropriate compactor.

Would this address #2386?

I was thinking of adding a thrift method to the CompactionCoordinator called cancel() that will call cancel on the appropriate compactor.

Would this address #2386?

Yup, that is the plan. I couldn't find a good way for the user to cancel the compaction so I made this external compactions admin utility.

I think this PR is ready for review. This creates the admin tool for external compactions but only with useful commands that currently work. I added RPCs for cancelling but have some ideas for a follow on task to provide more command and control.

This looks correct. Just one comment about API security check.

FYI @dlmarion I made some improvements in 4c78355 based on your comments. I just wanted to give you a heads up since you already approved this PR.

Changes LGTM.


How do you check if Apache 2.4.6 is compatible with RHEL 8 and RHEL 9?  i Have currently RHEL 7 with latest package Apache 2.4.6.

Before asking

[X] I have read the How to ask for help (我已阅读如何寻求帮助指引文档).

Your environment
currently OS version on server : RHEL 7
currently httpd version on serve:Apche 2.4.6
Describe your questions
Now RHEL 7 is going to out of support So Team wanted to upgrade to RHEL 7 To RHEL 8 and RHEL 9.
So we have reverse proxy server with OS RHEL 7 and Apache 2.4.6.
question is is Apache 2.4.6 is compatible with RHEL 9? IF not then what is next step if we need to move RHEL 9.
Eureka service list

eg:
Some logs info or acctch file
no logs

提供最新版DataSphereStudio全家桶安装服务。
包括（DataSphereStudio, Linkis, Exchangeis(Datax, Sqoop), Scriptis, Streamis(Flink), Visualis, DolphinScheduler)

另外包含 元数据，数据安全，数据质量，数据血缘。（这些都是DataSphereStudio不自带的服务）
包含hadoop集群搭建（hive, spark, flink, kafak, kylin）
提供上述所有系统二次定制开发服务
提供系统搭建运维疑难问题解决

添加备注，DSS大数据
持续为DataSphereStudio开源贡献力量


i18n Support

Please excuse some double commits, but it seems like a rebase did go wrong. We doublechecked to make sure every String is translateable, please tell us if we missed a String. There is also a sample translation added that just adds RS_ to every string. Users are able to change the language in the options.
I will also try and create a German translation as soon as this is merged into master. intnick will probably make a Serbian translation.

@lyoshenka might want to take a look at this one too

Please make sure to ping me once the few remaining minor changes are made -- I'll put this in master than so we stop generating conflicts with ongoing work.

Please make the changes discussed in Slack.

Changes should be made, but please review carefully


Pretraining Task MLM task/Itm class task error

Hey guys,
I'm not sure if this is intentional or an error but I thought I'd share my exploration in case it was useful.
If it's an error it would be useful for you and others to know
if it's NOT an error I'd be interested to understand the reasoning
I believe there is a mistake in the pretraining code shared.
Specifically, I believe the MLM task is incorrectly asked to predict masked words for negative examples for a given image in a batch. This can be seen firstly in the ClipForPretraining model: https://github.com/jayleicn/ClipBERT/blob/main/src/modeling/modeling.py#L287
and also the pretraining code:
https://github.com/jayleicn/ClipBERT/blob/main/src/pretrain/run_pretrain.py#L386
Where no attempt is made to distinguish between batch entires which are negatives and positive for the itm_loss.
The result of this is that the mlm_loss is calculated on text entires which are completely unrelated to the visual entries they are paired with.
The result is that, for the pretraining MLM task, the model cannot rely on information from the visual part to guess the masked textual tokens (as this information is a random unrelated image roughly half the time). I don't believe this was your intention, at least in other related work such as the UNITER which in section 3.2 phrases their MLM task as using both the textual and visual parts to predict masked words.
This shouldn't be a catastrophic issue for two reasons:

no loss is suffered for the visual parts in the mlm task
the itm task will still create a correspondence between the visual and text parts

Which is why your pretrainer still does something interesting. But probably correcting this bug should produce even better representations.

Hey @sinjax,
Thanks for your looking into our codebase! We leave it as such intentionally, hoping the model could figure out whether it should utilize visual input or not by itself. We did not carefully verify this hypothesis. I totally agree with you that it is probably a better idea to only do MLM for positive pairs, but there is no concrete evidence yet, it would be interesting to investigate this. Definitely let us know if you have some findings on this topic! Thanks!
Best,
Jie


Add @Generated annotation to ease configuring tools for static code analysis

Reason/Context
Please try answering few of those questions

Why we need this improvement?
Many comnpanies run static code analysis tools to check code quality. Usually is good to have the @Generated annotation to programmatically exclude automatically generated code that could not be complaiant, despite still safe to be used.

How will this change help?
Many tools can be configured to exclude classes annotated with https://docs.oracle.com/javase/8/docs/api/javax/annotation/Generated.html

What is the motivation?
See previous answers

Description
Please try answering few of those questions

What changes have to be introduced?
Add to any generated class the @Generated annotation

Will this be a breaking change?
I feel not as that package should always be in the classpath in a spring boot project as far as I thing

How could it be implemented/designed?
In the current template classes, add the @Generated annotation

@jbiscella your feed back for PR #323 are welcome.


Example of using subscriptions with Vapor

Has anyone tried this?  I assume we have to use Vapor's websocket API.  Is that correct?

Yes, I'm doing it successfully. Here's a quick example of how you can do it:
func routes(_ app: Application, apiBuilder: OpenAPIBuilder) throws {
    routes.webSocket(
        "graphqlSubscribe",
        shouldUpgrade: { request in
            negotiateWebSocketSubProtocol(req: request)
        },
        onUpgrade: { request, websocket in
            context = Context(db: app.db)
            request.graphQLSubscribe(
                websocket: websocket,
                on: self.api,
                auth: { authToken in
                    try request.jwt.verify(authToken, as: UserToken.self)
                }
            )
        }
    )
}

I ended up using a library called Pioneer that hides away some of the GraphiQL, websocket, and other hosting logic.  It also has a bunch of extensions to make Graphiti have async await support and even the subscriptions are asyncstreams too.
https://github.com/d-exclaimation/pioneer


Small improvements for cmake presets

Scope & Purpose
Small improvements for cmake presets

turn off jemalloc for ASan/UBSan builds, because no other memory allocator should be used with ASan

use the same ASan/UBSan options as we currently do in Oskar (they were recently changed there)

fix "incorrect" preset names

[ ] :hankey: Bugfix

[ ] :pizza: New feature

[ ] :fire: Performance improvement

[x] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.10: -
[ ] Backport for 3.9: -
[ ] Backport for 3.8: -

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

@MBkkt : thank you. I adjusted the options.

In general it's about local presets I don't really care about it

Keep in mind that these presets are not just local, they are part of the ArangoDB codebase as much as arangod/Cluster/ClusterTypes.h is.
The goal is to have well defined presets that developers use for reproducibility, and that are also used in CI.

Keep in mind that these presets are not just local,

while they don't used on Jenkins they are local.
(for tests and customer images)

they are part of the ArangoDB codebase as much as

So not really, for example now they were incorrect for sanitizers, and it doesn't have real effect.
I don't have anything against they but anyone can write own preset local and it's used only local.


Add portfolio : Mobile first

Mobile first portfolio with Linters configured

I have resolved the  issues as suggested in the comments


rev to the latest protocol

rev to the latest protocol
this introduces the ability to evaluate in the scope of another object
support parsing the new map<string,string> type
fix a todo around code gen for ElementLists

@danrubel

Still LGTM


Update CONTRIBUTING.md

Hello contributors,
Thank you all for swinging by, in the spirit of Hacktoberfest 2018 I'd like to invite you all to contribute to this repo, just update the CONTRIBUTE.md according to the format.
Happy Hacking!
Format

Project Title
Getting Started
Prerequisites
Installing
Running the tests
License
Acknowledgments
Contributing to the project
Using the Issue tracker
Bug Reports
Feature Request
Pull Request (New Contributors/Members)
Maintainers
Issues

Please check https://github.com/JAIJANYANI/Automated-Resume-Screening-System/pull/4

If this issue is still open I'd like to work on it

If this issue is still open I'd like to work on it

Yes, It's still open. Go for it


Installation Issue

I had install code with $git clone https://github.com/hpi-schul-cloud/jitsi-deployment.git  and run  $kustomize build . | kubectl apply -f - in overlays/development. But i have errors like this
"Error: accumulating resources: accumulateFile "accumulating resources from 'ops/': '/home/k8smaster/Documents/hpi-schul-jitsi/jitsi-deployment/overlays/development/ops' must resolve to a file", accumulateDirector: "recursed accumulation of path '/home/k8smaster/Documents/hpi-schul-jitsi/jitsi-deployment/overlays/development/ops': accumulating resources: accumulateFile "accumulating resources from '../../../base/ops': '/home/k8smaster/Documents/hpi-schul-jitsi/jitsi-deployment/base/ops' must resolve to a file", accumulateDirector: "recursed accumulation of path '/home/k8smaster/Documents/hpi-schul-jitsi/jitsi-deployment/base/ops': accumulating resources: accumulateFile \"accumulating resources from 'monitoring/': '/home/k8smaster/Documents/hpi-schul-jitsi/jitsi-deployment/base/ops/monitoring' must resolve to a file\", accumulateDirector: \"recursed accumulation of path '/home/k8smaster/Documents/hpi-schul-jitsi/jitsi-deployment/base/ops/monitoring': accumulating resources: accumulateFile \\\"accumulating resources from 'https://github.com/coreos/kube-prometheus?ref=master': YAML file [https://github.com/coreos/kube-prometheus?ref=master] encounters a format error.\\\\nerror converting YAML to JSON: yaml: line 31: mapping values are not allowed in this context\\\\n\\\", accumulateDirector: \\\"couldn't make target for path '/tmp/kustomize-756266654/repo': unable to find one of 'kustomization.yaml', 'kustomization.yml' or 'Kustomization' in directory '/tmp/kustomize-756266654/repo'\\\"\"""
error: no objects passed to apply
k8smaster@k8smaster:~/Documents/hp"
where is the porblem?
And thank you for sharing this.

Its on warning for Kustomize version. Need to install kustomize/v3.5.4

I read the requirements part carelessly. Thank you.

Hello again, I went over kustomize and installed but I'm getting some errors. $ kustomize build. | After kubectl apply -f - command only fails here.

And some containers remain in a pending state.

An additionally i think like this: Can i run jicofo, jvb, prosody, web in one pod, and scale this. And all of replicas under a proxy. Its more basic your system.
Thank you for reply.

Change the  on Certificate to your real base 64 token

@congthang1 is right, you need to change the secrets to your own secrets. The present placeholders will not work.
Btw. everything regarding "bbb" (which means Big Blue Button) is related to a different project we have deployed. We are only using this setup to monitor the Big Blue Button instances as well. Therefore you can safely skip/delete the BBB related yamls. I recommend to fork this repo.

Yes I know its for bbb but its will help deployment success :)

Hello @simoncolincap @janrenz @mvakert @wolfm89
Everything goes well apart from the below error at the time of deployment..
For your information, I have also replaced the placeholders for the base64 credentials in
/overlays/production/ops/bbb-basic-auth-secret.yaml
/base/jitsi/jitsi-secret.yaml
apiVersion: v1 kind: Secret metadata: namespace: jitsi name: jitsi-config type: Opaque data: JICOFO_COMPONENT_SECRET:6290f3e910afc1b0ded51a9ff5825e08 JICOFO_AUTH_PASSWORD:b8cb3a744c3a83b9107f6e4115c0bad8 JVB_AUTH_PASSWORD:119d7ffe32bb2964337068852d6ad078 JVB_STUN_SERVERS:meet-jit-si-turnrelay.jitsi.net:443 TURNCREDENTIALS_SECRET:119d7ffe32bb2964337068852d6ad675 TURN_HOST:<IP_ADDRESS> STUN_PORT:4000 TURN_PORT:4001 TURNS_PORT:4002
error: error validating "STDIN": error validating data: ValidationError(Secret.data): invalid type for io.k8s.api.core.v1.Secret.data: got "string", expected "map"; if you choose to ignore these errors, turn validation off with --validate=false
Swift response will be life saver..
Thanks in advance!

@sunilkumarjena21 Did you successfully deploy this setup? Can you share your deployment experience,

We have this running in IONOS Cloud. Our dev Op Tesm
Might not check issues here , I will ask them to do so


selectedOptionStyle with isMulti

Description
selectedOptionStyle="check" does not work with multi select option see below
chakra-react-select Version
4.1.4
Link to Reproduction
https://codesandbox.io/s/chakra-react-select-border-selectedoptionstyle-forked-r4vd8r?file=/example.js
TypeScript?

[ ] Yes I use TypeScript

Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

Operating System

[ ] macOS
[x] Windows
[x] Linux
[ ] iOS/iPadOS
[ ] Android

Additional Information
No response

If you check the docs on selectedOptionStyle it mentions this:

selectedOptionStyle — Options: color | check — Default: color
As of v1.3.0 you can pass the prop selectedOptionStyle with either "color" or "check". The default option "color" will style a selected option similar to how react-select does it, by highlighting the selected option in the color blue. Alternatively, if you pass "check" for the value, the selected option will be styled like the Chakra UI Menu component and include a check icon next to the selected option(s). If isMulti and selectedOptionStyle="check" are passed, space will only be added for the check marks if hideSelectedOptions={false} is also passed.

So you really just need to pass hideSelectedOptions={false} in order to make it work, because the default is true when isMulti is passed.
https://codesandbox.io/s/hq3ynk?file=/example.js:426-642


Some log messages to improve troubleshooting

📚 Context
While deploying rollups-node, we need to check if everything is ok right after it starts.
I still miss some logs that would be nice to have.
✔ Solution

[x] Log the rollups-node version when it starts.
[x] Ensure the rollups-node version matches the Rust services version to avoid confusion
[x] Log which AUTH_* method is being used
[x] Provide a single line of error for each problem found in the configuration
[ ] Log all configuration errors at once to avoid multiple node restarts in quick succession
[x] Use ISO 8601 as the date format

some internal rust daemons are still being logged as 1.2.0, and that may be confusing

This should be fixed regardless.

log which AUTH_ method is being used

Makes sense

@endersonmaia We'll drop the requirement of listing all configuration errors at once. The Node Unit is now focusing on tasks related to the new major 2.0 release, so we'll deprioritize this. Feel free to contribute with a PR, though. I can give you some pointers 😉

@torives I converted the list on this issue description to check boxes, could you mark if any of the items are already implemented, then I'll see if I can take one.

@endersonmaia #322 should solve all of them except the previously mentioned one.


Add and test support for new Dyson devices (Device owners' help is appreciated!)

Yesterday, Dyson announced the following products:

Purifier Big+Quiet
Purifier Big+Quiet Formaldehyde
360 Vis Nav

Based on previous product releases and MQTT/Wifi messaging patterns, adding support for these devices should be trivial. However, testing the new devices with this integration will require the assistance of device owners.
I will cut a beta release adding experimental support for these devices. If any owners are able to help with testing over the coming weeks, that would be great!

The main difference you'll find with the visnav robot is that instead of setting a vacuum power mode, you'll configure a "cleaning strategy". For example, the "auto" cleaning strategy will clean an area twice if it's particularly dusty and the "quick" strategy will skip edge cleaning etc.
There's just a different property in the command and state messages to configure that.
Otherwise the app functionality is pretty much identical to the heurist. Oh, except the clean history returns an additional dust map to be rendered over the clean map.

I just received a Purifier Big+Quiet Formaldehyde if you need someone to test that out.

Hey @cemarriott, that's awesome! Sorry for the slow reply here. If you'd be willing to help collect some information, I can hopefully add support for your Big+Quiet Formaldehyde (and maybe even the Big+Quiet base model) pretty quickly.
Right now, this process uses two tools to learn about the new devices. I want to consolidate the features into a single tool at some point, but that's a future goal.
The process goes like this:

Run get_devices.py to get device information.

You'll need to clone that repo, install Python, the pip package manager, and run pip install requirements.txt to download required dependencies for the script.

Save the following information from that script:

Device Type (I'll need to add this to const.py.
Serial and Credential (I don't need these, don't share them. You'll need them for the next step though)

Run dyson-mqtt-listen to get mqtt messages from the device. This is how we'll double-check that all the status/sensor messages are using the same format as previous devices.

You can download the executable binary for your platform of choice on the release page.
When running it, you'll need to use the flags for devices without wifi stickers.

Sorry if this all feels like a big convoluted process without much explanation. I need to work on simplifying it - for now, if you have any issues, please let me know and I'll be happy to help.

Very cool @dotvezz, love that you have tools for it. The device type is 664.
I saved the MQTT messages to a gist.
I popped the app open and changed the fan level and also the angle/tilt and included those messages too. The CO2 sensor is apparently new, and I'm not sure I have heard of any other device having the "tilt" adjustment. I bumped that tilt down to the "breeze" mode that oscillates as one of the messages too.
Let me know if you need anything else!

You're my hero. That's all super helpful. Once I finish up my day job tomorrow, I'll start work on a new branch that integrates all this and we'll get a beta release out the door for you and others with the same device.

@cemarriott just wanted to follow up, I'm finally getting around to this (Life got in the way, bad excuse but it's what I got) and I have to say thanks, this was a huge help. Together with your MQTT message dump and decompiling the latest Android APK, I was able to find everything needed for the full Big+Quiet lineup. I'll have a release for you soon!

v1.1.0 just released with initial support for all Big+Quiet devices!
There may be some missing features, particularly any that are unique to the Big+Quiet series. Feel free to let me know if anything's missing, then we can work out a plan to decode the MQTT messages with a bit more detail as needed.

Hi, I've added a Big+Quiet Formaldehyde and only some of the entities show up. It's missing fan speed, fan tilt, auto mode, and timer if that's supported. I was wondering if I maybe have a slightly different version, or if there has been some software change. It's bought in the UK and it's running the latest software version (0664PF.<IP_ADDRESS>2).
I'm happy to test things if needed.

@Jink0 hey, thanks for reaching out.

Fan speed is supported, it's a part of the fan entity - not its own entity.
Mode is supported as well, also a part of the fan entity.
Timers aren't currently provided by this integration because of its focus on being local-only as much as possible (IIRC timers utilize the Dyson cloud). I'd recommend setting up automations on your Home Assistant to achieve what you need.
Tilt is actually not supported, I didn't know it's a thing! I'll look into adding support.

Hey thanks for asnwering, I found the speed and mode controls, my mistake there. In the fan controls within home assistant there are Direction and Oscillating fields which don't seem to do anything, as this purifier doesn't have that funcitonality.
For tilt, it can either be full, 0, 25, or 50 degrees. Thanks for the help!

@Jink0 Oh good shout on the direction and oscillation fields! I'd just assumed it would have them and they'd be controllable since it's otherwise so similar to the other fans.
Next release will try to add tilt, and will remove Direction and Oscillation. Thanks!

@daknightuk hey, I admire your struggle! There's a (long) discussion about the 360 Vis Nav over here: https://github.com/libdyson-wg/ha-dyson/discussions/142.
Unfortunately, it appears that Dyson disabled local connectivity on the 360 Vis Nav. Technically, we've been able to work out some details on controlling it via the cloud! However, this integration is focused primarily on providing local-only control capability to Dyson device owners. Part of the reason for this is because so many users dislike relying on internet connectivity.
The other part, which is more important to the continued support of this integration, is to avoid disturbing Dyson. By staying local-only for control, we're just using undocumented features of devices that we own. By potentially using cloud features, we'd suddenly be doing something uncomfortably close to "unauthorized access" to Dyson's systems. I'm one guy, and Dyson is a multinational, multibillion-dollar company, so I want to play nice.
As it stands right now, I'm in "wait and see" mode. If the next generation of Dyson's fans/heaters also disable local connectivity, I'll have to make a decision on where I stand and where this integration goes. But for now, unfortunately, I can't support the Vis Nav.

@daknightuk hey, I admire your struggle! There's a (long) discussion about the 360 Vis Nav over here: #142.
Unfortunately, it appears that Dyson disabled local connectivity on the 360 Vis Nav. Technically, we've been able to work out some details on controlling it via the cloud! However, this integration is focused primarily on providing local-only control capability to Dyson device owners. Part of the reason for this is because so many users dislike relying on internet connectivity.
The other part, which is more important to the continued support of this integration, is to avoid disturbing Dyson. By staying local-only for control, we're just using undocumented features of devices that we own. By potentially using cloud features, we'd suddenly be doing something uncomfortably close to "unauthorized access" to Dyson's systems. I'm one guy, and Dyson is a multinational, multibillion-dollar company, so I want to play nice.
As it stands right now, I'm in "wait and see" mode. If the next generation of Dyson's fans/heaters also disable local connectivity, I'll have to make a decision on where I stand and where this integration goes. But for now, unfortunately, I can't support the Vis Nav.
Edit: for context about why I don't want to use cloud features, companies have a history of disliking it when you start using their cloud services on Home Assistant

https://community.home-assistant.io/t/haier-hits-home-assistant-plugin-dev-with-takedown-notice-lets-fork/675784
https://www.home-assistant.io/blog/2023/10/13/removal-of-mazda-connected-services-integration/
https://www.home-assistant.io/blog/2023/11/06/removal-of-myq-integration/

Interestingly, I almost found a way to integrate the Dyson 360 Vis Nav. I discovered that while the device doesn't permit direct connectivity, I was able to retrieve all my credentials. Unfortunately, I can't connect to MQTT.
My main goal is to integrate the device with Home Assistant so I can disable security sensors in rooms where the Dyson is operating—either while I'm at work or during its cleaning cycles. I came across OpenDyson, which allows command-line queries of Dyson's IoT. If I could somehow feed that data into Home Assistant, even just as a sensor, it would be incredibly useful.
I completely understand your concerns regarding Dyson's cloud services. I've noticed that their development team tends to ignore Home Assistant-related queries in forums, making it challenging to achieve the integration.
As a temporary workaround, I'm considering using the Alexa Media Player to send commands to the Dyson. However, I'm uncertain about the full range of available voice commands since they aren't documented.
If you have any suggestions or alternative approaches, I'd greatly appreciate your input!

@dotvezz Hi there, so I'm stuck with trying to get the vis nav to work, dyson have chosen to ignore my email into them regarding the MQTT connection so I don't think its going to be possible to do local control. I rewrote part of the opendyson code, specifically the module \cmd\funcs.go so its got my details built into it and its quite happy (on a PC) to sit there polling the dyson server and feeding back the result to MQTT. I would like to develop this into a seperate home assistant integration but I'm really stuck on where to start having not done this type of development before. How do you take the .go code and make it into a HA integration? is it an easy process. Any guidance, videos etc would be appreciated as I intend to host the finished integration on my github. Thanks in advance David

@daknightuk hey, I admire your struggle! There's a (long) discussion about the 360 Vis Nav over here: #142.
Unfortunately, it appears that Dyson disabled local connectivity on the 360 Vis Nav. Technically, we've been able to work out some details on controlling it via the cloud! However, this integration is focused primarily on providing local-only control capability to Dyson device owners. Part of the reason for this is because so many users dislike relying on internet connectivity.
The other part, which is more important to the continued support of this integration, is to avoid disturbing Dyson. By staying local-only for control, we're just using undocumented features of devices that we own. By potentially using cloud features, we'd suddenly be doing something uncomfortably close to "unauthorized access" to Dyson's systems. I'm one guy, and Dyson is a multinational, multibillion-dollar company, so I want to play nice.
As it stands right now, I'm in "wait and see" mode. If the next generation of Dyson's fans/heaters also disable local connectivity, I'll have to make a decision on where I stand and where this integration goes. But for now, unfortunately, I can't support the Vis Nav.
Edit: for context about why I don't want to use cloud features, companies have a history of disliking it when you start using their cloud services on Home Assistant

https://community.home-assistant.io/t/haier-hits-home-assistant-plugin-dev-with-takedown-notice-lets-fork/675784
https://www.home-assistant.io/blog/2023/10/13/removal-of-mazda-connected-services-integration/
https://www.home-assistant.io/blog/2023/11/06/removal-of-myq-integration/

Local MQTT is highly unlikely to be re-enabled on the visnav. Most of developers no longer exist (go check linkedin if you want to see who was let go): https://www.bbc.co.uk/news/articles/c6p2660ldn2o
Personally, if Dyson don't want to have their cloud endpoints disturbed, they should probably think about re-enabling the local control.


[ZEPPELIN-13] ZEPPELIN_CONF_DIR cannot be reached until ZEPPELIN_CONF_DIR become set

bin/common.sh tries to find and set ZEPPELIN_CONF_DIR in order to read zeppelin-env.sh, but ZEPPELIN_CONF_DIR is defined in zeppelin-env.sh, so we cannot use different ZEPPELIN_CONF_DIR.

Looks good to me!

this doesnt look good to me... convention is not followed
https://github.com/apache/incubator-zeppelin/blob/master/CONTRIBUTING.md#code-convention ... i spend a lot of time to set a coding convention;;;;

@anthonycorbacho I've read that guide, too. This is about Java and Scala coding style. Could you please which is not following convention? I also think consistency is very important.

This part

Shell style

i.e:
if [ "$1" == "--config" ]
then
...

sould be

if [[ "$1" == "--config" ]]; then
...

@anthonycorbacho Oops. I missed this. I read "Shell" as "Scala" :-). I'm about to make a hotfix now.


Devonthink support?

Hi,
Saw that devonthink was supported, but when I try to highlight within devonthink itself, the service doesn't pop up?
Thanks

Sorry for late reply.
The DEVONthink Pro support is that, for PDF files stored in DEVONthink Pro, Excerptor locates them by their UUID given by DEVONthink. So wherever a PDF file moves, as long as it is in DEVONthink, Excerptor can always find it.


Chart v3.0.2 : Half Doughnut chart canvas not resized to content like in v2

Expected Behavior

Canvas resized to content (no white spaces at top and bottom of canvas).
Current Behavior

Canvas not resized to content (white spaces at top and bottom).
Possible Solution

Tried different configurations without any success.
Steps to Reproduce

See : https://codepen.io/fcorbeil/pen/qBRjydE

Context

I want to get rid of white spaces at top and bottom.
Environment

Chart.js version: 3.0.2
Browser name and version: Any

Hi,
in the migration guide there is an inf that the aspectRatio changed.
https://www.chartjs.org/docs/master/getting-started/v3-migration.html

aspectRatio defaults to 1 for doughnut, pie, polarArea, and radar charts

set it to 2 an take a look if its fine.

You might want to use maintainAspectRatio: false

You rock!  @SebZar and @kurkle solutions worked like a charm!


Update install from source instructions

Hey, what this pull request changes is:

Switch to use headings
Add Tricks section
Add snippet to check if FFmpeg flags are available

Background: I wanted to know if Debian Strech provides all required the FFmpeg flags. So I've created a short snippet. I guess this file is the place where such a snippet could live.
Example output from the snippet (0 means available, 1 means missing):
0	--enable-gpl
0	--enable-postproc
1	--enable-swscale
0	--enable-avfilter
0	--enable-libmp3lame
0	--enable-libvorbis
0	--enable-libtheora
0	--enable-libx264
0	--enable-libspeex
0	--enable-shared
0	--enable-pthreads
0	--enable-libopenjpeg
1	--enable-libfaac
0	--enable-nonfree

This looks good. Thanks for your contribution.


Pulseaudio stack smashing error when starting

Hello, I have an error when launching pulseaudio service. I'm building the image (32 bits) for a CM4, Scarthgap branch. It's a fresh test image with just Alsa, Pulseaudio, Systemd and Dbus. This is the error message:
D: [pulseaudio] alsa-util.c:   start_threshold  : -1
D: [pulseaudio] alsa-util.c:   stop_threshold   :<PHONE_NUMBER>
D: [pulseaudio] alsa-util.c:   silence_threshold: 0
D: [pulseaudio] alsa-util.c:   silence_size : 0
D: [pulseaudio] alsa-util.c:   boundary     :<PHONE_NUMBER>
D: [pulseaudio] alsa-util.c:   appl_ptr     : 0
D: [pulseaudio] alsa-util.c:   hw_ptr       : 0
D: [alsa-sink-MAI PCM i2s-hifi-0] alsa-sink.c: Thread starting up
D: [alsa-sink-MAI PCM i2s-hifi-0] util.c: SCHED_RR|SCHED_RESET_ON_FORK worked.
I: [alsa-sink-MAI PCM i2s-hifi-0] util.c: Successfully enabled SCHED_RR scheduling for thread, with priority 5.
D: [pulseaudio] sink.c: alsa_output.platform-fef00700.hdmi.hdmi-stereo: state: INIT -> IDLE
I: [alsa-sink-MAI PCM i2s-hifi-0] alsa-sink.c: Starting playback.
*** stack smashing detected ***: terminated
Aborted (core dumped)
root@raspberrypi4:~# stack smashing detected
Please help, I have been struggling with this for several days.

Can you try /etc/asound.conf from say https://learn.adafruit.com/adafruit-max98357-i2s-class-d-mono-amp/raspberry-pi-usage#create-asound-dot-conf-file-3170879 and see if it helps ?

Hi kraj, thanks for your reply
I tried with your suggested conf file, but without luck. I'm  getting the same error.
It is worth clarifying that things were going well with the Kirkstone branch. But when I switched to scarthgap pulseaudio no longer wants to start.

Perhaps try to compile pulseaudio with -fsanitize=address added to cflags and then run it. It should give move information during runtime about memory errors.

Sorry, I don't know how to do that.

i had the same issue and worked through it recently. this issue is caused by alsa-lib and pulseaudio using different resolutions for the timestamp structs. in this case pulseaudio uses 32-bit timestamps while alsa-lib uses 64-bit timestamps. the stack corruption occurs when pulseaudio makes a call to alsa-lib to store a 64-bit timestamp into a 32-bit variable.
i encountered this issue with a yocto project i had setup on scarthgap. the issue has been fixed in yocto styhead and beyond.
here's the commit where pulseaudio's configuration was overridden to use 32-bit timestamps:
https://github.com/yoctoproject/poky/commit/e0ffea74cf3f4a492f440acc9e31cdbe7c805192
here's the commits where this was reverted:
https://github.com/yoctoproject/poky/commit/ba4dd8c51af81fbf87a5ecaa73c2c5b26b2fdeae
https://github.com/yoctoproject/poky/commit/763c6dab335968ac2367a9c4f372b1f64f50c212
the commits contain info on why this was done (and what changes were made to undo it). unfortunately this had the consequence of breaking compatibility between pulseaudio and alsa-lib.
my suggestion to fix this is to update to use the newer poky layer with these fixes, or manually apply the fixes shown in those commits above to configure pulseaudio for 64-bit timestamps and disable OSS support.


Only write config files if the --writeConfig option is specified

Fixes https://jira.duraspace.org/browse/FCREPO-2430

The following test fails on Travis and for me locally if I remove the old /tmp/importexport.yml file.
https://travis-ci.org/fcrepo4-labs/fcrepo-import-export/builds/236155126#L3283
We should probably remove: https://github.com/fcrepo4-labs/fcrepo-import-export/blob/master/src/main/java/org/fcrepo/importexport/ArgParser.java#L69 ...and everywhere it is used.


Showing the stages of an evaluation in onnx modifier

Greetings,
Is there a way to provide an image to onnx modifier for a loaded model and show how it proceeds through all the nodes? I would like to examine what each operation does.
Regards.

@Desperado17 I am afraid I can not get your point clearly. Do you mean to investigate the intermediate features between layers? It is not what onnx-modifier aims to do.

Closing due to inactivity.


Fixed react version causes invalid hooks call

Since React hooks were introduced the render methods of patternplate don't work anymore.
Uncaught Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app

I can try to use custom render and mount methods but it would be nice to see this work out of the box. (I think I already tried a while ago and still had the problem since react and react-dom are used as dependencies instead of peerDependencies throughout patterplate)
Live example: https://stickyroll.github.io/react-stickyroll/pattern/use-stickyroll-hook.html?guides-enabled=true&components-enabled=true
I will further investigate. If I have success I could open a PR if this project is still maintained.
my current renderer:
const {merge} = require("lodash");
const React = require("react");
const ReactDOMServer = require("react-dom/server");
const renderReact = require("./render-react");
const styled = require("styled-components");

module.exports = render;

function render(input) {
	const html = typeof input.html === "function"
		? input.html
		: () => {
			const sheet = new styled.ServerStyleSheet();
			const component = React.createElement(input.default);
			const html = ReactDOMServer.renderToString(sheet.collectStyles(component));
			const addedHead = typeof input.head === 'function' ? input.head() : '';
			const head = [addedHead, sheet.getStyleTags()].join('\n');
			return {html, head};
		};

	const copy = merge({}, input, {html});
	return renderReact(copy)
}

my current react-renderer:
const React = require("react");
const ReactDOMServer = require("react-dom/server");
const {merge} = require("lodash");
const renderDefault = require("@patternplate/render-default/render");

module.exports = render;

function render(input) {
	const html = typeof input.html === "function"
		? input.html
		: () => ReactDOMServer.renderToString(React.createElement(input.default));

	const copy = merge({}, input, {html});
	return renderDefault(copy);
}

my current mounting:
const React = require("react");
const ReactDOM = require("react-dom");

module.exports = mount;

function mount(input) {
	ReactDOM.hydrate(
		React.createElement(input.default),
		input.element
	);
}

Versions: (occurs all over since the styled-components 5.x release)
    "@patternplate/cli": "3.2.6",
    "@patternplate/widgets": "3.2.5",
    "react": "^16.12.0",
    "styled-components": "^5.0.0"

I just checked and it is in fact (as mentioned) tied to react being listed in the dependencies.

I added resolutions to my package.json
  "resolutions": {
    "react": "16.12.0",
    "react-dom": "16.12.0"
  },

Error
warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>

I've analyzed this issue a little further and the origin seems to be this file: https://github.com/patternplate/patternplate/blob/7f19af2dec0bdbe4b617fa1b9b29e537ebf1b690/packages/cover-client/index.js, specifically this line https://github.com/patternplate/patternplate/blob/7f19af2dec0bdbe4b617fa1b9b29e537ebf1b690/packages/cover-client/index.js#L4 for the cover
and the following for the demos:

https://github.com/patternplate/patternplate/blob/7f19af2dec0bdbe4b617fa1b9b29e537ebf1b690/packages/demo-client/index.js
https://github.com/patternplate/patternplate/blob/7f19af2dec0bdbe4b617fa1b9b29e537ebf1b690/packages/demo-client/index.js#L21


Set TTL issue

Hi,
I was attempting to set the TTL value in milliseconds instead of seconds using the SET method. The value i was using for TTL was 1 hour. The SET command would complete without error, but any following GET requests could not find the data. After realizing the method expects TTL in seconds, everything worked as expected.
What is the maximum permitted TTL value? I know this is my own fault for not reading the documentation more closely, but it would be nice to receive an error message if the TTL value is invalid instead of silently failing.
Cheers, Adam.

So, memjs just passes along the value to memcache. There actually isn't a maximum TTL value in memcache. However, anything over 30 days (2592000 seconds) is treated as an absolute epoch time (seconds since Unix 1970). The documentation for Client#create describes this.
All ears if you think there is a good way to reflect this in the API, though!

Could you inspect the TTL, and if over the 30 day limit, return an error if the epoch is in the past (before now)? If you are caching with a TTL, defining an expiry date in the past doesn't make a lot of sense.

That's a possibility. I see a couple issues with that:

The semantics of the TTL are to use the clock of the server running memcache, while checking on the client-side would have to use the local clock, which may not be synchronized. So it's not unreasonable that by trying to validate the TTL on the client would result in an incorrect error.

The behavior of memcache is not to return an error if the TTL is in the past. This could very well be behavior that a user exploits (for example, to elide a test for the validity of some value when setting it, and just letting memcache do that work).

This seems like an unfortunate choice of the memcache protocol, but a choice we need to live with. This is a command that accepts two types of parameters, that happen to have the same type, without anything in the protocol to differentiate what the caller means (and an arbitrary cutoff point).
I'd be open, instead to adding some type information to commands that accept a TTL to help a user be explicit about their choices. For example, I can imagine the TTL value taking an object that is either an Interval or a Timestamp and converting it to an integer for memcache accordingly. It'd just have to do this in a backwards compatible way...


Update jsoniter-scala-core, ... to 2.30.4

About this PR
📦 Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.30.1 to 2.30.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.plokhotnyuk.jsoniter-scala" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #92.


refactor code to allow config without monkey patching

Sometimes it would be useful to piggyback on pypki2/mypki's configuration functionality without actually applying pypki2's monkey patch of HTTPS.  Refactoring the code into submodules should make this possible.

Released in 4f8d613236194fd785c26e515d1029290ccf2b77


app_builder_exception

The following snippet produces an app_builder_exception message. I'm not sure what that means, but it seems unlikely to be the desired behaviour.
structure Category : Type.{2} :=
  (Obj : Type)
  (Hom : Obj → Obj → Type)
  (compose : Π ⦃A B C : Obj⦄, Hom A B → Hom B C → Hom A C)

open Category

set_option trace.app_builder true

structure Functor (source target : Category) : Type :=
  (onObjects     : Obj source → Obj target)
  (onMorphisms   : Π ⦃A B : Obj source⦄, Hom source A B → Hom target (onObjects A) (onObjects B))
  (functoriality : Π ⦃A B C : Obj source⦄ (f : Hom source A B) (g : Hom source B C),
                    onMorphisms (compose source g f) = compose target (onMorphisms g) (onMorphisms f))

(The set_option has no effect: I added it because the error messages suggests doing so.)

(While we're at it, if anyone want to explain to me what I should be doing instead of writing Type.{2} in the above --- perhaps using type variables?? --- I'd love to know.)

@semorrison: you can use type universe variables, e.g.
structure {u v} Category : Type ((max u v) + 1) :=
  (Obj : Type u)
  (Hom : Obj → Obj → Type (max u v))
  (compose : Π ⦃A B C : Obj⦄, Hom A B → Hom B C → Hom A C)

Here u and v are type universe variables. I only now the encoding using max and + 1 to tell Lean that Category is one level above the types of Obj and Hom. In the example I used two variables to allow that Hom is in a bigger type universe.
There was a short discussion on the lean-user mailing list: https://groups.google.com/forum/#!topic/lean-user/TDCcc6fPIPY

Thanks, @johoelzl.
I now realise that I may have made a mistake raising this as an issue, rather than asking on the mailing list first. With the set_option command, the following extra message appears (sometimes?):
10:1: [app_builder] failed to create an 'monad'-application,
    failed to solve unification constraint for #1 argument
    (Type ? → Type ? =?= Obj source → Type (max u v))

I'm unsure if this is all my fault or Lean's fault!


Add output parameters for the tool path and version

This allows calling the action multiple times in the
same job and retrieving the path and/or version in
other steps.
Fixes #65

Force-pushed with the PowerShell changes.

Did some extra testing and everything is 👍
Thanks for the contribution @tbroyer 🎉🎈


release notes for v0.5.15,v0.5.16,v0.5.17

Signed-off-by: databender<EMAIL_ADDRESS>Description
This PR fixes #3123
This PR also fixes #3017
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Thank you, @umairnsr87 ✔

Thank you, @umairnsr87 heavy_check_mark

Thanks alot @leecalcote


docker: bump cilium-iproute2 image

Bump iproute2 image, and then cilium-runtime and cilium-builder that depend on it:

Update iproute2 image to f873abca8c71, using latest build from image-tools
Update cilium-runtime-dev with scripts/update-cilium-runtime-image.sh
Build cilium-runtime from Quay on top of the above changes, and update
Build cilium-builder from Quay on top of the above changes, and update

Not sure how I got the cilium-runtime-dev tag wrong, I'm pretty sure I ran ./images/scripts/update-cilium-runtime-image.sh right after updating the iproute2 image, in the same commit.
Does anyone know if I can fix this tag and simply force-push here, or if I need to rebuild the cilium-runtime and cilium-builder images on top of the change?

Not sure how I got the cilium-runtime-dev tag wrong, I'm pretty sure I ran ./images/scripts/update-cilium-runtime-image.sh right after updating the iproute2 image, in the same commit.
Does anyone know if I can fix this tag and simply force-push here, or if I need to rebuild the cilium-runtime and cilium-builder images on top of the change?

test-me-please

test-me-please

I'm working on backports for this PR.

I'm working on backports for this PR.

Ah, is this about exposing ip xfrm output to bugtool? That would be useful context to have in the commit message and/or release notes.

I've added a release note.

Ah, is this about exposing ip xfrm output to bugtool? That would be useful context to have in the commit message and/or release notes.

I've added a release note.


[deploy] Pomchecker validation failure is not captured by release while --dry-run

Task List

[x] Steps to reproduce provided
[x] Stacktrace (if present) provided
[ ] Example that reproduces the problem (link to git repository is ideal)
[x] Full description of the issue provided (see below)

Steps to Reproduce
The release with --dry-run flag passed on this commit. However, the actual release failed. See https://github.com/ASSERT-KTH/collector-sahab/actions/runs/4787404774.
Expected Behaviour
The dry run phase should inform me about my invalid POM.
Actual Behaviour
The dry run does not notify me.
Environment Information

Operating System: Ubuntu 22.04
JReleaser Version: 1.5.1
JDK Version: 11.0.18

Please paste stacktraces from [out|build|target]/jreleaser/trace.log.
[INFO]  Cataloging artifacts
[INFO]    [sbom] Cataloging is not enabled. Skipping
[INFO]  Calculating checksums for distributions and files
[DEBUG]   [checksum] checksum does not exist: out/jreleaser/checksums/collector-sahab/collector-sahab-0.1.6-jar-with-dependencies.jar.sha256
[INFO]    [checksum] main/target/collector-sahab-0.1.6-jar-with-dependencies.jar.sha256
[DEBUG]   [checksum] reading out/jreleaser/checksums/collector-sahab/collector-sahab-0.1.6-jar-with-dependencies.jar.sha256
[INFO]  Signing distributions and files
[DEBUG]   [sign] signature does not exist: out/jreleaser/signatures/collector-sahab-0.1.6-jar-with-dependencies.jar.asc
[DEBUG]   [sign] signature does not exist: out/jreleaser/signatures/checksums_sha256.txt.asc
[DEBUG]   [sign] signing 2 files into out/jreleaser/signatures
[INFO]    [sign] main/target/collector-sahab-0.1.6-jar-with-dependencies.jar
[INFO]    [sign] out/jreleaser/checksums/checksums_sha256.txt
[DEBUG]   [sign] verifying 2 signatures
[DEBUG]   [verify] out/jreleaser/signatures/collector-sahab-0.1.6-jar-with-dependencies.jar.asc
[DEBUG]   [verify] out/jreleaser/signatures/checksums_sha256.txt.asc
[INFO]  Deploying Maven artifacts
[INFO]    [maven] Deploying all staged artifacts
[INFO]      [nexus2] Deploying to maven-central
[DEBUG]     [nexus2] Cannot run program "pomchecker": error=2, No such file or directory
[DEBUG]     [nexus2] located pomchecker-1.8.0.zip
[DEBUG]     [nexus2] downloading https://github.com/kordamp/pomchecker/releases/download/v1.8.0/pomchecker-1.8.0.zip
[DEBUG]     [nexus2] downloaded pomchecker-1.8.0.zip successfully
[DEBUG]     [nexus2] unpacked pomchecker-1.8.0.zip
[DEBUG]     [nexus2] cached /home/runner/.jreleaser/caches/pomchecker/1.8.0/pomchecker-1.8.0/bin/pomchecker
[DEBUG]     [nexus2] [ERROR] <description> is not defined in POM. Will use value from parent:
[DEBUG]     [nexus2] 	A tool for augmenting the static diff with runtime information
[DEBUG]     [nexus2] <url> is not defined in POM. Will use computed value from parent:
[DEBUG]     [nexus2] 	https://github.com/ASSERT-KTH/collector-sahab/matched-line-finder/
[DEBUG]     [nexus2] [ERROR] <description> is not defined in POM. Will use value from parent:
[DEBUG]     [nexus2] 	A tool for augmenting the static diff with runtime information
[DEBUG]     [nexus2] <url> is not defined in POM. Will use computed value from parent:
[DEBUG]     [nexus2] 	https://github.com/ASSERT-KTH/collector-sahab/collector-sahab/
[DEBUG]     [nexus2] [ERROR] <description> is not defined in POM. Will use value from parent:
[DEBUG]     [nexus2] 	A tool for augmenting the static diff with runtime information
[DEBUG]     [nexus2] <url> is not defined in POM. Will use computed value from parent:
[DEBUG]     [nexus2] 	https://github.com/ASSERT-KTH/collector-sahab/trace-diff/
[DEBUG]     [nexus2] [ERROR] <description> is not defined in POM. Will use value from parent:
[DEBUG]     [nexus2] 	A tool for augmenting the static diff with runtime information
[DEBUG]     [nexus2] <url> is not defined in POM. Will use computed value from parent:
[DEBUG]     [nexus2] 	https://github.com/ASSERT-KTH/collector-sahab/collector-sahab-commons/
[DEBUG]     [nexus2] [ERROR] <description> is not defined in POM. Will use value from parent:
[DEBUG]     [nexus2] 	A tool for augmenting the static diff with runtime information
[DEBUG]     [nexus2] <url> is not defined in POM. Will use computed value from parent:
[DEBUG]     [nexus2] 	https://github.com/ASSERT-KTH/collector-sahab/trace-collector/
[ERROR]     [nexus2] Command execution error. exitValue = 1
[INFO]  Writing output properties to out/jreleaser/output.properties
[ERROR] JReleaser failed after 13.907 s
org.jreleaser.model.JReleaserException: Rules for publishing to Maven Central were not met
	at jreleaser.shadow.org.jreleaser.sdk.commons.AbstractMavenDeployer.collectDeployables(AbstractMavenDeployer.java:136)
	at jreleaser.shadow.org.jreleaser.sdk.nexus2.Nexus2MavenDeployer.deploy(Nexus2MavenDeployer.java:57)
	at jreleaser.shadow.org.jreleaser.engine.deploy.maven.ProjectMavenDeployer.deploy(ProjectMavenDeployer.java:55)
	at jreleaser.shadow.org.jreleaser.engine.deploy.maven.MavenDeployers.deploy(MavenDeployers.java:167)
	at jreleaser.shadow.org.jreleaser.engine.deploy.maven.MavenDeployers.doDeploy(MavenDeployers.java:150)
	at jreleaser.shadow.org.jreleaser.engine.deploy.maven.MavenDeployers.deploy(MavenDeployers.java:59)
	at jreleaser.shadow.org.jreleaser.workflow.DeployWorkflowItem.doInvoke(DeployWorkflowItem.java:35)
	at jreleaser.shadow.org.jreleaser.workflow.AbstractWorkflowItem.lambda$invoke$0(AbstractWorkflowItem.java:43)
	at jreleaser.shadow.org.jreleaser.engine.hooks.CommandHookExecutor.execute(CommandHookExecutor.java:53)
	at jreleaser.shadow.org.jreleaser.workflow.AbstractWorkflowItem.invoke(AbstractWorkflowItem.java:43)
	at jreleaser.shadow.org.jreleaser.workflow.WorkflowImpl.doExecute(WorkflowImpl.java:115)
	at jreleaser.shadow.org.jreleaser.workflow.WorkflowImpl.execute(WorkflowImpl.java:52)
	at jreleaser.shadow.org.jreleaser.cli.Release.doExecute(Release.java:380)
	at jreleaser.shadow.org.jreleaser.cli.AbstractModelCommand.execute(AbstractModelCommand.java:89)
	at jreleaser.shadow.org.jreleaser.cli.Release.execute(Release.java:307)
	at jreleaser.shadow.org.jreleaser.cli.AbstractCommand.call(AbstractCommand.java:52)
	at jreleaser.shadow.org.jreleaser.cli.AbstractModelCommand.call(AbstractModelCommand.java:53)
	at jreleaser.shadow.org.jreleaser.cli.AbstractCommand.call(AbstractCommand.java:37)
	at jreleaser.shadow.picocli.CommandLine.executeUserObject(CommandLine.java:2041)
	at jreleaser.shadow.picocli.CommandLine.access$1500(CommandLine.java:148)
	at jreleaser.shadow.picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
	at jreleaser.shadow.picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
	at jreleaser.shadow.picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
	at jreleaser.shadow.picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
	at jreleaser.shadow.picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
	at jreleaser.shadow.picocli.CommandLine.execute(CommandLine.java:2170)
	at jreleaser.shadow.org.jreleaser.cli.Main.execute(Main.java:98)
	at jreleaser.shadow.org.jreleaser.cli.Main.run(Main.java:94)
	at org.jreleaser.tool.JReleaser.main(JReleaser.java:47)

To see the full stack trace, you may download the artifact here.

🎉 This issue has been resolved in v1.6.0 (Release Notes)


Implement distinct_on

A stab at implementing distinct_on.
I may have missed something important, but this looks like it works how I would (naively) expect it to.

hey @plumdog this looks great! thanks for contributing. i'll go over your other prs as well

Grand, thanks!


[ISSUE]Item Splitter has Inconsistent I/O, Breaking with Crescent Hammewr

Industrial Foregoing Version: 1.6.5-122
TeslaCoreLib Version: 1.0.12

The I/O configuration doesn't match the sides? It only outputted items when I enabled the right-hand side, and it outputted to the front side. I do have another one of these Item Splitters for another machine and I placed it over and over again to see if the direction it is placed from has any part to play in it. That Item Splitter has no issues whereas the one in the screenshots does, probably due to the direction I placed it from.
ALSO, you misunderstood my previous issue, the crescent hammer does indeed rotate the machines, but "SHIFT"+"RIGHT-CLICK" doesn't break the machine. Also, it would be a nice feature for the machines to retain their inventory when broken which is a feature in the mod "Mekansim".
Thanks :)

I didn't misunderstood the issue, the SHIFT part wasn't mentioned, use the tesla wrench


feat: customize button texts of message dialog

Demo:

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
This PR will be ready after https://github.com/PolyMeilex/rfd/pull/76 be merged.

This PR will be ready after https://github.com/PolyMeilex/rfd/pull/76 be merged.

Nice PR!

Where there is a new problem: the dialog level (Info / Warning / Error) is not implemented in the new message dialog.
I am trying to complete it but got stuck at https://github.com/microsoft/win32metadata/issues/968

I'm not familiar with Tauri architecture yet but beware that your manifest may need external edits, may get overwritten, etc. for users that need to add identity, enable high-DPI, add registration-free coclass entries, etc.

I'm not familiar with Tauri architecture yet but beware that your manifest may need external edits, may get overwritten, etc. for users that need to add identity, enable high-DPI, add registration-free coclass entries, etc.

I think that all manifests should be added by tauri, and provide some config option to users if necessary. Just like what electron did: https://github.com/electron/electron/pull/14596

Test failed:
  process didn't exit successfully: `D:\a\tauri\tauri\target\debug\deps\tauri-66d30672674b2f8e.exe` (exit code: 0xc0000139, STATUS_ENTRYPOINT_NOT_FOUND)

Seems because common controls v6 was not used when testing. I am unfamiliar with the restart crate and don't know how to fix it.

@meowtec it's not related to the restart crate; even if you remove both restart and app-updater from the workspace and run cargo test --features dialog-all it fails with the same error. Seems like we'd need to enable common controls v6 on the unit test runner itself?

Fixed with a trick @meowtec :P

Is okLabel and cancelLabel good names for this on the JS API? Example:
ask('something?', { okLabel: 'Sure', cancelLabel: 'Definitely not' })

Implements #3455

and #2147


issue-244 Add configuration value for the default readiness statuses …

…(UP/DOWN) for empty check responses
resolves #244

@pgunapal thanks for the review. Can you take a look again, please?


Add Support for LICENSE.txt

Please consider a logic like that to support .txt LICENSE files
let path = "\(packageCachePath)/\(pkgDir)/LICENSE"

let data: Data? = {
    if let data = fman.contents(atPath: path) {
        return data
    } else {
        return fman.contents(atPath: "\(path).txt")
    }
}()

guard let data else { return }

I believe this was supported in

#21


[BUG] :bug: /WIP command do not remove :construction: from title but adds one more

Current Behaviour
When we use /WIP command it will add :construction: to title
than again when we use /WIP command it will add another :construction: emoji
Expected Behaviour
Instead of adding another emoji it should remove the existing one
Steps To Reproduce

Create new issue
use /WIP command
again use /WIP command
See that title contains 2 `:construction: emoji

Anything else?

:tada: This issue has been resolved in version 1.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.7.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Combine multiple prints to a single one

The goal is to avoid interception with other prints from different threads.
Originally, I wanted to delete println() entirely, but it's used by print_error_message(). This function parses the given string to add error colorization. It's used to print e.g. JSON parsing errors.

Thanks :)


Make compliant for Ruby 3.x

Updated http-parser-lite gem to Ruby 3.3 compliant gem.
Removed deprecations / errors around the removal of exists? in Ruby 3.2

@iffyuva
Can someone please review this?  I would love to get a new version of the gem cut and available to work on Ruby 3.x

@jbrodie thanks for the PR.
@swrobel would you like to cut a new release? Thanks

@swrobel I have used it on > Ruby 3.x only at this point.
I can't say I have anything else below that to test it against, and I think anything below 3.x is out of support anyways.
3.0 is on the way out, 3.1 will be minimum.
I would think leaving it restricted to 3.0 would be fine as I can vouch for that working.
https://www.ruby-lang.org/en/downloads/branches/

@swrobel
I have added the gemspec ruby restriction, as well as changelog record.
Also, bumped to 2.0.0 version as this is something of a major change and it just felt like the right thing to do.

would you like to cut a new release?

@iffyuva I don't believe I have rubygems permission, so someone from your org will have to release the gem, but it should be good to go

@swrobel
@iffyuva
Any update on when to expect this to be release on rubygems?

@swrobel
@iffyuva
Hey guys,
I don't mean to pester but any chance we can get this new version on Rubygems?

@jbrodie I have cut a new release. Thanks for the PR. Cheers 👍

Awesome.  TY.


Add logging around specific number of matches

[x] I have signed the Contributor License Agreement.
[ ] This pull request is related to an issue.

In attempting to diagnose issues with search results, it's helpful to have the number of matches in the search result. This information is sent to telemetry, but is not ever put into the log.
Microsoft Reviewers: Open in CodeFlow

/azp run


Added README.md steps

@Anjalis14 Add this in Contributing.md .......After resolving the conflicts, please open a new PR for review.
Thank you!

ok sure i will
On Wed, Oct 16, 2024 at 11:26 AM Priya Ghosal @.***>
wrote:

@Anjalis14 https://github.com/Anjalis14 Add this in Contributing.md
.......After resolving the conflicts, please open a new PR for review.
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/PriyaGhosal/BuddyTrail/pull/791#issuecomment-2415798369,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFIAMOY7TI5S6HQZRPFNY33Z3X52FAVCNFSM6AAAAABP7ZS76SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJVG44TQMZWHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Anjalis14 For Now I have merged your PR . Now You can work on Contributing.md file

@PriyaGhosal  i have to add steps to contribute in contributing.md file right ???


Sticky server does not work with H2 client (#7261)

Backport #7261 to 8.1.x branch

(cherry picked from commit d285211b72c3db636623575ce5a69b2f3d74d4a0)
Conflicts:
proxy/ProxySession.cc
proxy/ProxySession.h
proxy/ProxyTransaction.cc
proxy/ProxyTransaction.h
proxy/http/Http1ClientSession.cc
proxy/http/Http1ClientSession.h

[approve ci Fedora]


2023-07-22-AlphaPo

/payout

/qualitycheck

/qualitycheck

@JediFaust good catch with the recent news linking the attack to DPRK!
/payout

@jhirschkorn note the link to DPRK and adjust the payout rate as needed.

Thanks, @JediFaust! 3209 characters were added/changed in this PR. At a rate of 5¢/char your contribution is worth $160.45. @albina-at-inca will process your payment.

@albina-at-inca payout on this should be 2x

Thanks, @JediFaust! 3209 characters were added/changed in this PR. At a rate of 5¢/char your contribution is worth $160.45. @albina-at-inca will process your payment.

@albina-at-inca payout on this should be 2x

Noted.


HW3: Development for Project (5+ hours)

Created this new PR today to split up the old PR between parts 1 and 2 (work was done last week)


FastUniq-like function

could you add a function that can deduplicate  the reads for de novo analysis, becuase it seems that only  FastUinq  can do such work

Thanks, I will consider about this feature request, and may implement it in a future version.


Why use a separate locale package?

Hi @noxify . Thanks for this project. I used it as a reference while adding next-international to my current t3 turbo project.
I have one question: why separate locales into another package? Is it so that it can be used in other nextjs projects at the same time? Or only for organizational reasons?
Thanks for this! I had not heard of i18n ally before. Looks awesome!

Hi @dBianchii,
soo sorry for the late reply.

Is it so that it can be used in other nextjs projects at the same time?

Yeah, could be a possible use case for this - Having some shared translation ( e.g. Save, Update ), but would work only if you plan to use generic translation ( e.g. Create instead of Create Task )

Or only for organizational reasons?

Tbh, I can't remember why I did it as separate package - possible that it's just over-engineered :D
If I'm not wrong, I had to use a "custom source" configuration for  i18n ally ( and read the JSON files), otherwise I got only a "blank screen".
I think you can implement the localization directly in the app, if you don't need the i18n ally extension - But with the current implementation I would keep it in a separate package, otherwise you have to add the lang:gen command in each app ( or use something else which generates the ts files.

Hope that makes sense, haven't checked the code and/or if it's now possible to read the ts files directly / using the next-international configuration from i18n ally.

As mentioned in #6 it seems that we could read the ts files directly, but they are read-only.
I assumed it's based on the "nested structure", but got the same result with a "flat structure".
I think using the json files is currently the "way to go" if you want to use the Editor UI from i18n-ally.
I have seen that there are some issues/PRs in their repo.
Will close this issue for now - if there is something else, please let know :)


Add MySQLServerConfiguration managed resource

Signed-off-by: sergenyalcin<EMAIL_ADDRESS>
Description of your changes
Fixes #286
Implementing MySQLServerConfiguration managed resource.
Support for configuring MySQLServer parameters. If the configuration has been applied successfully, the MySQLServerConfiguration MR will have the Ready condition in its status.
I would like to say a few things about the problem I encountered while working on this.
Valid configurations of the MySQL Server have been determined in server side and new ones cannot be created. Only existing valid configurations can be updated. Therefore, if the config cannot be found in the result of the get call (in Observe function), instead of returning nil, an error is returned and the error is reported in status conditions of the MySQLServerConfiguration managed resource.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

I have manually configured an existing MySQLServer instance's connect_timeout parameter using a MySQLServerConfiguration managed resource.
I have manually tried to configure an existing MySQLServer instance's invalid configuration parameter using a MySQLServerConfiguration managed resource. The invalid parameter could not be configured as expected. But we observed the error message in status conditions.
I have tested late-initialization functionality by adding a MySQLServerConfigration MR without value field. I observed that, this field set to actual value by controller.

The behavior I mentioned above (valid configurations are determined on the server side and new ones cannot be created) is the same for PostgreSql. In description of PostgreSQLServerConfiguration PR (#285), there is the following expression:

My observation is that for a psql (server) configuration that has not been manipulated previously, the postgresql.ConfigurationsClient.Get will report a 404 and for the MR, postgresqlserverconfiguration/external.Create will be called accordingly. However, if it has previously been manipulated, and even if it's set to its default value and its source is reset to system-default, I have observed that postgresql.ConfigurationsClient.Get returns the configuration object and postgresqlserverconfiguration/external.Create is thus not called.

My observation for both MySql and PostgreSql does not agree with this observation. As I mentioned above, all valid configurations are defined on the server side and the Get call returns successfully for a valid configuration whether it is manipulated or not. So, if there is no error in the old observation, there may have been a behavior change in the Azure Sdk since then.
It should also be noted that there is no problem in the main workflow on the PostgreSql side. That is, there is no error in configuring a valid parameter (by creating a Managed Resource) or reverting the configured parameter (by deleting the Managed Resource). The improvement mentioned here is that when trying to configure an invalid parameter, the error encountered is reported in status.conditions (We do not see any errors now).
The improvement on the PostgreSql side is not included to this PR, as it is not the subject of this PR, and because the PostgreSql resources that were created in the past may be running with the old behavior.
Thanks to @ulucinar for her guidance on this task.

Because we do not squash commits and preserve commit history, we should author a clean & descriptive commit history.


Connectivity issues with new Clip v2 API

With the update to a more recent node-red (2.1.4) and node-red-contrib-hue-magic (4.0.4), I've started to get connectivity problems when i deploy my whole setup. I have now disabled some of my flows, and run reduced functionality (3 tabs => 3 rooms).
When i enable more, I will typically run into 'request failed with status code 503' errors connecting to the bridge.
Thinking the bridge might be throttling the functionality, decided to add multiple bridge entries for the same bridge (with different app keys), however that does not seem to fix the issue for me.
In the earlier pre-Clip2 version, i had the possibility to reduce the polling frequency to avoid overloading the bridge interface, are there any tweaks i can use to reduce traffic to/from the bridge?

I have the exact same problem. Triggering more than 2 lights in parallel in Node Red, results in only 2 of them working and all the rest erroring with 'request failed with status code 503'. Hope a fix is available very soon. This breaks quite a lot of automations.

Same, fixed it for now with a 250ms delay.

I implemented a worker queue in HueMagic in the latest version. From now on, the commands to the bridge will be executed in a throttled manner, whereby the value of the parallel commands can be set in the bridge configuration.
Can you guys try it again with this update? It might be better if you set a value below 10 in the configuration if the errors are still appearing. Let me know if this fixed your issue.

Thanks for your quick efforts to fix! Unfortunately it didn't fix it. I have set worker to 8, but still only 2 lights can be controlled { "alert": 5, "color": "blue"}, the others (2) still show the "input error" and won't blink. "Error: Request failed with status code 503"

What happens if you set the worker value to 1? Do you still face this issues?

According to the Philips Hue documentation the bridge can execute different commands at different speeds. You can for example only execute 1 group or 10 light commands per second without hitting the implemented buffer. If you want play an alert effect (which needs more resources on the bridge) I would generally suggest you to put all these lights inside a group (maybe called “Alert”) and execute your alert command on the group. This will perform much better and hopefully without any API limitation errors.

Mmm, that is something to consider. However, something tells me I had it that way in the past (but maybe not with huemagic) and I moved away from it because lights weren't blinking in synchronisation.

Will try it tomorrow evening!

Seems to work if I set the worker to 1. Great job fixing it so fast! I was already executing my command on groups by the way...

Things have definately improved with this new release, but with workers set to 10, i still see a 503 at the end of my 'deploy'.
With workers set to 1, i don't see any 503 errors anymore.
What i do notice now is the following message twice for every one of the 9 groups that i use. This i did not see before, and could be related to changes made in the new release:
"The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.." Is this an error, or is it just a warning?
Not sure how exactly i can see when the bridge connection is ready, do i need to add a startup delay somewhere now?
Functionally everything seems to work as expected (at first glance, i did not test very extensively yet).

Blinking a group is also a no go. Apparently the group node has a bug to. They don't return to the previous state after the blinking but simply turn off :(
So I guess the worker issue needs fixing so we can address more than 2 lights in parallel.

I had 4.0.5 installed until a few minutes ago, and wanted to play with the "alarm" effect.
Triggering it once, was fine. Twice, fine too. But while testing my flow, it got worse and worse, and I ended up in a restart loop of my node red server.
I didn't see any 503 errors in the debug tab (debug nodes were enabled), but like 2 seconds after NR was restarted, it crashed again due to this issue:

To fix this, I had to delete all huemagic nodes I had. No clue what exactly I did wrong to trigger this.
I now updated to 4.1.0, set workers to 10 and the alarm function works fine now (did just a quick test).
E.g. if I set it to 1 second, it shows it for 1 second only. Before I had the infinite crash loop, setting the seconds had no effect. Sometimes it would show the alarm effect for up to 10 seconds before stopping, even if I set it to e.g. 2.
So I'll assume I messed with the buffer?
Anyways, once the alarm is finished, the lights stay off - as reported in #294


An attempt at a fix for a NoSuchMethodError (and running dartfmt)

The same changes apply on the rewrite_modular branch too; other than
dartfmt changes. Feels kinda too simple but it does get rid of the issue & message author functionality still works from what I tested on my own
The changes I made directly are from line 99 - 101
Resolves #48

Please create pull request into rewrite_modular branch


Add an external, persistent cache to speed up OLS queries

This has been implemented in the mzTab Validator webapplication.

This has been implemented in the mzTab Validator webapplication.


chore: release main

:robot: I have created a release beep boop
1.6.0
1.6.0 (2024-07-29)
Features

1password: Support for mantic (#23) (691e4c1)
1password: Update version options (9d2c5a6)
act: Update version options (42638d1)
doppler: Update version options (daef022)
snowflake-odbc: Update version options (3b3889b)
trivy: Update version options (7cedacd)

1password: 1.2.0
1.2.0 (2024-07-29)
Features

1password: Support for mantic (#23) (691e4c1)
1password: Update version options (9d2c5a6)

act: 1.1.0
1.1.0 (2024-07-29)
Features

act: Update version options (42638d1)

doppler: 2.3.0
2.3.0 (2024-07-29)
Features

doppler: Update version options (daef022)

snowflake-odbc: 1.2.0
1.2.0 (2024-07-29)
Features

snowflake-odbc: Update version options (3b3889b)

trivy: 1.1.0
1.1.0 (2024-07-29)
Features

trivy: Update version options (7cedacd)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/v1.6.0 :sunflower:

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/act-v1.1.0 :sunflower:

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/1password-v1.2.0 :sunflower:

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/doppler-v2.3.0 :sunflower:

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/snowflake-odbc-v1.2.0 :sunflower:

:robot: Release is at https://github.com/itsmechlark/features/releases/tag/trivy-v1.1.0 :sunflower:


Fix for #65 - run in application stack

#65 - Try to get application stack if there is no request stack

Is there a reason not to merge this?

I've resolved this in a slightly-cleaner but identical manner in https://github.com/TkTech/flask-babel/commit/2ada81c833640d512a00fcebdd867ff46294b932

Included in PR #88, thanks!


Text of network mapping and storage mapping screens

I suggest the following changes for the network mapping screen and the storage mapping screen.
Directions
Current text: Start with an existing network mapping between your source and target providers, or create a new one.
Suggested change: "Select an existing network mapping or create a network mapping."

The verb for a list is "Select." A user selects a list item from the list. "Start with" is not normal usage.
"Select ... or create ..." is consistent with the text of the General screen, "Select or type to create a namespace".
The phrase "between your source and target providers" is unnecessary. If the user has created a network mapping in the past, they know what it is for. If they create a new network mapping, there is an explanation.
Remove the comma after the first option. A list of two options does not require a comma to separate them.
"create a new one" is vague. Better to call it a mapping instead of "one". The word "new" is redundant if the user is creating a mapping.

List options
Current text: One of the options for the mapping list is Create a new network mapping.
Suggested change: "Create a network mapping".

"New" is redundant.

New network mapping
Current text: Map source and target networks. The default OpenShift pod network is pre-selected. Other networks can be selected in the dropdowns.
Suggested change: "Select a target network."

As far as I can see, the user cannot change the source network. "Map source and target networks" implies that the user can do something to the source network.
Not necessary to say that the default pod network is selected. The user can see this.
Not necessary to say "Other networks can be selected in the dropdowns". Telling the user to select a target network is sufficient. "Dropdowns" might not be understood by non-English speakers. If you refer to a dropdown list, it is better to call it a list. That is how the IBM style guide refers to this UI element.

Directions on storage mapping screen
Current text if a storage mapping is selected: Map source datastores to target storage classes. Sources missing from your selected mapping have been added. The default storage class is pre-selected. Other storage classes can be selected in the dropdowns.
Suggested change: "Select an existing storage mapping or create a storage mapping."

The last two sentences can be omitted for the same reasons mentioned above.

Sources missing from your selected mapping have been added

What does this mean?
Is there any way for the user to create a mapping that does not lack sources?
Does sources refer to source data stores? If so, data stores should be added to make the meaning clearer.
The existing storage mapping shows more than one source data store. Can a user create a mapping with multiple source data stores? I recall that there was an Add button in the past but that seems to have been removed.

cc @vconzola

@apinnick :

Sources missing from your selected mapping have been added

What does this mean?

When the user reaches this step, they have already selected their VMs. So the wizard knows which sources need to be mapped before the user can proceed. If they select an existing mapping (created on the mappings page) that does not include all of those sources, this message appears and those sources are added, leaving the user to select targets for them in addition to what was in the selected mapping.

Is there any way for the user to create a mapping that does not lack sources?

Yes, if the user selects an existing mapping that does already cover all of the required sources for the selected VMs, this message does not appear.

Does sources refer to source data stores? If so, data stores should be added to make the meaning clearer.

Yes, sources refers to VMware datastores (in the case of storage mappings) and VMware networks (in the case of network mappings). The term "source" was used because it's generic and can be the same in both steps. But we can change it so it says "datastores" and "networks" respectively.

The existing storage mapping shows more than one source data store. Can a user create a mapping with multiple source data stores? I recall that there was an Add button in the past but that seems to have been removed.

The Add button is present only when the user is creating a mapping on the mappings page. This is because in that context, the VMs being migrated are not known, so they have all sources in the provider available to them. In the plan wizard, we know exactly which sources are needed to migrate the selected VMs, so they have been added for the user and there is nothing to gain by adding more. If multiple source datastores are needed, they will be shown. The user can create a mapping with any number of source datastores from the mappings page.

@apinnick

Current text: Start with an existing network mapping between your source and target providers, or create a new one.
Suggested change: "Select an existing network mapping or create a network mapping."
The reason this is written the way it is is because the user isn't really selecting a network mapping and that's it. Mappings are templates that can be modified for each plan, so essentially when a user chooses to start with an existing mapping they're copying the contents of the mapping into the plan and then editing as necessary. I wanted to call them mapping templates, but that idea was nixed by PM. So, if there's a better way to describe what's actually happening than "Start with..." I welcome ideas.

The phrase "between your source and target providers" is unnecessary.
Agree.

Current text: Map source and target networks. The default OpenShift pod network is pre-selected. Other networks can be >selected in the dropdowns.
Suggested change: "Select a target network."
I'll rework this, but I want to give the user more explanation than just "Select a target network". I want them to know why the pod-network has been pre-selected (it's the default if no other OCP provider networks are chosen) and that they have an option to change it. Same for storage mappings.

"New" is redundant.
Agree. I'll remove this throughout.

@vconzola

The reason this is written the way it is is because the user isn't really selecting a network mapping and that's it. Mappings are templates that can be modified for each plan, so essentially when a user chooses to start with an existing mapping they're copying the contents of the mapping into the plan and then editing as necessary. I wanted to call them mapping templates, but that idea was nixed by PM. So, if there's a better way to describe what's actually happening than "Start with..." I welcome ideas.

Got it. Now I understand why you used "Start with..." That was the part that was not clear to me. I think the fact that the user can modify an existing mapping could be made more explicit.
How does this sound?  "You can select an existing network mapping to modify or you can create a new network mapping."

I want them to know why the pod-network has been pre-selected (it's the default if no other OCP provider networks are chosen) and that they have an option to change it.

I see. What do you think about this? "The OpenShift pod network is the default target network. You can select a different target network from the network list."

How does this sound? "You can select an existing network mapping to modify or you can create a new network mapping."

The weird part is that if they select an existing mapping that already covers the necessary sources, they won't need to (or even be able to) modify it. Also, in the case where they do need to modify it, "modify" doesn't seem like the ideal choice because they aren't free to change whatever they want, they are simply able to fill in the blank targets asked for by the wizard (sources have been modified for them).
Maybe instead, "You can select an existing network mapping or create a new network mapping. If any existing mapping is not sufficient for the selected VMs, you can complete it here." or something like that.

Maybe instead, "You can select an existing network mapping or create a new network mapping. If any existing mapping is not sufficient for the selected VMs, you can complete it here." or something like that.

@mturley We know that the user can't modify the source part of the mapping, so I'm not sure that "modify" can't be used. If the user selects an existing mapping, you're saying that they can only change the targets? I think that would be enough of a change to use the word "modify".
Would this work? "You can select an existing network mapping, updating the target network if necessary, or create a new network mapping."

Ah, true, I forgot you can change those existing target selections. Either of those two suggestions work for me then, I'll leave it to @vconzola . Maybe your initial suggestion is better. "You can select an existing network mapping to modify or you can create a new network mapping."

@mturley I agree. I prefer "You can select an existing network mapping to modify or you can create a new network mapping." I also like @apinnick suggestion of "The OpenShift pod network is the default target network. You can select a different target network from the network list." Do you need updated mockups or can you just make these changes in the code?

I can just make the changes directly. Thanks!

@apinnick we decided to just remove Sources missing from your selected mapping have been added, right? or did you want to replace that with something else after my explanation?

we decided to just remove Sources missing from your selected mapping have been added, right? or did you want to replace that with something else after my explanation?

@mturley  That's fine with me. No further suggestions.


Vowel symbols are removed from Devanagari (Hindi) scripts

This is somehow related to this issue.
In Devanagari, a vowel combines with a consonant to form a compound letter. However, the current tokenizer removes some vowel symbols and only the consonant symbol remains.
Example: कु (k + u)   → क  (k,  ु is removed)
I've not checked everything, but languages in Brahmi script family would have the same issue.

Yes, as I mentioned in the multilingual.md the normalization may cause ambiguities in certain languages. If you are not happy with the preprocessing, you are free to train your own model in your languages of interest.


CloudLinux support

CloudLinux is a RHEL-based distro.

Signed the CLA now.

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.

For Logstash 5.X, the module has been heavily rewritten. As a result, all outstanding pull requests (some of which are very old) are unfortunately suffering from severe merge conflicts, and many of them are probably no longer needed.
With the release of the new version, the time has come to close out all the pull requests that have, in all honesty, been neglected. Starting with a clean slate will help us focus on new pull requests that come in against the new code base and the much-improved acceptance test suite.
I apologise for the lost work that is represented in this pull request and will strive, as the current maintainer, to not let pull requests get into a state like this in future.


bring obsidian to the front at the time of the reminder

I am leaving obsidian open and hidden most of the time, so it would be nice if you could bring the obsidian window to the front when the reminder is fired. I don't know if it's easier, but I believe this is an alternative to the system notification support, no ?

@imeed166 @wenlzhang Can you check v1.0.3?
I've implemented system notification feature roughly.
Please check Use system notification.

Really useful feature. Just tested this on Windows 10, works great!

Yes @uphy it works great, thank you. But if I use system notification, I can't postpone the task. So 2 solutions comes to mind :

implement a native way to postpone the reminder with the option specified in the plugin settings
keep both system notification and obsidian notification enabled, so that when I get a reminder, I can postpone it by opening obsidian.

@imeed166 When you click the notification (not close button, left part of the it), an reminder modal should be seen in Obsidian.
In the modal, you can postpone the task as you did before.
(maybe solution 2)
Also, the Later options in the system notification is possible only in Mac. (the API seems not available on Windows)
I can implement it in the future 👍🏼

I see, perfect, solution 2 is already here. Yes, a mac specific implementation would be nice, but I think that it's already very functional as it is, so I think you should focus on other more urgent issues for now. Thank you again for this great plugin.

I'm glad to hear that.
Thank you for suggesting cool features!

I close this issue.
Instead, I create another issue for supporting system notification actions.

Thank you, @uphy , for implementing this! It works like a charm!


Updated recipe/meta.yaml to version 3.45.0

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Typescript

This adds typescript support for both main and renderer process. For now the app/main/index.js cannot be written in typescript we can make it work with minor change once we get there.

Would it make sense if we put the ts-node.js into shared or maybe common. directory?
/* To make the util runnable in both main and renderer process */
if (process.type === 'renderer') {
	const remote = require('electron').remote;
	app = remote.app;
} else {
	const electron = require('electron');
	app = electron.app;
}
const tsNode = require('ts-node');
tsNode.register({
	cacheDirectory: app.getPath('userData')
});


[LLVMGPU][TD] Workaround a miscompile with gpu pipelining

The pipelining of shared mem copies requires that the involved buffers have been multibuffered.
When this is not the case, this may lead to miscompiles like what we observed in https://github.com/openxla/iree/issues/13451.
In this specific case, multibuffering doesn't kick in for one of the buffer because one of its use is outside of the loop.
The use is hoisted out of the loop thanks to the
extract-address-computations optimization.
To workaround this miscompile, this patch runs extract-address-computations after the multi-buffering. This matches what we do for the aligned matmul strategy.
Ultimately we should fix the pipelining such that it doesn't kick in if the related buffers are not multi-buffered.
TODO: Add a proper test case.

Tried it locally and I am afraid this actually disables all the interesting transformations re lowering to mma_sync, hoisting redundant transfers etc.
Let's connect Thursday on this and plan next steps.

We ended up working this one out by adding a pattern in MLIR to fold the problematic subview.
Nothing to land here.


Headers are not included in request

I have to use token to get file like below. But when i inspect the request i see that url is corect but token i gave isnt included. Are headers even supported or we just have to settle with url?
<PDFViewer document={{         url: process.env.API_AUTHENTICATION + 'downloadpdf',             httpHeaders: {            'Authorization': 'Bearer ' + getCookie('token'),             }, withCredentials: true,         }} />

The document prop has a connection field, you can try that one and add some headers in there. Also, to see what are the possible options of the document object you can refer to the react-pdf-js documentation (but carefully, refer to the version that is used in this package, not the latest one!)

Thanks. Along with some help that worked flawlessly. Here's the code that works:
<PDFViewer document={{
connection: {
url: process.env.API_AUTHENTICATION + 'downloadpdf',
httpHeaders: {
'Authorization': 'Bearer ' + getCookie('token'),
},
withCredentials: true,
}
}} />

Cool! I'll add it in the docs, thanks for using!


@ldl5007 breaks all of my code, take 1

edit site command is registered multiple times, but it used to only be registered once

we can't deregister commands through the brackets api :-1:


Fix typo

Hi @charliethinker, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

aspnetcore/fundamentals/routing.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@Rick-Anderson And in the first paragraph the statement "Requests look for a match in the route collection by . "  meaning is not clear.

Thank you for the catch


Update ja.json localization for new dialog and channel related events

Update ja.json localization for new dialog and channel related events

@chrismaltby No problems :)
If you prefer me to update the translations at a certain point of time, plz let me know. Otherwise, I will just update and send new PRs as new commits are created.