Examples: Minor review, and improvements

This PR includes minor changes to the examples, including:

small fixes to CLI default params, error handling, and overall execution progress messages.
new files of requirements to be installed (with instructions)
some rephrasing in README (tcga)

Coverage remained the same at 97.485% when pulling 02940940f9cfd24716de6addce5cd02594032c83 on leriomaggio:master into 21dcf0697eef827268c928a7764faf6a816bf399 on histolab:master.

@ernestoarbitrio do you know why Travis is still waiting for the branch build? I can't see it on travis-ci.com.
Is it because Valerio is working on a fork? 🧐

@ernestoarbitrio do you know why Travis is still waiting for the branch build? I can't see it on travis-ci.com.
Is it because Valerio is working on a fork? 🧐

I believe so! Considering that the branch on our repo doesn't exists travis cannot run a build from a unknown one. So maybe there's something we can change on our conf. But for now if the PR is ok let's merge it !!!

@leriomaggio histolab by design has a protection branch rule. I noticed you're trying to merge your-repo:master onto histolab:master that's not possible. This PR should be reopened or rebase on another base-branch different from master. Hope I've been clear :D

@leriomaggio histolab by design has a protection branch rule. I noticed you're "asking" to merge your-repo:master onto histolab:master that's not possible. This PR should be reopened or rebased on another base-branch different from master. Hope I've been clear :D
Just for reference : https://github.com/histolab/histolab/blob/master/CONTRIBUTING.md

HI @ernestoarbitrio thanks for clarifying that.  I suspected that could be the issue. truth to be told: I had the contribution guidelines read only afterwards. So entirely my fault.
I will rebase on a new branch on my end, and re-open the PR.
Will keep you posted.
Cheers

@leriomaggio histolab by design has a protection branch rule. I noticed you're "asking" to merge your-repo:master onto histolab:master that's not possible. This PR should be reopened or rebased on another base-branch different from master. Hope I've been clear :D
Just for reference : https://github.com/histolab/histolab/blob/master/CONTRIBUTING.md

HI @ernestoarbitrio thanks for clarifying that. I suspected that could be the issue. truth to be told: I had the contribution guidelines read only afterwards. So entirely my fault.
I will rebase on a new branch on my end, and re-open the PR.
Will keep you posted.
Cheers

Well Done !!! 👍🏽


How does the breakout board for the commet work?

I was able to run v.0.1. However, the way the breakout board is indexed is unclear to me. Also, how is the quadruple pinned break out board supposed to work. Further, when I moved the breakout board from J2 to J1, some weird nonsense happened.

The breakout boards are unique to J1 and J2, so if you moved the same breakout board from one connector to the other I'm not surprised that you saw some weirdness.  One breakout board has a ground plane, and the other does not (accidentally).  So the board with the ground plane has two additional pins connected to ground to enable single ended measurements (measuring one leg of the differential pair referenced to ground.  Generally, you want to use the pins that are not grounded in order to measure the signal pairs differentially.  If that doesn't answer your question stop by my office next time you're around and I'll show you.


Polygons in focal nodes, but no polygon file

Checks sgVerify6

Codecov Report

Merging #38 into master will increase coverage by 0.06%.
The diff coverage is 96.29%.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
+ Coverage   96.97%   97.04%   +0.06%
==========================================
  Files           5        5
  Lines         331      338       +7
==========================================
+ Hits          321      328       +7
  Misses         10       10

Impacted Files
Coverage Δ

src/raster.jl
98.41% <96.29%> (+0.09%)
:arrow_up:

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 2930d05...3c35640. Read the comment docs.


Issue #116 #117 fix local creation of the status label

The local creation of the status label causes the label to not exist globally,
therefore the status events, like Update, Delete, etc will result in a null-
pointer as the variable does not actually exist.

Thanks!

Will incorporate the fix in a slightly modified form on the master.


Clicking on an empty paragraph in Firefox makes the element untype-able

You can see this in the demo also, if you create an empty paragraph (press enter), then click on the new blank element the cursor moves to the right side of the highlighted area. Then you won't be able to type in it unless you click on another element.

Interestingly this only happens if you create a new element and click it, if you empty the element and click it FF behaves as expected.


Create WCS header info

For each frame, create the WCS header using telescope information and the astrometric calibration (platescale, north angle, boresight). Each frame should have its own WCS header.

This should also write the distortion information into the header (likely coefficients of whatever basis we use to describe spatially varying distortion)


Add query, files and tests for morphology features

This is to index the morphology features that exist as separate annotations.
Following what was requested in this ticket:

separate axon and dendritic total lengths not just total length of the whole morphology
maximum branch order (Strahler index) [for axon, apical/basal dendrites]
xyz spatial extent of dendrites (bbox)
soma radius
arbor asymmetry (partition asymmetry) for apical and basal dendrites

@shinyhappydan how is that the integration tests didn't run?

Could you check the query is valid ?
If it is not it is possible it prevents Delta to start


REPO project，Leadef files cannot find files under sub git repository

vim or neovim?

[x] vim
[ ] neovim

Output of vim --version or nvim --version: 8.2

Output of :echo has("python"): 0

Output of :echo has("python3"): 1

Output of :echo &pythondll(only vim, not neovim): no output

Output of :echo &pythonthreedll(only vim, not neovim): no output

Output of :py print(sys.version):

Output of :py3 print(sys.version): 3.7.10
(default, May 31 2021, 10:48:48)
[GCC 5.4.0 20160609]

Output of :echo g:Lf_Debug_Cmd:

Output of :echo g:Lf_FilesFromCache: 1

Operating system:

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Configurations related to LeaderF in vimrc:

Describe your question, feature request, or bug.
my latest project is managed  by Repo, so there are several git repositories under sub-directory. In this case, I couldn't look up files under sub-directory which is managed by another git repository by using cmd "Leaderf files ".
I have tried several ways refrenced in history issues but failed in the end.
first I tried  add belows lines in vimrc
let g:Lf_UseVersionControlTool = 0
let g:Lf_DefaultExternalTool = "rg"

then I run echo g:Lf_Debug_Cmd which output is rg --no-messages --files --color never
which seems right, but I still can't files which is in other git repository
I also tried let g:Lf_ExternalCommand = 'rg --files %s'
after run  echo g:Lf_Debug_Cmd which output is rg --files "."
and I still failed to look up files in under repository...
I confirm rg installed and works well as I type rg --files "xxx" , results show up instantly.
Steps to reproduce
Actual behaviour
Expected behaviour

let g:Lf_RecurseSubmodules = 1

What is the hierarchy of your Repo?

Are the folders of other git repo in the .gitignore?

Run rg --no-messages --files --color never in the command line, I think it should work.

Are the folders of other git repo in the .gitignore?

Are the folders of other git repo in the .gitignore?

yes, so it seems to be the reason?  How can I exclude the .gitignore files whithout modifiled the .gitignore

Leaderf file --no-ignore.

Run rg --no-messages --files --color never in the command line, I think it should work.

I run rg --no-messages --files --color never > tmp_file,  and files in sub-directory didn't exits in the tmp_files.
but if run rg --files "xxx"  > tmp_file, files in sub-directory match the pattern 'xxx' can be found
run Leaderf file --no-ignore only show up the directory'name in .gitignore which matchs the pattern , but files under sub-directory  which matchs the patternstill can't be found

set let g:Lf_UseVersionControlTool = 0
let g:Lf_DefaultExternalTool = "rg" ,
plus with running Leaderf file --no-ignore works, confusing :)

but I do want to exclude some files in .gitnore except the the sub-directory , is there any bettery way to acchive this?

using g:Lf_WildIgnore would will fix this, thank you so much

How to auto execute this command Leaderf file --no-ignore  when enter vim ?
I've tried to write down autocmd BufWinEnter  Leaderf file --no-ignore in .vimrc but it did not work.

Finally, I write like this to solve that:
func OpenLeaderF()
  :Leaderf file --no-ignore
  :LeaderfFile
endfunc

nnoremap <c-p> :call OpenLeaderF()<cr>


Rewrite/Override XMLTV Timezones

I know it's the provider's responsibility to provide timezone info in their XMLTV feeds but with the conflicting start dates of summertime in different countries, etc, the provided timezone can cause listings to show up an hour off.
Since my server runs more than Xteve and Plex. I would prefer not to have change the system time.
Would it be possible to get a setting in each XMLTV feed for an offset?  That would allow feeds from multiple providers to be corrected individually as well.
Thanks!

Why doesn't your EPG Provider offer a TZ setting is the real issue....
zap2xml uses your system's time and timezone so make sure your system clock is correct. Set your TZ environment variable before running zap2xml if you want to change the timezone of scheduled programs (ie: export TZ=GMT).

Your provider does not have to take summer time into account, it is sufficient if it uses UTC for all channels. Your server / client does the conversion of the time zones including summer time. Assuming the time and time zone on your server is correct.
I use Schedules Direct, all times of the channels are in UTC (+0000) and I live in +0200. My EPG data is displayed correctly.

I would like to see this feature, as I have channels from two countries, which don't agree on the timezone, so now, UTC on my playlist, but time is off by 1 hour. maybe a bug in the xmltv provider, but would be nice to have this option.

Such a function is not planned. If the provider specifies the wrong time zone, he should fix it.


Successfully run game on iOS mobile target

You will need an iOS device, and you will need to use a service like https://www.macincloud.com/

Testing on iOS without an iOS device or macintosh is prohibitively difficult. We have a proof-of-concept working on android which somewhat paves the way for having a mobile port of the game some day. But, it won't be our focus.


Dynafed block parsing

With the dynafed upgrade going live soon, we'll need to be able to handle blocks with dynafed headers. @philippem linked me to this example that we could use as a test case: https://github.com/ElementsProject/rust-elements/blob/master/src/block.rs#L655
The Block.fromHex() method seems to have a problem handling it:
RangeError: value out of range

@asoltys we never touched block (de)serialization when forking from bitcoinjs. So the implementation has be done anyway since is missing also for pre-dynafed blocks.
We implemented that in go-elements tho, could be another reference.
Do you see any use case for browser block parsing? I would wait for neutrino support in Elements before doing any SPV like wallet in the browser

I use it in the coinos nodejs app server to parse Blocks as they get received to check if any of the block transactions pertain to any of the wallet addresses we're tracking and update their confirmed status. Most people would probably use walletnotify in that case but we're tracking some HD wallets outside of elementsd. That said, I could probably use electrs or bwt for this instead, I think they just weren't around when I wrote the code for this.
Anyways, this isn't something I expect you guys to fix. I might try to take it on though so figured it would be good to have an issue for it. I managed to get pre-dynafed blocks parsing a while ago: https://github.com/asoltys/elementsjs-lib/commit/04547ed6934c95a63da56f23f0024b4b7c3b135d

@asoltys  very interesting, thanks for the commit!
Let me see if we can allocate some time for it! Definitely interested in see the code you use to check transaction relative to an HD wallet in blocks, is it open source?

Thanks!
We are see to allocate to some resource to update LiquidJS to support blocks as well ( I always assumed nobody was using the block feature anyway, so thanks for heads up)


how can i delete bot's message??

sorry for my bad golang.
I hope to delete the messages but I don't know how to remove it.
in your guide,
var msgs []tb.StoredMessage
db.Find(&msgs) // gorm syntax

for _, msg := range msgs {
	bot.Edit(&msg, "Updated text")
	// or
	bot.Delete(&msg)
}

but If I try it to my sourcecode
var db, err = gorm.Open(sqlite.Open("test.db"), &gorm.Config{}) # I don't know how to use this.
var msgs []tb.StoredMessage
db.Find(&msgs) // gorm syntax

for _, msg := range msgs {
	bot.Edit(&msg, "Updated text")
	// or
	bot.Delete(&msg)
}

sorry but could you help me once?? T^T

Check the error that bot.Delete(&msg) returns.


Fixes for rustc 1.0.0-nightly (d754722a0 2015-03-31) (built 2015-03-31)

Blocked on https://github.com/BurntSushi/byteorder/pull/23

Seems to be fixed now https://github.com/BurntSushi/byteorder/pull/23#issuecomment-88550135

Thanks!


fix: change uriDetails type to URIComponents from uri-js package

This file is generated, I'm not sure how to get @otris/jsdoc-tsd to generate this.  Let me do some digging.

I followed your approach to try to use official syntax, then compensate for the shortcomings of @otris/jsdoc-tsd by doing replacements with gulp-replace.
There's also a change in the order of files for the docs-ts-raw gulp task, with index now after typedefs, which also reverses the output.
I think it's the smallest change for it to work.
Is it acceptable to you?
Thanks


Correct Tao Bao Browser for taobao.com

Fixes github issue: https://github.com/WhichBrowser/Parser-PHP/issues/259

Coverage remained the same at 100.0% when pulling a58a7dd4d66dfec2d47f135dd30a7ddd84dfd7e2 on ayumi-cloud:taobao into 4899110cd2f87b01e04ced62dbb9dec541031dee on WhichBrowser:master.


The equality comparison operator == is producing incorrect results for KeyPaths on Swift 6.0 Development Snapshots.

Description
There are cases when the equality comparison operator == is returning true when it ought to return false. Here, both sides involve KeyPaths, but the KeyPaths themselves are different.
Reproduction
Run the below code (built either in Debug or Release mode) with a recent Swift 6.0 Development Snapshot (2024-04-30 tested).
  struct O {var a: Int}
  struct I {var b: Int}
  print(\I.b == \O.a)

Expected behavior
The above code should print false.
Environment
Swift Development Snapshot 6.0 (2024-04-29a and 2024-04-30a) are affected.
If using Xcode, one can create a new xcodeproj, paste in the above code, switch to a 6.0-branch toolchain, and run.
This problem also occurs in Ubuntu 20 with an x86 machine.
Note that when running the executable on a MacOS terminal window, the executable itself ought to be using the libswiftCore.dylib corresponding to a 6.0-based toolchain, rather than the default system one.
Additional information
None of the nightly toolchains (i.e, 2024-05-01a) nor anything on the 5.10 branch appears to be affected.

This appears to be fixed as of the 2024-05-14a 6.0 snapshot.
The pertinent fix is here: https://github.com/apple/swift/pull/73347/


Alarms and timers

Is it possible to access the alarms and timers set on each echo device? if not, is it a feature that can be implemented?

Würde mich auch interessieren


Allow runners to determine throughput

With this commit Rally recognizes a new response metadata property
throughput from runners. When it is present, it will be used as is for
creating throughput samples. The following restrictions apply:

The runner must only be executed by one client. This is needed
because throughput is calculated across all clients but in this case
throughput samples are created without any further aggregation.
The runner should be rate-limited to avoid that too many throughput
samples are created. When throughput is calculated, all responses are
bucketed into one second buckets but when the calculation is overridden,
each sample also results in one throughput sample.

We also change the existing IndicesRecovery runner to use the new
property in order to calculate throughput directly.

Thank you for the change!


bug: import error using 2.3.6

Description
unable to import as described in the README. seems like the module is exporting default.default. I have to do the following to get it to work:

Screenshots:

Reproduction steps
unable to do `import HolyLoader from 'holy-loader'`

Screenshots
No response
Logs
⨯ Internal error: Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

### Browsers

Firefox, Chrome, Safari, Microsoft Edge, Opera

### OS

Mac

Hi @jonathanong
Thank you for this issue. What bundler are you using?

I'm using NextJS

@jonathanong can you npm update holy-loader and confirm whether this is fixed now?

yep it's fixed! thank you


Placement of currency symbol/code on input fields set to none doesn't work

Describe the bug
Placement of currency symbol/code on input fields set to none doesn't work, it still shows up
Steps To Reproduce

Show the code of your field.

MoneyInput::make('budget_value')
                    ->label(trans('cruds.execution.fields.budget_value') )
                    ->default(0)
                    ->live(),
MoneyColumn::make('budget_value')
                    ->label(trans('cruds.execution.fields.budget_value') )
                    ->sortable(),

What changes have you made to your global config?
Version of:

This package 1.3.2
Filament 3.2.92
PHP 8.3.8
Laravel 11.11.1
Anything else that you think might be relevant

Expected behavior and actual behavior
A clear and concise description of what you expected to happen and what actually happens.
Screenshots

Additional context
Add any other context about the problem here.

I'm not sure that I understand the problem. You don't want the currency symbol to show at all? If so, you can set symbolPlacement to hidden in the next version 1.4.0.


Swift Tutorial - Internal Error when clicking Create Account

On page 5 of the tutorial, https://codelabs.developers.google.com/codelabs/firebase-ios-swift/#4, I get an Internal Error when clicking "Create Account".
Here is the tail of the log from the Xcode console:
<FIRAnalytics/DEBUG> Uploading data. Host: https://play.googleapis.com/log
2016-06-07 16:52:47.281 FriendlyChatSwift[90258:] <FIRAnalytics/DEBUG> Received SSL challenge for host. Host: https://play.googleapis.com/log
An internal error has occurred, print and inspect the error details for more information.

Also, it's not clear how to "print and inspect the error details". Turning on the -FIRAnalyticsDebugEnabled option added other logging, but nothing about the error that I could tell.

Workaround seems to be entering an email address with an @ character and a non-zero length password. Then there will be a useful error message in the log or a successful login.

Yes, @ is needed for emails. This is being checked and fixed at Firebase side, not a sample issue.


iter_default_integrations() missing 1 required positional argument: 'with_auto_enabling_integrations'

TypeError: iter_default_integrations() missing 1 required positional argument: 'with_auto_enabling_integrations'

This iterator used to be parameter-less. It appear it should still be that way, and that it should use the outer with_auto_enabling_integrations variable.
https://github.com/getsentry/sentry-python/blob/bf48bd0681c68239ee651224b59b9d8aee78f514/sentry_sdk/integrations/__init__.py#L28

oops, I misread the code...

Hey Ofer, is this error triggered in the sdk somewhere?

I was using the function directly, and previously it didn't require a parameter. When I upgraded the SDK it broke my code.
But it's all good now, I've adapted the code.
Though generally I would say there should be an simple and documented way of selecting which integrations to include/exclude.

@koreno not entirely sure why you need that. You can pass default_integrations=False and then enable each integration one-by-one (importing it explicitly)

Then it's all-or-nothing. In my case we just needed to exclude the logging
integration since we're using a different logging framework.

Ofer

On Fri, Jul 10, 2020 at 11:11 AM Markus Unterwaditzer <
<EMAIL_ADDRESS>wrote:

@koreno https://github.com/koreno not entirely sure why you need that.
You can pass default_integrations=False and then enable each integration
one-by-one (importing it explicitly)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/getsentry/sentry-python/issues/757#issuecomment-656547375,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABMCR2ICMJMAYXYK7OB333R23EK3ANCNFSM4OUSBOEA
.


Update startup.md

ConfigureServices is called by the runtime. It was mentioned in the documentation as it must be called, I think it will be called is the right wording

Hi @sreejukg, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@sreejukg That is a nice improvement.

@sreejukg  @GuardRex  please review. We like to keep our sentences as short as possible.

LGTM

I think all OK

Could remove the "en-us" from the link btw ... but that's a broader issue that might be addressed in a sweeping PR later (maybe along with 301 and 302 links).


Expose itemKey as a configurable property

This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[ ] #patch# - backwards-compatible bug fix
[x] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Exposed itemKey as a configurable property.  List records with a matching itemKey will update instead of fully re-rendering when the record changes.

Changes Unknown when pulling 96fb90554c27bd1d5b075fd810f651126a8acf4d on sglanzer:keys into ** on ciena-frost:master**.

Changes Unknown when pulling 96fb90554c27bd1d5b075fd810f651126a8acf4d on sglanzer:keys into ** on ciena-frost:master**.

Approved


set pydivert to version 1.0.2

pydivert appears to have made changes in 2.0.0 that broke fakenet-ng

Implemented support for the latest PyDivert.


Fix Nav Bar burger Menu alignment

waiting on: https://github.com/Megabit/Blazorise/issues/2330

no longer needed


Governance - AzDo Bug: 5845

Review the Governance summary page for issued details.
Governance Report Release/6.0:
https://dev.azure.com/dnceng/internal/_componentGovernance/dotnet-arcade?_a=alerts&typeId=16588505&alerts-view-option=active
AzDo BUG:
https://dev.azure.com/dnceng/internal/_workitems/edit/5845

Release Note Category

[ ] Feature changes/additions
[x] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

Updates To Address Governance Issue PR:
https://github.com/dotnet/arcade/pull/14551

PR Was Merged.
I verified that the 6.0 branch now has an 'all good' state in it's governance report:

I manually resolved the AzDo Bug:
https://dev.azure.com/dnceng/internal/_workitems/edit/5845


Redirect to .org

@TylerSheffels would this work?
cc: @emord @millerdev

@benrudolph I think you want to do something like https://github.com/dimagi/commcarehq-ansible/blob/master/ansible/roles/nginx/vars/cchq_redirect.yml and https://github.com/dimagi/commcarehq-ansible/blob/master/ansible/deploy_proxy.yml#L16
The downside is that this requires adding a couple variables to the config settings

thanks for the info. closing for now until i have opportunity to fix

k should be good, just need to update the variables on salt

@benrudolph You will also need to add in a line in deploy_proxy.yml:
https://github.com/dimagi/commcarehq-ansible/blob/master/ansible/deploy_proxy.yml#L16

yep thanks, i strangely woke up last night and that was at the forefront my mind


chore: update default prover url

The ZKPool URL no longer includes the port. Update to remove port.
Reference: https://docs.zkpool.io/guides/how-to-connect-ZKPool/

Summary by CodeRabbit

Refactor

Updated the default prover URL to enhance connectivity and performance.

thanks!


GLTF 2.0 , children of children nodes are not loaded

Hello,
I have a node tree in my GLTF, but apparently, only the first level children are loaded.
I can fix It, but I wanted to know if there was a plan for that.

ping @bghgary

After some checks, that only appends when I have empty nodes.Removing them worked...

@nbouayad Can you attach the glTF file? I can take a look.

Up?


Audit Sponsership Paymaster

We have an audit with Chain Light starting 1st Oct. This ticket covers the audit process but does not include remediations.

@livingrockrises could you assign this to yourself please.


added screenshots for wiki

resolves #64
DCO1.1 Signed-off-by: Narine Cholakyan<EMAIL_ADDRESS>

Hi narinearraul,
Thanks for submitting this pull request!
I can confirm that the DCO1.1 sign-off has been included. It is okay to process this pull request.
dco-bot


itz auth login command suggestion wrong global flag

I ran the following command
itz doctor init
It failed and suggested following command
itz auth login --from-file /path/to/token.txt --service builder
Unfortunately, this suggestion also fails, becuase --service is an unknown global flag. Maybe --service-name is the correct one?
itz auth login --from-file /path/to/token.txt --service-name builder
See Screenshot

This feature has changed from how this works specifically, but I believe this will be now addressed in the 1.0 release (upcoming).


Resize Error

When autoResize is enabled, each window resize doubles the number of graphs, duplicating the same line over and over.

Fixed in 0.2.0, see https://github.com/statnett/vue-plotly/issues/6#issuecomment-399090119


Published in v0.8.0


Exclusion tool and doc updates

Guidelines
Where the guidelines in CONTRIBUTING.md followed? yes, especially the new guidelines I just added
Purpose
Describe the problem or feature in addition to a link to the issues. Documentation had some errors and we've had common feedback about needing easier ways to apply new settings gradually.
Approach
How does this change address the problem?  Added tool for more easily generating exclusions. Documentation corrections and better standards for branch naming.

Thanks @mabaumgartner had a copy/paste fail

The generate exclusions script is a great idea!


Bump some dependencies

bors r+

Ah, I didn't get the notification for the r+. The latest commit upgrades some npm packages and eslint complains a little about the TypeScript version. Do we care about that?

Actually, I think it was complaining even before my changes (we were already on 3.9).

r? @kjeremy

Rebased.

bors d+

bors r+
...I guess

Oof...
@matklad r=matklad

Build succeeded:

Rust (macos-latest)
Rust (ubuntu-latest)
Rust (windows-latest)
TypeScript


install jupyterlab

should have a minimal set-up for jupyterlab

see discussion in https://github.com/SyneRBI/SIRF-Exercises/issues/90#issuecomment-855203308


Update dependency

Update dependency to works with SF4

@mimol91 Thanks for the patch. I've also released current version as v1.0.0, so you can now use it as a stable dependency.


GUI bugfixes and feature catchup

Task: Fix those bugs!
Assignees: @kev007
Deadline: TODAY! (11.05.2016 @ 23:59)
Existing bugs:

URL encoding
Incorrect bounding box coordinates

Missing Features:

Username filter not being sent to backend
Using location coords if tweet.coordinates.coordinates is empty

use uri /api/testgeo


Feature: add a progress bar for new migration

Please follow on https://github.com/gogits/gogs/issues/829


New BLOCK: Deploy app on AWS VPC Site (VM Based)

Deploy a demo app on AWS, and publish the app via AWS vpc site. This module will focus on deploying an app on EC2 instances, published via the AWS VPC Site created by XC.

Ran into initial issue with NAT gateway. AWS base module needed to have a NAT added.


Scaffolding Sutil-Safe generates src/Shared/Shared.fs.js

I do not see src/Shared/Shared.fs.js within the template,
but it was generated when scaffolding Sutil-Safe

Hey! Thanks for opening the issue.
This was an embarrassing oversight on my part, this file somehow got into the nuget package that was pushed.
I've pushed a new version (v2.0.1) with that file removed.
Cheers :)


Date/Time profile captions generation

When applying the Date/Time profile to an object the captions for the datetime_t fields are not derived from the original timestamp_t attribute.

Can you explain more?
I assume you're talking about the Description field of the table, and this shows the description of the original attribute. It does not show the description of the data type, but that is never done. The data type descriptions are only shown over on the "Data Types" page.
In any case, if you could show the actual versus the expected, it would help me understand this issue.

Hey sorry, I should have been more descriptive. This is a view of the device object, which hastimestamp_t fields:

modified_time
created_time
first_seen_time
last_seen_time

When the Date/Time profile is applied, then the expected behavior is that the datetime_t versions of these fields are also shown in the browser, with the proper caption, name etc.

Caption
Name
Requirement
Type
Description

Created Time
created_time_dt
Optional
Datetime
The time when the device was known to have been created.

Created Time
created_time
Optional
Timestamp
The time when the device was known to have been created.

Instead of

Caption
Name
Requirement
Type
Description

created_time
created_time_dt
Optional
String
The time when the device was known to have been created.

Created Time
created_time
Optional
Timestamp
The time when the device was known to have been created.

We can see this behavior when running an extension that has added some additional fields to an object and the object has timestamp_t fields from the base schema.

you know what, after forcing myself to double-check a few things this was of course a user error, please ignore, thank you 👍


Risk Tracker: bug in discounting environment influence on close proximity interactions

On the website, if you select 1 foot distance you get the following warning

We are ignoring environment choice in this calculation. We are not confident that good ventilation or being outdoors substantially reduces the risk when people are this close to each other.

In the spreadsheet this appears to be handled by this fragment of the Activity Log!F formula
IF(AND(AD12=ACTIVITY_TITLE_CUDDLING,
             AA12=ACTIVITY_TITLE_OUTDOOR),
         ACTIVITY_TITLE_INDOOR,
         AA12)

But this special case doesn't apply to the other environments, such as planes, trains, "indoors with HEPA" or "a space with one or more sides open". This results in outdoor cuddling activities being rated 4x more dangerous than partially indoors, all other parameters the same.

Official release coming in the next few days. If you want to test it, you can here: https://deploy-preview-1017--microcov.netlify.app/tracker/changelog


Want to add glass morphisms.

Issue Type:
Feature Request Adding
Want to add:

@Avik-creator ig this is already present in the repo

I see but i haven't found it yet so I made a pr. I will check it again, if found I will close the issue @DEEPALI-SUK


make ibc Height type ser/de though string

since Height has a canonical string representation ("{revision_number}-{revision_height}"), it would make sense to make it serde through string. this would also make it easier to quickly parse a json message containing a height, instead of reading { "revision_number": N, "revision_height": M }.
we should check if anywhere expects the height to be the expanded json first, to ensure nothing breaks.

implemented in https://github.com/unionlabs/union/pull/3166


[WIP] Allow full error log

Currently we truncate (after 200 characters) the log error / warning that was received when connecting to a provider - In this patch we discard this action in favor of dealing with the full log in the UI.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1506718
cc: @cben @serenamarie125

@miq-bot add_label bug, gaprindashvili/yes

Ping @jrafanie .. you seem to be the original author behind the "truncate error messages to 200 chars" change. Guessing there may have been a reason to do that..

@himdel you mean it was me who wrote the original line? according to annotate it was Joe Rafaniello.. 😄 ....

@nimrodshn This also affects logging and we store this string in the authentications table in the status_details column. We truncate it because error responses from providers can be huge.  We've had may situations where a repeated error condition on login would fill the log or not fit int he varchar column.
I'd be ok with a few different solutions:

extending the truncate length to fit a reasonable error message to fix your bug (while still fitting into the status_details column)
Or move the truncate to the log line and where we save the status_details and all callers of authentication_check

@jrafanie just to be clear - your'e proposal is to truncate at several different locations - instead of one, I am not sure how that resolves my bug.. I understand that allowing more characters seems reasonable I just don't follow your'e other suggestion.

Also, If I were to truncate in different locations like you suggested, how much to truncate in each place?

Log file (I was thinking of doubling the allowed characters to 400)

status_details column (I was thinking of keeping it the same here)

all callers to authentication_check (I was doubling the allowed characters to 400)

@nimrodshn If you can reliably create an authentication failure error message on your provider > 500 characters, I would avoid truncating here and instead truncate to 400 or 500 in the log line, saving status_details into authentications, and other callers and verify it fixes your issue while not raising an error or silently failing.

@nimrodshn The other thing to keep in mind is the length might have been truncated for easier presentation in the UI so it might look strange if various places in the UI don't give enough visual space to show it.

About status_details column, it's currently not visible in UI, that's why no point making it longer.
if 400 vs 200 is as much as we're willing to raise, not worth the effort IMHO.
I was hoping for several KB, at least for UI.

The other thing to keep in mind is the length might have been truncated for easier presentation in the UI so it might look strange if various places in the UI don't give enough visual space to show it.

Right, showing a screenful of garbage in UI wouldn't look pretty, but there should be something to click to get more info.  See my comment https://github.com/ManageIQ/manageiq-ui-classic/pull/2862#issuecomment-348198346 for my perspective why when adding a provider doesn't work, and you don't even have any details to diagnose/google/ask for help, it's a miserable experience.

About authentications.status_details column it's currently not visible in UI, that's why no point making it longer. (provider details only shows "Error"/"Success" status & how long ago)

@cben I believe it's shown when you hover over the authentication checkmark/X in the provider screen.  There's a popup that shows the error for failures.

Maybe here @cben ?  https://github.com/ManageIQ/manageiq-ui-classic/blob/2f270bb4f872d19559f348f8260186db1f2bfb45/app/helpers/textual_summary_helper.rb#L200

@jrafanie

If you can reliably create an authentication failure error message on your provider > 500 characters, I would avoid truncating here and instead truncate to 400 or 500 in the log line

I did write a small server that does just this (return a really long response..)
Where exactly is here though?

@miq-bot add_label wip

I did write a small server that does just this (return a really long response..)
Where exactly is 'here' though?

"here" means the line change in this PR (remove the truncate call like you did but truncate it in those other areas)

@jrafanie Now is it OK with you? are there any more places I should truncate the err message?

@nimrodshn it seems ok, what test scenarios did you run?  Note, if there's any customization in the UIs for each provider that calls authentication_check, they'll be affected by this change.

@jrafanie The basic scenario I tried to solve was when a user adds a new provider he gets a truncated error message. With this PR he would get a longer message which will somehow be handled gracefully in the UI (not yet implemented).
Are there any other use cases you think I should consider?

@nimrodshn I'm ok with this.  The backend side is covered by the truncate for the column and log line so as long as @himdel is fine with a possibly enormous error message string being returned to all provider UIs, then I'm good with merging.

@jrafanie No issue from me :+1:
UI-side, we talked about having a opt-in option to add_flash that would make the UI only show the first line until the user expands the message.
So assuming no-multimegabyte responses... :)

(That said, maybe it would be good to wait with backporting to gaprindashvili until the UI PR is merged as well, so that we don't introduce a temporary state where the user could get the whole error.)

Sounds good to me.  @nimrodshn Is the ui classic PR standalone?  Can we merge that and backport it first?  Then un-WIP this and merge and backport?

@jrafanie Yes that's exactly the plan. I just need to give the UI PR few final touches before it's done.

@jrafanie just as a lower bound I have added another truncate on authentication_check as suggested by @cben in the UI PR.

@cben we check our ems/provider authentications on a schedule every hour I believe, so typically, I'd expect us to persist the status_details at most until the next scheduled check and even then it will be replaced with a "new" status.

@jrafanie UI PR was merged. So, unless any objections this is ready 😄 .


[OTHER] Improve Navbar UI for mobile device

Description
Improve the mobile navbar by using 100vw 100vh for better visibility and user experience.
Expected Behavior
The mobile menu should open in full screen.
Actual Behavior
now it only shows a piece of block
Screenshots (if applicable)

Assign it to me ill work on it @devvsakib

hay @saivinaygondrala do you still want to work on this?

I can work on it. Assign it to me @FrancescoXX .

This was resolved in PR #130 @FrancescoXX

we are keeping this for now


Object Replacement Characters not being sanitized

Hey there, I'm Alex from Tiptap 👋🏻
I wanted to upstream this issue to you as it's something that's affecting linkifyjs directly. It seems that linkifyjs does not handle properly the sanitization of a string when it comes to the find method that looks for link matches within a string. Here's an example of this character: \uFFFC this is an object replacement character and it looks like an empty string to the naked eye but if you pass something like find('https://google.com this) (where the space between the .com and this is the given character \uFFFC) the method will return you that the link is https://google.com this which some might say it's correct as it's a valid unicode character but people will be very confused by this as we've been by the reports we were having in our editor repo.
Just wanted to upstream this to you to see if it's something that you'd consider adding to the find method or to help anyone that might be having this issue so they know what could be about.
This was the issue in which we ended up discovering this https://github.com/ueberdosis/tiptap/issues/5679 just in case you're curious what this could potentially cause :)
Hope you have a great day 🙇🏻

Hi Alex, thanks for reporting! This should be a doable fix, linkify can interpret \uFFFC as whitespace and therefore exclude anything that comes after it from the link. Will update here when the fix is available.

Thank you @nfrasser 🙇🏻

@alexvcasillas fix is available in the latest v4.2.0 release.


Improve the check for Node bootstrap issue

How to categorize this PR?

/area testing
/kind flake
What this PR does / why we need it:
Improving the check for Node bootstrap issue. Now containerd logs are checked for I/O timeout errors during image pull.
Which issue(s) this PR fixes:
Fixes #290
Special notes for your reviewer:
Depends on https://github.com/gardener/gardener/pull/11010 and/or https://github.com/gardener/gardener/pull/11008
Release note:

NONE

/remove-lifecycle stale


Cocoa IME input did not composited.

In OSX, IME input didn't composited. (ㅎ,ㅏ,ㄴ ...)

In Linux + XIM, IME composition is correct. ("한" = ㅎ+ㅏ+ㄴ, ...)

Tested with
.. commit 40da56fbf79d74bfbda6929432fc8cfed3546919 (OSX, Linux both.)
.. test application
Thanks.

Duplicate of #456.


Fix bugs in Planner calendar

Codecov Report

Merging #95 into master will decrease coverage by 0.99%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #95      +/-   ##
============================================
- Coverage     73.51%   72.52%   -1.00%
  Complexity      524      524
============================================
  Files            83       83
  Lines          1601     1623      +22
  Branches        166      167       +1
============================================
  Hits           1177     1177
- Misses          378      400      +22
  Partials         46       46

Impacted Files
Coverage Δ
Complexity Δ

...seedu/tr4cker/ui/planner/PlannerCalendarPanel.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...ava/seedu/tr4cker/ui/planner/PlannerTabWindow.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

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 b0c9587...e035f9d. Read the comment docs.


Add more wicked version tests to ensure it works

The SP....-channel-4 stuff:
https://github.com/jmesnil/wildfly-channel/blob/main/core/src/test/java/org/wildfly/channel/version/VersionMatcherTestCase.java#L210

Caused by: java.lang.NumberFormatException: For input string: "202109080827"


Unable to test another model

Hi!
Did anybody tried to test another model in server/models/__tests__?
in post.spec.js we can see this:
import test from 'ava';
import request from 'supertest';
import app from '../../server'; // A
import Post from '../post';
import { connectDB, dropDB } from '../../util/test-helpers';

When I make another file, let's say user.spec.js, line A cause errors in npm run test script.
Any suggestions?

I'm also having this exact problem, seems to be some sort of clash between different Mongo processes but I can't figure out how to get the different tests to share the same process

There are multiple issues with the test environment.
One being that the arguments for test start the app on port 8080 every time, so multiple instances of the app cannot connect at the same time.
Other issues include connections to mongoDB before mockgoose is initialized and async execution issues where tests will run before the model creation completes in the beforeEach hook.
See my pull request for fixes to these issues https://github.com/Hashnode/mern-starter/pull/250

@MrChristofferson up to take a look at the test issues? This issue might be related to #250

This should be resolved with #367


Change parameter name in normal distribution from tau to sigma

Description
When using Distributions.Continuous.normal the normal distribution is initialized by mu (mean) and tau (standard deviation). More common is to use sigma as descriptor for standard deviation.
Since tau is part of an alternative parameterization describing the reciprocal of the variance it may be misleading to some users.
Additionally the normal distribution often is initialized by N(mean,variance) rather than the mean and standard deviation, which increases the need for a precise description.
Related information
https://en.wikipedia.org/wiki/Normal_distribution#Alternative_parameterizations

fixed by 28d06fc871b707579efe921d0bf86f2c436d968b


Tree view modal assistant

Description
Adding the Tree View on the AssistantDetail modal.

[x] Add new front API route to call connector getContentNodes
[x] Add swr function to get the content nodes
[x] Update the modal component to build a Tree instead of displaying the resources

Risk
Display was already kind of broken, we were displaying only the managed ds and just the number of item selected.
Deploy Plan
Nothing special.

(I worry a bit the two implementations will diverge?)

There's not a lot of code to be shared but I'll look into it. Merged this one already because sharing is not blocking 🙏🏻


Snowflake 0.11 driver incorrectly wrapping table names in double quotes

What happened?
This was working fine in 0.10 and the GO 1.72 driver.
Starting in 0.11 and the GO 1.80 driver table names are being incorrectly wrapped in double quotes.
This is breaking SQL selects now which can't find the table..
The ANSI standard below should be followed.
https://forum.knime.com/t/inquiry-regarding-double-quotes-in-table-name-creation/77438/2
Double quotes will be applied around the name of a table when the table name is not all uppercase, or contains spaces and possibly some other characters
If the table name is purely upper case and underscores, the DDL statement that snowflake shows won’t contain double quotes:
How can we reproduce the bug?
No response
Environment/Setup
No response

@lidavidm Snowflake's way of handling things is that if it's not in quotes, everything gets upper-cased automatically. Because our CI tests were using a lower-cased table name, we were running into an issue where some queries used quotes and others didn't in the validation suite. We then surrounded every query with quotes in the validation suite, but the table name itself was not surrounded with quotes for ingestion so we ended up with flaky CI tests where it might or might not find the table. https://github.com/apache/arrow-adbc/pull/1561 fixed the flakiness of the tests by making all of the casing consistent - what you put in is what you get - by wrapping identifiers in quotes if they weren't already.

Double quotes will be applied around the name of a table when the table name is not all uppercase, or contains spaces and possibly some other characters
If the table name is purely upper case and underscores, the DDL statement that snowflake shows won’t contain double quotes

In theory, that's essentially how the current 0.11.0 version of the driver works. If you provide a string for a table name where the characters aren't all uppercase or contains spaces / possibly other characters, then because we wrap it in double quotes, the table name will be handled correctly as provided. If the table name is provided with all of the characters already uppercased and without any special characters, then the fact that we add quotes to it won't affect its usage at all.
So this pretty much comes down to a question of whether or not we force users to perform the upper-casing themselves (the current version) or force users to include their own double quotes like they would if they were writing the raw SQL query themselves. There isn't a programmatic way for us to be able to tell what the user wants before-hand, the only alternative would be to make the auto-quoting an option they can toggle (and then we need to decide on a default).

https://docs.snowflake.com/en/sql-reference/identifiers-syntax
Snowflake reference

https://github.com/tobymao/sqlglot/blob/main/sqlglot/dialects/snowflake.py
Sqlglot reference..

I'll post some testing results between 0.10 and 0.11 later today.. Will test dummy, DUMMY, "dummy" and "DUMMY" with and without fully qualified schema..
I think we should follow Snowflake and SQLGLOT expected behavior as odd as it is to avoid any type of confusion.
If the table has no quotes then auto UPPERCASE the name.
If the table has quotes then use it as is.

@davlee1972 Thanks for the examples here, it's definitely a problem if we're breaking when someone passes quotes in as part of the string. I'll take a look and see what our best solution here is, most likely the best choice is going to be to go back to putting the onus on the caller to add the quotes and make some modifications in our validation suite.
I'll do a first pass at this tomorrow


Make VList's children Rc'ed

Description
Separated from #3042 to address bundle size issue.
This pull request makes VList to store children with Option<Rc<Vec<VNode>>>.
This increases the performance of {self.children.clone()}, which increases for about ~5% when running the benchmark locally with SSR Benchmark based on the function_router example. However, since we do not have a benchmark that depends heavily on cloning children, the performance increase might not be fully demonstrated.
But since ChildrenRenderer<VNode> stores VNode in a Vec<VNode>, it still involves an allocation every time children is passed.
This will be addressed in #3042, which should give a further performance increase.
This is also not a breaking change.
Checklist

[x] I have reviewed my own code
[ ] I have added tests

Looks like function_router is not a good example for benchmarking bundle size for this particular pull request.

Twiggy:
       +2643 ┊ <T as alloc::slice::hack::ConvertVec>::to_vec::hc92fe50ec0e432f4

The size increase is due to that rustc can no longer determine whether Clone is used for VNode (VList's children's Vec) or not at compile time because VList now uses Rc::make_mut and Rc::try_unwrap. Most examples are simple and do not involve this usage and hence resulted in a size increase.
This pull request is optimised for applications that actually uses children / VNode, which a decrease can be seen in the function_router and router example. I would expect most application with reasonable complexity would include these usage.
I have added a Many Providers test which does not show too much of a difference in this pull request,
╭─────────────────┬───────┬──────────┬──────────┬───────────┬────────────────────╮
│ Benchmark       │ Round │ Min (ms) │ Max (ms) │ Mean (ms) │ Standard Deviation │
├─────────────────┼───────┼──────────┼──────────┼───────────┼────────────────────┤
│ Baseline        │ 10    │ 300.598  │ 301.481  │ 300.914   │ 0.265              │
│ Hello World     │ 10    │ 373.998  │ 382.672  │ 376.125   │ 3.212              │
│ Function Router │ 10    │ 1161.455 │ 1189.956 │ 1169.719  │ 10.572             │
│ Concurrent Task │ 10    │ 1009.627 │ 1016.863 │ 1012.009  │ 2.213              │
│ Many Providers  │ 10    │ 1146.857 │ 1183.132 │ 1158.769  │ 14.629             │
╰─────────────────┴───────┴──────────┴──────────┴───────────┴────────────────────╯

But with slight modification with the benchmark adapted for #3042, the performance would increase about 20%.
╭─────────────────┬───────┬──────────┬──────────┬───────────┬────────────────────╮
│ Benchmark       │ Round │ Min (ms) │ Max (ms) │ Mean (ms) │ Standard Deviation │
├─────────────────┼───────┼──────────┼──────────┼───────────┼────────────────────┤
│ Baseline        │ 10    │ 300.385  │ 301.135  │ 300.652   │ 0.274              │
│ Hello World     │ 10    │ 377.968  │ 385.530  │ 379.333   │ 2.535              │
│ Function Router │ 10    │ 1112.299 │ 1134.035 │ 1117.234  │ 7.269              │
│ Concurrent Task │ 10    │ 1009.125 │ 1012.555 │ 1010.737  │ 1.059              │
│ Many Providers  │ 10    │ 895.768  │ 903.255  │ 900.444   │ 2.456              │
╰─────────────────┴───────┴──────────┴──────────┴───────────┴────────────────────╯

I think the performance increase might worth the bundle size tradeoff in this case?

Would work for me, if PR gets updated.


wifibox works but routing to <IP_ADDRESS> died

Description
A clear and concise description of what the problem is.  What is expected from the application?
wifibox stopped working after an update of GhostBSD
It launches and runs and it connects to the internet, verified with wifibox console, yet wifibox0 is <IP_ADDRESS>.0
Host operating system
Output of `uname -a`.
FreeBSD martin-ghostbsd-pc 14.0-STABLE FreeBSD 14.0-STABLE GENERIC amd64

Wireless NIC
Relevant output of `pciconf -lv`.
pciconf -lv
    subclass   = RAM
ppt0@pci0:0:20:3:	class=0x028000 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa370 subvendor=0x8086 subdevice=0x4030
    vendor     = 'Intel Corporation'
    device     = 'Cannon Lake PCH CNVi WiFi'
    class      = network

Wifibox version
Output of `wifibox version`.  Note that only the latest version is supported.
version
wifibox version 0.13.0
Disk image checksum: 1775c3767f5c480565079def723e8c8f79b3624c9e068e16565569833a6a44a3

Disk image type and version
The kind of VM image in use, e.g. Wifibox/Alpine, and its version.

Logs
Please copy and paste any relevant log output from the following sources:

- /var/log/wifibox.log (with DEBUG logging verbosity)
- /var/run/wifibox/appliance/log/dmesg
- /var/run/wifibox/appliance/log/messages

Hint: The DEBUG log verbosity could be configured in the `core.conf` file, which is located in the `$LOCALBASE/etc/wifibox` directory.

│2024-04-30T14:40:10-0400 DEBUG [bhyve] rdmsr to register 0x64e on vcpu 0                                                                        │
│2024-04-30T14:40:10-0400 DEBUG [bhyve] rdmsr to register 0x34 on vcpu 0                                                                         │
│2024-04-30T14:40:10-0400 INFO  Guest wifibox has started up                                                                                │
│2024-04-30T14:40:10-0400 INFO  Guest is managed by PID 5299                                                                                │
│2024-04-30T14:40:10-0400 INFO  Bringing up Unix Domain Socket pass-through                                                                      │
│2024-04-30T14:40:10-0400 INFO  Found guest IP address: <IP_ADDRESS>                                                                                │
│2024-04-30T14:40:10-0400 INFO  Configured sockets: [path=/var/run/wpa_supplicant/wlan0,user=root,group=0,mode=770,port=1200                     │
│path=/var/run/wpa_supplicant/p2p-dev-wlan0,user=root,group=0,mode=770,port=1201]                                                                │
│2024-04-30T14:40:10-0400 INFO  Hooking up <IP_ADDRESS>:1200 as /var/run/wpa_supplicant/wlan0 (root:0@770)                                           │
│2024-04-30T14:40:10-0400 INFO  Hooking up <IP_ADDRESS>:1201 as /var/run/wpa_supplicant/p2p-dev-wlan0 (root:0@770)                                   │
│2024-04-30T14:40:10-0400 INFO  End: wifibox restart                                                                                │

Additional context
Add any other context about the problem here that might help the investigation.
dhclient -d wifibox0
DHCPREQUEST on wifibox0 to <IP_ADDRESS> port 67
DHCPACK from <IP_ADDRESS>
bound to <IP_ADDRESS> -- renewal in 432000 seconds.
Have you tried to turn it on and off?

[X] Yes, I have read all the manual pages first!

what's weird is this:  bound to <IP_ADDRESS> -- renewal in 432000 seconds.
dunno where <IP_ADDRESS> is coming from

If the IPv4 address of the wifibox0 interface is <IP_ADDRESS> that means that dhclient could not yet get an address.  It may take a while to have the process completed.  If the resulting IP is something "weird", that is probably a cached IP from an earlier lease.
I am curious if that is the same if you configure a static IPv4 address for the wifibox0 interface?
If the static address assignment works, a problem could be around udhcpd in the guest.  You can learn about its health by using the following command:
wifibox# fgrep udhpcd /var/log/messages

At the same time, it might be worth to check the udhcp.conf file in $LOCALBASE/etc/wifibox/appliance.  Note that the default values there were changed, because I realized that a single-adddress range (as it was before) can become depleted easily.  That is because that single address may not be released when it is requested once more in a short period of time.  You may have to change udhcpd.conf in the following way:
start           <IP_ADDRESS>
end             <IP_ADDRESS>
max_leases      64

I have it like this:
`> cat /usr/local/etc/wifibox/appliance/udhcpd.conf
This is a configuration file for udhcpd(8) with relatively sane
defaults.  Consult https://udhcp.busybox.net/udhcpd.conf for more.

The value of interface should match with the one defined in the
interfaces.conf file: interface should be exactly the same,
router should correspond to address and subnet is the
netmask.  According to these settings below, IP addresses are
handed out for the <IP_ADDRESS>/24 network.  Even though there is a
single client expected, on quick restarts, the previously allocated
address might not be released, so there should be some room left for
such overlaps.  In the opt dns line, the %%DNS%% variable would
be replaced with the IP addresses of the DNS servers as provided by
the wireless network (wifibox extension).

Change these only if this is not suitable.
start           <IP_ADDRESS>
end             <IP_ADDRESS>
max_leases      64
interface       eth0
opt     subnet  <IP_ADDRESS>
opt     router  <IP_ADDRESS>
opt     dns     %%DNS%% <IP_ADDRESS> <IP_ADDRESS>
opt     lease   864000
`
and now this on rc.conf
`## ## WIFIBOX ## ##
result
wifibox0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500         options=0         ether 58:9c:fc:10:c3:41         id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15         maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200         root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0         member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>                 ifmaxaddr 0 port 4 priority 128 path cost 2000000         groups: bridge         nd6 options=9<PERFORMNUD,IFDISABLED>
wifibox_enable="YES"
devmatch_enable="YES"
devmatch_blocklist="if_iwm if_iwlwifi"
#DHCP
#ifconfig_wifibox0="SYNCDHCP"
background_dhclient_wifibox0="YES"
defaultroute_delay="0"
#defaultrouter="<IP_ADDRESS>"
gateway="<IP_ADDRESS>"
ifconfig_wifibox0="inet <IP_ADDRESS>/24"
end wifibox
`

Does it work with static IP?

I have it like this:
cat /usr/local/etc/wifibox/appliance/udhcpd.conf

start           <IP_ADDRESS>
end             <IP_ADDRESS>
max_leases      64
interface       eth0
opt     subnet  <IP_ADDRESS>
opt     router  <IP_ADDRESS>
opt     dns     %%DNS%% <IP_ADDRESS> <IP_ADDRESS>
opt     lease   864000

and now static on rc.conf
## ## WIFIBOX ## ##
wifibox_enable="YES"
devmatch_enable="YES"
devmatch_blocklist="if_iwm if_iwlwifi"
#DHCP
#ifconfig_wifibox0="SYNCDHCP"

background_dhclient_wifibox0="YES"
defaultroute_delay="0"
defaultrouter="<IP_ADDRESS>"
ifconfig_wifibox0="inet <IP_ADDRESS>/24"
# end wifibox

ifconfig

wifibox0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
        options=0
        ether 58:9c:fc:10:c3:41
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000000
        groups: bridge
        nd6 options=9<PERFORMNUD,IFDISABLED>

Have you done the following on the host?
# service netif restart wifibox0
# service routing restart

static IP + service netif restart wifibox0
solved it.

I am glad that the static IP assignment solved the problem for you.  But it would be better if we understood why this was required in the first place.  In my books, that is a workaround, not a real solution.

I can help anyway you need, just let me know what would be useful to you for me to do.

Thank you!  First off, I would circle back to one of my earlier comments:
If the static address assignment works, a problem could be around udhcpd in the guest. You can learn about its health by using the following command:
wifibox# fgrep udhpcd /var/log/messages

Here is another command that might be worth to try:
wifibox# service udhcpd status

A problem could be that the templating of udhcpd.conf does not always work as expected and the service cannot start up.  But this has be to established first.


Crash reporting

Crash reporting
Maybe I have should turn to Mixpanel forum as well but I start here.
Im wondering how Mixpanel's crash reporting works. Im using AppCenter where many crashes are not shown but are reported by Mixpanel.
How are you handing Mixpanel crash reporting? And is there is some way I can use the bindings to throw exception so they end up in AppCenter?

I don't use it personally as I use AppCenter for crashes and MixPanel for analytics.
According to their docs it should be automatically recorded. It could be possible that if you have AppCenter active then MixPanel isn't tracking the crashes.

Yeah I also use AppCenter for crashes. It's just that I get concerned when Mixpanel reports crashes like shown below:

And AppCenter seem to function but don't report that crashing.

That sounds like a bug for the AppCenter team.

I’ll take it up with them and report back if I find anything


[BUG] Wrong mode selection regression

Describe the bug
Since v0.2.0+rpt20240418 (latest), rpicam-apps chooses a mode for vc4 that is not compatible with my sensor.
I'm using my own sensor's driver for this test.
[2:38:27.119131966] [6034]  INFO Camera camera.cpp:1183 configuring streams: (0) 402x352-YUV420 (1) 640x480-R10_CSI2P
[2:38:27.119547700] [6037]  INFO RPI vc4.cpp:621 Sensor: /base/soc/i2c0mux/i2c@1/wolfy@10 - Selected sensor format: 640x480-SGBRG10_1X10 - Selected unicam format: 640x480-Y10P
[2:38:27.123569826] [6040]  WARN IPARPI ipa_base.cpp:1055 Could not set SHARPNESS - no sharpen algorithm
[2:38:27.123904765] [6040]  WARN IPARPI vc4.cpp:278 Could not set NOISE_REDUCTION_MODE - no SDN algorithm
[2:38:27.127907298] [6037] ERROR V4L2 v4l2_videodevice.cpp:1906 /dev/video0[13:cap]: Failed to start streaming: Invalid argument
ERROR: *** failed to start camera ***

640x480-Y10P should be 640x480-pGAA, like it was before.
[2:19:35.628599254] [5648]  INFO RPI vc4.cpp:570 Sensor: /base/soc/i2c0mux/i2c@1/wolfy@10 - Selected sensor format: 640x480-SGBRG10_1X10 - Selected unicam format: 640x480-pGAA

Bug report
bug.txt
Additional context
It was working fine in previous versions, effectively selecting 640x480-pGAA.
It works if I build rpicam-apps against mainline libcamera, and also older libcamera (february build), and fails with only latest.
The same happens on both rpi4 and rpi5.
Feel free to ask for more information. I'll try to debug this on my side to see if I can bisect this more.

Can you provide specific details on the camera, i.e. what make/model, is it a mono or Bayer sensor, etc?  Also, can you provide the output of rpicam-hello --list-cameras please?

Unfortunately this sensor is not yet mainlined. I plan on doing so once ready.
Here is the output of rpicam-hello --list-cameras.
Available cameras
-----------------
0 : st-vd55g1 [804x704 10-bit MONO] (/base/soc/i2c0mux/i2c@1/wolfy@10)
    Modes: 'R8' : 320x240 [315.16 fps - (82, 112)/640x480 crop]
                  640x480 [181.52 fps - (82, 112)/640x480 crop]
                  800x600 [149.77 fps - (2, 52)/800x600 crop]
                  800x704 [130.06 fps - (2, 0)/800x704 crop]
                  804x704 [130.06 fps - (0, 0)/804x704 crop]
           'R10_CSI2P' : 320x240 [315.16 fps - (82, 112)/640x480 crop]
                         640x480 [181.52 fps - (82, 112)/640x480 crop]
                         800x600 [149.77 fps - (2, 52)/800x600 crop]
                         800x704 [130.06 fps - (2, 0)/800x704 crop]
                         804x704 [130.06 fps - (0, 0)/804x704 crop]
           'SGBRG10_CSI2P' : 320x240 [315.16 fps - (82, 112)/640x480 crop]
                             640x480 [181.52 fps - (82, 112)/640x480 crop]
                             800x600 [149.77 fps - (2, 52)/800x600 crop]
                             800x704 [130.06 fps - (2, 0)/800x704 crop]
                             804x704 [130.06 fps - (0, 0)/804x704 crop]
           'SGBRG8' : 320x240 [315.16 fps - (82, 112)/640x480 crop]
                      640x480 [181.52 fps - (82, 112)/640x480 crop]
                      800x600 [149.77 fps - (2, 52)/800x600 crop]
                      800x704 [130.06 fps - (2, 0)/800x704 crop]
                      804x704 [130.06 fps - (0, 0)/804x704 crop]

I think I may see the problem.  Your sensor driver is advertising Mono formats (R8 / R10_CSI2P) as well as Bayer formats (SGBRG10_CSI2P / SGBRG8).  You should only have the Mono ones defined in the sensor - I assume this is a mono sensor?  Otherwise, I can see the pipeline handler getting very confused with the mode selection routine.

Thanks a lot. You're correct, this is a mono sensor. Adding these modes are a hack for backward compatibility with very old kernel that only handle RGB.
It works by removing the Bayer formats.
Any way not to confuse the pipeline like before ? So I could keep my Bayer formats.

Any way not to confuse the pipeline like before ? So I could keep my Bayer formats.

I think it's unlikely we can change anything in the pipeline handler to account for this without things going wrong elsewhere.  But you might be able to get things to work if you manually choose the mode through the --mode or --viewfinder-mode command line argument in rpicam-apps.  Could you give that a try?

Hum according to the --help :
  --mode arg                            Camera mode as W:H:bit-depth:packing, where packing is P (packed) or U
                                        (unpacked)

I can't find a way to specify RGB or Mono. I tried this line that does not specify it
rpicam-hello --mode "640:480:10:P"

But got the same output.
I still wonder 2 things :

Why the issue is not happening at all in cam/qcam.
Why was it handled correctly before. Even if supporting both RAW and Bayer formats is kind of hacky.

--no-raw gives me the correct format
[4:43:02.553938509] [3773]  INFO RPI vc4.cpp:629 Sensor: /base/soc/i2c0mux/i2c@1/wolfy@10 - Selected sensor format: 640x480-SGBRG10_1X10 - Selected unicam format: 640x480-pGAA

Anyway, having both RGB and Mono modes is bugged.
I think I'll remove hacky RGB modes and look for another way to handle older kernels and ISP drivers.
I'll debug a bit more libcamera to see what changed in the mode selection code (btw if you have any pointers I'll galdy accept them).
Thanks a lot for your support.

Great, you can find the rpicam-app code for mode selection here:
https://github.com/raspberrypi/rpicam-apps/blob/c8351a09174f143424884081a69b6dd8018f4ba3/core/rpicam_app.cpp#L184
I'll close this down now, please do reopen if you find a fix.


[feature](debug point) add macro DBUG_RUN_CALLBACK

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Check exact extension in checkFilename utility

As described in #3060 I changed the checkFilename function to check the exact extension.

Thanks! looks good to me.


BasicAuth fails when authentication profiles are active on ServiceNow

Environment
Operating System: Windows Server 2019
ServiceNow module version: 4.0.0
PowerShell version: 5.1

Steps to reproduce
Create active authentication profile for API account in SNow that includes Basic and at least one another type (https://docs.servicenow.com/bundle/utah-platform-security/page/integrate/authentication/task/create-authentication-profile.html).
Establish a new session from ServiceNow-powershell module that uses Basic auth and send a test query to ServiceNow.
Expected behavior
User is authenticated by ServiceNow and requested information is returned.
Actual behavior
ServiceNow returns '401 unauthorized' message.
More Info
This issue occurs because ServiceNow does not understand how the user is trying to authenticate. The reason for that is because the authorization HTTP header is missing word Basic before the concatenated username and password's Base64 representation.
I believe if PS credential object is passed to Invoke-WebRequest (which is what this module appears to do) then PowerShell 5.1 does not prepend word Basic in the authorization portion of the headers. However, if this module would instead create authorization header itself when Basic auth is used, then it can use the correct format.
Although this bug is actually due to PowerShell's behaviour, it can be addressed with a minor change in this module. It looks like appropriate authorization headers are being created by the module to use with Invoke-WebRequest when OAuth is used but not for Basic.

@Saadi6 can you please validate the fix with authentication profiles?  I've done so without them.

Thanks for the quick update. #249 fixed it!
-------------v4.0.0-------------
The remote server returned an error: (401) Unauthorized.

 -------------------with fix 249:----------------
WARNING: Getting 10 records...

sys_id                : xxxxxxxxxcaxxxxxxxxx
environment           : xxxxx


Issues with the web server for predictions?

Hi,
I submitted a small CSV file (~20 000 precursors) for prediction of MS/MS and RT to the Prosit web server. The job is somehow still in process though it has been > 36 hours since submission.
I just wonder if there are any issues with the server right now? I have never experienced these waiting times before, even if I have submitted csv files with > 1 000 000 precursors for prediction.
Best,
Marc

Hi Marc,
you are right there were some issues with the Prosit web server. They should be fixed now. Check your Job again it might be done already.
Best,
Ludwig

Thanks for the quick reply!
I just downloaded the data, so yes it seems to work now :-).
Best,
Marc


dirnames broken in v1.0.1

(go1.12.6) (v10.16.0) dustin@lamport ~/p/taskcluster [bug1564122] $ mkdir -p foo1/foo2/foo3/foo4
(go1.12.6) (v10.16.0) dustin@lamport ~/p/taskcluster [bug1564122] $ echo 'Hi' > foo1/foo2/foo3/foo4/file.md
(go1.12.6) (v10.16.0) dustin@lamport ~/p/taskcluster [bug1564122*] $ cat x.js
var md = require('md-directory');
console.log(md.parseDirSync('./foo1', {dirnames: true}));
# with the old version:
(go1.12.6) (v10.16.0) dustin@lamport ~/p/taskcluster [bug1564122*] $ node x.js
{ file: { data: {}, content: '
Hi
\n' } }
(go1.12.6) (v10.16.0) dustin@lamport ~/p/taskcluster [bug1564122*] $ yarn upgrade --latest md-directory
# with the new version:
(go1.12.6) (v10.16.0) dustin@lamport ~/p/taskcluster [bug1564122*] $ node x.js
{ 'foo2/foo3/foo4/foo2/foo3/foo4/file.md':
   { content: '
Hi
\n', data: {}, isEmpty: false, excerpt: '' } }

Sorry, I should have some more detail there: the filename in the second-to-last example is incorrect; it appears to be a join of the directory name and the full pathname of the file.

Hi @djmitche, sorry for the breakage.
In updating dependencies, I had to update read-directory, which had a major revision that dropped support for extensions in filenames (see rationale here https://github.com/sethvincent/read-directory/pull/3).
It looks like this bug comes directly from read-directory 3.0.1:
console.log(readDirectory.sync('./foo1', {dirnames: true}))
// { 'foo2/foo3/foo4/foo2/foo3/foo4/file.md': 'Hi\n' }
console.log(readDirectory.sync('./foo1', {dirnames: false}))
// { 'foo2/foo3/foo4/file.md': 'Hi\n' }

where read-directory 2.1.1 yields:
console.log(readDirectory.sync('./foo1', {dirnames: true}))
// { 'foo2/foo3/foo4/file': 'Hi\n' }
console.log(readDirectory.sync('./foo1', {dirnames: false}))
// { file: 'Hi\n' }

Investigating further now...

📦 released in v1.0.2

Let me know if this version works for you. I'm not quire sure what this line of your console output is showing...
(go1.12.6) (v10.16.0) dustin@lamport ~/p/taskcluster [bug1564122*] $ node x.js
{ file: { data: {}, content: '
Hi
\n' } }

...given that the example script you showed has {dirnames: true} set.
This new release should at least correctly match the described API behavior in the README.md:

opts.dirnames Boolean – include or exclude subdirectory names in keys of returned object, default: false

And it's worth re-stating that 1.0.1 was a breaking change that removed the opts.extensions option (another change inherited from updating read-directory), so content keys will have the .md at the end of the filename. This, at least, should be fairly simple to work around if you need bare filenames.

what this line of your console output

yeah, that was probably copy-paste failure.

Looks good to me!  Thank you!


Chart.js component test failed

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in QA
Followed all applicable steps in the TROUBLESHOOTING guide: TODO
Checked for relevant discussions on Discord: https://discord.gg/pPERUuv
Checked that your issue isn't already filed: https://github.com/COVID-19-electronic-health-system/Corona-tracker/issues

Description
Chart.js component test failed
Steps to Reproduce
run 'yarn test' in the console
Expected behavior:
test passed
Actual behavior:
test failed
Reproduces how often:
100%

Is this test still failing with the most recent merge? When I try it, it passes.

That's because the test as it stands now isn't doing anything


Dwijottam's Suggestion

<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="description" content="{PUT YOUR OWN DESCRIPTION}">
<meta name="author" content="Dharmesh Kumar">
<title>{PUT YOUR OWN}</title>
<link rel="shortcut icon" href="{PUT YOUR OWN ICON PATH}" type="image/x-icon" />

You should add these lines in the top of the  tag
These are meta data which would make website more Crawl-able by Google

Ok


[BUG] Table with images not rendering properly

Describe the bug
Table containing image inside cell has issue to resize on screen.
To Reproduce
Steps to reproduce the behavior:

Go to '@good-karma 2.0.7 announcement post'
Scroll down to 'table part of post'
See error

Expected behavior
It should resize image same as table, image should stay inside table.

Smartphone (please complete the following information):

Device: any
OS: Android
Version 2.0.7

moving to NRC because this RC (release cycle) is overdue


[docs] fix incorrect version to flink-1.16.0

Fix an incorrect flink version in the documentation

@sywmomoda Thanks.
We will update in version 2.4.0. Would you like to check in 2.4.0?
Close this for 2.3 now.


Fix compatibility issue with Docker Compose 2

The Docker Compose project has moved from v1 to v2.
For now, it's still possible to opt-out of v2 and revert to v1 when using Docker for Mac. However this option will likely go away at some point. It's therefore a good idea to ensure GOV.UK Docker works with both versions.
As far as I can see, the only compatibility issue that existed is that the nginx container attaches to the 'default' network. As I understand it, the network called default is no longer implicitly created with Docker Compose v2, so it needs to be defined in the docker compose file.
For more info, see: https://github.com/docker/compose/issues/9015
It's not clear when this change happened as it's not documented as a known change: https://docs.docker.com/compose/compose-file/compose-versioning/
Demonstration of compatibility issue
The scripts bin/replicate-mysql.sh and bin/replicate-postgres.sh both run the command:
govuk-docker config

When running with Docker Compose v1, this command outputs a YAML document describing the current project config.
With Docker Compose v2, the command fails with an error:
$ govuk-docker config
docker-compose -f [...] config
service "nginx-proxy" refers to undefined network default: invalid compose project

However when the default network is explicitly defined in the main docker-compose.yml file, both v1 and v2 run correctly without error.
With this change applied, I'm now able to successfully run bin/replicate-mysql.sh and bin/replicate-postgres.sh regardless of the Docker Compose version I'm using.

This PR effectively makes the troubleshooting content added in #506 redundant – so I've removed it as part of this change.


DIODE layer corrections on gnd2gnd diodes in sky130_fd_io cells

Specifically, this error shows up in the top_power_lvc_wpad and top_ground_lvc_wpad, which are the two pads with ground-to-ground back-to-back diodes.  At issue is the DIODE layer covering the entire layout of sky130_fd_io__gnd2gnd_sub_dnwl layout.  Something about this layout causes the cifinput rules in the magic techfile to convert the TAP layers to diodes.  I suspect that maybe the lower level cell's diffusion is getting interpreted as "barediff", but this needs to be checked.

Found to be an issue in the tech file with handling the DIODE layer;  fixed.


reddit: specify attributes on all protocols

~/Repos/HPI-fork/my/reddit/common.py in <module>
     36
     37 # Note: doesn't include GDPR Save's since they don't have the same metadata
---> 38 class Save(Protocol, RedditBase):
     39     @property
     40     def subreddit(self) -> str: ...

TypeError: Cannot create a consistent method resolution
order (MRO) for bases object, RedditBase

Sadly the solution from #179 seems to make mypy happy but doesn't work for the python MRO itself
I think we should revert it for now so that its at least functional and doesn't error, hopefully can find a more concise way to do this.

ha, so on my toy example I tried swapping Protocol and AP, and it passes runtime as well now 🤔
class BP(AP, Protocol):
    b: int

will try it on reddit just in case 😅

Was trying to figure out if it could always just be put behind a typing.TYPE_CHECKING but would probably require another file like models.py so that we could still have _merge_comments in common -- seems to be another option


ddl.get_schema should return space IDs

It doesn't pair with retrieving metadata from system spaces and is required by connectors (e.g. cartridge-java).
This relates to the index metadata too, of course.

Don't do that. space_id may differ on different replicasets.


clean up document comment grammar

Thank you very much, @johnnyman727

@homu r+

:pushpin: Commit 64d3615 has been approved by MichaelHirn

:zap: Test exempted - status


fix: remove sudokumb sample

fixes https://github.com/GoogleCloudPlatform/dotnet-docs-samples/issues/924
I used it for one presentation, but never had a chance to write blog posts about it.  I'll resurrect it if I have time to write those posts.  In the meantime, I don't won't its maintenance burdening anyone else.

Force mergin, the errors in CI are unrelated.


Folder not getting created on providing format path.

Folder not getting created on providing format path.

Am I right that the folder did not create when you run this formatter via something like -f node_modules/cucumber-junit-formatter[:<output-file>], where output-file contains the full path to the new file?

Looks like this issue must correspond to JUnit itself.

yes @mvtm-dn i have given full path. You can please try providing it and see. And this should be this repo issue i feel and not Junit. Please let me know why it must correspond to JUnit?

Could you please provide an example?

Sorry its been long time and i am unable to find where i tried it. You can go ahead and close this as of now.

Am I right you try to use formatter with something like cucumber-js -f node_modules/cucumber-junit-formatter[:/non-existing-path/to-file/result.json?

I remember using this path in gulpfile.

In fact, formatter received from cucumber not the path to the resulting file but the instance to write log to. So my code neither opened nor created any files and/or folders. My mistake was referring to Junit in one of my previous comments. Indeed you need to open the issue in cucumber repo if the issue is still exists


method of composing reductions across layers

Hello! Thanks for your idea and codes, and I am applying the code to my model. There are two questions for me now：

The paper says "greedily search" over the parameters and have a "simple compose strategy" when composing reductions across layers。Does this mean that search the best rate in different later MLP layers and then simply compose them?
Can I use a single command line to realize composing reductions across layers? Or i need to repeat doing intervention on a single layer for a few times to compose reductions?

Thank you!

Hello, thank you for your interest in our work!

There might be a dependence on whether a reduction at a certain layer is helpful, given there is a reduction made in another layer. Therefore, we cannot just compose reductions after individually searching for the best rate per layer, while holding other layers fixed.

Added a script that walks through our procedure for this.

We wanted to check if the benefits of performing laser across layers are additive or not, so we employed a simple strategy. The current strategy we use is as follows:
1. Initialize a vector that represents different amounts of reduction across each of the different layers
2. Edit the model with Laser starting from the final layer (restricted over a set $\rho$ values)
3. Validate over the validation set of the dataset
4. use the signal from #2 to reduce or increase the amount of reduction
5. repeat until convergence
6. return the vector of reductions
I have also added a script that walks through this procedure under the scripts directory.
One thing to note: This search procedure is probably not the most efficient and only performs a sparse search over possible $\rho$ values and only over the encoder MLP layers ('MLP_FC_IN') layers. A more thorough search might result in additional increased improvements!

MANY THANKS!!!!


[XMPP->*] Changing nickname results to all messages being echoed "through XMPP"

Describe the bug
When the XMPP Nickname option is changed and Matterbridge restarted, all other protocols start echoing messages claiming they are coming through XMPP.
To Reproduce
Steps to reproduce the behavior:

Run Matterbridge connected to XMPP
Change the XMPP Nickname
Restart matterbridge
Send a message on another protocol bridged to XMPP.

Expected behavior
The username changes normally and there are no echoed messages. Nothing special.
Screenshots/debug logs

relpda matterbridge[20911]: [0266] DEBUG irc:          == Receiving PRIVMSG: Mikaela test abcdef girc.Event{Source:(*girc.Source)(0xc0009168d0), Tags:girc.Tags(nil), Timestamp:time.Time{wall:0xbf9c885f5d446afe, ext:266744573728, loc:(*time.Location)(0x3082420)}, Command:"PRIVMSG", Params:[]string{"##Mikaela", "test abcdef"}, Sensitive:false, Echo:false}                                                                                huhti 11 11:29:01 relpda matterbridge[20911]: [0266] DEBUG irc:          <= Sending message from ##Mikaela on irc.freenode to gateway
huhti 11 11:29:01 relpda matterbridge[20911]: [0266] DEBUG gateway:      => Sending config.Message{Text:"test abcdef", Channel:"##mikaela", Username:"Mikaela", UserID:"~Mikaela@unaffiliated/
mikaela", Avatar:"", Account:"irc.freenode", Event:"", Protocol:"irc", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f5d47f646, ext:266744805919, loc:(*time.Location)(0x3
082420)}, ID:"", Extra:map[string][]interface {}(nil)} from irc.freenode (##mikaela) to matrix.feneas (#8GgdvoQq:feneas.org)                                                                  huhti 11 11:29:01 relpda matterbridge[20911]: [0266] DEBUG matrix:       => Receiving config.Message{Text:"test abcdef", Channel:"#8GgdvoQq:feneas.org", Username:"[fn] <Mikaela> ", UserID:"~Mikaela@unaffiliated/mikaela", Avatar:"", Account:"irc.freenode", Event:"", Protocol:"irc", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f5d47f646, ext:266744805919, loc:(*time.Location)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0266] DEBUG matrix:       Channel #8GgdvoQq:feneas.org maps to channel id !LSWnevuzcRXZZKhqso:privacytools.io
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG gateway:      mID matrix.feneas: $2GLOVsV0wqZ3Yr0xWZiReAXar4Qq0Pm8oAWDWZdCh0A                                                      huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG gateway:      => Sending config.Message{Text:"test abcdef", Channel:"##mikaela", Username:"Mikaela", UserID:"~Mikaela@unaffiliated/mikaela", Avatar:"", Account:"irc.freenode", Event:"", Protocol:"irc", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f5d47f646, ext:266744805919, loc:(*time.Location)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)} from irc.freenode (##mikaela) to irc.pirateirc (#mikaela)
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG irc:          => Receiving config.Message{Text:"test abcdef", Channel:"#mikaela", Username:"[fn] <Mikaela> ", UserID:"~Mikaela@unaf
filiated/mikaela", Avatar:"", Account:"irc.freenode", Event:"", Protocol:"irc", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f5d47f646, ext:266744805919, loc:(*time.Loca
tion)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG gateway:      => Sending config.Message{Text:"test abcdef", Channel:"##mikaela", Username:"Mikaela", UserID:"~Mikaela@unaffiliated/
mikaela", Avatar:"", Account:"irc.freenode", Event:"", Protocol:"irc", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f5d47f646, ext:266744805919, loc:(*time.Location)(0x3
082420)}, ID:"", Extra:map[string][]interface {}(nil)} from irc.freenode (##mikaela) to xmpp.blesmrt (mikaela)
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG xmpp:         => Receiving config.Message{Text:"test abcdef", Channel:"mikaela", Username:"[fn] <Mikaela> ", UserID:"~Mikaela@unaff
iliated/mikaela", Avatar:"", Account:"irc.freenode", Event:"", Protocol:"irc", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f5d47f646, ext:266744805919, loc:(*time.Locat
ion)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG xmpp:         => Sending message config.Message{Text:"test abcdef", Channel:"mikaela", Username:"[fn] <Mikaela> ", UserID:"~Mikaela
@unaffiliated/mikaela", Avatar:"", Account:"irc.freenode", Event:"", Protocol:"irc", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f5d47f646, ext:266744805919, loc:(*time
.Location)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG gateway:      mID xmpp.blesmrt: bq8qjvf686k4kbilat00
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG irc:          Sending to channel #mikaela
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG xmpp:         == Receiving<EMAIL_ADDRESS>Type:"groupchat", Text:"[fn] <Mikaela> test abcdef"
, Subject:"", Thread:"", Ooburl:"", Oobdesc:"", ID:"bq8qjvf686k4kbilat00", ReplaceID:"", Roster:xmpp.Roster(nil), Other:[]string{""}, OtherElem:[]xmpp.XMLElement{xmpp.XMLElement{XMLName:xml.
Name{Space:"urn:xmpp:sid:0", Local:"stanza-id"}, InnerXML:""}}, Stamp:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG xmpp:         <= Sending message from M on xmpp.blesmrt to gateway
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG xmpp:         <= Message is config.Message{Text:"[fn] <Mikaela> test abcdef", Channel:"mikaela", Username:"M", UserID:"mikaela@conf
erence.blesmrt.net/M", Avatar:"", Account:"xmpp.blesmrt", Event:"", Protocol:"", Gateway:"", ParentID:"", Timestamp:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}, ID:"bq8qjvf686k4kbi
lat00", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG gateway:      => Sending config.Message{Text:"[fn] <Mikaela> test abcdef", Channel:"mikaela", Username:"M", UserID:"mikaela@confere
nce.blesmrt.net/M", Avatar:"", Account:"xmpp.blesmrt", Event:"", Protocol:"xmpp", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f6f93f0af, ext:267051775191, loc:(*time.Lo
cation)(0x3082420)}, ID:"bq8qjvf686k4kbilat00", Extra:map[string][]interface {}(nil)} from xmpp.blesmrt (mikaela) to irc.freenode (##mikaela)
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG irc:          => Receiving config.Message{Text:"[fn] <Mikaela> test abcdef", Channel:"##mikaela", Username:"[X] <M> ", UserID:"mika
<EMAIL_ADDRESS>Avatar:"", Account:"xmpp.blesmrt", Event:"", Protocol:"xmpp", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f6f93f0af, ext:267051775191, lo
c:(*time.Location)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG gateway:      => Sending config.Message{Text:"[fn] <Mikaela> test abcdef", Channel:"mikaela", Username:"M", UserID:"mikaela@confere
nce.blesmrt.net/M", Avatar:"", Account:"xmpp.blesmrt", Event:"", Protocol:"xmpp", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f6f93f0af, ext:267051775191, loc:(*time.Lo
cation)(0x3082420)}, ID:"bq8qjvf686k4kbilat00", Extra:map[string][]interface {}(nil)} from xmpp.blesmrt (mikaela) to irc.pirateirc (#mikaela)
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG irc:          => Receiving config.Message{Text:"[fn] <Mikaela> test abcdef", Channel:"#mikaela", Username:"[X] <M> ", UserID:"mikae
<EMAIL_ADDRESS>Avatar:"", Account:"xmpp.blesmrt", Event:"", Protocol:"xmpp", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f6f93f0af, ext:267051775191, loc
:(*time.Location)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG gateway:      => Sending config.Message{Text:"[fn] <Mikaela> test abcdef", Channel:"mikaela", Username:"M", UserID:"mikaela@confer$
nce.blesmrt.net/M", Avatar:"", Account:"xmpp.blesmrt", Event:"", Protocol:"xmpp", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f6f93f0af, ext:267051775191, loc:(*time.Lo
cation)(0x3082420)}, ID:"bq8qjvf686k4kbilat00", Extra:map[string][]interface {}(nil)} from xmpp.blesmrt (mikaela) to matrix.feneas (#8GgdvoQq:feneas.org)
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG matrix:       => Receiving config.Message{Text:"[fn] <Mikaela> test abcdef", Channel:"#8GgdvoQq:feneas.org", Username:"[X] <M> ", U
<EMAIL_ADDRESS>Avatar:"", Account:"xmpp.blesmrt", Event:"", Protocol:"xmpp", Gateway:"mikaela", ParentID:"", Timestamp:time.Time{wall:0xbf9c885f6f93f0af, ext:26705
1775191, loc:(*time.Location)(0x3082420)}, ID:"", Extra:map[string][]interface {}(nil)}
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG matrix:       Channel #8GgdvoQq:feneas.org maps to channel id !LSWnevuzcRXZZKhqso:privacytools.io
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG irc:          Sending to channel ##mikaela
huhti 11 11:29:01 relpda matterbridge[20911]: [0267] DEBUG matrix:       == Receiving event: &gomatrix.Event{StateKey:(*string)(nil), Sender:"@mikaela-matterbridge:feneas.org", Type:"m.room.
message", Timestamp:1586604541569, ID:"$2GLOVsV0wqZ3Yr0xWZiReAXar4Qq0Pm8oAWDWZdCh0A", RoomID:"!LSWnevuzcRXZZKhqso:privacytools.io", Redacts:"", Unsigned:map[string]interface {}{"age":239, "t
ransaction_id":"go1586604541491644233"}, Content:map[string]interface {}{"body":"[fn] <Mikaela> test abcdef", "format":"org.matrix.custom.html", "formatted_body":"[fn] <Mikaela> test a
bcdef", "msgtype":"m.text"}, PrevContent:map[string]interface {}(nil)}
huhti 11 11:29:02 relpda matterbridge[20911]: [0267] DEBUG gateway:      mID matrix.feneas: $GUvjvgkmur6qZVj3lVsx1Cex9485srpFXHven9PQPdg
huhti 11 11:29:02 relpda matterbridge[20911]: [0267] DEBUG matrix:       == Receiving event: &gomatrix.Event{StateKey:(*string)(nil), Sender:"@mikaela-matterbridge:feneas.org", Type:"m.room.
message", Timestamp:1586604541876, ID:"$GUvjvgkmur6qZVj3lVsx1Cex9485srpFXHven9PQPdg", RoomID:"!LSWnevuzcRXZZKhqso:privacytools.io", Redacts:"", Unsigned:map[string]interface {}{"age":207, "t
ransaction_id":"go1586604541799113874"}, Content:map[string]interface {}{"body":"[X] <M> [fn] <Mikaela> test abcdef", "format":"org.matrix.custom.html", "formatted_body":"[X] <M> [fn]
<Mikaela> test abcdef", "msgtype":"m.text"}, PrevContent:map[string]interface {}(nil)}
huhti 11 11:29:02 relpda matterbridge[20911]: [0267] DEBUG irc:          Sending to channel #mikaela

Environment (please complete the following information):

OS: Linux
Matterbridge version: 1.17.2 d97b077e

Additional context
Please add your configuration file  (be sure to exclude or anonymize private data (tokens/passwords))
# Redacted: passwords, PirateIRC, Matrix, Telegram
[irc.freenode]                                                                                Nick="T4"
NickServNick="T4"
Server="chat.ipv6.freenode.net:6697"                                                                                UseTLS=true
UseSASL=true
SkipTLSVerify=false
Label="fn"
Charset="utf8"

#...

[xmpp.blesmrt]
Server="blesmrt.net:5222"
<EMAIL_ADDRESS>
Muc="conference.blesmrt.net"
#Nick="matterbridge"
Nick=":m:"
Label="X"

[[gateway]]

# ...
name="mikaela"
enable=true

    [[gateway.inout]]
    account="irc.freenode"
    channel="##Mikaela"

      [gateway.inout.options]
      key="redacted"

    [[gateway.inout]]
    account="irc.pirateirc"
    channel="#Mikaela"

      [gateway.inout.options]
      key="redacted"

    [[gateway.inout]]
    account="xmpp.blesmrt"
    channel="mikaela"

    [[gateway.inout]]
    account="matrix.feneas"
    channel="#8GgdvoQq:feneas.org"

The XMPP MUC is private/members-only and everyone can see each others XMPP IDs.
Issue ends when I revert the XMPP Nickname change.

If anyone has documentation links about this XMPP behaviour, feel free to add those so that I don't have to do research to fix it :-)

You are using the label setting wrong I think.
https://github.com/42wim/matterbridge/wiki/Settings#label
Its only and addition to RemoteNickFormat="[{PROTOCOL}] <{NICK}> "
Using it without, is probably causing this mess.

I am using label correctly, but I accidentally didn't paste the [general] section.
[general]
RemoteNickFormat="[{LABEL}] <{NICK}> "
IgnoreFailureOnStart=false
MessageSplit=true
MediaDownloadPath="/var/www/html/matterbridge"
MediaServerDownload="https://ds.relpda.mikaela.info:14402/matterbridge"
MediaDownloadSize=20000000
MediaDownloadBlacklist=[".html$",".htm$"]

Ah OK, I think I understand the problem now. It seems like Matterbridge fails to recognize its own messages as such on the (semi-anonymous) MUC and thus repeats them as if an non-bridge user posted them.
In general there is no way in XMPP MUC that is configured to be semi-anymonous to indentify a user by their Nick as the JID is hidden. So Matterbridge must somehow work around this by comparing messages to its own Nick.
Maybe the old Nick is cached for this purpose somewhere? Or the code simply does not account for Nick changes and keeps selfrecognising with the old nick? But where exactly would it store the old nic during a restart?
It might also be a timestamp issue that Matterbridge is getting confused with messages immediately after the Nick change. But then the problem should go away by itself after a short duration...

Ah OK, I think I understand the problem now. It seems like Matterbridge fails to recognize its own messages as such on the (semi-anonymous) MUC and thus repeats them as if an non-bridge user posted them.

As I said in the original submission, "everyone can see each others XMPP IDs" so the MUC is non-anonymous. However I also forgot to say that the matterbridge is an moderator (while in case of XMPP that isn't useful while in other protocols it would have permission to remove messages) so it would also see everyone's XIDs even if it was semi-anonymous.

Ok true, I over read that. But the core problem still seems to be a self recognition issue.
Can you confirm that this isn't a timing problem and it persists over several minutes?

Timing didn't seem to change this, but I tried to change the nickname again and as I am unable to reproduce this with nick M, I think maybe :M: is not a valid nickname in XMPP while I wasn't able to find clear rules on what would be. I think they would be in https://xmpp.org/extensions/xep-0045.html#bizrules.
Thank you for your help and sorry for opening this and not communicating well (I think the COVID-19 situation is getting the worst of me).