Add webui to latest

[ ]  ❗ [E500] node_modules found in repo. Please delete it
it's a visualization adapter, so it's needed
[ ]  ❗ [E519] "./dist/backend/main.js" found in package.json, but not found as file
look in the package under npmjs, the file is there
[ ]  ❗ [E603] NO "## Changelog" found in README.md
there is a changelog.md
[ ]  ❗ [E812] file test/ found in repository, but not found in .npmignore
there is /test
[ ]  ❗ [E813] file src/ found in repository, but not found in .npmignore
there is /src
[ ]  👀 [W171] "common.title" is deprecated in io-package.json
yeah, but every other packe still also contains it
[ ]  👀 [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
thought the release script will do this? i will not do manually
[ ]  👀 [W400] Cannot find "webui" in latest repository
??? don't understand this error

To answer questions asked at telegram:
Every new adapter will undergo an automatic revoew by adapter vhecker and a?manual review.  Please expect at least one or two weeks for a first review.
To minimize issues during review read the Readme of this repository carefully and check section requiremts for an adapter to be added to latest.

it's a visualization adapter, so it's needed

Why? node_modules includes unnecessary stuff.

there is a changelog.md

Some parts of the infrastructure/admin expect the most recent part of the changelog to be in the README. You can check how I solved in https://github.com/AlCalzone/ioBroker.zwave2/ - The last few entries are in the README, the rest automatically gets moved to CHANGELOG_old.md by the release script.

...npmignore

I recommend using the files field in package.json instead. Saying which files you want in the npm module instead of hoping you ignored all the ones you don't is less error-prone. Also the checker shouldn't complain then.

thought the release script will do this? i will not do manually

No. https://github.com/ioBroker/adapter-dev/ does, or just put the section in https://translator-ui.iobroker.in/ - only takes 2 minutes.

it's a visualization adapter, so it's needed

Why? node_modules includes unnecessary stuff. If you need those, look into a bundler, e.g. esbuild

no, my visu uses importmaps and no bundler. this is a architactural design decission

RE-CHECK!

RE-CHECK!

E500 will be part of review by Apillon77
W400 can be ignored of course for flatest PR

To E500
At the moment the inclusion of the node_modules folder could not be changed, as I'm not using a Bundler. Also it is not possible at the Moment to bundle the project, as how the loading of some of the modules happen in the webcomponent designer.
These may change in the feature when import attributes are supported by the platform and the bundlers. But also if someone uses HTTP2 the loading should be not so much slower, so I don't know if it is worth a bundling step.
And also, you could later add npm-packages to the designer, wich then also could depend on packages wich are included in the designer, this will not be possible when the designer is bundeld.

@Apollon77 Is it okay now with E500? I can nothing do about this...

Please wait until you get review feedback.
Your adapter is not the only one waitung.
Apollon77 will do a review as soon as he has time and report all things he thinks are important to fix.

RE-CHECK!

First of all - THANK YOU for the time and effort you spend to maintain this adapter.
I would like to give some (preliminary) feedback based on my personal oppinion. This is NOT an offical review and @Apollon77 might have several additional suggestions or even a different oppinion to one or the other statement. In addtion this revie ONLY refers to the backend / adapter part - the frontend / www part must be reviewed by @Apollon77.
Please feel free to contact him (or wait for a response from him) if you cannot follow my suggestsions or before you spend major effort.

[ ] errors reported by adapter checker must be fixed / evaluated
[E500] node_modules found in repo. Please delete it refers to  https://github.com/iobroker-community-adapters/ioBroker.webui/tree/master/www/node_modules. node_modules inside adapter direvctory are invalid. Whether a node_moduls directory insode www tree is acceptable must be evaluated / decided by @Apollon77.
So please wait for his statement regarding this point.

[ ] adapter has 'singleton' set to true / check compact attribute
As this adapter is allowed to have only one instance, creates subprocesses and seems to need significant resources please evaluate whether its really useful to enable compact mode for this adapter. Eventually set compact = false unless you see real benefits and have tested the adapter in compact mode.

[ ] reevaluate read/write attribute of states
All states defined at io-package.json have write attribute set to true. Its unlikely, that all those states are designed to operate as input for the adapter and should be written ba other adapters, i.e. state.npm is a feedback state used during npm installation - if I read the code correctly. (https://github.com/iobroker-community-adapters/ioBroker.webui/blob/b49e969ebb297e288a0316a506bd4d95da12ed51/io-package.json#L251)

[ ] onUnload code needs rewrite

https://github.com/iobroker-community-adapters/ioBroker.webui/blob/b49e969ebb297e288a0316a506bd4d95da12ed51/src/backend/main.ts#L201C1-L204C1
Rountine onUnload code must stop all running timers (seem none exist) and spawned subprocessed (i.e. npm installation). In addition onUnload must call the provide callback when completed. See templates or originally created adapter code for details.
In addtion evaluate the use of variable _onUnload. It is written once, but I did not find any usage.

[ ] adapt testing to supported node releases
Tests for node 16 is mandatory unless you require node 18 and higher (at package.json).
Tests for node 18 is mandatory as this is the recommended node version and node 16 will be eol and deprected Q3/2023.
Consider adding node 20 tests unless you already know incompatibilities.
So the recommended testmatrix is [16.x, 18.x, 20.x] or [18.x, 20.x] depending on engines requirments setting at package.json
As node 16 is end-of-life now, it's ok to remove node 16 from testing. In this case please require node 18 as minimum node version at package.json. Currently node 16 is required / allowed) but not tested.

In general I must state once more, that this review ONLY refers to the adapter / backend part. The frontend / www part need to be reviewed by @Apollon77.
Thanks for reading and evaluating this suggestions.
McM1957
Please add a comment when you have reviewed and fixed the suggestionsor at least commented the suggestions and you think the adapter is ready for a re-review!
Additional notess addressed at @Apollon77 - please consider them during your review

[ ] delivering node_modules below www
Please check whether delivering node_modules below www directory tree is ok or not and eventually adapterchecker should be adapted to handle this (if delivery is ok)

[ ] using state as command interface
Is using several states as command interface ok? Or wouldn't this be handled by message in a better way?

[ ] on the fly installation (running npm from adapter)
Is it ok that an adapter installs npm packages while the system is running?
Are there sufficient firewalls that the due to some error or user misuse the adapter cannot open scurity holes (i.e. installing anything without sufficient access rights of the user at the system) ?
Are there sufficient firewalls that npm installation does not interfere with oterh adapters or ioBroker core ?

[ ] complete frontend (www) including installation of npm and uploading needs review. I cannot check this due to missing knowhow in this area. Apollon77 please take this part.

First of all - THANK YOU for the time and effort you spend to maintain this adapter.
I would like to give some (preliminary) feedback based on my personal oppinion. This is NOT an offical review and @Apollon77 might have several additional suggestions or even a different oppinion to one or the other statement. In addtion this revie ONLY refers to the backend / adapter part - the frontend / www part must be reviewed by @Apollon77.
Please feel free to contact him (or wait for a response from him) if you cannot follow my suggestsions or before you spend major effort.

[ ]  errors reported by adapter checker must be fixed / evaluated
[E500] node_modules found in repo. Please delete it refers to  https://github.com/iobroker-community-adapters/ioBroker.webui/tree/master/www/node_modules. node_modules inside adapter direvctory are invalid. Whether a node_moduls directory insode www tree is acceptable must be evaluated / decided by @Apollon77.
So please wait for his statement regarding this point.
[ ]  adapter has 'singleton' set to true / check compact attribute
As this adapter is allowed to have only one instance, creates subprocesses and seems to need significant resources please evaluate whether its really useful to enable compact mode for this adapter. Eventually set compact = false unless you see real benefits and have tested the adapter in compact mode.

-> I have tested it, and most of the time the adapter does nothing. Only when you add or remove a NPM package

[ ]  reevaluate read/write attribute of states
All states defined at io-package.json have write attribute set to true. Its unlikely, that all those states are designed to operate as input for the adapter and should be written ba other adapters, i.e. state.npm is a feedback state used during npm installation - if I read the code correctly. (https://github.com/iobroker-community-adapters/ioBroker.webui/blob/b49e969ebb297e288a0316a506bd4d95da12ed51/io-package.json#L251)

-> not all, some of them (the onse for the files have none, it's only the npm state who is wrong, I fixed it)

[ ]  onUnload code needs rewrite

https://github.com/iobroker-community-adapters/ioBroker.webui/blob/b49e969ebb297e288a0316a506bd4d95da12ed51/src/backend/main.ts#L201C1-L204C1
Rountine onUnload code must stop all running timers (seem none exist) and spawned subprocessed (i.e. npm installation). In addition onUnload must call the provide callback when completed. See templates or originally created adapter code for details.
In addtion evaluate the use of variable _onUnload. It is written once, but I did not find any usage.

-> I look that I cancel the processes

[ ]  adapt testing to supported node releases
Tests for node 16 is mandatory unless you require node 18 and higher (at package.json).
Tests for node 18 is mandatory as this is the recommended node version and node 16 will be eol and deprected Q3/2023.
Consider adding node 20 tests unless you already know incompatibilities.
So the recommended testmatrix is [16.x, 18.x, 20.x] or [18.x, 20.x] depending on engines requirments setting at package.json
As node 16 is end-of-life now, it's ok to remove node 16 from testing. In this case please require node 18 as minimum node version at package.json. Currently node 16 is required / allowed) but not tested.

In general I must state once more, that this review ONLY refers to the adapter / backend part. The frontend / www part need to be reviewed by @Apollon77.
Thanks for reading and evaluating this suggestions. McM1957
Please add a comment when you have reviewed and fixed the suggestionsor at least commented the suggestions and you think the adapter is ready for a re-review!
Additional notess addressed at @Apollon77 - please consider them during your review

-> I will not add test for 16

[ ]  delivering node_modules below www
Please check whether delivering node_modules below www directory tree is ok or not and eventually adapterchecker should be adapted to handle this (if delivery is ok)

-> I wll not look into adapterchecker

[ ]  using state as command interface
Is using several states as command interface ok? Or wouldn't this be handled by message in a better way?

-> I would it have similar to vis, so I leave it like this

[ ]  on the fly installation (running npm from adapter)
Is it ok that an adapter installs npm packages while the system is running?
Are there sufficient firewalls that the due to some error or user misuse the adapter cannot open scurity holes (i.e. installing anything without sufficient access rights of the user at the system) ?
Are there sufficient firewalls that npm installation does not interfere with other adapters or ioBroker core ?

-> I could use Security of iobroker (if there is one), but yes it is needed like it is in the adapter.

[ ]  complete frontend (www) including installation of npm and uploading needs review. I cannot check this due to missing knowhow in this area. Apollon77 please take this part.

merged on error
Will create a new PR ...

PR https://github.com/ioBroker/ioBroker.repositories/pull/2589 created as replacement

To security once more:
The NPM Pakets wich are installed, are only searched and parsed, not run on the server. Only uploaded and then the code is run on the client. So I think not really a security concern.
Also the webui backend could be disabled, and only run when needed. It's only used for the NPM installation. I could think about that the client itself downloads the NPM and uploads to iobroker files, so not backend is needed at all. But this will not be done in next time.

please use PR https://github.com/ioBroker/ioBroker.repositories/pull/2589 created as replacement for further discussions.


broken basemaps

I updated the basemaps in an attempt to get broader study region coverage, use updated data, and better document the approach ... but they ended up looking quite wrong.  Not exactly sure why.
E.g. instead of city labels and general good representation, looks like this:

I attempted to use most up to date build and perhaps this was an error.  The most up to date on https://maps.protomaps.com/builds/ was 2024-10-21 (today) and uses v4.0.1 spec; previously I used 2023-10-12 or so and that was v3.x.x spec.  In fact, if I understand things rightly, v3 is the current support spec... so perhaps that is why things aren't working, because the format has changed and the library for reading and understanding the data (e.g. https://www.npmjs.com/package/pmtiles ) is still on v3?  I don't know if that's the right way of thinking about this, but might explain why things don't appear right.
In any case, things are not right hence this issue.
I'll try rolling back to a v3 version --- last date of which was 2024-08-12 and see if that does the trick.

This is as I thought above, and directly discussed in this thread:
https://github.com/protomaps/PMTiles/issues/463
I haven't yet fixed this though (despite attempting to roll back to 2024-08-12 that was still v3...).  More work to do.

Unclear why, but the styling appears to have spontaneously regressed... Has CloudFront cache-ing reset? It is very strange.  This issue appeared resolved about 24 hours ago, and now it is not, again.

So the issue here in a sense was one of caching, but more deeply its one of need for better naming conventions: I have been calling the basemap layer naively 'jibe_basemaps.pmtiles' --- but this doesn't provide important information: date of OpenStreetMap used in construction (e.g. 20231012, or 20241012), or specification of PMTiles that also varies over this period (v3.xx or v4.xx).  The latter is crucial as it requires different style definition files.  I initially opened this issue after updating basemaps and inadvertently advancing the map data to v4 while style definitions lagged on v3.  I then updated the map styles, however due to caching these hadn't kicked into effect.  I backtracked the data to v3 and all appeared well, I thought, but caching was out of sync still --- ended up with v4 styles on v3 data and a failure all round for it work.
Need to use both date and pmtiles schema in convention moving forwards, particularly for basemaps that rely on the stock layer style that matches the specification.
I will leave this issue open until at least the basemaps have their naming convention improved to include both date and specification version, and have confirmed that the configured style matches these.


future proofing sphp with semver and self-update

First of all, thanks for this useful script!
I found instructions to install it (via):
curl -L https://raw.githubusercontent.com/rhukster/sphp.sh/main/sphp.sh > /usr/local/bin/sphp
chmod +x /usr/local/bin/sphp

But when php 8.2+ comes out (assuming this script would be maintained and updated), I'll have to go figure out again where to grab the latest version.  And I noticed a few improvements that could be made to this respect

the README should contain install/update instructions.
there isn't any mention inside the sphp.sh file itself about where it came from or what version it is.
it would be amazing if there could be a self-update sub-command.

Updated README.md with some simple instructions


Cant search for music or videos or pictures on other drives

ℹ Computer information

Windows build number: 19042.423
PowerToys version: v.0.20.1
PowerToy module: powertoys run

📝 Provide detailed reproduction steps (if any)

… press alt-space
… search for mp3, mp4, jpeg etc
…

✔ Expected result
should see a list of media files
❌ Actual result
dont have any media files what so ever in mp3 or mp4 or jpeg etc etc for other drives, dont know id the OS drive works as i have no media files for that drive
You cant call it power toys if all its doing is replicating the search indexer, the search indexer doesnt index music or videos either, put it back to standalone like v19 which worked flawless for searching files

hi @boe323, thank you for the issue. Couple of questions:

are all your drives indexed
is this on a drive that is indexed?
Can you share a screen of both Powertoys Run in this state and your indexing options on Windows because I'm not able to repro this, typing mp3 brings up my mp3 files


Caption and Caption2 doesn't work

Message: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
Stack Trace: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at new NodeError (node:internal/errors:363:5)
at _write (node:internal/streams/writable:321:11)
at Socket.Writable.write (node:internal/streams/writable:334:10)

Duplicate of #70


Enable OVN IC CI

This will be removed once we're ready to default to OVN IC.
Relates-to: https://github.com/submariner-io/enhancements/issues/209

There seems to be an issue.
OVN IC:
2023-08-16T19:27:14.9265319Z Cluster settings::
2023-08-16T19:27:14.9266127Z   broker - 'cluster1'
2023-08-16T19:27:14.9266611Z   clusters - 'cluster1' 'cluster2'
2023-08-16T19:27:14.9267107Z   cni - ([cluster2]="" [cluster1]="" )

vs OVN:
2023-08-16T19:25:17.8719530Z Cluster settings::
2023-08-16T19:25:17.8720305Z   broker - 'cluster1'
2023-08-16T19:25:17.8720891Z   clusters - 'cluster1' 'cluster2'
2023-08-16T19:25:17.8721338Z   cni - ([cluster2]="ovn" [cluster1]="ovn" )

@dfarrell07 do we still have this issue? It would be great if we could get this merged as it can avoid any regression in ovn-ic.

Is this still relevant?

Is this still relevant?

yes this is important for us, now IC implementation is not getting tested in CI

Is this still relevant?

yes this is important for us, now IC implementation is not getting tested in CI

OK then I assume this should be planned for 0.17 so I moved it to the board.

Is this still relevant?

yes this is important for us, now IC implementation is not getting tested in CI

OK then I assume this should be planned for 0.17 so I moved it to the board.

Oh I see the enhancement is already on the board.


(CRASH) Exception generating new chunk

crash report
steps to reproduce:

press "create new world"
select worldtype "moderner beta"
select "1.0"
turn climatic biomes to "on"
edit biomes
create new world

Could you do this again and provide the full log? I can't exactly figure it out from the crash report.

okay this mod is completely broken now, it crashed when I didn't turn climatic biomes to on. here is the report and the log

Should be fixed in the next version.


Mobile support

This plugin feels unusable for someone who switches between mobile and desktop since the plugin won't work on mobile

#44


go to grandma's house

[ ] Request form
[ ] Fix title
[ ] Ask in Slack
[ ] JIRA issued
[ ] Prepare with the organizer
[ ] Setting the goal
[ ] Slides
[ ] Movies preparation
[ ] The day!
[ ] PDF release in SlideShare
[ ] Publish the movie
[ ] Subtitle to the movide
[ ] Publish the blog

Details of request

we couldn't


short hands

lint: work-around linter warning
add several new new checks and short-hands

This appear to have been laying around for a while...

Fixed typos.


Handle intervention end dates from intervention files

Automatically add end dates for interventions. When an endDate
field is specified in the interventions file, add that
automatically to the UI. There are a few caveates and assumptions
here:

Interventions can only be added and removed once. Interventions
cannot be applied multiple times.
The severest interventions will be removed first.

Now that states are starting to remove interventions, this change is going to be important.
Fixes https://github.com/covid-modeling/web-archive/issues/331

Interventions can only be added and removed once. Interventions
cannot be applied multiple times.

This is probably fine for now, but it may not be long before it becomes a problem for us.


[2201.3.x] Simplify the return type descriptor for verbose module IDs in refactor extract code actions

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Original PR - https://github.com/ballerina-platform/ballerina-lang/pull/38113
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@gayalkuruppu since we merged this to 2201.3.0-stage, there's no need to send this to 2201.3.x separately. 2201.3.0-stage is being synced to 2201.3.x frequently. Shall we close this?


Add QC controls to METexpress

Now that METexpress can plot both summary and aggregate statistics, we should add in the same QC controls that MATS has, which allow the user to filter points based on sub-data completeness and variance from the mean.

I think we only want the standard deviation filter on METexpress apps with scalar variables. It doesn't really make sense on the other statistics and could mislead people.

The standard deviation filtering is now working for METexpress. As previously stated, though, I'm going to look into only making those controls available on apps with scalar or precalculated stats.

This is done now.


fp16 or fp32 per channel image processing

Hi guys, I'm developing an open-source timewarp tool that runs within Autodesk Flame python subsystem and uses RIFE-2020. While looking for a faster backend then CPU-only currently avaliable in pytorch for MacOS I came across this implementation, managed to compile and test it and processing speed is promising. Thank you for the great and fast implementation!
While being rather novice amator in coding I briefly looked at the data types used and find quile a lot of assumptions for image channel data as "unsigned char". ncnn::VkMat seem to have it as 32bits, not sure about ncnn::Mat
The tasks we're working on in VFX field requires image channel data to be at least 16fp and to be processed without clamping negative values and preserving values over 1. This is currently achievable withing original RIFE pytorch implementation.
Do you think it is something that can be achieved with ncnn / vulkan, and if yes, could you please outline the areas in the code to potentially look at for such modification?
Thank you!

After playing around a bit:
ncnn::Mat::from_pixels() produce non-normalized result, float values is not within 0-1 range. Scaling it up and down produce the result that is close to original. Some clipping occures in high values though. The resulting image appears slightly brighter overall wich is not the case with original implementation

The clamping seem to happen in fusionnet. It i in the original RIFE-2020 code as well but can be easily commented out. Could you please share the process you guys using to convert the model to bin and param file as it would be very helpful in this case to get rid of clamping, thank you!


[1.3]  Linux platform, OTA speed is very slow, how to get better speed

Reproduction steps
The OTA-provider sample can work fine, And using the wifi/Ethernet to transmit data. but the speed of it is sadly slow, I have a 77mb *.ota file, and it made alomst 3 hours how can I resolve this situation, thank you guys very much!!
My platform is Linux platform.  OTA Provider and request are running on different Linux platform (Soc i.MX93 or i.MX8MM)
#provider
chip-ota-provider-app --discriminator 22 --secured-device-port 5565 --KVS /tmp/chip_kvs_provider --filepath /home/root/thermostat-app.ota &
#request
chip-ota-requestor-app --discriminator 18 --secured-device-port 5560 --KVS /tmp/chip_kvs_requestor --periodicQueryTimeout 60 --otaDownloadPath /home/root/download.bin
Even if I add  -P 5 to decrease the polling time, but the speed didn't improve.
chip-ota-provider-app --discriminator 22 --secured-device-port 5565 --KVS /tmp/chip_kvs_provider --filepath /home/root/thermostat-app.ota  -P 5&
[1713415243.648261][1468:1468] CHIP:ATM: ReceiveInit
[1713415243.648271][1468:1468] CHIP:ATM:   Proposed Transfer Control: 0x20
[1713415243.648281][1468:1468] CHIP:ATM:   Range Control: 0x0
[1713415243.648291][1468:1468] CHIP:ATM:   Proposed Max Block Size: 10240
[1713415243.648301][1468:1468] CHIP:ATM:   Start Offset: 0x0000000000000000
[1713415243.648311][1468:1468] CHIP:ATM:   Proposed Max Length: 0x0000000000000000
[1713415243.648321][1468:1468] CHIP:ATM:   File Designator Length: 29
[1713415243.648331][1468:1468] CHIP:ATM:   File Designator: /home/root/thermostat-app.ota
[1713415243.650419][1468:1468] CHIP:BDX: OutputEvent type: InitReceived
[1713415243.650440][1468:1468] CHIP:ATM: Sending BDX Message
[1713415243.650451][1468:1468] CHIP:ATM: ReceiveAccept
[1713415243.650460][1468:1468] CHIP:ATM:   Transfer Control: 0x20
[1713415243.650470][1468:1468] CHIP:ATM:   Range Control: 0x0
[1713415243.982741][1468:1468] CHIP:ATM:   Max Block Size: 1024
[1713415243.982754][1468:1468] CHIP:ATM:   Length: 0x0000000000000000
The Max Block Size is limited to 1024.   only 10KB data can be transferred in one second.
Bug prevalence
Whenvever I do this.
GitHub hash of the SDK that was being used
1.2 /1.3
Platform
IMX8
Platform Version(s)
No response
Type
Core SDK Performance Improvement
Anything else?
No response

I have the same problem. I use efr32mg24.

I also have same problem to transfer chip-ota-requestor-app-v2.ota(About 92M) that I made via ota_image_tool.py for testing TC-SU-3.2   as a OTA Provider/Controller DUT. It takes long time over 2hours to download now.
How can I reduce downloading time?
Can we change the Max Block Size in chip-ota-requestor-app or Any thing else?
Advise me if you have any solution plz.

No idea for Linux, sorry.  You could try using nm and the like to try to investigate why the binary is as big as it is....

Added NXP tag due to usage of ota_image_tool.py. @doru91

The original bug seems to be for iMX ... so assuming this is general NXP rather than linux?

@Trishia , @GnarFang for the large binary size, could you confirm if you ran strip on it?
I ran a short test on my machine and the size went from 95MB to 4.5MB for otarequestor (although that is probably not the image that should be OTAed)

Thanks!!! @andy31415
I didn't know about strip before. As a result, I could reduce the size of chip-ota-requestor-app to 1.5M with Optimization options that I mentioned above (https://github.com/project-chip/connectedhomeip/issues/33039#issuecomment-2406611066).
ubuntu@raspberrypi:~/connectedhomeip/out$ ls -alh
total 4.3M
drwxrwxr-x  3 ubuntu ubuntu 4.0K Oct 14 16:21 .
drwxrwxr-x 21 ubuntu ubuntu 4.0K Oct 11 15:16 ..
-rwxrwxr-x  1 ubuntu ubuntu 1.5M Oct 14 16:03 chip-ota-requestor-app-v2
-rw-rw-r--  1 ubuntu ubuntu 1.5M Oct 14 16:16 chip-ota-requestor-th-v2.ota


redirect to homepage in mintbase wallet in consumer apps

coverage: 83.826%. remained the same when pulling 19d5c1229963b8303f622c1090747c27b1c6c559 on change-mbwallet-redirect into 6092e621f245ff860552612be109e0e3fab31e8e on feat-add-wallet-package.


How to create Windows executable?

Dear Tidepool community :-)
I would ask you if there is a way to create a windows executable? I am able to get the uploader run on windows 10 as described in the Readme (with npm run dev). However, i am wondering how to create an executable and start it as standard windows application?
I know, i can download the Uploader and install it. But i would like to do it myself :-)
Thanks
Patrik

Hi @usko1 ! You should be able to do this using yarn package. Let me know if you run into any issues.

Great, thanks. It worked. I assume it is the same for mac, right?

Some things to try:

make sure you're using Node v12.13.0
remove the node_modules folder in both the main directory and  app
run yarn in the main directory to install the modules
try running yarn dev and/or yarn package again


Tutorials

name: Tutorial Pull Request
about: Add tutorial for user_defined_templates.v
Motivate of the pull request

[ x] To address an existing issue. If so, please provide a link to the issue.
[ ] Breaking new feature. If so, please decribe details in the description part.

Describe the technical details

What is currently done? (Provide issue link if applicable)
What does this pull request change?
This adds the user_defined_templates.v tutorial

Which part of the code base require a change
In general, modification on existing submodules are not acceptable. You should push changes to upstream.

[ ] VPR
[ ] OpenFPGA libraries
[ ] FPGA-Verilog
[ ] FPGA-Bitstream
[ ] FPGA-SDC
[ ] FPGA-SPICE
[ ] Flow scripts
[ ] Architecture library
[ ] Cell library

Checklist of the pull request

[ ] Require code changes.
[ ] Require new tests to be added
[x ] Require an update on documentation

Impact of the pull request

[ ] Require a change on Quality of Results (QoR)
[ ] Break back-compatibility. If so, please list who may be influenced.

Look good to me. Will merge.


Question: can nyc be controlled while it is collecting code coverage data?

I'm starting to use nyc to measure code coverage with my Node-based server system under Linux. I'm using a custom test system that stimulates the server and evaluates results. I'd like to have nyc trace coverage while the testing runs, but at the moment I have to restart the nyc/server system before starting tests, and exit after every set of tests to generate the code coverage report.
I'd like to leave the server system running continuously, and without restarting a) reset the statistics, and b) trigger generation of the coverage report. This could be done internal to the server code (perhaps by calling Istanbul functions), or external to the server (perhaps by sending signals).
Is there a way to a) reset the code coverage statistics, and b) trigger writing of the coverage report(s), without exiting and restarting the whole system?
(Previously posted at https://github.com/gotwarlost/istanbul/issues/875 ...)

Hi @dtgriscom sorry for the late reply, this sounds a bit similar to #597, and in the same way sounds really complex and a bit beyond the scope of what nyc is trying to do. You are more than welcome to try to take a crack at a PR or writing your own library/extensions to nyc :)

Thanks for the response. I'm not surprised, and unfortunately you won't be surprised to hear I'm unlikely to be able to submit a PR...
Thanks for the cool tool,
Dan

There's also #607 which is tangentially related. To accomplish:

Is there a way to a) reset the code coverage statistics, and b) trigger writing of the coverage report(s), without exiting and restarting the whole system?

You could try messing around with the internals of nyc but there isn't an official programmatic API atm so I'm not sure this is possible.


[Usage]: Is there any way to hook features inside vision-language model?

Your current environment
Initialize the LLaVA-1.5 model
llm = LLM(model="llava-hf/llava-1.5-7b-hf")
print(llm)
#embed_last_hook = Hook(model.language_model.model.norm) # for save embed
Define the prompts and images
base_p = '../../../data/detect/coco/train2017'
img_p1 = os.path.join(base_p, '000000265292.jpg')
img_p2 = os.path.join(base_p, '000000318124.jpg')
img_p3 = os.path.join(base_p, '000000370121.jpg')
prompts = [
{"prompt": "USER: \nWhat is the content of this image?\nASSISTANT:", "multi_modal_data": {"image": PIL.Image.open(img_p1)}},
{"prompt": "USER: \nWhat is the content of this image?\nASSISTANT:", "multi_modal_data": {"image": PIL.Image.open(img_p2)}},
{"prompt": "USER: \nWhat is the content of this image?\nASSISTANT:", "multi_modal_data": {"image": PIL.Image.open(img_p3)}}
]
Define sampling parameters
sampling_params = SamplingParams(temperature=0.0, top_p=1.0)
Generate outputs
outputs = llm.generate(prompts, sampling_params=sampling_params)
I want to add hook some features when llm's forward finished
how can i get feature inside?
How would you like to use vllm
I want to run inference of a [specific model](put link here). I don't know how to integrate it with vllm.

Perhaps you can try nn.Module's hook

import torch
class Hook:
def init(self, module):
self.hook = module.register_forward_hook(self.hook_fn)
self.output = None
def hook_fn(self, module, input, output):
    self.output = output

def close(self):
    self.hook.remove()

def load_captioning_model(model_id):
quantization_config = BitsAndBytesConfig(load_in_8bit=True)
model = LlavaForConditionalGeneration.from_pretrained(model_id, low_cpu_mem_usage=True, quantization_config = quantization_config)
processor = AutoProcessor.from_pretrained(model_id, pad_token="")
return processor, model
model_id = "llava-hf/llava-1.5-7b-hf"
processor, model = load_captioning_model(model_id)
embed_last_hook = Hook(model.language_model.model.norm) # for save embed
embed_last_hook.output  # (1, 4096)
When I use this code ( with HuggingFace ), i can get 1,4096's embed
But I got Another result below ( with vllm ),  torch.Size([596, 4096])
from vllm import LLM, SamplingParams
llm = LLM(model="llava-hf/llava-1.5-7b-hf")
D_HOOK = Hook(llm.llm_engine.model_executor.driver_worker.model_runner.model.language_model.norm)
D_HOOK.output # (596, 4096)
I want to get same features at huggingface. What should i do? and what is different between this ?

HuggingFace's model

Vllm's model


Fix pluralization for relationship types in JSON API serializer

See #86

Thanks for the PR!
(Babel seems to be having problems, merged anyways since it looks good)

Yeah, I had the same problems locally. Looks like it needs to be fixed at Babels side of things.

I updated the tests as well, your changes are now published.

Awesome! Thanks for the quick responses. You got yourself a new contributor. Love the project!


how to Archive Zip file from FromDirectory

your Example said
using (var archive = ZipArchive.Create()) { 	archive.AddAllFromDirectory(@"C:\source"); 	archive.SaveTo(@"C:\new.zip"); }
[https://github.com/adamhathcock/sharpcompress/wiki/API-Examples#archive-random-access-api-example]
but,I don't file the AddAllFromDierctory in ZipArchive.Create()

It's an extension method.  Search the source.


add composite Objects example

This is the Composite objects example added into Object folder taken from processing website

Why are some of the constructors using constructor functions while others use class?

hi @limzykenneth actually I have done this in one place because when constructor and function name is not same. you will see this in example the class name ring and function name is not the same. if you think this is not right so, please suggest me.

I'm not sure I understand. What I'm asking is that why for example the following:
Egg = function(xpos, ypos, t, s) {
  // etc...
}

is using constructor function and not ES6 class syntax like so:
class Egg{
  constructor(xpos, ypos, t, s){
    // etc...
  }
}

I think both of the things are working as same. if you want then I remove this from es6 class syntax.

Yes, they are more or less the same, which is why I'm wondering why for Egg and EggRing you used constructor functions but for Ring you used class syntax. If there is no particular reason to have them as constructor functions can you change them to use class syntax?

okay, I will change this.
Thanks

Can you please check this pr. I will make the changes that you suggest to me.

looks good now, thanks @17bcs029

Thanks, @lmccart for merging this pr.


Fixed #28215 -- Marked passwords as sensitive variables.

Trac ticket number

ticket-28215
Branch description
Marked passwords as sensitive variables, furthermore, marked some post parameters as sensitive. Finally, tests were added to test both of these.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.

Ahh okay, thanks for looking at my PR, I'll begin adding tests for those

Hi @sarahboyce, I've added the tests, could you review them for me please? Also sorry about the mess of commits

Yeah, you're right, I would expect those to pass as well, but I theorise that the test functions that the variables go through (during testing) are the ones that leak the sensitive data.
For example, if you go back to the test project that the ticket author made and run the tests with the modifications to ONLY the forms.py file (ie. excluding the sensitive variables wrappers from client.py), the tests there pass, yet when you implement the same test in test_auth_backends.py (checking if the sensitive data is in the file, not just that it is hidden in a single function), it fails because of test functions like Client.post and RequestFactory.post leaking sensitive data.
Should we hide these functions that may be used for testing purposes?

Yeah, you're right, I would expect those to pass as well, but I theorise that the test functions that the variables go through (during testing) are the ones that leak the sensitive data.

You were right. I did some tweaks to make this work :+1:

@GappleBee do you think all the sensitive variables in Django core are now covered?
If not, I will update the commit message and make sure the ticket remains open after this lands :+1:

Extra testing functions that are called during testing shouldn't impact the tests anymore, can you have a look at this @sarahboyce ?

I expect that the PasswordResetForm email context is sensitive also


Issue with LLMS and Memgraph docker compose

Document the issue from discord thread: https://discord.com/channels/842007348272169002/890968976627228752/1215640019168006205

@antejavor I was unable to reproduce the error. I've tried using Ollama both as a desktop app and within the Docker container. I've also used Docker and Docker compose to run the Memgraph MAGE docker image. Closing the issue. We can reopen if we get additional data.

As mentioned by the user host.docker.internal is needed on Mac or Windows if you have Lab running as a separate container from Memgraph/Memgraph MAGE. This should be noted here as well, as we talked about it on Slack (not sure where you added it, but I would add it to Docker Compose and GraphChat as the user mentioned).

It is mentioned at https://memgraph.com/docs/getting-started/install-memgraph/docker#issues-when-connecting-to-memgraph-lab-to-memgraph.
This looks like an issue that has too many variables that influence the setup and results (OS, install method of Memgraph and Ollama, etc.). I think that the best approach for now would be to add Callouts to Docker Compose and GraphChat pages and to mention something along the lines "If you are having issues with connecting, try to use host.docker.internal instead of localhost or <IP_ADDRESS>.".
I'll prepare PR for this.


Handle light vs deep integration of Electron

With the current implementation of electron-wrapper, launching the command quasar wrap electron simply creates a project structure to launch an Electron shell and executing the packaged application inside of it without deep integration (no access to Electron's renderer API).
I imagine two ways to solve this issue:

Add option to set light vs deep Electron integration to quasar wrap electron command (quasar wrap electron --deep/light).
Make quasar dev/build commands on project root folder (not electron/)  more explicit, in order to better handle Electron integration (quasar dev/build electron --deep/light instead of previous quasar dev)

In both cases, with deep integration I mean changing or adding to the webpack conf the target electron-renderer and electron package in dependencies inside package.json of root project. With light integration I mean the current mode (just Electron shell executing an URL without accessing to Electron API).
My personal choice would be no.2, because it should allow us to change dynamically the webpack config to handle both cases without changing code, so that the same codebase could be used for browser (quasar dev/build), Electron (quasar dev/build electron) or Cordova (quasar dev/build cordova).

I noticed that current implementation of electron-wrapper does not allow (by default) that I use Node.js Libraries (ex.: File System) inside my components. A deep integration will help with this limitation ?

@lucascampelo, although it has been two months I thought I'd still reply. Yes, setting 'target: electron-renderer' will allow usage of File System. As the suggested deep integration adds this target it would solve the problems. I think however it is better to have a separate webpack file as it still allows browser version's and use try-catch to check for 'fs' availability.

@Emptyless
I set 'target: electron-renderer' and also modified resolve to add modules: resolve('electron/node_modules'), and what i want to do is using ipcRenderer to control the main window like close it.
but nothing happened when i call ipcRenderer.send('window-all-closed')
here is the code:
import { ipcRenderer } from 'electron' // ....and methods: closeWindow () {   ipcRenderer.send('window-all-closed') }
any one can give me some suggestion?


Apply along axis dtype shape

@d-v-b this should solve the merge conflict in https://github.com/dask/dask/pull/3742

I might not merge this because It looks like we resolved the same conflict nearly simultaneously, as of 51d803d in this fork. Assuming the tests pass on master, I think it should be OK to leave this PR out.

Indeed. I also pushed some lines that weren't supposed to be there and that causes other conflicts. Closing this.


Use latest ruby version in ci

I updated some Ruby version.
And, I think Ruby2.4.1 spec should pass always.

Thanks, I'd already made all the pulls to the individual repos off my own but forgotten to push. The removed "failure" is just clean up, has no affect as we're running a different version of 2.4, so I won't repush those.


⚠ Bofrost.lu has degraded performance

In 4173b49, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 807 ms

Resolved: Bofrost.lu performance has improved in cfc5992 after 13 minutes.


Lr_scheduler step where to use , warning

    i want to use the the lr scheduler for gan and i am trying to figure out where to give the lr_scheduler_dis.step()

if i add it in training_step after loss is updated i am getting an warning which i want to fix
Warning: Detected call of lr_scheduler.step() before optimizer.step(). In PyTorch 1.1.0 and later, you should call them in the opposite order: optimizer.step() before lr_scheduler.step().  Failure to do this will result in PyTorch skipping the first value of the learning rate schedule. See more details at https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rate
def _gen_step(self, real_images, conditioned_images, scalar_gen, scalar_dis, aux_labels):
    # Pix2Pix has adversarial and a reconstruction loss
    # First calculate the adversarial loss
    # gen_opt = self.optimizers()

    fake_images = self.gen(conditioned_images, scalar_gen)
    dis_logits, aux_output = self.dis(fake_images, conditioned_images, scalar_dis)

    adversarial_loss = self.adversarial_criterion(dis_logits, torch.ones_like(dis_logits))
    criterion_loss = self.criterion(aux_output, aux_labels)#labels need to add
    error_fake = adversarial_loss + criterion_loss #adding real loss and criterion loss from labels
    error_fake.backward(retain_graph=True)#here not sure where to place this

    self.log("6_error_fake_gen", error_fake)
    self.log("2_Generator_adver_Loss", adversarial_loss)

    # calculate reconstruction loss
    recon_loss = self.recon_criterion(fake_images, real_images)
    lambda_recon = self.lambda_recon
    self.log("3_Generator_recon_Loss", recon_loss)

    gen_loss = adversarial_loss + lambda_recon * recon_loss

    # gen_opt.zero_grad()
    # self.manual_backward(gen_loss)
    # gen_opt.step()

    return gen_loss

def _dis_step(self, real_images, conditioned_images, scalar_gen, scalar_dis, aux_labels):
    # dis_opt = self.optimizers()#turinign of auto opt need to specify opt manually
    fake_images = self.gen(conditioned_images, scalar_gen)
    fake_logits, _ = self.dis(fake_images, conditioned_images, scalar_dis)

    real_logits, aux_output = self.dis(real_images, conditioned_images, scalar_dis)

    fake_loss = self.adversarial_criterion(fake_logits, torch.zeros_like(fake_logits))
    real_loss = self.adversarial_criterion(real_logits, torch.ones_like(real_logits))

    criterion_loss = self.criterion(aux_output, aux_labels)#labels need to add
    error_real = real_loss + criterion_loss #adding real loss and criterion loss from labels
    error_real.backward(retain_graph=True)#here not sure where to place this
    self.log("7_error_real_dis", error_real)

    accuracy = self.compute_acc(aux_output, aux_labels)

    self.log("4_Discriminator_fake_Loss", fake_loss)
    self.log("5_Discriminator_real_Loss", real_loss)
    self.log("7_accruracy", accuracy)

    dis_loss = (real_loss + fake_loss) / 2

    # dis_opt.zero_grad()
    # self.manual_backward(dis_loss)
    # dis_opt.step()
    return dis_loss #, error_real

def configure_optimizers(self):
    dis_opt = torch.optim.Adam(self.dis.parameters(), lr=self.learning_rate)
    gen_opt = torch.optim.Adam(self.gen.parameters(), lr=self.learning_rate)
    #learning rate scheduler
    #https://medium.com/mlearning-ai/make-powerful-deep-learning-models-quickly-using-pytorch-lightning-29f040158ef3
    self.lr_scheduler_dis = torch.optim.lr_scheduler.StepLR(dis_opt, step_size  = 10 , gamma = 0.5)
    self.lr_scheduler_gan = torch.optim.lr_scheduler.StepLR(gen_opt, step_size  = 10 , gamma = 0.5)

    return dis_opt, gen_opt

Originally posted by @msverma101 in https://github.com/Lightning-AI/lightning/issues/3051#issuecomment-1259411718

Hi
I see you are using manual optimization. You need to call the lr scheduler's step manually, after the optimizer step, but I can't see that in your code.
Make sure this code is not commented!
    gen_opt.zero_grad()
    self.manual_backward(gen_loss)
    gen_opt.step()
    self.lr_scheduler_gen.step()   # <---- add this

And also here:
    dis_opt.zero_grad()
    self.manual_backward(dis_loss)
    dis_opt.step()
    self.lr_scheduler_dis.step()   # <---- add this

Another note:
The best practice in Lightning is to return the schedulers from your configure_optimizers() like so,
def configure_optimizers(self):
    ....
    return [dis_opt, gen_opt], [lr_scheduler_dis, lr_scheduler_gen]

and then access them in your training step:
lr_scheduler_dis, lr_scheduler_gen = `self.lr_schedulers()`

Documentation


Pass the default process timeout from the main process to the subprocesses that build the projects

If we invoke project_subbilder.build() immediately on the subprocess, it gets a fresh set of global variables and thus also uses the standard default timeout of 10 minutes, ignoring any timeout that was specified using --default-timeout. And 10 minutes is not enough to stress test a project.

@swift-ci Please test

That’s really interesting. I can’t imagine ACHNBrowserUI finishing stress testing in 10 minutes (it’s more on the order of 2 hours). But anyway, let’s hope it’s fixed now.


Telugu Letter Pa incorrect split

The character combination U+0C2A, U+0C41, U+0C2A splits up into 2 graphemes, whereas my display only shows 1 grapheme:
var x = "ప" + "్" + "ప";
console.log(x)
console.log(new (require('grapheme-splitter'))().splitGraphemes(x))

gives
ప్ప
[ 'ప్', 'ప' ]

Yes, see answer to this similar issue:
https://github.com/orling/grapheme-splitter/issues/12


Reduce thread contention in subgraph indexing

Plan as outlined in https://github.com/graphprotocol/graph-node/issues/856#issuecomment-491342191:

[ ] Set the tokio threadpool size to 100.
[ ] Solve #905 by moving all store operations into a separate, blocking threadpool, and have them return futures. This is not hard but it's laborious and will have a big diff.
[ ] Try going back to the default threadpool size.

Since increasing the size I still see 1ms and 10ms contention warnings, but no 100ms which is an improvement, contention seems to have shifted to the DB connection pool which was expected. Still the situation in tokio is not great, probably due to the issue described in https://github.com/tokio-rs/tokio/issues/426#issuecomment-493710173.

What's the latest here? Didn't we add the blocking threadpool recently?

I believe we've sufficiently mitigated this issue that it shouldn't have any practical effect, but the solution is not ideal, so I'd like to keep this open. My explanation for the thread pool contention warnings that can still be observed sometimes is that half of them are due do this bug (fix isn't released yet) and the other half is simply that there is contention for the CPUs, I haven't confirmed this yet, but it would be an ops concern, so I'm removing the label from this issue.


[FEATURE] UniFi OS 2.X support

Support UniFi OS 2.X using LEGO binary https://github.com/go-acme/lego/

The paths of the certs were changed.
The new paths are the following:
UniFi OS cert: /data/unifi-core/config/unifi-core.key and /data/unifi-core/config/unifi-core.crt (there is an additional cert located at data/unifi-core/config/unifi-core-direct.crt and data/unifi-core/config/unifi-core-direct.key. This cert is for cloud access)
Java Keystore for UniFi guest portal: /data/unifi/data/keystore


Elasticsearch adaptor requires port in configuration

Was having an issue trying to transport data from Mongo to AWS ES, couldn't figure out why the command wasn't working since I got no errors and the process exited w/ 0.
didn't import, no errors etc:
...
awselasticsearch:
  type: elasticsearch
  uri: http://my-es.amazon.aws.com
...

working:
...
awselasticsearch:
  type: elasticsearch
  uri: http://my-es.amazon.aws.com:80
...

Actually, I looked around the elastigo code a bit, and it just defaults the port to 9200, might be worth adding this to documentation.

the SampleConfig shows the expected format of the uri parameter


Preserve Query in nextUrl during openid login redirect

Description
Successful Openid Login redirects back to the URL, from where the login was initiated.
Category
Bug fix
Why these changes are required?
Bug was reported: https://github.com/opensearch-project/security-dashboards-plugin/issues/1823 and https://github.com/opensearch-project/security-dashboards-plugin/issues/2119
What is the old behaviour before changes and new behaviour after changes?
The changed behaviour is best explained by following user-flow

User is not logged in
User clicks on a shared Dashboard Link
User is redirected to configured Openid IDP
After successful login, user is redirected to

Before:  /app/dashboards
After: /app/dashboards#/view/....

Optional: When Multitenancy is enabled, the tenant from the link was discarded before and is now kept.

The whole functionality is basically ported from the SAML login method.
Issues Resolved
Fix: https://github.com/opensearch-project/security-dashboards-plugin/issues/1823
Fix: https://github.com/opensearch-project/security-dashboards-plugin/issues/2119
Testing
Existing Tests pass
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@KleinSebastian Can you add a test to go along with the changes being introduced in this PR?

@cwperks I added a set of unit tests for the handleUnauthRequest call. E2E Tests for the functionality are unfortunately not working on my machine, so I skipped them. If you insist upon Cypress Tests I will try my best to do it on another machine.

@KleinSebastian There are a few test errors. Are these errors due to changes from this PR or was there a change in OSD that introduced these errors?

@cwperks I was able to reproduce the error. It was an issue with updating the "security_authentication" cookie due to the mismatch of "localhost" and "<IP_ADDRESS>" between OSD and Keycloak, resulting rejection of set-cookie in the browser due to the default SameSite behaviour "Lax".
Fixing the configuration does fix the E2E Tests as well as the need for a second redirect the existing E2E Tests.

@cwperks I was able to reproduce the error. It was an issue with updating the "security_authentication" cookie due to the mismatch of "localhost" and "<IP_ADDRESS>" between OSD and Keycloak, resulting rejection of set-cookie in the browser due to the default SameSite behaviour "Lax".
Fixing the configuration does fix the E2E Tests as well as the need for a second redirect the existing E2E Tests.

Awesome. Thank you. I just approved the CI checks to run again. We will get results in ~45min - 1 hr

@cwperks I saw that the E2E test runs failed again, but this time the OSD Server did not even start properly. I also saw that I introduced unwanted line ending changes. I reverted them because this might be the reason for the not starting server.

@cwperks I saw that the E2E test runs failed again, but this time the OSD Server did not even start properly. I also saw that I introduced unwanted line ending changes. I reverted them because this might be the reason for the not starting server.

I just started the CI checks again.

OSD is still not starting, I assume that the server is not able to contact Keycloak by using the "<IP_ADDRESS>" address and exits. I reverted the changes done to the E2E Setup and tried fixing the tests with the manual redirect workaround present in the existing tests.

@cwperks Are there some additional actions required from my side? Its my first time performing a PR on a public repo, so I'm a bit unsure about the process.

The PR needs 2 maintainer approvals and some are out of the office this week. @DarshitChanpura or @RyanL1997 could you take a look at this PR?


Kubernetes Events preset

Opening an issue for discussion, we could use k8sobjectsreceiver to watch Kubernetes Events and add a preset similiar to Kubernetes logs preset.
One caveat the receiver k8sobjectsreceiver  is alpha stability.
Thoughts?
Reference: https://github.com/open-telemetry/opentelemetry-helm-charts/issues/381
cc @nicolastakashi

Just a small note!
The k8seventsreceiver we're planning to add as a preset as described on the issue as reference is still an ALPHA receiver, maybe should be something we must highlight to the user that may have breaking changes in the future.

I support adding a preset for k8sobjectreceiver with a clear warning, both in the values.yaml and in NOTES.txt that the component is alpha.

@povilasv and @TylerHelmuth I'm going to prepare a PR for this.

@povilasv we can close this 😄


WSGI and Nginx for DanceCat

Add document about publishing DanceCat using WSGI and Nginx.

Done in #46


list table name in non case sensitive alphabetical order

When create many tables successively, table name should list in alphabetical order, like most database tools do, eg: DbVisualizer.
Otherwise, the disorder(the table create order) list make people really crazy when they wanna find some tables, it looks weird and dizzy.

+1, please merge!
Also, I like the addition of re-selecting table on refresh, since refresh is needed every time the app is re-launched.


⚠ Bofrost.at has degraded performance

In 23b932c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1699 ms

Resolved: Bofrost.at performance has improved in 195205f after 36 minutes.


OAuth Support without --link

Please provide a way to login with e.g. Github like in your Cloud Program, but without using the Cloud Program. A list of ways to do it ourself is I think good too

We don't have any plans on adding additional authentication methods so we recommend using an external oauth proxy.
We mention that briefly here: https://github.com/cdr/code-server/blob/v3.8.0/doc/FAQ.md#how-should-i-expose-code-server-to-the-internet
But I think we might be able to  reword this section to make it more discoverable, maybe something like "authentication methods"?

We don't have any plans on adding additional authentication methods so we recommend using an external oauth proxy.
We mention that briefly here: https://github.com/cdr/code-server/blob/v3.8.0/doc/FAQ.md#how-should-i-expose-code-server-to-the-internet
But I think we might be able to  reword this section to make it more discoverable, maybe something like "authentication methods"?

So I would Listen white Caddy on Port 80,443 then Pass that SSL Encrypted to the OAuth Proxy, there I login and then it gets passed to the CodeServer on port 8080

So I would Listen white Caddy on Port 80,443 then Pass that SSL Encrypted to the OAuth Proxy, there I login and then it gets passed to the CodeServer on port 8080

I got Oauth2_Proxy to work, which works just fine, so maybe adding a bit to the docs, but not more because you are completely right

I got Oauth2_Proxy to work, which works just fine, so maybe adding a bit to the docs, but not more because you are completely right

See https://www.pomerium.io/guides/vs-code-server.html


Deadlock in HelixTasks

Dump shows two helix tasks are waiting each other.

Example build: 507030, see "Unix_Debug_CoreClr / Test_Linux_Debug" leg
Example PR: https://github.com/dotnet/roslyn/pull/71332

The "known issue" template is incorrect for this type of report. I've edited the original post to remove those bits.


Where are they now feature: NC Food Inspector

Get content to highlight past success stories from our events

Unable to get content


Laravel Updater

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v7.15.0 branch.
Before merging, you need to:

Checkout the shift-ci-v7.15.0 branch
Review all pull request comments for additional changes
Run composer update
Test your application (no tests?)

:warning: You are running version 6.5.4 of consoletvs/charts. The latest version is 7.0.0. You should review this dependency to see if you can upgrade to the latest version.

:information_source: You are running an older version of Laravel. The latest version is 7.15.0. Run the Laravel 7.x Shift to upgrade to the latest version of Laravel.

:warning: You are running version 10.7.1 of laravel/cashier. The latest version is 12.0.0. You should review this dependency to see if you can upgrade to the latest version.

:warning: You are running version 0.8.1 of tightenco/ziggy. The latest version is 0.9.4. You should review this dependency to see if you can upgrade to the latest version.


Add highlightjs to dependencies

This package is dependent on highlightjs but not in bower.json's "dependencies" field.

Hi @asnowwolf ,
Though the highlightjs dependency is actually removed in #28 , it seems so many people asking about this.
So I guess I'll just add it back this weekend. Thanks for the opinion.

Well, I changed my mind after checking out on the bower package's github repo.
It has one huge packed highlight.js with all languages included, and usually you'll only use one or two of them. This adds so much overhead to the network transfer and javascript parsing.
Size difference:

fully packed: 438KB
basic: 42.4KB

So I recommend that you just stay with the suggested way to include highlight.js described in README.

There's currently no official bower package of highlight.js (see here). You should either build highlight.js yourself or use the pre-built one on cdnjs.

Closing the issue.


Add Switch Transformer implementation

Hi @fchollet and @apoorvnandan -
I extended the Text Classification with Transformer to add Switch Transformer implementation. I restructured the example to allow running two experiments: 1) with the standard Transformer block, and 2) with the Switch Transformer. In addition, I changed the Transformer block implementation to allow either 1) having a standard feedforward network, or 2) having a Switch layer.
I was thinking of creating a separate example, but I though it would be better to have a single example with both implementations. Happy to move it to a separate one.
Let me know what do you think.
Cheers

Thanks for the PR!

I was thinking of creating a separate example, but I though it would be better to have a single example with both implementations. Happy to move it to a separate one.

I think "text classification with Transformer" and "text classification with Switch Transformer" are different enough that it makes sense to have 2 separate examples instead of just one. This will also allow us to keep the original example as short and simple as possible.

@fchollet - I have split the examples now. Cheers

@fchollet - Thanks a lot for your comments. I addressed them
Let me know if you have any further ones

@fchollet - Thanks for your review. I have added the generated files.

Awesome, thank you! 👍


fix _debugCheckOwnerBuildTargetExists; sync localizations and tests

This PR addresses post-submit comments from https://github.com/flutter/flutter/pull/12213, namely:

Wrap calls to _debugCheckOwnerBuildTargetExists in assert.
Replace loadGeneration with typeToResources in _LocalizationsScope, with the side-effect that it fixes synchronous loading of Localizations resources
Fix the test that should have failed due to lack of synchronous load notification.

/cc @Hixie @HansMuller

 modulo nits
Thanks for fixing the test!


unexpected splash when navigating

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
i have a problem about splashes
material 3
go_router latest
i click on a inkwell or icon button and i use context.pushNamed().i go to next page but when i want to come back i see splashColor is still running
i am checking my build method and there is no rebuild in my widgets.
i searched a lot but i couldn't figure out.
plz help me with my problem
i do not know what you need to help me cause every where of my app i see this problem.if you guys need something to help me please tell and i will send them
Expected results
it should not have splash after comming back
Actual results
i see splash every time i come back with back button
Code sample
Code sample
InkWell(
        borderRadius: const BorderRadius.all(Radius.circular(12.0)),
        onTap: onTap,
        child: Ink(
          padding: const EdgeInsets.symmetric(vertical: 8.0, horizontal: 8.0),
          child: Row(
            mainAxisAlignment: MainAxisAlignment.spaceBetween,
            children: [
              Row(
                children: [
                  SvgPicture.asset(
                    'assets/icons/bulk/$icon.svg',
                    colorFilter: ColorFilter.mode((isEnabled) ? primary1 : Theme.of(context).colorScheme.neutralIcon, BlendMode.srcIn),
                    width: 28,
                    placeholderBuilder: (context) => const SizedBox(width: 28, height: 28),
                  ),
                  const SizedBox(width: 10),
                  Text(
                    title,
                    style: Theme.of(context).textTheme.titleMedium?.copyWith(color: Theme.of(context).colorScheme.textColor),
                  )
                ],
              ),
            ],
          ),
        ),
      )

Screenshots or Video
Logs
Logs
[Paste your logs here]

Flutter Doctor output
[✓] Flutter (Channel stable, 3.10.0, on macOS 12.6.1 21G217 darwin-x64, locale en-TR)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
[✓] Chrome - develop for the web
[✓] Android Studio
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.75.0)
[✓] Connected device (3 available)
[✓] Network resources
• No issues found!

Hi @mahdiqdi, this is a known issue. It is being tracked in https://github.com/flutter/flutter/issues/119897.
Kindly follow up in the original issue for updates.
Closing from here as duplicate.
Thank you


Possible Issue: GPM Testing and Stable

Hi!
I'm not sure if it is actually an issue or if it is on purpose, but I noticed that if a Grav users has enabled Testing releases for the GPM, he does not get notified if a more recent stable releases exists.
So do plugin developer just need to keep their testing release ahead of the stable one or is it a bug?
Thanks!

I think we should always have a notification for newer, non-testing releases. Marking as bug


[Monitor] Add Public Preview APIs of Metric Baseline

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/2049

Codecov Report

Merging #1710 into master will decrease coverage by 0.03%.
The diff coverage is 41.39%.

@@            Coverage Diff             @@
##           master    #1710      +/-   ##
==========================================
- Coverage   55.33%   55.29%   -0.04%
==========================================
  Files        4202     4215      +13
  Lines      100158   100436     +278
==========================================
+ Hits        55422    55540     +118
- Misses      44736    44896     +160

Impacted Files
Coverage Δ

...itor/azure/mgmt/monitor/models/retention_policy.py
62.5% <0%> (-8.93%)
:arrow_down:

...iagnostic_settings_category_resource_collection.py
66.66% <0%> (-13.34%)
:arrow_down:

...nitor/azure/mgmt/monitor/models/metric_settings.py
50% <0%> (-5.56%)
:arrow_down:

...tor/azure/mgmt/monitor/models/autoscale_profile.py
45.45% <0%> (-4.55%)
:arrow_down:

...onitor/azure/mgmt/monitor/models/scale_capacity.py
55.55% <0%> (-6.95%)
:arrow_down:

...t-monitor/azure/mgmt/monitor/models/time_window.py
55.55% <0%> (-6.95%)
:arrow_down:

...mt-monitor/azure/mgmt/monitor/models/recurrence.py
62.5% <0%> (-8.93%)
:arrow_down:

...-monitor/azure/mgmt/monitor/models/sms_receiver.py
50% <0%> (-5.56%)
:arrow_down:

...-monitor/azure/mgmt/monitor/models/scale_action.py
50% <0%> (-5.56%)
:arrow_down:

...mt-monitor/azure/mgmt/monitor/models/scale_rule.py
62.5% <0%> (-8.93%)
:arrow_down:

... and 81 more

Continue to review full report at Codecov.

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


error MSB4057: The target "CreateDeb" does not exist in the project

Hello,
I followed the instructions located in the readme file but I get the following error if I execute dotnet deb -r debian9.5-x64 -f netcoreapp2.2.0 command.
C:\Users\Privat\Desktop\Server-Core\Server-Core\Server-Core.csproj : error MSB4057: The target "CreateDeb" does not exist in the project
This is how my Program.cs class looks like
using Dotnet.Packaging;

namespace Server_Core
{
    class Program
    {
        static int Main(string[] args)
        {
            PackagingRunner runner = new PackagingRunner("Debian/Ubuntu installer package", "CreateDeb");
            return runner.Run(args);
        }
    }
}

This is how my Server-Core.csproj file looks like
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.2</TargetFramework>
    <RootNamespace>Server_Core</RootNamespace>
    <ApplicationIcon />
    <StartupObject />
    <Version><IP_ADDRESS></Version>
    <Authors></Authors>
    <Company></Company>
    <PackageRequireLicenseAcceptance>false</PackageRequireLicenseAcceptance>
    <GeneratePackageOnBuild>false</GeneratePackageOnBuild>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
    <DefineConstants>DEBUG</DefineConstants>
    <Optimize>false</Optimize>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="dotnet-deb" Version="0.1.1-*" />
	<DotNetCliToolReference Include="dotnet-deb" Version="0.1.1-*" />
  </ItemGroup>

  <ItemGroup>
    <Compile Update="Properties\Resources.Designer.cs">
      <DesignTime>True</DesignTime>
      <AutoGen>True</AutoGen>
      <DependentUpon>Resources.resx</DependentUpon>
    </Compile>
  </ItemGroup>

  <ItemGroup>
    <EmbeddedResource Update="Properties\Resources.resx">
      <Generator>ResXFileCodeGenerator</Generator>
      <LastGenOutput>Resources.Designer.cs</LastGenOutput>
    </EmbeddedResource>
  </ItemGroup>

  <Target Name="PackageDebian" DependsOnTargets="CreateDeb" Outputs="$(DebPath)"/>

</Project>

Thank you.
Sincerley,
Chris

I get the same error. Did you solved this issue?

Try to make sure you have the latest version of Packaging.Targets (and dotnet-deb). I just updated the README:
    <PackageReference Include="Packaging.Targets" Version="0.1.56" />

It seems that you have to run firstly the respective dotnet publish command and then the dotnet deb command. I had the same error, but after using  dotnet publish it worked correctly.

This can happen if you did not run dotnet restore first (you shouldn't need to run dotnet publish).
Can you check whether this problem reproduces on a clean checkout, and that running dotnet restore fixes this?

This can happen if you did not run dotnet restore first (you shouldn't need to run dotnet publish).
Can you check whether this problem reproduces on a clean checkout, and that running dotnet restore fixes this?

It does not fix it for me, neither publish nor restore fixed the Problem. I am using Rider 2019.1.2 on Windows 10. Command: dotnet deb -f netcore2.2 -r ubuntu.18.04-x64

RuntimeFrameworkVersion

@aggsol is right. I was adding the following PropertyGroup:
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.2</TargetFramework>
    <RuntimeFrameworkVersion>2.2.6</RuntimeFrameworkVersion>
    <RuntimeIdentifiers>win10-x64;linux-x64</RuntimeIdentifiers>
  </PropertyGroup>

Afterwards my project was compiled without the need of using dotnet publish.

@qmfrederik Maybe you could open up the wiki and list all relevant project properties and best practices, examples there?


[ENHANCEMENT]  Certificates only supported in home region, expand to any managed region

Bug reports which fail to provide the required information will be closed without action.
Required Basic Info

Accelerator Version:  (eg. v1.3)
Install Type: (Upgrade)
Upgrade from version: (v1.2.y)
Which State did the Main State Machine Fail in: (e.g. N/A, Phase 0)
None

Describe the bug
While we create a certificate section in account config like
- name: PublicCert
    type: request
    domain: '*.dev.sss.click'
    validation: DNS
    san:
      - '*.dev.sss.click'

This only create a certificate in home region. What is the way to create same certificate in another regions?
Steps To Reproduce

Create a simple config with workload-account-configs as

replacements:
addl_regions:
a:
- '${HOME_REGION}'
- us-east-1
b:
- '${HOME_REGION}'
- '${GBL_REGION}'
c:
- '${HOME_REGION}'
- '${GBL_REGION}'
workload-account-configs:
dev:
account-name: Dev
email<EMAIL_ADDRESS>ou: Dev
account-warming-required: false
src-filename: config.json
certificates:
- name: PublicCert
type: request
domain: '.dev.sss.click'
validation: DNS
san:
- '.dev.sss.click'

2. Run stepfunction and observe certificates created in home region only and missing in us-east-1

ASEA not working on new features see README.


Add favicon to chat space

To help me quickly find it among the many tabs I'm checking. :D

Add an @-sign roguelike icon to the repo, and it can also serve as a placeholder to show other folks how to add their own.

This is a 5-minute job that takes no code.

This exists!!


⚠ Bofrost.at has degraded performance

In 76da777, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2620 ms

Resolved: Bofrost.at performance has improved in b261284 after 14 minutes.


Building docker image via run_me.py fails

INFO     CourseHandler        Welcome to 'Mastering Big Data Analytics with Pyspark' by Danny Meijer<EMAIL_ADDRESS>INFO     CourseHandler        Course Version: 20200420
INFO     CourseHandler        Course Name: Mastering Big Data Analytics with Pyspark
INFO     CourseHandler        Container Name: mastering-pyspark-ml
INFO     CourseHandler        Downloading the data
INFO     CourseHandler        Processing Sentiment140TrainingData
INFO     CourseHandler        Directory "sentiment-140-training-data" already exists
INFO     CourseHandler        Skipping "trainingandtestdata.zip"
INFO     CourseHandler        Processing MovieLens-Small
INFO     CourseHandler        Directory "ml-latest-small" already exists
INFO     CourseHandler        Skipping "ml-latest-small.zip"
INFO     CourseHandler        Processing MovieLens
INFO     CourseHandler        Directory "ml-latest" already exists
INFO     CourseHandler        Skipping "ml-latest.zip"
INFO     CourseHandler        Connecting to Docker API
INFO     CourseHandler        Checking if Docker image is already set-up
WARNING  CourseHandler        Docker image has not been built yet
INFO     CourseHandler        Building Docker image
INFO     docker.api.build     Initiating (this might take a few moments)
Traceback (most recent call last):
File "run_me.py", line 325, in
course = Course()
File "run_me.py", line 117, in init
self._image()
File "run_me.py", line 256, in _image
self.build_image()
File "run_me.py", line 194, in build_image
rm=True,
File "C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\api\build.py", line 261, in build
self._set_auth_headers(headers)
File "C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\api\build.py", line 308, in _set_auth_headers
auth_data = self.auth_configs.get_all_credentials()
File "C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\auth.py", line 302, in get_all_credentials
for k in store.list().keys():
File "C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\credentials\store.py", line 72, in list
return json.loads(data.decode('utf-8'))
File "C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\json_init.py", line 348, in loads
return _default_decoder.decode(s)
File "C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\json\decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\json\decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

What version of Docker is being used? I also would like to see the output
of pip list.
This might be down to an API change on Docker side - will have to
investigate this once I get the above information.
On Wed, May 5, 2021 at 9:21 AM hansraj @.***> wrote:

INFO CourseHandler Welcome to 'Mastering Big Data Analytics with Pyspark'
by Danny Meijer @.***
INFO CourseHandler Course Version: 20200420
INFO CourseHandler Course Name: Mastering Big Data Analytics with Pyspark
INFO CourseHandler Container Name: mastering-pyspark-ml
INFO CourseHandler Downloading the data
INFO CourseHandler Processing Sentiment140TrainingData
INFO CourseHandler Directory "sentiment-140-training-data" already exists
INFO CourseHandler Skipping "trainingandtestdata.zip"
INFO CourseHandler Processing MovieLens-Small
INFO CourseHandler Directory "ml-latest-small" already exists
INFO CourseHandler Skipping "ml-latest-small.zip"
INFO CourseHandler Processing MovieLens
INFO CourseHandler Directory "ml-latest" already exists
INFO CourseHandler Skipping "ml-latest.zip"
INFO CourseHandler Connecting to Docker API
INFO CourseHandler Checking if Docker image is already set-up
WARNING CourseHandler Docker image has not been built yet
INFO CourseHandler Building Docker image
INFO docker.api.build Initiating (this might take a few moments)
Traceback (most recent call last):
File "run_me.py", line 325, in
course = Course()
File "run_me.py", line 117, in init
self._image()
File "run_me.py", line 256, in _image
self.build_image()
File "run_me.py", line 194, in build_image
rm=True,
File
"C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\api\build.py",
line 261, in build
self._set_auth_headers(headers)
File
"C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\api\build.py",
line 308, in _set_auth_headers
auth_data = self.
auth_configs.get_all_credentials() File
"C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\auth.py",
line 302, in get_all_credentials for k in store.list().keys(): File
"C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\site-packages\docker\credentials\store.py",
line 72, in list return json.loads(data.decode('utf-8')) File
"C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\json_init.py",
line 348, in loads
return _default_decoder.decode(s)
File
"C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\json\decoder.py",
line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File
"C:\Users\Hansrajjadhav\AppData\Local\Programs\Python\Python37\lib\json\decoder.py",
line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PacktPublishing/Mastering-Big-Data-Analytics-with-PySpark/issues/8,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQGM2446B7EG5RNEAKT7GDTMDWYTANCNFSM44EDTXZQ
.

Package           Version

bitbucket-api     0.5.0
boto3             1.17.0
botocore          1.20.0
certifi           2020.6.20
chardet           3.0.4
Deprecated        1.2.10
docker            5.0.0
fake-useragent    0.1.11
gitdb             4.0.5
GitPython         3.1.11
idna              2.10
jmespath          0.10.0
numpy             1.19.2
oauthlib          3.1.0
pandas            1.1.2
pip               20.2.4
PyGithub          1.53
PyJWT             1.7.1
pyodbc            4.0.30
python-dateutil   2.8.1
pytz              2020.1
pywin32           227
requests          2.24.0
requests-futures  1.0.0
requests-oauthlib 1.3.0
s3transfer        0.3.4
setuptools        47.1.0
sh                1.14.0
six               1.15.0
smmap             3.0.4
urllib3           1.25.10
websocket-client  0.59.0
wrapt             1.12.1
xpressinsight     1.1.0

@dannymeijer
You can take your time to check on it..
For the time being i have run the docker commands directly and modified the run_me.py to use the image created and spin up the container.
Thanks.

I never was able to get to the bottom of this one. It still works for me (even with latest version of Docker and Python) hence I am unable to reproduce the error.
Please let me know if you still need assistance.

Hi Danny -
Thanks for your response. Unfortunately I was not able to revert to your
earlier comment in May.
But it seemed like it was some intermittent issue due to the docker
version. Once I reinstalled it - it was working fine for me as well.
Regards,
Hansraj
On Mon, Jan 17, 2022 at 3:13 PM Danny Meijer @.***>
wrote:

I never was able to get to the bottom of this one. It still works for me
(even with latest version of Docker and Python) hence I am unable to
reproduce the error.
Please let me know if you still need assistance.
—
Reply to this email directly, view it on GitHub
https://github.com/PacktPublishing/Mastering-Big-Data-Analytics-with-PySpark/issues/8#issuecomment-1014325742,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2ZONTLLSLFU37A7B2AITUWPQFZANCNFSM44EDTXZQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
<PacktPublishing/Mastering-Big-Data-Analytics-with-PySpark/issues/8/1014325742
@github.com>

Thanks @hansraj - closing this as requested


"Unknown file size detected"

hi ,olli991
i got the error "Unknown file size detected" from hardware "mib std2 ZR +/nav",and GEM version is 4.3.
I installed toolbox from the bin file with usb programmer,no response from normal installation by sd card.
Incidental the support  file，hope to be solved,thank you verymuch.
VWZAZ2T5057250.zip

What is a train version in system version? Does your unit have one or two SD slots?

What is a train version in system version? Does your unit have one or two SD slots?

version:  mst2_cn_vw_zr_p0361t，HW30 / 0361 ,
,it's  has 2 SD card slots.
TKS verymuch

Update to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip and apply patch again.


Add node level chaos scenarios for bastion node

Scenario: node level test to shut down and start the bastion node. Upon  node startup, the list of services provided in the scenario will be checked if they are running or not.
Signed-off-by: Pravin Dsilva<EMAIL_ADDRESS>

Can one of the admins verify this patch?

I’m not super familiar with helper nodes, would the helper node name and IP address be returned from oc get nodes using a specific label_selector in the config? If so, I think we could reuse the stop start node scenario code but still add on the service check at the end for this specific action. AKA no need for helper_node_start_scenario and helper_node_stop_scenario in openstack_node_sceanrios. Thoughts?
Also, not sure if this is all from code you have added but can you please take a look at the spacing issues outlined using tox.
To run:
pip install tox (if not already installed; might want to add this to the requirements)
Run “tox” and fix all spacing/import issues

I’m not super familiar with helper nodes, would the helper node name and IP address be returned from oc get nodes using a specific label_selector in the config? If so, I think we could reuse the stop start node scenario code but still add on the service check at the end for this specific action. AKA no need for helper_node_start_scenario and helper_node_stop_scenario in openstack_node_sceanrios. Thoughts?

Yes, we intended to re-use the code but since the helper node is an external entity not part of the openshift cluster, there is no way to get the ip or hostname from oc get nodes.

Also, not sure if this is all from code you have added but can you please take a look at the spacing issues outlined using tox.
To run:
pip install tox (if not already installed; might want to add this to the requirements)
Run “tox” and fix all spacing/import issues

Sure, I have created another commit in this PR fixing all the indentation issues which are not part of my code. Thanks

Is there a plan to add this type of scenario to all could types? If not, it would be nice to give a better error when trying to use aws with the stop_start_helper_node_scenario for example. Instead of getting this ugly error message:
AttributeError: 'aws_node_scenarios' object has no attribute 'helper_node_stop_scenario'
Other than that LGTM

LGTM

@pravin-dsilva please squash the commits and we'll do a final review.   Thanks for working with us on this.

Thanks, please take a look.


Removed if-else and used switch case for more code readability

Used switch instead of if-else which makes code less messy

Gave arrow after a command to make it easier to recognize which words are actually commands

There are merge conflicts in this request, resolve those first.


Updated some test files (minor)

Coverage remained the same at 84.552% when pulling 2cc83a20b80338e072a13dc179e097ee2b3e1d92 on tests into ee381b7c2a582162e85c1920d6b3562ea92a7d17 on master.

Coverage remained the same at 84.552% when pulling 2cc83a20b80338e072a13dc179e097ee2b3e1d92 on tests into ee381b7c2a582162e85c1920d6b3562ea92a7d17 on master.

Coverage remained the same at 84.552% when pulling 2cc83a20b80338e072a13dc179e097ee2b3e1d92 on tests into ee381b7c2a582162e85c1920d6b3562ea92a7d17 on master.


Command line args

If the options are specified on the command line, then prompting is omitted. The problem is when validation fails on the group of inputs, then the while loop is tried again. However, since the values were already supplied on the command line, validation on the group of inputs is performed on the same incorrect values...in a while loop. The second time through any of the input while loops, we should force prompting - the value supplied on the command line should be the default.
2) Agent exits if --nostart is specified on the command line.
Should error out early if unknown command line parameter (i.e. typo)

If you error, it should print help.


DisabledTextTrivia children stuck in Loading when under a ChildTokens node in Details

Source of this bug: https://github.com/dotnet/roslyn/issues/76441
The child retriever silently fails without ever logging the exception, and never reporting the failed status, so the node is stuck displaying that it's loading. We should at least combat the bug on Roslyn's side by tolerating a null syntax tree which is how the line numbers are retrieved.

The program actually creates a new SyntaxTokenList which does not expose a public API to set the parent manually. Therefore, the returned tokens from the list are returned with a null parent. The Roslyn issue was closed because of this realization. This must be fixed in the side of Syndiesis to support an arbitrary IReadOnlyList<SyntaxToken> instead of just SyntaxTokenList.


Confusing due to interface of PipeableApply

I wrote some codes like following...
import { pipeable, option } from 'fp-ts';

declare const converter1: option.Option<(value: string) => string>;
declare const converter2: option.Option<(value: string) => string>;
declare const converter3: option.Option<(value: string) => string>;

pipeable.pipe(
  option.some('value'),
  option.ap(converter1),
  option.ap(converter2),
  option.ap(converter3),
);

But option.ap() takes Option instance as first argument.
This behavior is defined by PipeableApply.
export interface PipeableApply<F> extends PipeableFunctor<F> {
  readonly ap: <A>(fa: HKT<F, A>) => <B>(fab: HKT<F, (a: A) => B>) => HKT<F, B>
  //           ^^^^^^^^^^^^^^^^^^
  ...
}

I have usesd fp-ts@^1 before, at that time the codes like above was valid.
Like next...
import { option } from 'fp-ts'; // fp-ts@^1

declare const converter1: option.Option<(value: string) => string>;
declare const converter2: option.Option<(value: string) => string>;
declare const converter3: option.Option<(value: string) => string>;

option
  .some('value')
  .ap(converter1)
  .ap(converter2)
  .ap(converter3);

I don't know why ap() of fp-ts@^2 is defined in this way.
I am not professional at functional programming, so I don't know whether this is bug or not.
If you know correct usage of ap(), please let me know.
(I'm sorry if my English is strange, but I tried to write politely.)

ap signature is optimized for lifting a n-ary function (IME should be the most common case)
import { ap, Option, some } from 'fp-ts/lib/Option'
import { pipe } from 'fp-ts/lib/pipeable'

declare const f: (a: string) => (b: number) => boolean
declare const a: Option<string>
declare const b: Option<number>

const result = pipe(
  some(f),
  ap(a),
  ap(b)
)

Do I understand it correctly, that ap is only for wrapped functions? I somehow do not see real-world use cases.

That's the gist of Applicative, enabling 'parallel' (indépendant) évaluation whereas monadic computation are sequentials (and may depend from previous results).

@gcanti @sledorze
Thanks for reply.
I see the use case.


Twillio Flex Issue

So, I have set up the provided code according to the instructions, and it works up to the point where the IVR forwards the call to an agent. However, when my server logs show "forwarding call to agent," I don't receive any call on my Flex dashboard. Can anyone help me identify what might be causing this issue? we have followed all the configuration according to the given instruction from the following article.

I have the same problem and if I look in the error logs for the flex account it shows a [21264 - ‘From’ phone number not verified]. However the from number is my verified number (the cell number I setup the account with)


Support for GET form method

This allows using "get" as a form method for users who don't want to or can't use default "post".
<form method="get" ...

Is there a reason that this PR has not been merged? Tests are passing and I don't see any discussion.

+1

I don't see any tests nor documentation about the new functionality. These are required.


Add DoubleDouble from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of SamBelanger, to add DoubleDouble to CKAN.
Mod details:
name = /mod/1553/DoubleDouble
author = SamBelanger
abstract = This mod that adds binary systems!
license = MIT
Homepage = 20 oct 2017 ONLY
description = Hello guys this mod that adds binary systems!
README

Download the mods Kopernicus (1.3.0-6/1.3.1-2 RECOMMEND!!), ModularFlightIntegrator (Integrate to Kopernicus!), ModuleManager (Integrate to Kopernicus!) and BetterTimeWarp

Put the mods files in the GameData folder

Start the game (KSP)

Have fun :)

And if you have a suggestion or find bugs or errors, contact us<EMAIL_ADDRESS>or make a private message in the forum of KSP or otherwise) Thank you very much!
Please direct questions about this pull request to SamBelanger.

Add plz!

His @SamBelanger! Thanks for the submission! Is BetterTimeWarp a requirement, or a "really-good-to-have"?

BetterTimeWarp is not required


Convert Architecture class into a workspace.dsl file + a loading ArchitectureDocumentationProvider

Currently, Architecture in architecture-documentation is a java class containing the whole documentation.
We should convert it (thanks to an Enhancer, obviously) into a workspace.dsl file.
The benefit would be that we could use structurizr-lite, even on our documentation.
The side-benefit would be that user projects would gain "better" UI for some use-cases.

See https://github.com/structurizr/dsl/blob/master/docs/language-reference.md for language reference
See also https://dev.to/simonbrown/getting-started-with-structurizr-lite-27d0 for starting.


[hold] WFLY-9563 Integrate KUBE_PING discovery protocol

Jira
https://issues.jboss.org/browse/WFLY-9563
Proposal
https://github.com/wildfly/wildfly-proposals/pull/10

Why is this marked [hold], was it just because it was for 13.x or is there some other reason?

@rhusar please ping me when this is no longer a hold and I will remove the label.

@stuartwdouglas @rhusar I guess it is hold because WFLY-9563 is a feature request and it is missing some stuff to get merged. Adding Feature and removing the hold label

Great, thank you @slaskawi ! 1.0.6.Final was not out when I initially opened the PR, so removed the dependency now. What an Irony... we setup jgroups-extras so we can bring in dependencies.

@kabir I have held the PR to coordinate with other teams.
@wildfly/mergers-full This should be ready.

@rhusar I'm working on the precheck, but running into issues (not with this PR, that looks good so far). I'll let you know again tomorrow.

@rhusar @kabir The precheck is complete. I run into some issues, none blocking. Most of them don't even relate to KUBE_PING and are likely related to my environment. I'll describe everything in the planning issue. The one thing that's worth mentioning here is that KUBE_PING logs two warnings which are redundant and IMHO shouldn't be logged by the server:
12:26:03,871 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (ServerService Thread Pool -- 68) OPENSHIFT_KUBE_PING_NAMESPACE is deprecated, please remove it and use KUBERNETES_NAMESPACE instead
12:26:03,871 WARN  [org.jgroups.protocols.kubernetes.KUBE_PING] (ServerService Thread Pool -- 68) OPENSHIFT_KUBE_PING_LABELS is deprecated, please remove it and use KUBERNETES_LABELS instead

I did not specify any environment variables since the namespace and labels are a part of the server configuration. This is due to the if here: https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/src/main/java/org/jgroups/protocols/kubernetes/KUBE_PING.java#L176
This should IMHO look like:
if (propertyDefined && deprecatedDefined)
    log.warn("specify one");
else if (deprecatedDefined)
    log.warn("deprecated...");
}

But this is no big deal. I'll file a JGRP issue for this.
What I tested is a scale-up/scale-down scenario with 4 nodes on a local kubernetes instance via Minikube as well as filtering based on namespaces and labels - all of that behaves as expected.
In other words, I think we can move forward with this if you want. I still need to automate my tests, but I'll track that on the planning issue.


2021 07 freeipa dep fix

This change removes the ca_certs role from cluster.yml.
This functionality has been moved as part of the changes required to fix FreeIPA.
Note: This PR must be merged with the corresponding cloudera.cluster PR of the same name

Depends on https://github.com/cloudera-labs/cloudera.cluster/pull/40

Related to https://github.com/cloudera-labs/cloudera.cluster/pull/40