Fix wifi_signal_db percent for HA & athom-smart-plug-v2.yaml

Official doc here: https://esphome.io/components/sensor/wifi_signal.html
The real fix is the device_class: "" for the WiFi Signal Percent.
Fix #47

@jlsalvador this is a good find and that ESPHome has been updated to cater for this since it was originally added here.
Suggest looking at using just "%" (not "Signal %") as the unit of measurement, as '100 Signal %' is at worst a grammatical error, as '100%' makes sense even '100% Signal' makes sense, but '100 Signal %' doesn't.... maybe a typo in documentation has it reversed?
I would suggest however that you update the v1 plug (or ALL the other Athom devices, as they appear to include this sensor) to include this update:
https://github.com/athom-tech/athom-configs/blob/main/athom-smart-plug.yaml
You also need to update the projection_version number to reflect this change to the template/config.

@jlsalvador this is a good find and that ESPHome has been updated to cater for this since it was originally added here. Suggest looking at using just "%" (not "Signal %") as the unit of measurement, as '100 Signal %' is at worst a grammatical error, as '100%' makes sense even '100% Signal' makes sense, but '100 Signal %' doesn't.... maybe a typo in documentation has it reversed?
I would suggest however that you update the v1 plug (or ALL the other Athom devices, as they appear to include this sensor) to include this update: https://github.com/athom-tech/athom-configs/blob/main/athom-smart-plug.yaml
You also need to update the projection_version number to reflect this change to the template/config.

Done. Thank you.

Hello,
Is there anything I can do to help you accept or review this PR?
Greetings.


Simplify defining span annotations categories

Current state
For LLM evaluation user specifies LLMMetric config in the yaml config and possibly implements/extends existing LLM metric and changes the LLMMetric factory in factgenie/evaluate.py. Note all the metrics according to llm-eval/*yaml configs are loaded and offered.
So most of the LLM annotation campaign is defined in code.
With the single exception of the error_categories which one must insert via web browser dialog and they must match the categories specified in the yaml config for the LLM prompt.
Proposal

[ ] Rename error_categories to annotation_span_categories
[ ] Allow specifying the annotation_span_categories in the yaml metric configs in llm-eval/your_metric.yaml
[ ] Allow loading creating a human evaluation based on existing llm-eval campaign. Load the same annotation types from there.

WIP in https://github.com/kasnerz/factgenie/tree/campaign-management, will merge soon

Solved in #44


NtQueryInformationFile: HTML is mangled

The HTML is mangled in the middle of this page.

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

ID: 65a6b1c6-aeaf-e922-b8ea-47d7469e96a4
Version Independent ID: 0cbfe627-8995-97eb-185c-06e3fa202bbe
Content: NtQueryInformationFile function (ntifs.h) - Windows drivers
Content Source: wdk-ddi-src/content/ntifs/nf-ntifs-ntqueryinformationfile.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @lorihollasch
Microsoft Alias: loriwhip

Thanks! Looking into this.

Fixed in the source. Should go live later today.
Thanks for the heads up, @maharmstone

That's much better! The description of FileAttributeTagInformation is still in the wrong column, though.

D'OH!
Thanks for reviewing, @KalleOlaviNiemitalo. I'm embarrassed that I didn't proofread after the changes. I fixed the extra pipe symbol--and verified the fix in preview. Checked into the main branch. Will be live shortly.
Cheers,
Eliot


How to disable entirely without affecting other TS checking in VS Code

I frequently run into ts-styled-plugin(9999) errors in VS Code that are entirely false negatives and show up all over the place for our devs.
I have no idea why these errors show up. I do not have ESLint, TSLint, typescript-styled-plugin, or their respective VS Code extensions installed anywhere on my computer. It's not a part of my actual CLI TS compilation. It just shows up in VS Code.
I do not want this package to run at all, I want to entirely turn it off. The only way I've figured out how to do that so far is by entirely disabling typescript checking in VS Code with "typescript.validate.enable": false but that is not an acceptable solution as that disables all typescript checking in VS Code.
How do I block all ts-styled-plugin(9999) errors in VS Code without entirely disabling TS checking?

Seriously: a validator that gives a million false validation methods isn't a helpful tool, it's a drain on your mental resources.  As much as I'd love true styled-component CSS validation, I'll take nothing over a ton of false positives.

According to the documentation, modifying jsconfig.json should have the desired effect:
{
  "compilerOptions": {
    "plugins": [
      {
        "name": "typescript-styled-plugin",
        "validate": false
      }
    ]
  }
}

... but it doesn't work.  I added that to mine, restarted VS Code, and still saw bogus "errors" :(

This plugin is LAZYYYYY
how do you not support SVG attributes out of the box?
go home

Closing as this package has been deprecated in favor of the official styled-components/typescript-styled-plugin fork


fix: returned package contents was always empty

The contentsRules would always return true, no matter what rules you applied. I dug into the code and found that an empty struct was returned instead of the proper populated object. This PR addresses this issue.

New version available: https://pkg.go.dev/github.com/fdaines/arch-go (v1.4.2)


Add chart CR support to collector

Towards https://github.com/giantswarm/giantswarm/issues/5561
This is prep for adding an alert for incorrect tiller config. Currently the collector only supports chartconfig CRs this extends it to also consider chart CRs.

Tested on ginger.


CMake and VS Developer CMD problems

Make a Visual Studio project using VS Developer CMD using CMake.
Command:
cmake -G "Visual Studio 12" ..

remaking this project in osx/xcode


Avoid Domain if not needed

My first batch of changes, I have a few more locally, but since there were a lot of changes in this area the last days, I wanted to open up smaller PRs to get the ball rolling and not constantly having to incorporate changes from master :)
This PR contains 3 changes:

Updates C# project to 9.0 (needed for next point)
Change null / not null checks to is null/is not null (Justification see here: TLDR: is null avoid the == or != operator override)
Adding more shortcuts that avoid the Domain object

Effect of these changes:

Method
Mean
Error
StdDev
Gen 0
Gen 1
Allocated

NursesSat_WithOutputToNull_pr
1.097 ms
0.0100 ms
0.0088 ms
29.2969
13.6719
140 KB

NursesSat_WithOutputToNull_master
1.143 ms
0.0172 ms
0.0160 ms
29.2969
13.6719
141 KB

So around a 4% overall improvement and some small managed allocation gains.

In progress. Please update from master and resolve conflicts

Rebased and I additionally replaced the ref in FillLinearConstraint with an out. (ref is not needed for reference types, only if you want to overwrite the reference itself, but the simpler choice is out and initialize it inside.)

Merged. Thanks
Le mer. 12 janv. 2022, 22:00, Sandro Bollhalder @.***>
a écrit :

Rebased and I additionally replaced the ref in FillLinearConstraint with
an out. (ref is not needed for reference types, only if you want to
overwrite the reference itself, but the simpler choice is out and
initialize it inside.)
—
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/pull/3069#issuecomment-1011446716,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3PZP6IP7P6CHSMFTT3UVXTU7ANCNFSM5LXTEF2A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID:
@.***>


[fix] Correct typo from 'access' to 'assess' in interview description (#663)

Description:
This PR fixes a typo in the coding interview description, where "access" was mistakenly used instead of "assess."
The correction improves clarity in the sentence about assessing competencies during interviews.
Closes:
Closes #663.

Absolutely great work on the website by the way!


Quiz exercises: Revert broken drag and drop file upload changes

PR #6456 unfortunately includes many different bugs, in particular #6825, but also missing preview functionality and issues when editing the newly created quiz with drag and drop questions.
It is not possible to fix all issues on short notice, the whole file upload handing code needs to be refactored, because files are created and/or replaced multiple times, which is simply not necessary.
Therefore, we revert PR #6456 and the related PR #6718. Due to overlapping changes, we also have to revert PR #6445, otherwise there would be too many merge conflicts.

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Testing in courses
Thoroughly test all imaginable uses of drag and drop questions in course quizzes, in particular creating multiple ones, editing them directly after creation or when navigating into them again afterwards. Previewing the whole quiz, participating in the quiz, showing its solution, and re-evaluating drag and drop questions. Please be creative!

[ ] Testing 1
[ ] Testing 2
[ ] Testing 3
[ ] Testing 4

Testing in exams
Test the same as above for exam quizzes. Please be creative!

[ ] Testing 1
[ ] Testing 2
[ ] Testing 3
[ ] Testing 4

Note, if you find some edge case issues, or usability issues, please report them here. This PR is a hotfix for an urgent issue on production systems and should be deployed as quickly as possible. We want to make sure the general functionality is working again.

The editing and deletion of drag and drop quiz questions might lead to issues. We are unsure if this worked 100% properly before. If anyone can help us investigating those issues, this would be awesome.

The buttons are not perceptive and there is an "alt"

I mapped 3 options out of 4 and when I saved the image was compressed? If you see the size of the slots says 44x23 but they are compressed.

https://github.com/ls1intum/Artemis/assets/9006596/72148c1c-dda2-44d3-8bb8-96e71ab358e7
SVG images are supported by the file upload input field, but not by the editor (was probably broken before already)

https://github.com/ls1intum/Artemis/assets/9006596/708dd423-649a-4552-ade6-48aa0b71a12c
When you do a kind of weird replacement and insert the same file twice as Picture Drag Item, one of them is broken after saving (probably broken before).

Probably an issue that existed previously:
When there are 2 identical text-draggables, there is only one correct order to solve the question.

The "Durchsuchen" or however choose file equivalent button does not adapt to Dark Mode. I'm not sure if this is a new issue or if it got introduced with the last changes.

The "Durchsuchen" or however choose file equivalent button does not adapt to Dark Mode. I'm not sure if this is a new issue or if it got introduced with the last changes.

Probably also an existing one as we did not change anything here

Everything worked fine for me so far during testing with a non-exam exercise but I'm getting the following error when finishing a drag:
Saving answers failed: The quiz is not active

I could not see anything in the console but submit still worked fine.
Another issue was when I refreshed after submitting I was presented with an empty quiz, but when navigating back and pressing view submissions it looked fine.

@krusche requested that I add a small bugfix here, which enables the save button when the background image changes.
After changing the background image, you had to trigger some other change so that the save button would be enabled and you could save. Now this is fixed.
Testing steps:

Create a drag and drop quiz ("Create Quiz" -> Enter title -> "Add Drag-And-Drop Question" -> Add Short Question Title -> Upload a background -> Add a Drop Area, Add a Text Drag Item, connect them -> Save)
Upload another background
Now the Save button is enabled, without you having to change something else

https://github.com/ls1intum/Artemis/assets/9006596/38d2ce1d-2965-4979-9648-52ba0c119d0e

I could not reproduce the issue I had with the Saving answers failed: The quiz is not active error.
Is there a limit how big the file is allowed to be? I had for example some problems with my 2-4MB files. Also with smaller pictures I had sometimes the the alt text displayed and a message that it could not load the images. But it worked again after testing it a third and forth time. Are image cached when I upload the same image again? Do I have to try others? I think there are still some occasional issues when creating the exercise but when it displays correctly in the exercise editor it also works fine during participation.


Codes for spatial transcriptomics

Hello, thank you for sharing your code, which has been very helpful to me. I'm pretty new to spatial transcriptomics analysis, and I noticed that the "Spatial_analysis" folder doesn't seem to include the "brain_mets_analyze_puck.R" and "brain_mets_spatial_analysis.R" scripts. Would it be possible for you to share those with me?
Can I analyze the Slide-seq v2 data by following the Seurat v5 tutorial?
thanks a lot!

Hello, thank you for your interest in our code. I am sorry that we forgot to upload the two scripts you mentioned, but they are now available in the Spatial_analysis folder.
The brain_mets_analyze_puck.R script is based on the Seurat v5 tutorial, but we added some analyses that are not in the tutorial, so we recommend you use our script instead.


Dynamic highlight groups

I am interested in contributing a feature that lets IB determine the highlight group dynamically based on information from the rainbow delimiters plugin.
Related discussion: https://gitlab.com/HiPhish/rainbow-delimiters.nvim/-/issues/6
In short, I'd like to obtain the highlight group based on the parentheses/braces nesting level instead of the indentation level.
I was trying to find a place in code where we could optionally plug a call to rainbow-delimiters, but I'm not sure.
I'll apreciate any pointers or comments!

I am working on a new version for indent-blankline that will let other plugins hook into the generation of indentation guides.
But that being said, integrating rainbow-delimiters will be very difficult. The 2 plugins fundamentally work totally different.

Can you shortly describe where that fundamental difference lies? Is it the indentation level vs delimiter nesting level?

Both indent-blankline and rainbow-delimiters use treesitter. But the nodes are not the same. You would need some kind of logic that can map between the two. Writing this logic would be very difficult, and probably unique for each language, because each language has a different treesitter grammar.
Take a look at what rainbow-delimiters is doing now, https://gitlab.com/HiPhish/rainbow-delimiters.nvim/-/tree/master/queries it has queries for each possible bracket, for each language. You would then need to write logic to map each of those, to anything an indent-blankline scope could be, which is a lot.
And you can't just compare the start and end, because treesitter nodes usually contain the whole statement. For example, in this go code, rainbow-delimiters would have a node for { and one for }, but indent-blanklines scope is the whole thing, including the if err...
if err != nil {
	// some code
}

Thank you for taking the time to write this!
Indeed, this looks more complicated when comparing what parts of the treesitter structure these plugins operate on.
I don't want to immediately give up on the idea, especially since both IB and RD don't really seem to work for competing use-cases, but I'd probably need to study treesitter a bit more before I can put together some proposal.

To add to the discussion, the node that contains the delimiters is captured as @container. In the above Go code that node would be the block node of this tree:
if_statement [0, 0] - [2, 1]
  "if" [0, 0] - [0, 2]
  condition: binary_expression [0, 3] - [0, 13]
    left: identifier [0, 3] - [0, 6]
    operator: "!=" [0, 7] - [0, 9]
    right: nil [0, 10] - [0, 13]
  consequence: block [0, 14] - [2, 1]
    "{" [0, 14] - [0, 15]
    comment [1, 1] - [1, 13]
      "text" [1, 1] - [1, 2]
        "/" [1, 1] - [1, 2]
      "text" [1, 2] - [1, 3]
        "/" [1, 2] - [1, 3]
      "text" [1, 4] - [1, 8]
      "text" [1, 9] - [1, 13]
    "}" [2, 0] - [2, 1]
"\n" [2, 1] - [3, 0]

So it is possible to get the containers, but I don't know how you would map them to "indentation". But assuming we could do something with the container nodes, how would we get to them in the first place? For this I would use a custom strategy and builds a tree of container nodes and stores it somewhere, for example in a b: variable. Or it could feed the values directly to indent blankline. This strategy could be a wrapper that can wrap around another strategy so we don't have to re-invent highlighting all over again. I don't have such a strategy, but it should not be hard to write one. Open an issue in my repo if it would be useful.

This is now supported, see :help hooks.builtin.scope_highlight_from_extmark

Thank you for working on this!


Search filters & update post

Search optimization with filters and update post feature

Rejecting the PR because you pushed node_modules  folder. Too many files changed.


Staker Rewards Script: Frauds Detection

We want to check if an operator committed a fraud. To find that we look for TokensSlahed events emitted by TokenStaking contract.
Currently slash function from TokenStaking contract is used only by ECDSA Keeps. Random Beacon does not use slash, it uses seize. We assume that any slashing event is caused by fraud detected for ECDSA Keep supporting tBTC application.
Events filtering rules have to be revisited if we implement more usage for slash function.
Depends on: https://github.com/keep-network/keep-ecdsa/pull/625

@nkuba Do you mind updating PR description before I hit the merge button? What's in the PR description no longer reflect the implementation.

@pdyraga it's ready.


Does Ionide work with .NET Core? (Mac OS X)

Hi,
I'm following this tutorial Getting Started with F# on .NET Core, and when I launched Visual Studio Code + Ionide extension installed, I couldn't get F# REPL to run properly.
I don't have Mono installed as I want to stick with .NET Core.
Is my question too early? Eg. .NET Core is not supported yet by Ionide / Visual Studio Code.
Thanks!

As far as I know, F# on .NET Core is still under development and it's not supported by Ionide, so you need to use Mono. VS Code itself supports .NET Core but only for C#

Ionide understands .Net Core projects (both project.json and fsprojs targeting .Net Core). But you still need to have mono to run language services.

Just to help others that might stumble upon this issue while Googling.
So I just installed brew install mono and now F# REPL works in Visual Studio Code.


solved issue #657

Can one of the admins verify this patch?

@sdellang Thanks for the contribution.
I rebased your changes onto bb28d2b6cde6ffe58398cbc025a328e21777196b together with some integration tests. Therefore, closing this PR.


TypeError: Cannot read property 'enablePersistence' of undefined

Code
import firestore from '@/firebase/firestore'
import { GeoFirestore } from 'geofirestore'

// Create a GeoFirestore reference
const geofirestore = new GeoFirestore(firestore)

// Create a GeoCollection reference
const geocollection = geofirestore.collection('public/approved/events')

// also tried here like that:
// const geocollection = geofirestore.collection('public').doc('approved').collection('events')

// Create a GeoQuery based on a location
const query = geocollection.near({ center: new firestore.GeoPoint(48.1077212, 11.6019103), radius: 50 })

// Get query (as Promise)
query.get().then((value) => {
  console.log(value.docs) // All docs returned by GeoQuery
})

Console error
Uncaught TypeError: Cannot read property 'enablePersistence' of undefined
    at new e (geofirestore.js?5cdc:1)

I'm assuming you're testing version 3 of the library. With that in mind I don't believe your import syntax for for firebase is correct. Also you need to instantiate a firestore object, which I don't see.
I see some similarities in what you have to the sample I have in the readme, please give it another look though https://github.com/geofirestore/geofirestore-js/blob/v3.0.0/README.md#documentation
And if you have any questions let me know. I'll keep the issue open till Sunday so you can let me know if that works.

I updated the code, basically I have the part of the code of initialising app and firestore in a separate file.

@razbakov what version are you using? (And would you possibly be cool with making sample of on something like https://codepen.io/ ??)

My versions are:
"firebase": "^5.6.0",
"geofirestore": "^2.2.3",

Here is example - https://codesandbox.io/s/y04wj6zpoj

Ok! This I can easily address. I think you may have been referencing the documentation for version 3 which is located on geofirestore.com, however you're using version 2.x.x
Check out the docs for version 2
And as an example on how to do what you wanted to do...
import * as firebase from 'firebase/app';
import 'firebase/firestore';
import { GeoFirestore } from 'geofirestore'

// Initialize the Firebase SDK
firebase.initializeApp({
  // ...
});

// Array to store events
let events = [];

// Create a Firestore collection reference
const collection = firebase.firestore().collection('events');

// Create a GeoFirestore reference
const geofirestore = new GeoFirestore(collection);

// Create a GeoQuery based on a location
const query = geofirestore.query({ center: new firebase.firestore.GeoPoint(48.1077212, 11.6019103), radius: 50 })

// Listener for docs as they come in
query.on('key_entered', ($key, result) => {
    result.$key = $key;
    events.push(result);
});

// Listener for docs as they exit
query.on('key_exited', ($key) => {
    events = events.filter((event) => event.$key !== $key));
});

IF however you want to use version 3.0.0 (as your current code shows), you can install it like this:
npm i geofirestore/geofirestore-js#v3.0.0

It's still in kind of a beta state, however it's almost good to go, and I feel comfortable saying you could/should try it. I'm just writing tests to validate it works, otherwise the development is pretty much done (unless a test tells me I screwed up)


Add a "policies" section to JSON job description?

Should we gather all policy related options into a single "policies" section in the json? E.g.:
"policies":{
  "numberOfRetries": 2,
  "preferences":{
    "regions":[
      "IRIS", "FedCloud"
    ]
  }
}

https://github.com/prominence-eosc/prominence/issues/91 would be included in the "policies" section of course.

Jobs can now contain blocks like the following:
"policies":{
  "placement":{
    "requirements":{
      "sites":[
      ],
      "regions":[
      ],
    },
    "preferences":{
      "sites":[
      ],
      "regions":[
      ],
    }
  }
}

i.e. the default requirements and preferences can be overridden. Any group restrictions are of course still taken into account, so user's can't try to use resources they're not allowed to use.

Closing, this has existed for quite a while now.


Show only different part instead of the whole thing

When diffing 2 big objects which have a small difference in the middle, it's very hard to know what exactly gone wrong. I have to either scroll the terminal, or to redirect cargo test to a file and then use less.
So it would be nice to only display the difference, like diff tool does.
If you don't want to have a breaking change, than you can add a dedicated macro assert_eq_diff to display only diff.

It already does that, but it has a pretty long context of 5. I lowered the context to 4 now which makes it kick in slightly earlier.


weblate: 5.7 -> 5.7.1

Description of changes
Changelog: https://github.com/WeblateOrg/weblate/releases/tag/weblate-5.7.1

Things done

Built on platform(s)

[X] x86_64-linux
[X] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This unambiguously distinguishes tags from branches.


move CMSSW base to 14_1_X

At the end of 14_0_X cycle the pixel tracking alpaka implementation was merged (in 14_0_0_pre3). Also, alpaka 1.1.0 was integrated.
A combination of these is a good motivation to update our reference from 13_3 to 14_1.
CMSSW_14_1_0_pre0 could be a good start, although if we get to it by next week, a pre1 may be available already.

@ariostas
are you available to have a look? (since you made the update the last time).

Yeah, I'll take a look


[cubestore] add Annotations and Environment Variables

Specify environment variables for either router or workers
Add annotations and types to router service

Hi @asproul thanks for your PR.
Can you elaborate more on you use case? Is there some environment variables that are missing in the chart?
You can take a look to the cube chart. There is extraEnvVars,  extraEnvVarsFromConfigMap  and extraEnvVarsFromSecret options.  Maybe we can keep the same terminology for consistency. What do you think?

Merged, thanks @asproul


[WFCORE-679] Be able to check at runtime whether resource transformation

should be discarded or rejected.
https://issues.jboss.org/browse/WFCORE-679

Linux Build 1775 is now running using a merge of e8ab2c305fbfb47bce95fc318e361781d068e432

Windows Build 1336 is now running using a merge of e8ab2c305fbfb47bce95fc318e361781d068e432

Core - Full Integration Build 928 is now running using a merge of e8ab2c305fbfb47bce95fc318e361781d068e432

Windows Build 1336 outcome was SUCCESS using a merge of e8ab2c305fbfb47bce95fc318e361781d068e432
Summary: Tests passed: 3102, ignored: 66 Build time: 0:20:30

Linux Build 1775 outcome was SUCCESS using a merge of e8ab2c305fbfb47bce95fc318e361781d068e432
Summary: Tests passed: 3102, ignored: 66 Build time: 0:22:36

Core - Full Integration Build 928 outcome was SUCCESS using a merge of e8ab2c305fbfb47bce95fc318e361781d068e432
Summary: Tests passed: 2868, ignored: 373 Build time: 0:48:37

My javadoc comment is a nit. Looks good.


Add a pass through --registry-config flag

Add a flag --registry-config that can be used as a pass through to the helm command.
#717
#301

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

Project coverage is 93.48%. Comparing base (d8c22f6) to head (eef7e5a).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #735      +/-   ##
==========================================
+ Coverage   93.45%   93.48%   +0.03%
==========================================
  Files          20       20
  Lines        2154     2165      +11
==========================================
+ Hits         2013     2024      +11
  Misses        141      141

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


Put some Enzyme stuff in utils

DI extensions

Create an utils.jl file in the Enzyme extension

Codecov Report
Attention: Patch coverage is 0% with 24 lines in your changes missing coverage. Please review.

Project coverage is 0.62%. Comparing base (1db0e89) to head (639ef62).

Files
Patch %
Lines

...ace/ext/DifferentiationInterfaceEnzymeExt/utils.jl
0.00%
24 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (1db0e89) and HEAD (639ef62). Click for more details.
HEAD has 47 uploads less than BASE

Flag
BASE (1db0e89)
HEAD (639ef62)

48
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #384       +/-   ##
==========================================
- Coverage   96.58%   0.62%   -95.97%
==========================================
  Files         100      66       -34
  Lines        4926    2580     -2346
==========================================
- Hits         4758      16     -4742
- Misses        168    2564     +2396

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


META - User experience research

Description
We have identified several gaps or needs to be addressed in conda-store workflows and, therefore, conda-store-ui. As such, we have identified the need to design and conduct UX studies to:

Identify critical user workflows, unaddressed needs and priorities: individual users, team collaboration, cross-organisational collaboration
Further improve role mappings, role-based access, and sharing workflows and mechanisms
Improve existing workflows based on the learnings
Define a CLI and local experience for individual users and teams

### Tasks
- [ ] https://github.com/conda-incubator/conda-store/issues/757
- [ ] Draft user stories corresponding to the personas
- [ ] Design the user studies
- [ ] Run user studies
- [ ] Synthesise results and plan improvements

@smeragoel currently working on paperwork for studies

I volunteer to test this!


browser.newContext: options.isMobile is not supported in Firefox

When I tried to run a test with mobile emulation, I see the error in the title.
ran test with npx folio
const assert = require('assert');
const { devices } = require('playwright');
const { folio } = require('@playwright/test');

const fixtures = folio.extend();

fixtures.contextOptions.override(async ({ contextOptions }, runTest) => {
  await runTest({
    ...contextOptions,
    ...devices['iPhone SE'],
  });
});

const { describe, it } = fixtures.build();

...

Separate, how could I tell it to run against e.g. an array of mobile devices as opposed to a single one?

Closing as part of the triage process since the new test-runner got released yesterday. Please create a new issue if its still reproducible.


[Adopters] Add OpenGov to the list of adopters

Current State of the Meshery.io site
OpenGov is a Meshery user, but not listed on the meshery.io site.
Desired State of the Meshery.io site
OpenGov should be listed in the USED BY section of the site.

Contributor Resources

See the Contributing to Meshery.io Website section of the readme.md.

// @sakomws

@chinmaym07 would you like to take this on?
// @Jashpatel1

Yes @leecalcote sir .I can do that. 👍🏻


Adding default apiserver ports

default http port is 8080,
Added configurable httpPort option in config

Can one of the admins verify this patch?

ok to test

I've added some changes in this PR -> https://github.com/abhi4578/iudx-aaa-server-1/pull/1
If possible, could we either:

Remove all references to port 8443 in the configs and the README and change everything to 8080. We can then add detail in the config that if a port change is desired, add the httpPort key to the config.
Make the default port 8443 itself, instead of 8080

The problem I see now is that the README will have to be worded as below (it's a little confusing to me):

The server will be running at 8443, as per the supplied config-dev/config-depl/config-test (httpPort). The default port is 8080 when no port is specified in the config.

If this us OK to you, or you can reword it better, then we can leave it as is.

I've added some changes in this PR -> https://github.com/abhi4578/iudx-aaa-server-1/pull/1
If possible, could we either:
* Remove all references to port 8443 in the configs and the README and change everything to 8080. We can then add detail in the config that if a port change is desired, add the `httpPort` key to the config.

This option sounds good. we can go ahead with this.. In all other apiservers we have the httpPort at 8080 and hence this pr was raised to make it uniform and also to make it configurable if desired.

I've added some changes in this PR -> abhi4578#1
If possible, could we either:
* Remove all references to port 8443 in the configs and the README and change everything to 8080. We can then add detail in the config that if a port change is desired, add the `httpPort` key to the config.

This option sounds good. we can go ahead with this.. In all other apiservers we have the default http server port at 8080 and hence this pr was raised to make it uniform and also to make it configurable if change is desired.
Thanks! @ThorodanBrom

OK if @mahimatics approves, I'll make the changes to the README and configs. I'll add the the httpPort key only in configs/config-example.json and refer to that in the README.

I've added some changes in this PR -> abhi4578#1
If possible, could we either:
* Remove all references to port 8443 in the configs and the README and change everything to 8080. We can then add detail in the config that if a port change is desired, add the `httpPort` key to the config.

This option sounds good. we can go ahead with this.. In all other apiservers we have the default http server port at 8080 and hence this pr was raised to make it uniform and also to make it configurable if change is desired.
Thanks! @ThorodanBrom

OK if @mahimatics approves, I'll make the changes to the README and configs. I'll add the the httpPort key only in configs/config-example.json and refer to that in the README.

Sounds good to me. You can add those commits to this PR. It'll be better to have the httpPort as a configurable value.

Made the changes here -> https://github.com/abhi4578/iudx-aaa-server-1/pull/1/commits/292847f1feac4f81da669b33c07a0885a78683db

Made the changes here -> abhi4578@292847f.
@abhi4578 you can decide whether the docker compose files need to have 8443.

Merged the changes from abhi4578@292847f. to this pR

Have removed port 8443 from compose files . But it has some implications :
two implications:

the integration test  postman env needs to be changed to 8080
at jenkins ci, for integration test to work
All other existing prs need to merge this PR . Let me know @ThorodanBrom  if thats okay.

chuck it :) . will keep 8443 only for integration tests and it should not affect other prs

Yeah, let us just add httpPort:8443 to the integration test config.

done. ready to be tested and be merged.

54da345 - this is not our integration test config, it's used in the unit tests. The integration test config is not currently part of the repo.

54da345 - this is not our integration test config, it's used in the unit tests. The integration test config is not currently part of the repo.

okay, its done at jenkins. will revert this commit.

54da345 - this is not our integration test config, it's used in the unit tests. The integration test config is not currently part of the repo.

okay, its done at jenkins. will revert this commit?
Yeah, I think it's best to revert it

54da345 - this is not our integration test config, it's used in the unit tests. The integration test config is not currently part of the repo.

okay, its done at jenkins. will revert this commit?

Yeah, I think it's best to revert it
cool. done. no problem.

retest this please


📖 subscribe examples

Codecov Report

Merging #427 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #427      +/-   ##
==========================================
+ Coverage    86.9%   86.99%   +0.08%
==========================================
  Files         221      221
  Lines        4636     4636
  Branches      691      674      -17
==========================================
+ Hits         4029     4033       +4
+ Misses        605      601       -4
  Partials        2        2

Impacted Files
Coverage Δ

src/legacy/connect/models/deviceEventAdapter.ts
76.92% <0%> (-23.08%)
:arrow_down:

src/common/privateFunctions.ts
81.08% <0%> (-5.41%)
:arrow_down:

...BulkCreate/deviceEnrollmentBulkCreateRepository.ts
95.65% <0%> (-4.35%)
:arrow_down:

src/common/pagination.ts
88.14% <0%> (+1.48%)
:arrow_up:

src/legacy/connect/connectApi.ts
77.94% <0%> (+2%)
:arrow_up:

Continue to review full report at Codecov.

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


chore: add support for Python 3.11

FYI @seth-meltano

Duplicate of https://github.com/MeltanoLabs/meltano-map-transform/pull/98 afaict

@menzenski this was addressed by #98


ConfigurationError: handler of a recordAction should return a RecordJSON object

I'm using Ubuntu 18.04 & MongoDB 4.2, when I try to delete a document the log will say:
ConfigurationError: handler of a recordAction should return a RecordJSON object
the document is deleted, but the web UI is not showing anything after clicking delete/remove. But when I use my code in Windows with the same MongoDB and Admin Bro version, it just work well
Admin Bro version:
"admin-bro": "^1.3.1",
"admin-bro-expressjs": "^0.2.0",
"admin-bro-mongoose": "^0.3.0",

update admin to the latest version and it will work


Add Service Worker Support

Hi!
Is your feature request related to a problem? Please describe.
We have a Chrome extension that sends events using your lib in the foreground (called content script) and in the background (a service worker). In the foreground, we can use your browser tracker without problems, but we can't use this in the service worker due to these issues:

Browser Tracker needs a window object to work, and service workers don't have it.
Browser Tracker uses XHR to send events, and service workers use fetch only.

We developed a workaround to send events in the background using the Core Tracker and a port of the Node Emitter, but using fetch instead of got.
Describe the solution you'd like
It would be nice if your library supported service workers.
Thank you for your time!

Any updates on this issue? We could use node-tracker for now just to make it works, but it doesn't send a lot of useful properties that JS tracker used to send.


including removed theme.css - fix for #237

Fix for #237
CSS removed in PR #216

Great work! I'm thinking about adding a small test for this. in existence. Seems silly but definitely something that we can add just to catch little things like this (on all the variations)

Great work! I'm thinking about adding a small test for this. in existence. Seems silly but definitely something that we can add just to catch little things like this (on all the variations)

Added #239


style(fee): Fix error handle unpack.

This change is

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (93c0eaa) 70.43% compared to head (b8a1eff) 70.43%.

Files
Patch %
Lines

...es/blockifier/src/transaction/transaction_utils.rs
0.00%
5 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##           main-v0.13.1    #1390   +/-   ##
=============================================
  Coverage         70.43%   70.43%
=============================================
  Files                59       59
  Lines              7713     7713
  Branches           7713     7713
=============================================
  Hits               5433     5433
  Misses             1853     1853
  Partials            427      427

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


Brainstorming

Description:
Brainstorming for potential ideas for the project1.
Acceptance Criteria:
Must follow what Riz shared with us, here: (https://ukvirtfept092-nfv3117.slack.com/archives/C05NKQ6AB7A/p1699987808497739)
QA (quality assurance) / Testing:
Team of CANS must all agree on the ideas we will come up.

All good


Add logType and references to FleetNotification

What type of PR is this?
feature
What this PR does / why we need it?
Adds logType and references to FleetNotification
Which Jira/Github issue(s) this PR fixes?
https://issues.redhat.com/browse/OSD-18446
Special notes for your reviewer:
Didn't catch this in the initial update.
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[ ] Ran make generate command locally to validate code changes
[ ] Included documentation changes with PR

Codecov Report

Merging #91 (7d7f2fb) into master (4ceb3be) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   66.69%   66.69%
=======================================
  Files          19       19
  Lines        1165     1165
=======================================
  Hits          777      777
  Misses        322      322
  Partials       66       66

Files Changed
Coverage Δ

api/v1alpha1/managedfleetnotification_types.go
33.33% <ø> (ø)

/lgtm


[FLINK-26234] Start minikube manually to replace external github actions

According to the apache requirement, external github actions are not allowed to used in the workflow. So we need to start minikube manually instead of relying on the existing actions.
See https://github.com/apache/flink-kubernetes-operator/actions/runs/1859307064.

cc @gyfora @tweise
Just like this PR, now we have the CI pre-checks for all the tests.


Trigger translations for autofill breakage reporting

Task/Issue URL: https://app.asana.com/0/0/1207887150800792/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4798  👈
develop

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

Join @CDRussell and the rest of your teammates on  Graphite


Oversized attributes

Describe the bug
I've just spotted warnings in my log that attributes are not being stored due to being oversized.
Reproduction steps
I don't have a way to force this to reproduce, but it is repeating in my logs
Expected behaviour
n/a
Tariff Code
E-1R-FLUX-EXPORT-23-02-14-H
Integration Version
8.2.0
Home Assistant Version
2023.8.1
Fresh Install?
Not specified
Home Assistant Logs
Log Details (WARNING)
Logger: homeassistant.components.recorder.db_schema
Source: components/recorder/db_schema.py:584
Integration: Recorder ([documentation](https://www.home-assistant.io/integrations/recorder), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+recorder%22))
First occurred: 11:03:14 AM (8 occurrences)
Last logged: 11:03:16 AM

State attributes for sensor.octopus_energy_electricity_xxxxx_current_rate exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
State attributes for sensor.octopus_energy_electricity_xxxxx_export_current_rate exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
State attributes for sensor.octopus_energy_gas_xxxxx_current_rate exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored

Thanks for reporting. This is a duplicate of https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues/357, so closing.


Thank you for the theme !

Hello,
thanks for the clean and simple theme papaya !

I had a question but found it was zola related not the theme, and I found the answer).
Have a nice day.


cmd/eg: support ... package expansion

$ eg -w -t t.go cmd/...
cannot find package "cmd/..." in any of:

It'd be nice if eg supported ... the way that the go tool does.
I'm happy to do the legwork if desired.

I think we should extract cmd/go/pkg.go into a x/tools/go/build package and
vendor it into cmd/go/internal. Similarly for the vcs package.

Alternatively, we could expose an appropriate API in the main repo. This seems like the sort of thing that would be appropriate to expose in go/build.
(We could possibly also create a go/vcs package, but it's less clear to me that that is a good idea. Want to file a separate issue about go/vcs?)

By vcs package, I mean https://godoc.org/golang.org/x/tools/go/vcs.
cmd/go should vendor it and use it instead of maintain a copy in vcs.go.
Whether to add new API to go/build depends on how confident we are.
That's why I suggest adding API to x/tools/go/build first and see what
the community responds. We can always migrate it to go/build if we're
certain they are the correct design.


Bolt upgrade malforms package.json when dependency declared multiple times in package.json

Title
Description

Version
0.19.3

Type
Issue

node
8.4.0

When a package is declared in multiple different dependency types in a workspace's package.json, e.g. dependencies and devDependencies, bolt upgrade will add a new entry to package.json with the dependency entry names concatenated:
E.g.
"dependencies,devDependencies": {
  "bunyan": "^1.8.12"
}

I'm happy to take a look and create a PR for this.

Hmmm.. that definitely should be fixed, but possibly wasn't in until 0.20? Could you try upgrading?

Upgraded to 0.20.6 and it's fixed, cheers @lukebatchelor.

I know we didn't want a changelog till 1.0.0 but I might add a quick manual one if I get time later. Useful for this situation


[hi] Localization of the contents

some content on this page is not localized in hindi language !
### Tasks
- [ ] https://kubernetes.io/hi/docs/home/

/hi

/lang/hi

/language hi

/triage duplicate
This is a duplicate of issue https://github.com/kubernetes/website/issues/29353

@sftim Shouldn't we close this issue?


Make Use of Composition

We need to improve the way our components work. and the best way is to externalize the concerns instead of doing everything ourselves.
The Problems:

Imperative methods (we can't fix focus)
Pure rendering
ref
Style memoization
Getting theme from context or the default theme

The blessed solutions :angel: :angel:

[x] 1. Warpgate! I'm working on this one. A component that can warp imperative method calls down the tree. After giving it a lot of thought, I have finally found the solution and I'm working on it.
[x] 2. Recompose has already solved this
[x] 3. Also Recompose, see here :laughing:
[x] 4. I already solved it with react-memo, see the demo #3248
[x] 5. @newoga Took care of this a long time ago in a galaxy far away :smile:

The Chain:
We have those, good how do we line them up?

The dreaded ping :laughing: @newoga @oliviertassinari @mbrookes

@alitaheri The order of HOC looks good :heart_eyes:!

Thanks :grin:

and the best way is to externalize the concerns instead of doing everything ourselves.

Truth!
This issue makes me very happy, I think we're definitely heading in the right direction. I'd be very curious to see a branch where we can migrate a few of our bigger components end to end with this HOC chain.
Sounds good @alitaheri!

Thanks :grin: I'll go on and work on the warpgate. after it's done and all works as expected I'll write tests and documentations for both the warpgate and the memo. Then we can migrate the entire code base and live a happier life :laughing:
However, before complete migration I plan on breaking some parts of the code so we can implement these easier. right now, some files are monstrous!

This was good work, but things are changing with next. Closing.


As an organization interested in Justice40, I'd like an API so that I can automate my consumption of Justice40 data

Description
Justice40 publishes data and methodology on the Climate and Economic Justice Screening Tool (CEJST). The published data is structured and reasonably easy to consume, but there is no long-term strategy around publishing, versioning, or discoverability.
Additionally, Federal Agencies and NGOs have asked for a more formal API to make it easier to incorporate Justice40 data into their own systems for display and comparison between indices.
Solution
The solution is to publish Justice40 data and documentation via a simple, versioned API available at an easy to find Justice40 subdomain (e.g. **api**.environmentaljustice.gov). To aid in discoverability, that API should be defined using the OpenAPI specification and cataloged on data.gov.
Published data for each version should include:

Methodology and input data sources
Documentation such as technical guides, communities lists, and codebooks
Justice40 result data such as scoring result spreadsheets and geographic results in a standard format (e.g. GeoPackage)
Map data (e.g. tiles)

Additional Considerations
Data Formats
All data should be published in open, easily consumable formats. The specific format for files should be determined by a combination of openness and ease of use. For geographic data, this may be GeoPackage or GeoJSON. Spreadsheets should be published as CSV files, and documents should be PDF or Markdown.
All of this data should be generated as part of the Justice40 data pipeline.
Individual datasets should be published in a single format (i.e. do not publish the same information in multiple formats). While some sites publish their data in as many formats as possible, it's impossible for Justice40 to anticipate the desired data format for every consumer; therefore, Justice40 should pick open, common formats and allow consumers of Justice40 data to perform any translations necessary to make the data consumable by their system.
Published Data
The data published in each API version should be comprehensive; that is, there should be enough data to describe the API and the data available, define how to use the API and data, and, of course, there should be the data itself. Right now, that list includes the information above, but it could change as the API evolves.
API Versioning
Justice40 disadvantaged communities and scores may change over time. Some agencies may immediately shift to using the new score, but some may not. Because of this – and because agencies sometimes need to review older scores – it's critical that any Justice40 API include versioning. Major revisions of the score should receive their own version number, and minor revisions that have an impact on the score may receive a minor version number.
Sometimes agencies do not care if score data has changed; for example, some agencies may only want to show Justice40 map tiles on their map. In that case, Justice40 should maintain a current version of their API, always mapped to the latest version (e.g. api.environmentaljustice.gov/current/ could be mapped to api.environmentaljustice.gov/v1/).
It is beyond the scope of this request to determine how to implement API versioning (whether versioning is in the header, the url, or some other form).
Change Announcements
It is important to let agencies know of changes to the API. In addition to information in the OpenAPI specification, a process should be developed to announce API changes. This may involve a mailing list, a Google group (including the existing group), or some other way for agencies to subscribe to notifications of API updates.
Next Steps
Once this API is in place, client applications, such as CEJST, should be updated to use the API as their source of data. Existing versions of the data should be deprecated and agencies should be given up to 6 months to update their code to use the new API(s).

I made some small grammatical/punctuation edits to the above.
Outstanding question for consideration: Do we want to include guidance on how to treat the data sources that we pull in? Is the aim to be a re-publisher of other organizations' data or are we only interested in publishing data that results from USDS transformations?

awesome write up!

Outstanding question for consideration: Do we want to include guidance on how to treat the data sources that we pull in? Is the aim to be a re-publisher of other organizations' data or are we only interested in publishing data that results from USDS transformations?

Probably ultimately a question for Kameron, but my $0.02 is that we should not be a republisher of data (we should stick to publishing results and information about how we got to those results).

My 2 cents, my agency is wanting a lot of downstream app development using the CEJST output data, and speaking of republishing data, the only way I can deliver is....to republish the CEJST data. Having a REST API exposed (it currently is not) would alleviate that problem. I don't think the question is about the input data (used to create the CEJST output).


Case-sensitivity

Gread addon!
Could you add an option, or make it the default, that it doesn't check for case-sensitivity?
Edit: Got it working by prepending (?i) to your compiles, for example regex.compile("(?i)" + pattern[0]).

Hi there,
Thanks for enjoying the plugin!
Great idea. I've just added a case sensitivity checkbox to the settings.

Let me know how it goes.
It will be included in the v2.2.0 release in the asset library soon, or you can test it from repo.


Redirection from default locale in homepage

This is related to #67. It looks like that this is still not resolved:

"en" is default locale, mydomain.com is homepage of english version, mydomain.com/en shows same page with different URL. Should be redirected to mydomain.com...

I don't know if it is good or bad in SEO perspective but my client wants to have that redirection. Personally I agree with him, because I think we should have only one URL with the same content.
So I modified FluentRootURLController (at line 84):
} else if ($locale == $domainDefault) {
    return $this->redirect(Fluent::locale_baseurl($locale), 301);
}

I may create a pull request, but I don't know if it is good behavior. Also I didn't tested how it works with locale detection and saved locales.
May be it should be configurable?

You are right in that this is preferred behaviour; It might be risky to force a redirect in core, but you can probably solve your issue with a htaccess rule in your case.
The reason I feel that it's risky is that we've had lots of issues with redirects being wrong in this module, and I'd prefer that the module never did any redirects, instead leaving it up to user code. This was the motivation behind turning off all redirects by default.

But if I add in .htacces
Redirect 301 /uk/ /

after redirect my URL looks like
http://[my-site-name]/?url=/uk/
it is also not good for SEO
@uniun code not wokr for me
I add next
}  else if ($locale === 'uk_UA') {
   return $this->redirect(Fluent::locale_baseurl($locale), 301);
}

p.s. my default locale is uk_UA

Redirect 301 /uk/ / isn't the best way to write URL redirects in .htaccess
RewriteRule ^uk/?$ / [R=301,L,QSA] is better and should prevent the ?url=/uk/ showing.
You can write that locale check in your own _config.php I'd have thought.

Closing due to inactivity, feel free to reopen if this is still a problem


resize nullpx nullpx 无法触发滚动操作

Describe the bug
控制台打印 resize nullpx nullpx

Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

麻烦提供下复现步骤和版本号

The same thing happens to me.

codemir

The same thing happens to me.
 codemir

Can you provide a reproducible case or complete code? I am unable to reproduce this issue.

I've hit this bug as well using
"codemirror": ">=5.64.0 <6",
"codemirror-editor-vue3": "^2.7.0",

resize nullpx nullpx is only seen when height and width props are null.
https://codesandbox.io/p/sandbox/happy-northcutt-ylg489

I've hit this bug as well using
"codemirror": ">=5.64.0 <6",
"codemirror-editor-vue3": "^2.7.0",

resize nullpx nullpx is only seen when height and width props are null - ie the default.
https://codesandbox.io/p/sandbox/happy-northcutt-ylg489

Thank you for providing the case. I've noticed the issue, but from the case, it seems that only the console output is incorrect, while the rendering is fine. What is the situation on your end? I need to further confirm the issue.

@rennzhang correct: rendering is fine, only console output is wrong.


Can you share the dataset and approach for solving this issue?

Dataset :
[Skin Cancer ISIC] https://www.kaggle.com/datasets/nodoubttome/skin-cancer9-classesisic
Approach : This model is implemented using TensorFlow, Convolutional Neural Network, Seaborn, Matplotlib, PIL, scikit-learn

Hi @Sindhu-2004 can you please share your deep learning approach a bit briefly? Need some clarification in the architectures/methods/models you are trying to implement here.

Hi! @abhisheks008 I would like to do this project.
Dataset : HAM10000 (7 classes of skin lesions)
Approach : For image preprocessing I will be experimenting with dull razor, k-means or YOLOv4. After that I will be applying Transfer learning techniques like Resnet or Mobilenet and adding my own customized ANN layers after that. Finally I will apply KerasTuner for  Hyperparameters  and plot the graphs for results.

Hi! @abhisheks008 I would like to do this project. Dataset : HAM10000 (7 classes of skin lesions) Approach : For image preprocessing I will be experimenting with dull razor, k-means or YOLOv4. After that I will be applying Transfer learning techniques like Resnet or Mobilenet and adding my own customized ANN layers after that. Finally I will apply KerasTuner for Hyperparameters and plot the graphs for results.

But this issue is raised by another contributor, you can look for the issues which are raised by me.

@abhisheks008  But your issues has been assigned to someone else.

@abhisheks008 But your issues has been assigned to someone else.

Not all the issues have been assigned. Check out in the issues section, many of them are not assigned.

Along side EfficientNet can you implement 2 more architectures for this project?

I would like to add architectures like VGG-16 to develop a model, which contributes to the improvement of accuracy and ResNet (Residual Neural Network) which is used to obtain the diagnosis report as a confidence score with high accuracy.

Cool then VGG, EfficientNet and ResNet are the final models right? @Sindhu-2004

Yes sir

Assigned @Sindhu-2004


Installing Django application

Bootstrapping the Django application

"tasties" folder with the python files was created
"bootstrap.sh" modified to automate the environment

Closes #7

LGTM


Skipping backend devices

Devices that used as backed for logical layers (dmraid, bcache, LVM , etc) have "masters" in Ansible "devices" fact. This patch skip such devices on initial lookup.

Closing this due to inactivity, feel free to re-open, thanks!


Flutter CanvasKit: holding down Control in a Windows browser prevents scroll wheel detection

I've attached a sample Flutter app to demonstrate the issue.
When compiled with CanvasKit and the build served with a simple web server, the behavior of the app is different on Mac and Windows browsers.
On Mac, when the Control key is held down and the mouse wheel scrolled, the scroll wheel activity is detected. This also works when the shift key is held down.
On Windows, the default behavior for Control/ScrollWheel is to zoom the browser in and out. This can be disabled in Javascript with. The attached app index.html has the following in it:
  <script>
    document.addEventListener("wheel", (e) => (e.ctrlKey || e.shiftKey)
      && e.preventDefault(), { passive: false });
  </script>

With this in place, everything behaves as expected on the Mac.
In browsers on Windows, however, when the control key is held down, the app cannot detect scroll wheel movements. When shift (or other keys) is held down, it can.
ck_wheel_test.zip
This behavior can be replicated on latest Flutter master.

@mjohnsullivan , issue landed in engine, waiting for roll into flutter master.

@mjohnsullivan , issue landed in engine, waiting for roll into flutter master.

Thanks for landing the fix!

Thanks for landing the fix!


User Install: application doesn't stay pinned

Issue Type: Bug
So, I kept getting prompted to switch to user install of VS Code with the promise of better update experience.  Now every time VS Code updates it removed my pinned taskbar icon and I have to move it back to where I had it and re-pin it.
VS Code version: Code - Insiders 1.26.0-insider (6babef94104b27b252929324aa3c2d69cd38e9f2, 2018-07-16T05:18:37.865Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz (16 x 2394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.92GB (8.25GB free)

Process Argv
C:\Users\ed.evans\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe

Screen Reader
no

VM
0%

Extensions (29)

Extension
Author (truncated)
Version

aurelia
Aur
1.0.3

solargraph
cas
0.17.5

vscode-markdownlint
Dav
0.18.0

gitlens
eam
8.5.0

vscode-npm-script
eg2
0.3.5

platformio
for
0.2.5

rest-client
hum
0.19.0

VS-code-vagrantfile
mar
0.0.7

terraform
mau
1.2.3

rainbow-csv
mec
0.4.2

mssql
ms-
1.4.0

python
ms-
2018.6.0

azure-account
ms-
0.4.1

azurecli
ms-
0.4.2

cpptools
ms-
0.17.6

csharp
ms-
1.15.2

Go
ms-
0.6.84

PowerShell
ms-
1.8.1

vs-keybindings
ms-
0.2.0

team
ms-
1.136.0

debugger-for-chrome
msj
4.8.0

vscode-docker
Pet
0.0.27

Ruby
reb
0.18.0

vscode-icons
rob
7.24.0

vscode-hexdump
sle
1.6.0

python
tht
0.2.3

azure-iot-toolkit
vsc
1.0.0

vscode-arduino
vsc
0.2.17

vscode-react-native
vsm
0.6.12

But the update is smoother, right? :fireworks:

Now every time VS Code updates it removed my pinned taskbar icon and I have to move it back to where I had it and re-pin it.

That is interesting... What happens to that pin after an update? Can you show me?

I can confirm this has happened to me on my Windows 7 computer. After the user update, all my shortcuts, including the pinned one in the taskbar, become invalid (Windows prompts you to remove them if the target no longer exists). I have to manually hunt down the vscode executable in the Program Files directory to relaunch it. I get no errors during the update, and when I manually relaunch it everything works.

When I went to record the latest update, the pin was left alone this time and all worked correctly.  I think the original pin was from the system install that got modified to launch the user installed VS Code.  Not sure.

@eeevans That makes more sense. Closing it then. :+1: Thanks for the update.


⚠ Bofrost.at has degraded performance

In ff4f52b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 881 ms

Resolved: Bofrost.at performance has improved in e54f571 after 21 minutes.


Update installation instructions on Github

Hi Jordao, just noticed a small convenience thing, the install instructions with more conda deps from the docs are needed e.g. for a MacOS install. The instructions in the README.md lead to dep problem with higra.

Thanks @bentaculum , I'm updating the README on #152


🐛 [firebase_core] Firebase.initializeApp fails with error when using Firebase Emulator demo project.

I am using the Firebase Emulator to develop.
I am using a Firebase Emulator demo project that has no associated firebase/gcp cloud project actually created.
A demo project is defined here: https://firebase.google.com/docs/emulator-suite/connect_firestore
I use the following command to start the emulator with a specific demo project name...
firebase emulators:start --project demo-test --only firestore
The emulator successfully starts and hosts at localhost:8080.
Then when I try to run initializeApp in my Firebase Project as follows...
await Firebase.initializeApp(name: "demo-test");
    FirebaseFirestore.instance.settings = const Settings(
      host: 'localhost:8080',
      sslEnabled: false,
      persistenceEnabled: false,
    );

I get the following error...
Restarted application in 2,058ms.
E/flutter ( 7724): [ERROR:flutter/lib/ui/ui_dart_state.cc(198)] Unhandled Exception: [core/not-initialized] Firebase has not been correctly initialized.
E/flutter ( 7724):
E/flutter ( 7724): Usually this means you've attempted to use a Firebase service before calling `Firebase.initializeApp`.
E/flutter ( 7724):
E/flutter ( 7724): View the documentation for more information: https://firebase.flutter.dev/docs/overview#initialization
E/flutter ( 7724):
E/flutter ( 7724): #0      MethodChannelFirebase.initializeApp
package:firebase_core_platform_interface/…/method_channel/method_channel_firebase.dart:113
E/flutter ( 7724): <asynchronous suspension>
E/flutter ( 7724): #1      Firebase.initializeApp
package:firebase_core/src/firebase.dart:40
E/flutter ( 7724): <asynchronous suspension>
E/flutter ( 7724): #2      _MyHomePageState._asyncInit
package:mobile_app/main.dart:53
E/flutter ( 7724): <asynchronous suspension>
E/flutter ( 7724):

The expected behaviour is that Firebase should be able to be initialized with a pure emulator demo project.

Hi @Turburlar, Thanks for filing the issue After firebase initialization can you please try defining your settings by running

I have updated my code to take into account your suggestion.
The following code gives the same error...
    await Firebase.initializeApp();
    FirebaseFirestore.instance.useFirestoreEmulator('localhost', 8080, sslEnabled: false);

@maheshmnj Can you remove the blocked:customer-response tag please.

@Turburlar It was removed when you commented.

@Turburlar
Try by calling WidgetsFlutterBinding.ensureInitialized(); before initializing your app.
ie
WidgetsFlutterBinding.ensureInitialized();
 await Firebase.initializeApp();

Thanks for the update. Using the code sample above and initiating firebase emulator with the command provided above, I am getting same error as reported:
Launching lib/main.dart on iPhone 13 in debug mode...
Running pod install...
Running Xcode build...
Xcode build done.                                           55.8s
Debug service listening on ws://<IP_ADDRESS>:50903/UT_SjCI4aPo=/ws
Syncing files to device iPhone 13...
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: [core/not-initialized] Firebase has not been correctly initialized.

Usually this means you've attempted to use a Firebase service before calling `Firebase.initializeApp`.

View the documentation for more information: https://firebase.flutter.dev/docs/overview#initialization

#0      MethodChannelFirebase.initializeApp (package:firebase_core_platform_interface/src/method_channel/method_channel_firebase.dart:113:9)
<asynchronous suspension>
#1      Firebase.initializeApp (package:firebase_core/src/firebase.dart:40:31)
<asynchronous suspension>
#2      main (package:testdemo/main.dart:7:3)
<asynchronous suspension>

You haven't setup Firebase correctly. Ensure you have ran flutterfire configure in the root of your app directory and setup the platforms you require.


Accept the "200 Connection Established" response

According to the standard (see https://tools.ietf.org/html/draft-luotonen-web-proxy-tunneling-01#section-3.2), the valid (or even preferred) proxy response is 200 Connection established

If everything is in order, the proxy will make a  connection to the destination server, and, if successful, send a "200 Connection established" response to the client.

I tested it with my local proxy server (Telerik Fiddler) which returns "200 Connection Established" for new tunnels.
So, this change adds the "200 Connection Established" as a valid response (and also uses case-insensitive comparison, because the standard says "Connection established" and at least Telerik Fiddler proxy uses "Connection Established"...)

What's wrong with .Contains()?

@Laiteux String.Contains() doesn't have an overload that accepts the comparisonType as the second argument (we need it to specify the type of search - to ignore letter casing). String.IndexOf() has :)

Ohh, I thought this was using .NET Standard 2.1 in which case it would have such an overload. Nevermind then (:

@Rychu-Pawel could you please review it?

@DominikPalo of course. Thanks for mentioning me. I think I have never got a proper notification about this PR.


Off by 1 in slice of OffsetsBuffer

The implementations of slice on OffsetsBuffer calls slice on the underlying Buffer directly:
https://github.com/jorgecarleitao/arrow2/blob/2ecd3e823f63884ca77b146a8cd8fcdea9f328fd/src/offset.rs#L443-L459
But this is incorrect because then a slice with length 1 returns an OffsetsBuffer with only one value in the buffer.
I'd argue that either the documentation could be better that this is slicing the raw buffer and not the offsets that a slice of values of that length would have. Or the code could add the +1 itself.

I don't think this is incorrect? It slices the buffer? It doesn't do any semantic handling.

I found it confusing because at least in a couple places, the API does do semantic handling instead of raw buffer operations. E.g. with_capacity reserves space for n + 1 elements, so the input number refers to the number of values, not the number of offsets.
In any case, it's probably too disruptive to change the API now, so a docstring improvement would probably be best


Make RequestHandler an interface

Making RequestHandler an interface rather than an abstract class for consistency with ReactiveSocket, makes it more flexible to extend.

👍


So the geniuses at discord HQ decided in their wisdom that nicknames don't need to be unique...

A few options:

Always append the 4 digit id to nicknames.
Somehow rework everything to work with double nicknames.

I don't like the first one simply due to it being ugly, the second option isn't very attractive either.
So I'll need to think about it.

Just my humble opinion: the first solution (concat of nickname and four digits) is simple, avoids confusion, and is still very readable. I actually wished that the four digit code was displayed in Discord itself when using the compact layout (which hides profile pictures, the only way to distinguish users in such case).


CO-2380_Errors_when_deleting_non-empty_CO

Unload unnecessary associations during a CO delete

In general, adding dependent => true is not the correct behavior for most of the models here. eg: Deleting a CoMessageTemplate should not delete the Authenticator that points to it. Deleting a CO Person should not delete History Records where that CO Person was the Actor (this is why Expunge rewrites those records). Deleting a Pipeline should not delete an OrgIdentitySource that was configured to point to it.
The more fundamental problem in that Cake's dependency processing isn't that smart, so when you delete a CO it may or may not correctly delete things in the right order. This is why there's already a bunch of special code for CO deletion -- that's where changes probably need to be made to make sure the records get deleted in the right order.

Please change the base branch back to develop.


[Bug]: TestContainers cannot be used without JUnit4 dependency

Module
Core
Testcontainers version
1.19.0
Using the latest Testcontainers version?
Yes
Host OS
doesn't matter
Host Arch
doesn't matter
Docker version
doesn't matter

What happened?
I want to use TestContainers in a project with JUnit 5.
I want to exclude JUnit 4 dependency to avoid the risk that some of our developers occasionally use wrong annotations.
dependencies {
  testImplementation("org.testcontainers:junit-jupiter:1.19.0") { exclude group: 'junit' }
  testImplementation("org.testcontainers:selenium:1.19.0") { exclude group: 'junit' }
}

But my project doesn't even compile without JUnit 4.
Relevant log output
> Task :compileTestJava FAILED
/Users/andrei/projects/selenide-examples/testcontainers/src/test/java/org/selenide/examples/SearchTestWithDocker.java:31: error: cannot access TestRule
      .withRecordingMode(RECORD_ALL, new File("build"))
      ^
  class file for org.junit.rules.TestRule not found

Additional Information
No response

Duplicated of https://github.com/testcontainers/testcontainers-java/issues/970


Log warning when Shopify indicates deprecated API call was performed

Warn via the standard ActiveResource::Base.logger when ShopifyAPI makes a deprecated API call.

Thanks. Updated!

I'm trying to tophat this locally with a copy of Shopify_cli and I'm not getting a depreciation warning  out of the box. The nice thing about the OAuth warning is that if Im just hacking away with the cli, it spits out that warning right away. Anyway we can also log this to stdout all the time as well? Or should we  update the cli?

Ah interesting. I think the warn being called by the OAuth.revoke is actually Kernel#warn, which probably behaves differently than the ActiveSupport::LogSubscriber#warn being called in DetailedLogSubscriber in this PR.
We could warn via both the Kernel and ActiveResource::Base.logger warn methods?

I think we should. I just initialized the ActiveResource Logger in the CLI and its just too much detail. Good for a server log, not for a quick test hack.

Makes sense to me.

Looks like I need one more review from @Shopify/app-partner-dev-tools-education

Re-ping @Shopify/app-partner-dev-tools-education 🙏 - I just need one more review from your team to ship this, please and thanks!

np and thanks Tyler! <3


Add a test case for the component supplier integration

Changes Unknown when pulling 2a178ed16f570e8691b948e1a36f2331b0b3d4c8 on supplier_tests into ** on master**.


Generic Sobel Edge Detector

To test how the Sobel edge detector work with generic code.

Added simple Sobel edge detector. It was easy.


Tutorial Feedback

Hello,
Thanks for this tutorial. I would like to help improving it by giving some feedbacks, if that's not the right place please tell me:
1 - Not a git expert (yet) but for the Step-by-step tutorial (#0 through #8) it would be nice to give the command to clone just the branch, and not the master : git clone -b es5-tutorial --single-branch https://.....
2 - step 3 description is the same as step 2 description
3 - JSDoc for UserController, selectUser are incorrect (wrong params or missing params)
4 - In tutorial_5.html, the icon registering is not highlighted, nor the declaration of UserController as ul and the adding menu icon in the toolbar. (might be intented)
5 - By the way, wouldn't it be clearer to call UserController "uc" insteadd of ul (why ul ?), and users elements "user" instead of it (like iteration ?)
6 - You switch between ng-svg-src and ng-svg-icon without telling why, and in this case it makes no difference.
7 -  In tutorial_6.html, the icon registering is not highlighted, nor hiding the menu icon when displayed or the click support  (might be intented)
8-
A last point which is not directly related to this tutorial but more to the angular-seed project :
For new comers, it's really overwhelming to see all thoses node_modules install, considering those are mainly intented for testing purpose. Beginners need to see each new point step by step, so it seems unnecessary to run "npm install" (which downloads like 1 billion files), when all you need to do this tutorial is "bower install".
Maybe you should come to this point when we get to the e2e testing part, so that it's really clear why all those modules are for.
Thanks again for this tutorial.

Within 1-2 weeks, we will have a full video set "Introduction to Angular Material" on Egghead.io. Those videos will be using the ES5 tutorials and provide some details. I will also be presenting an ES6 tutorial set at the ng-nl conference in February; that recording should be on YouTube before the end of February.

Cool, eager to see that.


Feature/165 make plugin work with real data

I hope i didnt missed some place where dummy data is being used

Looks good! But in the ticket it says "Also get the archiving of the latest runs working again". I think this means you should also archive latest runs.
If you have time it would be also nice if you can fix the following behaviour. So when you open the IDE and you already have pitest reports they will get displayed. But when you go in you build file and remove one of the plugins and add them back then the results are not displayed again. It would be nice that if the pluginchecker is done the loading of pitest results is triggered.

Adressed requested changes


Ingest bike data

Create script to pull Lyft bike data on the bike stations and ridership for all three cities. This should be staright forward across cities because all owned by Lyft.

Lower priority


PHP grpc pecl install takes about 15 minutes to install

PHP grpc pecl install takes about 15 minutes to install
Docker - ubuntu 14, in the docker file
RUN apt-get install -y zlib1g-dev RUN pecl install grpc

You can try increase the parallel compile jobs using MAKEFLAGS, e.g. MAKEFLAGS=" -j10".

The discussion has also taken place in #34278 and #23626

For further discussion, please go to #34278


On Publish error doesn't disconnect the client

Hello,
On on_publish HTTP Callback, if I don't return success, it doesn't start publishing. But the client doesn't get disconnected, it retries and retires.
I have tried sending HTTP code other than 200, and also int value other than 0, but same result.
Is there any way to disconnect the client if I don't send success response on on_publish?

I will check it.

+1


bringing in updated help text

Will sit below the query box, like so:

An alternative could be to put this in its own html file behind a help link on the connector. Looks like the images haven't been updated for the interactive connector or the login process, we should probably take care of that.


term move and rename, possible

I was about to request  a new child of
FYPO:0002423	inviable after spore germination, without cell division, septated cells with abnormal cell shape
(stub)
inviable after spore germination, without cell division, multi-septated cells swollen elongated cells
but I was pretty sure this phenotype existed already
its this:

Sorbitol partially rescued sbg1Δ cells and sbg1Δ cells germinated on media with sorbitol survived for up to 3 days. However, cytokinesis still failed and cell
morphology was defective in these cells, which were elongated, multi-septated, and swollen (Fig 1B and S2 Movie).
However, since I was looking at these earlier, I remembered we had described this slightly differently in cell cycle/morphology paper.
It's
inviable after spore germination, without cell division, with swollen, branched, elongated germ tube
With the branched,
FYPO:0002515
FYPO:0003005
we can assume they are also septated (the branching in this context is a result of incorrect cytokinesis but the cells are septated (often multispetate).
(Jacky -this is rubber glove phenotype!)

I've been assuming I should wait for Jacky to confirm what to do before I change anything (and then I'll check back to make sure I understand what to do).

I'm pretty sure we do need to do this.
rename the existing term to include "multi-septate" not just septated

see also https://github.com/pombase/curation/issues/1219
note to self

Hi Midori
I have looked at the thread but I'm confused as to  what needs doing . Is this sto do with the  branched swollen multiseptated cells.
Jacky
From: Midori Harris <notifications<EMAIL_ADDRESS>Reply-To: pombase/fypo <reply<EMAIL_ADDRESS>Date: Thursday, 15 December 2016 at 14:35
To: pombase/fypo <fypo<EMAIL_ADDRESS>Cc: Subscribed <subscribed<EMAIL_ADDRESS>Subject: Re: [pombase/fypo] term move and rename, possible (#2927)
I've been assuming I should wait for Jacky to confirm what to do before I change anything (and then I'll check back to make sure I understand what to do).

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/pombase/fypo/issues/2927#issuecomment-267342129, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANVVaFkZVch015BzJjqQX093SFeTtjKsks5rIVBCgaJpZM4LKx-U.
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.

So existing term
"FYPO:0002423	inviable after spore germination, without cell division, septated cells with abnormal cell shape"
Jacky, the existing  annotations to this term from the deletion project are these:
http://www.pombase.org/spombe/related/FYPO:0002515
(I think  bgs1 was rubber glove phenotype...do you have a picture)
These phenotypes (based on the one above) appear to be  also both "multiseptated and elongated" (they don't look like traditional elongated cells , because the defect is separation.
The look a bit like one of those long balloons that has been made into "sausages".
Although now I am wondering, are these still a single cell, or are they really multiple cells chained together...it seems like the latter. so....we say that these cells have no division, but it looks as though they divide, but do not fully separate....
SPBP22H7.03 is just published as sbg1
So I'm not sure either.....I have stuggled with these cell separation mutants  before.... I have a folder with questions and examples.......

maybe its really this?
http://www.pombase.org/spombe/related/FYPO:0001971

This is kin1
it looks  quite similar?

anything to do for this one?

I will take this. I would like to check what this phenotype is annotated top.


Getting the ERROR "This driver instance does not have a valid session ID (did you call WebDriver.quit()?) and may no longer be used." When I try to use restart() or close() method

Hi there!
I am trying to execute an extremely simple code. No page object, no method calling from different classes , no customizing configuration file.  I am just trying to open a browser, then close it and then open a new browser instance.
#My Conf.js file is :
exports.config = {
  //directConnect: true,
  framework: 'jasmine2',
  seleniumAddress: 'http://localhost:4444/wd/hub',
  specs: ['spec.js']
}

#My spec file is:
const { browser, protractor } = require("protractor");
describe('abcd',  () => {
    it('Restart the browser', () => {
        browser.get('https://material.angular.io/')
        .then(()=>(browser.restart()))
        .then(()=>(browser.get('https://material.angular.io/')));
    });
       it ('2', async  () => {
        await browser.waitForAngularEnabled(false);
        await browser.get('https://www.google.com');
        await element(by.xpath("//input[@name='q']")).sendKeys('asdaf');
        await browser.close();
    });`
});

I want to close the browser after each It block and open a new instance of a browser in the next It block. I know that we can use restartAfterEachTest in the configuration file to restart browsers, but I am not looking for that, I want to close and open browsers from my Spec file.
If I use browser.restart() it shows me the is error "This driver instance does not have a valid session ID (did you call WebDriver.quit()?) and may no longer be used." and the IT block is failed.
If I use browser.close() , the first It block is passing but all subsequent It blocks are getting failed immediately and the error is "Invalid Session ID".
Looking for a solution, thanks in advance

ok

@Avijoy7 : You can use afterEach function to achieve this
afterEach (function(){
        driver.close();
    });

@Avijoy7 : You can use afterEach function to achieve this
afterEach (function(){
        driver.close();
    });

I have already mentioned in the description that methods like, restart(), close(), quit() are not working. It's not about creating another block of afterEach. anyways, thanks for your help


Not working on YouTube?

Not sure if the feature has been added yet, but I can't seem to find an extension which removes the outbound tracking of links on YouTube (IE: https://www.youtube.com/redirect?q=) It would be nice to see such thing added.
Many thanks.

I attempted making some code which "Works" sometimes, and sometimes does not.
`var newurl;
document.addEventListener('DOMNodeInserted', OnElementInserted, false);
function OnElementInserted(event) {
if (typeof(event.target) === 'undefined' && typeof(event.srcElement) === 'undefined') {
return;
}
var target = null;

if (typeof(event.target) === 'undefined') {
    target = event.srcElement;
} else {
    target = event.target;
}

if (target === null) {
    return;
}

var element = event.target;

if (element.tagName === "A")
    cleanUrl(element);

}
function cleanUrl(url) {
var index = url.href.indexOf("&q=");
if (index !== -1) {
    newurl = decodeURIComponent(url.href.split("&q=")[1].split("&")[0].toString());
} else {
    index = url.href.indexOf("?q=");

    if (index !== -1) {
        newurl = decodeURIComponent(url.href.split("?q=")[1].split("&")[0]);
    }
}

url.href = newurl;
url.src = newurl;

}`

Added in https://github.com/newhouse/url-tracking-stripper/pull/75 thanks!!!


Fix: renamed default config file

Resolves #725
Quality Assurance: Passing checks

@pavlovcik @rndquu , last PR was automatically closed as GitHub suggested to remove the commit and then resolve the conflicts. No extra changes are made. Please have a look at this.

"QA" needs evidence like links

@rndquu , any more suggestions or changes from your side on this?

The PR merge should be happening with the relevant changes in pay.ubq.fi right? @rndquu

The PR merge should be happening with the relevant changes in pay.ubq.fi right? @rndquu

You're free to merge the current PR
There is already a related issue for onboarding refactoring
We will deploy a new version of pay.ubq.fi only when https://github.com/ubiquity/pay.ubq.fi/issues/135 is implemented so that nothing is broken

Ok let me handle the merge once the conversations resolved.

@Wholesomebruh  bump for the second request:

2/ Then we should move ubiquibot-config-default.ts into the src folder to make sure it's being built/checked

@0xcodercrane , moved the ubiquity-config-default to src folder.

@0xcodercrane , moved the ubiquity-config-default to src folder.

This can break other systems, including the partner onboarding @rndquu rfc

@0xcodercrane , moved the ubiquity-config-default to src folder.

This can break other systems, including the partner onboarding @rndquu is this all clear?

I don't think so

@0xcodercrane , moved the ubiquity-config-default to src folder.

This can break other systems, including the partner onboarding @rndquu is this all clear?

I don't think so

It does break the onboarding but we already have a related issue for onboarding refactoring so we won't deploy a new version of pay.ubq.fi unless the https://github.com/ubiquity/pay.ubq.fi/issues/135 is implemented

From my understanding of my questions before merging the PR, I was free to merge right?
Ideally, we shouldn't merge the pr if it breaks something even if it is partner onboarding.
So I guess the solution here is to wrap up the related issues as soon as possible.

From my understanding of my questions before merging the PR, I was free to merge right?

yes

So I guess the solution here is to wrap up the related issues as soon as possible

yes


Error when creating a file on SMB share

When I create a file on an SMB share from within NeoTree I get the following error message:
Could not create file <filename you entered>
The file is created though but is not immediately visible in Neotree and the file is readonly. When I create a file with the :w command everything works as expected.
I attached a screenrecord as requested by @pysan3
https://user-images.githubusercontent.com/16334447/235639497-7c2ca0fe-3fd0-49cc-80ae-e8c83505f58e.mp4

It's at the end of the video.  Or do you mean something else? Just in case here is the output shown in the video:
-rwxr-xr-x 1 romano wheel 5  2. Mai 12:07 test2.txt
-r-xr-xr-x 1 romano wheel 0  2. Mai 12:07 test.txt

I couldn't diagnose the problem sadly.
I instead created a PR (#912) to workaround the issue we are having here.
IF that PR is merged, you will be able do something like this to force overwrite the permission so that you can work as normal.
event_handlers = {
  {
    event = "file_added",
    handler = function (destination)
      local uv = vim.loop
      local file_info = uv.fs_stat(destination)
      if not file_info then
        return
      elseif file_info.type == "file" then
        if vim.startswith(destination, "/mnt/share/samba/or/whatever") then
          vim.fn.setfperm(destination, "rw-r--r--") -- read `:h setfperm` for more options
        end
      end
    end,
  }
}

For more info, read this discussion as well.
https://github.com/nvim-neo-tree/neo-tree.nvim/discussions/708

Thank you!

Merged. Closing.

Just wanted to notify that I think it's properly fixed now with #1200.


⚠ Fortnite has degraded performance

In 41a0da9, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1528 ms

Resolved: Fortnite performance has improved in 89332bb.


[OTHER] Switch from Rinkeby testnet to Mumbai testnet ?

What would you like to share?
The first iteration of the dao dapp is running on Rinkeby Testnet. ETH gasfee are super high, maybe we should switch to Mumbai testnet ?
Additional information
No response
Would you like to work on this issue?

[ ] Yes, I want to work on this issue!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Yes it would be better

Anything works for me i have 18eth i am rich 😆 🤑  on rinkeby network only 🥲.

Same, anything works for me,
Btw Should create one bounty for rinkbey to mainnet bridge😂

@KukretiShubham You mean chainwiz bounty ?

no no, I was trying to joke. Ik I m bad at it.


Pointer broadcasting should be limited to within PDF page

Will be easier to handle if mouse location can be bounded by image (otherwise it's hard to reconcile between multiple users' different window proportions)

How would this affect #43? Would doodles be limited to page dims only?

Another idea: measure pointer positions outwards from the absolute center of window.innerWidth and window.innerHeight?


Project-factory: allow folder_id to be defined in defaults_file

Currently, setting the folder_id in defaults.yaml but not in the project.yaml, results in:
╷
│ Error: Unsupported attribute
│
│   on main.tf line 44, in module "projects":
│   44:   folder_id              = each.value.folder_id
│     ├────────────────
│     │ each.value is object with 1 attribute "labels"
│
│ This object does not have an attribute named "folder_id".
╵

This change allows you to set the folder_id in the defaults.yaml and have it be used for all the projects selected by the glob pattern.

Thanks @Malet!


Quickfix: revive legacyscheme

There are event recorders (template, apps, maybe others) which use the encoder from the legacy scheme. This is wrong: since openshift-apiserver is separate the types are not in that scheme anymore and should not be.
This PR is a quickfix against the CI fires. It should be reverted and all references to legacy scheme should be removed.

/retest

/lgtm

I think the DC failures are probably because the first set of oc images from openshift/oc got promoted.  Merging this to move us a little further forward.


docs: incorrect/misleading instructions on PATH importing

This came up during a Discord discussion on #scons-help
https://discord.com/channels/571796279483564041/571796280146133047/1006057851858452510
Both the man page and User Guide give examples of importing the external PATH variable into the SCons build, but the way it is demonstrated is not ideal. This is the first example in both places:
import os
env = Environment(ENV={'PATH': os.environ['PATH']})

The problem with this and the other examples is they overwrite the platform-default value of the ENV dictionary, rather than adding to or updating it.   It turns out this is actually potentially fatal on modern Windows, where a variety of things don't work if %USERPROFILE% is not set, and this clobbers it, as well as %SystemRoot% (apparently needed for socket operations).  On a Mac, this would clobber the setting of PATHOSX (which SCons itself uses, though possibly only in the TeX tool).
In the case of the Discord discussion, following this recommendation did in fact break a build on Windows.
It seems we should not make this approach a primary recommendation, or at the very least, include a warning.  Explaining how to do it "correctly" may be a little tricky, though.... the basic model could be something like:
env.AppendENVPath('PATH', os.environ['PATH'])

But because that has to happen after the Environment creation, it may run into problems of tools needing the imported path to initialize themselves.

Something like += type functionality would be ideal.
ENV_PATH_REPLACE ENV_PATH_PREPEND

Well, we do have AppendENVPath and PrependENVPath. Not a replace function.  But as mentioned above, you have to call that after you've already made the env, and if something in the initialization depended on paths, then it's "too late" at that point.
It also looks like you can't do env = Environment(ENV={'PATH': "${PATH}:/some/other/bin"}):  apparently, in this context, the elements of ENV don't get substituted. Maybe that wouldn't even make sense.

I was thinking those vars would be specifyable in the Environment() call and modify the envvars before tool initilization.

Was thinking about this just now, and it wouldn't be hard to add a kwarg that lets you specify a dict of variables that are to be appended to, rather than assigned to. In fact, it took just a few minutes to prototype.  Of course, doing so leads to more questions.
First, specifically for a path, just appending doesn't work, as the execution environment is a special case: the construction variable is ENV, which is a dict whose path element PATH is the one you want to append to. Which suggests we also need a way to update that dict, not just self._dict but self._dict['ENV'] - or perhaps more appropriately, an arbitrary dict.  That's not hard to do, either.
Second, when/how should these additional things be applied?  The current flow in environment is like (summarized):
# apply platform

# set all the standard args outright (saving keys):
self.Replace(**kw)

# apply vars from variables (saving those keys too):
if variables:
    variables.Update(self)

# stash the things that were set:
save = {}
for k in keys:
    save[k] = self._dict[k]

# apply tools
apply_tools(self, tools, toolpath)

# Restore the "set" values that were saved off,
# so user-set values win:
for key, val in save.items():
    self._dict[key] = val

So should consvars.append happen up where the variables.Update happens? Or at the end?
The end bit of that flow is a little dodgy anyway, even ignoring any further additions: it's no good if tools clobber user settings, but it also could be bad if user settings clobber necessary things set up by tools. Seems like the end up that simplified sequence should be not replace but merge...


⚠ Fortnite has degraded performance

In 06d63ce, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1497 ms

Resolved: Fortnite performance has improved in fb55e41.


Post release automated changes for hybridcompute releases

Post release automated changes for azure-arm-hybridcompute

API change check
API changes are not detected in this pull request.


Remove all dependencies

Hi,
Noticing that npm install pulls in 60 MB worth of packages, and finding that a little excessive, I've managed to trim the dependencies down to 0 with the only notable user facing change being the removal of the support check, justified as follows:

The check is fragile, testing against specific terminal versions instead
of employing something like terminfo, but also testing environment
variables for certain continuous integration services and such.

The plain text output of terminal apps should speak for itself. Even on
supported terminals, attributes like colours and URLs may be stripped for
many reasons. Hence, either output the full URL, or accept that the link
may not be a link.

The xo linter was removed with no replacement. It depends on 469 packages but is of limited benefit for so little source code.

I’m not really sure what you’re expecting here. I’m not going to merge this for obvious reasons. All the dependencies have a purpose even if you fail to see so.

I’m not joking at all. Of course you might find the removal of some a bit drastic, but you can cherry pick as you wish. Specifically, execa and meow stood out to me as offering little benefits over builtins. xo is pretty useful but it pulls in 469 packages. Wouldn’t eslint do just as well?


Add support for multiple session factories at the same time

Problem:
Sometimes we need to use multiple Hibernate bundles on a resource endpoint at the same time. In some projects, this is a requirement and we can't refactor the code to use only one. We found that in the current code we are able to register multiple Hibernate bundles but we can only use one at a time (With the @UnitOfWork annotation). This PR is to add the ability to use more than one bundle in the same @UnitOfWork context.
Solution:
We changed the @UnitOfWork annotation to accept multiple values for the bundle name. Also, we changed the UnitOfWorkAspect to process all the selected bundles (instead of processing only one) in the same way as before. So when we perform any operation in the aspect we execute it in all the selected bundles.
This allows us to see all the selected bundles as a group in the way that if an error occurs and the transaction needs to be reverted they are going to be rollbacked in all the selected bundles, the same happens with the commit and clean operations.
Result:
The result is that we can select multiple bundles in the same @UnitOfWork by passing the values as follow:
@UnitOfWork(value={'bundle1', 'bundle2'})
or just
@UnitOfWork({'bundle1', 'bundle2'})
The change is totally retro-compatible and we can specify only one bundle by:
@UnitOfWork('bundle')
or use the default one (if we only register one bundle) by not passing any value.
@UnitOfWork
The rest of the system will remain exactly the same and also the use of Hibernate will not change at all.

@dropwizard/committers Does anyone want to invest some time into this PR to make it ready for Dropwizard 2.0.0?