safety action version 2.0.0 is broken

safety version: 2.0.0
Python version: N/A
Operating System: Github Actions

Description
We run the pyupio/safety Github Action as described here: https://docs.pyup.io/docs/github-actions-safety#step-3-configure-your-github-workflow-yaml-file-to-run-safety-scans
That action relies on the latest docker version from safety; however, when said version requires new parameters, the related action is not kept up-to-date, and crashes.
What I Did
We defined the action as:
- uses<EMAIL_ADDRESS>  with:
    api-key: ***
    scan: file
    requirements: requirements.txt

And got the following error:
/app/entrypoint.sh: line 69: SAFETY_ACTION_CREATE_PR: unbound variable

Suggested fix
I think safety should implement one of the following patterns:

Run integration tests, ensuring that past versions of the action don't crash;
Communicate with its customers when old versions of its Github Actions are deprecated and should no longer be used;
Provide a clear error message when the Docker container fails on invalid error message (e.g. "Please update to<EMAIL_ADDRESS>
Thanks!

Hi @rbarrois, thank you for the detailed report!
You are right; I updated the image with a fix to handle the old versions of the GitHub action.

Run integration tests, ensuring that past versions of the action don't crash;

I implemented regression tests, so we can monitor if new features will break the old versions of the GitHub action.

Communicate with its customers when old versions of its Github Actions are deprecated and should no longer be used;

I communicated this to our internal team.

Provide a clear error message when the Docker container fails on invalid error message (e.g. "Please update to<EMAIL_ADDRESS>
Working on this too, it's in the roadmap.
This issue should be fixed, please let me know if all is good from your side and I'll close this issue. Happy to help!

@rbarrois, I'm closing this; feel free to open a new one if you find something still isn't working fine.
Thank you for the issue report!


Add events

Events
This issue covers the events that are a part of  groups.
This is in the project description:
A user belonging to the group can also create an event, making it available for the other group users. An event should have:

    Title
    Description
    Day/Time
    2 Options (at least):
        Going
        Not going

After creating the event every user can choose one of the options for the event.

And here are the audit questions:
Try to create an event in a group.

* Were you asked for a title, a description, a day/time and at least two options (going, not going)?

* Using the same browsers and the same users, after both of them becoming part of the same group, create an event with one of them.

* Is the other user able to see the event and vote in which option he wants?

Events are essentially to groups, what comments are to posts.
Backend:

[ ]  events table must be created:

title, description, time_and_date (when event will take place) and timestamp (when event was created)
creator_id will be a foreign key to users, and group_id will be a foreign key to groups.

[ ] event_members must be created:

event_id references events primary key id,
user_id references users, timestamp is also needed

[ ] Some new endpoints are needed:

POST /api/groups/id/events/create: Simple, creates the event. Returns the event id or the event as json
Request Body:

type SafeEvent struct {
	Title       string `json:"title"`
	Description string `json:"description"`
	TimeAndDate string `json:"time_and_date"`
}

GET /api/groups/id/events/id: returns  the event as json

Response:
{
id: number
group_id: number
created_by: number
title: string
description: string
time_and_date: string
timestamp: string
}

For events design I see two options:
Option 1 (slower but more engaging):

GET /api/groups/id/event/id/members:  returns a list of members, sorted alphabetically. Enables you to display who is going with the:

GET /api/groups/id/event/id/going endpoint

Option 2 (fast but boring):
Include going/not going in the /api/groups/event/id response as a bool, it would be easier and faster to do. But you would not be able to see other people who are going.
They respond in the same way as with every invite with the /api/invitations/id/respond endpoint.
Frontend:
Here you both know what's better. But a button that opens a form inside the groups makes sense. And be able to accept the invite to the event on notification bell, and in the group. Maybe a section to display ongoing events. And you can just move events that have expired after the time_and_date.

This issue covers the events that are a part of  groups.
This is in the project description:
A user belonging to the group can also create an event, making it available for the other group users. An event should have:

    Title
    Description
    Day/Time
    2 Options (at least):
        Going
        Not going

After creating the event every user can choose one of the options for the event.

And here are the audit questions:
Try to create an event in a group.

* Were you asked for a title, a description, a day/time and at least two options (going, not going)?

* Using the same browsers and the same users, after both of them becoming part of the same group, create an event with one of them.

* Is the other user able to see the event and vote in which option he wants?

Backend:
A new events table must be created:
title, description, timestamp works just like in posts.
creator_id will be a foreign key to users, and group_id will be a foreign key to groups.
event_members must be created. event_id references events, user_id references users, timestamp is also needed

FYI - I am only going to add these two endpoint:
GET /api/groups/id/events/id: returns the event as json
GET /api/groups/id/event/id/going: returns a list of members, sorted alphabetically. Enables you to display who is going.


customize ringing tone

Hello again,
please how do i set a customized ringing tone for this package?
i don't seem to get it right

please check prop ringtonePath

perfect... working smothly


Add FlatLaf Themes to Demo

Add the same themes selection from the FlatLaf demo to the ModernDocking demo.

The demo now has 4 themes, selectable from a Themes panel displayed on the right in the default layout.
Current themes are:
FlatLaf Light
FlatLaf Dark
Github Dark
Solarized Dark
I picked these mostly at random. The eventual plan is to expand this to everything available in the FlatLaf demo.


statusBarStyleGetter not available for syncStatusBar textOnly

statusBarStyleGetter is excluded when using syncStatusBar with 'textOnly'. Shouldnt it be like != false?
https://github.com/aparajita/capacitor-dark-mode/blob/6b3c158cbfc98c3e653ccb4af744a91c6016553e/src/base.ts#L227C7-L227C7

Something like this works for me:
if (this.syncStatusBar && Capacitor.getPlatform() === 'android') {
  setStatusBarStyle = true

  if (
    typeof this.syncStatusBar === 'boolean' ||
    this.syncStatusBar === 'textOnly'
  ) {
    if (this.syncStatusBar !== 'textOnly') {
      color = this.getBackgroundColor()
    }

    if (this.statusBarStyleGetter) {
      const style = await this.statusBarStyleGetter(statusBarStyle, color)

      if (style) {
        statusBarStyle = style
      }
    } else if (color) {
      statusBarStyle = isDarkColor(color) ? Style.Dark : Style.Light
    } else {
      // We aren't changing the status bar color, no need to set the style
      setStatusBarStyle = false
    }
  }
}

Yeah, you're right, will fix that.

Okay, v4.0.1 has been pushed, thanks.
FYI, this isn't necessary because this.syncStatusBar is typed such that no other types could be used:
if (
    typeof this.syncStatusBar === 'boolean' ||
    this.syncStatusBar === 'textOnly'
  )


Array of primitive values isn't binded

Vue.js version
1.0.24 and 1.0.12
Reproduction Link
example 1
example 2
Steps to reproduce
Click on the buttons that modify an array of booleans.
What is Expected?
The reactive data to be updated
What is actually happening?
data isn't updated
===
It seems that Vue isn't changind reactive data arrays of primitive data, booleans in this case. If there is an array defined like this
[true, true, false]

it won't be updated. A workaround for that case is to use it like this.
[{value: true}, {value: true}, {value: false}]

If this isn't a bug, then it should be mentioned in the docs.

It has nothing to do with primitive values specifically, its a reactivity caveat due to limitations of JavaScript: https://vuejs.org/guide/list.html#Caveats


feat(router): add wildcard to string patterns

As discussed on Discord, here you go 😄 Hope formatting is alright.

Thanks! I'll add tests to your branch directly


Use docker build binaries

这个 PR 实现什么功能/修复什么问题:
在 OSX 上能使用 docker 编译出可执行文件
是否需要 backport 到之前的 release 分支:

/cc @yousong @swordqiu @ioito @tb365 @wanyaoqi

Codecov Report

Merging #845 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #845      +/-   ##
=========================================
+ Coverage    7.59%    7.6%   +<.01%
=========================================
  Files         344     344
  Lines       53571   53571
=========================================
+ Hits         4071    4076       +5
+ Misses      49119   49116       -3
+ Partials      381     379       -2

Flag
Coverage Δ

#aFlag
7.6% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/util/rbacutils/rabc.go
69.69% <0%> (+1.13%)
:arrow_up:

pkg/appsrv/response.go
69.23% <0%> (+3.07%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm
/approve


Remove pre-push hook

Avoids running unnecessary tests on push. We have CI for that

Ah the comma 🤦♂

@swissspidy Build still failing.

Because I haven‘t fixed the errant comma yet :-)


Public Key adding issue

Hi,
Thank You for this project!!!
I want to integrate licensing into my project, however, I got stumbled on one issue. I want to change the public key while initializing the new project:

Generated license all the time ends up like this (length of 140):

And it is corrupted all the time.
Am I doing something wrong? Can you provide a sample of how to generate a license with a private-public key?
Any help is appreciated. Thank you in advance!

Found out that public/private keys are generated during the first compilation. All solved, closing issue


Consider blacklisting the HTML element?

Hey,
We've encountered an issue with this task when we set our html element to have a base font-size (of 18px for example) - for the rest of the styles to inherit from.
The task runs on the html's CSS and converts its value to a rem unit based against the rootValue in the config (18), changing it to 1rem.
This then causes it to be 16px (browser default) and the other elements on the page that have been converted to rem units are sized relatively according to a 16px base size instead of the 18px that we want.
Is there a way to exclude the html root element - could that be a best practise going forward?
Or is there any advice you can give us if we are using this wrong? Currently we're ignoring the html element's CSS by putting px value in capitals as you suggest: html { font-size: 18PX;}.
Anything I can do to help let me know,
thanks.

Does the selectorBlackList option solve your problem?
{
    selectorBlackList: [/^html$/]
}


[Feature] Safeguard against bad actors (custom build scripts)

We've got a lovely Idris community but if/when pack starts running arbitrary extra code as part of the building or installation of dependencies I would love to see (as an additive feature, not a pre-requisite) some safe guards against unexpected side effects.
Deno (NodeJS "successor") takes a permissions stance where the user running code must ok various kinds of things like making network requests or reading/writing to disk. That's an interesting angle to think about, but I think something as simple as a prompt for confirmation right before a dependency with custom build scripts is built would be great.
It's not all about bad actors, either. It's nice not to surprise the person running a build even if you're not doing anything malicious.

This is a great idea. Ideally, such a security measure would come with a command line option to turn prompting of (for instance when checking data collections automatically).

This was implemented in #31  together with some command-line options and a setting in the pack.toml for explicitly turning it on or off (it is turned on as a default). It's just a prompt for confirmation in case of custom build- or install hooks, however.

A simple safeguard has been implemented quite a while ago, together with command-line options and a pack.toml setting for turning this safeguard off. In addition and as suggested in #177, a "whitelist" setting was added to pack.toml files in #186, which allows users to turn off the safeguard only for certain trusted packages.
Since I try to keep up with feature request and clean up the issue tracker a bit, I'll close this as implemented. Feel free to reopen (or open a new issue), if you think the current safety measures are not enough.


I am a new user Flutter. I found problem about android studio that it occur red error as picture. Everyone who know what happened.

Have you installed the Flutter Plugin for VS Code?

Hi @Sukum99
can you please provide your flutter doctor -v
and your pubspec.yaml
Thank you

Sorry, I uninstall Android studio and Flutter then reinstall again. It is solved

@Sukum99
Closing as solved


Building sqlx-cli fails - exclusive range pattern syntax is experimental

When running this Dockerfile on my M1 MacBook Pro, the compilation fails:
FROM rust:1.76.0-bookworm
RUN cargo install<EMAIL_ADDRESS>
I'm getting following error message:
   Compiling sqlx-mysql v0.8.1
error[E0658]: exclusive range pattern syntax is experimental
  --> /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/sqlx-mysql-0.8.1/src/io/buf_mut.rs:19:13
   |
19 |             ..251 => self.push(encoded_le[0]),
   |             ^^^^^
   |
   = note: see issue #37854 <https://github.com/rust-lang/rust/issues/37854> for more information

error[E0658]: exclusive range pattern syntax is experimental
  --> /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/sqlx-mysql-0.8.1/src/io/buf_mut.rs:20:13
   |
20 |             251..0x1_00_00 => {
   |             ^^^^^^^^^^^^^^
   |
   = note: see issue #37854 <https://github.com/rust-lang/rust/issues/37854> for more information

error[E0658]: exclusive range pattern syntax is experimental
  --> /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/sqlx-mysql-0.8.1/src/io/buf_mut.rs:24:13
   |
24 |             0x1_00_00..0x1_00_00_00 => {
   |             ^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: see issue #37854 <https://github.com/rust-lang/rust/issues/37854> for more information

Docker image
SQLx version
result

rust:1.76.0-bookworm
<EMAIL_ADDRESS>Fail

rust:1.76.0-bookworm
<EMAIL_ADDRESS>Ok

rust:1.79.0-bookworm
<EMAIL_ADDRESS>Fail

rust:1.80.1-bookworm
<EMAIL_ADDRESS>Ok

Info

SQLx version: 0.8.1
SQLx features enabled: default
Database server and version: not applicable
Operating system: OS X Sonoma 14.6.1 on host.
rustc --version: 1.76.0, 1.79.2
Device: MacBookPro18,1, with Apple M1 Pro chip

Please consider upgrading your rust version or providing a PR.
Upgrading should not be breaking for you and adds some very nice improvements.
You can also consider providing a PR to lower the MSRV. 1.80 is likely a tad too new.

[!NOTE]
Relevant disclaimer about MSRV of sqlx.

Same root cause as #3461


Edge click events not working

I have a Sigma instance that I'm creating and binding a function to clickEdge like this:
  var sig = new sigma({
    renderer: {
      container: document.getElementById('sigma-container'),
      type: 'canvas',
    },
    settings: {
      enableEdgeHovering: true,
      minEdgeSize: 2,
    },
  });
  sig.settings('labelThreshold', 1);
 //...
  sig.bind('clickEdge', function(e) {
    console.log(e.data);
  });

However, nothing happens when I click on any edges. I also don't see any edges being colored with the default edge hover color when I mouse over them. Am I missing any settings? I have a working clickNode binding.
In looking through similar issues on Github, I found this similar open issue - https://github.com/jacomyal/sigma.js/issues/816.

I had the same problem. Firstly you have to work with a sigma type canvas. (I read events on edges works only with it).
Then be sure that :

enableEdgeHovering is setted on "true"
the edges you want to be clickable have a size setted

I tested it in Chrome only, with Sigma 1.2.1

I have noticed that edge hovering does not work when the edge is aligned horizontally or vertically (connecting nodes with the same x or y coordinate)
In the following example the edges from router-2 to pc and to switch are hoverable and the one from switch to pc is not:


Gulpif fails running script it shouldnt run

Consider the following task:
if (false) {
  sourcemaps = require('gulp-sourcemaps');
}

gulp
.src('app/styles/*.scss')
.pipe(gulpif(false, sourcemaps.init()));

When you run that, you get:
TypeError: Cannot read property 'init' of undefined

Why would the property be accessed although it shouldn't be executed?

What you're passing to gulp-if is the results of calling the init function.
Gulp-if won't use it, but the error happened before you called it.
On May 14, 2016 12:11 AM, "Christian Daguerre"<EMAIL_ADDRESS>wrote:

Consider the following task:
if (false) {
sourcemaps = require('gulp-sourcemaps');
}
gulp
.src('app/styles/*.scss')
.pipe(gulpif(false, sourcemaps.init()));
When you run that, you get:
TypeError: Cannot read property 'init' of undefined
Why would the property be accessed although it shouldn't be executed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/robrich/gulp-if/issues/66

Just figured that out by myself! Thanks a lot for your quick answer ;)

Maybe the following syntax could be considered for this case:
gulpif(condition, [object, method])

What do you think?

Interesting idea, similar to lazypipe.
On May 14, 2016 12:21 AM, "Christian Daguerre"<EMAIL_ADDRESS>wrote:

Maybe the following syntax could be considered for this case:
gulpif(condition, [object, method])
What do you think?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/robrich/gulp-if/issues/66#issuecomment-219205691

I had a similar issue with the following task to concat files only if a name is provided.
src is an array of one or more file paths
var doMerge = name !== undefined;
return gulp
    .src(src)
    .pipe(gulpif(doMerge, concat(name)));

Running the task produces the error:

Missing file option for gulp-concat

Any suggestions?
Also, isn't it a performance impact to run the expression for the true child before the checking the condition?

You're passing the results of calling the concat function to gulp-if. By
the time I see it, concat has already failed.
On Aug 1, 2016 9:23 PM, "NavenduSanwal"<EMAIL_ADDRESS>wrote:

I had a similar issue with the following task to concat files only if a
name is provided.
src is an array of one or more file paths
var doMerge = name !== undefined;return gulp
.src(src)
.pipe(gulpif(doMerge, concat(name)));
Running the task produces the error:
Missing file option for gulp-concat
Any suggestions?
Also, isn't it a performance impact to run the expression for the true
child before the checking the condition?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/robrich/gulp-if/issues/66#issuecomment-236555161, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAolfFWksoML2-Cd_UbQuUabv9AbUgdSks5qbdc0gaJpZM4Ieiw1
.

Can you suggest any work around?

var doMerge = name !== undefined;
var thefn = doMerge ? concat(name) : through2.obj(function(file, enc, cb) {
this.push(file); cb(null); });
return gulp
.src(src)
.pipe(thefn);
On Aug 1, 2016 9:36 PM, "NavenduSanwal"<EMAIL_ADDRESS>wrote:
Can you suggest any work around?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/robrich/gulp-if/issues/66#issuecomment-236557341, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAolfLvA2Pnr40CmHNk0s_zwF-7LRF54ks5qbdokgaJpZM4Ieiw1
.

Thanks! It worked just fine.

I had the same issue as has been discussed but with gulp-debug().  If the arg to gulp-if is always evalutated then surely this won't be suitable in quite a few case.
Can you think of design that would prevent its arguments being evaluated until the condition is true?

The closest we've come is lazypipe's passing of function name and arguments
as an array, but it just looks weird.

gulpif(condition, [method, object]) passing is more readable when using the same function with different arguments (compared to writing a workaround conditional no-op function).
Eg.
gulp.task('copy', () => {
    return gulp.src(paths.assets)
    .pipe(gulpif(showCopy, debug, {title:'copy files: '}))
    .pipe(gulp.dest('www'));
});

gulp.task('js', () => {
    return gulp.src(paths.js)
    .pipe(gulpif(showUglify, debug, {title:'uglify files: '}))
    .pipe(uglify())
    .pipe(gulp.dest('www/js'));
});

gulp.task('image', () => {
    return gulp.src(paths.assets)
    .pipe(gulpif(showMinify, debug, {title:'minify images: '}))
    .pipe(imageMin())
    .pipe(gulp.dest('www/img'));
});

Would allowing functions as arguments fix this issue?
I don't know if this produces any complications or breaks existing code.
It's my second day of using gulp, thus my horizon is very limited.
The following works in my scenario:
let mygulpif = function (condition, trueChild, falseChild, minimatchOptions) {

    const _getEffectiveChild = function (child) {
        return typeof child === "function" ? child() : child;
    };

    if (!trueChild) {
        throw new Error('gulp-if: child action is required');
    }

    if (typeof condition === 'boolean') {
        // no need to evaluate the condition for each file
        // other benefit is it never loads the other stream
        return condition ? _getEffectiveChild(trueChild) : (_getEffectiveChild(falseChild) || through2.obj());
    }

    function classifier(file) {
        return !!match(file, condition, minimatchOptions);
    }

    return ternaryStream(classifier, _getEffectiveChild(trueChild), _getEffectiveChild(falseChild));
};


Bug: App's menu opens when I change keyboard layout by Alt+Shift

Hello.
When I hit Alt+Shift to change my keyboard layout, app's menu opens so I can't type anything until I close it. It's really annoying.
Also I did some research and found that it seems to be a common problem for electron-based apps.
The thing is when you have some high-level menu labels without "underscored" letters (these ones that allow you to activate menu item by hittimg alt+underscored_letter), they will be activated when you hit Alt+Shift.
I don't know if it's a bug or just a feature but probable workaround is to edit menu labels' definitions in this way: label: 'File' -> label: '&File'. It will add an 'underscore' to letter F and therefore prevent this menu item from being activated by hitting Alt+Shift.
GPMDP 4.2.0
Linux x64 4.6.4-1-ARCH
KDE Plasma 5.9.4

Currently Alt+Space is by design both on the apps part and on the OS's.  If you want to change it to have menu specific hotkeys (&File) then I would accept a PR to do so

Not sure if I understood you correctly.
When I hit Alt+Space, track pauses and that's OK with me.
The problem is, when I hit Alt+Shift (in order to change my keyboard layout, that's a common hotkey in different OS'es and DE's) app's menu opens and tell me that I shall not pass until I close it.
That's a common scenario: I want to find some cool artist so I put a cursor in a search bar.
But sometimes I'm getting bored from good ol' Гражданская Оборона and go for something completely different with Latin letters in it's name.
So I hit Alt+Shift in order to switch from Cyrillic to Latin layout and app menu opens (I never asked for this). Therefore, in order to continue my quest I should close menu manually because it won't let me to perform any search.
It's clearly a misbehaving.
Actually, I don't care about menu hotkeys, I just proposed a possible workaround.
Also I'd prefer that a single app wouldn't force me to change a global hotkey.

Same bug in XFCE. It's very popular bug in electron apps, for example:
https://github.com/meetfranz/franz/issues/1088
https://github.com/zulip/zulip-electron/issues/528
https://github.com/RocketChat/Rocket.Chat.Electron/issues/50
https://github.com/vector-im/riot-web/issues/4345
And there is a very easy to fix:
https://github.com/meetfranz/franz/pull/1323
@MarshallOfSound can I submit a PR?

Feel free to PR @romkaspb

I'm really confused, the solution I've described is working in multiple electron apps and not working in Google Play Music Unofficial.
@jostrander may be we can investigate it together?
I'm only changing src/main/features/core/applicationMenu.js, and only adding & to each label (i. e. 'Edit' -> '&Edit').
Then, I'm running the following commands:
$ npm run build
$ npm start

And problem still reaching.
It's working at most electron apps, why it's not working here?
Are you using Electron on steroids? :)
May be a reason of it's behaviour that I already have installed this app from deb package to my ubuntu?
It seems that Atom had the same bug (https://github.com/atom/atom/blob/master/menus/linux.cson),
but atom guys solved it in very strange way. They have added & to random place of label (of course not random, but I did not reached the logic).

I'm on Ubuntu 18.04.2 with Gnome and I can't reproduce this, however I only have the en_US keyboard layout enabled. I can bring the menu bar up by using Alt alone but unfortunately Alt+Shift has no effect.
On another note, the & usually precedes the character you would hit to shortcut to that menu item, for example if you were trying to navigate the menus:

You would use &Edit, &View, &Playback, &Window, and &Help to allow you to navigate using Alt+E, etc.
I would try to uninstall the dpkg variant if you are running the development version, just as a precaution.

As I know this bug is not confirming on Gnome.
It's 100% confirmed on XFCE and in around a 50% confirmed on KDE.

I can confirm that KDE is still affected.


Errors on certain works after JS kicks in

What
Certain works are erroring once the JavaScript runs.
Seems to be an issue in the Download component.
Where
e.g. https://wellcomecollection.org/works/ve8mk3c2

This seems to be working now? So closing as done until we see it again.


Transform updates

Fixed an error in tcrd-protein transform (it was including DrugCentral IDs, incorrectly)
Updated HPA transform to accommodate newest release (source format changed, of course)
Added transform for HPA protein expression associations by subcell location - these are mapped to GO component terms
Expanded all test_transform_utils cases to cover full Koza transforms - they're essentially all integration tests and they take ages to complete, but should cover many more error cases and potential source data issues

Had intended to include protein families from TCRD here but that may make more sense taken directly from Interpro; the free-text-ish ones in TCRD look like they came from UniProt but those are curated from multiple sources.

Test environment ran out of memory. Will have to scale back the larger tests.


Game Crashes On Startup With Oculus

Minecraft Version
1.19.2
ModLoader
Forge
Shimmer version
Shimmer-1.19.2-0.1.14
Modpack info or mod list(please reduce mod range)
Oculus, Shimmer
The latest.log file and hs_err_pidXXX if exists
https://pastebin.com/BUtrqdhK
optifine , Rubidium , flywheel or any rendering related mods. mod version is required.
Oculus-mc1.19.2-1.6.4
Issue description
The game crashes immediately upon startup with the latest version of Oculus. Appears to be a mixin conflict. This notably doesn't occur with the previous released version of Oculus, v1.2.8a.
Steps to reproduce

Create a pack with Oculus, Shimmer, and anything else.
Boot the game.

Watch game crash, receive crash log.

Other information
No response

This also seems to happen with Indium for Fabric/Quilt

Checking daily for Shimmer updates to hopefully get this fixed as I too want to enjoy this nice mod along with Oculus

I've seen several issue reports and can confirm that it's still happening on the latest version of Oculus, 1.20.1. Does not seem like any time soon they will be a fix, unless mod dev is looking into it still.


switch to klog

/assign @adambkaplan
per promise in #5

/assign @coreydaley
let's confirm you lgtm'ing a approved PR will allow for merge

@gabemontero looks like it needs a rebase, then i can lgtm it

yeah #8 updated the gomod stuff as well @coreydaley ... I'll rebase momentarily

ok update after rebase up @coreydaley

/lgtm


system-tests: new scale test: testScaleRouterAutomatically

testScaleRouterAutomatically - only for standard space

Deploy 50K addresses type=anycast (with XXS size i.e. router = 0.0001) 10K addresses per pod
Check if router was scaled up (to 5 pods)
simple send/receive
Remove 20K addresses
Check if router was scaled down (to 3 pods)
simple send/receive

blocked by: https://github.com/EnMasseProject/enmasse/issues/1014

bug is fixed, test was enabled and merged with master: https://github.com/EnMasseProject/enmasse/pull/954
thank you @ulf for fixes in test :+1:


feat(eigen-client-extra-features): Eigen client memstore

What ❔
This PR reimplements memstore client

Why ❔

Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via zkstack dev fmt and zkstack dev lint.

Having store_blob and put_blob separately seems unnecessary, maybe it would be better to just combine them.

Having store_blob and put_blob separately seems unnecessary, maybe it would be better to just combine them.

Ill remove store_blob and make it more similar to RawEigenClient

Please add some docs to the memstore struct and important functions

Done


fix prototype datasets data loading tests

This re-enables the serialization test after pytorch/pytorch#74958. Test will fail for next ~3 hours until the other PR is part of the PyTorch core nightlies.
Edit: The PR evolved to something more. Instead of only serialization, we now also test traversability as well loading through a DataLoader. Together with #5723 we should now have sufficient coverage for our datasets to not accidentally break data loading workflow.

Even with the patch in https://github.com/pytorch/vision/pull/5711#discussion_r839678058, the split="val" configuration fails due to https://github.com/pytorch/pytorch/pull/74958#issuecomment-1084637227.

This PR is a sister to #5723, which adds a data loader test for DDP.

CI is happy with today's torch / torchdata nightlies.


PlatformText should inherit textTheme from PlatformApp

In an attempt to make the PlatformText widget a bit more useful it would be good to have it automatically inherit the textTheme from the PlatformApp. Right now to do this you have to set the style property of the PlatformText individually. On top of that you have to specifically see what platform is being used and call the right theme data (Material or Cupertino). This could be abstracted out to the PlatformText widget so setting the theme at the PlatformApp level actually cascades down.

The PlatformText widget just creates a normal flutter Text widget with the text string upper cased for Android. Everything else should work as if you used Text directly. Anything more than that I would feel becomes too opinionated and deviates from the purpose of this project.


Run pytest CI jobs nightly

This PR:

Adds configuration to run the 'pytest' GitHub Actions CI workflow/jobs every day. message_ix already has a separate 'nightly' workflow. This will serve as a 'canary' test, i.e. to identify when changes in dependencies or the CI environment break the code or the CI configuration.
Checks whether iiasa/message_ix#413 is also affecting ixmp.

How to review
Note that the CI checks all pass.
PR checklist

~Add or expand tests.~ N/A, CI changes only.
~Add, expand, or update documentation.~
~Update release notes.~

The macos-latest py3.6 and py3.8 jobs both fail with messages like:
Error: Error: package or namespace load failed for ‘rixmp’:
 .onLoad failed in loadNamespace() for 'rixmp', details:
  call: NULL
  error: Error 1 occurred creating conda environment r-reticulate
Error: Error: loading failed
Execution halted
* removing ‘/Users/runner/work/_temp/Library/rixmp’
Error: Error: Failed to install 'rixmp' from local:
  (converted from warning) installation of package ‘/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T//RtmpXji6yq/filebea728d7682/rixmp_<IP_ADDRESS>00.tar.gz’ had non-zero exit status
Execution halted
Error: Process completed with exit code 1.

"Error 1 occurred creating conda environment r-reticulate" is strange because the workflow does not use conda. This may be because a new version of reticulate is detecting the version of conda installed by default on the job runner and—incorrectly—attempting to create an environment.


Missing section for spike in DATA_README.md

In DATA_README.md, the explanation for the session-specific file spike is missing while the section for neural_trial_timings appears twice.

@methi1999 Thanks for reporting this. I have fixed the documentation.
Please also see a new version of this dataset at https://dandiarchive.org/dandiset/000231 and related preprint at https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>1259v1. The advantage of the new dataset is that it includes more raw data (the entire electrophysiological recording, all the videos), and it is in the NWB format. However, this Rodgers2021 dataset remains useful for replicating the analyses presented in my original paper.


Invalid string comparison in new date code

This code is incorrect and fails to work:
        public function getIndexForSelectedDate():Number
        {
            if (!_selectedDate) return -1;

            var str:String = _selectedDate.toDateString();

            for(var i:int=0; i < _days.length; i++) {
                var test:Date = _days[i] as Date;

				if (test && test.toDateString() == str)
					return i;

            }
            return -1;
		}

As it is doing comparisons on dates stings like so:
str: "Thu Nov 09 2017"
test: "Thu Nov 09 2017 00:00:00 GMT+1100 (AEDT)"
The strings will never match.
(Tested on OSX Chrome other browsers may or may not have the same issue)

Something does not seem right.
Your second string is what you get when calling toString() -- not toDateString().
Please attach a test case and steps to reproduce.

Timezones and daylight savings is also likely to cause issues. Suggest we go back to checking numeric month and year.

To reproduce select a month and step forward a month and backwards a month. See also #62 and pull request with that.

That was a bug which existed prior to the change you are referring to. I just committed a fix for that bug.
Unless you can give me a way to reproduce your problem, I'm going to close this issue.
Timezones and dls will not effect things.


Bufferview target error, zero when it should be element array enum

Given the spec: https://raw.githubusercontent.com/KhronosGroup/glTF/master/specification/2.0/schema/mesh.primitive.schema.json

Primitive Indices: "The index of the accessor that contains mesh indices.  When this is not defined, the primitives should be rendered without indices using drawArrays().  When defined, the accessor must contain indices: the bufferView referenced by the accessor should have a target equal to 34963 (ELEMENT_ARRAY_BUFFER); componentType must be 5121 (UNSIGNED_BYTE), 5123 (UNSIGNED_SHORT) or 5125 (UNSIGNED_INT), the latter may require enabling additional hardware support; type must be \"SCALAR\". For triangle primitives, the front face has a counter-clockwise (CCW) winding order."

The loader states that some gltf files have mesh primitives with a bufferview.target of 0, however see attached rock.gltf file, it states indices of 4, which means the target should be 34963. From the spec, unless I'm misunderstanding it, states that the target should only ever be 34963 or 34962 (when indices is missing). Another example is the Khronos avocado gltf2.0 example mesh
rock.zip

Just to add to this, forcing the target to be Element Array Buffer renders the mesh properly.
int target = bufferView.target == 0 ? GL_ELEMENT_ARRAY_BUFFER : bufferView.target;
glBindBuffer(target, vbo);
glBufferData(target, bufferView.byteLength,
    &buffer.data.at(0) + bufferView.byteOffset, GL_STATIC_DRAW);

So the problem lies specifically with the parser for 'target', I think, as the buffers are fine

Thanks!
Even though it looks the spec does not state default target value, it looks its safe to initialize it as 34963 (ELEMENT_ARRAY_BUFFER)

Just to add to this, forcing the target to be Element Array Buffer renders the mesh properly.

You can send a PR!

I thinks this issue is ready to close thanks to the merge of https://github.com/syoyo/tinygltf/pull/117

Yes thanks, just saw this. Looks like after the recent merge, everything is fine


fix: adds rel attribute to clickable tile anchor tag

closes #2996
This PR adds the rel attribute to the anchor tag in the clickable tile for security
Similar security also observed in the anchor tag for overflow menu options component

I have read the DCO document and I hereby sign the DCO.


casing of field names in examples is wrong

The given examples result in errors during Manifest-Validation:
"PackageURL" and other URL fields in the examples should be "PackageUrl" (PascalCased)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d657479f-c0b7-6358-c7d0-0402215edaa5
Version Independent ID: 8976699b-cdba-5206-bdb0-8a0875acfe45
Content: Create your package manifest
Content Source: hub/package-manager/package/manifest.md
Product: dev-environment
Technology: package-manager
GitHub Login: @KevinLaMS
Microsoft Alias: kevinla

Thanks for the report.  I will queue up a change.


⚠ SceneTime has degraded performance

In 9d96f64, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1596 ms

Resolved: SceneTime performance has improved in 0ad1c49 after 6 minutes.


Fatal Error

Hello, I've installed the pre-installed version on my server and when I try to Proxy a website I get this error;
Fatal error: Call to undefined method Proxy\Event\ProxyEvent::getName() in /home2/matrixebiz/public_html/phpproxy/vendor/athlon1600/php-proxy/src/Plugin/AbstractPlugin.php on line 47
What should I do? also, can I run this proxy with the website direct link like: http://myserver.com/phpproxy.php?http://WebsiteNeedingProxy.com
Thanks

Try it now:
https://www.php-proxy.com/download/php-proxy.zip

Okay, thank you. Now can I proxy a website by just using 1 single link, like?
http://myserver.com/phpproxy/index.php?http://WebsiteNeedingProxy.com

... because I need to proxy a Video link as well, like;
http://myserver.com/phpproxy/index.php?http://server.com/video.m3u8

To do all that, you would first need to edit config.php and change this line:
$config['url_mode'] = 2;

into this:
$config['url_mode'] = 0;

This is all explained at the top of that file:
how unique is each URL that is generated by this proxy app?
0 - no encoding of any sort. People can link to proxy pages directly: ?q=http://www.yahoo.com

Now you can link to proxified content directly like this:
yourproxy.com/index.php?q=anotherserver.com/video.mp4

Okay, thanks for the info but still not working with the Roku :(
Trying to proxy http://www.myserver.com/video.m3u8 to another m3u8 and the second m3u8 file is like this;
#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=1000,RESOLUTION=640x360,
http://www.myserver.com/phpproxy/index.php?q=http://www.externalserver.com/playlist.m3u8?id=0ad5aac39bb13fbe54d411dc4ce8255fe785654a
Works in VLC but not the Roku :(

If that still did not work, you should probably just use this:
https://www.proxynova.com/proxy-software/


Update github-enterprise graphql endpoint

Thank you for this amazing tool
The Graphql endpoint in the docs is incorrect. This PR aims to rectify that my updating the api endpoint to the correct value.
To find the correct value I used GHA in an enterprise server and got the value of the github.graphql_url   context variable
ref - https://docs.github.com/en/actions/learn-github-actions/contexts#github-context

Thank you for your contribution!


Broken Go snippets

Hi! Thanks for making this plugin!
I'm having issues with some Go snippets. In particular the func and if.
func:
func name(params)typetype {

}

Note that type appears twice, but only the second one is an insert node. The first type changes to whatever I insert into the second one.
if:
if conditioncondition{

}

Similarly to func, if also has the condition repeated. The first condition is an insert node, and the second condition changes to whatever I insert into the first one.

Also, the meth Go snippet doesn't even expand for some reason

@mawkler please test it with minimal configuration (or with cmp) from this sample directory - sample_configs
If it works, then problem is somewhere in configuration, maybe some conflict with other plugin. Try to make minimal config to reproduce that bug.

@mireq I get the exact same behaviour when using your minimal config cmp_lazy.lua

@mawkler if you can try it on empty user profile without ~/.config/nvim directory and ~/.local/share/nvim. If problem persists, please check nvim and nvim python bridge version. I will try to reproduce bug with same version.

@mireq

try it on empty user profile

Could you please elaborate on what you mean by this? I ran nvim -u path/to/your/config, is there anything else that I need to do?

@mawkler sorry for dealy, i have forgotten ths comment, too much work.
So nvim -u path/to/your/config should start nvim with custom config path instad of .config/nvim/init.lua.

No worries!

nvim -u path/to/your/config

That's what I did when I was trying both your minimal configs cmp_lazy.lua and minimal_lazy.lua, and I got the same bug 🙂

@mawkler try check nvim version (nvim -v). Try checkhealth. Check python version.

@mireq Good call! :checkhealth luasnip gave me the following warning:
- WARNING             For Variable/Placeholder-transformations, luasnip requires
              the jsregexp library. See `:help |luasnip-lsp-snippets-transformations`| for advice

Adding run = 'make install_jsregexp' to my LuaSnip lazy.nvim config solves it. I noticed now that your example configs also included that line, but my guess is that run doesn't run if you already have the plugin installed (which I did).
Anyway, thanks for the help!


Docker Error - Booted as backend: False - Response: {'detail': 'Not Found'}

I follow the Docker Setup but it did not work. Tried on both Ubuntu, Windows Docker and both cpu and cuda version but the same error of Booted as backend: False - Response: {'detail': 'Not Found'}.

Did you try to access the / URL? It is not defined and returns 404, as expected.
you have to access the /translate path, i.e.
http://localhost:24080/translate?target_lang=en&text=Hallo Welt

oh, it's my fault. Thanks so much :)


onMouseUp event bug

Codepen: https://codepen.io/galabl/pen/qBKgLEG
Since onchange event is fired too often it's not really reliable for me to use it(it fires even if the value didn't change) I wanted to use the onMouseUp event but it doesn't fire every time.
For example, if you click and drag slider pointer, it can happen that the mouse pointer is not on top of the slider pointer sometimes, in that case, the mouse up event is not fired.
Could you please take a look at this.
Thanks.

The 'onchange' event should be fixed now in v4.0.25, It should only fire when value changes:
You can use it it with CDN:
<EMAIL_ADDRESS>Codepen example:
https://codepen.io/mzusin/pen/qBJbYap


isBlade fails on degenerate metrics

>>> import clifford
>>> layout, _ = clifford.Cl(3, 0, 1, firstIdx=0)
>>> locals().update(layout.blades)
>>> e0.isBlade()
clifford\__init__.py: RuntimeWarning: divide by zero encountered in true_divide
  newValue = self.value / other
clifford\__init__.py: RuntimeWarning: invalid value encountered in true_divide
  newValue = self.value / other
False

As discovered by @enkimute

This happens in CGA too:
>>> from clifford.g2c import *
>>> t = up(e1) | (up(e1)^up(e2)^up(-e1))  # tangent blade
>>> t*t
0
>>> t.isBlade()
clifford\_multivector.py:264: RuntimeWarning: divide by zero encountered in true_divide
  newValue = self.value / other
clifford\_multivector.py:264: RuntimeWarning: invalid value encountered in true_divide
  newValue = self.value / other
clifford\_multivector.py:691: RuntimeWarning: invalid value encountered in greater
  nonzero_grades = self.layout._basis_blade_order.grades[abs(self.value) > eps]
False


I love tabcloud so much, looking for using it in Firefox too

I cannot find TabCloud as Firefox extension. Is it available?

Same.


Can`t send / use funds from Copay & Error message: "null is not an object"

I ran into an issue on copay.
I’ve received funds from simpleswap and transferred one part of it to an address (1st tx).
Then I tried sending the rest of my funds (2nd tx) but received an error message on copay (mobile), saying, that „null is not an object (evaluation ‚this.rate.toFiat(satoshi, settings.alternativelsoCode, coin)toFixed‘).
I can see my balance on on the mobile version, but have 0 Part on desktop. Desktop also shows the same error message.
I can´t load any tx-history as well.
I can provide screenshots if needed.

Thank you for logging this.
Based on the error, this relates to an issue that has been logged before and is in the process of being resolved and patched. Will be out with the upcoming release.
https://github.com/particl/copay/issues/35

Thanks!

please Helping comiunity, thanks, No TransactionDustOutputs of 0.0020 BTC: Could not build tx: bitcore.Error: Dust amount detected in one output


Publish data that can be visualised in Health Center

Fix for issue #141

Done.

I actually meant the comment in the code commit ;-)

Ah. Done that as well then :-)

LGTM. Merging.


An error occurred: unknown flag: --from-backup

This is after following the example on the README.md file.
Running the command:
ark restore create --from-backup nginx-backup

I downloaded the latest version of ark: Version: v0.7.1

Please see our docs for v0.7.1: https://heptio.github.io/ark/v0.7.1/. The --from-backup flag is only available if you build from the master branch.

@ncdc Ok great - thanks


Support for QuickActions to accompany reported diagnostics?

I have an existing extension that I'd like to port to this new model.
As part of that, I currently create error list entries and have accompanying quick actions to address the issues.
I see that the new model has the DiagnosticReporter that will help tag (& underline) issues and add them to the error list, but what about including support for adding quick action fixes to the things I report?

Hi @mrlacey, could you elaborate on the scenario a bit more? Are you extension one of the existing languages in Visual Studio or adding support for a new language? Thanks!

I've created an extension that (among other things) reports diagnostics and supplies quick actions for XAML files.
The language implementations don't support any extension capabilities for 3rd party extensions and so I have to treat the document as text and do everything myself.
The ability shown in this repo to report issues that are underlined and added to the error list would greatly simplify what I'm currently doing. But, as I also want to provide quick actions to fix the issues I'm reporting I need to be able to do this too.
The below image shows an example of an element with the squiggle because of an issue and options added as quick actions to address the issue.

For reference, the repo is at https://github.com/mrlacey/Rapid-XAML-Toolkit/ (& I'm only now updating to support VS2022)

We're moving feature suggestions and requests over to our Developer Community site so we can track them better.
This issue has been moved over to this ticket: [VisualStudio.Extensibility] Add support for QuickActions to accompany reported diagnostics. Please continue the discussion in the new ticket.


Remove the reliance on the yt_dlp.extractors.extractors module

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense

What is the purpose of your pull request?

[x] Improvement

This PR makes extractors automatically register themselves when the InfoExtractor class is subclassed, and dynamically walks the list of submodules of the yt_dlp.extractors module to walk through the list of all extractors. This removes the need to keep a giant list of extractors in the yt_dlp.extractors.extractors module; the file was therefore dropped as redundant. Dropping reliance on that module should prevent merge conflicts in the future when independently merging in extractors whose names appear near each other in the alphabet.
Plugin loading implementation is something of a hack right now and may need to be revisited later. But I don’t think it’s an outright blocker.
This change creates a hard dependency on Python 3.0 3.4, due to relying on some importlib features. My initial sketch even raised the dependency to 3.6, because it relied on PEP 487, but later on I decided to re-write it with a metaclass instead, since it may prove useful later anyway (I have some ideas already for what to put in __prepare__). Since we don’t officially support Python < 3.6 any more, either would be fine.
This patch seems to work fine on my machine, but it badly needs testing in other environments. In particular, I have no idea if the pre-built Windows binaries are going to work.

We have a duplicate extractor, it seems: https://trovo.live/video/ltv-100759829_100759829_1610625308 is matched both by TrovoVodIE and TrovoLive.

We have a duplicate extractor, it seems: https://trovo.live/video/ltv-100759829_100759829_1610625308 is matched both by TrovoVodIE and TrovoLiveIE.

TrovoLiveIE was never imported. Seems I forgot to delete it in a820dc722e93b40450b8280a23110c4960800123

I didn't test thoroughly, just some initial observations:

from yt_dlp.extractor import YoutubeIE needs to keep working. It should be easy enough to inject the extractors _ALL_CLASSES into the global namespace
I see you are checking for both BaseIE and for a _VALID_URL to determine whether to register. So is there any reason you are setting register=False for some of BASEIE? OnceIE is the only one that should need it, correct?
make_lazy_extractors is completely broken by this. Not that it is a big deal, since lazy-extractors has always been buggy

Initially I thought it would be enough to consider extractors without a _VALID_URL attribute to be ‘abstract’ (not meant to be used directly, but by being inherited from). But then I saw errors where an ‘abstract’ extractor inherited _VALID_URL from a ‘real’ extractor. I tried to exclude those from auto-registration by setting register=False, but those cases kept hitting and hitting. Eventually I got tired of the whack-a-mole and added the BaseIE name suffix check. I’m not too pleased with it, to be honest. I worry we might some day need to support a site named FlickBase or something, and then of course name the extractor FlickBaseIE…
I thought lazy extractors would keep working? (At least no worse than they did: it looks like enabling lazy extractors removes plugin support.)

it looks like enabling lazy extractors removes plugin support

Yes, I could not easily get them to work together and didn't want to put too much effort into fixing it. If you can make it work, go ahead. If not, that is okay too

The more I think about it, I don’t think this is a viable approach. I may revisit this later.


Fix Postman

Usage changes

changed L1 message to have all snake cases
fixed KeyError issue

Dev changes

Added flush response tests
Updated MockMessaging artifact

[x] Add tests for flush response

It looks like the case of the MockStarknetMessaging contract was changed a short while ago in this pr. However, the events used in starknet use snake case. I think the correct solution is to revert the MockStarknetMessaging contract.


Include default PasswordEncoder

I suggest including a default PasswordEncoder in pac4j, based on jBCrypt:
http://www.mindrot.org/projects/jBCrypt/
https://github.com/jeremyh/jBCrypt
The implementation is tiny, and it would be nice not to have to pull in all of shiro-core or spring-security-crypto in order to properly encrypt and salt passwords. Plus pac4j should really be secure by default, and unencrypted (or unsalted) password databases have caused major headaches for numerous companies.

A few versions ago, we had more PasswordEncoder implementations and we had that exact implementation: https://github.com/pac4j/pac4j/blob/1.9.x/pac4j-core/src/main/java/org/pac4j/core/credentials/password/JBCryptPasswordEncoder.java
We cleaned things a bit as there seems to be no use for libraries other than Spring and Shiro.
But we can bring it back.

@leleuj Shiro and Spring are enormous overkill to add as dependencies just to get password hashing (which is the only thing I would need them for, for my usecase).
Thanks for the link to the removed code. Obviously it's a tiny amount of code to add your own PasswordEncoder, and I could have done so. But I am suggesting not just that pac4j include this JBCryptPasswordEncoder.java, but that you actually pull in jBCrypt itself, into the pac4j repository (it's MIT licensed), so that you don't have to add another dependency.
In general, I have been surprised that pac4j is configured to be insecure by default: you have to manually add a PasswordEncoder, you have to manually enable all the standard security headers and CSRF protection in authorizers (those options are all off by default), etc.  These should all be opt-out configuration options, not opt-in configuration options!
So what I am proposing is that all passwords be encrypted by default with jBCrypt, unless you override the password encoder with another encoder.

Just notice that it is not the full spring dependency, but only spring security, so this can make sense.
Though I was personally in favour of keeping JBCryptPasswordEncoder when the change happened ;)

I wanted to limit the number of options, but indeed pulling Spring Security or Shiro may be overkill for only one class. So let's bring back the JBCryptPasswordEncoder with the optional jBCrypt dependency. Commit: https://github.com/pac4j/pac4j/commit/bdb6051cabcc9aabea74583229eaf9abf3f48435
That said, "manually add a PasswordEncoder" does not make pac4j "insecure by default": you choose the password encoder you want given the best suited cryptographic library you can/want to use.
About the security headers and the CSRF protection, you're right: we should turn them on by default ("csrf,securityheaders"), but it's a breaking change in the runtime behavior (especially the CSRF protection), so let's target that for pac4j v4: https://github.com/pac4j/pac4j/issues/1156

Great, thanks for considering these changes. So if jBCrypt is not on the class path, you will just get a ClassNotFoundException at runtime?

Yes, as there are multiple choices and as we want to limit the dependencies pulled by default, you need to explicitly add it.


New version: Spotify.Spotify version <IP_ADDRESS>0.g52970952

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow

@stephengillie


bug: KeepAwake MIA in iOS

Plugin version:
5.0.1
Platform(s):
iOS 17.6.1, iPad Pro 3rd Gen.
Current behaviour:
Calls to KeepAwake in iOS app fail silently - no result returned (works just fine in desktop web browser)
Expected behavior:
Calls to KeepAwake should return result
Related code:
Code in app:
  private async checkIsSleepSupported() {
    console.log('checkIsSleepSupported', KeepAwake);
    try {
      const ok = await KeepAwake.isSupported();
      this.sleepSupported = ok.isSupported;
      console.log('sleep supported:', KeepAwake, ok, this.sleepSupported);
    } catch (err) {
      console.error('KeepAwake failed:', err);
    }
  }

Other information:
Console logs in desktop browser (Chrome):
checkIsSleepSupported
sleep supported: Proxy(Object) {}  {isSupported: true} true

in Xcode console:
⚡  [log] - checkIsSleepSupported {}
⚡  [error] - KeepAwake failed: {"code":"UNIMPLEMENTED"}

Capacitor doctor:
💊   Capacitor Doctor  💊

Latest Dependencies:

  @capacitor/cli: 6.1.2
  @capacitor/core: 6.1.2
  @capacitor/android: 6.1.2
  @capacitor/ios: 6.1.2

Installed Dependencies:

  @capacitor/android: not installed
  @capacitor/cli: 6.1.0
  @capacitor/core: 6.1.0
  @capacitor/ios: 6.1.0

[success] iOS looking great! 👌

App is using Angular 18.x

This error does not come from the plugin, but from Capacitor. It appears that you have not installed the plugin correctly. Please take a look at the Capacitor iOS Troubleshooting Guide.

actually the problem appears to be that capacitor does not like mono-repos (I’m developing two apps with a lot of shared code). Wonder is that everything worked before except KeepAwake; now the app doesn’t run at all. Such fun.


Fix display of Reverse Solidus and Vertical Line characters

The "Reverse Solidus" and "Vertical Line" characters as shown in the "Member Names" subsection do not display correctly on some browsers (latest Chrome on Mac OS X). Replace them with their HTML entities to ensure they appear correctly.

Thanks!


metrics: change metrics registration management

Heads-up: the PRs this was building on have now been merged, so this PR requires rebase (or maybe merge would work ok? not actually sure tbh - rebase tends to be easier for this case because the state underneath is still the same, just the commit hashes have changed)


Rename application plugin to java-application

Expected Behavior
plugins {
    `java-application`
     // or with Kotlin DSL
     application(java)
}

Current Behavior
plugins {
    application // what is the application target/language?
}

Context
Currently, there are 3 applications plugins (application, cpp-application, swift-application), but only the application plugin does not contain the language. This behavior is wanted and it is total clear in the documentation, that this plugin creates a JVM application and based on the java plugin, but it is not intuitiv from reading the plugins block only. As a beginner, you need to look up the application plugin in the documentation.
Of course, you should read the documentation ;) but explicit providing the language is clearer.

Thank you for your interest in Gradle.
Changing a plugin name is not something done easily because it can have an impact on existing script. Think about other plugins that detect the application of this plugin: they would have to consider multiple names.
In addition, as you stated, this plugin is really a JVM application, irrelevant of the language used to code it. So java-application is incorrect as well.
Given all the other priorities, this is very unlikely to get any traction.


setupFilesAfterEnv: ["jest-mock-console/dist/setupTestFramework.js"] breaks test suits with no tests.

Get
  ● Test suite failed to run

    Invalid: beforeEach() may not be used in a describe block containing no tests.

Looking into this now

This looks to be an issue with jest itself and not caused by the library


Add InputPassword form component. Fixes #9179

Maybe we could add a InputText with type (it can be an enum) attribute instead ? I did this here https://github.com/RemiBou/Toss.Blazor/blob/master/Toss.Client/Shared/Forms/MyInput.razor. I don't see the added value of a specific class.

That's a good point, @RemiBou. We have another feature being built at the moment that will allow arbitrary attribute values to be passed through, so the same thing could be achieved using:
<InputText type="password" bind-Value="@SomeProperty" />

@rynowak @danroth27 Do you have strong opinions on whether <InputPassword /> should also exist as a standalone thing? My preference would be not to expand the set of built-in primitives when there's (about to be) such a simple and discoverable way to make an exactly-equivalent password field.

Do you have strong opinions on whether  should also exist as a standalone thing?

I'm fine with the more minimalistic approach.

I'm fine with not adding InputPassword

Great, closing as not required.


Server stops responding on GUI with large numbers of subnets

Version:
(0.6.6, commit-hash, etc) - Docker based implementation, agent and server on same host
Describe the bug
Server's is not responding on GUI with large numbers of subnets
To Reproduce
Steps to reproduce the behavior:

Add large number of /24 subnets. (lets say 1200)
On GUI unable to get response from server.
When we delete subnets manually from sqlite DB, then only server GUI is accessible.

Expected behavior
Server's working should not be affected by addition of large numbers of subnets. At least no effect should be on servers's GUI.

Please elaborate on what part of the gui is non responsive. When did you pull this version?
Thanks

I have natlas/server:0.6.10
I added 1062 segments of '/24'
Then I found that server is not responding and giving delay in response to browser, especially when scope management page is browsed.

0.6.11 released today and should provide significant performance improvements, however that many segments will still cause some delay on the /admin/scope page at this time because there is no pagination happening on the server side.


Add POA Network as list of nodes

I'm working on PR for MEW to add POA network.
I'd like to ask devs for support to let me know list of requirements before I submit a PR.
Current Commit:
https://github.com/oraclesorg/wallet/commit/b2387337c6e9752c07bf644b51db3fe4dce22e19
Deployed:
https://wallet.poa.network
Questions:
Warning for HD paths for Ledger. Please advice on how to fix them.
How to set default gasPrice to 1 gwei?
Anything else I should know/add before submitting PR?
FYI:
We don't intend to run our own version of MEW, we would like to submit PR and destroy our repo.

Tested it with Ledger Nano S, works as expected. Great work!

We only require that the chain has implemented EIP-155 to prevent replays

Also wonder about HD Paths for Ledger, will there be specific one for the POA?


How to implement routing in lit-html?

As a single page app, how can i implement url routing in lit-html?

You can use any router, as the lit-html is totally framework agnostic.
If you are looking for a router which works with Web Components, take a look at the vaadin-router: https://github.com/vaadin/vaadin-router

lit-html is just a templating library. Use whatever routing library you wish. Loss of people seem to use page.js

There are some sample apps using LitElement, take a look at how they do it: https://polymer.github.io/pwa-starter-kit/sample-apps/

PWA Starter kit routing approach is great! I manage to put all this in a route element here: https://github.com/fernandopasik/lit-redux-router
Feedback and contributions are very much welcomed!!

Very nice. I'm sure that a lot of incoming users will appreciate this.
https://themesurgeons.com
https://themesurgeons.com

@lit-labs/router https://github.com/lit/lit/discussions/3354


Make a login DM for hello

I thought about it for a few days, I think hello needs a login DM for itself, which sounds very difficult and is actually very simple; Most linux or BSD distributions require other login programs developed, I think because it requires different desktops to be able to use the same login program (Maybe wrong).
But how to present it, as long as kwin or the like displays the login window before the user logs in to the account, which means that the switching function of other desktop DEs is omitted and only the login window is retained. Others such as clock, battery, network, network users, password prompts, prompting aids, notifications, etc., these functions do not need to be added for the time being.

I figured it out from this screenshot.

https://github.com/helloSystem/LoginWindow, work in progress.


Support building with only Cargo

To make it more accessible we should support both cargo building and bazel building.
The major reason for this is because we should support windows, but in my experience it's quite difficult to get windows to work with bazel, so I'd like to just use cargo for such case.

@aaronmondal We talked about this, and decided to actually go through with it :smile:

Interesting! Do you already know how you'll handle the test libraries?

Currently the plan is to only support the cas binary and all supporting libraries. After a PR to do that lands, maybe we can add test support.

@allada what issues did you encounter on Windows?

@allada what issues did you encounter on Windows?

I have a working version of the code that compiles and runs on windows. The major issue that I have is configuring bazel for windows is really rough. I'm sure it's something I'm doing, but I can't even compile bazel itself on windows, but I also have a version of windows that likely needs a fresh install.
You can see a lot of corner cases in windows here: https://bazel.build/configure/windows


changed comment line

Directory changed to "bedpeOverlap" and all instances of 'bedPe' have been changed to 'bedpe'. There are still instances of BedPe because that is how the struct is named in the bedpe.go file. I can go about changing all of those if we would like. But from outward appearance the issue is fixed

Looks good, I committed Eric's suggestion. It looks like we're still failing tests related to files not found

Looks good, I committed Eric's suggestion. It looks like we're still failing tests related to files not found

I made a fork of this PR and fixed the failed tests in this PR: #794


help center: Remove deprecated mmctl flag from instructions.

--attachments is redundant and should not be used:
$ mmctl export create --attachments
Flag --attachments has been deprecated, the tool now includes attachments by default. The flag will be removed in a future version.

Tiny tweak follow-up to #23644

Is their a minimum Mattermost version for that behavior? We should assume folks exporting are on an old version.

@timabbott These are instructions for exporting from mattermost cloud - so you have to install mmctl https://github.com/mattermost/mmctl on your local computer or something, from which you'll be running the commands - so I think it should be reasonable to assume they'll be grabbing the latest version?
And this new default was added in https://github.com/mattermost/mmctl/commit/4e2542b9ae9e666b8d05a83cf9763b0e4ec36ece release 7.5.1 from Nov 16, 2022, so kinda new

@drrosa What would be your thoughts on this?

@drrosa What would be your thoughts on this?

Hm, it looks like mmctl can be used for a lot of things so I think it's also likely that some users may not be running the latest version when looking to export from mattermost cloud. I think it would be safer to leave the --attachments flag for now. We can drop it from our instructions once the flag gets removed in a future version of the tool and their docs https://docs.mattermost.com/manage/cloud-data-export.html#create-the-export.
That being said, I'm not opposed to removing the flag now since it's already deprecated and it will be removed in the future.

We could add text for the cloud instructions to check you're running at least mmctl 7.5.1 as that's required to get the attachments, if we think that's cleaner/simpler.

@timabbott @drrosa Added a statement about where to get mmctl from (since it wasn't mentioned, so seems useful) and the version requirement. Does that look reasonable?

Looks great, merged, thanks @mateuszmandera!


GitHub Sync

This is an automatically generated pull request.

Closing this as it looks like copybara is trying to re-sync many commits that are already in the repo.


[ART-3476] sign coreos-installer

as requested from ticket, first calculate the sha256sum.txt, then use ump_producer message-digest function get the sha256sum.txt file signed

File sha256sum.txt generated by coreos-installer_sync job can't be read by sign-artifacts job. Both jobs have separate workspaces on separate nodes.
I think options are:

Use a plugin like https://www.jenkins.io/doc/pipeline/steps/copyartifact/#copyartifacts-copy-artifacts-from-another-project
coreos-installer_sync calculates the base64 hash for sha256sum.txt, then pass the base64 hash to sign-artifacts by a parameter.
Follow our current practice to download sha256sum.txt from mirror (https://github.com/openshift/aos-cd-jobs/blob/9b0ed349b24fd452dabcec7c6237a4c5cb646ea2/jobs/signing/sign-artifacts/umb_producer.py#L45), though this is less secure.

Guess this is not the ticket to change the directory structure of this artifact, but it is weird that the s390x artifacts end up in the x86_64 directory.
I think the pattern of uploading to mirror from job 1, and then downloading from mirror from the signing job to compute sha's is not a great pattern. I'd much rather see that the shasum of the shasum256.txt file gets passed along as a parameter to the signing job. I would not be surprised if it would be a requirement that the signing job does not talk to the internet.

Agreed with @joepvd that the current layout of the directory is confusing: all binaries are synced to the x86_64 directory https://mirror.openshift.com/pub/openshift-v4/clients/coreos-installer/latest, which can be resolved to https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/coreos-installer/latest/.
If this PR needs to split the extracted binaries into their corresponding arch-specific directories before syncing to the mirror, we need to make sure the owner knows the change so things will not be broken.
Uploading and downloading sha256sum.txt is definitely not ideal and not secure. I remember we have a JIRA to improve that.

I merged it for now although coreos-installer is not updated very often


a deprecated usage of #name in MCFileTreeStCypressWriter>>#fileNameMapFor:

MCFileTreeStCypressWriter>>#fileNameMapFor: contains on the line 42 a deprecated call on #name. Should be asString

this is not a metacello problem?

It's a FileTree problem. I'll add an issue.

ah, sorry, I have seen this deprecation warning in IceMetadatalessStCypressWrite

solved in Name: SLICE-Issue-19823-exported-source-of-the-package-MonticelloFileTree-Core-in-pharo-core-repository-contains-strange-extension-PavelKrivanek.1
Author: PavelKrivanek
Time: 13 March 2017, 1:09:28.054389 pm
UUID: 4981ea51-fd06-0d00-8993-9cf30b6654c0
Ancestors:
Dependencies: MonticelloFileTree-Core-PavelKrivanek.150, MonticelloGUI-PavelKrivanek.435
make the two packages dirty by simple formating change and solution of a the deprecated #name usage.
(https://github.com/npasserini/iceberg/issues/294#issuecomment-286076547)


Update read me file.

looking at line 3 in the overview section, it should be " It's recommended that users should not " instead of " It's recommended that users not  "
can I make a change to that?

I feel that it's grammatically correct. Dropping "should" from "be" or "have" has different semantics, although the meaning is the same in this case.
I can add the should for clarity.


Intergration spec

Project requirements
N+1 problem is solved when fetching all posts and their comments for a user.

Before fix

After fix

Integration specs

Use Capybara to write integration tests for each view in your project.

User index page:

I can see the username of all other users.
I can see the profile picture for each user.
I can see the number of posts each user has written.
When I click on a user, I am redirected to that user's show page.

user show page:

I can see the user's profile picture.
I can see the user's username.
I can see the number of posts the user has written.
I can see the user's bio.
I can see the user's first 3 posts.
I can see a button that lets me view all of a user's posts.
When I click a user's post, it redirects me to that post's show page.
When I click to see all posts, it redirects me to the user's post's index page.

User post index page:

I can see the user's profile picture.
I can see the user's username.
I can see the number of posts the user has written.
I can see a post's title.
I can see some of the post's body.
I can see the first comments on a post.
I can see how many comments a post has.
I can see how many likes a post has.
I can see a section for pagination if there are more posts than fit on the view.
When I click on a post, it redirects me to that post's show page.

Post show page:

I can see the post's title.
I can see who wrote the post.
I can see how many comments it has.
I can see how many likes it has.
I can see the post body.
I can see the username of each commentor.
I can see the comment each commentor left.

recent changes:

we've fixed the required changes
provided a screenshot of the passing test below,


Add support for additional RHEL Edge image types

A user can now select the RHEL for Edge Container (.tar) image type. This image type supports the optional ostree fields for a parent commit, a ref for the name of the branch, and a url for the parent repository.
The user can also select the RHEL for Edge Installer (.iso) image type. This image type supports the required ostree fields of a ref for the name of the branch and a url for the parent repository.
The help text for the new URL field is Provide the URL of the upstream repository. This is where the OSTree commit will be pulled from. Does this explain what the URL represents?
There are currently no tests for this PR because these image types are not yet supported by osbuild-composer. They will not display for selection until they are supported.

Ignore the selected image type. I had to fake it to check the fields.

This is great! thanks @jkozol!
I wonder about the second screen, should we make the label Parent Repository URL, to make it clear that this is where the parent is taken from, and that we are not actually pushing the container anywhere. Could also put the Parent commit box under the Parent Repository URL one and in the help text say that it will be inferred from the parent repository if left blank.

The help text for the Parent Repository URL should probably be something like Provide the URL of the upstream repository. This is where the OSTree commit will be pulled from. We don't strictly speaking pull in the commit (yet), but this is an implementation detail, and we very well might do in the future.

@teg Would Parent repo URL be descriptive enough? There are some limits on how long the labels can be before they wrap and I would prefer to not override patternfly's default styling for this one.

@teg Would Parent repo URL be descriptive enough? There are some limits on how long the labels can be before they wrap and I would prefer to not override patternfly's default styling for this one.

Maybe just keep it as is and just update the help text?

@teg  Provide the URL of the upstream repository. This parent repository is where the OSTree commit will be pulled from.?

@teg Provide the URL of the upstream repository. This parent repository is where the OSTree commit will be pulled from.?

I think This repository is where the parent OSTree commit will be pulled from.

Closing as this has diverged uncomfortably far from master and rebasing would be more painful than starting off of master.


dnsmasq

dnsmasq cfg
......................
addn-hosts=/etc/dnsmasq.hosts/banner_add_hosts_1
addn-hosts=/etc/dnsmasq.hosts/banner_add_hosts_2
......................

LOG
bad address at /etc/dnsmasq.hosts/banner_add_hosts_1 line 8
FIX
# fe80::1%lo0 localhost
i use raw file bash script
wget -O /etc/dnsmasq.hosts/banner_add_hosts_1 http://sbc.io/hosts/alternates/fakenews-gambling-porn/hosts

Steve @StevenBlack  they keep popping up like 🍄 🍄 🍄  after the 🌧
😉

Hi @imbicile, thank you for this input.
This is a duplicate of #333, which is closed – won't fix.
Closing.

@StevenBlack
I'm using Linux on hosts with multiple adaptors connected to multiple networks, and in that context having interface tags on IPv6 link-local addresses is important. Commenting them out is not an option for me.
Using interface tags in /etc/hosts isn't some weird thing that only MacOS needs: any IPv6 enabled host can wind up needing them, but what's different about MacOS is that it can consult /etc/hosts to identify a default router, so they're a lot more common there.
As noted by RIPE Labs, specifying a source interface is necessary when making an outbound connection to a link-local address, and RFC 4007 specifies that attaching %zone-id tags to IPv6 addresses is the appropriate way of doing so. ("Zone" in this context means the network segment to which an interface is connected, so the usual way to identify zones is by the name or number of the respective interface.)
This means that tagged IPv6 addresses should be accepted in all contexts where the address can be used used to initiate connections; this includes entries in /etc/hosts.
Network tooling applications like ping or nmap have a -I flag or equivalent to specify the source interface or address, but most ordinary applications do not have a way of specifying the source interface, so it can only be controlled by including it as part of the address, and that in turn can only be put in /etc/hosts.
Please reconsider fixing this bug.

Hi Martin @kurahaupo thank you for this.
You know, appending to an issue closed 40-months ago isn't a great way to draw attention to something.
If you feel this is a bug can you please open a new issue, possibly referencing this 3 1/2 year old conversation, and clearly explain how this is a bug, and exactly what you recommend we do to fix this.
Also note that pull requests speak more loudly, and carry more weight, than an issue ever can.


Update requirements

Should we pin everything then?

I guess it wouldn't hurt to. Although it seems a bit too much. There isn't anything that relies on a specific version as far as I can tell.

Well, it's best practice. However, YAPF is changing very frequently, so I am in favor of unpinning that one, as there is no benefit of pinning it if we update it every month.

So maybe pin everything except YAPF ? Would that still be in best practice? I'm not familiar with python packaging best practices.

Well, it's best practice. However, YAPF is changing very frequently, so I am in favor of unpinning that one, as there is no benefit of pinning it if we update it every month.

YAPF was pinned for a reason that different PRs would have different syntax due to different versions being used to perform the feature.  I prefer to keep it pinned so that we all use the same version.

@retr0h I'm fine with it, as long as we update it regularly. Their updates always bring more clarity to the code formatting.

Should we remove all the pinning w/ the exception of YAPF then?

I think we should keep them, and update them once in a while.


Error while building

Hi,
while compiling the Guardian Council simulator and the Guardian Kernels using
./build.sh command, errors are generated. Please see the below image for the error. I am using Ubuntu 16.04 LTS and all the dependencies are installed. Can you help me out with this?

Hi Sukanta,
The issue appears to be that the gem5 simulator we used was compiled on an older GCC that doesn't throw errors of the form
-Werror=class-memaccess
Whereas your newer compiler does.
These warnings can be safely suppressed, by adding the following to the SConscript in the gem5-guardian folder, by adding this line after line 662, with the same indentation as line 662:
main.Append(CXXFLAGS=['-Wno-error=class-memaccess '])
Does that fix the problem?
Thanks,
Sam

Hi Sam,
Thanks a lot for your help.
Yes, it is working. Although, it is showing many other similar warnings, but it can be suppressed following same procedure.
Thanks again.
~Sukanta

Glad to hear it! Incidentally, do you know which version of GCC you were using to compile it? I'll update the Readme to try to fend off the error in future.

My gcc version is: aarch64-linux-gnu-gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
I had to append the following two lines after 662 line in the file /reproduce-asplos2020-gc-paper-master/gem5-guardian/SConstruct
  main.Append(CXXFLAGS=['-Wno-error=class-memaccess'])
  main.Append(CXXFLAGS=['-Wno-error=ignored-qualifiers'])

Great, thanks -- I've added something on troubleshooting to the readme. Are you compiling gem5 to run on an Arm system then, rather than x86?

No, my system is x86_64/Intel. gcc version of my system is 8.4.0. However, the build.sh script uses the aarch64-linux-gnu-gcc for compilation of the files, so I thought the errors might have been generated due to that compiler.
For more information of my system, please see this image,

Ah okay, great, thanks. Yes, it's the newer version of x86's GCC, to compile gem5, that caused the error. Good to know -- presumably this will be quite common -- so thank you for catching it!


INVALID_CLIENT: Invalid redirect URI

Hi,
This is probably a very stupid issue but I have fetched the code, updated app.js client_id, client_secret and redirect_uri
var client_id = 'my client id'; // Your client id
var client_secret = 'my secret'; // Your secret
var redirect_uri = 'http://localhost:8888/callback'; // Your redirect uri

Starting the app in the folder where app.js is located:
:~/Development/Spotify/web-api-auth-examples/authorization_code$ nodejs app.js
Listening on 8888

(Note that it is not node since I am running Ubuntu and there it is nodejs.)

When pressing the "Log in with Spotify" button I get this:

I have made a wireshark log during the transaction but can't make anything out of it.
In another issue was the question raised to test that the server is listening to that redirect_uri which here comes up as:

and running curl:
:~$ curl http://localhost:8888/callback
Found. Redirecting to /#error=state_mismatch
Any ideas?

The issue was to read here instead on a webpage.
I had missed these instructions:

To do so, go to your Spotify for Developers Dashboard and create your application. For the examples, we registered these Redirect URIs:

http://localhost:8888 (needed for the implicit grant flow)
http://localhost:8888/callback

Now it works as expected

it happen to me also ,solution is instead of giving http://localhost:3000 as redirect uri give http://<IP_ADDRESS>:3000,which is obtained at the terminal after running npm start.


Microsoft Whiteboard for Teams

whiteboard.microsoft.com needs to be added to this list. If a customer doesn't have it whitelisted it will prevent it from loading when the app is enabled for use in Microsoft Teams.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 077406d8-bff1-496e-3ea2-b38558fd9355
Version Independent ID: 57db3dec-2250-2dee-fd1a-ec6656911798
Content: Office 365 URLs and IP address ranges
Content Source: Enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @LauraWi
Microsoft Alias: laurawi

@greganth1 Thank you. We're reaching out to engage that engineering team so they can contribute their info to the automated process that generates the info in this topic.

Additional info from Whiteboard team.
Microsoft Whiteboard IP addresses to be whitelisted for Whiteboard:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
TCP Ports 80 and 443 need to be enabled.
The domains are the following:
whiteboard.microsoft.com
wbd.ms
whiteboard.ms


Stylegan without CSE checkpoint link is down

Hi @hukkelas,
The url for fdh_styleganL_nocse.ckpt is down so the configs using it (e.g. anonymizer/FB_cse_mask and FB_cse_mask_face) cannot be used. Could you please provide a way of getting the checkpoint of that model?
Thanks in advance

Same issue, the link which it redirects to: https://folk.ntnu.no/haakohu/checkpoints/deep_privacy2/fdh_styleganL_nocse.ckpt is not working anymore. Please fix @hukkelas