Integrate the vscode with the browser

We are currently running a contest for our customers which requires the completion of both frontend and backend projects. In order to facilitate this, we need to provide Visual Studio Code (VS Code) to the 1000 participants, with each participant needing their own code space.
Could you please advise on how we can integrate VS Code for this use case?

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Fixed rtomayko/rocco#69.

With version 2.0 redcarpet switched to renderers, moved old API to redcarpet/compat.
After the fix tests passed OK.

I close my pull request since redcarpet is pinned to version 1.


[BUG]: Edge case with parameter matrix - when a parameter is reused in multiple templates, its matrices are empty (except other)

Describe the bug
I have this SIR model from a paper (Hewitt et al. 2024).
The model equations are:
d s / d t = - R * y * s * i
d i / d t = R * y * s * i - y * i
d r / d t = y * i

We stratify this model by N locations over all the state variables and parameters s, i, r, R, y. Thus, the parameter y becomes a matrix y_k for k = 0, 1, ..., (N-1).
When I view this parameter matrix in Configure Model operator, the default view is subjectOutcome and it's completely empty.
Model AMR:
Hewitt Model A (NY counties) (1).json
To Reproduce
Steps to reproduce the behavior:
Open the matrix view of the parameter y
Expected behavior
Since y_k is used in many templates, the default and only view probably should just be "other". I suggest locking the dropdown to just "other".
Screenshots

I suspect this is correct, but you have a big sparse matrix and didn't scroll enough?

Schematically the orange and blue rectangles are where the values are, where each colour represents one of R * y * s * i and y * i.


META: Saved Collections/Bookbag Service (from 1783)

Problem Description:
This is a Meta ticket for a new bookbag/save/export feature in LUX.
Expected Behavior/Solution:
The bookbag/save/export feature in LUX  will allow users to save URL searches/items to their collection from LUX, Library, etc. It will also have all MVP features listed in the requirements spreadsheet below.
Requirements:
https://docs.google.com/spreadsheets/d/1C04s3JUD2WoLgPrOEvRz645GluBWxHwjUFQuGNOOLYs/edit#gid=0 - Sarah
Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[x] Requirements - sarah
[x] user access workflow - Amy
[ ] wire/frame mockup for user access - Mike
[ ] bookbag workflow - Amy
[ ] wire/frame mockup for bookbag workflow - Mike
[ ] protype
[ ] testing
[ ] approval
[ ] ~Committee discussions - Sarah~
[ ] ~Feasibility/Team discussion - Sarah~
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] ~Questions~
~List of questions for discussions. Answers should be documented within the issue.~

UAT/LUX Examples:

Example endpoints from LUX to use for development and testing, if applicable.

Dependencies/Blocks:

Blocked By: Issues that are blocking the completion of the current issue.
Blocking: Issues being blocked by the completion of the current issue.

Related Github Issues:
Related links:

Bookbag Workflow
User Access Workflow: Tab Process 1.3
Bookbag Workflow: Bookbag Workflow - AM change (in progress, need to follow up with M.A to see if any of the changes are feasible)

Wireframe/Mockup:
Place wireframe/mockup for the proposed solution at end of ticket.

I renamed this to be the META ticket since it was being used as a placeholder.
@miketullo95 I have added two checkboxes for wire frames, one for the user access (complete and checked off) and one for the bookbag collection (in progress). The link to the workflows is in the Related Links section and it includes information on what tab the workflows are located in.
Wire frames can be worked on for User Access. I will update you when wireframes can be started for the Bookbag workflow.


[bug] Module not found: Can't resolve 'fs'

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
1.0.0
wagmi Version
1.0.1
Current Behavior
i was working on an older nextJs project and i had to restart because it became too old , so i tried the npm init @rainbow-me/rainbowkit@latest , right out of the box just with npm run dev , i was faced with this :
error - ./node_modules/node-gyp-build/node-gyp-build.js:1:0
Module not found: Can't resolve 'fs'
Import trace for requested module:
./node_modules/node-gyp-build/index.js
./node_modules/bufferutil/index.js
./node_modules/ws/lib/buffer-util.js
./node_modules/ws/lib/sender.js
./node_modules/ws/index.js
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./node_modules/wagmi/dist/connectors/walletConnectLegacy.js
<EMAIL_ADDRESS>./pages/_app.tsx
https://nextjs.org/docs/messages/module-not-found
i upgraded my node on mac m1 from node18 to node20 and retried , same error, so i tried to create-next-app and tried to manually do everything on a fresh next project , and i got the same error
Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

Apologies; we have fixed this issue with our templates but haven't released the updated version of @rainbow-me/create-rainbowkit yet. Wagmi v1 now requires that you polyfill a few dependencies. You can reference the migration guide for further details, and the Next.js example or sample next.config.js below:
/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  webpack: config => {
    config.resolve.fallback = { fs: false, net: false, tls: false };
    return config;
  },
};

module.exports = nextConfig;


Forget to fix monet icon?

Shouldn't it have been fixed already? APK word is still not visible. 🤔

@AbdurazaaqMohammed


Add support for rounded corners in dialog

Hopefully using a dimen resource

Oooooh wait, this isn't a dimen resource. Yet.


setting_ui: Fix sorting by "Invited by" column.

GSoC'2024 Participant

Previously, the sorting was broken due to
incorrect referencing of the property.
The code has been updated to use the "referrer_name" property instead of "ref".

CZO

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

we need this fix in  8.x too

Merged and marked as a backport candidate, thanks @sujalshah-bit!


Update Composer dependencies (2023-08-28-00-13)

Visual regression test passed!
View the visual regression test report


Mingwei/merge

added visibility functionality, able to add public/friends posts to followers' inbox

version changed, I will create a new PR


'String' is not convertible to 'KeyType'

Hello,
first of all: great library. I just moved from another lib to Genome, and I find it much more transparent and efficient.
My problem: I want to save a UIImage, using this code in the sequence function:
		try image <~> map["image"]
			.transformFromJson {
				let stringData = $0
				let image = UIImage.fromBase64(stringData)
				return UIImage(data: imageData)
		}
			.transformToJson {
				let image: UIImage = $0
				let stringData = image.toBase64()
				return stringData
		}

However, this does not compile, as the error "'String' is not convertible to 'KeyType'" is thrown. What goes wrong, and how to fix it?
Thank a lot in advance!

Hardy

What about this different approach?
public struct SomeStruct : MappableObject {
public var image: UIImage!
 public init(map: Map) throws {
    try image = map.extract("image", transformer: { UIImage(data: NSData(base64EncodedString: $0, options: NSDataBase64DecodingOptions())!) })
}

public mutating func sequence(map: Map) throws {
    try image ~> map["image"].transformToJson{ UIImagePNGRepresentation($0)!.base64EncodedStringWithOptions([]) }

}

}

Good hint, works perfectly. I used this also for NSURL and other special stuff.


NoModificationAllowedError

No problems in Chrome.  When I DnD a file in Firefox, my React app blows up with:
NoModificationAllowedError: Modifications are not allowed for this document

Per https://developer.mozilla.org/en-US/docs/Web/API/DataTransfer/clearData
Note: This method can only be used in the handler for the [dragstart](https://developer.mozilla.org/en-US/docs/Web/API/Document/dragstart_event) event, because that's the only time the drag operation's data store is writeable.

It looks like this code is doing clearData() in the drop handler:
https://github.com/KarimMokhtar/react-drag-drop-files/blob/dev/src/useDragging.tsx#L56
This Stack Overflow is related:
https://stackoverflow.com/questions/58201273/nomodificationallowederror-in-firefox-when-using-dnd-events

Hi @TroyWolf  most likely I am gonna solve it on the weekend. Would you like to contribute and solve it with a PR?

I'll take a stab at it, yes. 👍🏼

@KarimMokhtar should I branch off main?

Nope Please branch from div i will merge to the main after testing and collecting PRs


Added missing sin import from math module.

Project example code was missing sin import and thus was not working. Proper import foxes the issue.

Thanks


Flag to disable changing save states

A flag to avoid writing save states could be useful when testing things.
Some ideas in https://gist.github.com/UnmatchedBracket/e66dd05f8f23cbe5e8d86b58ffbf1ae8.
Would probably prefer it to be something like -save_config=false that we already have.
Ideal if it still permits loading.
Even better if it keeps saving working for this instance, i.e. redirects save state writing to memory. That way, changing settings that require game reinit (e.g. language change) keep working during this as well. Is optional though. Doing it this way would likely live within VFS layer.

Flag suggestion: -debug_save_states=false.

I went the VFS route and the new -readonly flag now will disable state and config saving, while retaining all other game behavior as normal.


[Windows] Bug: npm ENOENT in %APPDATA%/npm

Which packages are affected?

[ ] @eslint/compat
[ ] @eslint/config-array
[ ] @eslint/core
[X] @eslint/migrate-config
[ ] @eslint/object-schema

Environment
Node version: 22.4.1
npm version: 10.8.1
ESLint version: 10.4.5 AND 11.0.0
Operating System: Windows 11 (Windows_NT 10.0.22631) plus my other local Windows 11 PC
What did you do?
First, I hope this is the right place to open this issue. This is the only npx command I've had issue with recently so I assume it's nothing I've done wrong 😁
What I did
Migrating my .eslintrc.json file using npx @eslint/migrate-config ".eslintrc.json"
What did you expect to happen?
The command to run successfully
What actually happened?
I have npm installed at C:\Program Files\nodejs and there's nothing in my AppData folder.
PS G:\MyPath> npx @eslint/migrate-config ".eslintrc.json"
npm error code ENOENT
npm error syscall lstat
npm error path C:\Users\MyUser\AppData\Roaming\npm
npm error errno -4058
npm error enoent ENOENT: no such file or directory, lstat 'C:\Users\MyUser\AppData\Roaming\npm'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: C:\Users\MyUser\AppData\Local\npm-cache\_logs\2024-07-17T12_50_57_438Z-debug-0.log

See workaround and details below 👇
Link to Minimal Reproducible Example
N/A
Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
Details taken from the log file
0 verbose cli C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 silly config load:file:C:\Program Files\nodejs\node_modules\npm\npmrc
4 silly config load:file:G:\MyPath\.npmrc
5 silly config load:file:C:\Users\MyUser\.npmrc
6 silly config load:file:C:\Users\MyUser\AppData\Roaming\npm\etc\npmrc
7 verbose title npm exec @eslint/migrate-config .eslintrc.json
8 verbose argv "exec" "--" "@eslint/migrate-config" ".eslintrc.json"
9 verbose logfile logs-max:10 dir:C:\Users\MyUser\AppData\Local\npm-cache\_logs\2024-07-17T12_50_57_438Z-
10 verbose logfile C:\Users\MyUser\AppData\Local\npm-cache\_logs\2024-07-17T12_50_57_438Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
14 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules/@topmarksdevelopment/hover-box
15 http fetch GET 200 https://registry.npmjs.org/@eslint%2fmigrate-config 560ms (cache miss)
16 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
17 verbose stack Error: ENOENT: no such file or directory, lstat 'C:\Users\MyUser\AppData\Roaming\npm'
17 verbose stack     at async lstat (node:internal/fs/promises:1024:18)
17 verbose stack     at async #loadActual (C:\Program Files\nodejs\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\load-actual.js:112:20)
17 verbose stack     at async exec (C:\Program Files\nodejs\node_modules\npm\node_modules\libnpmexec\lib\index.js:203:26)
17 verbose stack     at async Npm.exec (C:\Program Files\nodejs\node_modules\npm\lib\npm.js:207:9)
17 verbose stack     at async module.exports (C:\Program Files\nodejs\node_modules\npm\lib\cli\entry.js:74:5)
18 error code ENOENT
19 error syscall lstat
20 error path C:\Users\MyUser\AppData\Roaming\npm
21 error errno -4058
22 error enoent ENOENT: no such file or directory, lstat 'C:\Users\MyUser\AppData\Roaming\npm'
23 error enoent This is related to npm not being able to find a file.
23 error enoent
24 verbose cwd G:\MyPath
25 verbose os Windows_NT 10.0.22631
26 verbose node v22.4.1
27 verbose npm  v10.8.1
28 verbose exit -4058
29 verbose code -4058
30 error A complete log of this run can be found in: C:\Users\MyUser\AppData\Local\npm-cache\_logs\2024-07-17T12_50_57_438Z-debug-0.log

Workaround
I have npm installed at C:\Program Files\nodejs and no npm folder at %AppData% (or C:\Users\MyUser\AppData\Roaming).
I managed to get around the issue by creating the npm folder and adding 2 shortcuts for npm and npx that link to the files in  C:\Program Files\nodejs. To do this: have both files selected in nodejs folder, hold down your alt mouse button (usually right), drag it over to the new npm folder and release, then select "create shortcuts here" and rename them to npm and npx (remove the .ps1 - Shortcut)
With these shortcuts in place I could run the command without issue as below
PS G:\MyPath> npx @eslint/migrate-config ".eslintrc.json"
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

Migrating .eslintrc.json

Wrote new config to ./eslint.config.mjs

You will need to install the following packages to use the new config:

You can install them using the following command:

npm install  -D

P.s. it also seems you're outputting an install message even when nothing is required 😁

This is directly related to your installation of Node.js/npm and not with the package itself.
Another way to use the tool is just to install it globally and run from there:
npm install @eslint/migrate-config -g
@eslint/migrate-config .eslintrc.json


Introduce mesonBuildDir

#170697 introduced cmakeBuildDir, we want the same thing for Meson for the same reasons.
Beyond the reasons given in that PR there is one additional one:
During local development is is very nice to have multiple dev shells building the project for different platform. For this to work, we need each dev shell / incremental build to by siloed in a separate build directory. If we can specify a separate cmakeBuildDir in each dev shell, this becomes more convenient.

https://github.com/jonringer/nixpkgs/blob/master/pkgs/development/tools/build-managers/meson/setup-hook.sh#L23-L24 this is the hard-coded build in the Meson setup hook that needs to be modified.

https://github.com/NixOS/nixpkgs/pull/342868 fixed this


tests, network: Remove SkipWhenNotDualStackCluster

What this PR does
Use labels instead.
It statically determine which tests to run, without dynamic skipping.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer
We can also consider Dual stack to be the only one that supports IPv4 (this is true atm at least for kubevirtci)
and then we can drop also SkipWhenClusterNotSupportIpv4.
But maybe we do have external clusters where there is IPv4 only.

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

None

/test pull-kubevirt-e2e-k8s-1.29-ipv6-sig-network
lets see it runs the same amount of tests / pass

/hold
need to fix something

/hold cancel
Fix a mistake, the label should be on one of the Entries only (assuming we can add decorator to Entry as well, lets see the results)
Added commented as discussed

/test pull-kubevirt-e2e-k8s-1.29-ipv6-sig-network

/sig code-quality

Thanks @oshoval!
/approve


Add UI for unsharing shared chats

Adds an "Unshare" button in the header of shared chats.  I need to test this fully on prod to make sure it all works, which I'll do once CI passes.

Works on prod

Fixed a bug related to sharing while testing this, no PR: https://github.com/tarasglek/chatcraft.org/commit/d27e7694f99dd205b6122551ef2d1a0587aadec0


Problem with building in linux

flutter run -d linux returns error

Seems like you are on an incompatible Flutter version. What your flutter doctor output?

@Norbert515 Here

I have the same problem, for which version of flutter did your run it @Norbert515 ?


Disable backtick quotes if it is not a template

Now you could write either
let a = 'hello'

or
let a = `hello`

And it would pass standard linter for both cases, even if in the second case the template doesn't have any interpolated variables and in fact is just a different form of a string. So you could mix both forms, something conceptually similar to mixing " and ' quotes.
ESLint allows us to prevent this behavior by adding a rule
"quotes": [2, "single"]

This rule makes ESLint to throw an error for this
let a = `hello`

but don't throw any errors for this
let subject = 'world'
let a = `hello, ${world}`

Also see this issue in ESLint.

NACK,  only because it means if I am using templates,  I have more rules to remember or otherwise have standard bark at me.

I don't mind this, it'd warn for weird mixing stuff like:
var a = `hello` + '  my ' + `brethren`

Standard would tell you that you probably meant to either use single quotes or interpolate, but definitely not the weird thing right there above. I feel that this would indeed be in the spirit of https://github.com/feross/standard/issues/791 where there's a default way to do things, and we warn if people are deviating from it without there being a need to.
note: I don't really mind whatever way it goes, just like - feel it's consistent with the ruleset we've been applying so far.

it'd be simpler to just disable non-backtick quotes entirely

@dcousens In this case it would be necessary to rewrite README.md and the front page of https://standardjs.com , as they state that

Single quotes for strings – except to avoid escaping

Yeah personally I use back ticks all the time that way I am always ready to interpolate

it'd be simpler to just disable non-backtick quotes entirely

I like having two types of quotes to indicate intent. Interpolating is rare enough that I appreciating having it explicitly called out by the ` character.

Well really there is no harm leaving a template string as an interpolated string. Yeah normally it means that you are going to interpolate but I think it would be weird to have that as a rule

There also a couple of arguments against making backtick quotes default for all strings instead of single quotes:

Using backticks for strings without interpolated variables adds need of additional care about escaping because if you are not planning to interpolate, but for some reason want to have in your string literally ${console} then it should be properly escaped in order to avoid runtime errors or perhaps even vulnerabilities. It also not always possible to automatically determine the cases when an expression should be escaped and when it is not, like in this example with ${console}.
Making backticked strings default instead of single quoted ones would break all the codebases in pure ES5 that can't use string template syntax but use standard to enforce style rules.

I can see how disabling backticks would fit with Standard's existing philosophy

In ES5, the the rule is that you must use single quotes, except when you need the extra functionality of double quotes (e.g. to quote a single quote)
In ES6, a rule saying that you must use single quotes, except when you need the extra functionality of double quotes or backticks would make sense.  Extra functionality would include:

quoting other types of quote
templates
literal new lines

I also think this would make sense, such that

Single quotes for strings – except to avoid escaping

is enforced. Note that the implementation is very simple: Remove the "allowTemplateLiterals": true option from the quotes rule. Despite the naming of the option, "allowTemplateLiterals": false actually still allows template literals when their extra functionality is used, see examples in the doc for the quotes rule.

https://github.com/standard/eslint-config-standard/pull/151

Thanks for the input everyone!
I think that we should disallow template literals when placeholders or tagged template features are not used.
console.log('hello there')    // ✓ ok
console.log("hello there")    // ✗ avoid
console.log(`hello there`)    // ✗ avoid

$("<div class='box'>")        // ✓ ok
console.log(`hello ${name}`)  // ✓ ok

Only 1 ecosystem package (webtorrent-desktop) needed to be updated, and it was just one line that needed the update: https://github.com/webtorrent/webtorrent-desktop/commit/c8f1e23b1a3908e3b616b457736fdc2a31af9502
I'm going to ship this in v14.

Lovely!

And what about this case?
console.log(`I'd like to quote someone: "That will force manual escaping on me"`)

It seems to be legit, but it's forbidden by the rule.

@ArmorDarks as you know, Standard's preferred quotes are single quotes. Allowing double quotes when the string contains single quotes is one thing. Because single and double quotes are equal in all ways, as far as I know. Since backticks are a different language feature (inline expression and tags), allowing them in order to avoid escape characters is a different consideration.

I'm not sure how I'm supposed to feel about maintaining sentences like these and being forced to escape manually myself.
This rule is quite problematic, because using backticks without any tags or expressions clearly conveys the intent: this is language being displayed to humans.

@langsri-sha, could you please expand on "this is language being displayed to humans"? I don't quite understand what "language" means here. The string?

@mightyiam here are a few instances where I use backticks because the string is something that's communicated directly to humans:
debug(`Use the Force, Luke!`)
new Error(`Whoops, something went terribly wrong!`)
test(`foo does something`, () => {})

So was able to keep things neat and tidy with just single quotes and backticks. Now there's mixed use of single quotes, double quotes, escape sequences and backticks :grimacing:!

@langri-sha what do you mean by "communicated directly to humans", please? You mean, while those humans are reading the code? Or by test failure messages, error messages and debug logs?

By this I mean strings that are used to express written language. The case the OP makes with:

let a = 'hello'
let a = hello

:point_up: I see this more as "I have a problem that I can express strings in two different ways", but I don't think this sufficiently accounts for written language, like this paragraph that I just writing. As I said, we've moved from a consistent use of single quotes and backticks to mixed use of single quotes, double quotes, escape sequences and backticks.

@langri-sha thank you for the explanation. I understand what you mean now.
Personally, it's a non-issue for me. If you have a suggestion, could you please open a new issue with that?


Fix various cases in matching with constraints and affinities

-e affinity:container!=redis wasn't matching nodes with no container
-e affinity:images!=redis wasn't matching nodes with no image
-e constraint:region!=us-west wasn't matching containers with no label
-e affinity:container==redis wasn't matching containers names redis, because their name is actually /redis

I updated the description

I believe this is still broken.
Let's say you have two containers on node1, "A" and "B".
You run with affinity:container!=B.
When evaluating "A", affinity.Match will return true and will immediately accept node1 and break, even though it has "B".
We have to rethink NOTEQ expressions. I think we should somehow give Match the entire list of candidates we want to match and let it handle the not equal correctly (including returning true if the operator is != and the list is empty).

@aluzzardi you are probably right, we need to a list with all the containers and call Match only once with the list, like we do in images.

Yes, however I think we are doing it wrong in images as well: we call Match in a loop while going through the list of images, the whats should be constructed in the loop and Match should be called only once outside of the loop.
In that case, it doesn't make sense anymore for Match() to take varargs.

yes, and we don't need matchempty anymore, we can just check if the match parameter is empty :P

I noticed this behavior yesterday, I made a commit based on @vieux's branch to not interfere with this PR. mota@19bba42681a86c408add05fd60850768391343e2
I also fixed tests.

replaced by #327


test: update snapshots for guided remediation

There is a vulnerability reported on commons-io:commons-io and guided remediation further bumps the version to its fixed version.

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

Project coverage is 69.28%. Comparing base (cec1fa4) to head (7252d79).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1296      +/-   ##
==========================================
+ Coverage   68.45%   69.28%   +0.82%
==========================================
  Files         175      175
  Lines       16832    13120    -3712
==========================================
- Hits        11523     9090    -2433
+ Misses       4681     3401    -1280
- Partials      628      629       +1

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


[NVCC] Bugfix nvcc command tool that relies on the compile time env

TVM_CXX_COMPILER_PATH indicates the env in compilation and do not guarantee to exist in runtime

cc @rkimball @junrushao1994


Support exceptions 0.10.*

@elcuy @sestrella It looks good to me. If you don't mind I'll proceed with uploading the package.


Upstream update

Problem

Upstream update

Solution

Update sources in manifest.toml

PR Status

[x] Code finished and ready to be reviewed/tested
[ ] The fix/enhancement were manually tested (if applicable)

Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

!testme


(URGENT) Conflict in document type with Metanorma (brochure)

[relaton-bib] WARNING: type "brochure" is invalid.
...
Document Attributes: standard is not a legal document type: reverting to 'brochure'

The brochure document type is a valid type in BIPM.
Issue discovered in:

https://github.com/metanorma/bipm-si-brochure/pull/213

@ronaldtse we have type and doctype attributes. The type is defined in the grammar and can't be brochure. The BIPM doctype is defined in the flavor gramma and brochure is allowed value for it.
The log message said that the type attribute has brochure value which is invalid.

@andrew2net does this mean it is an issue with Metanorma? Ping @opoudjis .

@ronaldtse If the incorrect type comes from Metanorma then it does.

Thank you @andrew2net ! Will wait for @opoudjis to review.

This is specific to the compilation of collections.

Suppress error report on default doctype, if no doctype has been supplied at all.


Feature request: support user-defined macros written as SQL

Currently, user-defined macros need to be defined as python. An alternative SQL-based syntax would be more consistent with MODEL and AUDIT. That is, having a MACRO function to define user-defines macros in .sql files:
MACRO(
  name forall,
  defaults (
    condition NULL
  )
);
SELECT *
FROM @this_model
WHERE
  @AND(
    @REDUCE(@criteria, (l,r) -> l AND r),
    @condition,
  )

For supporting named arguments, perhaps a more general arguments could work, i.e.: you'd have to define each argument and its default value (and maybe its type for coercion)?:
MACRO(
  name accepted_range,
  arguments (
    min_v NULL,
    max_v NULL,
    inclusive TRUE,
    condition NULL,
  )
);
...

i believe you can do this already
https://sqlmesh.readthedocs.io/en/stable/concepts/macros/sqlmesh_macros/#local-variables

closing for now but happy to discuss alternatives

We do currently support reusable SQL macros written with jinja
https://sqlmesh.readthedocs.io/en/stable/concepts/macros/jinja_macros/#user-defined-macro-functions

Which, presumably, is an argument for having an equivalent in SQL directly. As a SQLMesh user that doesn't have to deal with dbt or jinja, it would be a more consistent experience to be able to write these as SQL. Writing them in python is okay, but less accessible to non-developer types of users (e.g.: "data analysts" or similar SQL-mostly roles).


Writing tests and functions for each function

For function 3, close_up, this issue is completed and PR was merged in.


capture_sequence() and capture_continuous() only capture RAW Bayer data on first frame

According to the documentation...
The bayer parameter of the capture() method causes the raw Bayer data recorded by the camera’s sensor to be output as part of the image meta-data.
I assume (maybe wrongly) that the bayer parameter should also be supported by the capture_sequence() and capture_continuous() methods.
However, tests show that the raw Bayer data is only added to the header of the first JPEG frame captured when using capture_sequence() and capture_continuous() methods, and not subsequent frames.
For example, when capturing 3 frames using the capture() method...
camera.capture('bayer0.jpeg', format='jpeg', bayer=True)
camera.capture('bayer1.jpeg', format='jpeg', bayer=True)
camera.capture('bayer2.jpeg', format='jpeg', bayer=True)

We generate 3 JPEG encoded images approximately 7MB in size, with the Bayer data packed in the header just as we would expect.
ls -l
-rw-r--r-- 1 pi pi 7224575 Mar  1 12:32 bayer0.jpeg
-rw-r--r-- 1 pi pi 7244684 Mar  1 12:32 bayer1.jpeg
-rw-r--r-- 1 pi pi 7229215 Mar  1 12:32 bayer2.jpeg

However, if we try to do the equivalent thing using capture_sequence() or capture_continuous() methods then the resulting file sizes indicate that only the first image has the Bayer data in the header (and indeed I have confirmed this by inspecting the data).
ls -l
-rw-r--r-- 1 pi pi 7206216 Mar  1 12:37 bayer0.jpeg
-rw-r--r-- 1 pi pi  821918 Mar  1 12:37 bayer1.jpeg
-rw-r--r-- 1 pi pi  815960 Mar  1 12:37 bayer2.jpeg

A demonstration of the problem follows. Simply uncomment the appropriate function call at the bottom of the script.
import time
import picamera
import io

bayer_mode = True
dir = '/home/pi/camera/bayer_bug'
num_of_images = 3

def filename_gen(num_of_frames):
    """
    Filename generator
    """
    frame = 0
    while frame < num_of_frames:
        yield '%s/bayer%d.jpeg' % (dir, frame)
        frame += 1

def capture_single_filenames(num_of_images):
    """
    Use camera.capture() method using filename as 1st argument
    """
    print('Using camera.capture() with filename...')
    stream = io.BytesIO()
    with picamera.PiCamera() as camera:
        camera.start_preview()
        # Let the camera warm up for a couple of seconds
        time.sleep(2)

        gen = filename_gen(num_of_images)
        start = time.time()
        for count in range(num_of_images):
            # Capture the image, including the Bayer data
            camera.capture(next(gen), format='jpeg', bayer=bayer_mode)
            # print('Captured image %d' % count)
        elapsed = time.time() - start
        print('Captured %d frames at %.2ffps' % (num_of_images, num_of_images / elapsed) )

def capture_single_stream(num_of_images):
    """
    Use camera.capture() method using stream as 1st argument
    """
    print('Using camera.capture() with stream...')
    stream = io.BytesIO()
    with picamera.PiCamera() as camera:
        camera.start_preview()
        # Let the camera warm up for a couple of seconds
        time.sleep(2)
        stream = io.BytesIO()

        start = time.time()
        for count in range(num_of_images):
            # Capture the image, including the Bayer data
            camera.capture(stream, format='jpeg', bayer=bayer_mode)
            # print('Captured image %d' % count)
            # Get number of bytes in the stream
            num_of_bytes = stream.tell()
            # Rewind the stream to start
            stream.seek(0)
            # Save stream contents to file
            filename = '/home/pi/camera/bayer_bug/bayer%d.jpeg' % count
            with open(filename, 'wb') as f:
                f.write( stream.read( num_of_bytes ) )
            # Empty the stream
            stream.seek(0)
            stream.truncate()
        elapsed = time.time() - start
        print('Captured %d frames at %.2ffps' % (num_of_images, num_of_images / elapsed) )

def capture_sequence_filenames(num_of_images):
    """
    Use camera.capture_sequence() method
    """
    print('Using camera.capture_sequence() with filename generator...')
    with picamera.PiCamera() as camera:
        camera.start_preview()
        # Let the camera warm up for a couple of seconds
        time.sleep(2)

        start = time.time()
        camera.capture_sequence( filename_gen(num_of_images), format='jpeg', bayer=bayer_mode )
        elapsed = time.time() - start
        print('Captured %d frames at %.2ffps' % (num_of_images, num_of_images / elapsed) )

def capture_continuous_filenames(num_of_images):
    """
    Use camera.capture_continuous() method using filename as 1st argument
    """
    print('Using camera.capture_continuous() with filename...')
    with picamera.PiCamera() as camera:
        camera.start_preview()
        # Let the camera warm up for a couple of seconds
        time.sleep(2)

        start = time.time()
        for count, filename in enumerate( camera.capture_continuous( '/home/pi/camera/bayer_bug/bayer{counter}.jpeg', format='jpeg', bayer=bayer_mode ) ):
            # print('Captured image %d' % count)
            if count == (num_of_images-1):
                break
        elapsed = time.time() - start
        print('Captured %d frames at %.2ffps' % (num_of_images, num_of_images / elapsed) )

def capture_continuous_stream(num_of_images):
    """
    Use camera.capture_continuous() method using stream as 1st argument
    """
    print('Using camera.capture_continuous() with stream...')
    stream = io.BytesIO()
    with picamera.PiCamera() as camera:
        camera.start_preview()
        # Let the camera warm up for a couple of seconds
        time.sleep(2)
        stream = io.BytesIO()

        start = time.time()
        for count, foo in enumerate( camera.capture_continuous( stream, format='jpeg', bayer=bayer_mode ) ):
            # print('Captured image %d' % count)
            # Get number of bytes in the stream
            num_of_bytes = stream.tell()
            # Rewind the stream to start
            stream.seek(0)
            # Save stream contents to file
            filename = '/home/pi/camera/bayer_bug/bayer%d.jpeg' % count
            with open(filename, 'wb') as f:
                f.write( stream.read( num_of_bytes ) )
            # Empty the stream
            stream.seek(0)
            stream.truncate()
            if count == (num_of_images-1):
                break
        elapsed = time.time() - start
        print('Captured %d frames at %.2ffps' % (num_of_images, num_of_images / elapsed) )

# capture_single_filenames(num_of_images)
#capture_single_stream(num_of_images)
capture_sequence_filenames(num_of_images)
#capture_continuous_stream(num_of_images)
#capture_continuous_filenames(num_of_images)

Interesting - it might be that the request for the bayer data needs to be made on every encoding start. If that's all it takes, it's a simple fix which I can get into 1.11.

Yup, it needs to be set before setting the capturing parameter every time. The original implementation passed in a path/filename, so you didn't want it overwriting files.

It would be great to see some progress on this in 1.11. This issue is still causing me some pain.

PRs welcome! Unfortunately at the moment I've got bigger issues with 1.11 that need sorting first (segfaults in data callbacks which I've spent two days trying to track - fruitlessly so far).


HWKAPM-517 Move 'trace' specific MDBs and JMS publishers to a sub-pac…

…kage, in preparation for adding similar processing capabilities for Spans

@pavolloffay Here's the next one - just moving some of the trace specific JMS classes into sub-package to separate them from the Span based implementations.

LGTM :+1:

@pavolloffay Thanks!


vagrant provision

When I am executing vagrant up or vagrant provision, it fails with the below error. Any suggestion to fix this is welcome.
==> local: /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.60/lib/chef/application/client.rb:442:in `loop'
==> local: /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.60/lib/chef/application/client.rb:442:in `interval_run_chef_client'
==> local: /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.60/lib/chef/application/client.rb:426:in `run_application'
==> local: /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.60/lib/chef/application.rb:58:in `run'
==> local: /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.60/lib/chef/application/solo.rb:216:in `run'
==> local: /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.10.60/bin/chef-solo:25:in `<top (required)>'
==> local: /usr/bin/chef-solo:52:in `load'
==> local: /usr/bin/chef-solo:52:in `<main>'
==> local: [2016-05-19T01:14:10-07:00] INFO: HTTP Request Returned 404 Not Found: Parent not found: chefzero://localhost:8889/nodes
==> local: ================================================================================
==> local: Chef encountered an error attempting to load the node data for "vagrant-2b949cc8"
==> local: ================================================================================
==> local: Resource Not Found:
==> local: -------------------
==> local: The server returned a HTTP 404. This usually indicates that your chef_server_url is incorrect.
==> local: Relevant Config Settings:
==> local: -------------------------
==> local: chef_server_url "chefzero://localhost:8889"
==> local: Platform:
==> local: ---------
==> local: x86_64-linux
==> local: Running handlers:
==> local: [2016-05-19T01:14:10-07:00] ERROR: Running exception handlers
==> local: Running handlers complete
==> local: [2016-05-19T01:14:10-07:00] ERROR: Exception handlers complete
==> local: Chef Client failed. 0 resources updated in 01 seconds
==> local: [2016-05-19T01:14:10-07:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> local: [2016-05-19T01:14:10-07:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
==> local: [2016-05-19T01:14:10-07:00] ERROR: 404 "Not Found"
==> local: [2016-05-19T01:14:10-07:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

==> local: Chef encountered an error attempting to load the node data for "vagrant-2b949cc8"
==> local: ================================================================================
==> local: Resource Not Found:
Do you have a role created that is named vagrant-2b948cc8?

I believe this is related to this issue in Chef core.
The fix seems to be to add the following to your chef_solo provisioner section in your Vagrantfile:
chef.version = '12.10.40'

The above seemed to work for me but is not working, now:
Omnitruck artifact does not exist for version 12.10.40 on platform ubuntu

As an aside: This seems like its resolved by updating Vagrant to > 1.8.1


Unintended move on button click

Clicking on a button within a widget, the listener gets called, but also dragging of the widget is activated. The click listener seems to filter the mouse up event, so the widget sticks at the mouse pointer. This effect can be reproduced with the demo app.

This is Firefox specific issue.

Actually now repeatable on Chrome too... looks like gridstack.js and vaadin's buttons do not like each others. This might be tricky to resolve.

0.2.0 has a workaround, it now uses drag handles. This because gridstack.js and Vaadin components do not behave well together, if they fight over same events.

0.2.1 will get GridStackButton that resolves issue without separate drag handle. New issues to be made with other misbehaving components.

Both workarounds in 0.2.1


cursor is not reappearing

Hyprland Version
f5913135c638997f8c13a52d0760803947ae3889
Bug or Regression?
Regression
Description
Broken in f5913135c638997f8c13a52d0760803947ae3889
Cursor is not  reappearing when being moved on mpv (doesn't happen on firefox or vlc)
not sure where is the issue here, but doesn't happen on sway-git
How to reproduce
use follow_mouse = 2
play a video in mpv
set mpv in fullscreen mode (internally)
on another monitor click in a window, so that mpv loses focus
move the mouse to mpv without giving it focus
mouse will disapear
after https://github.com/hyprwm/Hyprland/commit/f5913135c638997f8c13a52d0760803947ae3889 cursor does not reappear anymore
Edit: fullscreen doesn't seem to be required
Crash reports, logs, images, videos
No response

Sometimes happens for me on Qt apps too. Namely Dolphin, which I use a lot. Moving the cursor outside of that region or switching a workspace brings it back.

fixed 7a2027d1fd5d447a6e0f8af8b7d2f8c2e82da7c4


x86.c: sanitize data read from sysfs during board detection

Fixes #771. Tested on Edison and mock (though the latter isn't affected).

Merged. Thanks for the quick fix!


Optimized RAM usage for Reed Solomon

By removing unneeded / redundant bytes in the _gfExp array, the footprint of this array could be reduced by 257 bytes.
After 255 bytes, the array just repeats itself.
Benificial especially for mc's with minor RAM like ATMEGA328P.

Hi timoxd7,
Thanks for the pull request.
I'm going to make this a compile time option and integrate it into the next release.
Cheers,
Jim

Hi timoxd7,
I added the SSF_RS_ENABLE_GF_MUL_OPT option that allow you to decide to optimize GF_MUL for speed or favor code size.
Best,
Jim


PropertyMapLoader has excessive logging

The default Play logback configuration explicitly disables the PropertyMapLoader because it logs at too high a level:
  <!-- Off these ones as they are annoying, and anyway we manage configuration ourselves -->
  <logger name="com.avaje.ebean.config.PropertyMapLoader" level="OFF" />

https://github.com/playframework/playframework/blob/master/framework/src/play-logback/src/main/resources/logback-play-default.xml#L34
We were going through the logback configuration and thought to mention it https://github.com/playframework/playframework/pull/5391#discussion_r47827695
Is this something that is still an issue?

I presume this could be stated as:
'the logging in property map loader currently logs messages at INFO level -
can those be reduced to DEBUG level'
Is that an accurate interpretation?
Thanks, Rob.
On 18 Dec 2015 7:20 am, "Will Sargent"<EMAIL_ADDRESS>wrote:

The default Play logback configuration explicitly disables the
PropertyMapLoader because it logs at too high a level:

https://github.com/playframework/playframework/blob/master/framework/src/play-logback/src/main/resources/logback-play-default.xml#L34
We were going through the logback configuration and thought to mention it playframework/playframework#5391
(comment)
https://github.com/playframework/playframework/pull/5391#discussion_r47827695
Is this something that is still an issue?
—
Reply to this email directly or view it on GitHub
https://github.com/ebean-orm/avaje-ebeanorm/issues/501.

Yes, sorry if that wasn't clear.

No worries.  Looking at PropertyMapLoader the log messages are at DEBUG level (apart from ERROR).
Looking at history:  This probably was 'fixed' in #457 "When ebean.properties does not exist do not log error message" ... which was included in version 6.11.1
So yes, probably fixed in 6.11.1 I'd say.

Thanks @rbygrave. We can probably close this then. I sent a PR to upgrade Play to use a newer version that has the improvement. https://github.com/playframework/play-ebean/pull/68

Thanks. Closing.


Change the icon colour for read posts

In Firefox's Live Bookmarks, when I open a link in a new tab, the read post changes to a grey colour, and unread posts are an orange colour as shown below:

It's easier to distinguish between posts I've opened and new unopened posts.
Please bring this to Livemarks soon as Firefox 64 will remove native Live Bookmarks and this extension is the closest in user interface to Firefox's built in RSS tool.
Thanks!

It's currently not possible to do with the current extension framework, but #17 plans to add something very similar.


Controller doesn't fully clean up removed resources

Essentially as stated in the title, we have Terraform resources that we are applying via Flux.
In the log below you can see that the "destroy" and "destroyResourcesOnDeletion" is called successfully however once the resource is actually removed, it seems to be thrown into a failed reconciliation loop which results in some stale artifacts being left behind in Metrics and being reported in an "Unknown" state.
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:56:52.480Z","msg":"calling plan ...","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:56:52.505Z","msg":"plan to destroy","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:56:57.710Z","msg":"plan: ok, found drift: true","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:56:57.753Z","msg":"save tfplan: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:56:57.813Z","msg":"load tf plan: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:57:00.997Z","msg":"apply: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:57:00.997Z","msg":"inventory is disabled","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:57:01.022Z","msg":"finalizing destroyResourcesOnDeletion: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:57:01.061Z","msg":"finalizing secrets: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:57:01.087Z","msg":"clean up dir: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:57:01.087Z","msg":"setting up terraform","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"error","ts":"2024-07-09T15:57:01.088Z","msg":"unable to update status before Terraform initialization","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z","error":"Terraform.infra.contrib.fluxcd.io \"5539da99-8111-4e42-8f23-0496e977a0b2\" not found"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"error","ts":"2024-07-09T15:57:01.088Z","msg":"error in terraform setup","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z","error":"Terraform.infra.contrib.fluxcd.io \"5539da99-8111-4e42-8f23-0496e977a0b2\" not found"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"info","ts":"2024-07-09T15:57:01.088Z","msg":"clean up dir: ok","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"error","ts":"2024-07-09T15:57:01.088Z","msg":"unable to update status after the reconciliation is complete","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","reconciliation-loop-id":"3a3b2f5b-74f0-4922-9832-af9b074d668e","start-time":"2024-07-09T15:56:34.691Z","error":"Terraform.infra.contrib.fluxcd.io \"5539da99-8111-4e42-8f23-0496e977a0b2\" not found"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"error","ts":"2024-07-09T15:57:06.107Z","msg":"Reconciler error","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"bbdfadac-2ca3-48ef-bdb7-42cb25396149","error":"Terraform.infra.contrib.fluxcd.io \"5539da99-8111-4e42-8f23-0496e977a0b2\" not found"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"error","ts":"2024-07-09T15:57:06.107Z","msg":"Hit an error","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"d9e12a45-d383-4129-8eb7-b3fd6c818ae0","reconciliation-loop-id":"398a88bd-10c8-48ce-8a8f-d9f1e668dd94","start-time":"2024-07-09T15:57:06.107Z","function":"TerraformReconciler.Reconcile","namespacedName":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"error":"Terraform.infra.contrib.fluxcd.io \"5539da99-8111-4e42-8f23-0496e977a0b2\" not found"}
tf-controller-655d5c74c7-mr7xl tf-controller {"level":"error","ts":"2024-07-09T15:57:06.113Z","msg":"Hit an error","controller":"terraform","controllerGroup":"infra.contrib.fluxcd.io","controllerKind":"Terraform","Terraform":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"namespace":"edge-workspace","name":"5539da99-8111-4e42-8f23-0496e977a0b2","reconcileID":"a975fe22-a460-4d93-9857-8b2278804552","reconciliation-loop-id":"fad918b4-ecd9-4053-8077-4de80eb8ceef","start-time":"2024-07-09T15:57:06.113Z","function":"TerraformReconciler.Reconcile","namespacedName":{"name":"5539da99-8111-4e42-8f23-0496e977a0b2","namespace":"edge-workspace"},"error":"Terraform.infra.contrib.fluxcd.io \"5539da99-8111-4e42-8f23-0496e977a0b2\" not found"}

#1362 should solve this issue.

#1362 should solve this issue.

@TarasLykhenko  Seems not resolved. I see deleted Terraform objects still remain in metrics in Unknown status.
Using latest tofu-controller main-cb032d47


RegisterView: email varification on sign up fix

I think signup email sending was working fine during invoking: RegisterView.perform_create, where we call allauth.account.utils.complete_signup, allauth.account.utils.perform_login. But now it stops at string in perform_login:
adapter = get_adapter(request)
    if not user.is_active:
        return adapter.respond_user_inactive(request, user)

Not surprising, as new user is not active. Thus, I have provided the solution for that in RegisterView.
Please, let me know if I have mistaken somewhere or the same can be achieved in smarter way.
Thanks!

Hi,
as a user of rest-auth, thanks for the contribution!
This repo is not maintained anymore, so the development moved to dj-rest-auth. (reference: https://github.com/Tivix/django-rest-auth/issues/568)
It may be best, if you move this PR there. (and upgrade to using dj_rest_auth)
new repo link: https://github.com/jazzband/dj-rest-auth (I'm not the upkeeper of that repo, it just makes sense for me to help you merge your PR)
Many Thanks,
Barney


Redrawing the view

Hey guys, not a bug, but a Question, After the view gets obliterated via the call to startAnimation(), how do I go about redrawing it or making the view visible again? My goal is to have the ImageView disappear (shatter) using the animation, and then have it come back into view with a new image.
Thanks for the help and the awesome project guys! It's really well done!

So.... can this not be done then? I assume not since this was closed without any more info...

Hi,
It was auto closed by the commit message.
Please check new version 0.1.1. It might take some time for maven repository to update.
Then you may try to add your view after animation has ended:
    @Override
    public void onAnimationFinished() {
        mTilesFrameLayout.addView(view, 0);
    }

view can be newly inflated view or the same view that was inside of TilesFrameLayout initially.
Let me know how that works for you.
Thanks for your feedback, I'm glad you enjoy the lib :)

Ah excellent, thank you mlatu, I will test in the morning. And love the library! You guys at Yalantis always have some of the best stuff around!

Works perfect. Thanks again guys.


Added Tests for Consistency Testing

Signed-off-by: Latife Sen<EMAIL_ADDRESS>

[ ] Ensure that the commit message is a good commit message
[ ] Change in CHANGELOG.md described
[ ] Tests created for changes
[ ] Screenshots added (for UI changes)

There is a misunderstanding what the term "Test" meant in "Test for consistency". I meant that the Repository can check for consistency. Not that there is a JUnit test case. Unfortunately, the repository interaction was simplified this month. So, there now is RepositoryFactory.getRepository() and the REST resources are residing in their own project.
So, these are the next steps:

Understand IRepository
Understand BackendUtils
Understand CSARExporter + TOSCAExportUtil
Implement RepositoryConsistencyChecker which offers a single method List<ConsistencyCheckErrors> checkForConsistency(IRepository repository)
Implement a REST endpoint in org.eclipse.winery.repository.rest allowing access to this method
Implement an Angular-Component at org.eclipse.winery.repository.ui at the Administration tab which calls this method.

I think, this is PR is obsolete as there is a new branch https://github.com/OpenTOSCA/winery/tree/AddedConsistencyCheck
Naming hint: In the pull request template of Eclipse Winery, there is a link to good commit message:

Write the summary line and description of what you have done in the imperative mode, that is as if you were commanding someone. Start the line with "Fix", "Add", "Change" instead of "Fixed", "Added", "Changed".

This also applies for branch names.

One can also reuse a pull request by overwriting the branch.


question with RBlockingQueue.poll(timeout, TimeUnit.SECONDS)

Redisson version: 3.12.1
Java version: 1.8
Hi, in one of our environments BLPOP doesn't pop the elements, though there are elements in the queue when queried via redis-cli with LRANGE command. The issue happens only in one of the environments, are there any known issues with RBlockingQueue.poll(timeout, TimeUnit.SECONDS) where the timeout is zero? This method is called from a while(true) loop, the functionality works for 3-4 hours and then stops popping the elements. As I couldn't reproduce locally I couldn't attach the reproducible code.
          RBlockingQueue<String> queue = redissonClient.getBlockingQueue(queueName);
		try {
                         // some calling methods pass timeout as zero.
			return queue.poll(timeout, TimeUnit.SECONDS);
		} catch (InterruptedException e) {
			LOG.error(ex.message);
		}

Hi,
There are no known issues with BLPOP command. Which Redis vendor do you use?

HI @mrniko It's open source installation. All environments have same infrastructure. My question was if we use 0 timeout will it cause any issue? I will be changing it to queue.poll() as there is no point in using BLOP with 0 timeout. But I am curious are there are any known issues?

My question was if we use 0 timeout will it cause any issue?

No. It's good idea to try to change it with limited timeout. Please let me know if it fix the issue.

@rgampa : Even I am facing same issue in production. Can you please suggest if there is anything you have done to fix it.

Hi @tigernitw , as far as I remember we have replaced the 0 (infinite) timeout with max 5 sec timeout that time. Currently we don't see this behavior in our environments. Over the time we upgraded Redisson version in our code, currently it's at 3.19.2.


test: Updates to e2e tests. Removing AzDriverNode creation on setup/teardown and running scheduler extender tests only for v2 driver

…rnode create/delete before/after controller/scheduler tests.

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build 771969138

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 59.091%

Files with Coverage Reduction
New Missed Lines
%

pkg/azdiskschedulerextender/azdiskschedulerextender.go
7
70.72%

Totals

Change from base Build 768211665:
-0.2%

Covered Lines:
2197

Relevant Lines:
3718

💛  - Coveralls

Pushing these changes for visibility of the bug addressed in this PR. Controller and scheduler tests were deleting AzDriverNode instances which was causing tests running afterwards to fail. Similarly, scheduler extender was being added to v1 driver tests as well, causing another failure.
I've been running all testing configurations since yesterday to verify that there are no further issues. V1 tests are ok but I am now seeing some failures in v2 tests that I want to debug and address in this PR.


iOS: ITMS-90078: Missing Push Notification Entitlement

We identified one or more issues with a recent delivery for your app, "Private Kit" 0.5.6 (11). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement. Xcode does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor's Capabilities pane, or manually add the entitlement to your entitlements file. For more information, see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_ref/doc/uid/TP40008194-CH6-SW1.

I fix this problem by enabling push notification capability.
Click on .xcodeproj -> Capabilities -> Enable Push Notification

I believe this is fixed now.  Please reopen if not.


App collapse when reloading on android

It does not always happen but often happens when you reload the js bundles
26357-27166/com.eggf W/unknown:React: Tried to enqueue runnable on already finished thread: 'native_modules... dropping Runnable.
03-28 14:24:44.154 26357-27166/com.eggf W/MessageQueue: Handler (com.facebook.react.bridge.queue.MessageQueueThreadHandler) {42b9f710} sending message to a Handler on a dead thread
                                                        java.lang.RuntimeException: Handler (com.facebook.react.bridge.queue.MessageQueueThreadHandler) {42b9f710} sending message to a Handler on a dead thread
                                                            at android.os.MessageQueue.enqueueMessage(MessageQueue.java:309)
                                                            at android.os.Handler.enqueueMessage(Handler.java:623)
                                                            at android.os.Handler.sendMessageAtTime(Handler.java:592)
                                                            at android.os.Handler.sendMessageDelayed(Handler.java:563)
                                                            at android.os.Handler.post(Handler.java:323)
                                                            at com.facebook.react.bridge.queue.MessageQueueThreadImpl.runOnQueue(MessageQueueThreadImpl.java:60)
                                                            at com.facebook.react.bridge.ReactBridge.callFunction(Native Method)
                                                            at com.facebook.react.bridge.CatalystInstanceImpl$3.run(CatalystInstanceImpl.java:199)
                                                            at android.os.Handler.handleCallback(Handler.java:730)
                                                            at android.os.Handler.dispatchMessage(Handler.java:92)
                                                            at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
                                                            at android.os.Looper.loop(Looper.java:137)
                                                            at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:184)
                                                            at java.lang.Thread.run(Thread.java:841)

The logcat also print the libc error  after the exception throw out from android java,
03-28 14:24:44.844 26357-27573/com.eggf A/libc: Fatal signal 11 (SIGSEGV) at 0xbbadbeef (code=1), thread 27573 (mqt_js)

The same libc error I have reported before, but not the same situation. https://github.com/facebook/react-native/issues/6562#issuecomment-200079276

@narychen Is this still an issue?

@christopherdro I didn't pay further more attention to it. So let's close it.

I had the same exception after I called reactActivity.finish(). (reactActivity is an instance of ReactActivity)

I have this same exception when I reload the JS after opening a SocketChannel in native Android code. Is there any way to avoid this?

Which version did you use ?

We're using 0.40.

hello any updates? I am facing this error

This error is still an issue and the reason is that the UIManager creates a ShadowNodeRegistry that uses a SingleThreadAsserter.
https://github.com/facebook/react-native/blob/26684cf3adf4094eb6c405d345a75bf8c7c0bf88/ReactAndroid/src/main/java/com/facebook/react/common/SingleThreadAsserter.java#L23
The SingleThreadAsserter locks to the thread it was created with, but when the app reloads, that thread dies.
After the app has reloaded, all further calls to uiManager methods will result in that error.
Not sure what we can do about this, I've been struggling with that issue, and I can't find any way to replace that thread. This issue should be re-opened.

I opened a new issue here https://github.com/facebook/react-native/issues/18413

Tracking in #18413
Duplicate of #18413


HistoryCommand: Returns previous commands in reverse chronological order #534

Fixes #534

v1
@Zhiyuan-Amos submitted v1 for review.

[v1 1/1] HistoryCommand: Returns previous commands in reverse chronological order

(:books: Archive)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/537/1/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

v2
@Zhiyuan-Amos submitted v2 for review.

[v2 1/1] HistoryCommand: Returns previous commands in reverse chronological order

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v1 and v2)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/537/2/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

v3
@Zhiyuan-Amos submitted v3 for review.

[v3 1/1] HistoryCommand: Returns previous commands in reverse chronological order

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v2 and v3)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/537/3/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

@yamgent last call? :>

Apologies as I wasn't around during the discussion, so the first thought that came to my mind concerning this change was that it intuitively makes sense to me, thus the commit message.
Since the ResultDisplay remains scrolled all the way up when we display text that is longer than the size of the box, showing the history from most recent to the earliest does make sense, as we would expect the user to want to see what he has typed most recently, and he can scroll down if he wants to see what he has typed earlier. At least this is how it works for Google Chrome History as well.

"I guess we are making an assumption that user will want to see what he has typed most recently, just like how Google Chrome History works." This can be considered additional information to include in commit message. I think it's helpful for me to understand the reason of this change. :)

@Zhiyuan-Amos need you to resolve the merge conflict.

v4
@Zhiyuan-Amos submitted v4 for review.

[v4 1/1] HistoryCommand: Returns previous commands in reverse chronological order

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v3 and v4)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/537/4/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.


Fix secp256k1 derivation path

Currently, it does not increment the key sequence if it's not a valid private key:
https://xrpl.org/cryptographic-keys.html

Closing - forgot that findSecretKey implements the key sequence incrementing recursively.


RichTextLable: alignment and indentation breaks table

Godot version: 3.2.2
OS/device including version: Linux
Issue description:  Adding both alignment and indentation into a cell breaks the table layout and push a cell into the next row. It does not happen with only one of them and works as it supposed. You can see in the below image, In the first cell, I have added both indentation and right alignment. It went into the next row. Swapping cell positions or changing alignment also does not solve the problem.

Steps to reproduce:

Download and run rich_text_label_issue.zip.

It can be reproduced with this bbcode (cell 2 is moved to the next line):
[table=2]
[cell]cell 1[/cell]
[cell][center][indent]cell 2[/indent][/center][/cell]
[/table]

While this one looks as expected:
[table=2]
[cell]cell 1[/cell]
[cell][indent]cell 2[/indent][/cell]
[/table]


Do show TargetSourcesBuilder diagnostics for read-only dependencies

It doesn't make sense to show diagnostics which aren't actionable by the user, such as unhandled files in remote dependencies.
We should probably do a more broad filtering of unactionable diagnostics, but this is a start.

There are a couple of things that TargetSourcesBuilder errors for, which probably need to still be shown even if they aren't actionable. Maybe we should pass in an observability scope that does the filtering on a case by case basis?

This makes sense for now, I think.  Eventually we might want to still collect these but conditionally hide them in the output, so that they can be toggled on/off after the fact in an IDE for example.  But this makes sense for what we have now.


Error appear when import Main.Java in the net.floodlightcontroller.core ?

i have floodlight master branch iam trying to import the Main.Java  and theres error appear when i run the Main.Java

How i solve this error appear in the picture above?

@QingWang0909 ,brother can you help in my issue and thanks

Please refer to the thread here, it is the same problem:  https://groups.io/g/floodlight/topic/error_in_floodlight_import/30156714?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,30156714


ASP.NET Core Identity UI now uses "static web assets" feature

ASP.NET Core Identity UI now uses "static web assets" feature
In ASP.NET Core 3.0 we've moved Identity UI to use the new static web assets feature introduced in 3.0. As part of this move there are a few API breaking changes to note.
Bootstrap4 is the default UI framework for Identity UI. (Bootstrap 3 has reached end of life and you should consider migrating to a supported version).
Selecting the framework is done by using the IdentityUIFrameworkVersion property in your project file.
Version introduced
3.0
Old behavior
The default UI framework for Identity UI was Bootstrap 3.0. The UI framework could be configured using a parameter to the .AddIdentityUI() call in Startup.ConfigureServices.
New behavior
The default UI framework for Identity UI is now Bootstrap 4.0. The UI framework must be configured in your csproj file, instead of the .AddIdentityUI() call, by adding the following MSBuild property to your csproj file:
<IdentityUIFrameworkVersion>Bootstrap3</IdentityUIFrameworkVersion>

Reason for change
We updated the default UI framework to reflect a new version of Bootstrap. Because we use the new static web assets feature, the UI framework configuration moved to MSBuild since the decision on which framework to embed is a build-time decision not a run-time decision.
Recommended action
Review your site UI to ensure the new Bootstrap 4.0 components are compatible. If necessary, use the IdentityUIFrameworkVersion MSBuild property to revert to 3.0.
Category

ASP.NET Core

Affected APIs
IdentityBuilderUIExtensions.AddDefaultUI()

Issue metadata

Issue type: breaking-change

FYI, the explanation for this announcement discusses AddIdentityUI, but the affected API is AddDefaultUI.

@serpent5 Thank you for letting me know. Looking at this right now.


Revert "Filter out terminal and reverse predictions for RL/BL"

Reverts mbta/realtime_signs#611
In preparation for if we want to go back to showing Red and Blue line terminal predictions tomorrow morning.
Slack thread for context: https://mbta.slack.com/archives/C03K6NLKKD1/p1681224044867379

Reopening this PR as we plan to restore Blue Line terminal/reverse predictions soon


psm wrapper layer

Closing #13
uses #12 so targeting that branch for now

Should I still re-throw those errors in submitTx? I assume an error like these should cause the test to fail.


Questions about shot_num

I have three questions about the shot_num setting.
(1) In json_dataset.py，the parameter shot_num=10 (line 180+), and this means 10-shot setting?
(2)in loader.py, I found the using 2-way training strategy, we have 5 positive supports and 5 negative support, is this right?
(3) When testing, this code sets 10-shot evaluation setting but is not the same as 5-shot setting in the training stage.

Could you give me the specific code link for a better explanation?

code in lib/dataset/json_dataset.py and lib/roi_data/loader.py
I wanna to know how to change the setting to get 5 way 5 shot, 5way 10shot setting, etc.

Thank you for your help

Where the parameters that are used to get N way K shot settings and is the setting during train the same as testing? I am a little confused.


chore: restructure codebase

Please check the README.md from this PR for details.
Closes #2.

Hi, @ehmicky
This PR should address your concern in #2. I'd love to hear your thoughts.
Please check the README.md file for further details and use the CodeSandbox-CI package for testing :)

This looks good to me! Thanks a lot @Sec-ant!


Feature request: prevent sleep while music is playing through Spotify (or some other App)

Hi, first of all I'm not sure this is the right place to submit this. I use an M1 MBA with the lid closed while hooked up to an external display via Thunderbolt and with bluetooth keyboard and trackpad. I'm looking for a way to prevent the system from sleeping when music is being played on Spotify, or some other App. I suspect it could be possible to subscribe and listen for kMRMediaRemoteNowPlayingInfoDidChangeNotification notifications and use that as a trigger to toggle Amphetamine.

I have a similar issue.
I have the "Lock screen after x minutes of inactivity" setting turned on, and the "Use cursor movement to determine inactivity" setting turned off.
When I am on a Zoom call (which I would imagine counts as playing a video or similar) the screen locks.
This is not the case with macOS's native Screen Lock settings - it respects when a video is playing and doesn't lock.
I think Amphetamine should try and follow the system's behaviour when it comes to preventing sleep / auto lock.


Adds a package.json file

Hey! This is a really useful script, thanks for writing it. I was hoping to install it as a dependency through npm, this pull request just adds a package.json file to make that possible.
If you wanted to publish it to the npm registry, I think you should just need to run:
npm publish

…after merging the pull request. Then, anyone can install it using:
npm install smoothscroll

If you’d rather not do that, it will still be possible to install it via GitHub:
npm install alicelieutier/smoothScroll

I’d be happy to update the README depending on which one you’d prefer. Thanks!

Hey, this is a great idea!
I never published a package to npm, but I am happy to. I'll wait on you change in the README to merge, then.

There you go :)

Thanks !

Ok, just published it: https://www.npmjs.com/package/smoothscroll
Thanks :)


[usb] Fix lint errors and warnings, remove inline lint comments

This PR fixes lint errors and warnings.
Out-of-range endpoint indices are handled as follows (previously we had mutliple inline lint comments for these):

The code has been reworked slightly and commented to clarify that out-of-range indices are never used. Such tokens are simply not handled and dropped by the FSMs. The behavior is the same as before, but it was less clear from the code previously.
The actual index generation is reworked such that out-of-range indices are set back to 0.
SVAs have been inserted to warn about out-of-range endpoint indices.

This is related to lowRISC/OpenTitan#1093.

FYI @stefanlippuner

@msfschaffner could you please re-run lint and let me know if further changes are needed?

I can have a look at the functional changes at the end of the week.
The behaviour for unimplemented endpoints is also non-conformant. We would have to stall IN & OUT transfers and ignore SETUP transfers. But that does not seem too important to me, and we can address that later.

Thanks @eunchan , @msfschaffner and @stefanlippuner for your feedback. I implemented the requested changes.
Regarding the behavior in case of not implemented endpoints, we should definitely track this. I added it to the tracking issue.


Update Cilium install guide about EKS aws-node DaemonSet potential connectivity problem on uninstall

Recently we discovered that aws-node daemonset can cause connectivity issues due to flushing Linux routing tables
if Cilium is uninstalled via the cli and installed again. We have fixed it[1] for the EKS tests and now this PR updates the docs
to align helm installation with current practices (i.e. patch aws-node DaemonSet instead of delete) and also adds a note in
the getting started section when installing via cilium cli.
This is also related to re-enabling ci-eks ( #16938 )
For more information about the issue itself please see the commit descriptions in the PR below.
[1] https://github.com/cilium/cilium/pull/22590

Does this affect older versions (e.g., 1.12)? Should we backport these doc changes?

Good point! I've set the labels to backport everywhere. Thanks for bringing it up!


Fixes #3022

Pull Request
The issue or feature being addressed
Fixes #3022

Details on the issue fix or feature implementation
Fixes both issues described in the bug.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.60%. Comparing base (30fb944) to head (f700cb2).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3023      +/-   ##
==========================================
- Coverage   90.61%   90.60%   -0.01%
==========================================
  Files          74       74
  Lines        2962     2970       +8
  Branches      469      476       +7
==========================================
+ Hits         2684     2691       +7
- Misses        278      279       +1

Flag
Coverage Δ

Linux
90.60% <100.00%> (-0.01%)
:arrow_down:

Windows
?

macOS
90.60% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Hi @domaindrivendev and @martincostello, thank you for an excellent library. This is my first PR into Swashbuckle.AspNetCore, so please let me know if I'm missing anything!

Version 6.7.1 is now available from NuGet.org which resolves this issue.


Bot crash when trade offer sent

Hello, I'm want to use the SteamBot for my CSGO gamble site!
You can see the error here. It says something with Jordan Turley but I've already edited that, but it keeps saying that.
https://gyazo.com/d22c473aabc4af0ad5cf04c3c3cf150b

This is not a SteamBot issue.
cc @BlueRaja

@scholtzm, what can it be then? :)

well in the handler there are lines starting with : string pass =, find these and hardcode your password.

@TheAnthonyNL , thank you for your response :+1: Im not a good coder, so can you maybe help me? :)

#427 #527


feat: add graph-based dependency validation

Closes #363
📑 Description
Changes the Dependency manager to use a dependency graph for validation.
✅ Checks

[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required

ℹ Additional Information
Should help with #344, #398, #399

As shortly discussed, once I had at least 4 packages installed, the package overview page becomes quite slow. This is because package infos are requested quite often from the API server, and the client throttles the requests in that case. As a follow-up I created #444 to cache the package infos.

That's a great catch and I can see that you already started working on this :wink:

So implementing the cache is definitely a good first step, but it's such a "hardware" type of solution. I am not sure if it would also make sense to reuse the dependency graph and deep copy it for every Validate call (downside: more caching to take care of)? Sounds a bit like premature optimization though. But I think its worth keeping in mind for the future, that update checking is a quite complex operation, especially with a rising number of installed packages.

Yeah I agree. For this PR, I wanted to change the API of the DependencyManager as little as possible, but it could be a lot more efficient if the graph could be reused. This will probably be necessary anyways in the future when we need to perform additional pruning for the UI and CLI (#399) or find the max possible update version (#412).


The spell Boneshaker invalid cast time

Cast time shows as just "or" when Nethys shows it should be "2 or 3"

This has now been fixed.


Consider changing the password rotation requirement

The ncsc website is down so I cannot link to the guideance 🙁 , but from their twitter https://twitter.com/ncsc/status/808258353554132992
https://www.ncsc.gov.uk/articles/problems-forcing-regular-password-expiry (for when the website is back live).

A good quote from the article:

It’s one of those counter-intuitive security scenarios; the more often users are forced to change passwords, the greater the overall vulnerability to attack. What appeared to be a perfectly sensible, long-established piece of advice doesn’t, it turns out, stand up to a rigorous, whole-system analysis.

We also don't do the following very well, meaning regular password resets are more burdensome:

Allow users to reset password easily, quickly and cheaply.

We uncovered these problems during 2-step verification research but didn't fix them.

Having reset my passphrase again - I'm reminded of this old issue, please consider it.

This is on our backlog of work for Signon, but we don't currently have any work on it planned in our Roadmap

Hey @boffbowsh, need any help with this one?
I could see if we can carve out some time from Tariff as we use our own signon instance on dev.

Pull Requests are very welcome :)


Rename ADO displayNames for loadtesting

This PR renames some of the displayNames used for the embedded and standalone loadtest.

Running e2e now and will paste some screenshots here as soon as it's done. Will use the same displayNames in the other LT implementation as well to reduce the need to update screenshots later. @hjscherer FYI

@hjscherer renamed:


failed creating poet client harness: error during killing process: exit status 123 | kill: you need to specify whom to kill

Alpine Linux (which we use to run our tests in docker) has a funny version of lsof installed that doesn't tell the truth:
/go/src/github.com/spacemeshos/go-spacemesh # lsof -i tcp:18550 | grep LISTEN | awk '{print $2}' | xargs kill -9
kill: you need to specify whom to kill
/go/src/github.com/spacemeshos/go-spacemesh # apk add busybox-extras
(1/1) Installing busybox-extras (1.31.1-r19)
Executing busybox-extras-1.31.1-r19.post-install
Executing busybox-1.31.1-r16.trigger
OK: 160 MiB in 44 packages
/go/src/github.com/spacemeshos/go-spacemesh # busybox-extras telnet localhost 18550
Connected to localhost
@hello
/go/src/github.com/spacemeshos/go-spacemesh # lsof -i tcp:18550
1       /bin/busybox    /dev/pts/0
1       /bin/busybox    /dev/pts/0
1       /bin/busybox    /dev/pts/0
1       /bin/busybox    /dev/tty
2941    /tmp/poet/poet  /dev/null
2941    /tmp/poet/poet  /dev/null
2941    /tmp/poet/poet  pipe:[865420]
2941    /tmp/poet/poet  /root/.poet/logs/poet.log
2941    /tmp/poet/poet  anon_inode:[eventpoll]
2941    /tmp/poet/poet  pipe:[862641]
2941    /tmp/poet/poet  pipe:[862641]
2941    /tmp/poet/poet  socket:[862642]
2941    /tmp/poet/poet  socket:[862646]
2941    /tmp/poet/poet  socket:[864392]
2941    /tmp/poet/poet  socket:[863516]
2941    /tmp/poet/poet  /tmp/poet/data/1680/challengesDb/LOCK
2941    /tmp/poet/poet  /tmp/poet/data/1680/challengesDb/LOG
2941    /tmp/poet/poet  /tmp/poet/data/1680/challengesDb/MANIFEST-000000
2941    /tmp/poet/poet  /tmp/poet/data/1680/challengesDb/000001.log
2941    /tmp/poet/poet  /tmp/poet/data/1679/layercache_0.bin (deleted)
/go/src/github.com/spacemeshos/go-spacemesh # apk add lsof
(1/1) Installing lsof (4.93.2-r0)
Executing busybox-1.31.1-r16.trigger
OK: 160 MiB in 45 packages
/go/src/github.com/spacemeshos/go-spacemesh # lsof -i tcp:18550
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
poet    2941 root   11u  IPv4 862642      0t0  TCP localhost:18550 (LISTEN)
poet    2941 root   13u  IPv4 864392      0t0  TCP localhost:50380->localhost:18550 (ESTABLISHED)
poet    2941 root   14u  IPv4 863516      0t0  TCP localhost:18550->localhost:50380 (ESTABLISHED)
/go/src/github.com/spacemeshos/go-spacemesh # lsof -i tcp:18550 | grep LISTEN | awk '{print $2}'
2941
/go/src/github.com/spacemeshos/go-spacemesh # lsof -i tcp:18550 | grep LISTEN | awk '{print $2}' | xargs kill -9
/go/src/github.com/spacemeshos/go-spacemesh # lsof -i tcp:18550
/go/src/github.com/spacemeshos/go-spacemesh #

This causes problems inside the harness:
https://github.com/spacemeshos/poet/blob/79d0b528f546590e05857fdb692943d694c657e8/integration/harness.go#L132
I see this error from several of the go-spacemesh tests in github.com/spacemeshos/go-spacemesh/cmd/node including this one:
/go/src/github.com/spacemeshos/go-spacemesh # go test -timeout 0 -p 1 -count 1 -v github.com/spacemeshos/go-spacemesh/
cmd/node -run Test_PoETHarnessSanity
=== RUN   Test_PoETHarnessSanity
    Test_PoETHarnessSanity: app_test.go:72:
                Error Trace:    app_test.go:72
                Error:          Received unexpected error:
                                error during killing process: exit status 123 | kill: you need to specify whom to kill
                Test:           Test_PoETHarnessSanity
--- FAIL: Test_PoETHarnessSanity (1.16s)
FAIL
FAIL    github.com/spacemeshos/go-spacemesh/cmd/node    1.184s
FAIL

This code should make sure the output of the shell command here is not null before passing it to kill.

Closing as the integration harness was removed.


Unhandled exception on Mopidy startup

OS: Debian Wheezy
Version: Mopidy-Notifier  0.3.2
Mopidy 1.0.0
Mopidy pukes this up on startup:
ERROR    Unhandled exception in NotifierFrontend (urn:uuid:e76e0501-3a8d-4b4a-959b-5bc5e887c1c8):
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pykka/actor.py", line 191, in _actor_loop
self.on_start()
File "/usr/local/lib/python2.7/dist-packages/mopidy_notifier/frontend.py", line 27, in on_start
self.notify('Starting...')
TypeError: notify() takes exactly 3 arguments (2 given)
Seems that its related to the use of the "subtitle" variable with notify-send. For startup and shutdown, the variable never gets passed to notify, and on playback started, its called for passing to notify, but never populated.
I was able to fix this by changing the following in frontend.py:
ln 26:
def on_start(self):
    self.notify('Starting...', '')

def on_stop(self):
    self.notify('Shutting down...','')

ln 40:
    elif sys.platform.startswith('linux'):
        message = song + '\\n' + artists + ' - ' + album
        subtitle = ''

Don't know if its correct, or even a good idea, but notifications are working on my system now :)

Thanks for the report! I fixed it in version 0.3.3!


[AutoPR operationalinsights/resource-manager] Add operationalinsights/resource-manager/readme.typescript.md

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4207

(message created by the CI based on PR content)


The border color of h1 (#) is not reflected when specifying a Markdown style sheet

Type: Bug
When I specify my own CSS file and preview Markdown, the border color of h1 is not reflected.
This problem can be reproduced by following the procedure below.

add the following CSS file to Markdown: Stylesh1 {
    border: 10px solid red;
}

preview the following Markdown fileHeadline_1
==

VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:35:13.448Z)
OS version: Windows_NT x64 10.0.19043
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 x 3392)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.95GB (16.68GB free)

Process Argv
--crash-reporter-id 6ca6ac69-34a6-4a09-99ab-394cdacb706f

Screen Reader
no

VM
57%

Extensions (1)

Extension
Author (truncated)
Version

vscode-language-pack-ja
MS-
1.70.8170911

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
pylanb8912:30545647
vsclangdf:30486550
c4g48928:30535728
hb751961:30553087
dsvsc012:30540252
azure-dev_surveyone:30548225
i497e931:30553904

After checking the generated HTML in preview, the following CSS may have been loaded.
The following CSS is loaded even when the Markdown file is converted based on the CSS specified in Markdown: Styles, so it is assumed that the styles are overridden.
<link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/Microsoft/vscode/extensions/markdown-language-features/media/markdown.css">

Is it possible to set the above CSS file not to be loaded?

That file provides a baseline stying that your stylesheets can then augment
In your example, you can just add a more specific css rule for light/dark:
.vscode-dark h1 {
    border: 10px solid pink;
}

or if you want this to apply to all color themes:
.markdown-body h1 {
    border: 10px solid pink;
}

I understand how to write CSS for preview, thank you.


Add homebrew to install

Having option to install via homebrew could be a very good idea.

Hi, I added homebrew support in inamiy/homebrew-formulae with following installation command:
$ brew install inamiy/formulae/swift-rewriter

But currently (as of 0.1.0), there is no configuration file support yet, so that will be my next TODO.
For now, I will keep this issue opened without adding documentation in README, until configuration file support is ready.

Personally, I don't see a YAML/JSON configuration file as a required feature. I think rewriter.swift is actually a very swifty way to do it, considering the precedent of SwiftPM's Package.swift. It also seems like it could be much more flexible and powerful in the future, and the overloaded operators make it nearly as easy, if not easier, to write than JSON or YAML.


add commands to collect server metrics from BSD systems

add commands to collect server metrics from BSD systems

We are exploring just allowing a custom callback for this for full customization.

I see. Then, I'll wait. Thanks.