signalbackup-tools: 20231011-1 -> 20231015

Description of changes
Update to latest version. No changes that effect build.
Diff: https://github.com/bepaald/signalbackup-tools/compare/20231011-1...20231015
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.


olebole should be able to approve astropy PRs

Description
@olebole has a named role in Astropy Team and is a voting member. However, when he approves a PR (e.g., https://github.com/astropy/astropy/pull/14416), it is only a gray check mark, not a green one. What kind of access can/should he get for his role in Astropy?

That would be fine with me. Thank you for the trust!

I'll close this issue, since it's dealt with in https://github.com/astropy/astropy.github.com/pull/541
No need to keep both open.


drvPath Missing

Hi,
I was trying to use the latestNightly in this flake.nix
{
  description = "A basic Rust devshell";

  inputs = {
    nixpkgs.url      = "github:NixOS/nixpkgs/nixos-unstable";
    rust-overlay.url = "github:oxalica/rust-overlay";
    flake-utils.url  = "github:numtide/flake-utils";
  };

  outputs = { self, nixpkgs, rust-overlay, flake-utils, ... }:
    flake-utils.lib.eachDefaultSystem (system:
      let
        overlays = [ (import rust-overlay) ];
        pkgs = import nixpkgs {
          inherit system overlays;
        };
      in
      with pkgs;
      {
        devShells.default = mkShell {
          buildInputs = [
            openssl
            pkg-config
            llvmPackages_latest.llvm
            gdb
            llvmPackages_latest.bintools
            zlib.out
            llvmPackages_latest.lld
            exa
            fd
            ripgrep
            (rust-bin.selectLatestNightlyWith (toolchain: toolchain.default.override){
              extensions= [ "rust-src" "rust-analyzer" ];
              targets = [ "wasm32-unknown-unknown" ];
            })
          ];

          shellHook = ''
            alias ls=exa
            alias find=fd
            alias grep=ripgrep
            '';
        };
      }
    );
}

but I get this error:
error: attribute 'drvPath' missing

       at /nix/store/5mvhi8rc47b6gwg0p8908l4x5a3jmqd5-source/rust-overlay.nix:405:41:

          404|           trace "Failed to select nightly version after 100 tries" ret
          405|         else if ret != null && (tryEval ret.drvPath).success then
             |                                         ^
          406|           ret
(use '--show-trace' to show detailed location information)

I'm pretty new to Nix, so let me know if I've done something terribly wrong

Made a dumb mistake. Closing


Investigate alternate base boxes for minimal size or customizability

@byteknacker https://github.com/boxcutter/ubuntu is a great starting point for Ubuntu based distributions. There are other distros in the boxcutter organization as well.
There are other smaller distributions like Alpine Linux, but Vagrant support for these isn't super robust yet because it doesn't contain some of the standard Linux base components it normally hooks into.

Thanks for adding this! I will check this out.


Indicate VMName as variable

VMName as a variable without valid variable syntax is misleading as well as inconsistent with remaining documentation.

@amiosci : Thanks for your contribution! The author(s) have been notified to review your proposed change.


XPY Splash screen and icon scale update

A few of these icons were bothering me after compering them to other wallets. I added higher resolution icon; fixed the splash screen since it was off center.
P.S. I am not sure if this is the proper way to go about doing this. Helping out with the UI, etc...

This is exactly the way to go about helping out with the UI etc. Keep it up!
Looks good to me.

If you guys say it looks better I'm for it. I don't see a difference in the splash screen or much of one in the paycoin icon itself but I also always use the daemon so meh.

The splash screen was only just 4 pixels off center, really not a big difference but it was just bothering me knowing that it was off center. If you use the swipe or onion skin tab you will see the difference :)

Yeah such a small difference but if the effort has been made to correct it, I'm happy with merging it in :)


Unit | Component | sl grid row: There are no references to Ember.$, $ or jQuery

not ok 451 PhantomJS 1.9 - Unit | Component | sl grid row: There are no references to Ember.$, $ or jQuery
    ---
        actual: >
            null
        message: >
            Died on test #1     at test (http://localhost:7357/assets/test-support.js:3025)
                at testWrapper (http://localhost:7357/assets/test-support.js:6192)
                at test (http://localhost:7357/assets/test-support.js:6205)
                at http://localhost:7357/assets/tests.js:23809
                at http://localhost:7357/assets/vendor.js:152
                at tryFinally (http://localhost:7357/assets/vendor.js:33)
                at http://localhost:7357/assets/vendor.js:158
                at http://localhost:7357/assets/test-loader.js:60
                at http://localhost:7357/assets/test-loader.js:51
                at http://localhost:7357/assets/test-loader.js:82
                at http://localhost:7357/assets/test-support.js:6024: Attempted to wrap $ which is already wrapped
        Log: |

Will likely be resolved by https://github.com/softlayer/sl-ember-components/issues/1503

Resolved by https://github.com/softlayer/sl-ember-components/issues/1503


[BUG] Wrong output in example in section 'Usage'

In third usage example 'Select month and day:' of README section Usage wrong output is provided.

Hi goldenticket,
thanks for reporting! I have fixed the incorrect documentation.
Cheers Yord


Get the next_item before updating the audit [SEAL IGNORE]

This fixes an issue where finding the next item doesn't work when
current audit is saved, and the current filtering conditions are
looking for non-audited items.

I've now included this fix in https://github.com/alphagov/content-performance-manager/pull/223 as it didn't seem sensible to keep the issue present there when reworking the related code.

@cbaines does this PR need to be closed?

@cbaines does this PR need to be closed?

Not as far as I'm aware? But I haven't looked at it since moving teams.

After discussion with @pmanrubia I'm going to close this PR as the fix is in #223, but altered which makes merging this PR harder to accommodate if we decide to merge in #223.


Improve SSM Log infrastructure

Now currently, when start-smart.sh runs, it prints all log information on the screen. We'd better save the log to the /logs directory and arrange the log file according to date,  log file size, etc, as other project, such as HDFS will usually do.

Did it in other tasks


Trigger Helm chart release.

Description
Updates the release CI job to trigger an event to the Helm chart repository to ensure that the major and minor releases will be in sync between all Kubewarden components.
Fix https://github.com/kubewarden/policy-server/issues/376

Analogous to the one in kubewarden-controller repo. Note though that the one from controller repo failed because of the secret.

That's weird. We are using the same token used by the bot that triggers jobs to update the policy hub repository. @flavio we need to review the token permissions.

Moving this to block until we fix the secret permissions.

It looks like the PAT has the right privileged enabled:

I think I figured out why this is happening: the token belongs to @chimera-kube-bot. Hence the bot must have write permissions to some of the repository where the target workflow belongs to. In this case, I guess we must give it write access to the https://github.com/kubewarden/helm-charts repository.
Am I right, is there some other repo that we should grant write access to?

Am I right, is there some other repo that we should grant write access to?

On top of my head, I cannot think in any other one. As the request will be trigger from the components to the helm-chart repository. I think it only need write access to the helm-chart repository for now.

@jvanz I've just given write access to @chimera-kube-bot  to the hem-charts repository. Let me know if that fixes the issue :crossed_fingers:


Dismiss Alert dialog on LongPress

I need to dismiss the AlertDialog on LongPress

@mohammedX6  wrap AlertDialog with GestureDetector and set onLongPress like
GestureDetector(
        onLongPress: () {Navigator.pop(context);},
        child: AlertDialog(
      title: Text("Test"),
      content: Text("Done..!"),
    )
)

@mohammedX6
Please ask support questions / code assistance on stackoverflow.
Closing from here.


Soundboard, 101Soundboards, Myinstants support

Checklist

[v] I'm reporting a new site support request
[v] I've verified that I'm running youtube-dl version 2021.02.10
[v] I've checked that all provided URLs are alive and playable in a browser
[v] I've checked that none of provided URLs violate any copyrights
[v] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Soundboard https://www.soundboard.com/sb/Deer_Sounds_audio
101 Soundboards https://www.101soundboards.com/boards/21617-ultimate-fart-soundboard
MyInstants https://www.myinstants.com

Description
These are websites that contain short audio clips for sound effect purposes
Usable applications include

https://github.com/gamebooster/soundboard
https://github.com/Soundux/Soundux/issues/47
https://github.com/ruohki/lunchpad

https://github.com/ytdl-org/youtube-dl#does-the-issue-involve-one-problem-and-one-problem-only


Round3_DoubleDown: first Player up rejected to buy time, all other players had coins, but didn't get modal. phase advanced forward

round 3 double down phase. Ipad got the prompt to buy time first. rejected, and immediately moved into the decide phase.
This was a game with 4 players, fyi.
This didn't happen in the same game in round 1 or 2.

maybe something to do with turn order + randomization we introduced recently?


Vagrant test cluster is not torn down and Minions are missed when doing so manually.

We should call kube-down in e2e when running teardown. Currently we just echo "Vagrant ignores tear-down".
In doing so we also need to ensure that minion-2 is torn down. When calling cluster/kube-down.sh manually master and minion-1 are torn down correctly while minion-2 is missed.
/cc @derekwaynecarr

I think sorting this out should resolve any issues from https://github.com/GoogleCloudPlatform/kubernetes/issues/7719 and https://github.com/GoogleCloudPlatform/kubernetes/pull/7032#issuecomment-100319199.


Increase coverage

Various fixes to increase coverage and improve docstrings.

There are still some additional changes I want to do before merging

I don't think I will have time to work on this in the next few weeks so I think it is better to merge. If you think otherwise let me know, otherwise I will merge tomorrow.


Docs: Add unit to the maxFileSize in the FileUploaderInput props

coverage: 96.957%. remained the same when pulling fb3df748e752930bf6906423a342237b4a115832 on docs/fileuploader into 1ccba925f3e5f0988d472aee38571ca07b303a60 on main.


[docs] Updated error message for requirePropFactory.

[x] I have followed (at least) the PR section of the contributing guide.

Fixes #14559

@oliviertassinari Can you help me fix the argos problem?

@oliviertassinari  Can you help me fix the argos problem?

@udayRedI Thanks :)


Package structure

Hi,
thanks for this project, it's really helpful to get to know typelevel libraries. I get the clue behind splitting domain and infrastructure package.
While the domain package has a feature based structure, the infrastructure stays to component/technology based structure. But why?
Thinking further to add more domains like order, customer, shop and so on. Is it useful to place these domains into packages like doobie or inmemory. In case of several data sinks (like Elasticsearch, or a HTTP-REST service) it would be necessary to place implementations into packages like elasticsearch or http/rest
Would it be more significant to apply a feature based structure to the infrastructure package?
Greets

Hello @elcolto 👋
The domain package should be implementation independent.  Following DDD, it contains Services (gateways to the domain), Repositories (where to get and save data), Models which are your domain models (which in FP tend to have no logic just data).  Also, all your business logic, validations, and invariants go in here.
For infrastructure, I think this is where code organization can be rather subjective.  I personally prefer the existing package structure, but it is definitely not a mandate.  The onion architecture implementations I have come across (very subjective and limited to my experience) follow the same structure as in the pet store, and it is the one I use in "real" projects.
The onion architecture is not opinionated on package structure afaik.  The main driver of the onion architecture is to keep infrastructure concerns separate from your domain.
https://dzone.com/articles/onion-architecture-is-interesting
I am curious if there are tangible benefits in following a structure you recommended.  For example, new emerging standards where it would be more idiomatic.


README lacks instructions on how to install and enable this module

The README.md file in its current state is a bit sparse. There are detailed instructions on installing and enabling the functionality of this module on https://github.com/silverstripe/cwp/blob/master/docs/en/02_Features/pdf_export.md
I suggest we copy this information into the README.md or link to the CWP documentation under the installation heading.

Also, there is a current issue https://github.com/silverstripe/silverstripe-framework/issues/7970 that may affect the configuration of this module. Depending on how we decide to resolve it, we should keep in mind to record necessary 'workarounds' in the documentation, if necessary.
At the moment I changed my configuration to deal with this as follows:
---
Name: myconfig
---
CWP\PDFExport\Extensions\PDFExportExtension:
  pdf_export: true

soooooo is this done?

I think we ended up with two issues in one here, but the original "update the readme" still needs to be done =)


Fixed leak of OpenGL backend items on branch 0.14

Under some conditions (PlotWidget in a not visible tabbed DockWidget + some condition not yet clearly defined...) it happens that PlotWidget.replot is called (since PlotWidget.isVisible() is True) but BackendOpenGL.paintGL is not.
This can leads to new items to be created in the backend (in PlotWidget.replot) and never discarded (in BackendOpenGL.paintGL)
This PR workarounds this issue by adding the list of backend items to "discard " (which is done lazily in paintGL) only the ones that really needs to free some GPU resources (i.e., that has already been displayed).
It has the advantage of only modifying the OpenGL backend.
Related to #3443

Looks good to me.
Ill check it now.


how to determine the parameters in process_xxx.m

Hello, I am very interested in your work. I want to ask how to determine the parameters (i.e. 60: 80, 1:29, and 1:100) in process_xxx.m, for example, the chikusei_pan = mean(chikusei(:,:,60:80), 3); Botswana_pan = mean(Botswana(:,:,1:29), 3); pavia_pan = mean(pavia(:,:,1:100), 3);

Hi @yisun98 What do you mean by the parameters? Do you mean the band numbers? I referred the original dataset descriptions.


Update material and finish group modals

Definition of Done

[ ] The code does at least what is defined in the ticket and does not affect any other functionality
[ ] The PR has a meaningful title
[ ] There is a link to the issue-id
[ ] There are no 'hacks' or shortcuts refactoring is preferred
[ ] The happy case of the app was tested at least once manually

@Dansken I think we need to talk about this


Fixing hostname issue with IPv6 addresses

https://github.com/jmdns/jmdns/issues/62
Signed-off-by: Dominik Hufnagel<EMAIL_ADDRESS>(github: dhufnagel)

Thanks!


Second click to close Brackets under Linux

When attempting to close a Brackets window under Linux Mint 17.2, a second click is required on the "x" close button (it doesn't with any other application).
This issue was present in release 1.3, as well as in 1.4 and still is in 1.5.

Duplicate of https://github.com/adobe/brackets/issues/4611
Closing.


PS_PAYLOAD set_incrementing & set_decrementing missing

Problem found! It is my bad. The functions are renamed due to the introduction of more PS_PAYLOAD modes.

Maybe the best solution is to make the driver backward compatible with test suites as below?


Support 'module' entry point

Per the proposal in https://github.com/dherman/defense-of-dot-js/blob/master/proposal.md for replacing main with module for packages with ES modules in Node.
This gives a better path forward and better alignment with other tools.

Also it should be enabled by default. since it's not just our convention.


Closes vigetlabs/grunt-complexity#20

Throw a more detailed error message in event of an empty source file is
encountered. Setting content=' ' will only mask the issue rather than
providing the user with feedback to take an appropriate action on the
file.
Error thrown will now return:
Warning: Empty source file: 'src/routes/api.js'. Use --force to continue.

Added unit test and fixture for this corner case.

Thank you!

I know this is inexcusably late. I have no excuse. I am sorry for the gap.


Sherelyn magnitude fix

Sherelyn's fixes #95 with the merge conflict resolved.

CI needs to be fixed. #98 .

These changes apparently were made already.


pitch variants for sound effect

just like what dead cells does!

Ooooh, didn't know you could do that in the sounds.json!
I probably won't merge this pull request due to the merge conflict (some "newer" sounds are missing), but I'll most likely delegate the creation of this file to datagen and automate adding the pitch variants 😁
Thank you!

Updated for 1.6.0 version, as a temporal alternative for this feature(if anybody, like a modpack dev wants).


Update aio-lib-runtime major

Description
This uses the new bin script method of running your command.
Updated aio-lib-runtime version to support worker:runtime:nodejs:16
@oclif/config => (@oclif/core).Config
Fixes # (issue)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

I have a presentation for consultants for field enablement on Thursday and I want to wait to merge this until after since I won't have time to validate aio v9 works for Asset Compute Custom Workers.

i will merge as a bugfix release:
https://cq-dev.slack.com/archives/C013UDBFBGB/p1665161697013669?thread_ts=1664386796.277959&cid=C013UDBFBGB

Older versions should still target the previous version of the plugin.
With semver we should be okay.


CLI: Substitutions not substituted everywhere

My goal is to use a substitutions for container labels, like e.g.
steps:
  - id: some-id
    uses: some-image
    options:
      labels:
        sample-label: $_POPPER_SUBST_LABEL
    args: some-args

However, popper does substitutions only within top-level keys of each step (e.g. id) and top-level dicts (e.g. env), but not further down the yaml tree.
Observed behavior
popper run -f the-above-wf.yml --substitution _POPPER_SUBST_LABEL=this-should-appear results in
steps:
  - id: some-id
    uses: some-image
    options:
      labels:
        sample-label: $_POPPER_SUBST_LABEL
    args: some-args

instead of the expected output.
Expected behavior
steps:
  - id: some-id
    uses: some-image
    options:
      labels:
        sample-label: this-should-appear
    args: some-args

For reference, the documentation suggests that substitutions apply globally: link to doc.
Here's a link to the code.

#967 Solves this issue.


canu 1.6.4 release

Summary and Scope
Summary and Scope
[1.6.4]
Documentation updates to docs/network_configuration_and_upgrade

[1.6.3]
Use full show run commands to retrieve running config from canu network backup
UAN CAN ports are now shutdown if CHN is enabled.
Mellanox UAN CAN ports now only allow the CAN vlan.
Added CMC subrack port configuration.
Documentation updates to docs/network_configuration_and_upgrade

[1.6.2]
Correct the 'slot warning' to specify more accurate options

Issues and Related PRs
[List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CASMNET-1591

Testing
Nox
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

I removed canu from the NCN manifest. It will now get installed the same way csm-testing, goss-servers, and platform-utils get installed.


refactor(ast_codegen): no longer outputs discard variable for empty visitors.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4008  👈
#4007
#4006
#4001
#3954
#4000
#3998
#3995
#3994
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rzvxa and the rest of your teammates on  Graphite


Add Stale to DSC Resource Kit repositories

After testing Stale in my test repo DebugApps it seems to work very well for part of our workflow. I suggest we add this GitHub App to DSC Resource Kit.
It will not be enabled until each repo opt-in by adding the below configuration to .github/stale.yml. The below configuration will handle issues and pull request differently. Each repository can set this individually.
Issues
It will remind that there haven't been activity on an issue for 30 days. If there are no further activity withing 40 days it will close the issue. It will not close an issue if the issue is assigned one of the labels under exemptLabels (the last two of them is only needed for DscResources repo). Neither will it close issues that are part of a milestone or project (that is just a precaution, because those issues should have a work label assigned too). Any other label, like a "waiting label", 'question' or 'discussion' label will be kept together with the 'needs more information' label.
If a comment (activity) is made on the issue the 'needs more information' label is removed.
See example: https://github.com/PowerShell/SqlServerDsc/issues/811
Pull Request (PR)
PR's that are not labeled with 'needs review', 'on hold' or 'waiting for CLA pass' will be labeled as abandoned after 14 days of inactivity. Any other label, like a "waiting label" will be kept together with the abandoned label.
See example: https://github.com/PowerShell/SqlServerDsc/pull/1045

Note: Pull requests that are labeled as 'waiting for CLA pass' should be closed after 14 days. But his app cannot handle that.

Configuration
# Configuration for probot-stale - https://github.com/probot/stale

limitPerRun: 30

pulls:
  daysUntilStale: 14
  daysUntilClose: false
  exemptProjects: true
  exemptMilestones: true
  staleLabel: abandoned
  exemptLabels:
    - needs review
    - on hold
    - waiting for CLA pass

  markComment: >
    Labeling this pull request (PR) as abandoned since it has gone 14 days or more
    since the last update. An abandoned PR can be continued by another contributor.
    The abandoned label will be removed if work on this PR is taken up again.

issues:
  daysUntilStale: 30
  daysUntilClose: 40
  exemptProjects: true
  exemptMilestones: true
  staleLabel: needs more information
  exemptLabels:
    - bug
    - enhancement
    - tests
    - documentation
    - resource proposal
    - on hold
    - new module submission
    - module proposal

  markComment: >
    This issue has been automatically marked as needs more information because
    it has not had activity from the community in the last 30 days. It will be
    closed if no further activity occurs within 10 days. If the issue is labelled
    with any of the work labels (e.g bug, enhancement, documentation, or tests)
    then the issue will not auto-close.

  closeComment: >
    This issue has been automatically closed because it is has not had activity
    from the community in the last 40 days.

After activating this in SqlServerDsc an issues was found, the configuration above is updated. 'resource proposal' was added as an work-label.

Updated configuration not to close PR's (daysUntilClose: false). I thought leaving the key out would accomplish that, and for some reason it worked in my tests, but it closed PRs in SqlServerDsc. Reading the documentation it clearly says it should be set to false.

So it seems there is a bug or an unsupported scenario in the Stale app. It keeps closing PR's even when setting daysUntilClose: false (see https://github.com/johlju/DebugApps/pull/11). Reported it in issue https://github.com/probot/stale/issues/129, so hopefully someone in the community can shed some light on this .

I'm testing another configuration in my DebugApps repo , adding only: key too - if that does not work, then we have to remove the pulls: part of the configuration since it does not work as intended.

We need to remove the pulls: part of the configuration. It doesn't seem it works as intended. I will resolve this by temporary uncomment that part of the configuration and referencing to https://github.com/PowerShell/DscResources/issues/401#issuecomment-395050731.
Also, Stale needs it's own label to work properly. The labels used for marking issues and PR's as stale cannot be set manually by a maintainer - Stale will always remove the label on activity. For this purpose we need to add a new label 'Stale' and update the configuration accordingly. I will add a new label to the list in issue #364, and also the configuration in the issue description is updated.

To get where the Stale app adds in the automation context I added this code2flow flowchart. This is so we can document this.
This only shows the schedule part. I will create another one for the "on edit"

This is the code to build the flowchart.
// Runs approx. every hour.
// Checks each issue and
// pull request.
// Max 30 items per run.
On Schedule;
switch(Type)
{
  case Issue:
  {
    if(Is labeled with 'stale'?)
    {
      if(Inactive for 10 days?)
      {
        Close issue;
      }
    }
    else
    {
      if(Inactive for 30 days?)
      {
        if(Is part of project?)
        {
        }
        elseif(Is part of milestone?)
        {
        }
        // **Labels:**
        // needs review
        // on hold
        // waiting for CLA pass
        elseif(Has exempt label?)
        {
        }
        else
        {
          Label 'Stale';
          Write stale
          issue comment;
        }
      }
    }
    break;
  }

  case Pull Request:
  {
    if(Inactive for 14 days?)
    {
      if(Is part of project?)
      {
      }
      elseif(Is part of milestone?)
      {
      }
      // **Labels:**
      // bug
      // enhancement
      // tests
      // documentation
      // resource proposal
      // on hold
      // -
      // **Special labels:**
      // new module submission
      // module proposal
      elseif(Has exempt label?)
      {
      }
      else
      {
        Label 'abandoned';
        Write stale pull
        request comment;
      }
    }
    break;
  }
};
Finished;

I found a tool that can send in PR's; https://github.com/jd/git-pull-request
It works very well, although I need to run it in PS Core in my Ubuntu WSL, it failed on Windows reading a temp file itself created. Small thing looping through all repos now.
I can't update the change log automatically without a lot of logic, so I think for the sake of speed I will ignore that for this, any objections to that?
sudo git clone https://github.com/PowerShell/xActiveDirectory
sudo git clone https://github.com/PowerShell/xSCVMM
cd ./xSCVMM/
sudo git checkout -b activate-stale --track origin/dev
sudo mkdir .github
cd ./.github/
sudo cp ../../xActiveDirectory/.github/stale.yml .
cd ..
sudo git add .github/stale.yml
sudo git commit -m "Activate the GitHub App Stale on the GitHub repository"
sudo git pull-request --title "Activate the GitHub App Stale on the GitHub repository" --no-tag-previous-revision

And the result of the last command.
Forked repository: https://github.com/johlju/xSCVMM
Added forked repository as remote `github'
Fetching origin
Rebasing branch `activate-stale' on branch `origin/dev'
Current branch activate-stale is up to date.
Force-pushing branch `activate-stale' to remote `github'
Counting objects: 4, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 917 bytes | 0 bytes/s, done.
Total 4 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To https://github.com/johlju/xSCVMM.git
 * [new branch]      activate-stale -> activate-stale
$EDITOR is unset, you will not be able to edit the pull-request message
Activate the GitHub App Stale on the GitHub repository

Pull-request created: https://github.com/PowerShell/xSCVMM/pull/9

And the finished PR: https://github.com/PowerShell/xSCVMM/pull/9

I have now sent in PR's to activate Stale to all repos.
/cc @athaynes, @ld0614, @PlagueHO, @NikCharlebois, @jcwalker, @ykuijs, @mhendric, @mbreakey3, @kwirkykat

Thank you very much @johlju !

Stale is now activated on all repos except PSDscResources (waiting for @kwirkykat to merge that one).


Model not showing when loading from dropbox - must click zoom extents

There is a bug here when a model is loaded from a link. I can't see the model, but it seems like it's just missing the zoomExtents call. I'll look into it.

fixed :eyeglasses:


Works very well on SailfishOS, Thank you ! 😅
Demo can be found at

Wow I can't click it to open the issue, but anyway I can hack it


Implement Prometheus Metrics for Nauticus controller

The goal of this task is to implement Prometheus metrics for the Nauticus controller. This will involve creating new endpoints in the controller to expose metrics in a Prometheus-compatible format and configuring Prometheus to scrape these endpoints. The metrics should include information about the number of spaces, resource quotas, and network policies created, updated, and deleted. Additionally, it should include information about the number of errors that occur during these operations. The implementation should follow best practices for Prometheus metric collection and should be thoroughly tested before being merged into the main codebase. A documentation should be added to the official documentation of nauticus about how to use these metrics. The task should also include the setup of grafana dashboard for the metrics.

BTW, we might want to specify OpenMetrics format rather than Prometheus. Prometheus' de facto text format evolved into OpenMetrics.


refactor: remove standard_lib nested folder

Moved modules from standard_lib folder to its parent folder
Kept addon_basic.py in standard_lib folder for backward compatibility.

:tada: This PR is included in version 5.3.0-beta.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Implement querying fulltext values.

@rnewman you can take a look at the first commit, if you care to.
@fluffyemily if you're using the new parsing apparatus (yet to land!), this is a self-contained example of how to use it.

Also this is a fantastic example of extending the query parser. 👍

Obsoleted by #477.


beyondcompare5: Add version <IP_ADDRESS>045

The Scoop 'Extras' bucket supports only version Beyond Compare 4 so far - this PR introduces Beyond Compare 5.

Closes #13663

Relates to #13663

[x] I have read the Contributing Guide.

Edited PR description above:

the referenced issue https://github.com/ScoopInstaller/Extras/issues/13663 wanted to add Beyond Compare 5 (beta at that time)
Beyond Compare 5 is out of beta phase nowadays

/verify

/verify

Can I have an approval here, please.

/verify


Question: Is Project Reunion supporting Ribbon interface?

I find the Ribbon interface very useful, and my users do too. It's clean, fits many commands without taking lots of real-estate space, and most importantly, they are used to them because Office heavily uses them too. The new proposed UWP UI design with a lateral menu simply pissed off my customers, so we never had plans to migrate (apart from proof-of-concepts and demos). Will Project Reunion then support this useful user interface design and provide first-grade support for it?
And if the Ribbon won't be supported, why? If Office is still using it, why shouldn't we?
Thanks in advance!

@fernandoagomezf See: https://github.com/microsoft/microsoft-ui-xaml/issues/168

Let's let the ui-xaml issue above (microsoft/microsoft-ui-xaml#168) track this ask. Is this interesting enough that someone in the community would be interested in taking a shot at it?

@fernandoagomezf See: microsoft/microsoft-ui-xaml#168

Awesome thanks, so it's in the roadmap, just not released yet. This will be huge for my customers, when released!

@stevewri It has been discussed with the WinUI team that @yoshiask of the community will first create a Ribbon implementation in the Windows Community Toolkit (https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/3259) which will likely act as a template for the WinUI control to be added in the future.


Rename deprecated subscribeAsync function

subscribeAsync annotated as deprecated function  source
Using subscribe function instead.

i've created another branch to support the as-yet unreleased fully async operation of java-nats
https://github.com/employeerepublic/clj-nats-async/tree/jnats-1.1.0-TESTREL
i'll merge this PR and cut a new release when i merge that branch


[web] multiple severe benchmark regressions after engine roll

Engine roll: https://github.com/flutter/flutter/pull/155799
Regression: https://flutter-flutter-perf.skia.org/t/?begin=1727400207&end=1727400209&subset=all
Some regressions seem to have been misattributed to another PR too here: https://flutter-flutter-perf.skia.org/t/?begin=1727398530&end=1727398532&subset=all
I suspect this is due to https://github.com/flutter/engine/pull/55464. According to the benchmark history a previous attempt to land platform view changes cause the same regression: https://github.com/flutter/flutter/pull/155733

Fixed by https://github.com/flutter/engine/pull/55501


Notebooks

Make an examples

[x] with neural network, example of too many dimensional function
[x] with a suitable interesting function
[x] measure the execution time of each method

heavy_example_test_time.ipynb


docs: release notes

What I did
Added some minor updates to the Release notes page, covering the following:

Pages added to the Get started section back in May 2022
Content updates made in January 2023

@marionnegp Fixed, please merge.

I changed "Icon library" to "Icon libraries" in the linked text. I can merge this first thing tomorrow if you're good with that change.


fix: request custom domain error issue

If my custom api url is "http://localhost:3000/model",  this script is matched url result is "st:3000/model", but this wrong.  Expect result is  "http://localhost:3000/model".

If custom api url is "http://localhost:3000/model",  result is "st:3000/model"

it's not true

Expect result is "http://localhost:3000/model"

if not change happened to url, why not delete

close due to no response


Exec /bin/bash by default

Hi,
Pushing few patches concerning mainly two things:

There are still some references to old Docker repositories (ulexus/ or ceph/ceph-), that I replaced. I kept the ones for rbd in ulexus/ since they don't exist (yet ?) on ceph/.
I added an helper script in ceph/base to be able to assist in the execution of this image directly (which can be conveniant to use ceph directly).

If you intend to create ceph/rados ceph/rbd ceph/rbd-* , please create a patch with:
grep -Rl "ulexus/" |grep -v ".git" |xargs sed -i 's^ulexus/^ceph/^g'
Thanks,
Bertrand

@Ulexus LGTM, what do you think?

@leseb It looks good to me, yes.  I'll also kick off a rebuild on Docker (still no way for me to setup the autobuild... I have insufficient access to the Github account for that, whatever that implies)
@CoRfr Just rebase, and it should be good.  Sorry for the delay... not sure why I didn't see a notification about this PR.

@CoRfr And thanks!

@leseb @Ulexus I updated my branch to remove all fix references stuff, as this has already been done (and now ceph/ is an automated repo, awesome :) ).
PS: name is inconsistent for ceph/rbd (CEPH instead of Ceph)

Thanks; it looks good.  I'm curious why you explicitly name bash in the apt-get install statement, though.  I'm pretty sure it's in the base image already.
Capitalization fixed, mostly.  Full consistency would have be name them RBD and RADOS instead of rbd and rados... but since they are referring to the cli tools, I think it would be inappropriate.  I guess I could change MON, OSD, MDS, etc., but I'm going to stop here, for now.

1/ For bash, I though it was not in the ubuntu:14.04 for some reason, while it is (my mistake), so I'm removing that part
2/ For --rm, I use the base image a bit differently, using --volumes-from, as a "base" to communicate with the ceph system, which is why I don't want leftovers.
Something like: docker run --rm -ti --volumes-from=ceph-data ceph/base ceph osd ls
Though, I understand what you mean and removed the --rm.
3/ I renamed to entrypoint.sh for consistency as you asked.
I guess it would be nice to also have rados images in sync (entrypoint as /usr/local/bin/entrypoint.sh ), and I'm not sure the chmod step is necessary (expect for radosgw since the entrypoint.sh has no +x).

@CoRfr I'm pretty sure all the others are now in sync (/entrypoint.sh).  Let me know if I missed one, though.

The entrypoint.sh file was changed, but the Dockerfile still needs to be updated with the new path.

@Ulexus I'm not sure I understand. There are 2 different path for "entrypoint.sh", one is "/entrypoint.sh" (rbd-unlock, rbd-lock, rbd-volume) and one is "/usr/local/bin/entrypoint.sh" (mon, osd, mds, radosgw, rbd-volume).
Since "core" images where using "/usr/local/bin/entrypoint.sh", I went for that option, should it be "/entrypoint.sh" ?

My bad, I missed a rebase, I will update to /entrypoint.sh right away.

Thanks @CoRfr


Add projects list to our documentation.

This list should be information only and not the source of truth for projects.

this looks great … is there a way that we can have this automatically update when a new project is brought on (I’m sure there is, but I’m not sure what the best way to do it would be though!)

I guess it comes back to, what's the purpose of this documentation? We could refer people to the repositories page on the org to see what projects are there. And we can refer people to the issues to find the joined date.
Regarding needing to do something based on the join date, @williln's source of truth sheet of projects and next actions should cover that.
I guess I'm arguing maybe we don't have the list here and use this page to route folks to the relevant areas.

I do agree with @tim-schilling that it's possible this list will go stale, and there are other places where this information can be found... but I also think there is value in having the list of projects very easily accessible, especially for projects who are considering joining Django Commons. Seeing other projects you know, use, and trust that are part of Django Commons increases the overall "trust" factor for the organization, I think.
@tim-schilling would a compromise maybe be retaining this list until it gets too long to manage (at which point... yay, look how successful we are!), and then updating to point to the repositories link? I think it serves a valuable marketing purpose for now, but that probably won't always be the case.


$PATH for PGTK  window

Hello, I can't read the execution path of some programs under pgtk, so I added this support.

Thanks, makes sense.


add new settings to disable editing Main menus and Flat menus in the Wagtail CMS

#234

Hi @mvdwaeter,
Thanks for this! I'm happy with the implementation, and the docs additions are perfect too. It would be nice to have a couple of simple regression tests to show the effect of setting each to False. Is that something you're happy to do?

Hi @ababic , I added tests. As Django settings are always a pain to test, I ended up using a mock library  + reloading the wagtail_hooks file, to proof that the modeladmin_register function with respective menuAdmin type is called or not based on the setting.

Thanks @mvdwaeter! Wow, that was fast! However, I feel these tests could be simplified a little. How do you feel about just checking if accessing listing page returns a 404?
Also, there's an existing TestSuperUser test case in test_backend.py that would make a suitable home.

Hi @ababic , I started with that first, exactly with your provided test as a template. But unfortunately a 200 response was still returned because the modeladmin was already registered after settings were overridden. Perhaps I overlooked something, but I couldn't get it to work that way.
The tests I provided are actually very pure, it tests whether the modeladmin_register is called or not based on settings. Assuming that modeladmin_register is well tested by wagtail, that's all you need.

HI @mvdwaeter

But unfortunately a 200 response was still returned because the modeladmin was already registered after settings were overridden. Perhaps I overlooked something, but I couldn't get it to work that way.

Ah yes, that's probably the case. Not to worry then.

Assuming that modeladmin_register is well tested by wagtail, that's all you need.

I agree with this to a point. I just don't think it's good practice to have tests assume too much about the technical implementation if at all avoidable - especially so if they're reliant on the inner workings of other apps. It sounds as though this might be the only option though.

Thanks for this @mvdwaeter.  Really appreciate your time and effort with this - especially with how tricky the tests have been. Just one small change, and we're good to go! Also, please credit yourself in CONTRIBUTORS.md :)

Thank you :) Happy to contribute!


Use current rspec API for rspec stub example

In rspec 3, if you try:
helpers.stub(users_path: '/users')

You get a deprecation warning:
Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead.

And in addition to the deprecation warning, it actually fails with a message:
#<Draper::HelperProxy: ...  [lots of text] ... does not implement: users_path

If we switch to 'new' rspec API `allow(:helpers).to receive(:users_path).and_return("/users"), we don't get the deprecation method, but still get the failure with same error message.
If we additionally wrap in without_partial_double_verification introduced in RSpec 3.6 in May 2017, all is well.
It would save the user a lot of time to provide a nice non-deprecated working-under-default-Rspec example for RSpec stubbing, instead of giving them deprecated/non-working example and making them figure it out.
pic: 8128cca Work and Collection factories default to publisheddd
Description
Detail your changes here.
A few sentences describing the overall goals of the pull request's commits will suffice.
Some questions you might answer:

Why was this change required?
Did you have any tough decisions to make? Which one(s) did you go with and why?
Are there any deployment impacts to this change?
Is there something you aren't happy with or that needs extra attention?

Testing
Outline steps to test your changes.

Go here.
Click this.
See that.

To-Dos

[ ] tests
[ ] documentation

References

GitHub Issue ####
GitHub Pull Request ####

(This is a local working fork, didn't mean to make PR here)


Have to run the pkill command twice to kill kytos foreground process

Original issue opened by @rmotitsuki at https://github.com/kytos/kytos/issues/1236.
When executing kytosd in foreground mode the user must run the command pkill kytosd twice.
It seems that the kytos terminal runs in a different thread and it is not cancelled.

This issue is related to Issue #129 and PR #130. Basically, after applying the PR 130, the issue of having to run pkill twice started happening again.

This issue is related to Issue #129 and PR #130. Basically, after applying the PR 130, the issue of having to run pkill twice started happening again.

If we revert the PR 130, Kytosd in foreground we not provide the controller variable and also it will still not stop after the first Kill. Here is an execution example using the latest docker image (amlight/kytos:latest - 41434b0afd9b):
# Terminal 1
root@90aee3fe58e8:/# kytosd -f
Web update - Web UI was not updated

      _          _
     | |        | |
     | | ___   _| |_ ___  ___
     | |/ / | | | __/ _ \/ __|
     |   <| |_| | || (_) \__ \
     |_|\_\__,  |\__\___/|___/
            __/ |
           |___/

    Welcome to Kytos SDN Platform!

    We are making a huge effort to make sure that this console will work fine
    but for now it's still experimental.

    Kytos website.: https://kytos.io/
    Documentation.: https://docs.kytos.io/
    OF Address....: tcp://<IP_ADDRESS>:6653
    WEB UI........: http://<IP_ADDRESS>:8181/
    Kytos Version.: 2022.1rc1

 * Serving Flask app "kytos.core.controller" (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
kytos $> controller
---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
/usr/lib/python3.9/concurrent/futures/thread.py in <module>
----> 1 controller

NameError: name 'controller' is not defined

kytos $>

# Terminal 2:
root@90aee3fe58e8:/# pkill kytosd && sleep 5 && ps aux | grep kytos
root@90aee3fe58e8:/# ps aux | grep kytos
root       165  3.7  2.0<PHONE_NUMBER>0 pts/0    Sl+  00:47   0:02 /usr/bin/python3 /usr/local/bin/kytosd -f
root       200  0.0  0.0   3176   660 pts/1    S+   00:48   0:00 grep kytos

# Terminal 1 (I've just pressed ENTER):
kytos $>
Stopping Kytos daemon... Bye, see you!

So, in the above example, Kytos' console keeps waiting on an additional ENTER to finishes.

The following patch seems to close the console when the first pkill is received. However, it leaves the terminal in an inconsistent state (you have to run reset)
--- /usr/local/lib/python3.9/dist-packages/kytos/core/kytosd.py.orig	2022-01-19 10:04:27.000000000 +0000
+++ /usr/local/lib/python3.9/dist-packages/kytos/core/kytosd.py	2022-01-20 18:16:11.898125016 +0000
@@ -35,7 +35,7 @@
         os.chmod(pid_dir, 0o1777)  # permissions like /tmp

-def start_shell(controller=None):
+def create_shell(controller=None):
     """Load Kytos interactive shell."""
     kytos_ascii = r"""
       _          _
@@ -82,9 +82,10 @@

     ipshell = InteractiveShellEmbed(config=cfg,
                                     banner1=banner1,
-                                    exit_msg=exit_msg)
+                                    exit_msg=exit_msg,
+                                    user_ns={'controller': controller})
     ipshell.prompts = KytosPrompt(ipshell)
-    ipshell()
+    return ipshell

 # def disable_threadpool_exit():
@@ -129,12 +130,15 @@

     async def start_shell_async():
         """Run the shell inside a thread and stop controller when done."""
-        _start_shell = functools.partial(start_shell, controller)
+        interactive_shell = create_shell(controller)

         try:
-            data = await loop.run_in_executor(executor, _start_shell)
+            data = await loop.run_in_executor(executor, interactive_shell)
         finally:
+            # Exit all embedded code in shell
             stop_controller(controller)
+            interactive_shell.magic("%kill_embedded -x -y")
+            interactive_shell.pt_loop.stop()
         return data

     loop = asyncio.get_event_loop()

Maybe we could send a signal to the interactive shell to represent Ctrl-D.

The following patch seems to close the console when the first pkill is received. However, it leaves the running shell in an inconsistent state (you have to run reset)
--- /usr/local/lib/python3.9/dist-packages/kytos/core/kytosd.py.orig	2022-01-19 10:04:27.000000000 +0000
+++ /usr/local/lib/python3.9/dist-packages/kytos/core/kytosd.py	2022-01-20 18:16:11.898125016 +0000
@@ -35,7 +35,7 @@
         os.chmod(pid_dir, 0o1777)  # permissions like /tmp

-def start_shell(controller=None):
+def create_shell(controller=None):
     """Load Kytos interactive shell."""
     kytos_ascii = r"""
       _          _
@@ -82,9 +82,10 @@

     ipshell = InteractiveShellEmbed(config=cfg,
                                     banner1=banner1,
-                                    exit_msg=exit_msg)
+                                    exit_msg=exit_msg,
+                                    user_ns={'controller': controller})
     ipshell.prompts = KytosPrompt(ipshell)
-    ipshell()
+    return ipshell

 # def disable_threadpool_exit():
@@ -129,12 +130,15 @@

     async def start_shell_async():
         """Run the shell inside a thread and stop controller when done."""
-        _start_shell = functools.partial(start_shell, controller)
+        interactive_shell = create_shell(controller)

         try:
-            data = await loop.run_in_executor(executor, _start_shell)
+            data = await loop.run_in_executor(executor, interactive_shell)
         finally:
+            # Exit all embedded code in shell
+            interactive_shell.magic("%kill_embedded -x -y")
+            interactive_shell.pt_loop.stop()
             stop_controller(controller)
         return data

     loop = asyncio.get_event_loop()

Maybe we could send a signal to the interactive shell to represent Ctrl-D.

Does this patch fixes the issue with the controller variable being unavailable? Without it the console is almost useless.

Does this patch fixes the issue with the controller variable being unavailable? Without it the console is almost useless.

Yes, it does. The exact part that makes the controller variable available is using the additional parameter user_ns={'controller': controller}  into the InteractiveShellEmbed instantiation.
For the error in closing the console, the following code should take care of it:
+            interactive_shell.magic("%kill_embedded -x -y")
+            interactive_shell.pt_loop.stop()

However, as soon as you quit Kytos, the Linux console becomes useless (i.e., the terminal encoding becomes inconsistent somehow and you cannot type any other command). To fix this, you can run the command reset in the Linux console.
I believe that sending a CTRL+D could work well, but I didn't find an easy way of doing that.


Speech: Queuing messages for text-to-speech

Reference: https://github.com/Microsoft/BotFramework-WebChat/issues/1714
Customer had an issue where text-to-speech has been cutting out on Web Chat. To quote the conclusion:

So when the "additional questions" type message gets into the channel it interrupts the reading task to focus on the new task.
A workaround for now is to stop using "additional questions" type messages.
On the other hand it would be great if the webchat.js could queue messages to read in queued fashion.

(emphasis mine)
Queuing messages would prevent the bot from 'cutting out' and interrupting whatever current utterance is being made. Is queuing messages to prevent interruption of speech something we want to support in the near future? @compulim in particular has done the most work with Speech recently and may have thoughts on the matter.

We tested on Mockbot that the new incoming activity did not interrupt the current speaking activity. However, the new incoming activity is not spoken too.
Repro steps

Go to webchat-playground
Click the microphone button
Say "proactive"
The bot should come back in 2 batches of activity

The second batch come in when the first batch is being spoken

Expected
The second activity will be spoken immediately following the completion of the first activity. The second activity will not interrupt the first activity.
Actual
The second activity did not interrupt the speaking of the first activity. However, the second activity is not spoken either.

We START_DICTATE immediately after the first MARK_ACTIVITY completed. Looks like something wrong with startDictateAfterSpeakActivitySaga.js.

I believe this issue is the one we've hit with testing, here are some examples to help validate the change:
•	If one response is sent back WebChat appears to perform TTS reliably, eg:

•	If two responses are sent back WebChat fails to perform TTS on anything (despite Speak properties being set). Occasionally it will play the last message, sometimes truncated. Other times nothing is heard. I suspect the first is being played, the second comes in and does not wait until the first is completed. Due to the race condition it’s luck of the drawer if you hear anything.

•	This I believe is another example of “two responses” – “I found the following” and then a carousel of adaptive cards. Speak properties are set on both yet nothing is heard.

@ryanlengel can let you internally have a pointer to a bot so you can validate the change.

How to stop the bot from speaking and clear all the queues? This was available in v3 as we could reset the queue. in v4, the queue seems empty and this functionality seems missing.
This is not a how-to question, this is a missing functionality in v4.

@alokraj68, this is feature work done with the Cognitive Service team for 4.6, which is when we will bump the dependency in Web Chat. This is not yet testable in our latest bits but will be released at the beginning of November.

Please do let me know once it's in the latest bits so that we can test it.


Cleanup: make Endpoint.GetSecurityIdentity() lock-free

Make Endpoint.GetSecurityIdentity() lock-free
Fixes: #35907
Cleanup: make Endpoint.GetSecurityIdentity() lock-free

The issue that this PR purports to fix specifically outlines using an atomic.Pointer instead of the lock. We can't remove the lock without safeguarding preemption in another way.

Can I set the SecurityIdentity atomic.Pointer[identity.identity] in endpoint struct and then make changes along with it?

@joestringer @nathanjsweet Mass changes. I know it's a bit noisy to review, but please.


Make images in one sheet retina

I'm going to hold off on this
ᐧ
—
Sent from my mobile–apologies for brevity and any typos!
jonl.org |<PHONE_NUMBER>
On Tue, Feb 10, 2015 at 10:51 AM, Zach Latta<EMAIL_ADDRESS>wrote:

Assigned #16 https://github.com/hackedu/docs/issues/16 to @jonleung
https://github.com/jonleung.
—
Reply to this email directly or view it on GitHub
https://github.com/hackedu/docs/issues/16#event-233430766.

@MaxWofford can you take lead on this?

Yes. I'll make the changes.

<3
Sent from my iPhone

On Mar 10, 2015, at 10:13 PM, Max Wofford<EMAIL_ADDRESS>wrote:
Yes. I'll make the changes.
—
Reply to this email directly or view it on GitHub.

@MaxWofford what's the status on this?

@zachlatta I can :shipit: when I get back in SF on the 9th.

@zachlatta, I'm going to close this issue because it is not priority, please reopen if you feel otherwise

Let's leave open because it's an active issue with activity and @MaxWofford said he'll take care of it on the 9th.

Closing this because it is not high leverage right now.


Change overlay height for Twitter

Fixes #6

Looks good. Are the changes to dist/blueprint.css manual or a result of compilation?

Compilation haha
Will it happen after every change?


[SPARK-32024][WEBUI][FOLLOWUP][3.0] Quick fix on test failure on missing when statements

What changes were proposed in this pull request?
This patch fixes the test failure due to the missing when statements for destination path. Note that it didn't fail on master branch, because 245aee9 got rid of size call in destination path, but still good to not depend on 245aee9.
Why are the changes needed?
The build against branch-3.0 / branch-2.4 starts to fail after merging SPARK-32024 (#28859) and this patch will fix it.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Ran modified UT against master / branch-3.0 / branch-2.4.

cc. @dongjoon-hyun @gengliangwang @zhli1142015

Test build #125414 has started for PR 29047 at commit 6a36c9c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/30025/
Test PASSed.

Thank you!

Test build #125414 has finished for PR 29047 at commit 6a36c9c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/125414/
Test FAILed.

There was no conflict. I just merged #29046 through.


Make sure the maxATAC python package can be installed on python 3.7/3.8/3.9 on both Ubuntu and macOS

maxATAC python package should be easily installed with all required dependencies on Ubuntu 18.04/20.04 and macOS with pre-installed python 3.7/3.8/3.9.
The task is finished, when:

we can run maxatac --help command for any Python/OS combination with exit code 0
we have a test for it and proper documentation

This will require:

[x] Define the list of working dependencies for each python version. The list of working and tested dependencies should be saved in the same GitHub repo. When installing with pip, they will be provided through --constraint argument.
[x] Find a solution for installing not python dependencies if they are also required (bedtools, samtools, etc).
[ ] Make automatic tests for running the installation on every Python/OS combination. Here I can help because I've already implemented a similar thing here https://github.com/Barski-lab/cwl-airflow/blob/master/tests/run_conformance_tests_docker.sh

@michael-kotliar Do you have any experience setting up CI and upload to pypi?


[FEATURE] Create helper integration tests

This is for: https://github.com/ember-cli/ember-cli/issues/4517 and is paired with https://github.com/emberjs/ember.js/pull/13371
Note: I have not yet made integration tests default. I think it might be a good idea to do that in a followup PR once we know all is well and working?

Thank you!

Thanks for reviewing, @rwjblue.


Using force reply/creating step by step flows

I can't seem to get forceReply to work :/
bot.command('CommandName', (msg, reply) => {
	const { id } = msg.user;
	reply
		.keyboard([['Option1','Option2']])
		.forceReply() //Tried force() | force_reply() | forceReply(true)
		.text(`Would you like option 1 or 2?`)
});

bot.text(function (msg, reply) {
	console.log(msg);
	console.log(msg.reply); //Get undefined, no matter what variation I try
	reply.text(`Bot replying to a forced reply...`);
});

I must be doing something obviously wrong. Does anyone have any pointers?
Or is there any other way to create a step by step conversation flow (where I can hold conversation state between back and forth messages?)

Ps - Cheers for the easy to use library!
Edit - Added javascript in markdown

Ok so, reading the docs, I came across: https://core.telegram.org/bots/api#sendmessage where it mentions the keyboard and force reply clash.
Then tried some adjusted code where the keyboard is removed beforehand...
bot.callback((query, next)=>{
	if (query.data === 'Matched string') {
		const { id } = query.message.user;
		const reply = bot.reply(id);
		reply.keyboard();
		reply.text('What is the reply to this message?').forceReply();
	} else {
		return next()
	}
});

Still no luck. I suspect it may be because you can only send a single 'reply' via the bot callback (because sending a query.answer after a reply also throws an error). Hmmm...

ForceReply is intended for groups. Bots that have privacy mode enabled won't be able to see simple text messages (i.e. «Option1») unless those messages are a reply for the bot. By forcing a reply, you ensure the bot will get the message.
That's probably why ForceReply only works on groups. If you're in a direct chat, forcing a reply is pointless since you'll get the text, whether you use it or not.
So, your initial snippet works as expected on a group (screenshot of Telegram Desktop):

Note: The const { id } = msg.user; line crashes on a group, you should use msg.chat or msg.from unless you're sure it's a user.
Note: Remember to remove the keyboard when it's no longer needed by doing .keyboard(), i.e.:
reply.keyboard().text(`Bot replying to a forced reply...`);

See the hasher.js example for more info.

But all of this is irrelevant for mantaining flow; you don't need ForceReply or anything for that.
For info about maintaining flow, see the end of this section and the hasher.js example. (Note that in a real application, you'd use a DB instead.)

Ah got it, that explains that.
Read and forgot about the whole context object when going through the docs. Poor effort on my part.
It will work perfectly in conjunction with a database.
Cheers @jmendeth !!


4878: Fixed Undesired expansion of HL7 field with type ID

This PR is a follow-on to the latter half of #4793, which has been resolved for the state of WA in PR #4807. When we receive HL7 results from senders, ID fields such as OBR-25, OBX-2, and OBX-11 are expanded from standard ID values (e.g. "F", "CWE") to fully expanded values such as
Test Steps:

./gradlew package
./prime data --input junk/prescryptive-sample1a.hl7 --input-schema HL7/prescryptive-covid-19 --output-dir junk/output --route
Verify the HL7 output file:
OBR-25: Result Status +:                                F
Suppressed OBR-25-2, 3
OBX-2:  Value Type:                                        CWE
Suppressed OBX-2-2, 3
OBX-11: Observation Result Status:               F
Suppressed OBX-11-2, 3

Test File:
prescryptive-sample1a.txt
Changes

Include a comprehensive list of changes in this PR
(For web UI changes) Include screenshots/video of changes

Checklist
Testing

[X] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Fixes

#issue - List GitHub issues this PR fixes
https://app.zenhub.com/workspaces/onboarding--operations-6166edbd409257001e09f1b2/issues/cdcgov/prime-reportstream/4878

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Pull reviewers stats
Stats for the last 30 days:

User
Total reviews
Median time to review
Total comments

carlosfelix2
24
3h 38m
65

MauriceReeves-usds
23
1h 54m
12

whytheplatypus
16
18h 25m
23

jimduff-usds
15
4h 29m
9

kevinhaube
12
50m
9

cwinters-usds
11
1h 46m
5

jorg3lopez
10
1h 19m
5

TomNUSDS
10
44m
46

TurkeyFried
9
1h 26m
2

ahay-agile6
9
1h 7m
0

jbiskie
9
1h 2m
3

sethdarragile6
9
3h 4m
2

clediggins-usds
8
16m
0

oslynn
6
37m
1

brick-green-agile6
6
2h 15m
5

rhood23699
4
1d 15h 28m
0

bgantick
3
2h 27m
3

snesm
3
22h 43m
0

JosiahSiegel
2
43m
0

acoushawk
2
39m
0

meckila
2
8h 26m
9

jh765
2
10h 42m
4

jeremy-page
1
18h 23m
0

OBX-2 is fixed with ticket 4990 by changing value_type.type: from CODE to ID.


changing ZEIT to Vercel

Issue #33 : ZEIT has rebranded as Vercel
This PR should ideally not be merged until sure that nothing will be broken (that could take a while)

Let's go ahead and also change any code that needs to change as well. That includes package.json

Let's go ahead and also change any code that needs to change as well. That includes package.json

package.json is done.
Will tackle the rest now

package.json is done.
Will tackle the rest now

What exactly is the purpose of Cargo.toml in the project? I'm not sure I quite understand.
Shouldn't it have the information of the project - vercel-rust (prev. now-rust) instead of now-lambda?

What exactly is the purpose of Cargo.toml in the project? I'm not sure I quite understand.
Shouldn't it have the information of the project - vercel-rust (prev. now-rust) instead of now-lambda?

What exactly is the purpose of Cargo.toml in the project? I'm not sure I quite understand.
Shouldn't it have the information of the project - vercel-rust (prev. now-rust) instead of now-lambda?

Good question! There is actually a crate published from this repo, which folks should use in their rust code. I'll have to update that as well once I switch everything over

What exactly is the purpose of Cargo.toml in the project? I'm not sure I quite understand.
Shouldn't it have the information of the project - vercel-rust (prev. now-rust) instead of now-lambda?

Good question! There is actually a crate published from this repo, which folks should use in their rust code. I'll have to update that as well once I switch everything over

So is the final goal to make the crate resemble the npm package?

So is the final goal to make the crate resemble the npm package?

In name, yes. In functionality, no. now_lambda acts as a rust component to the entire vercel-rust system, which adds some extra functions and types to allow rust code to run well on vercel

In name, yes. In functionality, no. now_lambda acts as a rust component to the entire vercel-rust system, which adds some extra functions and types to allow rust code to run well on vercel

Ah I see

Ah I see


intentions written into little popup window do not go into list

I write an intention into the window and hit enter, and they do not transfer into the list anywhere. If I write the intention in the list on the list window, then they show up.

This is … sort of intentional.  The UI is pretty bad here, but it sometimes pops up an NSUserNotification to tell you that you were too late to set the intention, or an intention isn't running.  The only time the pop-up box actually enters the intention for you, is if you happen to set it in the first 4 minutes.
I am going to leave this open because I wouldn't refuse a PR to improve this, but in the nexus model ( #33 ) this will be addressed by the fact that the entire UI centers around putting into your intentions into a list, and the popup will be a prompt to select from the top of that list.


fix xpath and delete unnecesary req.txt

There are issues on scraping number of cases and install pkg-resources==0.0.0 on requirements.txt

Fixes #1


Updated npm dependencies

Addresses https://github.com/aspnet/AspNetCore/issues/13533

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=372349

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/3163
https://github.com/aspnet/AspNetCore-Internal/issues/2996

@mkArtakMSFT this will only update the transient dependencies that use floating versions. Is that intended or were you trying to update for a specific reason? Not a lot of context in the linked issue.

Just to avoid using vulnerable dependencies


MIC-427: E2E Tests for remaining referral pages (minus CYA)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 63.19%. Comparing base (e389ab0) to head (fa077d4).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #149      +/-   ##
==========================================
- Coverage   66.09%   63.19%   -2.90%
==========================================
  Files         166      166
  Lines        2315     2315
  Branches      377      377
==========================================
- Hits         1530     1463      -67
- Misses        754      815      +61
- Partials       31       37       +6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


be sure that the URL entered for the BackupStorageLocation starts with http:// or https://

We need to be sure that the URL entered for the BackupStorageLocation starts with http:// or https://
See: https://github.com/fusor/mig-controller/issues/269

We have a URL validation for cluster and backup storage urls. I'll have to make sure it's handling this (seems like it isn't).


Fix Parser plugin template for fluent-plugin-generate

In Parser plugin template for fluent-plugin-generate, parse method definition is in Fluent::Plugin module.
I think it should be in Fluent::Plugin::<class_name> class.

Thanks!


Add automatic architecture selection by default in the build stage.

The ${TARGETPLATFORM} is available for automatic architecture selection, which can be used for conda installation, etc. This should be the default for better support of ARM64 architectures, e.g., AWS Graviton CPUs.

This is probably best done by specifying the conda installation URL in the docker-compose.yaml file instead of inside the Dockerfile.

Use uname -m to get the architecture.


CI: Bump Node version to latest LTS

Seeing the following error in the CI build for #304
=== Building HelloLog for the web browser backend ===
/home/runner/work/purescript-cookbook/purescript-cookbook/node_modules/@parcel/utils/lib/index.js:37573
    #getIndex(item) {
             ^

SyntaxError: Unexpected token '('

#getIndex is using relatively new private class field syntax. According to MDN, that should be valid in Node v12 so I'm not sure why this is failing with a syntax error. Trying to bump to v18 to see if that helps.

I'll go ahead and merge this, just a version bump that appears to fix CI following a breaking change in parcel


[Snyk] Security upgrade org.apache.jena:jena-fuseki-main from 4.9.0-SNAPSHOT to 5.0.0

Snyk has created this PR to fix 5 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

jena-fuseki2/jena-fuseki-geosparql/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

Denial of Service (DoS) SNYK-JAVA-ORGECLIPSEJETTY-8186142
  112
org.apache.jena:jena-fuseki-main:  4.9.0-SNAPSHOT -> 5.0.0  No Known Exploit

Improper Validation of Syntactic Correctness of Input SNYK-JAVA-ORGECLIPSEJETTY-8186141
  62
org.apache.jena:jena-fuseki-main:  4.9.0-SNAPSHOT -> 5.0.0  Proof of Concept

Improper Validation of Syntactic Correctness of Input SNYK-JAVA-ORGECLIPSEJETTY-8186158
  62
org.apache.jena:jena-fuseki-main:  4.9.0-SNAPSHOT -> 5.0.0  Proof of Concept

Denial of Service (DoS) SNYK-JAVA-ORGECLIPSEJETTY-8186168
  50
org.apache.jena:jena-fuseki-main:  4.9.0-SNAPSHOT -> 5.0.0  No Known Exploit

Denial of Service (DoS) SNYK-JAVA-ORGECLIPSEJETTY-8186167
  40
org.apache.jena:jena-fuseki-main:  4.9.0-SNAPSHOT -> 5.0.0  No Known Exploit

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

Checkmarx One – Scan Summary & Details – be257b0b-bf50-42a8-bd3f-56f75f8dcb32
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2022-46337
Maven-org.apache.derby:derby-<IP_ADDRESS>
Vulnerable Package

CVE-2023-36478
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-43646
Npm-get-func-name-2.0.0
Vulnerable Package

CVE-2023-45133
<EMAIL_ADDRESS>Vulnerable Package

CVE-2024-23331
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-37890
Npm-ws-8.12.0
Vulnerable Package

CVE-2024-4068
Npm-braces-3.0.2
Vulnerable Package

CVE-2024-45296
Npm-path-to-regexp-0.1.7
Vulnerable Package

CVE-2024-45296
Npm-path-to-regexp-1.8.0
Vulnerable Package

CVE-2024-45590
Npm-body-parser-1.20.1
Vulnerable Package

CVE-2024-45801
Npm-dompurify-2.4.3
Vulnerable Package

CVE-2024-47554
Maven-commons-io:commons-io-2.11.0
Vulnerable Package

CVE-2024-47875
Npm-dompurify-2.4.3
Vulnerable Package

CVE-2024-7254
Maven-com.google.protobuf:protobuf-java-3.23.2
Vulnerable Package

CVE-2022-29622
Npm-formidable-1.2.6
Vulnerable Package

CVE-2023-26159
Npm-follow-redirects-1.15.2
Vulnerable Package

CVE-2023-28155
<EMAIL_ADDRESS>Vulnerable Package

CVE-2023-36479
Maven-org.eclipse.jetty:jetty-servlets-10.0.15
Vulnerable Package

CVE-2023-40167
Maven-org.eclipse.jetty:jetty-http-10.0.15
Vulnerable Package

CVE-2023-42503
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.4.21
Vulnerable Package

CVE-2023-45857
Npm-axios-0.27.2
Vulnerable Package

CVE-2023-46749
Maven-org.apache.shiro:shiro-web-1.11.0
Vulnerable Package

CVE-2023-46750
Maven-org.apache.shiro:shiro-web-1.11.0
Vulnerable Package

CVE-2024-25710
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2024-26308
Maven-org.apache.commons:commons-compress-1.23.0
Vulnerable Package

CVE-2024-28849
Npm-follow-redirects-1.15.2
Vulnerable Package

CVE-2024-29041
Npm-express-4.18.2
Vulnerable Package

CVE-2024-31207
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-34343
Npm-ufo-1.0.1
Vulnerable Package

CVE-2024-4067
Npm-micromatch-4.0.5
Vulnerable Package

CVE-2024-43796
Npm-express-4.18.2
Vulnerable Package

CVE-2024-43799
Npm-send-0.18.0
Vulnerable Package

CVE-2024-43800
Npm-serve-static-1.15.0
Vulnerable Package

CVE-2024-45811
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-45812
Npm-vite-4.0.4
Vulnerable Package

CVE-2024-47068
Npm-rollup-3.11.0
Vulnerable Package

CVE-2024-47764
Npm-cookie-0.5.0
Vulnerable Package

CVE-2024-6531
Npm-bootstrap-5.2.3
Vulnerable Package

Cx14b19a02-387a
Npm-body-parser-1.20.1
Vulnerable Package

Use_of_Cryptographically_Weak_PRNG
/jena-arq/src/main/java/org/apache/jena/sparql/expr/E_Random.java: 34
Attack Vector

Fixed Issues

Severity
Issue
Source File / Package

CVE-2022-38900
Npm-decode-uri-component-0.2.2

CVE-2007-2379
Npm-jquery-3.6.3

CVE-2014-6071
Npm-jquery-3.6.3

Host Namespace is Shared
/docker-compose.yaml: 20

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 35

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 39

Improper_Restriction_of_Stored_XXE_Ref
/jena-iri/src/main/java/org/apache/jena/iri/impl/BuildViolationCodes.java: 38

Networks Not Set
/docker-compose.yaml: 20


Doesn't work

Broken.
I can trigger the fileChooser but when i select a file, it crashes.
So am i right to consider this plugin deprecated ? I really would like to be wrong.
Android 4.3

I tested this on android 4.4.4 and android 5.x. It worked on those versions.

Hi,
I also have so available android 4.4.2 and Android Lollipop to test a filepicker.
For both of these version, a simple  works !
Still have struggle with Android version under 4.4. Thanks anyway :)

I tested on android 5.0 and no window open. No error too :)


Placing bids

I'm using place_buy_order and giving it there third argument which is bid price. It's not placing the order and waiting for that price. How do I do that?

Same problem. Created https://github.com/Jamonek/Robinhood/pull/98/commits/454bf18cb5435c07f77b96266b604107c5dac562 to fix it.


New Demucs release coming up

Hello @xserrat , on the 12th of November I will release a new version of Demucs. This should only require minor command line changes :) I'll submit a PR soon but wanted to give you a heads up.

The release just happened. I think though that the docker file should still be compatible out of the box.

@adefossez With the removal of the --models flag in Demucs v3, it is not compatible out of the box. This is because the Dockerfile stores the models in the /data/models Docker volume using the flag.
I have cooked up a temp working version and will submit a PR in case it is of use to anyone =)

Hi @adefossez , thank you so much for your concern regarding the compatibility. This is great news!! I'm going to try it as soon as possible and I let you know.

The release just happened. I think though that the docker file should still be compatible out of the box.

Hi @jaolan , thanks for your contribution. Your pull requests are welcomed so feel free to submit them! :) I'm going to check this issue as well!

The release just happened. I think though that the docker file should still be compatible out of the box.

Hi @adefossez , thank you so much for your concern regarding the compatibility. This is great news!! I'm going to try it as soon as possible and I let you know.

@adefossez With the removal of the --models flag in Demucs v3, it is not compatible out of the box but it is a simple fix. This is because the Dockerfile stores the models in the /data/models Docker volume using the flag.
I have cooked up a temp working version and will submit a PR in case it is of use to anyone =)

Hi @jaolan , thanks for your contribution. Your pull requests are welcomed so feel free to submit them! :) I'm going to check this issue as well!

Hey @xserrat with latest build I'm getting this error:
...
 => exporting to image                                                                                33.6s
 => => exporting layers                                                                                33.6s
 => => writing image sha256:f82cd9f65e54a9bdeeb2c29784c59380b774974334d42129c3d8aabe8f60a40f                                                                      0.0s
 => => naming to docker.io/facebook/demucs:latest                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
docker run --rm -i \
		--name=demucs \
		-v /Users/loretoparisi/Documents/Projects/demucs/input:/data/input \
		-v /Users/loretoparisi/Documents/Projects/demucs/output:/data/output \
		-v /Users/loretoparisi/Documents/Projects/demucs/models:/data/models \
		facebook/demucs:latest \
		"python3 -m demucs.separate --out /data/output --models /data/models \
		/data/input//root/audio/82929740.mp3"
usage: demucs.separate [-h] [-s SIG | -n NAME] [--repo REPO] [-v] [-o OUT]
                       [-d DEVICE] [--shifts SHIFTS] [--overlap OVERLAP]
                       [--no-split] [--mp3] [--mp3-bitrate MP3_BITRATE]
                       tracks [tracks ...]
demucs.separate: error: unrecognized arguments: --models
make: *** [run] Error 2

Yes ! I think a simple fix is to replace prepend the Demucs command with "$TORCH_HOME=/data/models". I can make a pull request tomorrow.

Sent a PR!


ApplicationGatewaySubnetInboundTrafficBlockedByNetworkSecurityGroup on repeated deployments

Describe the bug
I use the aks construction set from a module and when I deploy it the first time, it's all fine. When I don't change anything and deploy it again, it fails with this error:
{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "ApplicationGatewaySubnetInboundTrafficBlockedByNetworkSecurityGroup",
      "message": "Network security group /subscriptions/8b25cfae-660b-4066-9ce5-0858e9ab3eac/resourceGroups/test-raro-us/providers/Microsoft.Network/networkSecurityGroups/nsg-agw-nprd-euw-jk67 blocks incoming internet traffic on ports 65200 - 65535 to subnet /subscriptions/8b25cfae-660b-4066-9ce5-0858e9ab3eac/resourceGroups/test-raro-us/providers/Microsoft.Network/virtualNetworks/vnet-nprd-euw-jk67/subnets/appgw-sn, associated with Application Gateway /subscriptions/8b25cfae-660b-4066-9ce5-0858e9ab3eac/resourceGroups/test-raro-us/providers/Microsoft.Network/applicationGateways/agw-nprd-euw-jk67. This is not permitted for Application Gateways that have V2 Sku."
    }
  ]
}

my aks.bicep that I use to call the aks construction module:
// borrow from: https://github.com/Azure/Aks-Construction
// TODOS:

@description('Unique String for all public names')
@maxLength(4)
@minLength(4)
param salt string = take(uniqueString(resourceGroup().id), 4)

// You should use a bicep file to represent an application deployment
// This "Application Main.Bicep" will then call the AKS Construction module

//------Application General Parameters------

param location string =  resourceGroup().location

@allowed([
  'Production'
  'NonProduction'
])
@description('The performance/size spec of the generated resources')
param environmentScale string = 'NonProduction'

//------------------NAMING-----------------
//- As per CAF naming standards: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming
//Example generated names will be : sql-app-nprd-euw-001, aks-app-nprd-euw-001, log-app-nprd-euw-001

@description('Short name to use for environment resource name')
param environmentName string = 'nprd'

@description('Instance or other differentiator for resource deployment')
param namesuffix string = salt

@description('This json file is used to convert a long location name (eg. UK South) to its short version (eg. UKS)')
var shortLocationNames = json(loadTextContent('./shortLocationNames.json'))

@description('Maps the long name to the short name')
var shortLocationName = '${shortLocationNames[location]}'

@description('Creates a full resource name seed.')
var fullnameseed = '${environmentName}-${shortLocationName}-${namesuffix}'

@description('Should Private Links be created.')
param privateLinks bool = false

//--------------ENVIRONMENT-------------
var environmentConfigurationMap = {
  Production: {
    aks: {
      availabilityZones: [
        '1'
        '2'
        '3'
      ]
      AksPaidSkuForSLA: true
      JustUseSystemPool: false
      privateCluster: true
      networkPolicy: 'azure'
      agentCount:6
      agentCountMax:12
      agentVMSize: 'Standard_D8s_v4'
    }
  }
  NonProduction: {
    aks: {
      availabilityZones: []
      AksPaidSkuForSLA: false
      JustUseSystemPool: true
      privateCluster: false
      agentCount:1
      agentCountMax:3
      networkPolicy: 'azure'
      agentVMSize: 'Standard_DS3_v2'
    }
  }
}

//---------Kubernetes Construction---------
//ref: https://github.com/Azure/Aks-Construction
param k8sVersion string = '1.22.4'

module aksconst './aks-construction/main.bicep' = {
  name: 'aksconstruction'
  params: {
    location : location
    AksDisableLocalAccounts: true
    upgradeChannel: 'stable'
    resourceName: fullnameseed
    kubernetesVersion: k8sVersion
    enablePrivateCluster :  environmentConfigurationMap[environmentScale].aks.privateCluster
    agentCount: environmentConfigurationMap[environmentScale].aks.agentCount
    agentVMSize: environmentConfigurationMap[environmentScale].aks.agentVMSize
    agentCountMax: environmentConfigurationMap[environmentScale].aks.agentCountMax
    enable_aad: true
    enableAzureRBAC : true
    registries_sku: 'Premium' //no acr
    omsagent: true
    retentionInDays: 30
    custom_vnet: true
    ingressApplicationGateway: true
    appGWcount: 0
	  appGWsku: 'WAF_v2'
	  appGWmaxCount: 10
    appgwKVIntegration: true
    azureKeyvaultSecretsProvider: true
    createKV: true
    privateLinks: false // something prevents true from working here,  privateLinks
    networkPolicy: environmentConfigurationMap[environmentScale].aks.networkPolicy
    azurepolicy: 'audit' // no policy, lack of permissions
    availabilityZones: environmentConfigurationMap[environmentScale].aks.availabilityZones
    AksPaidSkuForSLA: environmentConfigurationMap[environmentScale].aks.AksPaidSkuForSLA
    JustUseSystemPool: environmentConfigurationMap[environmentScale].aks.JustUseSystemPool
  }
}

output aksClusterName string = aksconst.outputs.aksClusterName
output ApplicationGatewayName string = aksconst.outputs.ApplicationGatewayName

I use the azure cli to deploy it.
To Reproduce
Steps to reproduce the behavior:

Deploy the AKS Construction with the aforementioned aks.bicep
Deploy it again without changing anything
See error

Expected behavior
I would expect to not get an error and that repeated deployments run fine.

Reproduced issue. Will investigate.
az deployment group create -g innerloop -f .\localdebug\testing-issues\nsg-idempotant\main.bicep -n issuetest1
az deployment group what-if -g innerloop -f .\localdebug\testing-issues\nsg-idempotant\main.bicep -n issuetest1

'int' object has no attribute 'append'

az deployment group what-if -g innerloop -f .\localdebug\testing-issues\nsg-idempotant\main.bicep -n issuetest1 --debug

cli.azure.cli.core.azclierror: 'int' object has no attribute 'append'
az_command_data_logger: 'int' object has no attribute 'append'

az deployment group create -g innerloop -f .\localdebug\testing-issues\nsg-idempotant\main.bicep -n issuetest1

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"ApplicationGatewaySubnetInboundTrafficBlockedByNetworkSecurityGroup","message":"Network security group  blocks incoming internet traffic on ports 65200 - 65535 to  associated with Application Gateway. This is not permitted for Application Gateways that have V2 Sku."}]}

This looks like a problem with the Azure Resource Provider, I have raised an issue.
As a short-term workaround, to reduce the impact on Day1 users of this project; I have changed the default parameter value to not deploy the appgw nsg in #207 .
For users who require the NSG, it will have to be created outside the scope of the AKS-Construction codebase.
This does not fix the idempotency issue around the NSG, which should come as part of the issue raised.

Thanks @Gordonby, much appreciated. And now I know where to raise it the next time.

Thanks @Gordonby, much appreciated. And now I know where to raise it the next time.

It's an interesting bug, thanks for finding 👍

I've just tried this again, and can confirm it's still an issue

Fixed with v2.34.1 of the Azure CLI.


docs(semantic): improve doc comments on Reference methods

#6076  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


FastRender.loggingIn()?

It seems using Meteor.loggingIn() to show the loading template until login is complete can cause an infinite loading screen with FastRender (because of how accounts-password manages Meteor.loggingIn().
I wonder if there could be a workaround, or if there is some reactive way to easily check that FastRender has loaded a particular collection that I could use to get past that in cases where FastRender is active.
My loggingIn code in an Iron Router before hook:
  if Meteor.loggingIn()
    console.log 'Logging in...'
    @render(@loadingTemplate)
    @stop()

Hope we've worked on this and fixed the issue,


ESP32 not discoverable by iPhone

Hi,
I am just trying out this library to build a airquality sensor with an esp32. I started out with the EspHap_AirQuality example and adjusted it to use hapwebserver. It connects to my wifi and the website is working. But I can not discover it via iPhone or iPad.
The log states
IP address:
xxx.xxx.xxx.xxx
Free heap: 200448
>>> HomeKit: init_storage_ex size 0x581
>>> Home Integration: hap_services added chararacteristic  0: 00000023-0000-1000-8000-0026BB765291
>>> Home Integration: hap_services added chararacteristic  1: 00000095-0000-1000-8000-0026BB765291
>>> Home Integration: hap_services added chararacteristic  2: 00000093-0000-1000-8000-0026BB765291
>>> Home Integration: homekit_is_paired 0
>>> HomeKit: Starting server
>>> HomeKit: Using existing accessory ID: 45:2D:6A:FD:42:DE
>>> HomeKit: Configuring mDNS
Setting web server
>>> HomeKit: Save saveFileChunked file /index.html
>>> HomeKit: Save saveFileChunked file /setup.html
Web site http://xxx.xxx.xxx.xxx
File system http://xxx.xxx.xxx.xxx/browse
Update http://xxx.xxx.xxx.xxx/update

Afterwards it just outputs the PPM, but is not discoverable by the Home App on the devices. I can see it via mdns browser on chrome.
Many thanks in advance for this awesome library!
Best,
Henrik

Yes, I use the "Add device Manually". And the devices are connected to the same wifi  router and should be in range (xxx.xxx.xxx.224 (ESP32) vs xxx.xxx.xxx.141 (iPhone)). The subnet mask is <IP_ADDRESS>. Don't know if this is a problem.

So when I run dns-sd -Z _hap._tcp local. on my Mac, I get
ES-452D._hap._tcp                               TXT     "sh=lWdLYQ==" "ci=10" "sf=1" "ff=0" "s#=1" "c#=1" "id=45:2D:6A:FD:42:DE" "pv=1.0" "md=EspHapAir"

according to https://stackoverflow.com/questions/49590546/how-does-homekit-find-nearby-devices ff should not be 0.

This is not  case
From HAP specification
”ff” Pairing Feature flags (e.g. ”0x3” for bits 0 and 1). Required if non-zero. See Table 5-4 (page 49).
More thousands devices works on this library with ff=0. Problem is different...
Subnet mask should be OK , Briefly checking broadcast address  <IP_ADDRESS> is allowed for this..
Try to restart Home App

hmm ok. I tried to restart the app, the phone, no luck. how can I check if the broadcast address is allowed for this?

I mean that subnet mask <IP_ADDRESS>  allows to use address  <IP_ADDRESS> (which is broadcast) as local addresses and Apple device should get this response via mDNS
In one enviropment i see similar problem, but device finally appears after 5 min..
Do you have other Apple Homekit devices on your Network working properly ?
As well you can use network sniffer to analyze traffic. Seems that ESP32 working properly... Due you able get right mDNS intoduction.
Try to check another simple example ESPHapLed (for ESP32)
If you are using latest commit for this library ? please check as well

I don't have another homekit device (it is my first try), but other network discovery services (for printer, airplay etc) work fine. I am using the latest commit from master. The ESPHapLed also does not work. Maybe I try a fresh install on a mac later today(i first did not have esphap via git installed).

Ok, keep me informed.  I didn't meet with the similar problem before.  As mentioned with more thousands devices

Small update: I installed homebridge and it finds the sensor rightaway.... I can also add the homebridge via their qr code, but can not discover it via non scanning a code. The connection between iPhone and sensor still seems broken (I can't read out the airquality on the iphone, only in the homebridge UI, but the sensor is listed and saying that it does not respond).

Looks like you have a problem on your network enviropment.  If you have possibility just try another one. For instance setup any new wifi router.
Anyhow the HAP communication is quite simple. End devices introduces theyselfs by mDNS (seems is working on your env),
Means, Apple devices sends multicast query (to port 5353) ,  devices should respond to this query....
And second steps, when devices IP is resolved, communication by HAP protocol uses port 5556 (in case of ESPHap), this  port is not fixed and introduced by mDNS. In case of ESPHap you can change that.
So, no other idea, than you have some closed ports on your router.

Can I make esphap more verbose?

So i made it more verbose.... The homebridge installation obviously contacting the esp32:
[130801][I][server.c:3236] homekit_server_accept_client(): >>> HomeKit: Got new client connection: 57

[130803][I][server.c:2254] homekit_server_on_update_characteristics(): >>> HomeKit: [Client 57] Update Characteristics

[130819][I][server.c:3236] homekit_server_accept_client(): >>> HomeKit: Got new client connection: 58

[130821][I][server.c:2123] homekit_server_on_get_characteristics(): >>> HomeKit: [Client 58] Get Characteristics

[130831][I][server.c:3176] homekit_client_process(): >>> HomeKit: [Client 58] Connection: close received, client will be disconnected

[130840][I][server.c:3190] homekit_server_close_client(): >>> HomeKit: [Client 58] Closing client connection

[132786][I][server.c:3236] homekit_server_accept_client(): >>> HomeKit: Got new client connection: 58

[132788][I][server.c:2051] homekit_server_on_get_accessories(): >>> HomeKit: [Client 58] Get Accessories

[132798][I][server.c:3176] homekit_client_process(): >>> HomeKit: [Client 58] Connection: close received, client will be disconnected

[132805][I][server.c:3190] homekit_server_close_client(): >>> HomeKit: [Client 58] Closing client connection

[132945][I][server.c:3236] homekit_server_accept_client(): >>> HomeKit: Got new client connection: 58

[132948][I][server.c:2123] homekit_server_on_get_characteristics(): >>> HomeKit: [Client 58] Get Characteristics

[132956][I][server.c:3176] homekit_client_process(): >>> HomeKit: [Client 58] Connection: close received, client will be disconnected

[132966][I][server.c:3190] homekit_server_close_client(): >>> HomeKit: [Client 58] Closing client connection

But no entries from my iPhone, even if I scan the code on "/setup.html".

Problem seems to be network related. Works in different environment.