🐛 | Web UI error - shuffles everytime a song is directly selected from playlist

Bug
What I did
I started playing a playlist, where shuffle is activated. Then i opened the playlist in the web player. When direct selecting a song then, not the selected song is starting. It will be played a random song from the playlist.
Further information that might help
Everytime i select a song from playlist (only playlists which have shuffle activated), the playerplay routine (playout_controls.sh) is called, and within that another script is called:
        # Change some settings according to current folder IF the folder.conf exists
        . ${PATHDATA}/inc.settingsFolderSpecific.sh

I don't know why, but inc.settingsFolderSpecific.sh is calling:
        if [ $SHUFFLE == "ON" ]
        then
		    if [ "${DEBUG_inc_settingsFolderSpecific_sh}" == "TRUE" ]; then echo "  # # CHANGING: mpc shuffle" >> $PATHDATA/../logs/debug.log; fi
            **mpc shuffle**
        else

Because of that, the playlist will be shuffled again, BEFORE the selected song is starting. The problem is then, that the selected song now has another playlist position.
I have now commented out mpc shuffle in line 53 of inc.settingsFolderSpecific.sh.
Now the song selection ist working fine.
Can someone explain, whats the reason of shuffeling in inc.settingsFolderSpecific.sh???
Isn't it done by shuffle_play.sh???
If there is no disadvantage of doing that, i could pull request the fix.
Software
Base image and version
Raspbian GNU/Linux 10 (buster)
Branch / Release
master
Hardware
RaspberryPi version
Raspberry Pi 3 Model B Rev 1.2
RFID Reader
13ba:0018 PCPlay Barcode PCP-BCG4209
Soundcard
08bb:2902 Texas Instruments PCM2902 Audio Codec

We fixed many shuffle issues in 2.2.
I’m closing this now, feel free to reopen the issue or open a new issue, if this still persists in 2.2


[core-amqp] Rhea's TypeErrors which are not of TypeError instance should also not be translated

This issue is a copy of Azure/amqp-common-js#59 (comment)
Refer to it for complete context.
** Summary **
https://github.com/Azure/amqp-common-js/issues/49 covers the issue of "Non-amqp and non-system errors should not be retryable by default"
Rhea uses normal Errors (not TypeError) for the case of TypeErrors.
See https://github.com/amqp/rhea/blob/master/lib/errors.js#L27
To handle such cases, we need to update the below if check to include || err.name === "TypeError"
// Built-in errors like TypeError and RangeError should not be retryable as these indicate issues

@chradek In our recent work to re-work MessagingError in core-amqp, does the above get handled?

That should be the case, yes. We only convert AmqpErrors and SystemErrors into MessagingError now. AmqpErrors are errors that have the condition or value property, and checking the rhea code, their TypeErrors have neither. This should now be safe to close.

Great, thanks!


Minor league

"8. Worth mentioning that preprints can be an important "minor league" for journals to scout for papers from and that the more that we can show this happening the more preprints will benefit" - DB

I take this on in the "Preprints from a publisher's perspective" section where I say:

As measured above, preprints are able to garner attention on par with papers published in highly selective microbiology journals. Thus, it is in a journal's best interest to recruit these preprints to their journals. Several journals including PLOS Genetics and Genome Biology have publicly stated that they scout preprints for this purpose


Removed items being passed on POST

Items selected, then unselected are still being passed with the form data:
https://www.screencast.com/t/oVtooqGwl3k

Sorry, I don't have Flash installed here, can you describe the issue in some other way?

Ah, I'm sorry!  Here it is as an MP4:  https://www.screencast.com/t/feWNGeWir

Thanks! I suppose you're using the jQuery build, right? Can you show me the code you use for initializing Selectivity? Am I understanding correctly it is only removing that's causing an issue, right?

Yes, I'm using the jQuery build.  The problem is that when I remove a directory which I had formerly checked, it still submits in the POST data.  Thanks for your help with this!
Here's the code:
$(".selectivity").selectivity( { backspaceHighlightsBeforeDelete: true } );
Then..
													<select id="cb" name="cb[]" multiple class="selectivity">
														<?

													  for ($s = 0; $s < $snum_results; $s++)
													  {
													     echo "<option value=\"$srow[dir]\" ";
													     if (in_array($srow[dir], $dir_arr))
													         echo "selected";
													     echo "> $srow[dir]</option>";
													     $srow = mysqli_fetch_array($sresult);
													  }

														?>
													</select>

Thanks for that code sample! I think what is going wrong is that the
selected options you generate in your markup are still being sent when you
submit the form. I can agree that's a bug that should be handled by
Selectivity, but I have to think how I can easily solve that. Will keep you
posted!
On Tue, 25 Jul 2017 at 02:35 orthodoxws<EMAIL_ADDRESS>wrote:

Yes, I'm using the jQuery build. The problem is that when I remove a
directory which I had formerly checked, it still submits in the POST data.
Thanks for your help with this!
Here's the code:
$(".selectivity").selectivity( { backspaceHighlightsBeforeDelete: true } );
Then..
  											<select id="cb" name="cb[]" multiple class="selectivity">
  												<?

  											  for ($s = 0; $s < $snum_results; $s++)
  											  {
  											     echo "<option value=\"$srow[dir]\" ";
  											     if (in_array($srow[dir], $dir_arr))
  											         echo "selected";
  											     echo "> $srow[dir]</option>";
  											     $srow = mysqli_fetch_array($sresult);
  											  }

  												?>
  											</select>

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/arendjr/selectivity/issues/196#issuecomment-317593909,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgjLgTPpEfaXVZ0WmQaUiU95N4reKNFks5sRThFgaJpZM4NtmmC
.

Thank you very much! I appreciate it!


question about using remote datasource

Hi, there,
I am very interested in this component! I have a question and appreciate your help. I want to use remote datasource (like example 5) through rest call. The return format is json array. However, there is no root object, can I still use such kind of json format? I googled and found a post couple years ago, it said this component can't consume json array without root object. Can anyone confirm that?
By the way, if it can, could anyone provide an example?
Thanks,
Sam

Try not using remote-url-data-field, meaning not setting this field at all.

@samwzm did it work?

I believe it worked.


Discuss graded algebras

Graded algebras and actions of the multiplicative group are discussed.  This also leads to a very natural proof that finitely presented modules are reflexive.  The theory of infinitesimals is not needed.

I read everything and I will commit some typos after merging.


Thread (currently unused) logger argument to KeyValueStore

Motivation

I'm going to follow up with some more changes to the caching code. When I do,
I'll make use of this new logger argument.
I recall wanting this to exist so that I could have written log statements when
implementing #5974, because it's otherwise tricky to debug (the cache version
checking logic depends on being compiled in release mode, which makes for poor
debugger symbols).
Test plan

Existing build

Have you tried compiling with --config=debugsymbols? That doesn't fix everything, but it does give you enough information that optimized code is reasonably debuggable.

I was trying both --config=release-linux and --config=release-debug-linux, neither of which were particularly pleasant to debug.

Have you tried compiling with --config=debugsymbols? That doesn't fix everything, but it does give you enough information that optimized code is reasonably debuggable.

I was trying both --config=release-linux and --config=release-debug-linux, neither of which were particularly pleasant to debug.

--config=debugsymbols can be specified in addition to the above, or with -c opt.


500 Internal server error from revoke endpoint when regenerating tokens from the Store

Description:
This issue occurs when the Store UI has the last generated access token which is already revoked from Revoke API. Since it is already revoked, while regenerating a token from Store UI it fails to revoke the token and generate a new one.
Steps to reproduce:

Generate access token from the store UI.
Revoke the generated access token using the revoke endpoint.
Try to regenerate access tokens from the UI

Affected Product Version:
APIM 2.2<PHONE_NUMBER>869)

This is not reproducible in latest built pack (APIM 4.0.0)


Skbio development environmental installation issues

Summary
While attempting to install scikit-bio for development, I received the following error message. This error occurred with both the editable and non-editable installations. I was following the steps for setting up a development environment for scikit-bio listed here, and the issue occured on step 5.

          ********************************************************************************
          An error happened while installing `scikit-bio` in editable mode.

          The following steps are recommended to help debug this problem:

          - Try to install the project normally, without using the editable mode.
            Does the error still persist?
            (If it does, try fixing the problem before attempting the editable mode).
          - If you are using binary extensions, make sure you have all OS-level
            dependencies installed (e.g. compilers, toolchains, binary libraries, ...).
          - Try the latest version of setuptools (maybe the error was already fixed).
          - If you (or your project dependencies) are using any setuptools extension
            or customization, make sure they support the editable mode.

          After following the steps above, if the problem still persists and
          you think this is related to how setuptools handles editable installations,
          please submit a reproducible example
          (see https://stackoverflow.com/help/minimal-reproducible-example) to:

              https://github.com/pypa/setuptools/issues

          See https://setuptools.pypa.io/en/latest/userguide/development_mode.html for details.
          ********************************************************************************

  !!
    cmd_obj.run()
  error: command '/usr/bin/gcc' failed with exit code 1
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building editable for scikit-bio
Failed to build scikit-bio
ERROR: Could not build wheels for scikit-bio, which is required to install pyproject.toml-based projects

Environment
(skbio-dev) ajcagle@~/scikit-bio$ uname -a
Linux barnacle2 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

(skbio-dev) ajcagle@~/scikit-bio$ python --version
Python 3.11.6

(skbio-dev) ajcagle@~/scikit-bio$ gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

(skbio-dev) ajcagle@~/scikit-bio$ pip --version
pip 23.3.1 from /home/ajcagle/miniconda3/envs/skbio-dev/lib/python3.11/site-packages/pip (python 3.11)

@constellation99 Thanks for reporting! I see the -fopenmp-simd issue, which could be related to certain low-level instructions needed for sequence alignment, which we plan to get rid of in a near future version. By the way, the GCC version (4.8.5) looks bit old. Would it be possible to try scikit-bio on a machine with newer GCC?

@qiyunzhu Thanks for your help! I updated GCC and that seemed to fix the issue. I was able to install skbio successfully.

Thanks, @constellation99! What version were you successful with? It may not represent the lowest supported version but it provides a starting point

Hi, @wasade! I updated GCC to the newest version, which is 13.2.0.


Incorrect output when y flag used

With this input:
regexp = /foo/y
string = foofoo

the regexp.exec(string) value is null, but the value should be the same as when the g flag is used (at least in this case, IIUC; try in the browser’s console).

Thanks for the heads up. The issue is being caused by use of same RegExp object (reference) for all the operations.
Given the same variables, if string.match(regexp) is called before exec, the value is null.
So the fix would be to "clone" the regex object instead of sharing between those calls.
Right now I'm in the process of migrating Regexly to dockerized setup on AWS (v0.2.0 will have server backed permalinks) so this fix will also land in v0.2.0. It's taking longer than usual because of my lack of experience with docker and aws.


docs: add Pull Request Template

Description
As a contributor I want to know in advance, before opening a pull request that commit linting is in effect so that I don't get my PR marked as failing just because I didn't know that the commit message was supposed to be in a certain format.
Create a Pull Request template as explained here:
https://help.github.com/en/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
Acceptance Criteria

Pull Request template explains that commit linting is in effect and provides a link to the original specs => https://www.conventionalcommits.org/en/v1.0.0-beta.4/#specification
PR template has a few words about the git sign off requirement as well (and a link to guide) just in case someone is new to it and potentially gets all confused about why their PR is marked red.
The PR template also must explain that the pull requests should be rebased onto master and squashed into a single commit to help maintainers review it more efficiently and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and why (which is literally the most important feature of a source code version control system such as git).
PR template includes a link to this very well written guide as a "must read" item for beginners: https://github.com/servo/servo/wiki/Beginner's-guide-to-rebasing-and-squashing

FYI: There's a discussion on the Hyperledger Technical Steering Committee's mailing list about contributor on-boarding at the moment, might want to read through that thread and the final outcome of it later as well while working on this task.

I would like to work on this one, thank you


feat: add possibility to set scheduler and syncer interval

Asked on the slack how to configure how often jobs are scheduled, so started looking at it.
It seems that it was already mentioned in the code, so just adding env variable with default values to make it possible to run only once a day for example (In my case we have a lot of repos, running it more often doesn't really bring value but add a lot of computing).
I didn't configure the timeout one, but can add it if you think it's necessary

Long time I didn't write go 😅
Should be all good now !


Code used for Meet 0 - Is operational

Before issuing a pull request, please see the contributing page.

Hi there! I think you meant to push this to your team's repo. This is the public base FTC repo. Just wanted to let you know coming from someone who has made this mistake before.
To delete this PR, just click the close pull request button under this comment. When you create a new PR for your branch/fork, make sure you're pushing to your team's fork, not to this one. Have a good day and good luck with your robot!

Thanks for helping me resolve this!
I realized my mistake shortly after I had made it and didn't entirely
understand how to pull it back. I have since merged this branch into our
team's fork.
Thanks again!
Team 18119
On Mon, Nov 1, 2021 at 2:18 PM Charlie @.***> wrote:

Hi there! I think you meant to push this to your team's repo. This is the
public base FTC repo. Just wanted to let you know coming from someone who
has made this mistake before.
To delete this PR, just click the close pull request button under this
comment. When you create a new PR for your branch/fork, make sure you're
pushing to your team's fork, not to this one. Have a good day and good luck
with your robot!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FIRST-Tech-Challenge/FtcRobotController/pull/220#issuecomment-956611958,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APKC5FCUSQPWKJ6OXMECRIDUJ37Z7ANCNFSM5HBWW77A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Instagram  @.**_operational_18119


improve icons

Hello, original icons seem surprisingly small to me, new icons looks much bigger on my setup (macOS Ventura, kitty, nvim 0.10). I took them from another plugin that I use https://github.com/SmiteshP/nvim-gps/blob/master/lua/nvim-gps/init.lua.

Those icons are deprecated. If you search for the code points on https://www.nerdfonts.com/cheat-sheet you'll see that the ones you're adding are marked as "removed". For more information see https://github.com/ryanoasis/nerd-fonts/issues/1190#issuecomment-1530999114
I'm not sure why the existing icons aren't rendering properly for you; kitty should be the same even across operating systems


Fix IRR priority merging

Merge routes of each AS while merging IR::as_routess.
Binary (script) allow multiple input IRR directories.

This slightly reduces #special cases and increase #ok in stacked area plots of AS/AS Pair.
The reduction comes from the reduction of SpecAsIsOriginButNoRoute and SpecAsSetContainsOriginButNoRoute.

AS
AS Pair
AS special

old

new

Data for above plots:
as_stats4.csv
as_pair_stats4.csv.gz

All these stats follow #101.
Also related, no significant changes:
as_neighbors_vs_rules4.csv


Getting Error : Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://localhost:3000') does not match the recipient window's origin ('http://localhost:3030')

Hi,
I am getting error when trying to submit login
Ubuntu 18.04
Rocket chat server running on http://localhost:3000
This application running on http://localhost:3030
Error in console :
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://localhost:3000') does not match the recipient window's origin ('http://localhost:3030')

Same problem here. Are we misunderstanding something, it is a ssl problem?

Same problem for me, i just need understand whats is Iframe Url and API URL, because i have my application and rocketchat in different domains.

I am have the same problem. Did you find a solution?

You log in to the rocket chat programmatically and get a token
you create on a certain URL (Iframe URL) the output of js code performing authorization in the window where it is displayed and the received token is already present in it
the web interface only works through the receipt of this code, the web interface always requests a token code for this url
you cannot log in directly through the web interface

yes? this is not very nice because the chat is used in different ways at the same time :)

And to be able to get a token from the current session it is necessary that the domains of the site and chat were the same. No other options?

Same problem here, I need acces from https://localhost to development tests. I Try change cors permssion and nothing happens..

Any news about this? I facing the same issues!

Honestly, I don't get how I should identify the user when the iframe calls sso route. I mean it ´is an iframe - I cannot access any cookie which I set before on the parent host.

Honestly, I don't get how I should identify the user when the iframe calls sso route. I mean it ´is an iframe - I cannot access any cookie which I set before on the parent host.

I fixed the issue by navigating to "General" tab under the "Administration" settings and unchecked "Restrict access inside any Iframe"
        <script>
            console.log('initializing the chat box');
            let host = 'https://rocket.rdicorp.com';
            fetch(host + '/api/v1/login', {
                method: 'POST',
                headers: {
                    'Content-Type': 'application/x-www-form-urlencoded;charset=UTF-8'
                },
                body: 'user=' + encodeURIComponent('username_goes_here') + '&password=' + encodeURIComponent('password_goes_here')
            }).then((response) => response.json())
              .then((respose) => {
                  console.log('chat logged in', respose, respose.data.authToken);
                  let container = document.getElementById('chat-box-holder');

                  if (respose.status == 'success') {

                      var frame = document.createElement('iframe');
                      frame.src = host +'/channel/general/?layout=embedded';
                      frame.title = 'Chat box';
                      frame.scrolling = 'no';
                      frame.frameBorder = '0';

                      container.appendChild(frame);

                      frame.contentWindow.postMessage({
                          event: 'login-with-token',
                          loginToken: respose.data.authToken
                      }, host);

                  }
               });
        </script>


Incorporate ABC metrics

Description
Incorporate ABC metrics
Fixes #120
Type of change

New feature (non-breaking change which adds functionality)
Documentation update

Testing steps
Please run ./abcgo.sh on command line

Codecov Report

Merging #121 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #121   +/-   ##
=======================================
  Coverage   70.14%   70.14%
=======================================
  Files          12       12
  Lines         710      710
=======================================
  Hits          498      498
  Misses        208      208
  Partials        4        4

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 3a0e1a3...3201b81. Read the comment docs.


Flutter Web Release Version Doesnt show asset image in tooltip

Using flutter web release. The tooltip does not show my asset image. Using debug it shows fine. I tried using edge and chrome and both do not work on release.
This is debug Mode. Works fine:

This is all i get with the release version.

Widget ruleInfoButton(){   SuperTooltipController ruleToolTipController = SuperTooltipController();   return OnHoverLarge(builder: (isHovered)   {     return Tooltip(message:'Show how each rule is calculated',child:SuperTooltip(popupDirection: TooltipDirection.down,barrierColor: Colors.transparent,controller:ruleToolTipController,content: Image.asset('assets/ruleTable.jpg'),         child:IconButton(color:isHovered ? Colors.blueAccent:null,icon:const Icon(Icons.info_outline), onPressed: () {           ruleToolTipController.showTooltip();         },)));   }); }

Is this package dead? no support?

@Jesse-Abruzzo
Thanks for submitting the issue.
I will look into it

any update on this? still doesnt work in flutter web release mode

Anything????

Anything????

So sorry, I have been so busy lately,
If you provide a PR on this. That will be great. I'll just preview then merge
Thanks for understanding

No worries. Not sure what the issue is. Im migrating to a different package.


Banks fail to load

Hi, i tried this recently, but i ran into an issue, fmod dosent load the banks, if i have the fmod loader in a seperate room, it shows the errors, else it fails to compile, when i load in an event, this happens

Hello! May I ask for more information? Code snippets, screenshots, you name it.

i copied them over from your example, and modified it to work for my stuff

sounds/Desktop/Master.strings.bank :  1
FMOD error!(% d) % s
An invalid parameter was passed to this function.
sounds/Desktop/Master.bank :  3
FMOD error!(% d) % s
An invalid parameter was passed to this function.
sounds/Desktop/music.bank :  5
FMOD error!(% d) % s
An invalid parameter was passed to this function.
sounds/Desktop/sfx.bank :  7
FMOD error!(% d) % s
An invalid parameter was passed to this function.
code is mostly the same from the example

and this is if i load a sound from the banks
FMOD error!(% d) % s
An invalid object handle was used.
FMOD error!(% d) % s
An invalid object handle was used.

oh, it suddenly fixed itself

Ah well that's good then. Though would've liked to know exactly what was different.

I tried it on a different project again, and it didnt work again, but now i cant get it to fix itself. what should i try?

May I suggest you sending your project or like showing me your code, I would like to analyze it further.

https://www.mediafire.com/file/ubbq6ob4k0s2pts/PVZ_8_bit.zip/file

here

I figured out the solution. you might want to put it in the wiki or something:
Make sure that the FMOD object is persistent, else it will not work.

Ah ok, in that case, I will close this issue as resolved and will add to the wiki.


Changing subscription name for matching CI naming convention

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
/kind cleanup
/kind failing-test
/kind enhancement
/kind documentation
/kind code-refactoring

What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
Test acceptance criteria:

[ ] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:

/test v4.10-kuttl-parallel

/test v4.11-kuttl-sequential

/test v4.11-kuttl-sequential

/test v4.11-kuttl-sequential


Ban Appeal

In all seriousness, we do agree for no "hacks" upon playing, and as such the only hacks/cheats I used were passive and minor hacks such as auto-sprint and show-healthbar. I did implement some mods (like morph, where they can't be utilised on servers).
I cannot prove that I used what I say I used or anything (since any screenshot I take would look like I altered them), and my isolation in the server doesn't help much. Although, during my time in the server, I have not once tried to abuse what staff permit nor what I have (such as enabling op hacks).

 You installed ForgeWurst which has some of the abilities you described as well as many others. Whether some of the mods abilities are allowed and some aren’t is regardless.
This is my one and only warning for you. I’m changing your permanent ban to be one more day of a tempban, under the implication that you remove ForgeWurst and never use it again on our server. If you’re caught with any hack mods installed, used or not, it will be a permanent ban with no chance of appeal.


Support for GNAT Community 2021

The generated code should be compatible with GNAT Community 2021.

The switch to GNAT Community 2021 is blocked by Componolit/ada-runtime#80.


[Scope Request] codeunit 9178 "Application Area Mgmt." - remove OnPrem Scope, function GetApplicationAreas

Please remove the OnPrem Scope from the function GetApplicationAreas in the codeunit 9178 "Application Area Mgmt.". I do not see a reason why this function would be limited to OnPrem development.

@miljance you can use the procedure `GetApplicationAreaSetup`` in codeunit 9179 "Application Area Mgmt. Facade" instead.
I think microsoft to update the codeunit 9178 "Application Area Mgmt." from Scope OnPrem to Access Scope Internal.
I would be better to mark this procedures as obsolete with a obosletion comment that redirct to the facade codeunit and then clean up this codeunit.
Addtioanlly they would have to move the event from the Impelmentation codeunit ( codeunit 9178 "Application Area Mgmt.") to the "Public Interface Codeunit"(codeunit 9179 "Application Area Mgmt. Facade)

That should do the trick. Thanks! Closing this request.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11415.


Added Hound CI config File

Fixes: #174
Changes:

Added config file for integartion of HoundCI

Benefits:
Hound reviews your code when a pull request is opened or updated. If Hound finds any style violations in the modified code it will comment on the appropriate line. It will be easier for the beginners to fix the issue and makes the life easier for reviewer and if we add flake8 in travis build than PR will fail due to violations in the PR so beginners will find difficult to debug and fix the issue

@AnshulMalik Review again 😄

LGTM  Travis was failing when this PR was submitted but it had nothing to do with the changes in this PR.


Removed unsafe record selector from export list

The comment explains the motivation for this change

On second thought i'll just put the comment here instead:

segString is exported instead of _segString
To avoid usage like this that break the guarantee that PathSegment and mkPathSegment provide:
>>> (\c -> c {_segString = "Lots'O'SlashesOhNoBroken!!//////////"}) <$> mkPathSegment "noSlashesOrControlCharsIsSafe"
Just (PathSegment {_segString = "Lots'O'SlashesOhNoBroken!!//////////"})

This is bad behaviour, instead it should be an error, mkPathSegment should be the only way to get a String into a PathSegment (or maybe a Prism).
Exporting a function instead seems like boilerplate to most, but its cases like these that demonstrate the subtle difference that make it worthwhile, we hide the record selector and instead export segString and we get the desired error:
>>> (\c -> c {segString = "Lots'O'SlashesOhNoBroken!!//////////"}) <$> mkPathSegment "noSlashesOrControlCharsIsSafe"

<interactive>:4:11:
    ‘segString’ is not a record selector
     In the expression:
      c {segString = "Lots'O'SlashesOhNoBroken!!//////////"}
    In the first argument of ‘(<$>)’, namely
      ‘(\ c -> c {segString = "Lots'O'SlashesOhNoBroken!!//////////"})’
    In the expression:
      (\ c -> c {segString = "Lots'O'SlashesOhNoBroken!!//////////"})
      <$> mkPathSegment "noSlashesOrControlCharsIsSafe"


Add possibility to configure Jetty's minRequestDataRate

Resolves #2181.

Coverage increased (+0.01%) to 85.484% when pulling eec0a47e03058581e2d6f8799326f9ceda825788 on patrox:issue_2181_jetty_minRequestDataRate into d3a7b57dfd13d7bfa976c751c6483b75c38eee64 on dropwizard:master.

Coverage increased (+0.01%) to 85.484% when pulling f7f98720ed4318ba5410eef5fb396d87c5c147db on patrox:issue_2181_jetty_minRequestDataRate into d3a7b57dfd13d7bfa976c751c6483b75c38eee64 on dropwizard:master.

Coverage increased (+0.01%) to 85.484% when pulling f7f98720ed4318ba5410eef5fb396d87c5c147db on patrox:issue_2181_jetty_minRequestDataRate into d3a7b57dfd13d7bfa976c751c6483b75c38eee64 on dropwizard:master.


chore: rename repo to trustbloc-did-method

Signed-off-by: Troy Ronda<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   90.46%   90.46%
=======================================
  Files          12       12
  Lines         304      304
=======================================
  Hits          275      275
  Misses         16       16
  Partials       13       13

Impacted Files
Coverage Δ

...dri/trustbloc/discovery/staticdiscovery/service.go
90.9% <ø> (ø)
:arrow_up:

cmd/did-method-rest/startcmd/start.go
93.33% <ø> (ø)
:arrow_up:

cmd/did-method-rest/main.go
77.77% <ø> (ø)
:arrow_up:

pkg/did/client.go
89.33% <ø> (ø)
:arrow_up:

pkg/restapi/didmethod/operation/operations.go
75% <ø> (ø)
:arrow_up:

pkg/restapi/didmethod/controller.go
100% <ø> (ø)
:arrow_up:

pkg/vdri/trustbloc/vdri.go
94.44% <ø> (ø)
:arrow_up:

...dri/trustbloc/selection/staticselection/service.go
100% <ø> (ø)
: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 0a55a6a...7c0ce0d. Read the comment docs.


eps & pdf export not working on Mac 10.10.2 and Matlab R2014b

when I try to export a figure to eps, ps or pdf I get the following error:
>> plot([0 100]*1e10,[0 100]*1e10,'-b')
>> export_fig test.eps
Error: /undefined in Infinity
Operand stack:
   --nostringval--   560   0   0
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1951   1   3   %oparray_pop   1950   1   3   %oparray_pop   --nostringval--   1934   1   3   %oparray_pop   1820   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1179/1684(ro)(G)--   --dict:0/20(G)--   --dict:121/200(L)--
Current allocation mode is local
Last OS error: Invalid argument
Current file position is 9496
GPL Ghostscript 9.15: Unrecoverable error, exit code 1
Ghostscript error: perhaps /private/tmp/tp0576f1d3_2479_440d_ac55_425c20a76e9c.pdf is open by some other application
export_fig error. Please ensure:
  that you are using the latest version of export_fig
  and that you have Ghostscript installed
  and that you have pdftops installed
  and that you do not have multiple versions of export_fig installed by mistake
  and that you did not made a mistake in the expected input arguments

If the problem persists, then please report a new issue.

Error using eps2pdf (line 149)
Error: /undefined in Infinity
Operand stack:
   --nostringval--   560   0   0
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1
   %stopped_push   1951   1   3   %oparray_pop   1950   1   3   %oparray_pop   --nostringval--   1934   1   3   %oparray_pop   1820   1   3   %oparray_pop   --nostringval--
   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1188/1684(ro)(G)--   --dict:0/20(G)--   --dict:121/200(L)--
Current allocation mode is local
Last OS error: Invalid argument
Current file position is 9496
GPL Ghostscript 9.15: Unrecoverable error, exit code 1

Error in export_fig (line 512)
                eps2pdf(tmp_nam, pdf_nam, 1, options.append, options.colourspace==2, options.quality, options.gs_options);

and FYI I use ghostscript 9.15 built from sources and pulled the current version of export_fig from the repo...

ok, it seems that it was caused by the 'Units' properties of the figure. If I set the units to 'pixels' everything works like a charm!

@leshaker - I could not recreate the error on my Windows machine, but I trust your solution and it is pretty safe in any case to temporarily set the figure units to 'pixels' for the duration of the export (reverting back to the original units when the export is done), so I have just uploaded this fix.


Az login issue

Error:1
Done setting cloud: "azurecloud"
Note: Azure/login action also supports OIDC login mechanism. Refer [https://github.com/azure/login#configure-a-service-principal-with-a-federated-credential-to-use-oidc-based-authentication] for more details.
Attempting Azure CLI login by using service principal with secret...
Error: The subscription of '0b6fcf9a-a18f-47b8-b229-01cde8a03feb' doesn't exist in cloud 'AzureCloud'.
Error: Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to [https://github.com/Azure/login#readme] for more information.
Error:2
Attempting Azure CLI login by using service principal with secret...
Error: The subscription of '0b6fcf9a-a18f-47b8-b229-01cde8a03feb' doesn't exist in cloud 'AzureCloud'.
Error: Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.

Double check if the 'auth-type' is correct. Refer to [https://github.com/Azure/login#readme](https://apc01.safelinks.protection.outlook.com/for more information.
Code: ResourceGroupNotFound
Message: Resource group 'ipssq00rgpprmry' could not be found.

We are getting above 3 error in the workflow,once we re-trigger the same job it's getting successful run without changing anything.

@sekharreddy2772 - is this error coming from the az-login step of the workflow or the sql-action step?

Closing this issue until @sekharreddy2772 can clarify which step is throwing the error


Thanks for the review @MarcoFalke. I've addressed your review comments and rebased on master.

Thanks for the review @MarcoFalke. I've addressed your review comments and rebased on master.
Originally posted by @jnewbery in https://github.com/bitcoin/bitcoin/pull/21160#issuecomment-926529232

Thank u


Would be great if logging.INFO should show all LLM api calls, including ones made for validation

Is your feature request related to a problem? Please describe.
Would be great if logging.INFO should show all LLM api calls, including ones made for validation.  There is too much info in debug mode (like tcp calls), and info does not show llm_validator calls
Describe the solution you'd like
llm_validator calls show in logging = INFO
Describe alternatives you've considered
using debug logging (but its hard with too much info
I think INFO can have more information about request/response.  DEBUG is a bit too low level and hard to process due to tcp call details.

I second this. Visibility into the function/tool message (you normally already have access to the system and user messages) , without the noise of debug level logging, would be very helpful.

happy to take PR for this!


8 scan lists

Set scan lists from menu.
Change list to scan from menu or using scan key during scan.
If current scanlist is empty scan will not start.
Scan all channels ignoring scanlist available using scan key during scan.

Todo

[ ] Move indicator that hide the bell
[ ] Jump over the empty lists
[ ] Scan all in scanlist menu selection
[ ] Update Readme
[ ] Quick actions to directly scan a predefined list instead of the selected one


Use [[page title]] instead of page title?

I'm interested in migrating from Notion to Logseq. For that I don't just want to have each page as a separate Markdown document , but also to use the following method of linking to pages.
Instead of  page title, each page should be listed as [[page title]].
This way users of Obsidian or Logseq (as well as a dozen other apps that now use this standard), will be able to import the MD files and jump from document to document rather than linking back to Notion.

I don't see [[page title]] being rendered by markdown editors. May I know what it signifies?

The concept is simple. If i have a page in the same folder with the title "dogs" and I write [[dogs]] in any markdown document in that same folder, it will automatically link to that page.
This was developed by a new category of app called "tools-for-thought" which can be thought of as personal wikis. Roam was the first widely adopted one, then Obsidian and Logseq followed, now there are literally dozens of such apps out, and other markdown rendering apps such as Drafts (on mac and iOS) have also adopted the standard. Not all of them use Markdown files, but the two most popular ones (Obsidian and Logseq) do.

Actually, talking about Obsidian gave me an idea. I see that there is already a Notion import tool for that. It might work better for me...

Hi! Thank you for raising this issue.
We're currently working on notion-to-md v4 which includes significant architectural improvements so it's exactly designed for such use cases.
I'd love your insights on this. Please checkout the GitHub discussion #112   to discuss how we can best solve your use case? Your feedback would be really valuable in shaping v4's development.


fixup kustomize after merge of cosa-upload tasks

I missed this during review of #15
cc @aleskandro

/lgtm


Add PWA

Does this PR cause start screen changes?: No, not visually
Checklist

[ ] Documentation updated

Summary
Adds a message to error pages linking to Google so that users can bypass the screen if its not working.
Adds a PWA to allow offline or error access.

This has got too far out of sync. Will start up again when I get chance.


when can you release 3DMM fitting algorithm?

Unfortunately, for now, we cannot release them before getting our company’s official permission. Alternatively, we provide an open-source solution based on DECA.


Improved typing of provider fields

What kind of change does this PR introduce?
This changes the type of the provider fields on UserAppMetadata and UserIdentity from string to Provider, which is the more accurate type.
What is the current behavior?
Right now, the field is typed as string, which tells typescript it can be any string, when in fact it can only ever be one of the values of Provider.
this is my first PR here, let me know of there's something I missed!

Hey, actually it can only be a string. This is the information that is coming out from the GoTrue server. If you use an older version of gotrue-js, but a newer version of gotrue (the server) you will not be able to recognize any new providers supported by the server. This is why it has to be a string.
Furthermore, SSO providers are not enumerable, i.e. the provider name is sso:<uuid> as they're registered on the server. In that case you also can't use a const-style type.
I'll close this PR, though absolutely feel free to suggest changes whenever you see anything that can be improved. If you want to change something but are not sure, open an issue where you can discuss approaches with the team and community before spending time on it.

Alright, no problem! it only took me 2 minutes so I didn't waste too much time :sweat_smile:


Support for MRI 2.4

I found dry-initializer has a failing spec on MRI 2.4, I'm going to find out why...

Ok, so
MRI 2.3:
$ ruby -e "instance_eval(&lambda { |_| return })"

MRI 2.4:
$ ruby -e "instance_eval(&lambda { |_| return })"
-e:1:in `block in <main>': unexpected return (LocalJumpError)
	from -e:1:in `instance_eval'
	from -e:1:in `<main>'

I'll file a ticket to bugs.ruby-lang.org, but we can easily fix it for now, I'll commit a workaround

https://bugs.ruby-lang.org/issues/13090

I guess this can be merged/released?

I think so )))
@flash-gordon thank you!
Sorry man, I'm too busy now with a commertial project, couldn't answer earlier

ah, sure, no problem


The kconfig-hardened-check tool and Linux Kernel Defence Map

Hello everyone!
Hope that creating this issue is a proper way of contributing to your working group.
Maybe my kconfig-hardened-check tool is in scope of your discussions.
Short intro:
There are plenty of Linux kernel hardening config options. A lot of them are not enabled by the major distributions.
kconfig-hardened-check helps to check the Linux kernel Kconfig option list against the hardening preferences,
which are based on the:

KSPP recommended settings,
CLIP OS kernel configuration,
last public grsecurity patch (options which they disable),
SECURITY_LOCKDOWN_LSM patchset,
direct feedback from Linux kernel maintainers.

As I know, several Linux distributions already use kconfig-hardened-check.
I also created the Linux Kernel Defence Map that is a graphical representation of the relationships between these hardening features and the corresponding vulnerability classes or exploitation techniques.
I gave a talk at the Linux Plumbers Conference 2020 about these projects.
See the video and slides if you are interested.
Please let me know if I can contribute by creating a pull request or doing something else.
Best regards,
Alexander

Hey Alexander.  Sorry this has laid dormant.  Thank you for sharing this.  It's exactly the kind of thing we're looking for.  How quickly are you keeping the tool up to date with new kernel releases?  How far back in kernel revisions do you support?

Hi @ware
In July I will start working on kconfig-hardened-check tool on regular basis. That will include supporting new kernel releases and developing new features.
This tool can be used for kernel configs of any kernel version.

Hello everyone! Hello @ware!
The kconfig-hardened-check tool and Linux Kernel Defence Map get regular updates, new features, and releases.
I believe these projects are relevant for the OpenSSF Security Tooling working group.
Thanks!

Hello!
As I mentioned, kconfig-hardened-check is a tool for checking the security hardening options of the Linux kernel.
In addition to Kconfig options, it now can check kernel cmdline arguments and sysctl parameters.
So this project got a new name that describes it better: kernel-hardening-checker.


EDUPUB's new dc:type is "education"

EDUPUB, now known as EPUB for Education, was previously identified with a dc:type of "edupub", it has been now renamed to "education".
The EDUPUB validation profile should be triggered for both values, and an INFO message should be triggered when "edupub" is found.

See also idpf/education#3

Done in #788

Removing from 4.1.0 milestone because PR #788 was removed from milestone. Feel free to work on it and assign it back to 4.1.0 as long as we're still working on it.


docs: fixed padding after code blocks

Signed-off-by: Dmitry Kharitonov<EMAIL_ADDRESS>
This change is

test-docs-please

Coverage decreased (-0.002%) to 44.602% when pulling e67091bcb2ce8de7c53732bb3cdf8e8049601f4f on geakstr:pr/fix-padding-after-code-blocks into c58d749816d943c4f9426f67738013f4e8778463 on cilium:master.


types: fix type of Cloudworker.dispatch

Dispatch returns a Promise that resolves to Response

Thank you!


Comments density

Rule Suggestion
Is your rule for a general problem or is it specific to your development style?
a General problem
What does your suggested rule do?
https://docs.sonarqube.org/display/SONAR/Metric+Definitions
comment_lines_density
Density of comment lines = Comment lines / (Lines of code + Comment lines) * 100
With such a formula:
50% means that the number of lines of code equals the number of comment lines
100% means that the file only contains comment lines

List several examples where your rule could be used
Determine if there are enough comments in the source code
Additional context

@TristanFAURE this rule does not seem useful to me. why would i want to enforce a certain ratio of comments to code? seems like the wrong metric.

Hello @giladgray, I totally understand your comment and I was ready for it.
In some businesses like aeronautic, space, automotive... it exists standard that force us to give this kind of metric (like my other PR check function size). If we can't measure it we will not be able to use typescript for the development of some software :( (or we will have to find another linter)
I don't ask to make this parameter enable by default but it would be very nice to review this PR to let people who need it use it :(

@TristanFAURE ah in that case this rule does not belong in the main TSLint repo, as it is specific to certain use cases. it belongs in your own codebase and can be enabled using the ruleDirectories option. you can develop it in a separate package and even publish it to NPM, but it does not belong here.

I understand your point of view but it is a little bit a pity because we are a lot working in this area and we all need it. But it is okay I can host it internally


Make sure a CORS preflight request doesn't go to a wrong service

Motivation:
Currently, with the following code:
Server.builder()
      .route().get("/foo").build(someService);

a CORS preflight request (OPTIONS method) will go to someService,
which is not an expected behavior.
It is mainly because of the hack we added some time ago for adding
support for @CorsDecorator:

DefaultRoute - https://github.com/line/armeria/blob/armeria-0.95.0/core/src/main/java/com/linecorp/armeria/server/DefaultRoute.java#L88-L99
AnnotatedHttpServiceFactory - https://github.com/line/armeria/blob/armeria-0.95.0/core/src/main/java/com/linecorp/armeria/internal/annotation/AnnotatedHttpServiceFactory.java#L368-L378

Modifications:

Add RoutingResultType to represent three routing state:

MATCHED
NOT_MATCHED
CORS_PREFLIGHT (not matched, but need to handle a CORS preflight request)

Modify the routing logic so that:

If the routing result type is CORS_PREFLIGHT and the service is
decorated with a CorsService, the request goes to the service.
If the routing result type is CORS_PREFLIGHT and the service is
NOT decorated with a CorsService, the request goes to the fallback
service.

Add a test case for what's explained in the 'motivation' section.

Result:

Slightly cleaner hack
A CORS preflight request does not go to a wrong service anymore.

@hyangtack @anuraaga You might be interested in this change.

Added the 'breaking-change' label because it adds some behavioral changes in the routing API. I think it will not affect most users, though.


Parameterise bird.conf

To facilitate using an inventory group to define neighbors, template elements of the config:

Hard-code logging, router ID, and maybe protocol device
Allow customization of protocol direct and protocol kernel
Nested dictionaries for protocol bgp, bfd, osfp, static, etc
Use bird define variables for own IP/AS?

closed by 2e736e8d988c81d585fc069b090e24dae0d349ae


Bash shell script issue with "%" sign

I'm using VSCODE for my ssh sessions. Since the July 2022 update, whenever I try to execute a command that has the % sign I get one of those two print errors:
bash: printf: '\': invalid format character
bash: printf: 'Z': invalid format character
I tried a different ssh client and the issue doesn't appear, so it's something with this update. Is anyone aware of a solution?

Did you notice https://code.visualstudio.com/updates/v1_70#_shell-integration-enabled-by-default? Please try disabling shell integration to see if this change to the default has triggered your issue.

Yes, that did the trick. Thanks!

It's to do with 633 E:
builtin printf '\033]633;E;echo '\''%'\''\007'
bash: printf: `\': invalid format character

Same problem in zsh:

@Tyriar, there's actually a simpler way to fix this issue than escaping the % char ending up in the printf format string, by passing it as a separate parameter to printf.
I have left a comment in the linked pr as well: https://github.com/microsoft/vscode/pull/157352/files#r939627065

We don't have to escape if $__vsc_current_command is passed as a separate parameter to printf, avoiding the need for the sub-shell and sed, like this:

builtin printf "\033]633;E;%s\007" "$__vsc_current_command"

@ryenus that's much nicer if it works 👍

@ryenus that's much nicer if it works 👍

It should, as the same approach is already used in __vsc_update_cwd(), and __vsc_command_complete().
BTW, thank you for being open and kind 👍


Hello, is there a specific tutorial for deployment?

dotnet publish -c Release

Or download the prebuilt assets from releases.
Download prebuilt OpenH264 build https://github.com/cisco/openh264/releases/tag/v2.2.0
Prepare your GBA bios and game rom
Put everything under the same directory.
Launch the server
dotnet OptimeGBA-Web.dll --Optime:BiosHome=<dir-with-bios> --Optime:Rom=<path-to-rom>  [--VideoEncoding="<encoding>"]

I ran into this problem during deployment

This looks like a dynamic library issue from OpenH264. Did you downloaded v2.2.0 with correct architecture (x64, x86 or ARM64)?

I replaced it with openh264-2.2.0-win64.dll and still get the error.


Testing Foreign Key Violation causes fixture unloading in dead transaction

What steps will reproduce the problem?
Try to test ActiveRecord::delete() on unit with foreign key, that restrict it's deletion (ON DELETE RESTRICT) and expect \yii\db\IntegrityException with code 23503 (Foreign key violation)
What is the expected result?
Tast passes
What do you get instead?
[yii\db\Exception]
SQLSTATE[25P02]: In failed sql transaction: 7 ОШИБКА:  текущая транзакция прервана, команды до конца блока транзакции игнорируются
Additional info
Seems like \yii\db\Transaction expects to be informed about transaction death by \yii\db\IntegrityException. But PHPUnit catch it for test and didn't rethrow. So Yii tries to unload fixture in dead transaction.

Q
A

Yii version
2.0.12

PHP version
5.6

Operating system
Linux Ubuntu 16.04

Database type
Postgresql

Test method example:
`/**

@test
@expectedException \yii\db\IntegrityException
*/
public function removingUnitWithFKRestrictionThrowsException()
{
$zip = ActiveRecordUnit::findOne(1);
$zip->remove();
}`


bug: Google Home fails to reconnect after service restart

Bridge and devices become and stay offline after service restart. Hint regarding what to look for would be great - can try to lost debug logs, but didn't see anything on first glance.
HomeKit stays connected to the second bridge though.

Does it happen everytime you restart the app? But only for Google Home and not Apple Home?

Happened both times my HA server restarted after setting things up. HomeKit comes back up fine, Google home not so.
Will try with a small test server to see, setting up room associations after recreating a bridge for Google Home gets old real quick :|

Does it happen when you restart the addon, or only when restarting the whole home assistant system?

I was apparently seeing two different issues and drawing a rushed conclusion:

Crash (the 1000 pending lock queue issue) where restart of the service didn't help. Unfortunately the volatile journal was lost to the next one. My suspicion was that something had gone bad in the persisted bridge state, but I cannot reproduce.

Power-loss where matter-hub seemed to start too early, failed but stayed alive so no service restart (and I as I had to leave thought it was a repeat of the above):

Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.659Z ] [ DEBUG ] [ Matter / UdpChannelNode                            ]: Socket created and bound remoteAddress: undefined:5353 localAddress: <IP_ADDRESS>:5353
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.684Z ] [ ERROR ] [ Matter / MdnsService                               ]: No IPv4 addresses on interface: eth0
Nov 30 15:40:17 raspberrypi npx[1128]:   at NodeJsUdpChannel.create (file:///opt/matterhub/node_modules/@matter/nodejs/dist/esm/net/NodeJsUdpChannel.js:72:17)
Nov 30 15:40:17 raspberrypi npx[1128]:   at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Nov 30 15:40:17 raspberrypi npx[1128]:   at async UdpMulticastServer.create (file:///opt/matterhub/node_modules/@matter/general/dist/esm/net/UdpMulticastServer.js:32:50)
Nov 30 15:40:17 raspberrypi npx[1128]:   at async MdnsServer.create (file:///opt/matterhub/node_modules/@matter/protocol/dist/esm/mdns/MdnsServer.js:32:7)
Nov 30 15:40:17 raspberrypi npx[1128]:   at async MdnsBroadcaster.create (file:///opt/matterhub/node_modules/@matter/protocol/dist/esm/mdns/MdnsBroadcaster.js:62:7)
Nov 30 15:40:17 raspberrypi npx[1128]:   at async file:///opt/matterhub/node_modules/@matter/protocol/dist/esm/mdns/MdnsService.js:35:27
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.852Z ] [ INFO  ] [ Matter / ServerNodeStore                           ]: Opened 08bae7333ea14453b0dcb15f2cbebf41 storage at /home/homeassistant/.home-assistant-matter-hub/08bae7333ea14453b0dcb15f2cbebf41
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.869Z ] [ INFO  ] [ Matter / SessionManager                            ]: restoring resumption record for node<PHONE_NUMBER> and peer node<PHONE_NUMBER> for fabric index 1
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.872Z ] [ INFO  ] [ Matter / SessionManager                            ]: restoring resumption record for node 499721741 and peer node 499721741 for fabric index 2
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.873Z ] [ INFO  ] [ Matter / SessionManager                            ]: restoring resumption record for node<PHONE_NUMBER> and peer node<PHONE_NUMBER> for fabric index 1
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.875Z ] [ INFO  ] [ Matter / SessionManager                            ]: restoring resumption record for node 94168445 and peer node 94168445 for fabric index 1
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.934Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.basicInformation.state
Nov 30 15:40:17 raspberrypi npx[1128]: [ 2024-11-30T14:40:17.995Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.accessControl.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.018Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.groupKeyManagement.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.048Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.generalCommissioning.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.067Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.administratorCommissioning.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.093Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.operationalCredentials.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.136Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.generalDiagnostics.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.197Z ] [ DEBUG ] [ Matter / EventHandler                              ]: Set/Restore last event number: 40
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.199Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 locked 08bae7333ea14453b0dcb15f2cbebf41.descriptor.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.223Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41>#1 committed and unlocked 8 resources
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.238Z ] [ INFO  ] [ Matter / Endpoint                                  ]: 08bae7333ea14453b0dcb15f2cbebf41 ready endpoint#: 0 type: RootNode (0x16) behaviors: 💤parts ✓index ✓basicInformation ✓accessControl ✓groupKeyManagement ✓generalCommissioning ✓administratorCommissioning ✓operationalCredentials ✓generalDiagnostics ✓c>
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.243Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction reactor<08bae7333ea14453b0dcb15f2cbebf41.commissioning.#initializeNode>#5 locked 08bae7333ea14453b0dcb15f2cbebf41.commissioning.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.246Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction reactor<08bae7333ea14453b0dcb15f2cbebf41.commissioning.#initializeNode>#5 committed and unlocked 1 resource
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.261Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator>#9 locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.descriptor.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.264Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction reactor<08bae7333ea14453b0dcb15f2cbebf41.descriptor.#updatePartsList>#a locked 08bae7333ea14453b0dcb15f2cbebf41.descriptor.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.267Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction reactor<08bae7333ea14453b0dcb15f2cbebf41.descriptor.#updatePartsList>#a committed and unlocked 1 resource
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.269Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator>#9 committed and unlocked 1 resource
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.274Z ] [ INFO  ] [ Matter / Endpoint                                  ]: 08bae7333ea14453b0dcb15f2cbebf41.aggregator ready endpoint#: 1 type: Aggregator (0xe) behaviors: 💤parts ✓index ✓descriptor
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.494Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_denon_avr_x1700h>#1c locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_denon_avr_x1700h.identify.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.514Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_living_room>#21 locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_living_room.identify.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.527Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights>#26 locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights.identify.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.545Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights>#26 locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights.groups.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.555Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights>#2b locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights.identify.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.561Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights>#2b locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights.groups.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.573Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_denon_avr_x1700h>#1c locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_denon_avr_x1700h.descriptor.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.576Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_living_room>#21 locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.media_player_living_room.descriptor.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.579Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights>#26 locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights.onOff.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.581Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights>#26 locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_office_lights.descriptor.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.583Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights>#2b locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights.onOff.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.585Z ] [ DEBUG ] [ Matter / Transaction                               ]: Transaction initialize<08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights>#2b locked 08bae7333ea14453b0dcb15f2cbebf41.aggregator.light_bedroom_lights.descriptor.state
Nov 30 15:40:18 raspberrypi npx[1128]: [ 2024-11-30T14:40:18.587Z ] [ ERROR ] [ Bridge / 08bae7333ea14453b0dcb15f2cbebf41          ]: Failed to start bridge due to error: TypeError: Cannot read properties of undefined (reading 'attributes')
Nov 30 15:40:18 raspberrypi npx[1128]:     at LightDevice (file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:1310:55)
Nov 30 15:40:18 raspberrypi npx[1128]:     at createDevice (file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2166:10)
Nov 30 15:40:18 raspberrypi npx[1128]:     at BridgeDeviceManager.upsertDevice (file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2416:26)
Nov 30 15:40:18 raspberrypi npx[1128]:     at file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2405:21
Nov 30 15:40:18 raspberrypi npx[1128]:     at Array.map (<anonymous>)
Nov 30 15:40:18 raspberrypi npx[1128]:     at BridgeDeviceManager.upsertDevices (file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2403:16)
Nov 30 15:40:18 raspberrypi npx[1128]:     at async BridgeDeviceManager.loadDevices (file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2377:25)
Nov 30 15:40:18 raspberrypi npx[1128]:     at async _BridgeServerNode.start (file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2531:7)
Nov 30 15:40:18 raspberrypi npx[1128]:     at async _BridgeService.initialize (file:///opt/matterhub/node_modules/home-assistant-matter-hub/dist/backend/cli.js:2596:7)

For that one, it seems that a process exit is missing for fatal issues.

Is there any way to detect that home assistant is not yet ready? I don't find the HA websocket api well documented.
Similar to the message that the UI is showing during HA restart?
We could delay everything until it detects HA to be fully running.


Non-AMD dependencies seem not to be working correctly

I'm trying to use a non-AMD jQuery plugin loaded from CDN and once in a while I'm seeing an error, which seems like the plugin is being loaded before jQuery.
I have the following setup:
config.json (standard external omitted for brevity):
  "externals": {
    "jquery": {
      "path": "https://code.jquery.com/jquery-2.1.1.min.js",
      "globalName": "jQuery"
    },
    "simpleWeather": {
      "path": "https://cdnjs.cloudflare.com/ajax/libs/jquery.simpleWeather/3.1.0/jquery.simpleWeather.min.js",
      "globalName": "jQuery",
      "globalDependencies": ["jquery"]
    }
  }

WebPart:
import * as $ from 'jquery';
require('simpleWeather');

Both scripts load correctly (200 OK status), but once in a while I'm seeing the following error:
Error: Unable to load web part script resources due to: Error: ReferenceError: jQuery is not defined at eval (https://cdnjs.cloudflare.com/ajax/libs/jquery.simpleWeather/3.1.0/jquery.simpleWeather.min.js:2:3490) Evaluating https://cdnjs.cloudflare.com/ajax/libs/jquery.simpleWeather/3.1.0/jquery.simpleWeather.min.js Error loading https://spoppe-a.akamaihd.net/files/simpleWeather. at http://lt-wama.local:4321/node_modules/@microsoft/sp-client-preview/dist/sp-client-preview.js:19233:32

The network graph shows both scripts are loaded simultaneously despite the dependencies. Using the ModuleLoader similar setup works as expected.

@nickpape-msft - can you take a look at this and see if it is a documentation issue (here's how you do this) vs a product issue (you can't do this)?

This issue has been addressed. We'll update the issue again once it is included in an update. Thanks!

This has been fixed in Drop2


Table compaction removes duplicates

Table compaction process should remove duplicate records from the table to ensure the highest quality/most accurate search results.

Issue moved to smartcitiesdata/forklift #87 via ZenHub

Moved since compaction happens in forklift today.


Inefficient +setcpuaffinity defaults

PR #2448 changed cpuAffinityRecvHandler to use logical indices when assigning CPU affinity instead of non-portable OS indices in response to Issue #2445, where the latter causes an abort with +setcpuaffinity on Bridges. This new numbering scheme may result in poor performance in some cases due to grouping threads as closely as possible on adjacent SMTs while leaving entire cores unused. The example reported is with +p12 on a 2 sockets x 8 cores x 2 PUs = 32-way SMP machine.

I have also reproduced this on a 1 socket x 4 cores x 2 PUs = 8-way SMP machine, so it doesn't just happen on multi-socket machines.

After working on this for some time I think it's better to just revert the change that introduced this problem. The code in question needs more substantial replacement. #2649


Missing dependency(strnatcmp) in krsort's comment.

Thank you for your good library.

Thanks, fixed in https://github.com/kvz/phpjs/commit/fcadeab08015fae2eb60e944124dd02ae8b79991


first prototype of a stream plugin

The approach taken is to reuse the existing index.html template and instead flatten album hierarchies in a rather unorthodox way. Media stay linkable by prefixing the album path to their internal paths.
Many issues with the code still:

[x] the way albums are flattened is definitely out of whack, with nasty copy() all over the place. not really sure it actually keeps the original albums sane. (update: unit tests make sure the original albums are kept intact)
[ ] performance might break down on large albums. (is this really a problem?)
[x] class methods that should be in the Album class are just lying around stupidly in the plugin instead
[x] code refactoring, once done, should trickle back into the feeds plugin as well
[ ] i am unsure if the modification of filename and thumbnail_path is sufficient for our needs. is url, for example, used anywhere?
[x] no unit tests: only tested this by hand and by looking at the ouput.
[ ] documentation missing (maybe? are docstrings enough?)

Other todos:

[ ] only one stream is created. having per-album streams might seem redundant, but for large hierarchies, it could prove useful.
[ ] stream page is not linked from anywhere. i haven't figured out how this is done in the feeds plugin yet and can hack around this in the album descriptions for now.
[ ] album exclusion could prove useful to avoid the privacy leaks that feeds suffer from

Closes: #303 (eventually)

note that i have found that reordering the test suite may lead to breakage. by using -x -ff to repeatedly test the streams plugin, i managed to trigger a failure in test_cli.py (KeyError("adjust_options") or something). i have lost the backtrace now unfortunately, but this is something to keep in mind: maybe i introduced a regression somehow?

i have now mostly complete unit test coverage for the code that's actually there, and i updated the todo list in the summary. what's basically missing now is a way to link to (or include?) the stream page somewhere. the feeds plugin is embedded directly in the theme templates:
          {% if 'sigal.plugins.feeds' in settings.plugins %}
          {% if settings.rss_feed %}
RSS Feed{% endif %}
          {% if settings.atom_feed %}
Atom Feed{% endif %}{% endif %}

should i just do the same, in the same place?
we also need to decide if we want a single stream page or a per-directory one, which would complicate the above template...
i think album exclusion can be implemented in a later stage, unless you think it's absolutely necessary.

Just discovered this and loved it!


Add a cancellation API endpoint for publishing

Discovery is needed to determine how we will accomplish this.
We know we will need to add a unique identifier to the original publish request to track the process.
We need to modify the events to provide information regarding the identifier for the publish event.

I'm closing this as not planned, we have other issues like #305 that are similar. And more work is needed outside of publisher to facilitate this regardless (e.g. in Connect)


[RFR] fix back method on batchDeleteController

[x] fix back button
[x] add test

need https://github.com/marmelab/admin-config/pull/12 to fix test.

Tests failed.

Can you rebase to retreieve the latest admin-config dependency ?


lib.css is a 404

Summary
/assets/css/lib.css is a 404
No gulp build errors, lib.css is present with content inside assets/css
Steps to Reproduce

Install Postleaf
Run Postleaf

Additional info

Postleaf version: latest (how do I tell?)
Node version: 7
Affected browsers: All
Operating system: Centos 7.3

Fix: Make sure your .env file has the correct APP_URL setting for the url you are accessing.


odc.stac.load with both nodata and groupby="solar_day" is not merging scenes properly

In short, it appears that passing in a specific (valid) nodata value causes groupby to not work properly.
It's a bit tricky to untangle, but here's an example notebook.
Simple reproduction of the issue can be seen in this code:
from pystac_client import Client
from odc.stac import load
from planetary_computer import sign_url

catalog = "https://planetarycomputer.microsoft.com/api/stac/v1"
client = Client.open(catalog)

ll = [177.5, -18.5]
ur = [179.0, -17.0]
bbox = [ll[0], ll[1], ur[0], ur[1]]

items = list(client.search(
    collections=["landsat-c2-l2"],
    datetime="2023-01/2023-03",
    bbox=bbox)
.items())

print(f"Found {len(items)} items")

# Found 40 items

data_grouped = load(
    items,
    resolution=90,
    bbox=bbox,
    measurements=["qa_pixel"],
    chunks={},
    patch_url=sign_url,
    groupby="solar_day",
    nodata=0
)

CLOUD = 3
CLOUD_SHADOW = 4

bitmask = 0
for field in [CLOUD, CLOUD_SHADOW]:
    bitmask |= 1 << field

cloud_grouped = data_grouped.qa_pixel.astype("uint16") & bitmask != 0

count_not_cloud_grouped = (~cloud_grouped).sum(dim="time").compute()
count_not_cloud_grouped.plot.imshow(size=10)

This bright yellow triangle goes away if we remove the groupby="solar_day" or if we remove nodata=0. I'm pretty sure nodata is 0, but can't be sure.

Oh, 🤦.
The issue is that the qa_pixel band's 0 bit is the nodata bit, which means 1 is nodata...
My bad!

@alexgleith looks like we need a custom fuser implemented in odc.stac.load, although doing externally in Dask is probably a better option in terms of flexibility, so maybe just some examples would do. Unlike dc.load give me "completely unfused" pixels is an option here even when all items share the same timestamp.

give me "completely unfused" pixels

Yeah, I see what you're saying. It's nice there's the option for people who know what they're doing!
It's also nice to have an opinionated way of fusing. I wonder if there's a way to make it more obvious that you can fuse by day. (With groupby="solar_day").


Staking not detected

Issue description
ClientError: `Response error with status code 503: {"error":{"code":"503","message":"Service Unavailable, error: node is not synced: code=503, message=Service Unavailable"}}
Firefly version
1.3.10
OS details
Windows 11 Pro Education 21996.1
Can the issue be reliably reproduced?
No
Steps to reproduce the issue

...
Expected behaviour
I couldn't staking iota
Actual behaviour
A concise description of what you're experiencing.
Errors
Sun, 26 Dec 2021 20:22:28 GMT
ClientError: Response error with status code 502: Bad Gateway
Sun, 26 Dec 2021 20:15:35 GMT
ClientError: Response error with status code 404: {"error":{"code":"404","message":"Not Found, error: event not found: 57607d9f8cefc366c3ead71f5b1d76cef1b36a07eb775158c541107951d4aecb: code=404, message=Not Found"}}
Sun, 26 Dec 2021 20:14:48 GMT
ClientError: Response error with status code 503: {"error":{"code":"503","message":"Service Unavailable, error: node is not synced: code=503, message=Service Unavailable"}}

Duplicate #1894

same issue here aswell

👋 Hi, I’m @michaelwants, I am also currently experiencing this problem. I see it has been marked as a bug, does anyone know if there is a solution yet?
Cheers,

👀 I’m interested in ...
🌱 I’m currently learning ...

iam having same problem
says status not connected

same...
waiting for fixing...

I have the same problem.

Same for me. Steps as follows (Windows 10 Professional):
1- Installed Firefly yesterday.
2- Sent MIOTA to Firefly.
3- Staked in both projects. Live staking updates working fine.
4- Started PC this morning, upon Firefly launch "Something went wrong" error message.
5- Clicked on Staking icon, Staked Funds = 0 Mi.

Official statement:
We have some issues with the COO Node atm, the devs are working already on it, please be patient, you can't do anything at the moment.
Your Firefly will show "network disconnected" and you don't see your staking rewards. This is just temporary.
At the moment, no new staking rewards are generated during this downtime and no transactions can be issued. Your currently already gained rewards will NOT be lost, the minutes of this downtime will automatically be added to the staking period, so the exact 90 days staking will be achieved.

Thank you ✌
On Wed, 29 Dec 2021, 20:38 Richard K., @.***> wrote:

Official statement:
We have some issues with the COO Node atm, the devs are working already
on it, please be patient, you can't do anything at the moment. Your Firefly
will show "network disconnected" and you don't see your staking rewards.
This is just temporary. At the moment, no new staking rewards are generated
during this downtime and no transactions can be issued. Your currently
already gained rewards will NOT be lost, the minutes of this downtime will
automatically be added to the staking period, so the exact 90 days staking
will be achieved.
—
Reply to this email directly, view it on GitHub
https://github.com/iotaledger/firefly/issues/1896#issuecomment-1002516710,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXCU4MOGRDT63GTTOSM6DSTUTLM2TANCNFSM5KZIGEBQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

This is not a bug with firefly, the network is currently not issues new milestones. Please follow official IOTA channels to be notified when this issue is resolved. https://twitter.com/iota/status/1476130331812106244?s=20


Mention fuse-box-typechecker in documentation

Had to do some serious googling to find that project... would be useful to include in docs. Happy to do when I confirm it works.

Yeh I feel the documentation needs to be a little more in-depth as well. Hopefully once I get Fuse-Box working can take some of that burden from @nchanged and other contributors and contribute to the documentation.

@jpike88 Can you make a PR please ?

I stalled on this because I have no idea how to locally host the documentation so it all lines up correctly.
@nchanged I know it's all markdown, but what is _doc.json describing? Not sure what tool I need to work with this.

@jpike88 just edit an .md file there ;-)

I have no way of previewing the full site though. I'm editing a .json file and just adding another .md file? Feel like I'm working a little blind

why would you want to add an extra section? But sure, just add it there, and point to an md file similarly to the others. Other than then it should be a valid MD, that you can preview on github or any other editor with md preview feature. Just make sure to use only one # and ## as subsections

@jpike88 How's going ?

poop hit the fan over the last week with my projects, still busy as hell. I do have this as a todo, will probably achieve this on friday

FuseBox v4 Major Upgrade
As of today, the latest major version of FuseBox v4 is available in fuse-box@next. FuseBox has undergone a full re-write from scratch, learning from its mistakes in the previous versions.
There are a lot of improvements, speed and config wise.
Get started here
We are still working on the documentation and polishing before the major release. We are getting very close. And we need help testing.
npm install fuse-box@next

Most of the issues that I am closing have been resolved, however, if you find that your issue is still relevant in v4 don't hesitate to re-open or (better) create a new one with v4 configuration.


fix: calendar icon components' props not use.

closes #5225

you would need to run pnpm run build:registry  to update contents of the registry @laoer536

Okay, I have done as you said.


fix: welcome command not working on initial run

Please describe the changes this PR makes and why it should be merged:
When running the welcome script for the first time, I've noticed that the command fails with the following error:

Digging a bit into it, I found that dev/script.tsx does not exist because the pnpm run dev command is not awaited - but I understand why it's not because the command runs vite and such never ends unless we exit the process.
So I've moved the file writing to dev/script.tsx from the welcome script to the dev one. For reference, this error was thrown only if we don't have the dev/script.tsx file - so only on the initial run of this command (= if we don't have the dev folder).
Also, not really sure if it's intentional to update the dependencies when committing (ESLint has been bumped to 8.21.0, tell me if I need to revert this)
Status

[x] Code changes have been tested against prettier, or there are no code changes
[x] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[x] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[x] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.407%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1379

Relevant Lines:
2331

💛  - Coveralls

Package bumping should be intentional! LGTM :)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.407%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1379

Relevant Lines:
2331

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.407%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1379

Relevant Lines:
2331

💛  - Coveralls


All themes have bugged "Blue" colour?

Using Windows 10. Unless this is intended - each theme seems to have the "Blue" colour on the Select property type to be the same colour purple as the actual "Purple" colour. This doesn't apply to text colours or text highlights. Screenshots below of the colour menus for each theme (labelled):
Dark+:

Gameish:

Neutral:

Pastel Dark:

@dragonwocky I was about to open a new issue for this. Can I suggest reopening this as this is not fixed yet? Maybe adding a "awaiting-release" tag would be clearer.

that's probably a better way of doing it, yeah - was just trying to make it clear to myself what i needed to do and what i didn't.


Data does not be saved after uninstalling app

I tried to get some values once app installed if app was installed before. In this case, I got empty data instead of showing some values.

It depends on behavior of underlying system components - Android SharedPrefs and KeyStore and iOS Keychain. So it’s expected behavior for Android. For iOS usually the values are kept across installs.


Add config option for stdio baud rate

@kjbracey-arm has a good write up for the motivation behind this addition: #1969
Adds core.stdio-baud-rate configuration option. Defaults to 9600 for backwards compatibility.

@kjbracey-arm has a good write up for the motivation behind this addition: #1969

The same conversation that you mention explains that why the default baud rate is a better fit for a target configuration parameter.

The same conversation that you mention explains why the default baud rate is a better fit for a target configuration parameter.

Oh, I think I follow. So would the appropriate default mirror STDIO_UART_TX and be defined in the appropriate device.h?

I added support for a device provided STDIO_UART_BAUD_RATE. Let me know if this isn't what you were looking for.

This seems over complicated. There should be a single stdio_uart_baudrate which is default to 9600 and the application can override this or be old skool and just initialize an object in the application and use the baudrate member. It should not be defined or overridable by a target rather the application.
Why do we need STDIO_UART_BAUD_RATE and MBED_CONF_CORE_STDIO_BAUD_RATE

We dont need STDIO_UART_BAUD_RATE and MBED_CONF_CORE_STDIO_BAUD_RATE.

Agreed. Let me repeat what I already said in #1969 here: sometimes, the default baud rate depends a lot on the target board, since it might not be able to support high baud rates due to a number of hardware limitations (either in the MCU UART implementation, the clock used for the UART or both). I actually hit this issue once, although not with a mbed board (but still with a board that used an ARM MCU). So, if you want your printf("Hello world!\n") to always work without additional fiddling with the code or the configuration, the best place to define the default baud rate is in the target. You can add it as a configuration parameter to the base Target itself, then various targets can override that if they need to. As usual, the application will have the last word on the final value of the baud rate.

If the default is 9600 across boards, the expected immediate use here is that the applications that currently set baud to 115200 in their main.cpp (every mbed app I've ever worked on) will set it to 115200 in their JSON.
(If the default was faster, the apps would just leave it alone.)
At the minute the apps make the setting with an assumption that they're running on K64F (because they pass K64F pin assignments). But the point of the JSON is to make it generic - the apps would want to have it an all-target setting. If the baud rate is not supported, the board should ignore the setting and continue to use the default.

-1
Reasoning here https://github.com/mbedmicro/mbed/pull/1984#issuecomment-228058695

I'm going to go ahead and close this since it doesn't look like there's a clear way forward. This conversation can continue over here: #1969


setState called when widget is not mounted on MultiFrameImage emitter

customer:money is rarely seeing this crash (14 times within 4 weeks):
Thread 0 main thread_CastError: Null check operator used on a null value
at State.setState(framework.dart:1289)
at _ImageState._handleImageFrame(image.dart:1188)
at ImageStreamCompleter.setImage(image_stream.dart:616)
at MultiFrameImageStreamCompleter._emitFrame(image_stream.dart:946)
at MultiFrameImageStreamCompleter._decodeNextFrameAndSchedule(image_stream.dart:925)
at <asynchronous gap>(async)

Seems like there's a race between image frames being emitted and the widget being disposed.

Kizoojun

/cc @dnfield

I assume this is happening in non-debug modes? There are asserts higher up that should be triggered if it were to happen when asserts are enabled.

We could add some more defensive code before calling setState, but we should be doing everything correctly here and I'd like to understand better why this is happening.
In ImageState.dispose, we're unsubscribing from the stream. That should prevent further calls to _handleImageFrame.
The only thing I can think of is if we're somehow leaving a stray listener on the stream, but we shouldn't be.
It'd really help to have a reproduction for this.

We don't have repro unfortunately. It happens rarely in the wild (i.e. release mode). If nothing jumps out at you, we can close this. If the crash rates increase, we can revisit and hopefully have a repro.

On second thought, let's keep it open since closing this will also close the internal bug.

We could defensively add a mounted check but it'd be really nice to either know we can't avoid it because of async something messing it up (I can't see anything that would) or that we should remove it when we figure out what the real bug is.


chore: Removes documentation from README and link to docs on Charmhub instead

Description
Improves the README, metadata and config files
Note for reviewers:
Please take a look at the enhanced docs in Charmhub:

https://discourse.charmhub.io/t/route53-lego-operator-k8s-docs-index/12514

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[x] I validated that new and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

Looks good, but I would not use all caps for the name of the service. Amazon uses the capitalization I suggested.

Unless you want to yell it loudly...


Spreadsheets with requested variables

Spreadsheets with requested variables in format produced by dreqPy for CMIP6 should be created automatically. As requested during MIP/modeller drop-in at TT workshop. json file already provided listing requested variables, but spreadsheets are a preferred format for some users.

included in #30


Library modules (plugins)

Scripts can be added as script tags. The script will execute when the tag is added to the dom. The script can dispatch a custom event with the script method as details. In the client an event listener can handle this event and execute the method which has been passed as event details.
The script tag can be removed in the event handler.
However, having multiple scripts on multiple layers and multiple locations is problematic. The script would be loaded over and over again and multiple event handler with the same name may listen for the same custom event.
This can be solved by script modules.
Modules are defined on a locale as key value pairs in the modules object. The key being the name of the module and the value being the src of the module.
"modules": {
  "cluster": "/mapp/queries/cluster.js"
}

Modules can be loaded with xyz.modules() method. This method returns a promise which resolves once all modules are loaded.
Module scripts themselves need to call a custom event of the same name as the module key. The module method to add the module can be passed as detail in the custom event.
The method to add a module should only receive the current xyz object.
document.dispatchEvent(new CustomEvent('cluster', { detail: addModule }))

function addModule(_xyz) {

  _xyz.locale.modules.cluster = layer => {
    //module logic
   console.log(layer)
  }

}

The module method itself should be added as a function of the same name to the locale.modules object. This will effectively overwrite the src of the module with the actual module method.
The module can now be called.
If defined as an array in the layer configuration the module will be called with the layer as input for the module method. The module will be called when the layer view is created, thus allowing to add custom modules to the layer view.
"modules": ["cluster"]

tbc modules for location views.

Plugins for locations should be stored as function which receives the entry like so:
document.dispatchEvent(new CustomEvent('run_model', {
  detail: _xyz => {

    _xyz.locations.plugins.run_model = entry => {
   //plugin logic here
    }
  }
}))

In the entry the plugin must be called by the name as defined in the locale plugins.
{
  "class": "_report",
  "plugin": "run_model"
}

In the infoj process the plugin will now be called.
if (entry.plugin) {

  _xyz.locations.plugins[entry.plugin]
        && _xyz.locations.plugins[entry.plugin](entry)

  continue
}

https://geolytix.github.io/xyz/docs/develop/lib/plugins/


Add async tests for plugins

Description

Add asynchronous testing for plugins
Clean title in USER GUIDE for alerting section

Issues Resolved

To increase coverage
As requested here https://github.com/opensearch-project/opensearch-py/pull/398#discussion_r1245755900

LGTM, finish it up?

Hi @dblock, there are two points I'd like to look at:

the tests pass but the teardown of the last test is flaky, because the event loop seems closed
and coverage isn't increasing, because it seems that coverage reports sent to codecov are from the test workflow (https://github.com/opensearch-project/opensearch-py/blob/main/.github/workflows/test.yml), and in the test workflow no OpenSearch is run. So in fact coverage doesn't really represent what's being tested. I'm taking a little more time to see if it isn't possible to have a workflow that would launch all the tests (with a running OpenSearch), and that would send a complete report, which would make it possible to have a real coverage report on plugins for example.

@florianvazelle I wouldn't worry about coverage

@dblock Ok, so It's good to me now


Add macros.inc to a target deps, move unitialized buffer to the end of the data section

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.84%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
212

Relevant Lines:
291

💛  - Coveralls


nixos/zookeeper: recursively set permissions and ownership on dataDir

Motivation for this change
https://github.com/NixOS/nixpkgs/pull/59389#issuecomment-527469690
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @volth

@GrahamcOfBorg test zookeeper


Feature Request: Button in /resin message to rerun /resin

I'm happy to work on this and would've done the work before creating an issue but seeing as I'm busy today and tomorrow I figure I might as well put it here in case you have thoughts or objections.
Would be if I could just click a button on the /resin breakdown to quickly run it again.

Hmm, I generally want to avoid keeping long-running interactions (e.g. if the bot restarts, the button won't work any more because the view needs to be registered)
How long do you want to keep the button there? Forever?

Let me take a closer look at the button spec to understand how it functions before I get back to you.

Going to look at this this upcoming week.


Remove RGS

Fixes #2014.

Thanks for the review, @bonomat. I just pushed it as soon as it compiled haha.

Superseded by #2094.