jabref: 5.6 -> 5.7

Description of changes
lockfile is removed. There is no dynamic version used so it's not needed. Downgrade the java version from 18 to 17 since java 18 is not packaged yet (https://github.com/NixOS/nixpkgs/pull/165354). It builds and works well.

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build jabref

@gebner Do you still maintain jabref?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/22

You should also mark "Tested basic functionality of all binary files (usually in ./result/bin/)" in your PR. You said you tested it and verified the basic functionality?

Your commits https://github.com/NixOS/nixpkgs/commit/6ce2b1a950d97064546b119b76b71e039bec5c42 and https://github.com/NixOS/nixpkgs/commit/c9af52f43ccfe5d71da18d3c7b3d5abc5df8134c not relate to jabref

What do you mean?

Error on my side during working with your branch. Sorry, I'll delete the comment.

@SuperSandro2000 ping 4 merge


Update Horizen (ZEN)

Currency name: Horizen
Symbol: ZEN
Website: https://www.horizen.global/
Theme color: #0e9de5
Logo (SVG): Horizen_logos_SVG.zip

What's to update? We already updated it last year: https://github.com/atomiclabs/cryptocurrency-icons/issues/237

// @bagintz

Hello @ldevalliere I'm in charge of this repo now and looking at this—is this issue still relevant? If not please provide me with the current SVG file and color. Thank you.

Yes, still relevant.
Issue: https://github.com/spothq/cryptocurrency-icons/blob/master/svg/color/zen.svg is not in color.
Solution: "Horizen_logomark.svg" inside of the zip file in top comment provided above is in color.

Done.


Simplify doc hero colors and use "sky" accent color for collection pages

Bug/issue #, if applicable: 90502658
Summary
This simplifies the new documentation hero to only utilize role data when determining the accent color used for the enhanced background.
The "sky" accent color should be used for top level collection pages and the "teal" accent color should be used for other high level pages like API collections, articles, and sample code.
Testing
Steps:

Configure the VUE_APP_DEV_SERVER_PROXY=https://ethan-kusters.github.io/swift-argument-parser env var and run the dev server with npm run serve
Open http://localhost:8080/documentation/argumentparser and verify that the --accent-color CSS property for the hero is --color-type-icon-sky
Open http://localhost:8080/documentation/argumentparser/gettingstarted and verify that the --accent-color CSS property for the hero is --color-type-icon-teal

(Or use any other documentation archive to test with.)
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[X] Added tests
[X] Ran npm test, and it succeeded
[X] Updated documentation if necessary

So we no longer want the Module icon on the root of the documentation? The changes themselves make sense and produce what they are expected, I am just not sure about this change.

Nope, you're right. I didn't mean to change the icon as well—only the colors—that was just a mistake. Fixed with 8aa76a4a45f724ec8fb67aaa34bac61501d0ad90

Funny that we use the CollectionIcon for anything that we cant match, but not the collection type 🤣

Yeah, mostly just an issue with how we've named things, using Collection and APICollection to mean different things (but they sound so similar and the icon for APICollection was named CollectionIcon)
I definitely agree that it's funny though 😅

@swift-ci test


unique id

what is the uniqeid
it fixed in all sessions?
i can view it in mail source

@lea-top, I'm not sure which uniqueid you are asking about...
The UID for email messages is generated by the IMAP server when a new message is received.  The S22.Imap ImapClient does not have any control over that value.  You might want to read through section <IP_ADDRESS> of RFC 3501 for the details.[1]
The UID of a mesage is fixed in all sessions and for all time.  It is assigned at the time the message is created in a particular mailbox, and it NEVER changes.
You seem to ask "Can I view it [the message UID] in mail source?"
You will receive the UID when you call StoreMessage(), StoreMessages(), or Search().  UID's are just uint, so you can view them.  You also receive UID's if you register event handlers for the MessageDeleted or NewMessage events.
The UID is not stored in the "mail source".  (I am assuming you mean the body of the email message as transmitted over the wire.)
If you are asking about some other "mail source" please help me understand where you are thinking about.
[1] https://tools.ietf.org/html/rfc3501#section-<IP_ADDRESS>


Revert "cilium: Ensure xfrm state is initialized for route IP before …

This reverts commit https://github.com/cilium/cilium/commit/c9ea7a52bd59c167c6e7611d4976e3c041f4e7f0.
This works around a condition where restarting the agent uses a new
IP for Cilium Internal IP. But, it turns out this is because of an
incorrect set helm chart option in our reproducer. When configured
correctly we require CiliumInternalIP to reused so this patch is not
necessary. In fact it complicates the code so lets drop it.
The helm option is cleanState. It must be set to false
cleanState=false
Note that cleanState="false" is a string type and will default to
true because of bool typing. Creating a subtle and broke config.
Signed-off-by: John Fastabend<EMAIL_ADDRESS>

/test


feature(Analysis/Normed/Module/Dual): Lemma used in proof of Banach-Dieudonneé theorem

Adds a lemma implicit in the proof of Bourbaki, TVS IV.24, §5 Theorem 1 (Banach-Dieudonneé theorem)
(See also Lemma 12.2 from Conway, A Course in Functional Analysis for the Banach space version).

Thanks!
bors merge


fftw3 + fftw3_f03 : add in-place r2c and c2r transforms

This PR is currently a draft. It is a POC showing in-place r2c and c2r is possible, at least for the fftw3 and fftw3_f03 backends.
Serial tests on a workstation show performance loss (~20%) for physical_in_x and performance gains (~3% for r2c and ~18% for c2r) for physical_in_z.
More testing is needed. The main advantage of in-place transforms is to remove the working array wk13 and to reduce the memory footprint.The best solution is probably to make in-place r2c and c2r transforms optional when the OVERWRITE flag is present. The code calling would then select

data structure (physical_in_x or physical_in_z)
in-place r2c and/or c2r when the OVERWRITE flag is present

Serial tests using a 12_x12_x128 grid in the physical space :

| r2c_x | c2r_x | r2c_z | c2r_z |   | x, r2c + c2r | z, r2c + c2r
-- | -- | -- | -- | -- | -- | -- | --
master, fftw3_f03 | 0.16 | 0.18 | 0.25 | 0.31 |   | 0.34 | 0.55
master+overwrite, fftw3_f03 | 0.15 | 0.16 | 0.24 | 0.28 |   | 0.31 | 0.52
master, fftw3 | 0.15 | 0.18 | 0.24 | 0.30 |   | 0.33 | 0.54
master+overwrite, fftw3 | 0.15 | 0.15 | 0.24 | 0.28 |   | 0.31 | 0.52
PR, fftw3_f03 | 0.15 | 0.18 | 0.24 | 0.30 |   | 0.33 | 0.54
PR+overwrite, fftw3_f03 | 0.19 | 0.19 | 0.23 | 0.22 |   | 0.37 | 0.46
PR, fftw3 | 0.15 | 0.17 | 0.24 | 0.30 |   | 0.33 | 0.54
PR+overwrite, fftw3 | 0.19 | 0.19 | 0.23 | 0.23 |   | 0.38 | 0.46
  |   |   |   |   |   |   |
master, fftw3_f03 | 1.03 | 1.15 | 1.01 | 1.11 |   | 1.09 | 1.07
master+overwrite, fftw3_f03 | 1.00 | 1.00 | 1.00 | 1.00 |   | 1.00 | 1.00
master, fftw3 | 1.00 | 1.12 | 1.00 | 1.10 |   | 1.06 | 1.05
master+overwrite, fftw3 | 1.01 | 0.99 | 1.00 | 1.01 |   | 1.00 | 1.00
PR, fftw3_f03 | 1.01 | 1.12 | 0.98 | 1.08 |   | 1.07 | 1.03
PR+overwrite, fftw3_f03 | 1.21 | 1.21 | 0.97 | 0.81 |   | 1.21 | 0.88
PR, fftw3 | 1.00 | 1.12 | 0.99 | 1.10 |   | 1.06 | 1.05
PR+overwrite, fftw3 | 1.21 | 1.24 | 0.97 | 0.82 |   | 1.22 | 0.89


[google chrome]  open with chrome dev?

Extension
https://www.raycast.com/Codely/google-chrome
Description
I use the dev build and it's not picked up as chrome by the extension.
Steps To Reproduce
No response
Current Behaviour
No response
Expected Behaviour
No response

+1. I'm using the dev build of Chrome and the extension does not pick it up.
Might have to time to take a look at the code later but for now I'm only reporting this.


unknown is not assignable to the union of all other primitives

TypeScript Version:  3.9.0-dev.20200328

Search Terms: unknown union not assignable, exclude unknown
Expected behavior: At least one of the two below to not error out
Actual behavior: Both error out

Related Issues: #35221, although solving that isn't a hard requirement
Code
type FakeUnknown1 = undefined | null | void | boolean | number | bigint | string | symbol | object;
const test1: FakeUnknown1 = 0 as unknown;

type FakeUnknown2 = undefined | null | boolean | number | bigint | string | symbol | object;
const test2: FakeUnknown2 = 0 as unknown;

Output
const test1 = 0;
const test2 = 0;

Compiler Options
{
  "compilerOptions": {
    "strictNullChecks": true,
    "target": "ES2020",
  }
}

Playground Link: Provided

What's the use-case for this?

In my case, it's so I can use Exclude<unknown, X> without issue. One case where I need it is in a proof of a few type-level invariants (so I don't have to fuzz test it as heavily):
type AnyNonSpecialObject =
    | Exclude<Maybe<Any>, object>
    | Array<AnyNonSpecialObject> & {"%"?: Exclude<Maybe<Any>, number>}
    | object & {"%"?: Exclude<Maybe<Any>, number>}
export type __TestVnodeAny = Assert<AnyNonSpecialObject, Vnode>
export type __TestAttributeUnionNonPrimitiveTypeIdentifierIsAny =
    Assert<Maybe<Any>, VnodeAttributes["%"] | VnodeNonPrimitive["%"]>
export type __TestFunctionsAreNotValidVnodes =
    Assert<Is<(...args: Maybe<Any>[]) => Maybe<Any>, Vnode>, false>
export type __TestConstructorsAreNotValidVnodes =
    Assert<Is<new (...args: Maybe<Any>[]) => Maybe<Any>, Vnode>, false>

For context:
type Maybe<T> = T | null | undefined
// `FakeUnknown2` is as per the above
type Any = Exclude<FakeUnknown2, null | undefined>

It'd be nice to not have to roll my own Any type here, and BTW, if I replace the Maybe<Any> with unknown here (and within Vnode as appropriate - I've omitted it for brevity as it's over 200 lines of pure type-level code excluding comments), the proof fails.

This is kind of confusing since the world of known types depends on target and will probably expand in the future. In a true interpretation of unknown we also have to include kinds of values that haven't been invented yet, I think -- technically hosts are already allowed to invent their own.

So in other words, I'm stuck until negation types come into existence?

Welp, I guess I'm stuck with my current solution.


UI issue : (Paint , Write) Activity

Hey @llaske
I have found a UI issue in various activities popup search bar is not properly aligned.
For reference I have attached screenshots for the same, please look and review them and give me your thoughts.
Paint Activity:

Write Activity:

No. It's the standard way to display popup in Sugar UI.

ok @llaske


[Feature] Freeze Table Columns

Summary
Would like to be able to freeze table columns like Excel.
Motivation
Keeps important data in the table while you scroll right.

@tlawrence-TAG thank you for the feature request!

Duplicate of  #3265


biosdrain 2.0.0 doesn't even load up on SCPH-70004 and SCPH-75004

Just tried biosdrain v2.0.0 with multiple USB on Sony PS2 SCPH-70004 and SCPH-75004 (both PAL) using uLaunchELF 4.43a.
Got a black screen without nothing else when launching it
Got to use v1.0.0 to dump bios correctly

Thanks for the report. I've turned 2.0.0 into a prerelease and the latest release is now back to 1.0.0.
Sorry for the inconvenience, I'll get to bug hunting :sweat_smile:

It's okay !
Hit me up if when you will have fixed it so I can test it and give you feedback again if needed
Good luck with it

If anyone is curious, I've got the black-screen issue figured out, but the IOP toolchain has a regression that prevents the sysman IRX from loading. I'm awaiting for a fix there before I can test it properly and provide a working release :face_exhaling:

Can you try this latest release?

I tested the 2.0.2 instead of 2.0.1
It worked on both PS2 !


feature: Adding a next button for watching the next video in the thread.

Problem description
I'm always frustrated whenever I finish watching a video I always search for the next button so that I can jump over to  video in the order. For eg :
If I am on 3.1 video, a button which on click takes us to 3.2 will be very helpful to make it more userfriendly.
Also

I am watching this video the side bar does not shows which week or video is selected. This feature will help tackle that problem as well
Solution
A solution can be linking the videos with each other (maybe use doubly linked list which can have prev and next as well . We can add a prev link as well (maybe not needed) but can add that as well.
All the video be sorted week wise and contains a prev button to go to prev video i.e if you are on video 8.2 prev will take you to 8.1
and A next link which takes us to 8.3 .

working on this

@hkirat @devsargam upon inspection, i found there was already a function getNextVideo. i wonder why it wasnt used?


Translation errors when choosing the target projects for multicluster apps

Version: v2.3-head
UI Index: https://releases.rancher.com/ui/latest-2.3/index.html
Steps:

Create 2 DO clusters
At the global level , click on Apps . Launch a catalog and choose the "Target Projects"  from the dropdown
The translation is lost for the "Target Projects"

Available in latest-2.3.

This issue is not seen when testing with latest v2.3-head  and UI Index: https://releases.rancher.com/ui/latest-2.3/index.html


Removing sources from the middle causes Anki to crash

Seen in Merge #9, there is an issue with removing sources leading to a crash unless removing from the end of the list.
@B0sh previously proposed a fix in Pull request #7, which fixed the issue, but this had a new issue where adding a source would add with the same number as the last source of the list, leading to duplicate source numbers.
Would like to find a fix that solves both issues, looking at the logic of the #7 implementation seems like a good hint towards solving this.

Fixed by #14


sendMessage message id is too huge

I'm sending message using:
await client.invoke({
  _: 'sendMessage',
  chat_id: chatId,
  input_message_content: {
    _: 'inputMessageLocation',
    location: {
      _: 'location',
      latitude: latitude,
      longitude: longitude,
    },
    live_period: 60,
    heading: heading,
    proximity_alert_radius: proximityAlertRadius,
  },
});

And got the following response:
{
  _: 'message',
  id:<PHONE_NUMBER>865,
  sender_id: { _: 'messageSenderUser', user_id: 707334 },
  chat_id:<PHONE_NUMBER>,
  sending_state: { _: 'messageSendingStatePending', sending_id: 0 },
  is_outgoing: true,
  is_pinned: false,
  can_be_edited: false,
  can_be_forwarded: true,
  can_be_saved: true,
  can_be_deleted_only_for_self: false,
  can_be_deleted_for_all_users: true,
  can_get_added_reactions: false,
  can_get_statistics: false,
  can_get_message_thread: false,
  can_get_viewers: false,
  can_get_media_timestamp_links: false,
  can_report_reactions: false,
  has_timestamped_media: true,
  is_channel_post: false,
  is_topic_message: false,
  contains_unread_mention: false,
  date:<PHONE_NUMBER>,
  edit_date: 0,
  unread_reactions: [],
  message_thread_id: 0,
  self_destruct_in: 0,
  auto_delete_in: 0,
  via_bot_user_id: 0,
  author_signature: '',
  media_album_id: '0',
  restriction_reason: '',
  content: {
    _: 'messageLocation',
    location: {
      _: 'location',
      latitude: -7.962716,
      longitude: 112.6201,
      horizontal_accuracy: 0
    },
    live_period: 60,
    expires_in: 60,
    heading: 90,
    proximity_alert_radius: 100
  }
}

However, on the receiving end of the bot, the highest message ID is still under 800.
Am I doing something wrong? Sorry for opening ticket if this has already been discussed before, I can't find an appropriate telegram/discord group to discuss this.

This is messageSendingStatePending
You should wait for
messageSendingStateFailed
Or
messageSendingStateSecsses

Aaaah I see. Did not noticed that.
Thank you🫡


Wallet Balance in ATM Mode

It would be useful to have the wallet balance available in ATM mode so one could see how many sats he has available to sell.  This way the seller could avoid errors due to trying to sell more than he has.

TPoS doesn't have wallet access! It's tricky to pull the balance from the wallet, and may pose some privacy issues.
@arcbtc ?

I don't think we want this. If you want to check the wallet balance, you can do it in the main LNbits view.


Send didOpen requests after LS crashed

I've reported the same issue over at https://github.com/Microsoft/vscode-languageserver-node/issues/304, but haven't gotten any reaction for more than three weeks, so trying here again :)
Direct quote from the other issue:

This is the scenario: I have VS Code open, with a file open with unsaved changes. Now my language server crashes for some reason. VS Code restarts my language server. New LS instance starts up, but as far as I can tell this new instance never receives a didOpen request with the content of the unsaved file that is open in the editor. So now the state in the editor and the LS have diverged: my LS doesn't know about the unsaved edits in the file.

So I guess one option would be that VS Code sends a didOpen request when it restarts a LS after a crash for all open files.

Or is there some other way we should handle that?

This issue (bug?) is causing some serious problems in the julia language extension and we don't know what the correct way to handle it is.
Any feedback, comment would be greatly appreciated!

@dbaeumer would be fantastic if we could get some response on this eventually, and even if it is "I don't have time to look into this for the next x weeks", then we could at least move forward with the julia extension. Right now our next release is blocked because of this issue.

Sorry, I was out on vacation and very busy with other stuff for the Jan. release. Will comment on the original issue in the LS repository.

Cool, thanks! And sorry to be ungeduldig :)


Update Bag docs

@cowlicks, I would enjoy hearing about what in this could be improved or what questions you have after reading.

Looks good. Travis failure is another hang in test_worker.test_compute. I restarted it.


Update BlockFetcher.cs

_LastSaved should be updated with  DateTime.UtcNow and not DateTime.Now to be consistent with the rest of the checkpoint save functions

Sorry for the delay, I forgot to watch the Indexer project on github.


Enhancement issue #3

Example of use:
SimpleText.from(text)
            .pattern(Pattern.compile("myPattern", Pattern.CASE_INSENSITIVE)).textColor(...)
            .pattern("myPattern1", "myPattern2").textColor(...)

@jaychang0917redso Can you generate a new version?

@jaychang0917 I would love to see this merged also


Only upload results to S3 when tests fail

These changes make the pipeline to only upload the test logs to S3 when tests fail. Before this, logs wouldn't be uploaded when tests fail.

 Is that not the case?

Apparently, when is only allowed in finally when using tektoncd/pipeline v0.21.0, and we use v0.20.0. I'll see how to upgrade.


Couple filters issues

The elements shown within select for foreign key (like Event.site or Event.organizer) should be ordered by name, not by database ID

Default ordering for All Events page should be "soonest first"

Add filtering by roles to the All Persons page (requires adding explicit relationship Person↔Role through Task; we can consider adding Person↔Event through Task, too)

On 2015-06-22 10:15 AM, Piotr Banaszkiewicz wrote:

Default ordering for All Events page should be "soonest first"

Where are past events shown?  Under all upcoming events?

Add filtering by roles to the All Persons page (requires adding
explicit relationship Person↔Role through Task; we can consider
adding Person↔Event through Task, too)

Do you understand @gperu's use case for this?

Where are past events shown?  Under all upcoming events?

Good question. In a simplest case we would only use "distance" from the current date and sort by it. This would probably mean upcoming and past events intertwining.

Do you understand @gperu's use case for this?

I think it's:

New person comes, and they want to teach at a workshop. So I need to be able to know about their past: if they were helping or teaching, or none.

I think his use case is easily solved by looking at the person details page.

On 2015-06-22 10:33 AM, Piotr Banaszkiewicz wrote:

Where are past events shown? Under all upcoming events?

Good question. In a simplest case we would only use "distance" from
the current date and sort by it. This would probably mean upcoming and
past events intertwining.

Strong -1 on that (it would be confusing as hell).  I think "upcoming
only" as a filter (perhaps on by default?) accomplishes what Giacomo wants.

Do you understand @gperu <https://github.com/gperu>'s use case for
this?

I think it's:
New person comes, and they want to teach at a workshop. So I need
to be able to know about their past: if they were helping or
teaching, or none.

I think his use case is easily solved by looking at the person details
page.

I agree.
--
Dr. Greg Wilson    |<EMAIL_ADDRESS>Software Carpentry | http://software-carpentry.org

Strong -1 on that (it would be confusing as hell). I think "upcoming only" as a filter (perhaps on by default?) accomplishes what Giacomo wants.

Okay. Good idea.

bump

This is marked as 0.7. Do you need it in 0.6?

Nope, just wondering if we need further discussion.


Fix robocop stopping when trying to resolve source from relative path

Closes #244

I've tested it manually in WSL and I was able to reproduce the bug (and fix it with this code change). We will need to extend our tests by test for this bug.


[Suggestion] Add rule "no-static-members" to disallow usage of static class members

Please add rule like "no-static-members: true" to disallow usage of static class members.
This restriction will be very useful for teams/developers who tries to avoid static methods in their code.
I think it should work for public static and static protected members. Probably it should allow private static members.
Allow
Class-level constants (static properties marked as readonly):
public static readonly DEFAULT_CAPACITY: number = 100;

protected static readonly PROTECTED_PROPERTY_KEY: symbol = Symbol();

private static readonly PRIVATE_PROPERTY_KEY: symbol = Symbol();

Also there are specific static methods that returns instances of class they defined on:

named constructors
factory methods

I think such methods should also be allowed because:

there is not support of multiple constructors
static methods that creates class instances allows to keep incapsulation

To detect such methods it's enough to check type of method's return value.
export class SomeService {
    private static _instance: SomeService;

    public static getInstance(): SomeService {
         // get or create singleton
    }
}

const klass: Class = Class.of(SomeService);

Disallow
All other static class members - methods, accessors, properties without readonly modifier etc

Allow

Class-level constants (static properties marked as readonly):

public static readonly DEFAULT_CAPACITY: number = 100;

protected static readonly PROTECTED_PROPERTY_KEY: symbol = Symbol();

private static readonly PRIVATE_PROPERTY_KEY: symbol = Symbol();

Protected and private static methods

Disallow
All other static class members - methods, accessors etc

Ha, this seems like it would be a very contentious rule. Some folks would argue that, under some codebases, it's preferable to group constructs directly onto the classes they're logically associated with. Others would argue that you shouldn't ever have classes in the first place.
Maybe this should go into tslint-microsoft-contrib instead?
/cc @adamtreineke because we've spent a few afternoons screaming at each other over this.

Hi @JoshuaKGoldberg!

this seems like it would be a very contentious rule

I cannot agree with you in this. In object-oriented programming static method considered bad practice:

Static methods represents global shared state
Static methods are hard to mock and test
Static methods breaks encapsulation

Keeping this in mind developers should avoid creating and using static methods.
Here is nice article explaining why developers should avoid static methods.

Some folks would argue that, under some codebases, it's preferable to group constructs directly onto the classes they're logically associated with.

You're right. As I know, all rules can be enabled or disabled. I think those guys may ignore this rule if they have good reason. But again, in true object-oriented programming static methods are source of many problems. There are only few reasons to use static members: for example, to create util class which extends some of default types for example, some kind of StringUtils with additional methods not present in language specification, or Assert with assertion methods (they never encapsulate any state so it's okay to make them static).

Oh, I personally agree with your points and would absolutely push to enable this rule in my projects. The issue is not whether this is a good suggestion, but rather whether it's too opinionated or tied into a particular line of thought. Can it be made generic enough to justify being in TSLint core? More specifically: how can this rule be constructed to (mostly) flag the really bad uses of statics while (mostly) allowing the reasonable ones? If this is to get into TSLint core without first being in tslint-microsoft-contrib or another repository, it should safely fall into that safe space.
As prior art, no-unnecessary-class exists in TSLint core because the extra class it guards against is purely bloat with approximately no benefit. One could just use exported functions or an {} object literal in pretty much all cases (oversimplified, but vaguely accurate).

Thank you for more detailed explanation, Josh.
For me, the proposed rule is "on the same level of abstraction" as member-access, prefer-const and prefer-readonly. They all designed to make code more predictable and safe.
If you say that it's good practice to put new rules into separate project, I will trust your expirience.
Here are code samples to look at the whole picture:
export class Demo {
  // ALLOW static read-only property (aka constant)
  public static readonly VALUE: number = 0;
  protected static readonly VALUE: number = 0;
  private static readonly VALUE: number = 0;

  // FORBID static getters and setters
  public static get someProperty() { /* return value */ }
  public static set someProperty(value) { /* save value */ }
  protected static get someProperty() { /* return value */ }
  protected static set someProperty(value) { /* save value */ }
  private static get someProperty() { /* return value */ }
  private static set someProperty(value) { /* save value */ }
}

export class Class {
  // ALLOW - named constructor
  public static of(type: Type): Class { /* get class reflection */ }
  // FORBID - no encapsulation, not a named constructor
  public static getName(klass: Class): string { /* get class name */ }
}

tsconfig.json
As for rule configuration format, I see it like this:
Enable rule. In this case linter should emit errors for static getters, setters and methods whose are not a named constructors.
{
  "no-static-members": true
}

Disable rule
{
  "no-static-members": false
}

Two additional thoughts came to my mind:

This rule requires type information to check static method return type
Allowed return type of static method should be equal to current class and not equal to any subclass or superclass.

Examples of named constructors:
class Promise {
  public static all(promises: Array<Promise>): Promise<any[]>
  public static resolve<V>(value: V): Promise<V>
  public static reject(error: any): Promise<never>
}

class Class {
  public static of(type: Type): Class;
}

Note: per #4534, this issue will be closed in less than a month if no PR is sent to add the rule. If you really need the rule, custom rules are always an option and can be maintained outside this repo!

💀 It's time! 💀
TSLint is being deprecated and no longer accepting pull requests for new rules. See #4534. 😱
If you'd like to see this rule implemented, you have two choices:

Recommended: Use typescript-eslint to lint your TypeScript code with ESLint ✅
Legacy: Write it as a custom TSLint rule 🤷♂

👋 It was a pleasure open sourcing with you!
If you believe this message was posted here in error, please comment so we can re-open the issue!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Data Minimization for Protection Against Misuse of KYC Data

Colleagues,
I am opening this issue in order to address the topic of how we can better protect the KYC Match/Fill-in APIs against misuse targeting to information phishing. Applying the data minimization principle, as described in EU GDPR and other relative regulations, can be of help to this direction.
A first idea/proposal is to establish a process during the onboarding of new Service Providers and/or New Services, where it will be agreed which KYC data fields are allowed to be exchanged, depending on the specific User Case requirements. This is already happening in many markets.
Then a mechanism that will enforce such agreement needs to be implemented. As discussed, such mechanism(s) are already in place in some "local" implementations. Whether such mechanism should be defined within our specifications needs to be discussed and decided. If yes, scopes can be used to define specific sub-sets of data fields allowed per scope, and SP access to KYC info can be limited to the specific scopes that will be allowed for each UC as required.
As mentioned in our call, this topic is under discussion also in ID & Consent sub-group, thus we should ensure that we are aligned with this discussion as well. However we also need to distinguish the topics of end-user consent for providing specific personal data and the "general" eligibility of an aggregator/service provider to request and get the specific kind of data.
Your feedback and comments are welcome.
Efthymis Isaakidis

hi @EfthymisIsaakidis-DTCS, at Orange we've recently discussed about an Eligibility API allowing a partner for example to know what kind of service/data a developer is eligible before requesting the CAMARA API.
I wonder if this kind of service could not be a solution not only for scopes of data.
Thanks
Gilles

Hi @EfthymisIsaakidis-DTCS
For Match and GDPR it really depends what legal basis is applicable for the use case.
In case of user consent, you will need to inform the user when asking for opt-in what data is requested. The user can then decide whether they provide the data or not.  If you really want to make it fancy, you can make a distinction between which fields are considered mandatory, and which are optional (and which the end user can decide to include or not).
For other legal basis, like legitimate interest which is often selected in case of fraud prevention, you can agree during the onboarding what data should be included. If the merchant asks in an API call more than agreed, you can simply reply with N-NA for that attribute, since that attribute is not available for the agreed use case.


[0.5] Backport of PR 109 - [merged]

In GitLab by @wtbarnes on May 17, 2021, 05:50
Merges cherry-pick-6a86ebae -> 0.5
Pull from sunpy main branch for devdeps
Closes #104
See merge request LMSAL_HUB/aia_hub/aiapy!109
(cherry picked from commit 6a86ebae3cf039335c600ba130fffb0cb14bee57)
8a3f723b pull from sunpy main branch

In GitLab by @wtbarnes on May 24, 2021, 12:03
added 3 commits
4f83313a...21346193 - 2 commits from branch 0.528f5ffbd - Merge branch 'ci-dev-deps' into 'master'
Compare with previous version

In GitLab by @wtbarnes on May 24, 2021, 12:14
mentioned in commit 1ed2d405a307622f222e1d052e61c15a7d15936b

In GitLab by @wtbarnes on May 24, 2021, 12:04
enabled an automatic merge when the pipeline for 28f5ffbdc3e5a0c52a2af8758b3640e5721fc759 succeeds

In GitLab by @codecov on May 24, 2021, 12:10
Codecov Report

Merging #110 (28f5ffb) into 0.5 (2134619) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              0.5     #110   +/-   ##
=======================================
  Coverage   97.23%   97.23%
=======================================
  Files          15       15
  Lines         470      470
=======================================
  Hits          457      457
  Misses         13       13

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 2134619...28f5ffb. Read the comment docs.


"typescript.suggest.enabled": false still shows TypeScript suggestions if cache was once initiated

VSCode Version: 1.51.1
OS Version: macOS 10.15.7

Steps to Reproduce

Open a JavaScript file which imports a project which has types on DefinitelyTyped:

import { Box } from 'gestalt';

const Modal = () => {
  return (
    <Box bottom />
  )
}

Hover over bottom
Show you the TypeScript types
Set "typescript.suggest.enabled": false
Reload (CMD+R) or restart VSCode
Hover over bottom
Still shows the TypeScript types

Current Workaround
Delete the TypeScript cache

Set  "typescript.suggest.enabled": false
Remove TypeScript cache: rm -rf ~/.cache/typescript/4.0/node_modules/@types/gestalt/
Hover over bottom
TypeScript types don't show up

This is less than ideal since:

The cache automatically gets populated for any project/workspace that imports the library and does not have "typescript.suggest.enabled": false set
We have to ask our developers to perform this manual step each time

Other Notes

Does this issue occur when all extensions are disabled with code --disable-extensions?

Yes, since this does not disable the built-in vscode.typescript-language-features

Our team uses Flow types so we would like to disable the TypeScript suggestions for our project

For JS files you should use javascript.suggest.enabled.
Could you please clarify what initial problem you want to solve with removing these types?
Why not instruct users to put "typescript.disableAutomaticTypeAcquisition": true into their settings.json for projects?
Or if they have jsconfig.json to put there typeAcquisition.exlude?
{
  "typeAcquisition": {
    "exclude": ["gestalt"]
  }
}

@IllusionMH "typescript.disableAutomaticTypeAcquisition": true, is exactly what we needed, thank you!

Could you please clarify what initial problem you want to solve with removing these types?

The initial problem we were trying to solve is the CMD+click on a prop would always open a modal where we still had to choose between TypeScript and Flow, instead of directly taking you to the flow type

Now, with "typescript.disableAutomaticTypeAcquisition": true, we no longer have that issue and it directly takes us to the type:

If yoy are going to use Flow instead of TS it's recommended to desable built-in TS extension for this workspace to avoid conflicts between two language services. See https://marketplace.visualstudio.com/items?itemName=flowtype.flow-for-vscode#setup
https://code.visualstudio.com/Docs/languages/javascript#_can-i-use-other-javascript-tools-like-flow
And linked instructions: https://code.visualstudio.com/docs/nodejs/working-with-javascript#_disable-javascript-support
Even with ATA disabled, some of modules in project might bring @types/* modules in their devDependencies and TS might use those.

@IllusionMH thanks - we already had the following options set to disable the TypeScript integration but the suggestions still showed up:
"javascript.validate.enable": false,
"typescript.validate.enable": false,

Is there a way to programmatically, without each developer having to manually follow these steps, disable the vscode.typescript-language-features extension? We're trying to make their setup as seamless as possible.

I'm not aware of any.
Looks like request for this API was declined #15466, but #40239 might help if implemented.
Disabling TS should be only done once per workspace which shouldn't be hard.


Fixed migration guide request.ParseFromRequest example code

Seems to be a small copy/paste error with the function arguments and Claims.

Thanks! I'll review when I return from vacation on Monday.
-dave

On Jul 19, 2016, at 10:18 AM, Zai Chang<EMAIL_ADDRESS>wrote:
Seems to be a small copy/paste error with the function arguments and Claims.
You can view, comment on, or merge this pull request online at:
https://github.com/dgrijalva/jwt-go/pull/151
Commit Summary
Fixed migration guide request.ParseFromRequest example code
File Changes
M MIGRATION_GUIDE.md (5)
Patch Links:
https://github.com/dgrijalva/jwt-go/pull/151.patch
https://github.com/dgrijalva/jwt-go/pull/151.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

thanks


How to deep copy checkpoint.model ?

I am trying to copy checkpoint.model (in sample.lua file) into another variable and then I want both the variables to perform independently (basically I need a way to deep copy).
I tried many ways, including this: [(https://gist.github.com/tylerneylon/81333721109155b2d244)]
But, some of the variables have datatype userdata in checkpoint model, and because of this I am not able to perform of deep copy.
Can anyone please suggest a way how to perform that ?

An easy way to get a deep copy of anything in Torch is to serialize and deserialize the same object:
local model_copy = torch.deserialize(torch.serialize(model))

@already-taken-m17
@jcjohnson
After training a model, I find the training epoch seems not enough, so I reload it and try to finetune(retrain), but why the training loss seems like the beginning training loss, just like I am training it from scratch? I saver the model using
local model_copy = torch.deserialize(torch.serialize(model))
and torch.save('model_dir',model_copy)
Help?


Investigate PyScaffold

https://pyscaffold.org/en/stable/index.html
Compare / contrast design decisions and features.

Also:

https://github.com/pydanny/cookiecutter-django
https://github.com/skorokithakis/django-project-template


e2e: fix support_archive tests

Description
Fix e2e tests.
How can this be tested?
make test/e2e/supportarchive
Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

I've ran it in my cluster and it worked.


Fixed documentation in util package.

Corrected copy/pasta.

Coverage remained the same at 100.0% when pulling 63ced47a154cc254c26a3b2051e3c5981bda64ab on feature/doc_fix into b0df5a17d8c20a81ee8466a62007ab7c75e33c64 on develop.


Multi instance support - clarification needed

HI,
i have specific requirement that i need to run two instances of IOT for the supporting two different region with this SDK.
For example i need to support for EU and AU. Is the multi instance Support present?
Thanks in advance for your info!

Hey @sakthisg ,
not really sure what you mean here...I'm kind of guessing that you want the same thing to be on 2 regions at once? In which case no, a device is set on a region.
If that is not the question please be a bit more specific on what is you're trying to do and what is the expected behavior?

With this IOT SDK,Say i have two applications A and B - A is for region EU
and B is for region LT. Will the thing present in both the region? Will the
IOT registeration done for both the regions?
On Wed, May 20, 2020 at 1:58 AM Gilberto Lopez Zayas <
<EMAIL_ADDRESS>wrote:

Hey @sakthisg https://github.com/sakthisg ,
not really sure what you mean here...I'm kind of guessing that you want
the same thing to be on 2 regions at once? In which case no, a device is
set on a region.
If that is not the question please be a bit more specific on what is
you're trying to do and what is the expected behavior?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-iot-device-sdk-cpp/issues/186#issuecomment-631064094,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHP2WXYZKOLOYFFJANWJRMTRSLTWNANCNFSM4M3MVT3Q
.

i am getting errors when i try to setup IOT. Network is working fine(Youtube and other application works). What is the reason for getting timed out?
The MQTT request timed out : SDK Code -703. waitInSecs: 60
Exiting Thread MQTT Keep alive Action!!
Successfully Exited Thread MQTT Keep alive Action!!
Exiting Thread TLS Read Action Runner!!
Successfully Exited Thread TLS Read Action Runner!!
Exiting Thread Outbound Action Processing!!
Successfully Exited Thread Outbound Action Processing!!

The issues are related to time zone hence closing this.


Implemented skip violations

Initial implementation of #199

[x] Implementation
[ ] Tests

thanks for trying to make deptrac better,
i am unsure about this PR. I would agree that we need some way to skip violations but there are a bunch of issues with this approach.
when i wrote deptrac i had the idea that a dependency is something abstract. in fact  we (mostly) use deptrac on the "class"-level but if we think further dependencies has nothing to do with classes.
for example we could write a npath collector that collects every function that is "too complex". than you could write a rule to prevent some parts of your code to prevent on too complex code. You would end up with a dependency between (may) 2 functions, not classes.
skip_violations is only build on class level.
atm. i am unsure about how to solve this issue but i guess the approach is not generic enough.

@timglabisch agree with you.
Talking about classes and functions. I can change the configuration format to support both functions and classes to avoid configuration BC breaks. Or it might be improved in future releases until \SensioLabs\Deptrac\DependencyResult\DependencyInterface supports only classes.
When you integrate DepTrac in CI/CD with large code base (our case) all dependencies cannot be easily fixed, because it would take a lot of developer-hour. IMO DepTrac definitely should support violation skip possibility otherwise integration process might not be so smooth.

@timglabisch as you can see in #199 we have implemented a workaround using existing functionality, but not the best option. We would like to see jUnit support as well to see and control the amount of existing skipped violations. Also, an approach described in #199 provides a possibility to skip some class completely from an analysis, but in the scope of this PR I have implemented a possibility to skip exact violation which minimizes probability to introduce new violations.

@timglabisch any ideas? Should I continue work on PR or you will just close it?

I think this would be good start having a skipping mechanism. If there is somebody having the use case skipping functions/npath then they/we should start thinking about abstracting the mechanism.
@torinaki 👍 feel free to continue

@smoench , @timglabisch it seems that PR is ready for review.

@torinaki Would be great if you could rebase on actual master. I extended the travis ci config to enforce static analysis. As soon as the pipeline gets green I will merge your PR :)

@torinaki It seems you have just a few coding style issues. They could be easily fixed with php-cs-fixer. Just download the latest phar-file and run following command php php-cs-fixer.phar fix. Thanks :)

Thank you @torinaki


Extension errors when CMD/CTRL+hovering symbols from other files

When holding CMD/CTRL and hovering a module or function from another file, it seems like Credo tries to run on that file but fails, causing this error message to be displayed as a notification:

Command /Users/jamin/.asdf/shims/mix credo returns empty output! Please check your configuration. Did you add or modify your dependencies? You might need to run mix deps.get or recompile.

The error only occurs when the file of the hovered symbols is not open:
https://user-images.githubusercontent.com/6618434/144095983-4dc7308a-22a0-4306-9b1a-e7c4c6c66591.mov
The error does not occur when the file is already open:
https://user-images.githubusercontent.com/6618434/144096028-6234a2ed-0111-4030-b1b2-d9d48a5ebab9.mov
This is the debug log (elixir.credo.enableDebug set to true) when duplicating the error:
> Retreiving credo information: Executing credo command `/Users/jamin/.asdf/shims/mix credo info --format json --verbose` for /Users/jamin/Projects/vscode_elixir_issue/lib/other_module.ex in directory /Users/jamin/Projects/vscode_elixir_issue

> Removing linter messages and cancel running linting processes for /Users/jamin/Projects/vscode_elixir_issue/lib/other_module.ex.

> Command `/Users/jamin/.asdf/shims/mix credo` returns empty output! Please check your configuration. Did you add or modify your dependencies? You might need to run `mix deps.get` or recompile.

The extension still functions correctly (linting open Elixir files), though.
Steps to Reproduce

Create a new Elixir project with mix new.
Install Credo and set up config with mix credo.gen.config.
Create a new file and module (OtherModule) with a function (some_function).
Reference that function in another file and module (MainModule).
Close all files except the one containing MainModule.
Hold CMD/CTRL and hover over OtherModule or some_function.
Observe the "returns empty output" error in a notification.

Hello there! Thanks for bringing that up. That seems to happen because of https://github.com/microsoft/vscode/issues/109908: When the hover popup is opened it triggers the event that a document has open, and, thus, the document starts a linting process. However, immediately afterwards, vscode triggers the event that the document has been closed. This in turn triggers all running credo processes for this document to be cancelled.
I'll release a fix where SIGTERM errors on credo processes will not be reported.


Increase max_length of MediaFileTranslation captions?

Hi,
I'm wondering if there are any issues with setting the max_length of captions in MediaFileTranslation from 200 to something much larger?
I have a fork of FeinCMS where the only change is we are setting the max_length to 1024.
Assuming this doesn't cause any new issues, I'd love for a longer max_length.
Thanks.

#668
Here you go.  Thanks.


Any plan for Scan?

I saw some commented code in Exredis.Api, any plan to implement them?

I tried so, and yes, it works.
But I found it is not that convenient somehow.
I'm thinking, maybe it would be nicer to wrap the scan result as a Stream, could be more Elixir friendly.


cryptography >= 3.1 is required

The README doesn't specify a minimum version for cryptography but trying to use dpapi-ng on an ubuntu 20.04 box with cryptography 2.8 results in the error:

missing 1 required positional argument: 'backend'

From the release notes it seems cryptography 3.1 is the first version to make the 'backend' argument optional.
It would be good if the requirements could be updated.

I can certainly update the requirements to reflect this but keep in mind 2.8 is from 2019 which is 5 years old at this point in time. I appreciate you sharing this though as the min should definitely be valid for what it needs.

I've set the minimum in https://github.com/jborean93/dpapi-ng/pull/10. I chose 3.4.4 due to type annotations which isn't really a runtime requirement but it helped simplify testing requirements.

Appreciate it's a pretty old version - ran into the issue as Ubuntu 20.04 LTS ships 2.8 and is still in support for a few months (and of course for some people there are paid support options that may leave it running longer).


Implment xls export of the results

It will be great to have the option to export the results to .xls As runnerty-executor-mysql does

this is available in version 3.0.0


[WIP] Allow emoji as first character in full-line inline fields

While messing with my vault, I noted that I can use emoji as keys for inline fields if I embed them in a line (e.g., Today I ate [🍿::50] popcorns.). However, if I want to use the same inline field with the full line syntax (e.g., just a line with 🍿:: 50), I get zero results.
I've played a bit to the code. I added a couple of test cases in the unit tests and I've identified a regex that fixes, at least, the difference during the parsing step.
Unfortunately, this still doesn't solve the problem. Probably there is some other place in the code I am missing.
If you think this is a valid potential fix, maybe I can use a hint to complete this PR. :)

One issue with this - there is previous precedent to not parse emoji as the first character due to people who use it purely decoratively:
- ✔ Completed:: False
- ⚙ Project:: Thing

Changing this precedent would break existing metadata (by changing how these are queried); we might be able to special case some scenarios (like allowing pure emoji keys with no text), but the general case will not work.


Switch concurrency model

Instead of having each machine iterate through the task list, it will have each task iterate through the machine list.

I hope we're not waiting for each finish their tasks. Things will ssloowwww as the number of machines increases

What other choice do we have ?

I do feel that each task should iterate through the list of machines and despatch them all at once. If something bad happens we can just do a rollback.
We don't gain anything by waiting for one machine to finish all the tasks and then moving on to the other.

This feature has been created and tested for standard deploy.  It will be merged to master when rolling_deploy branch is finished


Extension no longer available on Chrome Web Store

I've just set up a new computer and noticed that my Chrome sync didn't automatically install this extension.
When trying to go the extension page in the Chrome Web Store it just responds with a 404 page.

I have the same problem

Google automatically took it down  because it didn't have a screenshot.
I've added a screenshot now, so we'll wait and see:

Looks like adding a screenshot worked and it's available again. Thanks! :)


The 'replace' confirmation dialog grabs scroll position

delete some content from the codemirror editor in https://codemirror.net/demo/search.html demo, such that the vertical scroll disappears
resize the browser window such that the bottom of the codemirror editor is hidden, and the browser window shows a scroll bar
Ctrl+Shift+F to search and replace some text at the bottom of the editor

The browser window will scroll to make sure the selected text to be replaced visible. However the showing of the  'Replace? Yes No Stop' dialog will scroll the window immediately to the top,  hence our end user won't see the text selection any more. This happens so quickly that looks like the window was not scrolled at all.
Although this sounds a made up case, however for large documents, it is desirable to make the browser window scrolling, instead of the codemirror editor, to make sure the browser's search functionality works well. If instead we make the codemirror editor scrolling, the browser's search dialog won't find anything that is out of the codemirror editor's visible area.

If you can solve this in a clean way a patch would be welcome. It is unlikely that i'll work on it, though.


Support recursive wildcard in Evaluation path for JSON rules

Allow path to specify a wildcard that should add all matching property children recursively in the template path.  One suggestion is to use "**" to represent a recursive wildcard.
Examples
Template JSON to evaluate
{
  "prop1": {
    "child1": {
      "value1": 1,
      "value2": 2
    }
 },
  "prop2": {
    "child2": {
      "value1": 1,
      "value3": 3
    },
    "child3": {
      "value1": 1,
      "value4": 4
    }
  }
}

Rule Evaluation 1
{
  "path": "prop1.**"
  // ...
}

Paths evaluated
prop1.child1.value1
prop1.child1.value2
Rule Evaluation 2
{
  "path": "**.value1"
  // ...
}

Paths evaluated
prop1.child1.value1
prop2.child2.value1
prop2.child3.value1
Rule Evaluation 2
{
  "path": "**"
  // ...
}

Paths evaluated
prop1.child1.value1
prop1.child1.value2
prop2.child2.value1
prop2.child2.value3
prop2.child3.value1
prop2.child3.value4

This feature is to reach parity with ARM-TTK

Revisit when there is a customer need.


GCP: Configure BOSH Director is repeatedly failing

Issue
with V0.23.1 downloaded from PivNet, Opsman is successfully installed, Configuring BOSH director failed
Expected result
Complete Configuring BOSH director successfully
Current result

Configuring IaaS and Director...

configuring iaas specific options for bosh tile

configuring director options for bosh tile

configuring security options for bosh tile

configuring resources for bosh tile

configuring availability zones for bosh tile

configuring network options for bosh tile

could not execute "configure-bosh": tile failed to configure: request failed: unexpected response:

HTTP/1.1 500 Internal Server Error

Transfer-Encoding: chunked

Cache-Control: no-cache, no-store

Connection: keep-alive

Content-Type: text/html; charset=utf-8

Date: Fri, 13 Apr 2018 22:27:55 GMT

Expires: Fri, 01 Jan 1990 00:00:00 GMT

Pragma: no-cache

Server: nginx/1.4.6 (Ubuntu)

Set-Cookie: _web_session=NjNnWE1zeHZHYm1rTmF4K05WcytwK2c1THh0alhSSmNITExlOFdaWWJqeEs0aWIwOXpYMFVwalZQbGUrNnc2aTllTUdXK2FZR25zVFEvZnpmUG42S0hMekRBbnNOTWVRaFVDRS9reTJzR2JxS2ZMcnRTYVFnUmo5OURVNzJZcWl5L0NrcEdWcWVEYUU0dVZmZTRhclNnPT0tLTdITmswUWRrRHQ1UVFQRGgxZkE4SWc9PQ%3D%3D--65aec988b1d83f2d461d0a86ffa259026982c70a; path=/; secure; HttpOnly

Strict-Transport-Security: max-age=15552000

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

X-Request-Id: 353afac4-2e70-4112-a2c1-be87a3c26896

X-Runtime: 0.203689

X-Xss-Protection: 1; mode=block

2bb9

<!DOCTYPE html>

<meta content='text/html; charset=utf-8' http-equiv='Content-Type'>

<meta content='0' http-equiv='expires'>

<meta content='text/javascript' http-equiv='Content-Script-Type'>

<meta content='text/css' http-equiv='Content-Style-Type'>

<meta content='IE=Edge,chrome=1' http-equiv='X-UA-Compatible'>

<link href='/favicon.png' rel='icon' type='image/png'>

<title>Ops Manager</title>

<meta name="csrf-param" content="authenticity_token" />

<meta name="csrf-token" content="cbRrbvonjuKc6k8JeAU/xXSiP+YFEWu2yFE4O6J2NQD+WEGAVuqpyUPFHMO/SZVpvaD7OHZGzJDGmUqo8yCZkA==" />

<link rel="stylesheet" media="screen" href="/assets/application-bd2cd61e06e7e298f373f3612c3c1ba12023ad1786c2a5ff89ce73622304fa86.css" />

500 An error occurred.

Contact Pivotal Technical Support to report the problem.

Back to dashboard

NoMethodError

undefined method `service_network=' for #<Persistence::Models::Network>

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activemodel-5.0.4/lib/active_model/attribute_methods.rb:433:in `method_missing'

/home/tempest-web/tempest/web/app/models/persistence/framework/hashable_model.rb:75:in `block in initialize'

/home/tempest-web/tempest/web/app/models/persistence/framework/hashable_model.rb:74:in `each'

/home/tempest-web/tempest/web/app/models/persistence/framework/hashable_model.rb:74:in `initialize'

/home/tempest-web/tempest/web/app/presenters/networks_presenter.rb:57:in `new'

/home/tempest-web/tempest/web/app/presenters/networks_presenter.rb:57:in `block in load_networks_from_params'

/home/tempest-web/tempest/web/app/presenters/networks_presenter.rb:51:in `each'

/home/tempest-web/tempest/web/app/presenters/networks_presenter.rb:51:in `load_networks_from_params'

/home/tempest-web/tempest/web/app/presenters/networks_presenter.rb:18:in `initialize'

/home/tempest-web/tempest/web/app/controllers/infrastructure/networks_controller.rb:15:in `new'

/home/tempest-web/tempest/web/app/controllers/infrastructure/networks_controller.rb:15:in `update'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/abstract_controller/base.rb:188:in `process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal/rendering.rb:30:in `process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/abstract_controller/callbacks.rb:20:in `block in process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:126:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:506:in `block (2 levels) in compile'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:455:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:101:in `__run_callbacks__'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:750:in `_run_process_action_callbacks'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:90:in `run_callbacks'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/abstract_controller/callbacks.rb:19:in `process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal/rescue.rb:20:in `process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/notifications.rb:164:in `block in instrument'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/notifications.rb:164:in `instrument'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal/instrumentation.rb:30:in `process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal/params_wrapper.rb:248:in `process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activerecord-5.0.4/lib/active_record/railties/controller_runtime.rb:18:in `process_action'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/abstract_controller/base.rb:126:in `process'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionview-5.0.4/lib/action_view/rendering.rb:30:in `process'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal.rb:190:in `dispatch'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_controller/metal.rb:262:in `dispatch'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/routing/route_set.rb:32:in `serve'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/journey/router.rb:39:in `block in serve'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/journey/router.rb:26:in `each'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/journey/router.rb:26:in `serve'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/routing/route_set.rb:725:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in `call!'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/etag.rb:25:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/conditional_get.rb:38:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/head.rb:12:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/session/abstract/id.rb:232:in `context'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/session/abstract/id.rb:226:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/cookies.rb:613:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:97:in `__run_callbacks__'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:750:in `_run_call_callbacks'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/callbacks.rb:90:in `run_callbacks'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/callbacks.rb:36:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/railties-5.0.4/lib/rails/rack/logger.rb:36:in `call_app'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/railties-5.0.4/lib/rails/rack/logger.rb:26:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/request_id.rb:24:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/method_override.rb:22:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/runtime.rb:22:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/activesupport-5.0.4/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/executor.rb:12:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/static.rb:136:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/rack-2.0.4/lib/rack/sendfile.rb:111:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/actionpack-5.0.4/lib/action_dispatch/middleware/ssl.rb:84:in `call'

/home/tempest-web/tempest/web/lib/rack/streaming.rb:63:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/railties-5.0.4/lib/rails/engine.rb:522:in `call'

/home/tempest-web/tempest/web/lib/stack_prof_middleware.rb:78:in `call'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/thin-1.7.0/lib/thin/connection.rb:86:in `block in pre_process'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/thin-1.7.0/lib/thin/connection.rb:84:in `catch'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/thin-1.7.0/lib/thin/connection.rb:84:in `pre_process'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/thin-1.7.0/lib/thin/connection.rb:50:in `block in process'

/home/tempest-web/tempest/web/vendor/bundle/ruby/2.3.0/gems/eventmachine-1.2.3/lib/eventmachine.rb:1076:in `block in spawn_threadpool'

Back to dashboard

PCF Ops Manager v2.1-build.214;

©2013-2018 Pivotal Software, Inc; All Rights Reserved.

End User License Agreement

 |

API Docs

0

Have you found a fix for that issue?

No. I was not able to fix it. I configured it manually after creating opsman.
@Kenuat Where can I see this compatibility matrix to find right pipeline setup for PCF 2.1?
Thanks.


Update Post

Hey team
This PR updates our hiring process post. Please take a look. Thanks.

Thanks for your comments @etagwerker. This is ready to review again.


[Event Request] table 5767 "Warehouse Activity Line" - OnAfterSetConditionalTrackingFilters

We would like to add a new event OnAfterSetConditionalTrackingFilters and a new procedure:
procedure SetConditionalTrackingFilters()
begin
    //A200F0000.Event.ns
    SetFilter("Serial No.", "Serial No.");
    SetFilter("Lot No.", "Lot No.");

    OnAfterSetConditionalTrackingFilters(Rec);
    //A200F0000.Event.ne
end;

Event Signature:
[IntegrationEvent(false, false)]
local procedure OnAfterSetConditionalTrackingFilters(var WarehouseActivityLine: Record "Warehouse Activity Line")
begin
    //A200F0000.Event
end;

This function does not exist.

We already have this procedure and event, but in more generic way:
procedure SetTrackingFilterFromWhseActivityLine(WhseActivityLine: Record "Warehouse Activity Line")
begin
    SetRange("Serial No.", WhseActivityLine."Serial No.");
    SetRange("Lot No.", WhseActivityLine."Lot No.");

    OnAfterSetTrackingFilterFromWhseActivityLine(Rec, WhseActivityLine);
end;


chore(deps): fix installation warning for vue composition api

The same version number should be used in all places.

fixed in 2.0.6


[Epic] Overhaul Logging

Problem Statement
Current logging for the Fides webserver leaves a lot to be desired. It is exceedingly difficult to debug/track down issues both in production as well as dev environments.
Solution
Logging should be revisited holistically for Fides. There is a laundry list of potential TO-DO items, with varying levels of complexity:

Fix the server swallowing logs, specifically on 500s
TRACE level logging that is _very verbose`
Generally apply logging security measures, especially with regards to logging credentials or other sensitive information
Include a place within the UI for users to see logs
Some kind of logging integration with DataDog or other providers (Atlas Example)
Log private request IDs when processing DSRs for easier debugging of specific requests
Standardize Log Formatting (there are currently multiple formats...not great for parsing cleanly)
Add HTTP logging to the Privacy Center

NOTE: This issue description will continue evolve as we discuss and decide on what the exact changes will be.
related slack thread: https://ethyca.slack.com/archives/CBKK8TS74/p1686627425751419

cc @daveqnet @RobertKeyser @NevilleS @seanpreston

Update after our planning chat yesterday - let's identify a couple of the low-hanging fruit items here (e.g. fixing the server swallowing logs, adding TRACE logs with a lot of detail, etc.) and ship a few improvements, but we'll want to break this out into other follow-up issues. I'm not expecting us to solve logging immediately

@daveqnet @seanpreston @RobertKeyser can y'all write wishlists for logging in the following format?
This isn't something we'll solve in a day (or a sprint) so it's worth getting everything into a big Epic and prioritizing as we go 🙂

Critical Requirements

 - description

Nice to Haves

 - description

Sure thing, @ThomasLaPiana. From my (security) perspective, I've just adapted the L1 (most basic) logging requirements from ASVS 4.0.
Critical Requirements

Log Content: Secrets - Verify that the application does not log credentials. Session tokens should only be stored in logs in an irreversible, hashed form. (ASVS 4.0 7.1.1)

I've excluded payment data from the original req as fides does not include any payment/billing integrations.
Not a requirement, but if you want more info on what constitutes a credential and should be excluded, the OWASP cheatsheet is good on this:  https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html#data-to-exclude . Some examples: database connection strings if they include passwords, bearer tokens in Authorization headers if logging full

Log Content: PII - Verify that the application does not by default log other sensitive data as defined under local privacy laws. (ASVS 4.0 7.1.2)

You can take "sensitive data as defined under local privacy laws" to mean PII or personal data.
The "by default" is my addition. fides should be private by default, but my data protection position here is that the user deploying fides is a data controller and should be empowered (through, say, configuration) to make a decision to collect data in line with local privacy laws. For example, a user deploying fides in the EU could make a decision to collect IP addresses using a legitimate interests lawful basis under the GDPR (e.g. security & abuse detection and prevention) and configure fides to do this, but separately they'd have to include this info on their privacy notice to end users.

Log Protection: Output Encoding - Verify that all logging components appropriately encode data to prevent log injection.

What we're trying to protect against here is an attacker trying to inject fake or malicious entries to fides logs. As a reminder, log4shell was a log injection vulnerability in log4j. 😬 I am hopeful that the logging library used will meet this requirement for us, but it'll need to be verified. If we support logging to locations other than stdout/stderr e.g. logging to file, then this requirement will be more difficult to meet.

Nice to Haves

I think the scope of the must-haves above is large enough as it is! If I could include nice-to-haves, basically anything marked as L2 here, excluding the error handling section as it's beyond the scope of this epic.

One pice of a additional info: as a security best practice we recommend to users not to set a lower log level than INFO in production deployments. DEBUG (and TRACE if we add it) should only ever be set temporarily for initial deployment and later troubleshooting.
FATAL
ERROR
WARN
INFO
DEBUG
TRACE

Meeting with @RobertKeyser on June 30, 2023
What're some logging changes you'd like to see?

Inconsistent logging formats between the Privacy Center, Fides, Workers, etc.
There is no request ID throughout the Privacy Request task logs, so it's hard to figure out exactly where/why things are failing
Some exceptions and failures show up as multiple lines in DataDog
JSON logging would be easier, current format requires some additional parsing especially due to varying log formats
When an API request returns a 500 we get the stack trace in the logs but not the request itself (We hypothesize this is because we aren't wrapping things in a try/except so when the exception gets raised the logging doesn't get called)
Privacy Center has no HTTP logging
Less strict masking for certain logs (such as connection tests), this adds a lot of friction when debugging

What're some changes you'd like to see as far as running and maintaining Fides instances?

Be able to set up messaging and storage destinations from within the UI
Inviting users as opposed to setting up their password directly

Additional request: Can we enable SQL-level logging in SQLAlchemy when the log level is set to TRACE?


Do not take vehicles into account for base size calculation

This patch uses LuaPlayerBuiltEntityEventFilters to make sure
that the TLBE.Main.entity_built () callback is not called for
vehicles.
Additionaly during base size recalculation we skip entities of
type car (currently cars and tanks).
Fixes #22
Please note, that I haven't yet tested this patch (will probably do it soon-ish).

I verified that without this fix the base tracker is indeed influenced by placing vehicles (car, tank, spidertron) and with this fix the base tracker does not care about them anymore :+1:


Publish source distribution please

Hi @Martiusweb,
You publish only binary wheels, which leads to the situation where it's impossible to install it using distutils.
This happens with pbr tool (which is OpenStack's project being widely used in the wild):
https://travis-ci.org/webknjaz/asap-authentication-python/jobs/285562717#L489
Ref: https://github.com/pytest-dev/pytest-asyncio/issues/13#issuecomment-126959408
May I ask to to publish sdist as well?
P.S. Why not configure automatic deployment of distributions to PYPI straight from Travis CI? I could send you PR implementing this.

Hi,
I uploaded the sources for the 0.10.0 release.
I'd gladly review a PR though :)

Thanks :)

@Martiusweb PR done.


Add RPM image scanner

What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds support for scanning RPM databases
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
I split layer scanning tests into separate files
Does this PR introduce a user-facing change?
Added support for scanning images with RPM package managers

I rebased to include the fix in #343

/hold cancel


Restore old method of viewing post engagements (likes, reposts, QRTs)

Recently Twitter just pushed out a new update which makes viewing engagements on any tweet obtuse.

As you can see above you can only see the quantity of people's actions. There's no more text to click on to view them. Now you have to click on the three dots and press on "View post engagements" as shown below.

The post engagements is basically it's own page now that allows you to choose what engagement to view as seen below.

I personally think this is a big downgrade and would love to see it restored somehow in a way, even if it means to just link directly to the respective engagement within the post engagements page itself.

It really goes to show you how awful Twitter's changes are that I came here to post this same issue and it's already been done. :)

Reference for the old implementation we'll be restoring:
https://web.archive.org/web/20220707151054/https://twitter.com/actioncookbook/status/684515262712967170

hello, can you do something about when there are no quotes on a tweet but you want to see reposts/likes


Add multi series pie example

#6273 proposed the addition of a new sample file that showed how to use the legend callbacks in a multi series pie chart.
This PR cleans up the sample and adds to the samples page

I can't get the sample code to work, the plugin functions never run. Should I open an issue?

Apologies for the ping on an old PR, but are the tooltips for this example bugged? @etimberg

Yes, there is indeed a bug. The tooltips always show the first dataset's label.
I've raised https://github.com/chartjs/Chart.js/issues/11961

While not accepted as a bug, there is a "solution":
https://github.com/chartjs/Chart.js/issues/11961#issuecomment-2493372303


Add Max Window  Width for Tiled Windows

I'm on an ultrawide monitor and it would be great to have an option to limit the width of a tiled window when it is the only one on a workspace. So Firefox doesn't take up the whole screen unnecessarily.
LeftWM has this feature and it's described here.
Thanks!

isn't that basically pseudo when only? :P That'd be scriptable

Thanks. It appears from the documentation that pseudotiling is only be related to the Dwindle layout. Is this doable on the Master layout?

Is there any interest in adding such a feature? Having a single window full screen is unnecessary on an ultrawide and manually floating it and resizing it is inconvenient.

at the current moment, no. I have many other things to prioritize. Feel free to make a MR though

Adding some interest in this feature. I would absolutely love it in Hyprland, as LeftWM is X11 and I would rather not have to switch back from a Wayland compositor

Adding my interest too! this would be a great addition. Firefox fullscreened on a 21:9 doesn't look great, above all when websites are not centered (e.g. Duckduckgo and Google)

I have been playing around with Hyprland coming from sway and this is one of the main things that I miss. In sway, the settings relevant setting that I use to achieve this is smart_gaps inverse_outer it works a little different than how you have described (it is entirely possible to still have a window take up a wider area) but it solves the issue for me on a 32:9 monitor.
It is a part of the smart_gaps function which is usually used to remove gaps if there is only one window, however instead it does the inverse and adds the smart gaps only if there is a single window, I set this, then set the gaps horizontal to be 1/4 the window width. This makes sure that a single window is limited to roughly 16:9 and subsequent windows drop the gap.
I mention this, both to voice my support of such a feature, but also to provide a breadcrumb to someone who has the time and expertise to look through the code to look at implementing the feature. I would assume that being both wlroots based wayland window managers, this would be feasible to replicate?

If that counts, I'm interested as well in this feature which LeftWM has. As mentioned above floating it and resizing it is inconvenient.

this has been somewhat addressed recently through workspace selectors
the following rule adds gaps on the sides when there's only one window in the workspace
workspace = w[t1], gapsout:10 400

some related discussions: https://github.com/hyprwm/Hyprland/issues/5312

this has been somewhat addressed recently through workspace selectors the following rule adds gaps on the sides when there's only one window in the workspace
workspace = w[t1], gapsout:10 400

some related discussions: #5312

Hey, @thejch, I have tried your solution but I keep getting the error: Invalid workspace identifier found: gapsout:10 400. Do you have a guess to what the source of the error might be?

Hey, @thejch, I have tried your solution but I keep getting the error: Invalid workspace identifier found: gapsout:10 400. Do you have a guess to what the source of the error might be?

You probably didnt update to the latest version

You probably didnt update to the latest version
Oh, that must be it! I am using NixOS stable channel and the version I have is 0.32.3, while I notice now that the last release here is already 0.38.1. Thank you.

this has been somewhat addressed recently through workspace selectors the following rule adds gaps on the sides when there's only one window in the workspace
workspace = w[t1], gapsout:10 400

some related discussions: #5312

This works perfectly for me. Thank you for following up. Closing.

Had a similar use case for the title of the this thread, but the application is a little different than what's described in the post.
I use mdr to open markdown cheatsheets for hyprland, helix, yazi, bash aliases, etc. For all of these, I only need them to take up a quarter of the screen width at most. It would be cool to have the ability for mdr to open at 25% width in both master and dwindle layouts.


Add and improve documenation

Fixed a few typos in existing documentation
Uploading first two simple tutorials. The example projects they link to are still hosted on my personal github account -should they be also moved into this repository? If so, where do they fit, structurally?

Thanks for the PR! I think we could add the tutorials to a tutorials subdirectory in this repo.


[Frontend] Create Sign Up Page

Hi,
In this pr:

Create the signup page. On this page, a user can enter the following details to sign up:

A unique username.
A unique email address.
A password.

Add redux-logger and redux-persist to log state changes as well as persist the state changes in local storage

STATUS: APPROVED ✔
These updates have been approved. You can now merge this branch.


Update model via PUT / - support?

Today people can update the model via PUT /model and PUT /  + data+model in the body
Seems odd that someone can't define the registry and upload the data in one import operation when they can export it in one.
Proposal: allow it
We could choose to not support it for v1 but we need to decide whether to consider it for v1 or not

agreed on the 4/3 call to allow it

Follow-on question, does PUT require the use of ?model similar to how we require ?inline so people don't change it by accident by doing a GET + PUT w/o realizing they're updating the model? I think we should

Added requirement for ?model


API call failed: fresh install

fresh clone & install & start

hub clone mars/heroku-cra-node
cd heroku-cra-node/
npm install && npm start

# in a new tab
cd heroku-cra-node/react-ui
npm install && npm start

load localhost:3000

assert the api request to /api fails as 404

question
Did I miss a step somewhere?

Does the server start-up successfully?
What is logged in the terminal from the server process as it starts and then during those failing requests?

@mars yup. the server was down - sorry i forgot to check that


Misleading Licence Requirements

The Line "A Microsoft 365 Business plan that includes Microsoft 365 Apps for Business." Is Misleading!!
Shared Activation This will only work with "A Microsoft 365 Business Premium" Plan.
If you have a  "Microsoft 365 business standard" Plan which includes "Microsoft 365 Apps for Business" this will not activate Office Apps in Shared Activation Mode

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

ID: 6da18a8b-9e96-0155-7b30-9c211070d793
Version Independent ID: 5a7e610a-bfcb-d9cc-03f7-589d970128d9
Content: Deploy Microsoft 365 Apps by using Remote Desktop Services - Deploy Office
Content Source: DeployOffice/deploy-microsoft-365-apps-remote-desktop-services.md
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

Thanks for highlighting this. We've submitted a fix to the doc in #851


non-nullable lists on isRequired

this change renders lists non-nullable if isRequired: true is defined. this relates more the the required semantics of jsonschema. additonally, list elements will not be nullable, which is consistent with the way AppSRE uses jsonschema in qontract-schema
https://json-schema.org/understanding-json-schema/reference/object.html#required-properties
the qenerate generated gql dataclasses would reflect such a change as follows
example of a not required list
-    saas_files: Optional[list[Optional[SaasFileV2]]] = Field(..., alias="saasFiles")
+    saas_files: Optional[list[SaasFileV2]] = Field(..., alias="saasFiles")

example of a required list
-    saas_files: Optional[list[SaasFileV2]] = Field(..., alias="saasFiles")
+    saas_files: list[SaasFileV2] = Field(..., alias="saasFiles")

Signed-off-by: Gerd Oberlechner<EMAIL_ADDRESS>

LGTM!


Getting a summary.length error and trouble displaying data in year mode

Hello,
While running my webapplication, it works initially. When clicking about, I run into the error below:

Also, I cannot see data displayed when showcasing the year (much like the other issue posted half a year ago).
This is how my code looks like:

I'm a bit new to React, so it might be a stupid problem on my end, but I can't seem to debug it. If you want to attempt to recreate the issue, the repo is here:
https://github.com/SoerenToennesen/Website
where I the calendar heat map is created under CalendarHeatMap.js
There is also another error, which I'm not sure why is created, as seen in the gif provided below (year_label.year is not a function).

Thanks for the detailed bug report! I'll check it out later today and get back to you

Hands down best error report I've ever seen hah, I was able to reproduce your issue and I believe it has to do with d3 and moment versions used, if you set the specific versions in your package.json the example works
    "d3": "4.11.0",
    "moment": "2.19.1",

PS. I should probably make these dependency versions explicit in the original project so that it would install the correct version next time.

Thank you for the fast reply and solutions - I'll change the versions then! :)


Implement handler that terminate the container

Implement handler that terminate the container
When using DEFAULT=kill-container in the metadata, the seccomp agent will send a kill signal to the pid1 of the container. This effectively terminates the container.
How to use
Use a SeccompProfile with the following:
spec:
  defaultAction: SCMP_ACT_ALLOW
  architectures:
  - SCMP_ARCH_X86_64
  listenerPath: "/run/seccomp-agent.socket"
  listenerMetadata: "DEFAULT=kill-container"
  syscalls:
  - action: SCMP_ACT_NOTIFY
    names:
    - unshare

Testing done
$ kubectl exec -ti mypod -- /bin/sh
# unshare -u
command terminated with exit code 137
$ kubectl get pod
NAME    READY   STATUS   RESTARTS   AGE
mypod   0/1     Error    0          18m

@alban also, I see that we are parsing the metadata as if it was a map[string]string... Your example has only one field (DEFAULT=xxx), but how would it look like if there are more? Don't have it at the top of my head now.
Also, what do you think instead of DEFAULT we use DEFAULT_ACTION?

Also, it will be great to document (at least some comment in the code) what you told me on slack: this differs from SCMP_ACT_KILL_PROCESS as that would just kill the process that does the syscall, this kills the pid1 of the container (pid1 as advertised by runc), which would normally kill all processes in the container.

also, I see that we are parsing the metadata as if it was a map[string]string... Your example has only one field (DEFAULT=xxx), but how would it look like if there are more? Don't have it at the top of my head now.

It could be this keys=values separated by new lines like this:
"listenerMetadata": "MKDIR_TMPL=-{{.Namespace}}-{{.Pod}}-{{.Container}}\nEXEC_PATTERN=/bin/true\nEXEC_DURATION=2s\nMOUNT_PROC=true"

This is parsed in pkg/kuberesolver/kuberesolver.go parseKV().


Bug: Chalk terminal colours don't show work for help action

Context

Using version 6.04 of Hygen from npx
The generator name is landing-page

Problem
Running the following command npx hygen landing-page help, doesn't work as expected.
The landing-page/help/index.ejs.t contents:
---
message: |
    - hygen {bold mailer} new --name [NAME]
---

The npx hygen landing-page help output:
Loaded templates: _templates
[object Function] help:
- hygen {bold mailer} new --name [NAME]

Note
Version 4.x of Hygen works as expected and does bold/color in the terminal correctly.
Is this a bug or has the way that help is supposed to work, changed since version 4?

This can be fixed by #248

I still have the same problem using version 6.1.0 (event the fixed has been merged). Or do we still need to do the workaround?

The PR above didn't fix the issue. the version 6.1.0 still have this bug. any idea on how to dix it?
Thanks

Fix for this issue is in https://github.com/jondot/hygen/pull/335

The issue is still present in 6.2.11. On a fresh install, running hygen init self then hygen generator help the chalk templates aren't rendered.

Here's a patch to fix this issue.
diff --git a/node_modules/hygen/dist/logger.js b/node_modules/hygen/dist/logger.js
index 312f112..5194ca3 100644
--- a/node_modules/hygen/dist/logger.js
+++ b/node_modules/hygen/dist/logger.js
@@ -4,8 +4,9 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 const chalk_1 = __importDefault(require("chalk"));
+const template = require("chalk/source/templates");
 // chalk 4.1.2 doesn't type template property
-const { yellow, red, green, magenta, template } = chalk_1.default;
+const { yellow, red, green, magenta } = chalk_1.default;
 class Logger {
     constructor(log) {
         this.log = log;

patches/hygen+6.2.11+001+chalk.patch

npx patch-package

@jondot Is there a plan to fix this or remove the reference in the docs?


Remove Players column

It's non-intuitive, and doesn't hold relevance for most decks.
We should only show that data on competition pages.

Interesting. It's true that it's not really relevant right now when both the tournaments that have happened were about the same size. Maybe it will remain irrelevant forever.

71cfa0c.


Add OpenShift Dashboards for GitOps

What type of PR is this?

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

/kind enhancement
What does this PR do / why we need it:
This provisions a set of dashboards in the OpenShift console (Observer > Dashboards) to provide monitoring for GitOps. These dashboards are based on the upstream Argo CD dashboards but have been modified to work with the OpenShift console which has a reduced feature set compared to Grafana.
Have you updated the necessary documentation?

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

Which issue(s) this PR fixes:
https://issues.redhat.com/browse/GITOPS-1767
Fixes #?
GITOPS-1767
Test acceptance criteria:

[*] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:
Install the GitOps Operator on an OpenShift cluster and then navigate to Observe > Dashboards in the console. In the dropdown list of dashboards note that three new dashboards are now available:

GitOps Overview
GitOps Components
GitOps gRPC

Thanks @gnunn1, I tested this out and it works great!
One other point I would mention is maybe we can move the dashboards folder out of the controllers folder and keep it at the same level as the controllers folder

Moving dashboards outside of controllers doesn't work for me, there are some limitations around go embed with respect to where the content is located.
The go:embed directive only works with files that are accessible from the current working directory or a subdirectory of it. This means that you cannot use the go:embed directive to embed files outside of your project directory or in a parent directory.

https://www.iamyadav.com/blogs/a-guide-to-embedding-static-files-in-go

I have made the requested changes plus added the ability for it to update the dashboard configmap if the data element doesn't match the expectation.

/ok-to-test


Delete unassociated public IP addresses to save money : Dynamic IP which is unattached from NIC

Hi Team,
Thanks in advance, In my subscription i see there are multiple Public IP which is currently in dynamic state and not attached to any NIC. They are in ARM deployment model.
I don't think there is cost associated with dynamic Public IP as there is no IP Address assigned by Microsoft also this Public IP is not attached to any NIC.
Azure advisor still shows that there is potential cost savings. Is my understanding clear about dynamic public IP addresses and it's associated costing?
Kindly find the below FAQ from the IP Address pricing page.
Question :  Am I charged for a public IP address when my virtual machine is stopped-deallocated?
Answer : In ARM deployment model, there is no charge for dynamic public IP addresses when the associated virtual machine is “stopped-deallocated”
https://azure.microsoft.com/en-in/pricing/details/ip-addresses/

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

ID: b703202c-7c7d-7177-6496-d1c61dacf22b
Version Independent ID: f9ee0bcc-f74a-dbba-c9b9-f84bf7b800a7
Content: Reduce service costs using Azure Advisor
Content Source: articles/advisor/advisor-cost-recommendations.md
Service: advisor
GitHub Login: @kasparks
Microsoft Alias: kasparks

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

@kasparks - fyi

Hi Team,
Any update on this?

Hi,
just following up to see any update.

Hi @aquibqureshi26  - thanks for the question! I am following up internally with the team that owns Public IPs and I will get back to you when I have more information.

@kasparks any update from the Pub IP team?

Hi @aquibqureshi26 - There is no charge for the following Dynamic Basic IPs that are asssociated with a stopped-deallocated VM or that are not associated to a VM. Your understanding is correct.
Thank you for following up on this!

So Kasparks, will there be any change in the advisor report of cost savings? as it is misleading.


Test 03 2023

good util

good i advise

Can you add a feature in microwin that you can add exes and it makes a app in your custom iso


alert word: Add UI to support add, delete alert word

I think adding a "Personnel setting" option in the settings screen, there listing some settings like  "language", "alert words" will become easy for a user to check some information.
I have not included any tests here. which I would like to do if needed
check by changing the theme if color refactoring is needed I will change it

adding a word to alert word list

removing a word

Fixes: #3979

@ray-kraesig I have changed some code in the commit. Please review

Just to mention, there was similar work done long time back #986. Just in case, it might help in any way.

Fixed sathe issues pls review@ray-kraesig